DCT

2:26-cv-00605

DataCloud Tech LLC v. Cambium Networks Ltd

Log In
Key Events
Complaint
complaint Intelligence

I. Executive Summary and Procedural Information

  • Parties & Counsel:
  • Case Identification: 2:26-cv-00605, E.D. Tex., 07/23/2026
  • Venue Allegations: Venue is alleged to be proper on the basis that the Defendant is a foreign company.
  • Core Dispute: Plaintiff alleges that Defendant's unnamed products and services infringe two patents related to deploying software applications over a network and remotely accessing electronic files.
  • Technical Context: The patents relate to client-server architectures for efficiently deploying and managing applications and data on remote devices, a foundational technology for modern cloud-based services and network management.
  • Key Procedural History: The complaint asserts that because the patents-in-suit claim methods, the marking requirements of 35 U.S.C. § 287 do not apply, and therefore Plaintiff is entitled to past damages. A Certificate of Correction was issued for the '351 patent.

Case Timeline

Date Event
2001-02-20 '351 Patent Priority Date
2002-03-29 '298 Patent Priority Date
2007-07-17 '351 Patent Issue Date
2007-11-20 '351 Patent Certificate of Correction Issue Date
2008-07-08 '298 Patent Issue Date
2026-07-23 Complaint Filing Date

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

U.S. Patent No. 7,246,351 - "System And Method For Deploying And Implementing Software Applications Over A Distributed Network"

(Issued July 17, 2007; Compl. ¶11)

The Invention Explained

  • Problem Addressed: The patent's background section describes the challenges of deploying software applications to remote users, particularly on resource-constrained wireless devices like WPDAs. Browser-based solutions were slow and required constant connectivity, while locally installed compiled applications were large, difficult to install, and costly to update across different platforms '351 Patent, col. 1:41 - col. 2:67
  • The Patented Solution: The invention proposes an "Application Virtual Machine" (AVM), a small program installed on a client device. This AVM downloads text files (e.g., XML) containing application logic from a server and then "assembles the retrieved program logic into a functioning, graphical application in temporary memory" on the client device '351 Patent, col. 3:17-19 '351 Patent, abstract This architecture separates the application's execution engine from its logic, enabling rapid deployment of rich, platform-specific applications without large downloads or complex installations '351 Patent, col. 5:16 - col. 6:5
  • Technical Importance: The technology aimed to combine the rich user interface of a traditional desktop application with the deployment ease of a web application, a significant goal for the emerging mobile and wireless device market of the early 2000s '351 Patent, col. 2:61 - col. 3:6

Key Claims at a Glance

  • The complaint asserts independent claim 14 Compl. ¶16
  • Claim 14 is a method claim with the following essential elements:
    • providing to the client device text files containing embedded program logic for the software module to assemble into a computer program
    • running the computer program to provide a graphical user interface for receiving and interpreting user inputs to the client device
    • storing the embedded program logic on the client device
    • and assembling into the computer program running on the client device

U.S. Patent No. 7,398,298 - "Remote Access And Retrieval Of Electronic Files"

(Issued July 8, 2008; Compl. ¶21)

The Invention Explained

  • Problem Addressed: The patent addresses the need for users to access and manage their data stored on remote servers from a variety of different computing devices, a process complicated by disparate networks and device capabilities '298 Patent, col. 1:21-34 The background notes the lack of integrated systems for remote data management control and delivery verification '298 Patent, col. 2:1-13
  • The Patented Solution: The patent describes a server-based system that allows authenticated users to remotely access and manage their data and its corresponding directory structure '298 Patent, abstract A user can request to see their file directory, select a file, and direct the system to deliver it to a target (e.g., another user's email address), and then receive a confirmation that the delivery was completed '298 Patent, Fig. 12 The system utilizes a "profile data store" to control which data and directory structures are accessible to each user '298 Patent, col. 10, claim 1
  • Technical Importance: The invention provides a centralized framework for what is now commonly understood as cloud file management, enabling a user to control their remote data from any connected device and securely manage its distribution '298 Patent, col. 2:4-13

Key Claims at a Glance

  • The complaint asserts independent claim 13 Compl. ¶26
  • Claim 13 is a method claim with the following essential elements:
    • receiving a request at a server for remote management control of data directory structures
    • processing the request by providing directory structure information from a profile store if the data is deemed accessible
    • wherein a single directory structure is selected by the user for modification
    • delivering desired data to identified delivery targets
    • generating a notification of the delivery
    • determining data accessibility based on the profile store
    • delivering the user requested data and sending a confirmation of the delivery

III. The Accused Instrumentality

Product Identification

  • The complaint does not identify any specific accused products or services by name. It alleges infringement by unnamed "products and services" offered by the Defendant Compl. ¶16 Compl. ¶26

Functionality and Market Context

  • The complaint alleges that the functionality of the accused instrumentalities is detailed in Exhibits C and D, which are incorporated by reference but not attached to the complaint document Compl. ¶16 Compl. ¶26 The complaint states that Defendant "performed all steps of the asserted claim" and controlled the functionality, suggesting the accused instrumentalities are systems or methods operated by Defendant that allegedly practice the patented methods Compl. ¶17 Compl. ¶27 The complaint does not provide sufficient detail for analysis of the accused instrumentality's specific functions or market context.

IV. Analysis of Infringement Allegations

The complaint references but does not include the claim charts (Exhibits C and D) that detail its infringement allegations Compl. ¶16 Compl. ¶26 Therefore, a tabular analysis is not possible.

The complaint's narrative theory for the '351 Patent alleges that Defendant's systems and services practice the method of claim 14 by providing text files with embedded logic to client devices, where a program then assembles them into a functional application Compl. ¶16 Compl. ¶17

For the '298 Patent, the complaint's narrative theory alleges that Defendant's systems and services practice the method of claim 13 by offering a service for remote management of data directory structures. This allegedly includes receiving user requests, processing them based on user-specific profiles, delivering data to specified targets, and sending delivery confirmations Compl. ¶26 Compl. ¶27

No probative visual evidence provided in complaint.

  • Identified Points of Contention:
    • '351 Patent: A central question will be whether the accused system's function constitutes "assembling" a "computer program," as the patent describes building a graphical application from components '351 Patent, col. 3:17-19 The dispute may focus on whether pushing configuration files or updates to a network device meets this limitation, or if a more dynamic, on-the-fly application construction is required. Another point may be whether the information transmitted by the accused system qualifies as "embedded program logic" or is merely data or settings.
    • '298 Patent: The infringement analysis may hinge on the scope of "remote data directory structure management" and "modification." A question for the court will be whether this language, used in the context of "electronic files," can read on the management of device configurations or network hierarchies, or if it is limited to traditional user file systems. Furthermore, a factual question will be what, if any, function in the accused system constitutes "sending a confirmation of the delivery" as required by the claim.

V. Key Claim Terms for Construction

  • The Term: "assembling into the computer program" (from '351 Patent, claim 14)
  • Context and Importance: This term is central to the inventive concept of the '351 patent. Its construction will likely determine whether the patent covers modern cloud-based configuration management systems or is limited to the specific on-the-fly application-building process described in the specification.
  • Intrinsic Evidence for Interpretation:
    • Evidence for a Broader Interpretation: Plaintiff may argue that the claim language itself does not require a specific type of assembly, and any process where downloaded logic is combined with a client-side component to create a functioning program falls within the term's plain meaning.
    • Evidence for a Narrower Interpretation: The specification repeatedly describes the process in the context of an "Application Virtual Machine" (AVM) that "assembles the retrieved program logic into a functioning, graphical application in temporary memory" '351 Patent, col. 3:17-19 Defendant may argue this context limits the term to the creation of a full graphical application from component parts, as opposed to simply applying new settings.
  • The Term: "a single directory structure ... selected ... for modification" (from '298 Patent, claim 13)
  • Context and Importance: Practitioners may focus on this term because its scope dictates the type of data management covered by the patent. A broad construction could cover a wide range of cloud services, while a narrow one could limit it to conventional file hosting.
  • Intrinsic Evidence for Interpretation:
    • Evidence for a Broader Interpretation: Plaintiff could argue that a "directory structure" is any hierarchical organization of data, and "modification" is any change to that data or its organization. This could potentially encompass managing settings in a network device tree or other non-file-based hierarchical data.
    • Evidence for a Narrower Interpretation: The patent is titled "Remote Access And Retrieval Of Electronic Files" and includes figures showing user interfaces with conventional file paths like "HOME/PEBBLES/PHOTOS" '298 Patent, Fig. 9A Defendant may cite this as evidence that "directory structure" should be given its ordinary meaning related to a file system for storing user documents, not abstract configuration hierarchies.

VI. Other Allegations

  • Indirect Infringement: The complaint includes allegations that track the legal standard for divided infringement, stating that Defendant "conditioned the third party's use of the functionality... on the performance of that step" and "controlled the manner and/or timing of the functionality" Compl. ¶17 Compl. ¶27 This suggests Plaintiff is prepared to argue that Defendant is liable even if all steps of the claimed methods are not performed by a single actor.
  • Willful Infringement: The complaint does not explicitly plead willful infringement or allege that Defendant had pre-suit knowledge of the patents. It does, however, include a prayer for relief requesting the court declare the case "exceptional" and award attorneys' fees under 35 U.S.C. § 285 Compl. ¶31.D

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

  • Pleading Sufficiency and Evidentiary Gaps: A threshold issue may be whether the complaint, which omits identification of any accused products and relies on unattached exhibits, meets the plausibility pleading standards. Should the case proceed, a primary challenge for the plaintiff will be to produce evidence demonstrating that the Defendant's unnamed network services technically perform the specific steps of the asserted method claims.
  • Definitional Scope: The case will likely turn on claim construction. A core issue for the '351 patent will be one of technical scope: does the act of managing or configuring network devices via a cloud platform constitute "assembling" a "computer program" from "embedded program logic" as envisioned by the patent?
  • Technological Equivalence: For the '298 patent, a key question will be one of functional analogy: can the concept of "remote data directory structure management," rooted in user file access, be construed to cover the management of hierarchical device settings in a modern network infrastructure, or is there a fundamental mismatch in the technological context?
Loading Complaint