DCT

2:26-cv-00395

Intellectual Ventures I LLC v. Unitedhealth Group Inc

Log In
Key Events
Amended Complaint
complaint Intelligence

I. Executive Summary and Procedural Information

  • Parties & Counsel:
  • Case Identification: 2:26-cv-00395, E.D. Tex., 09/23/2026
  • Venue Allegations: Plaintiff alleges venue is proper because Defendants maintain numerous regular and established places of business within the Eastern District of Texas, including operational facilities and employees in Richardson, Plano, Frisco, and other cities. The complaint provides extensive documentation of these locations.
  • Core Dispute: Plaintiff alleges that Defendant’s backend computing systems and financial services, which utilize technologies such as Spark, Docker, and Kubernetes, infringe four patents related to parallel and distributed computing, cluster management, and root image caching.
  • Technical Context: The technology at issue relates to foundational methods for managing and executing large-scale software applications across multiple computers, a critical component of modern cloud computing and enterprise data processing infrastructure.
  • Key Procedural History: The complaint alleges that Defendant had pre-suit knowledge of all four patents-in-suit via a notice letter dated May 13, 2026. It further alleges knowledge of the '’844 and '’584 patents from an earlier letter dated April 29, 2025. These allegations form the basis for the willfulness claims.

Case Timeline

Date Event
2003-05-21 U.S. Patent No. 7,712,080 Priority Date
2004-12-30 U.S. Patent No. 8,332,844 Priority Date
2007-10-30 U.S. Patent No. 8,352,584 Priority Date
2007-10-30 U.S. Patent No. 7,822,841 Priority Date
2010-05-04 U.S. Patent No. 7,712,080 Issued
2010-10-26 U.S. Patent No. 7,822,841 Issued
2012-12-11 U.S. Patent No. 8,332,844 Issued
2013-01-08 U.S. Patent No. 8,352,584 Issued
2025-04-29 Notice Letter regarding '844 and '584 Patents sent to Defendant
2026-05-13 Notice Letter regarding all Patents-in-Suit sent to Defendant
2026-09-23 Complaint Filed

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

U.S. Patent No. 7,712,080 - "Systems and Methods for Parallel Distributed Programming"

  • Patent Identification: U.S. Patent No. 7,712,080 (“the ’080 Patent”), “Systems and Methods for Parallel Distributed Programming,” issued May 4, 2010.

The Invention Explained

  • Problem Addressed: The patent's background describes conventional methods for programming across multiple processors and memories as being problematic Compl. ¶82 Specifically, the "message passing" approach is described as "burdensome to develop" and disruptive to code structure, while the "distributed shared memory" (DSM) approach is often inefficient due to the need to transfer large amounts of data '080 Patent, col. 1:31-col. 2:2
  • The Patented Solution: The invention proposes a "navigational programming" model using "self-migrating threads" or agents that can physically move from one processor to another to access data '080 Patent, col. 3:15-30 This allows a program to maintain its logical structure while executing efficiently across a distributed system. The complaint highlights a method of transforming a sequential program into a parallel one by "spawning" a child program to run concurrently when a certain condition is met Compl. ¶82 '080 Patent, col. 11:15-col. 12:9
  • Technical Importance: The technology aimed to simplify the complex task of writing efficient code for parallel and distributed systems, a key challenge in the era of multi-core processors and computer clusters.

Key Claims at a Glance

  • The complaint asserts at least Claim 9 Compl. ¶82
  • The essential elements of independent claim 9, a system claim, include:
    • At least one distributed shared variable capable of loading into a memory area.
    • At least one distributed sequential computing program configured to access the shared variable.
    • The program is configured to transform into a distributed parallel computing program by spawning at least one child distributed sequential computing system program when an intermediate condition occurs.
    • The parallel program concurrently uses the original and spawned child programs to perform parallel processing.
    • The intermediate condition comprises a result required by the spawned child program to continue its computation.
  • The complaint does not explicitly reserve the right to assert dependent claims for the '080 Patent.

U.S. Patent No. 8,332,844 - "Root Image Caching and Indexing for Block-Level Distributed Application Management"

  • Patent Identification: U.S. Patent No. 8,332,844 (“the ’844 Patent”), “Root Image Caching and Indexing for Block-Level Distributed Application Management,” issued December 11, 2012.

The Invention Explained

  • Problem Addressed: In clustered computing environments, updating the "boot image" for all compute nodes is "cumbersome, as it means updating a number of copies of the boot image" '844 Patent, col. 1:64-67 Compl. ¶103 Pre-creating images for each server wastes disk space, while creating them on-the-fly from a master image is slow '844 Patent, col. 1:53-61
  • The Patented Solution: The patent describes a system using a read-only "root image" (a base system image) and a separate, writable "leaf image" for each compute node '844 Patent, col. 2:15-22 The leaf image stores only the changes and new data blocks specific to that node, rather than a full copy of the system '844 Patent, claim 1 This "branching store file system" merges the root and leaf images at a block level to present a complete, unique environment to each node, while also caching frequently accessed blocks from the root image to improve performance '844 Patent, col. 6:2-20 Compl. ¶103
  • Technical Importance: This approach provides a method for efficiently managing and deploying operating systems and applications in large-scale, stateless computing environments, reducing storage costs and boot times.

Key Claims at a Glance

  • The complaint asserts at least Claim 7 Compl. ¶103
  • The essential elements of independent claim 7, a method claim, include:
    • Storing blocks of a root image of compute nodes on a first storage unit.
    • Storing leaf images for respective compute nodes on respective second storage units, where the leaf images include "only additional data blocks not previously contained in said root image and changes made by respective compute nodes."
    • Caching blocks of the root image that have been accessed by at least one of the compute nodes in a cache memory.
  • The complaint does not explicitly reserve the right to assert dependent claims for the '844 Patent.

U.S. Patent No. 8,352,584 - "Systems for Hosting Customized Computing Clusters"

  • Patent Identification: U.S. Patent No. 8,352,584 (“the ’584 Patent”), “Systems for Hosting Customized Computing Clusters,” issued January 8, 2013.
  • Technology Synopsis: The patent addresses the technical problems of managing multi-cluster configurations and efficiently using cluster resources Compl. ¶126 '584 Patent, col. 1:39-43 The invention is a system for hosting multiple, customized computing clusters for different clients, where each cluster is isolated from the others via gateways and a central monitoring system tracks operational and connectivity problems Compl. ¶126 '584 Patent, claim 1
  • Asserted Claims: The complaint asserts at least independent Claim 1 Compl. ¶126
  • Accused Features: The complaint alleges that UnitedHealth systems that "utilize multi-cluster Kubernetes" infringe this patent Compl. ¶124

U.S. Patent No. 7,822,841 - "Method and System for Hosting Multiple, Customized Computing Clusters"

  • Patent Identification: U.S. Patent No. 7,822,841 (“the ’841 Patent”), “Method and System for Hosting Multiple, Customized Computing Clusters,” issued October 26, 2010.
  • Technology Synopsis: Similar to the '584 Patent, this invention addresses the complexity and expense of maintaining multiple computer clusters '841 Patent, col. 2:22-25 Compl. ¶149 The solution described is a system for hosting multiple customized clusters that are isolated and monitored, with a main monitor and per-node monitors to report hardware and software problems Compl. ¶149 '841 Patent, claim 1
  • Asserted Claims: The complaint asserts at least independent Claim 1 Compl. ¶149
  • Accused Features: The complaint alleges that UnitedHealth systems that "utilize multi-cluster Kubernetes" infringe this patent Compl. ¶147

III. The Accused Instrumentality

Product Identification

  • The "Accused Systems and Services" are identified as UnitedHealth's internal financial and healthcare technology platforms Compl. ¶33 The complaint specifically names systems utilizing open-source technologies Spark, Docker, and Kubernetes as the instrumentalities that infringe the patents-in-suit Compl. ¶34 Compl. ¶66

Functionality and Market Context

  • The Accused Systems and Services are described as the backend infrastructure that enables UnitedHealth's various business operations, including health plan administration, claims processing, data analytics, and customer support Compl. ¶9 Compl. ¶24 These systems are allegedly deployed on UnitedHealth's on-premise and/or private cloud infrastructure Compl. ¶83 Compl. ¶104 The complaint also identifies agent-facing portals like "Jarvis" as part of the ecosystem that relies on this underlying technology Compl. ¶40 A screenshot from the complaint shows the "Welcome to Jarvis" portal for agents and brokers to sign in Compl. p. 27 As the nation's largest health insurance provider, these technology platforms are central to UnitedHealth's operations, which serve over 151 million people Compl. ¶32

IV. Analysis of Infringement Allegations

Although the complaint references external claim chart exhibits which are not provided Compl. ¶96 Compl. ¶119, the narrative allegations provide a basis for analysis.

  • ’080 Patent Infringement Allegations
Claim Element (from Independent Claim 9) Alleged Infringing Functionality Complaint Citation Patent Citation
at least one distributed sequential computing program... A program or job submitted to UnitedHealth's Spark environment. ¶80; ¶83 col. 5:26-54
configured to transform into at least one distributed parallel computing program by spawning at least one child distributed sequential computing system program when at least one intermediate condition occurs... UnitedHealth's systems allegedly use Spark, a distributed computing framework, which takes a single program and breaks it into parallel tasks (child programs) that are distributed across worker nodes for concurrent execution based on data dependencies or stages (intermediate conditions). ¶82; ¶83 col. 5:56-62
wherein the at least one distributed parallel computing program concurrently uses the at least one distributed sequential computing program and the at least one spawned child distributed sequential computing program to perform parallel processing and/or operations... Spark's architecture allegedly involves a driver program (the original program) coordinating with multiple executor processes (spawned child programs) that run concurrently on different nodes to perform parallel processing. ¶82; ¶83 col. 6:23-31
  • ’844 Patent Infringement Allegations
Claim Element (from Independent Claim 7) Alleged Infringing Functionality Complaint Citation Patent Citation
storing blocks of a root image of said compute nodes on a first storage unit; UnitedHealth allegedly uses Docker, which relies on a base system image (the "root image") that is stored as a set of read-only layers and serves as the foundation for containers. ¶101; ¶104 col. 1:62-64
storing leaf images for respective compute nodes on respective second storage units, said leaf images including only additional data blocks not previously contained in said root image and changes made by respective compute nodes... Docker containers, when running, create a new writable layer (the "leaf image") on top of the base image. This layer allegedly stores only the new files or modifications (changes) made by that specific container. ¶103; ¶104 col. 2:15-22
caching blocks of said root image that have been accessed by at least one of said compute nodes in a cache memory. Docker's storage drivers and the underlying host operating system allegedly cache frequently accessed layers or blocks from the base "root" image to accelerate container startup and operation. ¶103; ¶104 col. 6:2-20
  • Identified Points of Contention:
    • Scope Questions ('080 Patent): A primary question will be whether the general-purpose, data-centric parallelism of Apache Spark constitutes the specific "navigational programming" and "spawning" of a "child...program" as described in the '080 patent. The defense may argue that the patent's teachings are confined to a "mobile agent" paradigm where the code itself migrates, which is functionally different from Spark's distribution of data and tasks.
    • Technical Questions ('844 Patent): While the functional overlap between Docker's layered filesystem and the '844 patent's claims appears significant, the analysis may focus on precise technical implementation. A key question is whether a Docker container's writable layer contains only the new and changed blocks as strictly required by the claim language, particularly as construed in light of the prosecution history cited in the complaint Compl. ¶103 The defense may argue that Docker layers contain additional metadata or structures that take them outside the literal scope of the claim.

V. Key Claim Terms for Construction

  • Term: "distributed sequential computing program" ('080 Patent, Claim 9)

  • Context and Importance: The definition of this term is fundamental to the scope of the '080 patent. Plaintiff's infringement theory against Spark hinges on this term being construed broadly to cover modern data-parallel jobs. Practitioners may focus on this term because if it is construed narrowly to mean only a "mobile agent" program as explicitly detailed in the specification, it may be difficult to read on the accused Spark systems.

  • Intrinsic Evidence for Interpretation:

    • Evidence for a Broader Interpretation: The background of the invention discusses "parallel distributed programs" in general terms, suggesting the invention is meant to be a broad improvement in that field '080 Patent, col. 1:25-30
    • Evidence for a Narrower Interpretation: The detailed description heavily emphasizes a specific implementation called "navigational programming" that uses "self-migrating threads" and explicit hop() commands to move between processors ('080 Patent, col. 3:15-30; col. 5:43-46). This could support an argument that the claimed "program" is limited to this specific type of mobile agent.

  • Term: "leaf images including only additional data blocks... and changes made" ('844 Patent, Claim 7)

  • Context and Importance: The word "only" makes this a potentially narrow limitation. The infringement case against Docker depends on its container layers meeting this specific definition. Practitioners may focus on this term because the prosecution history, which the complaint itself references, appears to have added this limitation to secure the patent, potentially creating a file history estoppel that limits the patentee to a very strict interpretation Compl. ¶103

  • Intrinsic Evidence for Interpretation:

    • Evidence for a Broader Interpretation: The summary of the invention describes the leaf/root concept in more general, functional terms, which might support an interpretation where "only" does not exclude incidental metadata inherent to the filesystem's operation '844 Patent, col. 2:15-22
    • Evidence for a Narrower Interpretation: The complaint's own citation to the patent's file history suggests the patentee distinguished prior art by emphasizing that the leaf images "do not include blocks of said root image that are unchanged" Compl. ¶103 This provides strong evidence for a narrow construction where the leaf image must be strictly limited to deltas, and cannot contain any unmodified blocks from the root. A screenshot of a WellMed clinic in Plano, Texas, is provided as one of many examples of Defendant's physical presence in the district Compl. p. 19

VI. Other Allegations

  • Indirect Infringement: The complaint alleges induced infringement across all patents, asserting that UnitedHealth provides instructions, documentation, and training to its employees, partners, and customers on how to use the Accused Systems and Services (e.g., Spark, Docker, Kubernetes) in an infringing manner Compl. ¶89 Compl. ¶112 Compl. ¶135 Compl. ¶158 Contributory infringement is also pled, on the basis that the accused software components are especially made or adapted for infringement and are not staple articles of commerce with substantial non-infringing uses Compl. ¶93 Compl. ¶116 Compl. ¶139 Compl. ¶162
  • Willful Infringement: Willfulness is alleged for all four patents based on pre-suit notice. The complaint alleges UnitedHealth had actual knowledge of all patents-in-suit no later than May 13, 2026, and of the '844 and '584 patents as early as April 29, 2025, via notice letters Compl. ¶88 Compl. ¶111 Compl. ¶134 Compl. ¶157 The complaint asserts that despite this knowledge, UnitedHealth was "willfully blind to its existence" and continued its infringing activities Compl. ¶88

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

  • A core issue will be one of definitional scope: can the claims of the '080 patent, which describe a "navigational programming" model with migrating agents, be construed broadly enough to cover the architecture and operation of a general-purpose, data-parallel framework like Apache Spark? The outcome of this claim construction battle may be dispositive for this patent.
  • A second central question will involve technical equivalence and public domain: for the '844, '584, and '841 patents, the dispute will likely focus on whether the accused open-source technologies (Docker, Kubernetes) function in a manner that is technically indistinguishable from the patent claims. This raises the critical question of whether the patents claim novel inventions or are instead attempting to cover widely adopted, conventional features of public-domain software, a question that touches on both infringement and validity.
  • A final key question will be one of venue and corporate presence: given the extensive portion of the complaint dedicated to establishing Defendant's physical offices, employees, and operations within the Eastern District of Texas Compl. ¶¶6-58, a threshold battle may be fought over whether these activities are sufficient to establish a "regular and established place of business" for venue purposes under 28 U.S.C. § 1400(b).