DataCloud Tech LLC v. Rockchip Electronics Co Ltd

I. Executive Summary and Procedural Information

• Parties & Counsel:
  • Plaintiff: DataCloud Technologies, LLC (Georgia)
  • Defendant: Rockchip Electronics Co., Ltd. (People's Republic of China)
  • Plaintiff's Counsel: Rozier Hardt McDonough PLLC
• Case Identification: 2:26-cv-00189, E.D. Tex., 03/10/2026
• Venue Allegations: Plaintiff alleges venue is proper in the Eastern District of Texas because Defendant conducts substantial business, commits acts of infringement, and has significant ties to the state and district.
• Core Dispute: Plaintiff alleges that Defendant's website infrastructure and video player technology infringe two patents related to anonymous network communication and the dynamic assembly of software applications on a client device.
• Technical Context: The patents address foundational technologies for network privacy and efficient, cross-platform software deployment, which are central to modern web architecture and application delivery.
• Key Procedural History: The complaint does not mention any prior litigation, inter partes review proceedings, or licensing history related to 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"

The Invention Explained

• Problem Addressed: The patent describes the problem of user privacy on the internet, where a client's information (e.g., e-mail, web history, host computer details) can be recorded and traced by servers, and existing proxy solutions merely substitute one traceable identity for another ʼ959 Patent, col. 1:56 - col. 2:28
• The Patented Solution: The invention proposes a three-component architecture-a "deceiver," a "controller," and a "forwarder"-to create an anonymous communication session ʼ959 Patent, abstract When a client requests a website, the request is intercepted by the deceiver, which consults the controller. The controller resolves the true destination IP address, selects an intermediary forwarder, and instructs the deceiver to return the forwarder's IP address to the client. The client then communicates with the forwarder, believing it is the destination server. The forwarder relays traffic, making it appear as the source to the destination server. This process is designed to make both the client and the destination server unaware of the intermediary, thereby anonymizing the connection ʼ959 Patent, col. 3:46 - col. 4:49 ʼ959 Patent, Fig. 1
• Technical Importance: This architecture provides a method for session-based anonymity that aims to be more robust than simple IP address substitution by creating a transient, virtual communication path.

Key Claims at a Glance

• The complaint asserts at least independent claim 1 Compl. ¶20
• Claim 1 of the '959 Patent includes these essential elements:
  • Setting up a forwarding session between a client and a destination server in response to a client request.
  • The session employs a "forwarder" disposed between the client and destination server to relay packets in both directions.
  • The session is implemented such that "neither the client or the destination server is aware of the employment of the forwarder."
  • The system employs a "controller" that communicates with the forwarder and a domain name server (DNS) to resolve the destination's name.
  • The system employs a "deceiver" that receives the client's initial request and communicates with the controller.
  • The forwarding session is initiated after the controller receives the resolved name 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"

The Invention Explained

• Problem Addressed: The patent addresses challenges in deploying software applications over networks, particularly to devices with limited resources like wireless personal digital assistants (WPDAs) ʼ351 Patent, col. 1:23 - col. 2:6 Browser-based applications are described as functionally limited, while locally installed applications are noted as being large, platform-dependent, and difficult to update ʼ351 Patent, col. 2:25-61
• The Patented Solution: The patent describes an "Application Virtual Machine" (AVM), which is a software module or assembler program that runs on the client device ʼ351 Patent, abstract This AVM downloads one or more text files (e.g., XML files) that contain embedded program logic from a server. The AVM then retrieves this logic and "assembles" it into a functioning, graphical application within the client's memory, providing a "native look and feel" without requiring a full, pre-compiled application download ʼ351 Patent, col. 3:10-24 This approach is designed to allow for small initial downloads and easy updates, as only the server-side text files need to be modified ʼ351 Patent, col. 5:15 - col. 7:4
• Technical Importance: This method describes a "thin-client" architecture for delivering rich application functionality, a precursor to modern web frameworks that dynamically build user interfaces from declarative markup and scripts.

Key Claims at a Glance

• The complaint asserts at least independent claim 14 Compl. ¶31
• Claim 14 of the '351 Patent includes these essential elements:
  • Storing and running a "software module" on a client device.
  • Providing the client device with "text files containing embedded program logic" for the software module to "assemble into the computer program."
  • The resulting computer program provides a graphical user interface (GUI) for user input.
  • Running the computer program that was assembled from the embedded program logic on the client device.
  • Enabling user interaction with the running computer program.
• The complaint does not explicitly reserve the right to assert dependent claims.

III. The Accused Instrumentality

Product Identification

• The accused instrumentalities are Rockchip's "website infrastructure (www.rock-chips.com)" for the '959 Patent and the functionality that allows users "to view video content on their mobile devices" for the '351 Patent Compl. ¶21 Compl. ¶32

Functionality and Market Context

• For the '959 Patent, the complaint alleges that Rockchip's website infrastructure, when responding to user requests, operates in a way where "neither the client nor the destination server was aware of the employment of the forwarder" Compl. ¶21 The allegations describe a system where subdomains may share a public IP address, requiring a DNS query to find a corresponding private IP address Compl. ¶21
• For the '351 Patent, the complaint alleges that a "software module such as the Rockchip website" runs on a user's device, connecting to a Rockchip server to fetch "logic and interface components as text-based files" Compl. ¶32 These files allegedly contain "embedded code for assembling functional parts of the website such as the video player directly on the device," which then provides a GUI with interactive controls like play and pause buttons Compl. ¶32
• The complaint does not provide specific details on the market positioning of the accused functionalities beyond their general operation on Rockchip's public website.

IV. Analysis of Infringement Allegations

No probative visual evidence provided in complaint. The complaint references Exhibits A and B, but they were not included with the filing. The following analysis is based on the narrative infringement allegations in the complaint body.

'959 Patent Infringement Allegations

'351 Patent Infringement Allegations

Identified Points of Contention

• Scope Questions ('959 Patent): A central question will be whether Rockchip's "website infrastructure," which may involve modern technologies like reverse proxies, load balancers, or content delivery networks, can be mapped onto the patent's specific architecture of a "deceiver," "controller," and "forwarder." The complaint's assertion that this architecture exists is conclusory and does not explain how these distinct components are implemented in Rockchip's system Compl. ¶¶20-21
• Technical Questions ('959 Patent): The infringement theory hinges on the allegation that "neither the client nor the destination server was aware of the employment of the forwarder" Compl. ¶21 The defense may argue that in standard web communications, a client is aware it is connecting to a public-facing IP address (e.g., a load balancer) which is distinct from the internal server, a technically different scenario from the patent's description of being "deceived" into thinking an intermediary is the final destination ʼ959 Patent, col. 4:43-46
• Scope Questions ('351 Patent): The analysis will likely focus on whether a standard web browser qualifies as the claimed "software module" and whether the rendering of a modern, dynamic webpage from HTML, CSS, and JavaScript files constitutes "assembling" a "computer program" as contemplated by the patent. The patent appears to describe a dedicated, pre-installed client (the AVM) that assembles applications, which may be distinct from a general-purpose browser rendering standard web content ʼ351 Patent, col. 3:12-19
• Technical Questions ('351 Patent): The complaint alleges the "Rockchip website, ran on the mobile device" Compl. ¶32 This phrasing conflates the website (content) with the client-side software (browser) that renders it. A key question will be what specific "software module" Plaintiff can prove is "storing and running" on the client device that performs the claimed assembly function, separate from the ordinary operation of a web browser.

V. Key Claim Terms for Construction

• Patent: '959 Patent

  • The Term: "deceiver"
  • Context and Importance: This term is critical because it is a specifically named component of the claimed three-part architecture. The infringement case depends on mapping Rockchip's website infrastructure onto this structure. Practitioners may focus on this term because the complaint does not identify a specific, corresponding component in the accused system, instead alleging its function in a conclusory manner Compl. ¶20
  • Intrinsic Evidence for Interpretation:
    • Evidence for a Broader Interpretation: The specification states the deceiver "provides name resolution for clients" and that the "routine works the same as a standard name server, except when a query is received from a client, the deceiver allows the controller to supply the information" ʼ959 Patent, col. 2:38-42 This could support an argument that any component that intercepts a client's DNS-like request and passes it to another component for handling meets the definition.
    • Evidence for a Narrower Interpretation: The detailed description shows the deceiver as a distinct architectural block that transparently receives packets from the client and queries the controller to initiate name resolution ʼ959 Patent, col. 4:51-61 ʼ959 Patent, Fig. 1 This suggests a specific, purpose-built intermediary, not just any part of a standard web server stack that handles incoming requests.

• Patent: '351 Patent

  • The Term: "assemble into the computer program"
  • Context and Importance: The definition of this term is central to distinguishing the claimed invention from the conventional operation of a web browser. The Plaintiff's theory requires that a browser's act of rendering a webpage from source files be considered "assembling" a "program."
  • Intrinsic Evidence for Interpretation:
    • Evidence for a Broader Interpretation: The patent abstract describes the process as an "application assembler" that "assembles the retrieved program logic into a functioning application." Claim 14 recites assembling a "computer program" that provides a GUI ʼ351 Patent, abstract ʼ351 Patent, col. 24:14-23 Plaintiff may argue that dynamically creating an interactive video player with buttons from script and markup files fits this functional description.
    • Evidence for a Narrower Interpretation: The specification repeatedly refers to the "Application Virtual Machine (AVM)" as the component that performs the assembly ʼ351 Patent, col. 4:29-34 It contrasts its invention with browser-based solutions ʼ351 Patent, col. 2:30-41 This could support a narrower construction requiring a dedicated, non-browser client module that builds an application in a manner distinct from a browser rendering HTML.

VI. Other Allegations

• Indirect Infringement: The complaint alleges inducement of infringement, but provides no specific facts to support the required elements of knowledge and intent Compl. ¶9
• Willful Infringement: The complaint does not contain any allegations of willful infringement or pre-suit knowledge of the patents.

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

This case appears to be an attempt to apply patents from the early 2000s to ubiquitous, modern web technologies. The outcome will likely depend on the court's interpretation of claim terms in light of significant technological evolution in the field.

1. A core issue will be one of architectural mapping: Can the functions of a modern, distributed website architecture (e.g., using reverse proxies or CDNs) be persuasively mapped onto the '959 patent's specific and distinct "deceiver, controller, and forwarder" components, or is there a fundamental mismatch between the accused system and the claimed invention?
2. A second core issue will be one of definitional scope: Can the ordinary function of a web browser-downloading text-based HTML, CSS, and JavaScript files and rendering them into an interactive webpage-be construed as a "software module" that "assembles" a "computer program" as required by the '351 patent, or does the patent claim a more specialized thin-client system distinct from conventional web browsing?