DataCloud Tech LLC v. Lattice Semiconductor Corp

I. Executive Summary and Procedural Information

• Parties & Counsel:
  • Plaintiff: DataCloud Technologies, LLC (Georgia)
  • Defendant: Lattice Semiconductor Corporation (Delaware)
  • Plaintiff's Counsel: Rozier Hardt McDonough PLLC
• Case Identification: 7:26-cv-00083, W.D. Tex., 03/10/2026
• Venue Allegations: Plaintiff alleges venue is proper in the Western District of Texas based on Defendant maintaining an "Operations Center" in Austin, Texas, and conducting substantial business within the district.
• Core Dispute: Plaintiff alleges that Defendant's website infrastructure and video content delivery system infringe two patents related to anonymous network communication and the deployment of software applications over a distributed network.
• Technical Context: The technologies at issue concern methods for managing network communications to protect user privacy and for dynamically assembling software applications on a client device, both of which are foundational concepts in modern web services and content delivery.
• Key Procedural History: The complaint notes that a Certificate of Correction was issued for U.S. Patent No. 7,246,351 on November 20, 2007, but provides no other significant procedural history for 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's background section describes the privacy problem inherent in standard internet protocols, where a user's activity and identifying information (like an IP address) can be logged and tracked by web servers, leading to privacy threats such as unwanted solicitations and user profiling '959 Patent, col. 1:57-col. 2:8
• The Patented Solution: The invention proposes a system architecture to anonymize a client's network session using three distinct components: a "deceiver," a "controller," and a "forwarder" '959 Patent, abstract When a client requests to visit a website, the request is intercepted by the deceiver, which passes it to the controller. The controller resolves the website's true IP address and selects a separate forwarder. The system then "deceives" the client by providing the forwarder's IP address as if it were the destination's. The forwarder then acts as an intermediary, relaying traffic between the client and the destination website, thereby masking the true identities of both endpoints from each other '959 Patent, col. 3:12-col. 4:51 '959 Patent, Fig. 1
• Technical Importance: This architecture provides a structured method for creating temporary, anonymous communication channels over a public network, addressing fundamental user privacy concerns prevalent in web browsing '959 Patent, col. 2:24-29

Key Claims at a Glance

• The complaint asserts independent claim 1 Compl. ¶23
• Essential elements of claim 1 include:
  • In response to a client request to communicate with a destination website, setting up a forwarding session using a forwarder.
  • The forwarding session is implemented such that "neither the client or the destination server is aware of the employment of the forwarder."
  • A controller communicates with the forwarder and a domain name server (DNS) to resolve the destination's name.
  • A deceiver receives the initial client request and initiates the controller to query the DNS.
  • The forwarding session is initiated after the controller receives the answer from the DNS.
• The complaint alleges infringement of "one or more claims," which may suggest an intent to assert dependent claims later Compl. ¶22

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 the difficulties in deploying functional software applications over networks, particularly to resource-limited devices like early wireless personal digital assistants (WPDAs) '351 Patent, col. 1:24-col. 2:3 The background notes that browser-based applications were often limited and required constant connectivity, while fully-installed local applications were large, difficult to deploy, and cumbersome to update '351 Patent, col. 2:25-61
• The Patented Solution: The patent describes a system centered on an "Application Virtual Machine" (AVM), which is a small assembler program installed on the client device '351 Patent, abstract This AVM downloads one or more text files (e.g., XML files) from a server that contain "embedded application logic." The AVM then retrieves this logic and assembles it "on the fly" into a functioning, graphical application in the device's temporary memory, without requiring a permanent, large-scale installation '351 Patent, col. 3:11-24 This allows for rich client-side functionality with the ease of updating of a server-side application.
• Technical Importance: This "thin-client" approach allows for the deployment of applications that have the feel and performance of native software but are maintained and updated centrally on a server, a model that presages many modern web application frameworks '351 Patent, col. 3:1-6

Key Claims at a Glance

• The complaint asserts independent claim 14 Compl. ¶34
• Essential elements of claim 14 (a method claim) include:
  • 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 a computer program.
  • The assembled computer program provides a graphical user interface (GUI) for user interaction.
  • Running the assembled computer program on the client device.
  • Enabling user interaction with the running program.
• The complaint alleges infringement of "one or more claims," suggesting other claims might be asserted Compl. ¶33

III. The Accused Instrumentality

• Product Identification: The complaint identifies two accused instrumentalities:
  1. For the '959 Patent, the accused instrumentality is Defendant's "website infrastructure" at www.latticesemi.com Compl. ¶24
  2. For the '351 Patent, the accused instrumentality is the system that allows users to view video content on mobile devices, which involves a "software module such as the Lattice website" running on the device to fetch, assemble, and run a video player Compl. ¶35
• Functionality and Market Context:
  • The complaint alleges that Lattice's website infrastructure operates as an intermediary when responding to user requests, managing connections in a way that purportedly obscures the final destination server from the end-user's client Compl. ¶24
  • Regarding video playback, the complaint alleges that when a user accesses video content on a mobile device, the Lattice website functions as a software module on that device. This module is alleged to connect to a Lattice server to fetch "program logic and interface components as text-based files," which contain embedded code. This code is then allegedly used to assemble a functional video player with a graphical user interface (including play and pause buttons) directly on the user's device Compl. ¶35

IV. Analysis of Infringement Allegations

'959 Patent Infringement Allegations

'351 Patent Infringement Allegations

Identified Points of Contention

• '959 Patent:
  • Scope Questions: A primary question will be whether a standard, modern web architecture-which may use reverse proxies, load balancers, or content delivery networks (CDNs) that abstract the underlying server infrastructure-can be considered to be the specific three-part "deceiver, controller, forwarder" system claimed in the patent. The patent's focus on providing anonymity may be a key distinction from architectures designed for performance and scalability.
  • Technical Questions: The complaint's allegations map the functionality of Lattice's website to the claimed components in a conclusory manner. A potential point of contention will be what evidence demonstrates that distinct "deceiver" and "controller" functions, as described in the patent, are actually performed by the accused infrastructure.
• '351 Patent:
  • Scope Questions: A central issue may be whether a standard web browser executing JavaScript to render an interactive webpage qualifies as the claimed "software module" that "assembles" a "computer program." The defense may argue that the patent requires a specific, pre-installed "Application Virtual Machine" (AVM) or plugin, not a general-purpose browser.
  • Technical Questions: The dispute may turn on the definition of "assemble." The complaint alleges the video player is assembled from "text-based files." This raises the question of whether this refers to the standard process of a browser parsing HTML, CSS, and JavaScript, or if it implies a more specific process of constructing an executable from logic-bearing text files as described in the patent's specification.

No probative visual evidence provided in complaint.

V. Key Claim Terms for Construction

'959 Patent

• The Term: "deceiver"
• Context and Importance: This is a non-standard term of art created for the patent. Its construction is critical because if it is defined narrowly as a purpose-built component for DNS misdirection to achieve anonymity, it may not read on a standard web server front-end or load balancer. A broader construction covering any initial point of contact that redirects a request could favor the plaintiff's infringement theory. Practitioners may focus on this term because the infringement allegation appears to equate it with a standard component of web infrastructure.
• Intrinsic Evidence for Interpretation:
  • Evidence for a Broader Interpretation: The specification describes its function in general terms: "The deceiver provides name resolution for clients...when a query is received from a client, the deceiver allows the controller to supply the information" '959 Patent, col. 2:36-40
  • Evidence for a Narrower Interpretation: The patent's title, abstract, and summary all frame the invention as a system for "providing anonymity" '959 Patent, title '959 Patent, abstract '959 Patent, col. 2:24-29 The figures depict the "deceiver" as a discrete architectural block, separate from the controller and forwarder, suggesting it is a specific component in the anonymization scheme rather than a generic network front-end '959 Patent, Fig. 1

'351 Patent

• The Term: "software module to assemble into the computer program"
• Context and Importance: This phrase is at the heart of the infringement allegation. The viability of the plaintiff's case may depend on whether this term can be construed to cover a standard web browser rendering an application from scripts. If the term is limited to the specific "Application Virtual Machine" (AVM) described in the patent, infringement may be more difficult to establish.
• Intrinsic Evidence for Interpretation:
  • Evidence for a Broader Interpretation: The claim language itself is general. An argument could be made that a web browser is a "software module" that "assembles" a functioning webpage (the "computer program") from "text files" containing program logic (HTML and JavaScript).
  • Evidence for a Narrower Interpretation: The specification consistently and repeatedly describes the invention as an "Application Virtual Machine (AVM)" or "assembler program" that is downloaded and installed on the client device as a distinct piece of software, which then downloads and assembles the application files '351 Patent, abstract '351 Patent, col. 3:11-24 This suggests the "software module" is the AVM itself, not a pre-existing, general-purpose browser.

VI. Other Allegations

• Indirect Infringement: The complaint makes a general allegation of inducement and contributory infringement Compl. ¶12 For the '351 Patent, the facts alleged-that Defendant "allowed" and "enabled" users to view video content on their devices-may be intended to support a claim of induced infringement, where end-users are the direct infringers by performing the claimed method steps Compl. ¶35
• Willful Infringement: The complaint does not use the term "willful." However, the prayer for relief requests a declaration that the case is "exceptional" and an award of attorneys' fees under 35 U.S.C. § 285 Compl. ¶39.D The complaint does not plead specific facts alleging pre- or post-suit knowledge of the patents that would typically support a claim for willful infringement.

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

The resolution of this dispute may depend on the court's interpretation of claim scope in the context of evolving web technologies. The central questions appear to be:

• A core issue will be one of architectural equivalence: can the '959 Patent's specific three-part "deceiver, controller, forwarder" architecture, created for the stated purpose of user anonymity, be construed to cover components of a modern commercial website's infrastructure that are likely designed for load balancing and content delivery?
• A key question of technological scope will be whether the act of a standard web browser rendering an interactive video player from server-sent scripts falls within the '351 Patent's claims, which describe a distinct "assembler program" or "Application Virtual Machine" that builds a functioning application on the client device.
• An evidentiary question will be one of functional distinction: what proof can be offered to show that the accused systems perform the specific, discrete functions required by the claims (e.g., the DNS-querying function of the "controller" in the '959 Patent, or the application "assembly" step of the '351 Patent), as opposed to generally analogous but technically different operations common to all modern web services?