DataCloud Tech LLC v. Moodys Analytics Inc

I. Executive Summary and Procedural Information

• Parties & Counsel:
  • Plaintiff: DataCloud Technologies, LLC (Georgia)
  • Defendant: Moody's Analytics, Inc. (Delaware)
  • Plaintiff’s Counsel: Stamoulis & Weinblatt LLC; Kent & Risley LLC
• Case Identification: 1:26-cv-00154, D. Del., 02/10/2026
• Venue Allegations: Venue is asserted in the District of Delaware on the basis that the defendant is a Delaware corporation.
• Core Dispute: Plaintiff alleges that Defendant’s website infrastructure infringes two patents related to methods for anonymous network communication and for deploying software applications over a distributed network.
• Technical Context: The patents address foundational internet technologies concerning user privacy through network traffic misdirection and efficient, platform-independent software delivery to client devices.
• 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 mentions no other 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 “’959 Patent”)

The Invention Explained

• Problem Addressed: The patent’s background section identifies the problem of user privacy on the internet, where standard protocols like HTTP allow servers to record and trace a client’s identity and browsing activity, leading to privacy threats such as unwanted solicitations and tracking via "cookies" (’959 Patent, col. 1:56-67). Existing proxy servers are described as an inadequate solution, as they merely substitute one traceable identity for another ’959 Patent, col. 2:7-19
• The Patented Solution: The invention proposes a system architecture comprising three main components: a "deceiver," a "controller," and a "forwarder" ’959 Patent, abstract When a client attempts to connect to a website, the deceiver intercepts the request and passes it to the controller. The controller resolves the destination IP address, selects a forwarder, and instructs the deceiver to send the forwarder's IP address back to the client, masquerading as the destination. This establishes a communication session where traffic is routed through the forwarder, thereby concealing the client's identity from the destination server and vice-versa ’959 Patent, col. 2:33-47 ’959 Patent, Fig. 1
• Technical Importance: This architecture was designed to provide a more robust form of user anonymity by creating ad hoc, session-specific communication channels that isolate client activity, and to enable the creation of "virtual namespaces" for secure group communications ’959 Patent, col. 2:48-54

Key Claims at a Glance

• The complaint asserts at least independent claim 1 Compl. ¶17
• The essential elements of claim 1 include:
  • In response to a client request to communicate with a destination website, setting up a forwarding session.
  • The session employs a "forwarder" positioned between the client and destination server to transfer packets in both directions.
  • The session is set up such that "neither the client nor 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 initial request from the client and initiates the controller to query the DNS.
  • The forwarding session is initiated after the controller receives the answer from the DNS.

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 “’351 Patent”)

The Invention Explained

• Problem Addressed: The patent describes challenges in deploying robust software applications to remote users, particularly over low-bandwidth or wireless connections to devices like Personal Digital Assistants (PDAs). The background notes that browser-based applications lack functionality and require constant connectivity, while traditional locally installed applications are large, platform-dependent, and difficult to update (’351 Patent, col. 1:26-51; ’351 Patent, col. 2:25-61).
• The Patented Solution: The invention provides a system where a client device first installs a lightweight "assembler program" or "Application Virtual Machine" (AVM) ’351 Patent, col. 3:11-15 This AVM then downloads one or more text files (e.g., XML files) from a server, which contain embedded application logic. The AVM retrieves this logic and assembles it "on the fly" into a functioning, graphical application within the client device's temporary memory, providing a rich user experience with a native look and feel without a large, permanent installation ’351 Patent, abstract ’351 Patent, col. 4:29-38
• Technical Importance: This approach sought to merge the benefits of thin-client architectures (centralized logic, easy updates) with the performance and rich graphical interface of locally executed software, making it suitable for deploying complex applications in resource-constrained environments ’351 Patent, col. 5:51 - col. 6:35

Key Claims at a Glance

• The complaint asserts at least independent claim 14 Compl. ¶28
• The essential elements of claim 14 include:
  • Storing and running a "software module" on a client device.
  • Providing text files to the client device that contain "embedded program logic" for the software module.
  • The software module uses the logic to "assemble into the computer program".
  • The resulting computer program provides a graphical user interface (GUI) for user input.
  • Running the assembled computer program on the client device.
  • Enabling user interaction with the running program.

III. The Accused Instrumentality

Product Identification

• The accused instrumentality is identified broadly as "Defendant's website infrastructure" Compl. ¶17 Compl. ¶28

Functionality and Market Context

• The complaint alleges that this infrastructure performs the methods claimed in the patents-in-suit. For the ’959 Patent, it is alleged to establish an anonymized forwarding session using a deceiver, controller, and forwarder architecture Compl. ¶17 For the ’351 Patent, it is alleged to deliver text files with embedded logic to a software module on a user's device, which then assembles a functioning application Compl. ¶28 The complaint does not provide specific details on the technical operation or market position of the accused infrastructure beyond these conclusory allegations.
• No probative visual evidence provided in complaint.

IV. Analysis of Infringement Allegations

The complaint references claim chart exhibits that are not provided with the filing. The following summary is based on the narrative infringement allegations.

’959 Patent Infringement Allegations

Identified Points of Contention

• Scope Questions: A primary question will be whether components of a modern web architecture (e.g., load balancers, reverse proxies, content delivery networks) can be mapped onto the specific "deceiver", "controller", and "forwarder" elements recited in the claim. The defense may argue that these standard components do not meet the structural and functional requirements of the claimed invention.
• Technical Questions: The complaint alleges that "neither the client nor the destination server is aware of the employment of the forwarder." A key factual dispute will likely be what evidence supports this specific lack of awareness within the defendant's system, as this is a critical distinguishing feature of the claimed method.

’351 Patent Infringement Allegations

Identified Points of Contention

• Scope Questions: The infringement theory appears to read on the standard operation of modern websites, which deliver HTML, CSS, and JavaScript files to a web browser. A central issue will be whether a standard web browser qualifies as the claimed "software module" and whether its rendering process constitutes "assembl[ing]" a "computer program" as contemplated by the patent, which heavily describes a specific "Application Virtual Machine."
• Technical Questions: The complaint does not specify what constitutes the "software module" that is allegedly "storing and running" on the client device prior to receiving the text files. The case may turn on whether this module must be a distinct, pre-installed component (like the patent's "starter plugin") or if a general-purpose web browser suffices.

V. Key Claim Terms for Construction

• Term (’959 Patent): "deceiver"

  • Context and Importance: This is a term of art specific to the patent, not a standard networking term. Its construction is critical because the infringement case depends on finding a corresponding component in the accused infrastructure. Whether this term is construed broadly to cover any initial request handler or narrowly to require a dedicated misdirection component will be a central issue.
  • Intrinsic Evidence for a Broader Interpretation: The specification states, "The deceiver provides name resolution for clients. 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 it is a functional role rather than a specific device.
  • Intrinsic Evidence for a Narrower Interpretation: The detailed description and figures depict the "deceiver" as a discrete architectural component (104) that transparently intercepts a packet from the client and forwards the query to the "controller" ’959 Patent, Fig. 1 ’959 Patent, col. 3:51-61 This suggests a specific, purpose-built element distinct from a standard DNS server.

• Term (’351 Patent): "software module to assemble into the computer program"

  • Context and Importance: The definition of this phrase will likely determine whether the claim reads on conventional web browsing or is limited to the more specialized system described in the patent. The dispute will focus on whether a web browser is the "software module" and its rendering of a webpage is "assembl[ing]" a program.
  • Intrinsic Evidence for a Broader Interpretation: The claim language itself is general and does not explicitly require the "Application Virtual Machine" or "AVM" detailed in the specification. An argument could be made that the claim terms should be given their plain and ordinary meaning, where a browser (a software module) assembles various text and script files into an interactive application.
  • Intrinsic Evidence for a Narrower Interpretation: The specification repeatedly and consistently describes the invention in terms of a specific "Application Virtual Machine (AVM)" or "assembler program" that is installed on the client device to perform the assembly ’351 Patent, abstract ’351 Patent, col. 3:11-24 This consistent emphasis may support a narrower construction limiting the "software module" to such a dedicated assembler, distinguishing it from a general-purpose browser.

VI. Other Allegations

• Indirect Infringement: The complaint contains generalized allegations suggesting infringement may be divided between Defendant and a third party (e.g., an end user). It alleges that Defendant "conditioned the third party's use" on performing the claimed steps and "controlled the manner and/or timing of the functionality" Compl. ¶18 Compl. ¶29 These allegations lack specific factual support, such as references to user instructions or manuals.
• Willful Infringement: The complaint does not explicitly allege willful infringement or plead facts suggesting Defendant had pre-suit knowledge of the patents.

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

This dispute appears to hinge on fundamental questions of claim scope and the application of patent claims to widespread, standard internet technologies. The key questions for the court will likely be:

1. Architectural Equivalence: For the ’959 Patent, a core issue will be whether the plaintiff can prove that the defendant's web infrastructure contains the specific three-part "deceiver", "controller", and "forwarder" architecture required by the claims. The case may turn on whether equating these terms with standard networking components like reverse proxies or load balancers is a permissible interpretation of the claim scope.

2. The "Assembler" Distinction: For the ’351 Patent, the central question is one of definitional scope: can the claim language "software module to assemble...a computer program", when read in light of the specification's extensive focus on a proprietary "Application Virtual Machine," be construed to cover the routine functioning of a standard web browser rendering a dynamic webpage from HTML and JavaScript files?

3. Evidentiary Support: Given that the complaint's infringement allegations closely track the language of the claims without providing detailed factual support or accessible exhibits, a primary challenge for the plaintiff will be to produce evidence in discovery that demonstrates the accused "website infrastructure" actually performs the specific and nuanced functions required by the claims.