DataCloud Tech LLC v. Lite On Technology Corp

I. Executive Summary and Procedural Information

• Parties & Counsel:
  • Plaintiff: DataCloud Technologies, LLC (Georgia)
  • Defendant: Lite-On Technology Corporation (Taiwan)
  • Plaintiff's Counsel: Kent & Risley LLC
• Case Identification: 2:26-cv-00654, E.D. Tex., 08/05/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 website infrastructure infringes a patent related to a system and method for deploying software applications over a distributed network.
• Technical Context: The technology concerns a client-side architecture for running web applications, where a small client program assembles and executes application logic from text files sent by a server, aiming to improve performance and reduce server load.
• Key Procedural History: The asserted patent was the subject of a Certificate of Correction issued on November 20, 2007. The complaint asserts that the marking requirement of 35 U.S.C. § 287 does not apply because the asserted claim is a method claim.

Case Timeline

Date	Event
2001-02-20	'351 Patent Priority Date
2002-02-20	'351 Patent Application Filing Date
2007-07-17	'351 Patent Issue Date
2007-11-20	Certificate of Correction for '351 Patent Issued
2026-08-05	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"

• Patent Identification: 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's background describes the limitations of web applications in the early 2000s, particularly for resource-constrained devices like wireless personal digital assistants (WPDAs) '351 Patent, col. 2:1-17 Applications run entirely on a server were slow due to network latency for each user interaction, while applications requiring large, pre-installed client-side software were difficult to deploy and maintain across various devices '351 Patent, col. 2:18-41
• The Patented Solution: The invention proposes a client-side "Application Virtual Machine" (AVM), also referred to as an "application assembler," that is installed on the user's device '351 Patent, col. 4:32-35 This AVM downloads platform-neutral text files (e.g., XML) from a server, which contain the application's logic and user interface definitions '351 Patent, abstract The AVM then locally "assembles" these files into a functioning application on the client device, handling user interactions without necessarily contacting the server for every action, thereby creating a more responsive user experience '351 Patent, col. 7:31-50
• Technical Importance: This architecture aimed to provide the performance and rich interactivity of a traditional desktop ("fat-client") application with the ease of deployment and maintenance of a server-based ("thin-client") application '351 Patent, col. 6:55-68

Key Claims at a Glance

• The complaint asserts at least independent claim 14 of the '351 Patent Compl. ¶16
• The essential elements of independent claim 14, a method claim, are:
  • running a software module on a client device;
  • passing to the client device text files containing embedded program logic for the software module to assemble into a computer program;
  • providing, by the software module, a graphical user interface for receiving and interpreting user inputs to the client device;
  • parsing, by the software module, the text files on the client device to extract the embedded program logic; and
  • assembling, by the software module, the embedded program logic into the computer program running on the client device.
• The complaint's use of the phrase "at least claim 14" suggests the possibility that other claims, including dependent claims, may be asserted later in the litigation Compl. ¶16

III. The Accused Instrumentality

Product Identification

• The complaint identifies the accused instrumentality as Defendant's "website infrastructure" Compl. ¶16

Functionality and Market Context

• The complaint does not provide specific details regarding the functionality of the accused website infrastructure. The infringement allegations are contained within a claim chart referenced as "Exhibit B," which was not provided with the complaint document Compl. ¶16 The complaint alleges that Defendant made, used, sold, and advertised these products and services Compl. ¶16, but offers no further context on their specific functions or market position beyond this general statement.

No probative visual evidence provided in complaint.

IV. Analysis of Infringement Allegations

The complaint alleges that Defendant's website infrastructure infringes claim 14 of the '351 Patent Compl. ¶16 However, the complaint provides no specific factual allegations in its body to support this conclusion. Instead, it incorporates by reference an external document, "Exhibit B," which is described as a claim chart but was not included with the filed complaint Compl. ¶16 Without this exhibit, a detailed analysis of the infringement theory is not possible based on the provided documents. The narrative theory is that the Defendant's "website infrastructure" performs the steps of claim 14, either literally or under the doctrine of equivalents Compl. ¶16

• Identified Points of Contention:
  • Evidentiary Questions: The primary question will be what evidence Plaintiff can produce to support its allegations. The complaint's reliance on a missing exhibit suggests that the specific mapping of the accused infrastructure to the claim limitations will be a central point of discovery and dispute.
  • Technical Questions: A key technical question may be whether a modern website's operation-which typically involves a web browser executing JavaScript to manipulate a Document Object Model (DOM)-performs the specific steps of "parsing" and "assembling" program logic from "text files" in the manner required by the claim, as that process was understood and described in the context of the patent's 2001 priority date.

V. Key Claim Terms for Construction

• The Term: "software module"

• Context and Importance: This term from claim 14 defines the core client-side component that performs the key steps of the claimed method. The construction of this term will be critical in determining whether standard components of modern web browsers could be considered infringing, or if the claim is limited to a more specialized, add-on piece of software.

• Intrinsic Evidence for Interpretation:

  • Evidence for a Broader Interpretation: The claim uses the generic term "software module". The specification also uses the similarly general term "application assembler" '351 Patent, col. 22:56 Plaintiff may argue this language is not limiting and should cover any software entity that performs the claimed functions.
  • Evidence for a Narrower Interpretation: The specification repeatedly and extensively describes the preferred embodiment of this module as an "Application Virtual Machine" or "AVM" '351 Patent, col. 4:32-35 This AVM is described as a specific, downloadable, and compiled executable program that is installed on the client device '351 Patent, col. 9:46-54 '351 Patent, col. 11:60-63 A defendant could argue that "software module" should be construed as being limited to such a distinct, installed application, rather than a general-purpose JavaScript engine that is a standard part of a web browser.

• The Term: "assembling... the embedded program logic into the computer program"

• Context and Importance: This term describes the central function of the "software module". The interpretation of what constitutes "assembling" will likely be a focal point of the infringement analysis, particularly when comparing the patented method to modern web technologies.

• Intrinsic Evidence for Interpretation:

  • Evidence for a Broader Interpretation: The patent describes this process as including the creation of a "Document tree" based on a downloaded XML file and then using that tree to render a user interface '351 Patent, col. 12:5-8 Plaintiff may argue that this is analogous to a modern browser parsing HTML and using JavaScript to dynamically build a webpage, thus qualifying as "assembling."
  • Evidence for a Narrower Interpretation: The specification details a specific architecture for assembly involving "Component Factories" that render visual components based on the parsed schema '351 Patent, col. 14:52-68 A defendant may argue that "assembling" is limited to this specific multi-step process of using dedicated factories to build an application from scratch, which may be technically distinct from how a standard browser renders a webpage.

VI. Other Allegations

• Indirect Infringement: The complaint includes allegations that appear to address divided infringement under 35 U.S.C. § 271(a). It states that to the extent a third party performs a step, Defendant "conditioned the third party's use" on that performance and "controlled the manner and/or timing of the functionality" Compl. ¶17 No specific facts are provided to support this allegation of control.
• Willful Infringement: The complaint does not explicitly allege willful infringement. It does, however, request that the court declare the case "exceptional" and award attorneys' fees under 35 U.S.C. § 285 Compl. ¶21.D

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

This case appears poised to center on the challenge of applying a patent from the early-2000s web era to modern internet technologies. The key open questions for the court will likely be:

• A core issue will be one of definitional scope: Can the term "software module", described in the patent's specification as a distinct, installed "Application Virtual Machine," be construed to cover the integrated, standard JavaScript engine of a modern web browser?

• A central question will be one of technical and evidentiary sufficiency: Having filed a complaint devoid of specific infringement facts, can the Plaintiff produce evidence demonstrating that Defendant's modern "website infrastructure" performs the specific method of "assembling" program logic as recited in claim 14, or is there a fundamental mismatch in the underlying technical operation compared to that envisioned by the patent?