Robinhood Markets Inc v. Intellectual Ventures I LLC

I. Executive Summary and Procedural Information

• Parties & Counsel:
  • Plaintiff: Robinhood Markets, Inc. (Delaware)
  • Defendant: Intellectual Ventures I LLC, Intellectual Ventures II LLC, OL Security LLC, and Zarbana Digital Fund LLC (Delaware)
  • Plaintiff's Counsel: Duane Morris LLP
• Case Identification: 1:26-cv-00774, D. Del., 06/30/2026
• Venue Allegations: Venue is asserted as proper in the District of Delaware because each Defendant is a Delaware limited liability company and is therefore a resident of the district. The complaint also alleges Defendants have purposefully availed themselves of the forum by litigating prior actions involving the same patents in Delaware.
• Core Dispute: Plaintiff *Robinhood Markets Inc v. Intellectual Ventures I LLC* seeks a declaratory judgment that its use of common open-source software does not infringe, and that the claims are invalid, for six patents asserted by Defendants related to distributed computing and data processing.
• Technical Context: The technologies at issue involve foundational aspects of modern distributed and cloud computing, including resource management, task scheduling, data routing, and cluster organization, which are critical for operating large-scale online platforms.
• Key Procedural History: The complaint details extensive pre-suit licensing discussions initiated by Defendants (collectively, "Intellectual Ventures" or "IV") starting in late 2023. IV allegedly provided claim charts mapping the patents-in-suit to various open-source software packages used by Robinhood, made licensing demands, and set a deadline of June 30, 2026, after which its monetary demand would increase. The complaint also cites a history of IV asserting the same patents against other companies, creating the threat of imminent litigation that forms the basis for this declaratory judgment action.

Case Timeline

Date	Event
2004-12-30	'844 Patent Priority Date
2005-08-16	'894 Patent Priority Date
2005-12-06	'183 Patent Priority Date
2006-09-27	'081 Patent Priority Date
2007-10-30	'584 Patent Priority Date
2008-03-14	'287 Patent Priority Date
2010-02-23	'081 Patent Issue Date
2011-04-19	'287 Patent Issue Date
2012-12-11	'844 Patent Issue Date
2013-01-08	'584 Patent Issue Date
2013-01-01	Robinhood founded (approx.)
2017-06-20	'183 Patent Issue Date
2022-01-11	'894 Patent Re-issue Date
2023-12-14	IV initiates licensing discussions with Robinhood
2025-11-17	IV provides written correspondence and claim charts
2025-12-17	Videoconference between parties
2026-01-28	Videoconference between parties
2026-02-10	Videoconference between parties
2026-02-26	Substantive videoconference on infringement allegations
2026-03-10	Substantive videoconference on infringement allegations
2026-03-11	IV sends draft license agreement to Robinhood
2026-03-30	IV sends estimate of potential damages
2026-05-06	Call between parties
2026-05-14	Call between parties
2026-06-30	Complaint Filing Date

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

No probative visual evidence provided in complaint.

U.S. Reissued Patent No. RE48,894 - "Disaggregated Resources and Access Methods"

Reissued January 11, 2022 Compl. ¶12

The Invention Explained

• Problem Addressed: The patent describes the inefficiency of centralized computer resources, which can create performance bottlenecks and single points of failure, and notes the difficulty of managing distributed resources without a central controller, particularly regarding maintaining a consistent state (coherency) across the system '894 Patent, col. 2:1-20
• The Patented Solution: The invention proposes a system of independent "resource nodes" (e.g., storage, memory) that form a "disaggregated resource." Each node provides information about itself to "resource consumers" (applications or users). The consumers collect this information to build their own "map" of the entire resource, allowing them to access specific parts of the resource directly without a central manager. This map translates a logical resource request into a physical address on a specific node '894 Patent, abstract '894 Patent, Fig. 2
• Technical Importance: This architecture facilitates scalable and resilient distributed systems by decoupling logical resources from specific physical hardware, a foundational concept for modern cloud computing and infrastructure-as-a-service platforms '894 Patent, col. 2:1-9

Key Claims at a Glance

• The complaint identifies Claim 8 as an asserted claim Compl. ¶41
• Independent Claim 8, a method claim, includes the following primary steps:
  • receiving, at a resource consumer device, node names corresponding to each of a plurality of resource nodes;
  • determining, using the resource consumer device, an organizational structure of the plurality of resource nodes based on the received node names;
  • generating, using the resource consumer device, a resource map based at least in part on the organizational structure; and
  • messaging, by the resource consumer device, one or more resource nodes about a data set based at least in part on the resource map '894 Patent, col. 27:45-col. 28:54
• The complaint seeks a declaration of non-infringement for "any claim of the '894 Patent" Compl. ¶50

U.S. Patent No. 9,686,183 - "Digital Object Routing Based on a Service Request"

Issued June 20, 2017 Compl. ¶13

The Invention Explained

• Problem Addressed: Conventional network protocols like TCP/IP route data packets based primarily on a destination address, without considering the specific services available at intermediate network nodes or the unique requirements (e.g., Quality of Service) of the data being transmitted '183 Patent, col. 1:11-34
• The Patented Solution: The patent discloses a method where a "digital object" is routed through a network based on a "service request" specified in a separate "digital transmission form." A network device inspects this form, determines the requested service, and consults a routing table to forward the object to a downstream node capable of providing that service. This allows for dynamic, service-aware routing as nodes can update their availability '183 Patent, abstract '183 Patent, Fig. 4
• Technical Importance: This invention describes a form of content-aware or service-aware networking, enabling more intelligent data routing based on application-level requirements rather than just network addresses, a principle related to modern Software-Defined Networking (SDN).

Key Claims at a Glance

• The complaint identifies Claim 1 as an asserted claim Compl. ¶41
• Independent Claim 1, a method claim, includes the following primary steps:
  • receiving a digital transmission form from a source node, where the form is wholly separate from a corresponding digital object;
  • the digital transmission form specifies at least one requested service and a time of transmission;
  • determining availability of one or more nodes to provide the service;
  • receiving at least a portion of the digital object; and
  • transmitting the portion of the digital object to an available node '183 Patent, col. 25:5-30
• The complaint seeks a declaration of non-infringement for "any of the claims of the '183 Patent" Compl. ¶62

Multi-Patent Capsules

• U.S. Patent No. 7,669,081

  • Patent Identification: U.S. Patent No. 7,669,081, "Systems and Methods for Scheduling, Processing, and Monitoring Tasks," issued February 23, 2010 Compl. ¶14
  • Technology Synopsis: The patent describes a framework for managing and executing complex processes by breaking them into a series of tasks. The system uses "checkpoints" with associated rules to govern execution, save the state of a process, and enable recovery from failures, allowing for resilient, application-level task scheduling '081 Patent, abstract
  • Asserted Claims: Claim 1 Compl. ¶41
  • Accused Features: The complaint identifies Apache Spark as the accused open-source software, alleging it does not use checkpoints that capture machine state in the manner required by the claim Compl. ¶41 Compl. ¶74

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

  • Patent Identification: U.S. Patent No. 8,332,844, "Root Image Caching and Indexing for Block-Level Distributed Application Management," issued December 11, 2012 Compl. ¶15
  • Technology Synopsis: The patent relates to managing application environments in a distributed system at the block level. It uses a read-only "root image" as a common base and separate "leaf images" to store node-specific modifications. The system also includes caching frequently accessed blocks from the root image to improve performance '844 Patent, abstract
  • Asserted Claims: Claim 7 Compl. ¶41
  • Accused Features: The complaint identifies Docker as the accused open-source software, arguing its layered architecture is different from the claimed "root image" and "leaf image" stored on separate units Compl. ¶41 Compl. ¶85

• U.S. Patent No. 7,930,287

  • Patent Identification: U.S. Patent No. 7,930,287, "Systems and Methods for Compound Searching," issued April 19, 2011 Compl. ¶16
  • Technology Synopsis: The technology describes a search service that acts as an intermediary for standard search engines. It engages in an iterative, interactive dialogue with a user to determine the "purpose" of a search, develops refined search criteria, and then collects and processes the results from other search engines on the user's behalf '287 Patent, abstract
  • Asserted Claims: Claim 28 Compl. ¶41
  • Accused Features: The complaint identifies Elasticsearch as the accused open-source software, arguing it receives queries and returns results, but does not "request and receive" clarifications as required by the claim Compl. ¶41 Compl. ¶96

• U.S. Patent No. 8,352,584

  • Patent Identification: U.S. Patent No. 8,352,584, "System for Hosting Customized Computing Clusters," issued January 8, 2013 Compl. ¶17
  • Technology Synopsis: The patent discloses a system for hosting multiple, customized computing clusters for different clients. Each cluster is isolated from the others and connected to a private company network via a gateway, with client access controlled by a firewall. The system includes a central monitoring system to oversee the clusters '584 Patent, abstract
  • Asserted Claims: Claim 1 Compl. ¶41
  • Accused Features: The complaint identifies Kubernetes as the accused open-source software, arguing its use of a multi-cluster network communicating over the Internet does not meet the claim requirement of a "private communication network" Compl. ¶41 Compl. ¶107

III. The Accused Instrumentality

Product Identification

The accused instrumentalities are several widely-used open-source software platforms: Apache Kafka, Apache Airflow, Apache Spark, Elasticsearch, Docker, and Kubernetes (collectively, "Open Source Software") Compl. ¶11

Functionality and Market Context

Robinhood alleges that IV's infringement accusations are based on Robinhood's use of this Open Source Software to build and operate its digital infrastructure for its financial services platform Compl. ¶21 Compl. ¶34 The complaint notes that these software tools are often freely licensed to the public to encourage collaboration and interoperability Compl. ¶33 IV's allegations are reportedly based on evidence such as public job postings by Robinhood that indicate its use of these technologies Compl. ¶22

IV. Analysis of Infringement Allegations

RE48,894 Infringement Allegations

Claim Element (from Independent Claim 8)	Alleged Infringing Functionality	Complaint Citation	Patent Citation
receiving, at a resource consumer device, node names corresponding to each of a plurality of resource nodes	The complaint alleges that the accused software (Apache Kafka) receives a "bootstrap server list of addresses," which it contends are not "node names" and are specifically disclaimed by the patent.	¶52	col. 27:46-48
determining, using the resource consumer device, an organizational structure of the plurality of resource nodes based on the received node names	The complaint does not provide sufficient detail for analysis of this element.	¶51	col. 27:49-52
generating, using the resource consumer device, a resource map based at least in part on the organizational structure	The complaint does not provide sufficient detail for analysis of this element.	¶51	col. 27:53-56
messaging, by the resource consumer device, one or more resource nodes of the plurality of resource nodes about the data set based at least in part on the resource map	The complaint does not provide sufficient detail for analysis of this element.	¶51	col. 27:57-62

• Identified Points of Contention:
  • Scope Questions: A central dispute will be the construction of the term "node names." Robinhood alleges that the "bootstrap server list of addresses" used in Apache Kafka is not equivalent to "node names" and is, in fact, "specifically disclaimed" by the patent Compl. ¶52 This raises the question of whether a list of server hostnames or IP addresses falls within the scope of the claimed "node names," which the patent specification suggests may be a more structured, logical identifier conveying group and role information '894 Patent, col. 13:21-35 '894 Patent, col. 14:26-44
  • Technical Questions: Beyond the "node names" dispute, a key factual question will be whether the processes by which an Apache Kafka client discovers and interacts with brokers in a cluster perform the specific functions of determining an "organizational structure" and generating a "resource map" as recited in the claim.

9,686,183 Infringement Allegations

Claim Element (from Independent Claim 1)	Alleged Infringing Functionality	Complaint Citation	Patent Citation
receiving a digital transmission form from a source node, wherein said receiving is performed by a network device within a network...	The complaint alleges that the accused software (Apache Airflow) uses a "Directed Acyclic Graph" to describe task order, which it argues does not correspond to the claimed "digital transmission form."	¶63	col. 25:5-9
wherein the digital transmission form is wholly separate from the digital object	The complaint implies a mismatch by stating Airflow's graph describes task order for workflow orchestration, rather than being a separate form for forwarding a distinct digital object.	¶63	col. 25:8-9
wherein the digital transmission form specifies at least one requested service to be performed in transmitting the digital object... and wherein the at least one requested service specifies information relating to a time of transmission	The complaint does not provide sufficient detail for analysis of this element.	¶62	col. 25:10-15

• Identified Points of Contention:
  • Scope Questions: A primary issue is whether an Apache Airflow "Directed Acyclic Graph" (DAG), which defines a computational workflow, can be construed as a "digital transmission form" that is "wholly separate from the digital object" as required by Claim 1. Robinhood argues it cannot, suggesting a fundamental categorical difference between a workflow definition and a data routing instruction form Compl. ¶63
  • Technical Questions: The dispute raises the question of whether orchestrating a sequence of computational tasks in Airflow is technically equivalent to the patent's described method of "transmitting" a "digital object" from a "source node to a destination node" through a network Compl. ¶63 This suggests a potential mismatch between the application-level workflow management of the accused product and the network-level data routing described in the patent.

V. Key Claim Terms for Construction

For the '894 Patent

• The Term: "node names" (Claim 8)
• Context and Importance: Robinhood's primary non-infringement argument for this patent is that Apache Kafka uses a "list of addresses," which it contends are not "node names" Compl. ¶52 The definition of this term is therefore critical to determining if the accused software meets this limitation.
• Intrinsic Evidence for Interpretation:
  • Evidence for a Broader Interpretation: The specification describes "Resource node names" as logical identifiers that "resource consumers can resolve... to an address," which could support an interpretation where any resolvable identifier, including a hostname in a server list, qualifies '894 Patent, col. 13:21-35
  • Evidence for a Narrower Interpretation: The patent provides examples of structured node names (e.g., "Z.M1.R1") that convey hierarchical and role information about the node's place in the disaggregated resource '894 Patent, col. 14:26-44 '894 Patent, Table 1 IV may argue this structured, informational quality is a required characteristic of "node names," and Robinhood's position is that the simple "bootstrap server list of addresses" lacks this quality and was "specifically disclaimed" Compl. ¶52

For the '183 Patent

• The Term: "digital transmission form" (Claim 1)
• Context and Importance: Robinhood alleges that the "Directed Acyclic Graph" (DAG) used by Apache Airflow for workflow orchestration does not meet the definition of a "digital transmission form" for routing a separate "digital object" Compl. ¶63 The construction will determine if an application-level workflow script falls within the scope of a term used in the context of network data routing.
• Intrinsic Evidence for Interpretation:
  • Evidence for a Broader Interpretation: IV could argue that the term should be read broadly to encompass any digital instructions that govern the processing or movement of other data, as the abstract links routing to a "service request," which could be interpreted as a task in a workflow '183 Patent, abstract
  • Evidence for a Narrower Interpretation: The patent's detailed description and background consistently frame the invention in the context of routing a "digital object" (a payload) through a network of intermediary nodes like ISPs, based on the separate "form" '183 Patent, col. 1:11-23 '183 Patent, col. 13:23-34 This supports an interpretation limited to network data forwarding, as opposed to the application-level task execution management performed by Airflow. The claim's requirement that the form be "wholly separate" from the object may also support a narrower construction '183 Patent, col. 25:8-9

VI. Other Allegations

Indirect Infringement

The complaint seeks a declaratory judgment of non-infringement under any theory, including indirect infringement (contributory or by inducement) Compl. ¶51 Compl. ¶62 It does not, however, allege specific facts related to inducement, as its purpose is to deny such liability.

Willful Infringement

Willfulness is not formally alleged, as this is a declaratory judgment action filed by the accused infringer. However, the complaint establishes a basis for what would be a willfulness claim by IV if it were to file counterclaims. The complaint details extensive pre-suit communications, including IV providing claim charts and analysis in 2025 and 2026, which establishes pre-suit knowledge of the patents and the infringement allegations Compl. ¶¶38-41

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

1. Technical Mismatch vs. Claim Scope: A central issue for the court will be whether the high-level, application-layer open-source software used by Robinhood operates in a manner that falls within the scope of patents that often describe lower-level networking, hardware, and resource management functions. This raises a recurring question of functional equivalence: does a software workflow orchestrator (Apache Airflow) perform the same method as a network data router ('183 patent), and does a software containerization platform (Docker) use the same architecture as a block-level storage system ('844 patent)?

2. Patent Validity in the Face of Open-Source Art: Robinhood repeatedly argues that the patented technologies are directed to abstract ideas or conventional concepts that were well-understood and predated by systems like Google MapReduce, Hadoop, and Apache Oozie Compl. ¶58 Compl. ¶69 Compl. ¶80 Compl. ¶102 A key question will be one of patentability: can the claims of the asserted patents withstand challenges under 35 U.S.C. §§ 101, 102, and 103, especially when the accused "infringing" technologies are themselves widely adopted, foundational open-source projects that may be considered part of the state of the art?