Health Care Service Corp v. Intellectual Ventures II LLC

I. Executive Summary and Procedural Information

• Parties & Counsel:
  • Plaintiff: Health Care Service Corporation (Illinois)
  • Defendant: Intellectual Ventures II LLC (Delaware); Callahan Cellular LLC (Delaware); OL Security LLC (Delaware)
  • Plaintiff's Counsel: Heyman Enerio Gattuso & Hirzel LLP
• Case Identification: 1:26-cv-00466, D. Del., 04/23/2026
• Venue Allegations: Venue is alleged to be proper in the District of Delaware because each Defendant is a resident of, is incorporated in, or is subject to personal jurisdiction in the District.
• Core Dispute: Plaintiff seeks a declaratory judgment of non-infringement and invalidity for five patents, alleging that Defendants have accused it of infringement through its use of common third-party software including Apache Spark, Elasticsearch, Kubernetes, and Docker.
• Technical Context: The patents-in-suit relate to foundational technologies in distributed computing, including task scheduling, compound search, asset management, and data management for virtualized environments.
• Key Procedural History: This action was precipitated by a licensing demand from Defendants, which included threats of litigation and exemplary claim charts mapping the patents-in-suit to Plaintiff's alleged use of third-party software. The complaint notes that Defendants have engaged in a broad litigation campaign asserting the same patents against other companies using the same software. For U.S. Patent No. 8,266,124, the complaint highlights statements made during prosecution where the patentee allegedly disclaimed coverage of software or virtualized processes to overcome prior art rejections, which may give rise to a prosecution history estoppel argument.

Case Timeline

Date	Event
2001-12-18	Priority Date for U.S. Patent No. 8,266,124
2004-12-30	Priority Date for U.S. Patent No. 8,332,844
2006-09-27	Priority Date for U.S. Patent No. 7,669,081
2007-10-30	Priority Date for U.S. Patent No. 8,352,584
2008-03-14	Priority Date for U.S. Patent No. 7,930,287
2009-02-18	Patentee's Office Action Response filed during prosecution of the '124 Patent
2010-02-23	Issue Date for U.S. Patent No. 7,669,081
2010-12-09	Patentee/Appellant Reply Brief filed during prosecution of the '124 Patent
2011-04-19	Issue Date for U.S. Patent No. 7,930,287
2012-02-24	Board of Patent Appeals and Interferences Decision for '124 Patent
2012-09-11	Issue Date for U.S. Patent No. 8,266,124
2012-12-11	Issue Date for U.S. Patent No. 8,332,844
2013-01-08	Issue Date for U.S. Patent No. 8,352,584
2023-11-15	Defendants file litigation against Liberty Mutual, Comerica, and JP Morgan Chase
2024-11-02	Defendants file litigation against Southwest Airlines and American Airlines
2025-02-11	Defendants' representative first contacts Plaintiff to discuss patent portfolio
2025-03-04	Defendants' representative follows up with Plaintiff
2025-03-15	Defendants file litigation against Nationwide Mutual Insurance and Bank of New York Mellon
2025-04-04	Defendants' representative escalates demands, referencing recent lawsuits
2025-06-20	Defendants send exemplary claim charts to Plaintiff's counsel
2025-07-23	Defendants file litigation against Home Depot
2026-02-23	Defendants file litigation against Deere & Co.
2026-03-26	Defendants file litigation against Government Employees Insurance Co.
2026-04-23	Complaint for Declaratory Judgment filed

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

U.S. Patent No. 7,669,081 - "Systems and Methods for Scheduling, Processing, and Monitoring Tasks"

• Issued: February 23, 2010

The Invention Explained

• Problem Addressed: The patent's background describes the complexity and expense of operating multiple, disparate "closed" computer systems and notes the migration toward "open architecture" (OA) systems, which creates a need for sophisticated task scheduling within these more complex environments ʼ081 Patent, col. 1:20-2:14
• The Patented Solution: The invention is a framework for managing a complex process composed of multiple tasks. It introduces the concept of "checkpoints," which are more than just data save-points; they contain "intelligence" in the form of "checkpoint rules" that govern how the process proceeds from one stage to the next ʼ081 Patent, col. 12:18-22 This system uses a task scheduler and a series of processor functions linked by these rule-based checkpoints to create a resilient, configurable, and state-aware execution flow at the application level, independent of the underlying operating system ʼ081 Patent, abstract ʼ081 Patent, Fig. 2
• Technical Importance: This technology provided a method for building robust, fault-tolerant distributed applications by abstracting complex scheduling and state management away from bespoke application code into a reusable, rule-driven framework ʼ081 Patent, col. 4:1-12

Key Claims at a Glance

• The complaint identifies independent Claim 1 as asserted Compl. ¶43
• The essential elements of Claim 1 are:
  • A computer-implemented method for performing a process, comprising:
  • (a) receiving a request to perform a process having tasks and a scheduler rule;
  • (b) receiving checkpoints associated with the process, where each checkpoint has state data and a "checkpoint rule" that defines what tasks to execute and how, based on the state data and a condition;
  • (c) determining a first task to be scheduled into a priority queue per the scheduler rule;
  • (d) determining the first checkpoint to be used for the first task per the scheduler rule;
  • (e) creating checkpoint state data for the first checkpoint; and
  • (f) saving the checkpoint state data for the first checkpoint.

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

• Issued: April 19, 2011

The Invention Explained

• Problem Addressed: The patent identifies the difficulty users face in formulating effective search queries for conventional search engines, which often leads to irrelevant results, and notes the general challenge of judging and ranking relevance ʼ287 Patent, col. 1:21-41
• The Patented Solution: The invention describes an intermediary "search service" that acts as an intelligent front-end to standard search engines. Instead of accepting a single query, this service engages the user in an iterative, conversational dialog (e.g., asking clarifying questions) to determine their true intent ʼ287 Patent, col. 7:13-28 Based on this refined understanding, the service formulates and submits targeted search criteria to one or more backend search engines (e.g., Google) and then collects and potentially re-ranks or summarizes the results for the user ʼ287 Patent, abstract ʼ287 Patent, Fig. 4
• Technical Importance: This approach aimed to improve search relevance by shifting the burden of query formulation from the user to an intelligent system that could better parse human intent before leveraging the power of existing large-scale search infrastructure ʼ287 Patent, col. 7:13-19

Key Claims at a Glance

• The complaint identifies independent Claim 28 as asserted Compl. ¶59
• The essential elements of Claim 28 are:
  • A system comprising: a network interface to connect to a server providing a search service; and
  • display hardware configured to present an interactive interface that is "supplied by the search service."
  • The interface is configured to iteratively collect input to refine a search purpose.
  • The interface is further configured to request and receive a "first clarification," send it to the service, and in response, request and receive a "second clarification" to send to the service.

U.S. Patent No. 8,266,124 - "Integrated Asset Management"

• Issued: September 11, 2012
• Technology Synopsis: The patent describes a method and system for managing the lifecycle of physical computer hardware assets. Information from various sources regarding assets (e.g., desktops, printers) is aggregated into a centralized database, which is then used to schedule and manage "transition events" such as installation, relocation, or maintenance Compl. ¶¶72, 77 '124 Patent, abstract During prosecution, the patentee distinguished the invention from software-based systems Compl. ¶79
• Asserted Claims: Independent Claim 1 Compl. ¶76
• Accused Features: Plaintiff's alleged use of the Kubernetes container orchestration platform Compl. ¶73

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

• Issued: December 11, 2012
• Technology Synopsis: The technology relates to managing distributed applications using a copy-on-write approach. A common "root image" is stored on a first unit, and "leaf images" containing only the changes or additions for a specific compute node are stored on separate units '844 Patent, abstract This allows for efficient storage and deployment. The system also caches frequently accessed blocks from the root image to improve performance Compl. ¶92
• Asserted Claims: Independent Claim 7 Compl. ¶96
• Accused Features: Plaintiff's alleged use of the Docker containerization platform Compl. ¶93

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

• Issued: January 8, 2013
• Technology Synopsis: The patent describes a system for providing customized, hosted computing clusters to multiple clients. Each client's cluster can have a different configuration and is isolated from other clusters via gateways. The system includes a central monitoring system to oversee the operations of the hosted clusters '584 Patent, abstract Compl. ¶109
• Asserted Claims: Independent Claim 1 Compl. ¶113
• Accused Features: Plaintiff's alleged use of the Kubernetes container orchestration platform Compl. ¶110

III. The Accused Instrumentality

Product Identification

The accused instrumentalities are the third-party software platforms Apache Spark, Elasticsearch, Kubernetes, and Docker, which Plaintiff HCSC allegedly uses Compl. ¶1 Compl. ¶34

Functionality and Market Context

The complaint characterizes these as "off-the-shelf/built-in functionality" in widely used open-source or third-party software products for cloud computing, data processing, and container management Compl. ¶23 Compl. ¶33 Compl. ¶35 The infringement allegations described in the complaint are not based on any unique customization by HCSC, but rather on the standard operation of these platforms Compl. ¶33 The complaint includes a table of at least ten other companies that Defendants have sued for using the same software, suggesting the technologies are foundational in modern IT infrastructure Compl. pp. 10-11

IV. Analysis of Infringement Allegations

'081 Patent Infringement Allegations

Claim Element (from Independent Claim 1)	Alleged Infringing Functionality	Complaint Citation	Patent Citation
(b) receiving a plurality of checkpoints associated with the process, each checkpoint comprising checkpoint state data and at least a respective checkpoint rule governing execution of the process, wherein the checkpoint state data comprises information about the state of the process and wherein the checkpoint rule defines, based at least in part on at least one of the checkpoint state data and a first predetermined condition, one or more of the plurality of tasks to be executed and the way in which the one or more tasks will execute;	Plaintiff argues that Apache Spark's checkpointing mechanism does not meet this limitation because it only marks a Resilient Distributed Dataset (RDD) for saving to a file to truncate its dependency graph, and does not contain any "instructions or rules governing execution of a process."	¶45	col. 12:18-22

• Identified Points of Contention:
  • Scope Questions: The central dispute may concern the definition of a "checkpoint rule." The complaint argues that Apache Spark's checkpointing is a passive data-persistence mechanism, not an active, logic-containing rule that "defines" future tasks and their execution method as required by the claim Compl. ¶¶45-46 The complaint references a code example from Spark's documentation to illustrate that checkpointing saves a dataset and recovering it restores that same dataset, suggesting an absence of the claimed rule-based execution logic Compl. p. 14 This raises the question of whether a mechanism that simply truncates a dependency lineage, thereby indirectly affecting future computation paths, can be considered a "rule governing execution."

'287 Patent Infringement Allegations

Claim Element (from Independent Claim 28)	Alleged Infringing Functionality	Complaint Citation	Patent Citation
display hardware configured to present an interactive interface that is supplied by the search service...	Plaintiff argues that Elasticsearch is a backend server/cluster software accessed via software APIs and does not supply or include any display hardware or a user-facing interactive interface.	¶61	col. 7:13-20
wherein the interactive interface is configured to iteratively collect input... and further configured to request and receive at least one first clarification... and further configured to, in response to receiving the first clarification, request and receive at least one second clarification...	Plaintiff argues that Elasticsearch provides API responses to direct queries and does not supply or drive the claimed multi-turn, iterative clarification dialog on client display hardware.	¶62	col. 7:32-40
...and "enters the criteria to one or more standard search engines"...	Plaintiff argues that Elasticsearch is itself a search engine and does not function as an intermediary that develops criteria and then enters them into other search engines like Google or Yahoo.	¶63	col. 7:13-45

• Identified Points of Contention:
  • Technical Questions: A primary technical question is whether Elasticsearch functions as the claimed "search service." The complaint, supported by a diagram, posits that Elasticsearch is a backend engine that is called by an application, rather than a service that supplies a "full conversational, iterative interface" to a user's device Compl. ¶61 Compl. p. 18, Fig. 1 The patent's own flowchart appears to depict the service as an intermediary that interacts with the user before accessing "standard search services" Compl. p. 20, Fig. 4
  • Scope Questions: The analysis may turn on whether the claim language "supplied by the search service" can be interpreted to mean "made possible by the service's APIs" or if it requires the service itself to provide the complete, client-side interface code. Furthermore, a question exists as to whether Elasticsearch, a standalone search engine, can be considered an intermediary that "enters the criteria to one or more standard search engines" as described in the patent's abstract and specification (Compl. ¶63; '287 Patent, abstract).

V. Key Claim Terms for Construction

• The Term: "checkpoint rule" (from '081 Patent, Claim 1)

• Context and Importance: This term is central to Plaintiff's non-infringement argument for the '081 patent. The case may turn on whether Apache Spark's checkpointing feature, which saves data to a file, can be construed as containing a "rule" that actively "defines" how future tasks are executed, or if it is merely a passive state-saving mechanism Compl. ¶¶44-46

• Intrinsic Evidence for Interpretation:

  • Evidence for a Broader Interpretation: The claim language states the rule "defines... the way in which the one or more tasks will execute" '081 Patent, cl. 1 An argument could be made that by truncating a dependency graph, Spark's checkpointing indirectly "defines" how future tasks will execute by changing their computational basis.
  • Evidence for a Narrower Interpretation: The specification describes a checkpoint as having "'intelligence' because the checkpoint includes and is associated with one or more rules that tell how the checkpoint 136 is to proceed" ('081 Patent, col. 12:18-22). It further states the rules "encapsulate[] the decision making necessary for selecting the next processor function" '081 Patent, col. 4:16-20, suggesting an active, logic-bearing component rather than a passive data snapshot.

• The Term: "interactive interface that is supplied by the search service" (from '287 Patent, Claim 28)

• Context and Importance: Plaintiff's non-infringement argument for the '287 patent hinges on this phrase. Practitioners may focus on this term because if the "search service" (accused Elasticsearch) is required to directly provide a complete user interface, then a backend, API-driven product would likely not infringe Compl. ¶¶60-61

• Intrinsic Evidence for Interpretation:

  • Evidence for a Broader Interpretation: The term "supplied by" is not explicitly defined. It could be argued that a service "supplies" an interface by providing the necessary API endpoints and data structures for a separate client application to construct and render it.
  • Evidence for a Narrower Interpretation: The specification describes the user being directed to "describe to the service the nature of the information desired" via an interface that "will typically be a text entry window" ('287 Patent, col. 7:13-19). It also contrasts the invention with a "standard search engine interactive page" '287 Patent, col. 7:9-12, suggesting the claimed service provides the complete interactive experience, not just the backend logic.

VI. Other Allegations

• Indirect Infringement: In each relevant count, the complaint seeks a declaration of no indirect infringement, asserting that because there is no direct infringement by the use of the accused software, there can be no secondary liability for inducement or contributory infringement Compl. ¶47 Compl. ¶64 Compl. ¶84 Compl. ¶101 Compl. ¶125

The complaint does not provide sufficient detail for analysis of Willful Infringement.

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

• A core issue will be one of definitional scope: can terms rooted in specific technical contexts be interpreted to cover modern, abstracted technologies? For instance, can a "checkpoint rule" ('081 patent), described as containing executable "intelligence," be construed to cover a data snapshot mechanism in Apache Spark that truncates a dependency graph? Similarly, does the term "computer-related hardware devices" ('124 patent) read on virtualized software containers like Kubernetes, particularly given the patentee's alleged disclaimers of software coverage during prosecution?

• Another central issue will be one of architectural mismatch: does the accused software's architecture align with the specific system structure required by the claims? For example, does Elasticsearch, a backend API-driven search engine, function as the claimed intermediary "search service" that "supplies" an iterative, conversational user interface ('287 patent)? Likewise, does the Kubernetes architecture, with its single "cloud provider api" per cluster, contain the "first gateway" and "second gateway" for separate clusters as claimed in the '584 patent?

• A key evidentiary question will concern the prosecution history of the '124 patent. The complaint alleges the patentee made clear and repeated disclaimers, distinguishing the claimed invention (managing physical hardware) from prior art (managing software updates) to secure the patent. The court will need to determine the scope and effect of these statements and whether they create an estoppel that bars the patent owner from now asserting its claims against virtualized software management systems like Kubernetes.