DataCloud Tech LLC v. Hitachi Vantara LLC

I. Executive Summary and Procedural Information

• Parties & Counsel:
  • Plaintiff: DataCloud Technologies, LLC (Georgia)
  • Defendant: Hitachi Vantara LLC (Delaware)
  • Plaintiff's Counsel: Stamoulis & Weinblatt LLC
• Case Identification: 1:26-cv-00902, D. Del., 07/23/2026
• Venue Allegations: Venue is alleged to be proper in the District of Delaware because the Defendant is a corporation organized under the laws of Delaware.
• Core Dispute: Plaintiff alleges that Defendant infringes two patents related to methods for deploying software applications over distributed networks and for managing content within tag-delimited templates.
• Technical Context: The patents address technologies for creating and deploying flexible, thin-client software applications, particularly in the context of early web and mobile device environments where bandwidth and client-side resources were limited.
• Key Procedural History: The complaint notes that a Certificate of Correction was issued for each of the asserted patents. No other significant procedural events, such as prior litigation or post-grant proceedings, are mentioned.

Case Timeline

Date	Event
2000-02-15	**U.S. Patent No. 8,607,139** Priority Date
2001-02-20	**U.S. Patent No. 7,246,351** Priority Date
2007-07-17	U.S. Patent No. 7,246,351 Issue Date
2007-11-20	U.S. Patent No. 7,246,351 Certificate of Correction Issued
2013-12-10	U.S. Patent No. 8,607,139 Issue Date
2014-06-24	U.S. Patent No. 8,607,139 Certificate of Correction Issued
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 on July 17, 2007 (Compl. ¶11))

The Invention Explained

• Problem Addressed: The patent's background describes the challenges of deploying functional software applications to remote users, especially on resource-constrained devices like wireless personal digital assistants (WPDAs). Browser-based solutions were described as slow and limited, while locally installed applications were large, difficult to install, and hard to update ʼ351 Patent, col. 1:40 - col. 2:67
• The Patented Solution: The invention proposes an "Application Virtual Machine" (AVM), a small software module that resides on the client device. This AVM downloads text files (e.g., XML files) containing application logic from a server and then "assembles" this logic into a functioning, graphical application within the client's memory. This architecture separates the application logic from the execution engine, aiming to combine the rich user experience of a native application with the deployment flexibility of a web application ʼ351 Patent, abstract '351 Patent, col. 3:10-24
• Technical Importance: The technology sought to enable the creation of thin-client, graphical applications that could function effectively over slow connections while providing a "look and feel" previously found only in traditional, locally installed software ʼ351 Patent, col. 3:1-9

Key Claims at a Glance

• The complaint asserts independent claim 14 Compl. ¶16
• The essential elements of method claim 14 are:
  • storing and running a software module on a client device of a user;
  • providing to the client device text files containing embedded program logic for the software module to assemble into the computer program;
  • running the computer program assembled from the embedded program logic on the client device; and
  • enabling user interaction with the computer program running on the client device.

U.S. Patent No. 8,607,139 - "System and process for managing content organized in a tag-delimited template using metadata"

(Issued on December 10, 2013 (Compl. ¶21))

The Invention Explained

• Problem Addressed: The patent background explains that managing content for websites was inefficient. Hard-coding content directly into HTML pages made widespread changes difficult and required technical expertise. Existing template-based systems were often proprietary and lacked flexibility ʼ139 Patent, col. 1:56 - col. 2:40
• The Patented Solution: The invention describes a system where a "metadata template," written in a tag-delimited language like XML, defines the structure, data types, and properties for a set of content. This template is used to automatically generate a data entry form. A user populates this form, and the system then renders a final document (e.g., a web page) by combining the user's data with the structure defined in the template, thus separating the content from its presentation ʼ139 Patent, abstract '139 Patent, col. 2:53 - col. 3:24
• Technical Importance: This approach provided a structured, non-proprietary method for content management, enabling non-technical users to update website information via forms while allowing developers to maintain consistent site structure and appearance ʼ139 Patent, col. 2:41-50

Key Claims at a Glance

• The complaint asserts independent claim 8 Compl. ¶26
• The essential elements of method claim 8 are:
  • displaying a graphical interface based on a metadata template, the metadata template comprising an object that represents a structure and an appearance of a web page, wherein the object is based on a class stored in a base template, and wherein the graphical interface comprises an input field corresponding to the object, the input field defining a property of a data entry field;
  • generating a data entry form comprising the data entry field, wherein the data entry field is configured to accept input corresponding to content of the object; and
  • generating the web page based on the metadata template, wherein the web page comprises the content represented by the input.

III. The Accused Instrumentality

Product Identification

• The complaint does not explicitly name any accused products or services. Instead, it states that Defendant has infringed "because it shipped, distributed, made, used, imported, offered for sale, sold, and/or advertised the products and services described below in a way that infringes" and then incorporates by reference claim charts attached as Exhibits C and D Compl. ¶16 Compl. ¶26 These exhibits were not filed with the complaint.

Functionality and Market Context

• The complaint does not provide sufficient detail for analysis of the functionality or market context of any accused instrumentality. All infringement allegations are contained within the unfiled exhibits Compl. ¶16 Compl. ¶26

IV. Analysis of Infringement Allegations

The complaint references claim-chart exhibits (Exhibits C and D) that are not provided with the public filing Compl. ¶16 Compl. ¶26 The narrative infringement theory is limited to a recitation that the Defendant's unspecified products and services perform the steps of the asserted claims. No probative visual evidence provided in complaint.

• Identified Points of Contention:
  • Given the lack of information about the accused instrumentality, the initial point of contention will be evidentiary: identifying the specific products, services, and underlying architecture that Plaintiff accuses of infringement.
  • For the '351 Patent, a central technical question may be whether the accused system's client-side software "assemble[s]" a "computer program" from separate "text files containing embedded program logic," as required by claim 14, or whether it operates as a more conventional pre-compiled application that retrieves data.
  • For the '139 Patent, a key dispute may concern whether the accused system employs a "metadata template" to "generat[e] a data entry form" for content creation. The analysis would question if the defendant's content management process aligns with the specific template-driven architecture described in the patent.

V. Key Claim Terms for Construction

'351 Patent, Claim 14

• The Term: "assemble into the computer program"
• Context and Importance: This term is central to the claimed invention, which distinguishes itself from prior art by dynamically building an application on the client side. Practitioners may focus on whether "assemble" requires a specific type of construction process (e.g., rendering a GUI from XML definitions) versus merely executing a script that fetches data.
• Intrinsic Evidence for Interpretation:
  • Evidence for a Broader Interpretation: The specification describes how the system "assembles the retrieved program logic into a functioning, graphical application in temporary memory" (ʼ351 Patent, col. 3:18-20), language that could be argued to encompass a range of dynamic client-side processing.
  • Evidence for a Narrower Interpretation: The detailed description focuses on an "Application Virtual Machine (AVM)" that "interprets XML and other code" and "dynamically builds the user interface locally" (ʼ351 Patent, col. 5:19-24; '351 Patent, col. 7:36-37). This may support a narrower construction limited to systems that build applications from structured, declarative files like XML, rather than general-purpose scripting.

'139 Patent, Claim 8

• The Term: "metadata template"
• Context and Importance: The definition of this term is critical to determining the scope of the claim. The dispute will likely turn on what constitutes a "metadata template." Practitioners may focus on whether any file defining structure qualifies, or if it must contain the specific hierarchical elements detailed in the patent.
• Intrinsic Evidence for Interpretation:
  • Evidence for a Broader Interpretation: The patent summary states the invention "generates templates containing data describing data, known as metadata" and that the "data types and Web page structure are described and stored in the template as a dynamic content package of classes" (ʼ139 Patent, col. 2:55-62). This could suggest a broad definition.
  • Evidence for a Narrower Interpretation: The specification provides a detailed example of a template comprising "classes," "properties," "controls," and "data types," organized in an object model (ʼ139 Patent, Fig. 5; '139 Patent, Fig. 6). This may support an argument that a "metadata template" must include this specific, structured organization for defining a data entry form.

VI. Other Allegations

• Indirect Infringement: The complaint alleges a theory of divided infringement, stating that to the extent a third party performs any claimed step, the "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 These allegations appear tailored to satisfy the "control or direction" standard for liability in cases of divided infringement.
• Willful Infringement: The complaint does not contain an explicit allegation of willful infringement or plead facts suggesting pre-suit knowledge of the patents by the Defendant. It does include a prayer for relief requesting that the court declare the case "exceptional" and award attorneys' fees pursuant to 35 U.S.C. § 285 Compl. ¶31.D

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

1. An Evidentiary Question: The primary and most immediate question is evidentiary. As the complaint incorporates all specific infringement allegations by reference to unfiled exhibits, the initial phase of the case will revolve around discovering the identity and technical architecture of the accused instrumentalities.
2. A Question of Technical Scope ('351 Patent): A core issue will be whether the accused system's client-side software performs an act of "assembl[ing]" a "computer program" from text-based logic files, as claimed. The case may turn on the distinction between a system that dynamically constructs an application interface and one that operates as a more conventional pre-compiled program that simply executes scripts or fetches data.
3. A Question of Definitional Scope ('139 Patent): The infringement analysis will likely focus on whether the accused system's content creation workflow falls within the patent's definition of a "metadata template." A central question will be whether the defendant's method for defining and capturing content is equivalent to the patent's specific process of using a structured template to generate a data entry form, which in turn is used to generate a final web page.