DCT

1:26-cv-00397

Travelers Indemnity Co v. Intellectual Ventures I LLC

Log In
Key Events
Complaint
complaint Intelligence

I. Executive Summary and Procedural Information

  • Parties & Counsel:
  • Case Identification: The Travelers Indemnity Company v. Intellectual Ventures I LLC, et al., 1:26-cv-00397, D. Del., 04/08/2026
  • Venue Allegations: Plaintiff alleges venue is proper because each Defendant is a resident of, incorporated in, or subject to personal jurisdiction in the District of Delaware, and has purposefully availed itself of the forum by bringing prior patent enforcement actions in the district.
  • Core Dispute: Plaintiff seeks a declaratory judgment of non-infringement for fourteen patents that Defendants have asserted against Plaintiff's use of common, third-party, open-source and commercial software platforms.
  • Technical Context: The technologies at issue span fundamental aspects of modern enterprise computing, including application containerization, data streaming, distributed data processing, and secure networking.
  • Key Procedural History: The complaint arises from a patent licensing campaign initiated by IV against Travelers beginning in December 2023. IV sent multiple notice letters accusing Travelers of infringement based on its use of third-party software and threatened litigation. The complaint notes that IV has filed numerous similar lawsuits against other companies based on the same patents and accused software. The complaint also mentions that two of the asserted patents survived ex parte reexamination proceedings at the USPTO.

Case Timeline

Date Event
2001-12-14 U.S. Patent No. 8,407,722 Priority Date
2002-03-13 U.S. Patent No. 7,257,582 Priority Date
2003-03-31 U.S. Patent No. 7,949,785 Priority Date
2004-05-21 U.S. Patent No. 7,712,080 Priority Date
2004-12-30 U.S. Patent No. 8,332,844 Priority Date
2006-09-27 U.S. Patent No. 7,669,081 Priority Date
2007-08-14 U.S. Patent No. 7,257,582 Issued
2007-10-30 U.S. Patent No. 8,352,584 Priority Date
2009-03-24 U.S. Patent No. 8,447,762 Priority Date
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
2011-06-21 U.S. Patent No. 7,930,287 Issued
2012-08-28 U.S. Patent No. 8,266,124 Issued
2012-12-11 U.S. Patent No. 8,332,844 Issued
2013-01-08 U.S. Patent No. 8,352,584 Issued
2013-03-26 U.S. Patent No. 8,407,722 Issued
2013-05-21 U.S. Patent No. 8,447,762 Issued
2015-06-02 U.S. Patent No. 9,047,349 Issued
2017-06-20 U.S. Patent No. 9,686,183 Issued
2021-01-12 U.S. Patent No. RE48,894 Issued
2023-12-14 IV initiates contact with Travelers regarding patent licensing
2024-06-24 IV sends first "formal notice letter" to Travelers
2025-03-17 IV emails Travelers noting two asserted patents survived ex parte reexamination
2025-08-29 IV sends a second or supplemental notice letter to Travelers
2026-04-07 IV sends a third notice letter to Travelers from the Kasowitz law firm
2026-04-08 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 the inefficiency of managing application environments in a clustered computing system where multiple "compute nodes" run similar software Compl. ¶52 Traditional methods require creating and maintaining a full, separate software image for each node, which is resource-intensive and complicates updates '844 Patent, col. 1:12-2:2
  • The Patented Solution: The invention proposes a "branching store file system" where a single, read-only "root image" containing the common application environment is stored once Compl. ¶52 Each compute node then only stores its unique modifications and new data in a separate "leaf image" '844 Patent, col. 2:15-28 This block-level approach separates the base image from the changes, aiming to save storage space and streamline updates across the cluster '844 Patent, abstract
  • Technical Importance: This storage model provides a more scalable and efficient way to deploy and manage operating systems and applications across large numbers of servers, a core challenge in the growth of data centers and cloud computing '844 Patent, col. 1:12-28

Key Claims at a Glance

  • The complaint identifies independent claim 7 as asserted Compl. ¶56
  • Essential elements of Claim 7 include:
    • A method for providing data to a plurality of compute nodes, comprising:
    • storing blocks of a root image of said compute nodes on a first storage unit;
    • 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, wherein said leaf images of respective compute nodes do not include blocks of said root image that are unchanged by respective compute nodes;
    • and 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 explicitly reserve the right to assert dependent claims for this patent.

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

The Invention Explained

  • Problem Addressed: The patent addresses the difficulty of enabling computing devices, which may be located anywhere and behind different public or private network boundaries (like firewalls and NATs), to securely join and communicate with each other as if they were on a single private enterprise intranet Compl. ¶66 '785 Patent, col. 2:25-32
  • The Patented Solution: The invention provides a "private virtual dynamic network" that creates a separate, private virtual address realm Compl. ¶66 As illustrated in the patent's Figure 4, devices in different private domains (e.g., behind firewalls) can communicate through a "Virtual Domain" over the public Internet '785 Patent, Fig. 4 This is managed by a "virtual network manager" and software agents that allow devices to participate without requiring new hardware or software changes '785 Patent, abstract
  • Technical Importance: This technology facilitates the creation of secure, peer-to-peer virtual private networks (VPNs) that are flexible and can operate across complex, heterogeneous network topologies, a key requirement for remote work and distributed systems '785 Patent, col. 1:21-25

Key Claims at a Glance

  • The complaint identifies independent claim 30 as asserted Compl. ¶70
  • Essential elements of Claim 30 include:
    • A virtual network manager, comprising:
    • a network interface configured for data communication via a virtual network that is defined by a domain name having an associated public network address;
    • a memory and a processor to implement a register module configured to register devices in a virtual network;
    • the register module further configured to: receive a registration request from an agent associated with a device; and distribute a virtual network address to the device when the device is registered;
    • a DNS server for the virtual network, configured to receive a DNS request from a first device and return a network address associated with a network route director, a private network address for a second device, and a virtual network address for the second device.
  • The complaint does not explicitly reserve the right to assert dependent claims for this patent.

Multi-Patent Capsules

  • U.S. Patent No. 8,407,722: "Asynchronous Messaging Using a Node Specialization Architecture in the Dynamic Routing Network," issued March 26, 2013. This patent describes a network for routing update messages about "live objects" from input sources to client devices Compl. ¶83 The system uses a hierarchy of registries and specialized nodes to selectively forward updates to clients that have registered for them, ensuring clients receive relevant updates '722 Patent, abstract The complaint asserts independent claim 14 Compl. ¶86 The accused features involve the use of Apache Kafka Compl. ¶45c
  • U.S. Patent No. 7,257,582: "Load Balancing With Shared Data," issued August 14, 2007. This patent describes a method for distributing the processing of a large input file among a plurality of processors Compl. ¶98 The input file is logically subdivided into partitions without being read first, and descriptions of these partitions are distributed to subtask processors, which then read and process their assigned partitions on a first-come/first-served basis '582 Patent, col. 2:4-15 The complaint asserts independent claim 1 Compl. ¶102 The accused features involve the use of Apache Spark Compl. ¶45d
  • U.S. Patent No. 7,712,080: "Systems and Methods for Parallel Distributed Programming," issued May 4, 2010. The patent relates to a distributed parallel computing system using a "distributed shared variable" that is logically single but physically spread across multiple memories Compl. ¶114 Compl. ¶120 A computing program can "transform" into a parallel program by "spawning" a child program to perform parallel processing when an intermediate condition occurs '080 Patent, abstract The complaint asserts independent claim 9 Compl. ¶119 The accused features involve the use of Apache Airflow and/or Apache Spark Compl. ¶45e
  • U.S. Patent No. 7,669,081: "Systems and Methods for Scheduling, Processing, and Monitoring Tasks," issued February 23, 2010. This patent describes a computer-implemented method for performing a process composed of multiple tasks and checkpoints Compl. ¶185 A scheduler determines the order of tasks, while "checkpoint rules" associated with each checkpoint govern the execution of the process, defining which tasks are to be executed and how '081 Patent, abstract The complaint asserts independent claim 1 Compl. ¶189 The accused features involve the use of Apache Spark Compl. ¶45f
  • U.S. Patent No. 8,352,584: "System for Hosting Customized Computing Clusters," issued January 8, 2013. The patent describes a system for hosting multiple, customized computing clusters for different clients, where each cluster can have a different configuration of processing nodes, data storage, or networking Compl. ¶130 The system isolates the clusters from each other and includes a monitoring system '584 Patent, abstract The complaint asserts independent claim 1 Compl. ¶134 The accused features involve the use of Kubernetes Compl. ¶45b Compl. ¶131
  • 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. This patent describes a method for accessing files in a virtualized Network Attached Storage (NAS) system Compl. ¶150 Instead of storing full file paths, the system generates a "hashed-name key" from the file name and parent handle, reducing the size of the storage table '762 Patent, abstract The complaint asserts independent claim 7 Compl. ¶154 The accused features involve the use of MongoDB Compl. ¶45g
  • U.S. Patent No. RE48,894: "Disaggregated Resources and Access Methods," issued January 12, 2021. The patent describes a system where disaggregated resources (e.g., storage) are distributed among multiple resource nodes Compl. ¶198 Resource consumers collect incomplete information from individual nodes to create a complete map of the resource, which is then used to access it '894 Patent, abstract The complaint asserts dependent claim 15 Compl. ¶202 The accused features involve the use of Apache Kafka Compl. ¶45h
  • U.S. Patent No. 7,930,287: "Systems and Methods for Compound Searching," issued April 22, 2011. This patent describes a search service that presents an interactive interface to a user Compl. ¶170 Through iterative interaction, the service determines the user's purpose, develops search criteria, and then submits those criteria to one or more standard search engines on the user's behalf '287 Patent, abstract The complaint asserts independent claim 28 Compl. ¶174 The accused features involve the use of Elasticsearch Compl. ¶45i
  • U.S. Patent No. 9,686,183: "Digital Object Routing Based on Service Request," issued June 20, 2017. This patent describes a method for routing a "digital object" through a network where intermediate nodes determine availability to provide a requested service specified in a separate "digital transmission form" Compl. ¶217 Compl. ¶223 The object is then transmitted to nodes based on their availability to provide that service '183 Patent, abstract The complaint asserts independent claim 1 Compl. ¶222 The accused features involve the use of Apache Airflow Compl. ¶45k
  • U.S. Patent No. 8,266,124: "Load Balancing with Shared Data," issued September 11, 2012. The patent describes a method for integrated asset management of physical "computer-related hardware devices" Compl. ¶234 Compl. ¶239 The method involves receiving indications of "transition events" (e.g., installation, relocation) for these hardware devices and recording information about these events and changes into a centralized database '124 Patent, abstract Compl. ¶239 The complaint asserts independent claim 1 Compl. ¶238 The accused features involve the use of Kubernetes Compl. ¶45j
  • U.S. Patent No. 7,840,589: "Systems and Methods for Using Lexically-Related Query Elements Within a Dynamic Object for Semantic Search Refinement and Navigation," issued November 23, 2010. This patent describes a method for dynamically refining search queries in real-time Compl. ¶251 As a user types a query, a dynamic object (e.g., a drop-down menu) displays alternative, lexically-related search elements from a controlled vocabulary, allowing the user to refine the search '589 Patent, abstract The complaint asserts independent claim 22 Compl. ¶255 The accused features involve website search functionality on Travelers.com Compl. ¶45l
  • U.S. Patent No. 9,047,349: "Methods for Effective Processing of Time Series," issued June 2, 2015. The patent describes a method for representing and processing time series data by treating it as a "virtual part of data in the data store without actually being stored in the data store" Compl. ¶265 Compl. ¶269 This allows time-series queries to be processed directly in the data store layer, rather than in a higher application layer '349 Patent, abstract The complaint asserts independent claim 1 Compl. ¶269 The accused features involve the use of Elasticsearch Compl. ¶45m

III. The Accused Instrumentality

Product Identification

The accused instrumentalities are not products made or sold by Travelers, but are third-party software platforms that Travelers allegedly uses in its daily operations Compl. ¶34 Compl. ¶46 The complaint specifically names Docker, Kubernetes, Kafka, Spark, Airflow, MongoDB, and Elasticsearch as the accused software Compl. ¶1 Compl. ¶45

Functionality and Market Context

The complaint alleges that these are widely-used, third-party, and often open-source software products central to modern cloud computing and data processing infrastructure Compl. ¶34 Compl. ¶46

  • Docker: Accused of infringing the '844 Patent, Docker is a containerization platform Compl. ¶53 The complaint describes its functionality as using a "copy on write" strategy where a base "root image" (read-only layers) is shared, and changes for a specific container are written to a separate "thin R/W layer" (the "leaf image") Compl. ¶58
  • Kubernetes: Accused of infringing the '785 and '584 Patents, Kubernetes is a container orchestration platform Compl. ¶67 Compl. ¶131 The complaint describes its function as managing "pods" (accused "devices"), which are deployable units of computing that can be grouped into "clusters" and run on "nodes" (which can be virtual or physical machines) Compl. ¶71 Compl. ¶136 It uses a DNS service to create DNS records for pods and services within its virtual network Compl. ¶71

IV. Analysis of Infringement Allegations

Claim Chart Summary

The complaint presents Travelers' arguments for non-infringement by summarizing and refuting infringement contentions IV has allegedly made in other litigations.

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

Claim Element (from Independent Claim 7) Alleged Infringing Functionality (per IV's theory) Complaint Citation Patent Citation
storing blocks of a root image of said compute nodes on a first storage unit; Docker's read-only layers in a Docker image are the "root image." ¶58 col. 2:15-17
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... The "thin R/W layer in a runnable container" is the "leaf image," which uses a copy-on-write strategy for changes. ¶58 col. 2:18-24
...wherein said leaf images of respective compute nodes do not include blocks of said root image that are unchanged by respective compute nodes; Docker's copy-on-write strategy leaves unchanged data in the original image layers, allegedly meeting the negative limitation. ¶58 col. 2:24-27
and 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. 2:28-31

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

Claim Element (from Independent Claim 30) Alleged Infringing Functionality (per IV's theory) Complaint Citation Patent Citation
a network interface configured for data communication via a virtual network that is defined by a domain name having an associated public network address; Kubernetes' kube-proxy network interface allows communication via services defined in the cluster, which are assigned DNS names that can be associated with external public IP addresses. ¶75 col. 7:42-45
a memory and a processor to implement a register module configured to register devices in a virtual network... The Kubernetes DNS Service module watches the Kubernetes API for new services and creates DNS records, allegedly "registering" them. ¶71 col. 7:49-51
receive a registration request from an agent associated with a device; The creation of a new service in the Kubernetes API is the "registration request" from a "device" (a Kubernetes "pod"). ¶71 col. 7:52-53
distribute a virtual network address to the device when the device is registered... The complaint does not provide sufficient detail for analysis of this element. col. 7:54-58
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 has a cluster-aware DNS server (like CoreDNS) that resolves DNS requests for services to the appropriate network addresses. ¶71 col. 7:59-67

Identified Points of Contention

  • '844 Patent: The complaint includes a Docker documentation diagram showing a container's layered file system Compl. ¶58 This visual illustrates the separation between the read-only "Image Layers" and the "Thin R/W layer." A central technical question is whether Docker's "copy on write" mechanism meets the claim's negative limitation Compl. ¶59 The complaint alleges that when a file is modified, Docker's writable layer contains the entire modified file, including unchanged blocks, which would suggest a failure to meet the claim requirement that the leaf image "do[es] not include blocks of said root image that are unchanged" Compl. ¶59 A second point of contention is definitional: what evidence supports construing a Docker "container"-an isolated software process-as a "compute node" which the patent specification describes as including a "processing unit and memory"? Compl. ¶59
  • '785 Patent: The complaint provides screenshots from Kubernetes documentation defining "Containers," "Pods," and "Services" Compl. ¶72 A key legal question is one of claim scope: can the term "devices" as used in the claim be construed to read on Kubernetes "pods," which the complaint argues are software abstractions, not hardware with processors and memory as described in the patent? Compl. ¶73 A second technical question is whether the internal networking of a Kubernetes cluster, which can be configured with external IPs but often operates on a private, internal network, constitutes a "virtual network that is defined by a domain name having an associated public network address" as required by the claim Compl. ¶¶74-76

V. Key Claim Terms for Construction

'844 Patent: "compute nodes"

  • The Term: "compute nodes"
  • Context and Importance: The infringement theory depends on mapping this term to Docker "containers" Compl. ¶59 The construction of this term will determine whether the patent's architectural claims, written in the context of server hardware, can apply to modern software containerization technology.
  • Intrinsic Evidence for Interpretation:
    • Evidence for a Broader Interpretation: The patent does not appear to explicitly limit "compute nodes" to physical hardware in all instances, and one might argue that a virtual machine or a container acts as a logical equivalent of a compute node in a distributed system. The term itself could be argued to encompass any logical unit of computation.
    • Evidence for a Narrower Interpretation: The complaint highlights that the '844 Patent's specification states, "[i]n its most basic configuration, compute node 100 typically includes at least one processing unit 102 and memory 104" (Compl. ¶59, citing '844 Patent, col. 4:29-31). This language, tying the term to physical components like a "processing unit," may support a narrower construction limited to hardware or full virtual machines, and not lightweight software processes like containers.

'785 Patent: "devices"

  • The Term: "devices"
  • Context and Importance: IV's infringement allegation, as presented by Travelers, equates Kubernetes "pods" with the claimed "devices" Compl. ¶71 The viability of the infringement claim hinges on whether a software construct like a pod, which is a logical host for containers, falls within the patent's definition of a "device."
  • Intrinsic Evidence for Interpretation:
    • Evidence for a Broader Interpretation: The patent's claims do not explicitly define "device," and a party could argue that in the context of a "virtual" network, a "device" should be interpreted broadly to include virtual or logical devices, such as a pod that acts as a network endpoint.
    • Evidence for a Narrower Interpretation: The complaint points to specification language describing a "hardware architecture for the machines, server or other devices" that "includes one or more processors, a memory, a mass storage device," etc. (Compl. ¶70, citing '785 Patent, col. 9:42-48). This explicit linkage to hardware components may support an argument that the term "devices" as used in the claims is limited to physical computing hardware and does not read on software abstractions like pods.

VI. Other Allegations

Indirect Infringement

The complaint is for a declaratory judgment of non-infringement. It affirmatively states that Travelers does not indirectly infringe any of the asserted patents, including through inducement or contributory infringement, because there is no underlying direct infringement to support such claims Compl. ¶61 Compl. ¶78

Willful Infringement

This being a DJ action for non-infringement, the complaint does not allege willfulness. It notes IV's licensing campaign and notice letters, which establish IV's belief that Travelers had knowledge of the patents Compl. ¶¶34-43

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

This declaratory judgment action appears to be a preemptive strike against a broad patent assertion campaign targeting the use of fundamental, widely-adopted enterprise software. The case will likely center on the following key questions for the court:

  • A primary issue will be one of definitional scope and technological evolution: Can patent terms rooted in the language of physical hardware from the early-to-mid 2000s (e.g., "compute node," "devices") be construed to cover modern, abstracted software constructs like "containers" and "pods"? This question will be central to claim construction and will likely determine the applicability of several of the asserted patents to the accused software.
  • A second core issue will be one of technical and operational mismatch: For patents where the definitional scope may be broader, does the specific, step-by-step operation of the accused open-source software (e.g., Docker's file-based copy-on-write, Kafka's metadata discovery) meet the precise limitations recited in the claims? The complaint raises pointed arguments suggesting that the "off-the-shelf" functionality of these platforms diverges from the specific methods claimed by the patents.
Loading Complaint