DataCloud Tech LLC v. Advance Local Media LLC

I. Executive Summary and Procedural Information

• Parties & Counsel:
  • Plaintiff: DataCloud Technologies, LLC (Georgia)
  • Defendant: Advance Local Media LLC (New York)
  • Plaintiff’s Counsel: Stamoulis & Weinblatt LLC; Kent & Risley LLC
• Case Identification: 3:26-cv-01353, D.N.J., 02/10/2026
• Venue Allegations: Plaintiff alleges venue is proper in the District of New Jersey because Defendant has a regular and established place of business in the state and has committed acts of infringement there.
• Core Dispute: Plaintiff alleges that Defendant’s website infrastructure infringes three U.S. patents related to network communication, dynamic software deployment, and metadata-based content management.
• Technical Context: The technologies at issue relate to foundational aspects of web service delivery, including anonymizing user traffic, efficiently deploying applications to client devices, and managing web content generation.
• Key Procedural History: The complaint does not allege any significant procedural history, such as prior litigation or administrative proceedings involving the asserted patents.

Case Timeline

II. Technology and Patent(s)-in-Suit Analysis

U.S. Patent No. 7,209,959 - “Apparatus, System, and Method for Communicating to a Network Through a Virtual Domain Providing Anonymity to a Client Communicating on the Network,” Issued April 24, 2007

The Invention Explained

• Problem Addressed: The patent’s background section identifies privacy threats inherent in the standard HTTP protocol, which allows servers to record and trace a client's identity and browsing activity (’959 Patent, col. 1:57-65). Existing proxy servers are described as insufficient because they merely substitute one persistent identity for another, rather than providing true session-based anonymity ’959 Patent, col. 2:7-19
• The Patented Solution: The invention proposes a three-part system—a "deceiver", a "controller", and a "forwarder"—to create an anonymous communication session ’959 Patent, abstract When a client requests a website, the "deceiver" intercepts the request and asks the "controller" to find the website's true IP address. The "controller" then instructs the "deceiver" to return the IP address of a separate "forwarder" to the client. The client then communicates with the "forwarder", which relays traffic to the destination website, effectively masking the client’s and the destination's true IP addresses from each other for the duration of the session ’959 Patent, col. 3:45-4:13 ’959 Patent, Fig. 1
• Technical Importance: This architecture aimed to provide enhanced, session-specific anonymity for network communications beyond what was offered by conventional proxy servers at the time.

Key Claims at a Glance

• The complaint asserts at least independent claim 1 Compl. ¶17
• Claim 1 is a method claim with the following essential elements:
  • Responding to a client’s request to communicate with a destination website.
  • Setting up a forwarding session using a "forwarder" placed between the client and a destination server.
  • Using the "forwarder" to transfer packets such that neither the client nor the destination server is aware of the "forwarder"'s employment.
  • Using a "controller" to query a domain name server (DNS) to resolve the destination website's name.
  • Using a "deceiver" to receive the client's initial request and trigger the "controller" to query the DNS.
  • Initiating the forwarding session after the "controller" receives the response from the DNS.
• The complaint does not explicitly reserve the right to assert dependent claims.

U.S. Patent No. 7,246,351 - “System And Method For Deploying And Implementing Software Applications Over A Distributed Network,” Issued July 17, 2007

The Invention Explained

• Problem Addressed: The patent addresses the difficulty of deploying robust, graphical software applications over networks, particularly to devices with limited bandwidth like wireless personal digital assistants (WPDAs) (’351 Patent, col. 2:26-41). The patent describes browser-based applications as functionally limited and locally installed applications as large, costly, and difficult to update ’351 Patent, col. 2:42-61
• The Patented Solution: The invention describes an "Application Virtual Machine" (AVM), a small assembler program that is first installed on the client device ’351 Patent, abstract This AVM then downloads one or more text files (e.g., XML files) from a server that contain embedded application logic. The AVM uses these files to "assemble" a fully functioning graphical application in the device's temporary memory, providing a rich user experience without requiring a large, permanent software installation ’351 Patent, col. 3:10-24
• Technical Importance: The technology aimed to combine the ease of deployment of web applications with the rich functionality and "native look and feel" of traditional installed software.

Key Claims at a Glance

• The complaint asserts at least independent claim 14 Compl. ¶28
• Claim 14 is a method claim with the following essential elements:
  • Storing and running a software module on a user's client device.
  • Providing the client device with text files containing embedded program logic for the software module to assemble into a computer program.
  • The assembled computer program provides a graphical user interface (GUI) for receiving and interpreting user inputs.
  • Running the assembled computer program on the client device.
  • Enabling user interaction with the running computer program.
• The complaint does not explicitly reserve the right to assert dependent claims.

U.S. Patent No. 8,607,139 - “System and process for managing content organized in a tag-delimited template using metadata,” Issued December 10, 2013

• Technology Synopsis: The patent addresses inefficiencies in web development where content is hard-coded into a page's structure, making updates difficult (’139 Patent, col. 2:5-9). The solution is a system that uses a "metadata template" to define the structure, data types, and properties of a web page's content. This template is used to automatically generate a data entry form for a user, and the content entered into that form is then used to populate the template and generate the final web page ’139 Patent, abstract
• Asserted Claims: At least method claim 8 Compl. ¶39
• Accused Features: The complaint alleges Defendant’s website infrastructure performs a method of displaying a graphical interface based on a metadata template to generate a data entry form and, subsequently, a web page containing the user-provided content Compl. ¶39

III. The Accused Instrumentality

Product Identification

• The accused instrumentality is Defendant’s "website infrastructure" Compl. ¶17 Compl. ¶28 Compl. ¶39

Functionality and Market Context

• The complaint does not describe the specific components or commercial positioning of Defendant's infrastructure. Instead, it alleges that the infrastructure, in its operation of serving web content to users, performs the methods claimed by the patents-in-suit. The allegations suggest the accused functionality is fundamental to how Defendant's websites are delivered and managed, covering network-level communication, client-side application rendering, and back-end content generation Compl. ¶¶17, 28, 39

IV. Analysis of Infringement Allegations

No probative visual evidence provided in complaint.

’959 Infringement Allegations

’351 Infringement Allegations

Identified Points of Contention

• Architectural Mapping: For the ’959 Patent, a central question will be whether the functions of standard web infrastructure components (e.g., load balancers, content delivery networks, reverse proxies) perform the specific, distinct roles of the claimed "deceiver", "controller", and "forwarder". The analysis may focus on whether the accused system has the claimed three-part architecture or operates in a fundamentally different way.
• Scope of "Assemble": For the ’351 Patent, a likely point of dispute is whether a standard web browser rendering a webpage from HTML, CSS, and JavaScript files performs the claimed step of a "software module" that "assembles" a "computer program". The defense may argue that this claim language, in light of the specification's focus on a specific "Application Virtual Machine" (AVM), requires more than conventional browser operation.

V. Key Claim Terms for Construction

’959 Patent, Claim 1

• The Term: "deceiver"
• Context and Importance: This term is not a standard industry term and appears to be a neologism specific to the patent. Its construction is critical because it defines the component that first interacts with a client request. The dispute will likely center on whether a conventional network component, such as a DNS resolver or a proxy server, can be considered a "deceiver".
• Intrinsic Evidence for Interpretation:
  • Evidence for a Broader Interpretation: The specification states the "deceiver" "provides name resolution for clients" and "communicates with clients and with the controller" ’959 Patent, col. 2:40-42, language which could be argued to cover a range of network devices.
  • Evidence for a Narrower Interpretation: The detailed description and figures depict the "deceiver" (104) as a distinct architectural component that "transparently" receives the client's packet and forwards the query to a separate "controller" (106) to initiate the anonymization process ’959 Patent, col. 3:51-61 ’959 Patent, Fig. 1 This may support an interpretation requiring a specific, dedicated function not performed by a standard DNS server.

’351 Patent, Claim 14

• The Term: "software module to assemble into the computer program"
• Context and Importance: The definition of this phrase will be central to determining infringement. Practitioners may focus on whether this term can read on a standard web browser processing HTML and script files, or if it is limited to the more specialized "Application Virtual Machine" (AVM) described in the patent.
• Intrinsic Evidence for Interpretation:
  • Evidence for a Broader Interpretation: The claim language itself does not mention an "AVM" and uses general terms like "software module" and "text files", which could plausibly be argued to encompass a browser and its downloaded web assets.
  • Evidence for a Narrower Interpretation: The specification consistently and repeatedly describes the invention as an "Application Virtual Machine (AVM) that is deployed by a server over a network to client devices" ’351 Patent, col. 4:29-32 The abstract and summary center on this AVM, which "assembles the retrieved program logic into a functioning, graphical application" ’351 Patent, col. 3:15-18, suggesting the "assembling" is a specific function of the AVM, not a generic browser.

VI. Other Allegations

Indirect Infringement

• The complaint alleges that to the extent any claimed steps are performed by a third party (e.g., an end user), Defendant is liable for indirect infringement. The allegations state that Defendant "conditioned the third party's use of the functionality" and "controlled the manner and/or timing of the functionality" Compl. ¶18 Compl. ¶29 Compl. ¶40

Willful Infringement

• The complaint does not contain an explicit count for willful infringement or allege that Defendant had pre-suit knowledge of the patents. It does, however, request damages as justified under 35 U.S.C. § 284, which is the statutory basis for enhanced damages Compl. ¶44.B

VII. Analyst’s Conclusion: Key Questions for the Case

The resolution of this case may turn on the following key questions:

• A core issue will be one of architectural equivalence: Does the Defendant's standard website infrastructure, which may use conventional components like load balancers and CDNs, map onto the specific three-part "deceiver, controller, forwarder" architecture required by the '959 Patent, or is there a fundamental mismatch in technical operation?
• A second central question will be one of definitional scope: Can claim terms such as "software module to assemble" ('351 Patent) and "metadata template" ('139 Patent) be construed broadly enough to cover the operation of a standard web browser rendering modern websites, or are they limited by the patent specifications to more specialized, proprietary systems like the "AVM" and content management frameworks described therein?