DCT
2:26-cv-00186
DataCloud Tech LLC v. Honeywell Intl Inc
Key Events
Complaint
Table of Contents
complaint Intelligence
I. Executive Summary and Procedural Information
- Parties & Counsel:
- Plaintiff: DataCloud Technologies, LLC (Georgia)
- Defendant: Honeywell International Inc. (Delaware)
- Plaintiff's Counsel: Rozier Hardt McDonough PLLC
- Case Identification: 2:26-cv-00186, E.D. Tex., 03/06/2026
- Venue Allegations: Plaintiff alleges venue is proper in the Eastern District of Texas because Defendant maintains a facility in Plano, Texas, and conducts substantial business in the district, including committing the alleged acts of infringement.
- Core Dispute: Plaintiff alleges that Defendant's website infrastructure, mobile video player functionality, and Honeywell Safety Suite software infringe three patents related to anonymous network communication, on-demand software application deployment, and remote data management.
- Technical Context: The patents-in-suit address distinct but related aspects of network services: providing user anonymity, efficiently deploying rich applications over networks with limited bandwidth, and enabling permission-based remote management of file directory structures.
- Key Procedural History: The complaint does not mention any prior litigation, Inter Partes Review (IPR) proceedings, or licensing history related to the asserted patents.
Case Timeline
| Date | Event |
|---|---|
| 2000-04-04 | U.S. Patent No. 7,209,959 Priority Date |
| 2001-02-20 | U.S. Patent No. 7,246,351 Priority Date |
| 2002-03-29 | U.S. Patent No. 7,398,298 Priority Date |
| 2007-04-24 | U.S. Patent No. 7,209,959 Issued |
| 2007-07-17 | U.S. Patent No. 7,246,351 Issued |
| 2007-11-20 | U.S. Patent No. 7,246,351 Certificate of Correction Issued |
| 2008-07-08 | U.S. Patent No. 7,398,298 Issued |
| 2026-03-06 | Complaint Filed |
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 describes the privacy risks for users on the World Wide Web, where information such as a client's email address, visited websites, and computer details can be recorded and tracked by servers '959 Patent, col. 1:56-65 Existing solutions like proxy servers are described as merely substituting one trackable identity for another, failing to provide true anonymity '959 Patent, col. 2:7-19
- The Patented Solution: The invention proposes a system architecture comprising three distinct functional components-a "deceiver," a "controller," and a "forwarder"-that work together to anonymize a client's network session '959 Patent, abstract When a client requests a website, the deceiver intercepts the request and communicates with the controller; the controller resolves the destination website's true IP address but provides the client with the IP address of a forwarder. The client then communicates with the destination website through the forwarder, which masks the client's IP address from the destination server and masks the destination server's IP address from the client '959 Patent, col. 3:45-col. 4:49 '959 Patent, Fig. 1
- Technical Importance: This system was designed to create ad-hoc, session-specific anonymity for network clients and enable the creation of "virtual namespaces" for specific user communities '959 Patent, col. 2:47-59
Key Claims at a Glance
- The complaint asserts at least independent claim 1 ("Compl. ¶23").
- Essential elements of claim 1 include:
- In response to a client request, setting up a forwarding session using a "forwarder" disposed between the client and a destination server.
- Implementing the session such that neither the client nor the destination server is aware of the forwarder's employment.
- Employing a "controller" that communicates with the forwarder and a domain name server (DNS) to resolve the destination website's name.
- Employing a "deceiver" that receives the initial client request and initiates the controller's query to the DNS.
- Initiating the forwarding session after the controller receives the answer 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 identifies the challenge of deploying robust software applications to remote users across networks, particularly those with slow connections or on devices with limited resources like wireless personal digital assistants (WPDAs) '351 Patent, col. 1:26-34 '351 Patent, col. 2:63-65 Traditional installed applications are large and difficult to update, while browser-based solutions offer limited functionality and require constant connectivity '351 Patent, col. 2:26-40
- The Patented Solution: The patent describes an "Application Virtual Machine" (AVM), which is a small, client-side assembler program '351 Patent, abstract The AVM downloads one or more text files (e.g., XML files) from a server that contain embedded application logic. It then "assembles the retrieved program logic into a functioning, graphical application in temporary memory" on the client device, creating an application with a native look and feel without a traditional installation process '351 Patent, col. 3:10-24
- Technical Importance: This architecture enables the rapid deployment of feature-rich, thin-client applications that can be updated simply by modifying the text files on the server, significantly reducing deployment and support costs '351 Patent, col. 7:6-14
Key Claims at a Glance
- The complaint asserts at least independent claim 14 ("Compl. ¶34").
- 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.
- The software module assembles the program logic from the text files into a computer program.
- The assembled computer program provides a graphical user interface for receiving and interpreting user inputs.
- Running the assembled computer program on the client device.
- Enabling user interaction with the running program.
- The complaint does not explicitly reserve the right to assert dependent claims.
U.S. Patent No. 7,398,298 - "Remote Access And Retrieval Of Electronic Files"
- Issued: July 8, 2008
Technology Synopsis
- The patent addresses the need for users to not only access remote data but also to manage its underlying directory structure and receive confirmation that data has been delivered to intended recipients '298 Patent, col. 2:15-24 The patented solution is a server-side computing application that manages user authentication and provides remote control over data directory structures stored in a "profile data store," allowing users to select and modify specific directory structures and receive notifications upon data delivery '298 Patent, abstract '298 Patent, col. 1:50-col. 2:2
Asserted Claims
- The complaint asserts at least independent claim 13 ("Compl. ¶45").
Accused Features
- The complaint accuses the "Honeywell Safety Suite," an enterprise solution that allegedly provides "fine-grained role-based access control," allowing administrators to manage employee accounts, assign access levels, and control which users can see specific data and reports ("Compl. ¶46").
III. The Accused Instrumentality
Product Identification
- The complaint accuses three distinct instrumentalities:
- Honeywell's primary website infrastructure ("www.honeywell.com") ("Compl. ¶24").
- A system on Honeywell's website that enables users to view video content on mobile devices ("Compl. ¶35").
- The "Honeywell Safety Suite," described as an "end-to-end enterprise solution for pre-production validation" ("Compl. ¶46").
Functionality and Market Context
- Website Infrastructure: The complaint alleges that Honeywell's website infrastructure operates in a way that creates the appearance of a direct TCP connection between a user and a server, while allegedly masking an intermediary forwarding architecture ("Compl. ¶24"). It is also alleged to use a controller to query a domain name server to resolve internal IP addresses for various subdomains that share a public IP address ("Compl. ¶24").
- Mobile Video Player: This system is described as a software module (the Honeywell website) that runs on a user's mobile device and connects to a Honeywell server to "fetch program logic and interface components as text-based files" ("Compl. ¶35"). These files allegedly contain embedded code that assembles a video player on the device, providing a graphical user interface (GUI) with controls for video playback ("Compl. ¶35"). The complaint references Exhibit B, which it states provides evidence of a graphical user interface for a video player with user interaction controls ("Compl. ¶34"; "Compl. ¶35").
- Honeywell Safety Suite: This is alleged to be an enterprise software solution that stores data on servers and provides user management features for controlling organizational access levels ("Compl. ¶46"). Its functionality is said to include "fine-grained role-based access control," allowing designated administrators to manage accounts, assign permissions, and restrict access to content and features ("Compl. ¶46"). The complaint references Exhibit C as providing evidence that this product performs the steps of the asserted claim ("Compl. ¶45"; "Compl. ¶46").
IV. Analysis of Infringement Allegations
7,209,959 Infringement Allegations
| Claim Element (from Independent Claim 1) | Alleged Infringing Functionality | Complaint Citation | Patent Citation |
|---|---|---|---|
| setting up a forwarding session...employing a forwarder disposed between the client and the destination server...such that neither the client or the destination server is aware of the employment... | Honeywell's website infrastructure allegedly creates what appears to be a direct TCP connection, which masks the underlying architecture, so "neither the client nor the destination server was aware of the employment of the forwarder." | ¶24 | col. 8:52-62 |
| employing a controller configured to communicate with the forwarder and a domain name server, wherein the controller queries the domain name server to resolve the name of the destination website... | "Domains names hosted by Honeywell were queried by the controller to resolve the name of the destination website..." The complaint alleges this is necessary when subdomains share the same public IP address. | ¶24 | col. 8:62-col. 9:1 |
| employing a deceiver configured to communicate with the controller and the client, wherein the deceiver receives the request by the client... | "The deceiver both (i) received the request and (ii) later sent the data from the destination server in a manner that makes the deceiver appear to be the source of the data when the source of the data is actually the destination server." | ¶24 | col. 9:4-9 |
| in response to the controller receiving the answer from the domain name server and initiating communication with the forwarder, initiating the forwarding session. | The complaint alleges that after the controller queries the DNS and initiates communication with the forwarder, the forwarding session is initiated. The complaint references Exhibit A as providing evidence of this method. | ¶23 | col. 9:10-13 |
- Identified Points of Contention:
- Architectural Questions: A primary question will be whether Honeywell's standard website architecture-which may include common components like reverse proxies, load balancers, or content delivery networks (CDNs)-can be characterized as the specific three-part "deceiver-controller-forwarder" system required by the claim. The analysis may focus on whether these standard components perform the distinct functions recited for each claimed element.
- Scope Questions: The dispute may turn on the scope of the terms "deceiver," "controller," and "forwarder." The question is whether these terms can read on multifunction network devices or if they require distinct software applications or hardware as depicted in the patent's figures '959 Patent, Fig. 1
7,246,351 Infringement Allegations
| Claim Element (from Independent Claim 14) | Alleged Infringing Functionality | Complaint Citation | Patent Citation |
|---|---|---|---|
| storing and running a software module on a client device of a user | A "software module such as the Honeywell website, ran on the mobile device." | ¶35 | col. 24:14-16 |
| providing to the client device text files containing embedded program logic for the software module to assemble into the computer program | The website module "connected to the Honeywell server to fetch program logic and interface components as text-based files." These files allegedly "included embedded code for assembling functional parts of the website such as the video player directly on the device." | ¶35 | col. 24:17-20 |
| wherein the computer program provides a graphical user interface for receiving and interpreting user inputs... | "Once assembled, the video player provided a graphical user interface (GUI) that allowed the user to interact with the video content. This interface included user input controls...such as play, pause, and other playback options..." | ¶35 | col. 24:20-23 |
| enabling user interaction with the computer program running on the client device | User inputs via the GUI controls (e.g., play, pause) were allegedly "interpreted and handled locally on the device." | ¶35 | col. 24:26-28 |
- Identified Points of Contention:
- Technical Questions: A key technical question will be whether the standard operation of a modern web browser-fetching HTML, CSS, and JavaScript files and rendering them to create a dynamic user interface-constitutes the claimed process. What evidence does the complaint provide that an "assembly" process, distinct from standard browser rendering, occurs on the client device?
- Scope Questions: The analysis will likely focus on the term "assemble into the computer program." Does this term, in the context of the patent's disclosure of an "Application Virtual Machine" '351 Patent, col. 4:28-34, require a specific client-side environment that compiles or constructs an application, or can it be construed broadly to cover a web browser's Document Object Model (DOM) construction and script execution?
V. Key Claim Terms for Construction
U.S. Patent No. 7,209,959
- The Term: "deceiver," "controller," "forwarder"
- Context and Importance: These three terms define the fundamental architecture of the claimed invention. The infringement case depends entirely on whether Honeywell's network infrastructure can be mapped onto this three-part structure. Practitioners may focus on these terms because they are not standard industry terms and appear to be defined by their function within the patent.
- Intrinsic Evidence for Interpretation:
- Evidence for a Broader Interpretation: The specification describes these components as "algorithms" and "applications" that can reside on a single computer or on separate computers '959 Patent, col. 2:36-39 '959 Patent, col. 5:35-42, which may support a functional interpretation where a single, complex network appliance could perform one or more of these roles.
- Evidence for a Narrower Interpretation: Figure 1 of the patent depicts the deceiver (104), controller (106), and forwarder (107) as distinct, separate entities with specific communication paths between them and other network components '959 Patent, Fig. 1 The detailed description consistently discusses them as separate components performing discrete steps in a sequence '959 Patent, col. 3:45-col. 4:49, which may support a narrower construction requiring a specific, segregated architecture.
U.S. Patent No. 7,246,351
- The Term: "software module to assemble into the computer program"
- Context and Importance: This phrase is central to the infringement theory against Honeywell's mobile video player. The case may turn on whether the routine rendering of a web page by a browser constitutes "assembling" a "computer program." Practitioners may focus on this term because modern web applications achieve a similar result (a functional UI) through different technical means than what appears to be disclosed in the patent.
- Intrinsic Evidence for Interpretation:
- Evidence for a Broader Interpretation: The abstract states the system "assembles the retrieved program logic into a functioning application," and the claims use similar broad language '351 Patent, abstract This could support an argument that any process that takes programmatic text files and creates a functional UI meets the limitation.
- Evidence for a Narrower Interpretation: The specification heavily details the role of a specific client-side engine called the "Application Virtual Machine" (AVM) that performs the downloading and assembly '351 Patent, col. 4:28-34 The patent states, "The AVM interprets XML and other code downloaded from a web server...to render a full-featured application on the client computer" '351 Patent, col. 5:22-25 This context suggests the "assembling" is performed by a specialized client program, not a standard web browser.
VI. Other Allegations
- Indirect Infringement: The complaint makes a passing reference to contributory and induced infringement ("Compl. ¶12"), but it does not plead specific facts to support the required elements of knowledge and intent for any of the accused products.
- Willful Infringement: The complaint does not include an explicit allegation of willful infringement.
VII. Analyst's Conclusion: Key Questions for the Case
- Architectural Equivalence ('959 Patent): A core issue will be one of architectural mapping: can the functions of a modern, multi-layered web delivery infrastructure be mapped onto the specific "deceiver-controller-forwarder" architecture recited in Claim 1, or does the patent require a non-conventional system distinct from standard network components like load balancers and reverse proxies?
- Technological Evolution ('351 Patent): A key question of definitional scope will be central: can the term "assemble into the computer program," which the patent describes in the context of a bespoke "Application Virtual Machine," be construed to cover the dynamic rendering of a web application by a standard mobile browser, a technology that has evolved significantly since the patent's priority date?
- Functional Specificity ('298 Patent): An evidentiary question will focus on functional specificity: does the "role-based access control" of the Honeywell Safety Suite provide users with the specific capability for "remote management control of data directory structures," including the selection of a "single directory structure...for modification" as claimed, or does it merely offer permissioned access to data within a predefined and static file system?
Analysis metadata