ALDI Inc v. Intellectual Ventures I LLC

I. Executive Summary and Procedural Information

• Parties & Counsel:
  • Plaintiff: Aldi Inc. (Illinois)
  • Defendant: Intellectual Ventures I LLC (Delaware); Intellectual Ventures II LLC (Delaware); and OL Security LLC (Delaware)
  • Plaintiff's Counsel: Morris, Nichols, Arsht & Tunnell LLP
• Case Identification: 1:26-cv-00461, D. Del., 04/21/2026
• Venue Allegations: Venue is asserted based on Defendants being residents of, incorporated in, or subject to personal jurisdiction in Delaware, and their history of patent litigation within the district.
• Core Dispute: Plaintiff ALDI Inc. seeks a declaratory judgment that its use of common, third-party, open-source software does not infringe six patents that Defendants have asserted against it in pre-suit demand letters.
• Technical Context: The technologies relate to foundational aspects of large-scale distributed computing, including data storage management, cluster orchestration, parallel processing, and server migration, which are core components of modern cloud and enterprise IT infrastructure.
• Key Procedural History: This declaratory judgment action was precipitated by demand letters sent by Defendants (IV) to ALDI in June 2025 and March 2026, as part of what ALDI characterizes as a broader, revenue-based licensing campaign targeting the retail and eCommerce industry. The complaint alleges IV has filed numerous lawsuits against other major companies asserting the same patents against the same open-source software platforms. The complaint also raises prosecution history estoppel arguments, alleging that for certain patents, the patentees disclaimed during prosecution the very architectures now being accused.

Case Timeline

Date	Event
2002-03-13	U.S. Patent No. 7,257,582 Priority Date
2004-12-30	U.S. Patent No. 8,332,844 Priority Date
2005-08-16	U.S. Patent No. RE48,894 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
2008-03-14	U.S. Patent No. 7,930,287 Priority Date
2009-12-03	U.S. Patent No. 9,948,712 Priority Date
2011-04-19	U.S. Patent No. 7,930,287 Issued
2012-12-11	U.S. Patent No. 8,332,844 Issued
2013-01-08	U.S. Patent No. 8,352,584 Issued
2018-04-17	U.S. Patent No. 9,948,712 Issued
2022-01-11	U.S. Patent No. RE48,894 Issued
2023-11-XX	IV entities sued JPMorgan Chase, Comerica, and Liberty Mutual
2024-11-XX	IV entities sued American Airlines and Southwest Airlines
2025-03-XX	IV entities sued Bank of New York Mellon and Nationwide
2025-06-XX	IV entities sent first formal notice letter to ALDI
2025-07-XX	IV entities sued The Home Depot
2026-02-XX	IV entities sued Deere
2026-03-XX	IV entities sued GEICO
2026-03-20	IV entities sent second demand letter to ALDI
2026-04-21	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 (Issued Dec. 11, 2012)

The Invention Explained

• Problem Addressed: The patent's background describes the inefficiency of managing operating system and application software images in large computing clusters. Pre-creating an image for each server wastes disk space, while creating images "on the fly" from a master image results in slow cluster startup times and redundant operations like file system indexing. '844 Patent, col. 1:49-67 '844 Patent, col. 2:1-14
• The Patented Solution: The invention proposes a "root-leaf" system operating at the block level, below the file system. A common, read-only "root image" (e.g., a base OS) is stored once on a first storage unit. Changes made by an individual compute node are stored as a separate "leaf image" on a second storage unit. The leaf image contains only the new or modified data blocks. To improve performance, frequently accessed blocks from the root image are cached. '844 Patent, abstract '844 Patent, col. 2:33-49
• Technical Importance: This block-level, copy-on-write architecture aims to significantly reduce both storage consumption and application deployment time in large-scale, distributed server environments. '844 Patent, col. 2:50-54

Key Claims at a Glance

• The complaint focuses on independent method Claim 7 Compl. ¶41
• The essential elements of Claim 7 are:
  • 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, with said leaf images including only additional data blocks not previously in the root image and changes made by nodes to root image blocks.
  • The leaf images of respective compute nodes do not include blocks of the root image that are unchanged by the respective compute nodes.
  • Caching blocks of said root image that have been accessed by at least one of said compute nodes in a cache memory.
• The complaint seeks a declaration of non-infringement for all claims of the '844 Patent Compl. ¶103(b)

U.S. Patent No. 8,352,584 - System for Hosting Customized Computing Clusters (Issued Jan. 8, 2013)

The Invention Explained

• Problem Addressed: The patent background identifies that while High Performance Computing (HPC) clusters are beneficial for solving complex problems, they are difficult and resource-intensive to set up, manage, and maintain, placing them out of reach for many potential users '584 Patent, col. 1:38-54
• The Patented Solution: The patent describes a hosted system that provides multiple, customized computing clusters for remote clients. The system features at least two distinct clusters, each with a different configuration (e.g., for different client tasks), connected to a private network. Gateways isolate the clusters from each other, and a monitoring system tracks their operational status. Clients access their assigned cluster over a public network. '584 Patent, abstract '584 Patent, col. 3:11-40
• Technical Importance: The invention outlines a "cluster-as-a-service" model, allowing organizations to leverage customized, high-performance computing resources without the capital expenditure and operational burden of owning the infrastructure. '584 Patent, col. 1:55-60

Key Claims at a Glance

• The complaint focuses on independent system Claim 1 Compl. ¶51
• The essential elements of Claim 1 are:
  • A computer system comprising a private network linked to a public network.
  • A first cluster and a second cluster, each comprising computing resources including "at least one hardware processor," with each cluster in a different configuration.
  • A monitoring system for the clusters.
  • A first gateway and a second gateway linking the respective clusters to the private network.
  • The system isolates communications between the first and second clusters.
  • Both the first and second clusters are "high performance" clusters.
• The complaint seeks a declaration of non-infringement for all claims of the '584 Patent Compl. ¶103(c)

U.S. Patent No. 7,257,582 - "Load Balancing With Shared Data" (Apache Spark)

• Patent Identification: U.S. Patent No. 7,257,582, "Load Balancing With Shared Data," issued August 14, 2007.
• Technology Synopsis: The patent describes a method for parallel processing where an input file is logically subdivided into partitions. Descriptions of all partitions are distributed to a plurality of processors, which then self-allocate unprocessed partitions on a "first-come/first-served" basis without a central controller or scheduler. The complaint alleges the applicant disclaimed centrally directed task assignment during prosecution, likening the patented method to a "four-way stop" intersection where processors self-direct Compl. ¶¶62, 65, 66
• Asserted Claims: Claim 1 is identified as the example claim Compl. ¶65
• Accused Features: ALDI's use of Apache Spark is accused Compl. ¶63 The complaint argues Spark uses a central "driver" to assign tasks to "executors," which is the "traffic light" architecture allegedly disclaimed during prosecution Compl. ¶¶66, 67

U.S. Patent No. RE48,894 - "Disaggregated Resources and Access Methods" (Apache Kafka)

• Patent Identification: U.S. Reissued Patent No. RE48,894, "Disaggregated Resources and Access Methods," issued January 11, 2022.
• Technology Synopsis: The patent claims a method where a "resource consumer device" determines the organizational structure (e.g., parallel, serial) of a plurality of "resource nodes" based on the received node names themselves. The node names are configured to encode the topology, allowing the consumer to build a resource map from the names alone Compl. ¶¶72, 75, 76
• Asserted Claims: Independent Claim 8 and dependent Claim 15 are identified as the example claims Compl. ¶75
• Accused Features: ALDI's use of Apache Kafka is accused Compl. ¶73 The complaint argues that Kafka clients learn the cluster topology from metadata responses provided by brokers, not from the broker names, which are described as opaque administrative identifiers with no structural meaning Compl. ¶¶76, 78

U.S. Patent No. 7,930,287 - "Systems and Methods for Compound Searching" (Elasticsearch)

• Patent Identification: U.S. Patent No. 7,930,287, "Systems and Methods for Compound Searching," issued April 19, 2011.
• Technology Synopsis: The patent describes a search system that includes "display hardware" and provides an "interactive interface" supplied by the search service itself. This interface engages in a stateful, multi-turn "iterative clarification loop" with the user. The patent also describes the search service as an "intermediary" that develops search criteria and submits them to other standard search engines Compl. ¶¶83, 86, 88, 89
• Asserted Claims: Claim 28 is identified as the example claim Compl. ¶86
• Accused Features: ALDI's use of Elasticsearch is accused Compl. ¶84 The complaint argues Elasticsearch is backend server software with no display hardware or user interface (it uses APIs), is stateless and cannot perform the claimed iterative dialog, and is the search engine itself, not an intermediary Compl. ¶¶87-89

U.S. Patent No. 9,948,712 - "System and Method for Migrating an Agent Server to an Agent Client Device" (Docker Swarm)

• Patent Identification: U.S. Patent No. 9,948,712, "System and Method for Migrating an Agent Server to an Agent Client Device," issued April 17, 2018.
• Technology Synopsis: The patent claims a mandatory, sequential protocol for migrating a unique "agent server" instance from a departing device to a successor "agent client" device. The protocol requires the transfer of "agent server migration data" via a request/response process to move the unique server state Compl. ¶¶94, 97, 98
• Asserted Claims: Claim 16 is identified as the example claim Compl. ¶97
• Accused Features: ALDI's use of Docker Swarm is accused Compl. ¶95 The complaint argues Swarm's architecture, which uses the Raft consensus algorithm, is incompatible with the patent's premise. In Swarm, all manager nodes maintain complete, identical, and synchronized state at all times, meaning there is no unique server instance or migration data to transfer Compl. ¶¶98, 99

III. The Accused Instrumentality

Product Identification

• The accused instrumentalities are several widely adopted, third-party, open-source software platforms: Apache Spark, Elasticsearch, Docker, Kubernetes, Docker Swarm, and Apache Kafka Compl. ¶1 ALDI is accused of infringement through its use of this software Compl. ¶1

Functionality and Market Context

• The complaint alleges these are common, off-the-shelf software platforms used for core enterprise functions such as data processing (Apache Spark, Apache Kafka), containerization and orchestration (Docker, Kubernetes, Docker Swarm), and search (Elasticsearch) Compl. ¶¶25, 32 The complaint asserts that IV's infringement theories target the standard, native functionality of these platforms rather than any specific implementation or customization by ALDI Compl. ¶29 This allegation is central to ALDI's argument that IV is engaged in a broad, industry-wide licensing campaign untethered to specific acts of infringement Compl. ¶¶23, 29, 35

No probative visual evidence provided in complaint.

IV. Analysis of Infringement Allegations

'844 Patent Infringement Allegations

Claim Element (from Independent Claim 7)	Alleged Infringing Functionality	Complaint Citation	Patent Citation
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;	The complaint alleges Docker is not a block-level system. It operates at the file-system layer and does not provide a distinct "first storage unit," as all image layers reside in a unified storage area.	¶42; ¶43	col. 10:11-13
storing leaf images for respective compute nodes on respective second storage units...	The complaint alleges Docker does not provide "respective second storage units." All layers are managed by the same storage driver on the same host.	¶43	col. 10:14-16
said leaf images including only additional data blocks not previously contained in said root image and changes made by respective compute nodes...	The complaint alleges Docker's file-level copy-on-write mechanism copies entire files, not just modified blocks. The resulting container layer contains data previously in the image and is not comprised of "only" new or changed data.	¶43	col. 10:17-21
caching blocks of said root image that have been accessed by at least one of said compute nodes in a cache memory.	The complaint alleges Docker has no runtime block-level cache for root image blocks. Any OS-level caching is generic host behavior, not a feature of Docker's architecture as claimed.	¶43	col. 11:1-3

• Identified Points of Contention:
  • Scope Questions: A central question is whether the term "block-level", which appears throughout the patent's description of its architecture, can be interpreted to read on Docker's "file-system-layer" architecture Compl. ¶42 The dispute suggests a fundamental mismatch between the patent's claimed storage-layer operations and the accused product's file-layer operations.
  • Technical Questions: The analysis may turn on whether Docker's copy-on-write functionality, which operates on entire files, can satisfy the claim limitation requiring a leaf image to include "only" new or changed data blocks Compl. ¶43 This raises the factual question of what a Docker container's writable layer actually contains versus what the claim strictly requires.

'584 Patent Infringement Allegations

Claim Element (from Independent Claim 1)	Alleged Infringing Functionality	Complaint Citation	Patent Citation
A computer system, comprising: a... first cluster comprising a set of computing resources, including at least one hardware processor...	The complaint alleges Kubernetes is a software platform, not a "computer system" containing a "hardware processor." It argues prosecution history estoppel prevents this term from covering a software or virtualized processor.	¶56; ¶57	col. 11:15-18
a second cluster comprising a set of computing resources... wherein the first configuration differs from the second configuration;	The complaint alleges Kubernetes manages a single cluster under a single control plane and does not itself constitute a multi-cluster system with differing configurations as required by the claim.	¶57	col. 11:21-26
wherein communications between the first cluster and the second cluster are isolated;	The complaint alleges that any isolation between multiple Kubernetes clusters is supplied by external network infrastructure, not by Kubernetes itself as the claim appears to require.	¶57	col. 11:43-45
a first gateway communicatively linked between the first cluster and the private communications network;	The complaint alleges Kubernetes does not provide dedicated per-cluster gateways; this functionality is supplied by external, independent network infrastructure.	¶57	col. 11:34-38
wherein the first cluster is a high performance cluster; and wherein the second cluster is a high performance cluster.	The complaint alleges Kubernetes is a general-purpose orchestration platform and does not itself constitute a "high performance cluster" as the claim requires.	¶57	col. 11:45-48

• Identified Points of Contention:
  • Scope Questions: A primary legal question, grounded in prosecution history, is whether the claim term "at least one hardware processor" can read on Kubernetes, a software platform that contains no hardware and runs on infrastructure provided by an operator Compl. ¶¶52-55 Compl. ¶57 The resolution of this issue via claim construction could be dispositive.
  • Technical Questions: The infringement analysis will likely require determining whether Kubernetes, as a single-cluster management tool, can be said to provide the claimed system comprising two distinct, isolated clusters with dedicated gateways. This raises a factual question about whether the functions allegedly performed by external infrastructure can be attributed to the accused Kubernetes software itself.

V. Key Claim Terms for Construction

From the '844 Patent (Claim 7):

• The Term: "storing blocks" / "block-level"
• Context and Importance: The complaint frames the central non-infringement argument around an architectural mismatch, asserting the patent claims a "block-level" storage system while Docker operates at the "file system layer" Compl. ¶42 Practitioners may focus on this term because its construction-whether it is limited to direct storage-block manipulation versus encompassing higher-level file operations-could determine whether Docker's architecture falls within the claim's scope.
• Intrinsic Evidence for Interpretation:
  • Evidence for a Broader Interpretation: The patent does not appear to provide an explicit definition that would broaden the term beyond its conventional meaning in computer science.
  • Evidence for a Narrower Interpretation: The patent repeatedly distinguishes its "block-level" approach from file-level systems '844 Patent, col. 2:25-30, states that its Union Block Devices (UBDs) operate below the file system '844 Patent, col. 5:62-65, and describes its invention as "operating system, independent" because it is concerned with data blocks "rather than files they form" '844 Patent, col. 6:1-3 This language may support a narrow construction limited to storage-layer operations.

From the '584 Patent (Claim 1):

• The Term: "at least one hardware processor"
• Context and Importance: The complaint alleges that the patentee added this limitation during prosecution specifically to overcome a rejection for lacking hardware, creating a potential prosecution history estoppel Compl. ¶¶52-55 The definition of this term is critical because the accused product, Kubernetes, is a software platform that does not itself provide any hardware Compl. ¶57
• Intrinsic Evidence for Interpretation:
  • Evidence for a Broader Interpretation: The claims themselves do not explicitly exclude virtualized processors.
  • Evidence for a Narrower Interpretation: The complaint alleges that during prosecution of the parent patent, the examiner rejected claims for not containing "components that are limited to hardware," after which the patentee amended the claims to add "hardware processor" Compl. ¶¶53-54 This prosecution history, if accurately characterized, may strongly support a narrow construction that excludes software or virtualized processors, thereby preventing the patentee from recapturing subject matter surrendered to obtain the patent.

VI. Other Allegations

• Indirect Infringement: For each of the six patents, the complaint asserts that because ALDI does not directly infringe, it also cannot be liable for indirect infringement (induced or contributory) Compl. ¶44 Compl. ¶58 Compl. ¶68 Compl. ¶79 Compl. ¶90 Compl. ¶100 The complaint does not plead specific facts related to inducement or contribution, as its purpose is to secure a judgment of non-infringement on all grounds.
• Willful Infringement: The complaint does not contain allegations of willful infringement against ALDI, as ALDI is the plaintiff seeking declaratory relief. However, the complaint establishes that Defendants provided ALDI with pre-suit notice of the patents-in-suit through demand letters Compl. ¶¶2, 32, a fact that would be foundational to any subsequent counterclaim for willful infringement by Defendants.

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

This case appears to be a preemptive strike against a large-scale, patent monetization campaign targeting the use of ubiquitous open-source software. The resolution will likely depend on the court's determination of a few central issues:

• A core issue will be one of architectural mismatch: does the actual technical operation of modern, widely-adopted open-source platforms like Docker, Kubernetes, and Apache Spark align with the specific-and in some cases, contrary-architectures patented over a decade ago? The complaint repeatedly argues that the accused products function in a manner fundamentally different from that required by the claims.
• A second key issue will be one of prosecution history estoppel: for the '584 and ''582' patents, can the claims be construed to cover the accused software platforms after the patentee allegedly amended the claims to add limitations like "hardware processor" or disclaimed centrally-scheduled systems to secure their allowance?
• A third question is one of definitional scope: can system claims reciting specific hardware components (e.g., '584 patent's "hardware processor," ''287' patent's "display hardware") be infringed by the use of pure software platforms that do not themselves provide or constitute the claimed hardware?