DCT

1:26-cv-00392

Hartford Fire Insurance Co v. Intellectual Ventures I LLC

Log In
Key Events
Complaint
complaint Intelligence

I. Executive Summary and Procedural Information

  • Parties & Counsel:
  • Case Identification: 1:26-cv-00392, D. Del., 04/07/2026
  • Venue Allegations: Venue is alleged to be proper in the District of Delaware because the Defendant entities are residents of, incorporated in, or subject to personal jurisdiction in the district.
  • Core Dispute: Plaintiff seeks a declaratory judgment that it does not infringe, and that the asserted patents are invalid, in response to Defendants' multi-year patent licensing and enforcement campaign targeting Plaintiff's use of common third-party and open-source software.
  • Technical Context: The technologies at issue relate to foundational aspects of modern distributed computing, including virtualization, container orchestration, data processing, and network management.
  • Key Procedural History: The complaint alleges that beginning in late 2023, Defendants ("IV") engaged in an "aggressive patent licensing and enforcement campaign" against Plaintiff ("The Hartford"), which included multiple letters accusing The Hartford of infringement and threatening litigation. The complaint also notes that IV has filed numerous similar lawsuits against other companies based on the same patents and accused software. One of the patents-in-suit, the '785 Patent, is noted as having survived an ex parte reexamination at the USPTO.

Case Timeline

Date Event
2001-12-18 U.S. Patent No. 8,266,124 Priority Date
2003-03-31 U.S. Patent No. 7,949,785 Priority Date
2003-05-21 U.S. Patent No. 7,712,080 Priority Date
2003-05-22 U.S. Patent No. 7,203,711 Priority Date
2004-03-04 U.S. Patent No. 8,447,762 Priority Date
2004-12-30 U.S. Patent No. 8,332,844 Priority Date
2005-12-06 U.S. Patent No. 9,686,183 Priority Date
2006-09-27 U.S. Patent No. 7,669,081 Priority Date
2007-04-10 U.S. Patent No. 7,203,711 Issued
2010-02-23 U.S. Patent No. 7,669,081 Issued
2010-05-04 U.S. Patent No. 7,712,080 Issued
2011-05-24 U.S. Patent No. 7,949,785 Issued
2012-09-11 U.S. Patent No. 8,266,124 Issued
2012-12-11 U.S. Patent No. 8,332,844 Issued
2013-05-21 U.S. Patent No. 8,447,762 Issued
2017-06-20 U.S. Patent No. 9,686,183 Issued
2023-12-14 IV sends initial email to The Hartford
2024-07-03 IV sends notice letter identifying five patents
2025-08-29 IV sends notice letter identifying six additional patents
2026-03-03 IV sends third notice letter via outside litigation counsel
2026-04-07 Complaint for Declaratory Judgment filed

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

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

The Invention Explained

  • Problem Addressed: The patent addresses inefficiencies in deploying and managing software environments across numerous compute nodes in a cluster, such as the significant time, storage, and bandwidth required to create and update a complete, independent boot image for each node U.S. Patent No. 8,332,844, col. 1:49-63
  • The Patented Solution: The invention proposes a system using a common, read-only "root image" and individual "leaf images" for each compute node U.S. Patent No. 8,332,844, col. 2:15-21 A leaf image stores only the data blocks that are new or changed relative to the root image, which significantly reduces storage requirements and allows for near-instantaneous creation of new application environments U.S. Patent No. 8,332,844, col. 5:35-43 The system also caches frequently accessed blocks from the root image to improve performance U.S. Patent No. 8,332,844, abstract
  • Technical Importance: This differential storage model is a foundational concept for modern lightweight virtualization and containerization, enabling the rapid and efficient scaling of applications in cloud and data center environments U.S. Patent No. 8,332,844, col. 1:33-38

Key Claims at a Glance

  • The complaint identifies independent claim 7 as an exemplary asserted claim Compl. ¶46 It also states that independent claims 1, 7, 10, and 11 are asserted Compl. ¶47
  • Independent Claim 7 recites a method with these essential elements:
    • Storing blocks of a "root image" on a first storage unit.
    • Storing "leaf images" for respective compute nodes on second storage units.
    • The leaf images include "only additional data blocks not previously contained in said root image and changes made... to the blocks of the root image".
    • The leaf images "do not include blocks of said root image that are unchanged".
    • Caching blocks of the root image that have been accessed by a compute node.

U.S. Patent No. 7,949,785 - "Secure Virtual Community Network System"

The Invention Explained

  • Problem Addressed: The patent addresses the difficulty of enabling secure, direct communication between computing devices that are located in different physical networks, particularly when they are behind firewalls and Network Address Translation (NAT) devices, which typically prevent direct inbound connections U.S. Patent No. 7,949,785, col. 2:1-34
  • The Patented Solution: The invention describes a "virtual network manager" that creates a "virtual address realm" or overlay network U.S. Patent No. 7,949,785, abstract Devices register with the manager to receive a unique virtual IP address. A specialized DNS server within the manager resolves requests for devices in the virtual network, returning routing information that allows devices to communicate as if they were on the same private network, regardless of their physical network location or the presence of NATs U.S. Patent No. 7,949,785, col. 12:1-15 U.S. Patent No. 7,949,785, Fig. 7
  • Technical Importance: This technology creates a secure, software-defined network overlay, a concept central to modern VPNs and the networking models used by container orchestration platforms to manage communication between distributed application components U.S. Patent No. 7,949,785, col. 9:1-9

Key Claims at a Glance

  • The complaint identifies independent claim 30 as an exemplary asserted claim Compl. ¶67 It also states that independent claims 1, 30, 38, 48, 62, and 75 are asserted Compl. ¶68
  • Independent Claim 30 recites a virtual network manager with these essential elements:
    • A network interface for a virtual network defined by a domain name.
    • A "register module" configured to register "devices" in the virtual network by receiving a registration request and distributing a virtual network address to the device.
    • A "DNS server" configured to receive a DNS request from a first device and return network addresses associated with a network route director and a second device.

Multi-Patent Capsules

  • U.S. Patent No. 7,712,080: "Systems and Methods for Parallel Distributed Programming," issued May 4, 2010.

    • Technology Synopsis: The patent describes a distributed computing system using a "distributed shared variable" that can be loaded into memory. The system transforms a sequential computing program into a parallel one by spawning a child program when an intermediate condition is met Compl. ¶86
    • Asserted Claims: Independent claims 1 and 9 Compl. ¶87
    • Accused Features: The technology is accused of being infringed by The Hartford's use of Apache Airflow and/or Apache Spark, specifically targeting Spark's "Resilient Distributed Datasets" (RDDs) as the "distributed shared variable" (Compl. ¶¶84; Compl. ¶90; Compl. ¶91).

  • U.S. Patent No. 8,447,762: "Storing Lossy Hashes of File Names and Parent Handles Rather Than Full Names Using a Compact Table for Network-Attached-Storage (NAS)," issued May 21, 2013.

    • Technology Synopsis: The patent describes a method for accessing files that involves receiving a file-access request containing a "native file handle" determined from a "virtual file handle" that has a "client unique identifier" Compl. ¶108 This system uses multiple handle types to manage file access.
    • Asserted Claims: Independent claims 1, 7, 10, and 11, with claim 7 cited as exemplary Compl. ¶¶108-109
    • Accused Features: The technology is accused of being infringed by The Hartford's use of MongoDB. The infringement theory appears to map MongoDB's "_id" variable to the three required identifiers: a client unique identifier, a native file handle, and a virtual file handle (Compl. ¶¶106; Compl. ¶111).

  • U.S. Patent No. 8,266,124: "Integrated Asset Management," issued September 11, 2012.

    • Technology Synopsis: The patent describes a method of managing computer assets by "receiving an indication of an occurrence of at least one transition event" for "computer-related hardware devices" and recording information from that event into a centralized database Compl. ¶127
    • Asserted Claims: Independent claims 1 and 18 Compl. ¶128
    • Accused Features: The technology is accused of being infringed by The Hartford's use of Kubernetes Compl. ¶125 The complaint notes that IV has made similar infringement accusations against Kubernetes in other litigations Compl. p. 13

  • U.S. Patent No. 7,203,711: "Systems and Methods for Distributed Content Storage and Management," issued April 10, 2007.

    • Technology Synopsis: The patent describes a system for archiving and indexing files that comprises four distinct engines: a "content engine" for storage, an "indexing engine" for data content, a "metadata engine," and a "triage engine" for monitoring incoming files Compl. ¶146
    • Asserted Claims: Independent claims 1 and 10 Compl. ¶147
    • Accused Features: The technology is accused of being infringed by The Hartford's use of Elasticsearch Compl. ¶144 The complaint provides a table from a notice letter mapping this patent to Elasticsearch Compl. p. 11

  • U.S. Patent No. 7,669,081: "Systems and Methods for Scheduling, Processing, and Monitoring Tasks," issued February 23, 2010.

    • Technology Synopsis: The patent describes a computer-implemented method for performing a process that involves receiving checkpoints, where each checkpoint includes "checkpoint state data" and a "checkpoint rule governing execution of the process" that defines which tasks will execute and how Compl. ¶164
    • Asserted Claims: Independent claim 1 Compl. ¶164
    • Accused Features: The technology is accused of being infringed by The Hartford's use of Spark and/or PySpark Compl. ¶162 The complaint includes a table summarizing a notice letter that maps this patent to Spark/PySpark Compl. p. 11

  • U.S. Patent No. 9,686,183: "Digital Object Routing Based on a Service Request," issued June 20, 2017.

    • Technology Synopsis: The patent describes a method performed by a network device that receives a "digital transmission form" which is "wholly separate from the digital object." This form specifies a requested service and is used to determine the availability of nodes to provide that service for transmitting the object Compl. ¶182
    • Asserted Claims: Independent claim 1 Compl. ¶182
    • Accused Features: The technology is accused of being infringed by The Hartford's use of Airflow Compl. ¶180 The complaint includes a table from a notice letter mapping this patent to Airflow Compl. p. 12

III. The Accused Instrumentality

Product Identification

  • The accused instrumentalities are a collection of third-party and open-source software products that The Hartford allegedly uses in its operations Compl. ¶39 Compl. ¶41 These include Docker, Kubernetes, Apache Airflow, Apache Spark, MongoDB, Elasticsearch, and Apache Kafka Compl. ¶39

Functionality and Market Context

  • The accused products are foundational components of modern cloud-native and distributed data-processing architectures Compl. ¶41 The complaint alleges that IV's infringement theory is based on The Hartford's "alleged use of the Accused Software Products" and focuses on "off-the-shelf/built-in functionality," not on any customization unique to The Hartford Compl. ¶41
  • The complaint provides a table identifying five of the asserted patents, their example claims, and the corresponding open-source software used by The Hartford that is accused of infringement Compl. p. 7 This visual illustrates the direct mapping alleged by IV between its patents and these widely-used software tools.
  • Another table in the complaint consolidates notice letters from IV, mapping all eight patents-in-suit to specific open-source software products, reinforcing the allegation that the dispute centers on standard functionalities of these products Compl. p. 11
  • The Hartford alleges that IV is engaged in a broad litigation campaign, providing a table that summarizes other lawsuits filed by IV asserting the same patents against the same software products used by other companies Compl. p. 13

IV. Analysis of Infringement Allegations

The complaint does not contain claim charts but rather narrative non-infringement arguments, from which the Defendants' alleged infringement theories can be inferred. The following tables summarize these inferred theories.

U.S. Patent No. 8,332,844 Infringement Allegations

Claim Element (from Independent Claim 7) Alleged Infringing Functionality Complaint Citation Patent Citation
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 to the blocks of the root image... Docker "containers," which function as writable layers on top of a base "image," are alleged to be the claimed "leaf images." Compl. ¶49 ¶49 col. 5:35-43
caching blocks of said root image that have been accessed by at least one of said compute nodes in a cache memory. The complaint does not provide sufficient detail for analysis of this element. col. 6:8-14
  • Identified Points of Contention:
    • Scope Questions: The primary dispute may center on whether a Docker "container" meets the specific definition of a "leaf image." The complaint argues that a Docker container does not satisfy the claim's requirement of containing "only additional data blocks... and changes" Compl. ¶48 Compl. ¶51 This raises the question of whether the structure and content of a Docker container layer fall within the scope of the claim's "only" limitation.

U.S. Patent No. 7,949,785 Infringement Allegations

Claim Element (from Independent Claim 30) Alleged Infringing Functionality Complaint Citation Patent Citation
a register module configured to register devices in a virtual network... Kubernetes components are alleged to function as a "register module" for registering "devices." The complaint alleges IV's infringement theory is based on Kubernetes's standard functionality Compl. ¶65 Compl. ¶70 ¶65; ¶70 col. 11:1-20
a DNS server for the virtual network, the DNS server configured to receive a DNS request from a first device... and return a network address... Kubernetes's internal DNS service (e.g., CoreDNS), which provides service discovery and name resolution for "Pods" and "Services" within the cluster, is alleged to perform the functions of the claimed DNS server Compl. ¶65 Compl. ¶70 ¶65; ¶70 col. 11:61-67
  • Identified Points of Contention:
    • Scope Questions: A central issue will be the construction of the term "device." The complaint argues that Kubernetes registers "Pods," which it contends are not a "device" as claimed in the '785 Patent Compl. ¶70 This raises the question of whether the patent's term "device" can be construed to cover a logical construct like a Pod, which is a group of one or more application containers.

V. Key Claim Terms for Construction

U.S. Patent No. 8,332,844

  • The Term: "leaf image"
  • Context and Importance: The plaintiff's non-infringement position for the '844 Patent hinges on this term. The complaint alleges that Docker containers do not meet the claim's requirement that a "leaf image" contains "only additional blocks not previously contained in said root image and changes made... to the blocks of said root image" Compl. ¶47 Compl. ¶48 The interpretation of "leaf image" and the weight given to the word "only" will be critical.
  • Intrinsic Evidence for Interpretation:
    • Evidence for a Broader Interpretation: The patent's abstract describes that "The leaf images include additional data blocks not previously contained in the root image and changes made by respective compute nodes to the blocks of the root image," but omits the restrictive term "only" U.S. Patent No. 8,332,844, abstract A party might argue this suggests the core inventive concept is the differential storage itself, not the purity of the storage mechanism.
    • Evidence for a Narrower Interpretation: Claim 7 itself explicitly uses the term "only," as does the detailed description, which states, "The leaf image... only contains new data blocks... and changes made to the blocks of the root image" U.S. Patent No. 8,332,844, col. 5:35-43 This language may support a narrow construction that excludes any structure containing more than just the specified differential data.

U.S. Patent No. 7,949,785

  • The Term: "device"
  • Context and Importance: This term is central to the non-infringement argument for the '785 Patent. The complaint asserts that the accused Kubernetes software registers "Pods," not "devices" Compl. ¶70 The case may turn on whether a logical, ephemeral software construct like a Pod can be considered a "device" in the context of the patent.
  • Intrinsic Evidence for Interpretation:
    • Evidence for a Broader Interpretation: The claims use the general term "device" without express limitation to hardware. A party could argue that any addressable endpoint within the virtual network that sends or receives data fulfills the function of a "device" as contemplated by the patent's system.
    • Evidence for a Narrower Interpretation: The specification consistently refers to "computing devices" and "machines" when describing the entities that join the virtual network U.S. Patent No. 7,949,785, col. 1:26 U.S. Patent No. 7,949,785, col. 2:1 Furthermore, the patent describes a "Member Agent" being "installed on a client device," language which may suggest a more traditional computing platform rather than an abstract collection of processes like a Pod U.S. Patent No. 7,949,785, col. 8:16-18

VI. Other Allegations

This section is omitted as the complaint is for declaratory judgment and does not contain allegations of indirect or willful infringement.

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

This declaratory judgment action will likely center on fundamental questions of claim scope and the applicability of patents from an earlier technological era to modern, abstract, open-source software architectures. The outcome may depend on the court's resolution of these key issues:

  • A core issue will be one of definitional scope: Can terms like "device" and "leaf image," which are rooted in the context of physical or virtual machine management, be construed to cover more abstract, logical constructs like Kubernetes "Pods" and Docker "containers"? This question will likely drive the infringement analysis for the '785 and '844 patents.
  • A key thematic question will be one of technical evolution: Does the functionality of the accused open-source software (e.g., Spark, Elasticsearch, Airflow) represent a fundamentally different technical approach from what is described and claimed in the patents-in-suit, or does it practice the same core inventive concepts using a different implementation?
  • An underlying issue will be patent eligibility: The complaint repeatedly asserts that the claims of the patents-in-suit are directed to abstract ideas under 35 U.S.C. § 101 Compl. ¶57 Compl. ¶76 Compl. ¶98 Compl. ¶117 Compl. ¶136 Compl. ¶154 Compl. ¶172 Compl. ¶190 The court will have to analyze whether the claims, which often describe methods of organizing, storing, and processing data in distributed systems, are directed to patent-ineligible abstract concepts implemented with generic computer components.
Loading Complaint