Intellectual Ventures I LLC v. Unitedhealth Group Inc

I. Executive Summary and Procedural Information

• Parties & Counsel:
  • Plaintiff: Intellectual Ventures I LLC and Intellectual Ventures II LLC (Delaware)
  • Defendant: UnitedHealth Group Inc., UnitedHealthcare Inc., Optum Inc., and WellMed Medical Management, Inc. (Delaware / Minnesota)
  • Plaintiff's Counsel: Cherry Johnson Siegmund James PLLC
• Case Identification: 2:26-cv-00395, E.D. Tex., 05/14/2026
• Venue Allegations: Venue is alleged to be proper based on Defendants maintaining numerous regular and established places of business within the Eastern District of Texas, including operational facilities and offices in cities such as Richardson, Plano, Frisco, and McKinney.
• Core Dispute: Plaintiff alleges that Defendant's internal technology platforms and financial services, which utilize distributed computing technologies like Spark, Docker, and Kubernetes, infringe four patents related to parallel and distributed computing, cluster management, and image caching.
• Technical Context: The lawsuit concerns foundational technologies for large-scale distributed computing, which are central to the operation of modern cloud infrastructure, big data analytics, and enterprise-level software deployment.
• Key Procedural History: The complaint alleges that Defendant had pre-suit knowledge of the patents-in-suit via notice letters dated April 29, 2025, and May 13, 2026, which may be relevant to the allegations of willful infringement.

Case Timeline

Date	Event
2003-05-21	'080 Patent Priority Date
2004-12-30	'844 Patent Priority Date
2007-10-30	'841 Patent Priority Date
2007-10-30	'584 Patent Priority Date
2010-05-04	'080 Patent Issued
2010-10-26	'841 Patent Issued
2011-01-01	Defendant Optum created (approx.)
2012-12-11	'844 Patent Issued
2013-01-08	'584 Patent Issued
2025-04-29	Notice letter sent regarding '844 and '584 Patents
2026-05-13	Notice letter sent regarding '080, '844, '584, and '841 Patents
2026-05-14	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, Systems and Methods for Parallel Distributed Programming, issued May 4, 2010.

The Invention Explained

• Problem Addressed: The patent addresses the complexity of programming for systems with multiple processors and distributed memory areas '080 Patent, col. 1:25-28 It notes that prior "message passing" approaches are burdensome and disrupt the original code structure, while "distributed shared memory" (DSM) approaches are often inefficient due to large data transfers '080 Patent, col. 1:31 - col. 2:4
• The Patented Solution: The patent proposes a "navigational programming" model using "self-migrating threads" '080 Patent, col. 3:15-24 A program is transformed into a parallel version by "spawning" a child program when an intermediate result is generated that the child program will need to continue its computation '080 Patent, col. 11:14-29 This allows the original and child programs to execute concurrently, with the system managing the migration of computational tasks to the physical location of the data they need to access '080 Patent, col. 3:19-28
• Technical Importance: This approach sought to simplify parallel programming by preserving the original algorithm's structure while achieving the efficiency of more complex, manual parallelization techniques.

Key Claims at a Glance

• The complaint asserts at least Claim 9 '080 Patent, col. 11:5-10 Compl. ¶82
• Independent Claim 9 is a system claim comprising the following essential elements:
  • A distributed parallel computing system with at least one memory area and processor.
  • At least one "distributed shared variable" physically distributable across memories.
  • At least one "distributed sequential computing program" that is configured to be transformed into a "distributed parallel computing program."
  • The transformation occurs by "spawning at least one child distributed sequential computing program" when an "intermediate condition" occurs.
  • The parent and spawned child programs are used "concurrently" to perform parallel processing.
  • The intermediate condition comprises an "intermediate result" required by the spawned child program to continue its computation.

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, Root Image Caching and Indexing for Block-Level Distributed Application Management, issued December 11, 2012.

The Invention Explained

• Problem Addressed: In clustered computing, managing and updating the boot image for each compute node is "cumbersome" '844 Patent, col. 1:64-67 Pre-creating images for every server wastes disk space, while creating them "on the fly" by copying a master image results in long "bring-up time" '844 Patent, col. 2:1-7
• The Patented Solution: The patent describes a "branching store file system" using a read-only "root image" and a "leaf image" for each compute node '844 Patent, col. 2:15-22 Changes made by a node are stored only in its unique leaf image, which is then virtually merged with the common root image '844 Patent, col. 2:19-25 The solution also involves caching blocks of the root image that are accessed by a compute node and sharing indexing results for the root image among nodes to reduce redundant work '844 Patent, col. 2:40-49
• Technical Importance: This block-level, differential storage approach was designed to accelerate the deployment and updating of applications in large, distributed server environments.

Key Claims at a Glance

• The complaint asserts at least Claim 7 '844 Patent, col. 11:26-40 Compl. ¶103
• Independent Claim 7 is a method claim comprising the following essential elements:
  • Storing blocks of a root image on a first storage unit.
  • Storing leaf images for respective compute nodes on respective second storage units.
  • The leaf images include "only additional data blocks not previously contained in said root image and changes made by respective compute nodes to the blocks of the root image."
  • A negative limitation: "wherein said leaf images of respective compute nodes do not include blocks of said root image that are unchanged by respective compute nodes."
  • Caching blocks of the root image that have been accessed by at least one compute node in a cache memory.

Multi-Patent Capsule: U.S. Patent No. 8,352,584 - System for Hosting Customized Computing Clusters

• Patent Identification: U.S. Patent No. 8,352,584, System for Hosting Customized Computing Clusters, issued January 8, 2013.
• Technology Synopsis: The patent addresses the technical and logistical challenges of managing multiple, customized computing clusters for different clients '584 Patent, col. 2:20-27 It discloses a system architecture that uses gateways to isolate network traffic between clusters, a monitoring system to detect both cluster-level and node-level operational problems, and a firewall to control client access, thereby enabling the hosting of diverse cluster types in a shared infrastructure '584 Patent, abstract '584 Patent, col. 3:4-11
• Asserted Claims: At least Claim 1 is asserted Compl. ¶126
• Accused Features: The complaint alleges that Defendant's use of "multi-cluster Kubernetes" in its systems and services infringes the '584 Patent Compl. ¶124 Compl. ¶127

Multi-Patent Capsule: 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, Method and System for Hosting Multiple, Customized Computing Clusters, issued October 26, 2010.
• Technology Synopsis: This patent, a parent to the '584 Patent, also targets the problem of hosting and managing multiple clusters, noting that their complexity and resource consumption make them difficult for individual companies to maintain '841 Patent, col. 2:20-27 The proposed solution is a hosted system where clients can access customized clusters remotely, with the system providing monitoring for operational and connectivity problems and gateway mechanisms to isolate communications within each cluster '841 Patent, abstract
• Asserted Claims: At least Claim 1 is asserted Compl. ¶149
• Accused Features: The complaint alleges that Defendant's use of "multi-cluster Kubernetes" in its technology platforms infringes the '841 Patent Compl. ¶147 Compl. ¶150

III. The Accused Instrumentality

• Product Identification: The complaint identifies the accused instrumentalities as Defendant's "Accused Systems and Services," which are financial services and technologies that utilize backend platforms including, but not limited to, Docker, Spark, and Kubernetes Compl. ¶33 Compl. ¶34 Compl. ¶66
• Functionality and Market Context: The complaint alleges that these distributed computing technologies (Spark, Docker, Kubernetes) are used and managed by UnitedHealth Group to enable the various financial and healthcare products and services it offers to its customers, employees, and other third parties Compl. ¶34 Compl. ¶66 The complaint asserts that Defendant is the largest health insurance provider in the United States and that these technologies are integral to its vast operations, which include commercial and government-sponsored health insurance plans, pharmacy benefit management services, and healthcare technology solutions Compl. ¶32 The complaint includes a screenshot of the "Welcome to Jarvis" agent portal, which provides agents and brokers with sales tools and plan information, suggesting these portals are part of the accused systems that rely on the underlying infringing technologies Compl. p. 27 The complaint also includes numerous screenshots of Defendant's office locations, such as one for a branch in Richardson, TX, to establish a physical presence in the district where the accused systems are allegedly used and managed Compl. p. 3

IV. Analysis of Infringement Allegations

The complaint references claim chart exhibits that were not provided with the filing Compl. ¶95 Compl. ¶118 Therefore, the infringement allegations are summarized below in prose based on the complaint's narrative.

'080 Patent Infringement Allegations

The complaint alleges that Defendant's use of Apache Spark infringes the '080 Patent Compl. ¶80 Compl. ¶83 The infringement theory suggests that Spark's method of operation maps to the claimed method of transforming a sequential computing program into a parallel one. Specifically, it is alleged that Spark's process of breaking down a large computation and distributing it across multiple nodes for concurrent processing constitutes "transforming" the program by "spawning at least one child... program" that concurrently uses the original program to perform parallel processing, as recited in Claim 9 Compl. ¶82 The complaint points to Defendant's job postings requiring experience with Spark as evidence of use Compl. ¶83 Compl. ¶58

'844 Patent Infringement Allegations

The complaint alleges that Defendant's use of Docker technology infringes the '844 Patent Compl. ¶101 Compl. ¶104 The infringement theory centers on the alignment between Docker's container image architecture and the patent's claimed "root image" and "leaf image" structure. The complaint posits that Docker's use of a base image (the "root image") and layered, differential images for each container (the "leaf images") practices the claimed method Compl. ¶103 The allegations suggest that Docker's leaf images meet the claim limitation of including only additional or changed data blocks, and not including unchanged blocks from the root image Compl. ¶103 Evidence of use is supported by allegations of Defendant's job postings that require experience with Docker and Kubernetes Compl. ¶104 Compl. ¶60

Identified Points of Contention

• '080 Patent - Scope and Technical Equivalence: A central question may be whether the operations of a modern data-processing framework like Spark fall within the scope of the '080 patent's claims, which are described in the context of "navigational programming" and "self-migrating threads" '080 Patent, col. 3:15-24 The court may need to determine if Spark's task scheduling and data distribution is technically equivalent to the patent's specific method of "spawning" a "child" program that migrates between processors.
• '844 Patent - Technical Accuracy and Negative Limitations: The analysis may focus on whether the technical operation of Docker's layered filesystem meets the specific positive and negative limitations of Claim 7. A key question will be whether a Docker "leaf image" in fact satisfies the requirement that it "do[es] not include blocks of said root image that are unchanged" '844 Patent, col. 13:65-67 This could require a detailed technical examination of the specific storage drivers (e.g., OverlayFS, AUFS) used in Defendant's accused Docker implementations.

V. Key Claim Terms for Construction

'080 Patent, Claim 9

• The Term: "transforming the at least one distributed sequential computing program into at least one distributed parallel computing program by spawning at least one child distributed sequential computing program"
• Context and Importance: This phrase captures the core inventive step alleged for parallelization. Its construction will be critical because the infringement case depends on whether a modern framework like Spark, which partitions and schedules tasks, performs this specific "transforming by spawning" action. Practitioners may focus on this term because its scope will determine if the patent reads on a broad class of distributed systems or is confined to the specific "mobile agent" paradigm described in the specification.
• Intrinsic Evidence for Interpretation:
  • Evidence for a Broader Interpretation: The claim language itself is functional and does not explicitly mention "mobile agents" or "migration." The patent also describes the transformation in general terms of splitting a thread into two, where one continues on the current node and a "clone" hops to the next node, which could be argued to cover general task forking '080 Patent, col. 7:57-65
  • Evidence for a Narrower Interpretation: The specification heavily emphasizes "self-migrating threads" and "navigational programming" as the context of the invention '080 Patent, col. 3:15-31 The detailed description of transformations consistently uses "hop" commands and discusses agent migration, which may support an interpretation limiting the claim to this specific implementation '080 Patent, col. 5:43-45 '080 Patent, Figures 3a-5b

'844 Patent, Claim 7

• The Term: "leaf images ... do not include blocks of said root image that are unchanged"
• Context and Importance: This negative limitation is a defining feature of the claimed leaf image. The infringement analysis for Docker will turn on whether its layered images satisfy this requirement. Practitioners may focus on this term because negative limitations can create sharp distinctions, and a technical mismatch in how Docker's union filesystem handles pointers to unchanged blocks versus how the patent describes it could be dispositive.
• Intrinsic Evidence for Interpretation:
  • Evidence for a Broader Interpretation: The patent's abstract describes the leaf images as including "changes made by respective compute nodes to the blocks of the root image," which could be argued to imply a purely differential structure consistent with this limitation '844 Patent, abstract
  • Evidence for a Narrower Interpretation: The claim is part of a patent for a "block-level" system '844 Patent, title The specification describes the system as operating below the file system, dealing directly with data blocks '844 Patent, col. 5:65 - col. 6:2 This context may support a narrow, literal interpretation that requires the leaf image, at the block level, to be devoid of any pointers or data representing unchanged blocks from the root, a technical standard that an off-the-shelf Docker implementation might not meet.

VI. Other Allegations

• Indirect Infringement: The complaint alleges both induced and contributory infringement for all four patents. Inducement is primarily based on allegations that Defendant provides instructions and documents to its employees, customers, and vendors on how to use the infringing systems (e.g., Spark, Docker, Kubernetes) Compl. ¶¶89-91 Compl. ¶¶112-114 Contributory infringement is alleged on the basis that Defendant provides software and technologies that are especially adapted for use in an infringing manner and are not staple articles of commerce with substantial non-infringing uses Compl. ¶¶93-94 Compl. ¶¶116-117
• Willful Infringement: The complaint alleges willful infringement and willful blindness for all four patents Compl. ¶¶88, 111, 134, 157 The basis for this allegation is Defendant's alleged actual knowledge of the patents from notice letters dated April 29, 2025, and May 13, 2026, and its continued infringement after receiving such notice.

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

1. A question of technological evolution and scope: Can the claims of the '080 patent, which appear rooted in the "mobile agent" paradigm of the early 2000s, be construed to cover modern, mainstream distributed processing frameworks like Apache Spark? The case may turn on whether Spark's task scheduler is considered equivalent to the patent's specific "transforming by spawning a child" process.
2. A question of precise technical implementation: Does the architecture of containerization technology like Docker, particularly its use of layered union filesystems, satisfy the specific negative limitation in the '844 patent requiring that "leaf images... do not include blocks of said root image that are unchanged"? This question will likely require a deep technical dive into the block-level operation of the accused systems.
3. A question of abstraction and functionality: For the '584 and '841 patents, a key issue will be whether the functionalities provided by a container orchestration platform like Kubernetes-such as service discovery, load balancing, and monitoring-are equivalent to the claimed systems for hosting and managing "customized computing clusters," including the specific gateway, firewall, and monitoring components described in the patents.