2:25-cv-02956
First Horizon Bank v. Intellectual Ventures Management LLC
I. Executive Summary and Procedural Information
- Parties & Counsel:
- Plaintiff: First Horizon Bank (Tennessee)
- Defendant: Intellectual Ventures Management, LLC, Intellectual Ventures I LLC, Intellectual Ventures II LLC, Callahan Cellular L.L.C., OL Security Limited Liability Company, Invention Investment Fund I, L.P., and Invention Investment Fund II, LLC (collectively "Defendants") (Primarily Washington and Delaware)
- Plaintiff’s Counsel: Baker, Donelson, Bearman, Caldwell & Berkowitz, P.C.
- Case Identification: 2:25-cv-02956, W.D. Tenn., 02/12/2026
- Venue Allegations: Plaintiff alleges venue is proper in the Western District of Tennessee because a substantial part of the events giving rise to the claims occurred in the district, where Defendants directed business, licensing, and enforcement activities.
- Core Dispute: Plaintiff seeks a declaratory judgment that its banking and financial services do not infringe eight patents owned or managed by Defendants and that the asserted claims of those patents are invalid.
- Technical Context: The patents-in-suit relate to foundational technologies in computer networking, secure transactions, and distributed systems, which are integral to modern cloud computing, data processing, and financial technology infrastructure.
- Key Procedural History: The complaint details a history of licensing negotiations between the parties beginning as early as 2014. It also notes that inter partes review (IPR) proceedings were filed against U.S. Patent Nos. 7,949,785, 8,332,844, and 8,407,722, but were terminated due to settlement before a substantive decision by the Patent Trial and Appeal Board. Additionally, an ex parte reexamination for the '844 Patent and a reissue proceeding for the RE48,894 Patent are mentioned as ongoing.
Case Timeline
| Date | Event |
|---|---|
| 2000-12-18 | Priority Date for U.S. Patent No. 8,407,722 |
| 2003-03-31 | Priority Date for U.S. Patent No. 7,949,785 |
| 2003-05-22 | Priority Date for U.S. Patent No. 9,678,967 |
| 2004-06-15 | Priority Date for U.S. Patent No. 7,464,862 |
| 2004-06-16 | Priority Date for U.S. Patent No. 10,567,391 |
| 2004-12-20 | Priority Date for U.S. Patent No. 8,332,844 |
| 2005-08-16 | Priority Date for U.S. Patent No. RE48,894 |
| 2007-10-30 | Priority Date for U.S. Patent No. 8,352,584 |
| 2008-12-16 | Issue Date for U.S. Patent No. 7,464,862 |
| 2011-05-24 | Issue Date for U.S. Patent No. 7,949,785 |
| 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 |
| 2013-03-26 | Issue Date for U.S. Patent No. 8,407,722 |
| 2017-06-13 | Issue Date for U.S. Patent No. 9,678,967 |
| 2020-02-18 | Issue Date for U.S. Patent No. 10,567,391 |
| 2022-01-11 | Issue Date for U.S. Patent No. RE48,894 |
| 2025-04-30 | Unified Patents files Ex Parte Reexamination request for '844 Patent |
| 2025-07-22 | USPTO grants Ex Parte Reexamination request for '844 Patent |
| 2026-02-12 | Complaint Filing Date |
II. Technology and Patent(s)-in-Suit Analysis
U.S. Patent No. 7,949,785 - "SECURE VIRTUAL COMMUNITY NETWORK SYSTEM"
The Invention Explained
- Problem Addressed: The patent's background describes the difficulty of enabling secure, direct communication between devices that may be on different private networks, behind firewalls, or using dynamic IP addresses, a common challenge in the expanding Internet ('785 Patent, col. 2:25-54).
- The Patented Solution: The invention proposes a "private virtual dynamic network" that acts as a private LAN, allowing devices to join and communicate as if they were on the same local network '785 Patent, col. 1:57-61 A central "virtual network manager" registers devices, assigns them virtual network addresses, and uses a "route director" to facilitate communication, translating between public, private, and virtual addresses to bypass NAT devices and firewalls '785 Patent, col. 10:10-24 '785 Patent, abstract
- Technical Importance: This technology addresses a foundational problem of network address translation (NAT) traversal and secure peer-to-peer connectivity, which is critical for creating virtual private networks (VPNs) and other forms of secure, direct communication over the public internet '785 Patent, col. 2:5-9
Key Claims at a Glance
- The complaint identifies independent claim 30 as asserted Compl. ¶ 196 Compl. ¶ 214
- The essential elements of independent claim 30 are:
- A virtual network manager, comprising:
- A network interface for data communication via a virtual network defined by a domain name with an associated public network address;
- A memory and a processor implementing 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; and
- A DNS server for the virtual network configured to receive a DNS request from a first device and return network addresses associated with a second device (including a route director address, a private network address, and a virtual network address).
- The complaint also references independent claims 1, 38, 48, 62, and 75 in its non-infringement arguments Compl. ¶ 198
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 background describes inefficiencies in clustered computing, where multiple "compute nodes" (servers) are booted from a master software image '844 Patent, col. 1:40-48 Creating a full copy of the image for each node is slow, and pre-creating clones wastes disk space '844 Patent, col. 1:53-64
- The Patented Solution: The invention proposes a system using a shared, read-only "root image" and individual, writable "leaf images" for each compute node '844 Patent, abstract A leaf image stores only the changes (the delta) made by a node relative to the root image '844 Patent, col. 2:18-22 This allows for rapid deployment of new compute nodes without copying the entire root image. The system also includes caching frequently accessed blocks from the root image to further improve performance '844 Patent, abstract
- Technical Importance: This "copy-on-write" approach at the block level is a fundamental technique for efficiently managing virtual machine and container environments, significantly reducing storage overhead and deployment time in large-scale, distributed systems '844 Patent, col. 2:50-54
Key Claims at a Glance
- The complaint identifies independent claim 7 as asserted Compl. ¶ 278 Compl. ¶ 292
- The essential elements of independent claim 7 are:
- 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, where the leaf images include only additional data blocks not previously contained in the root image and changes made to the blocks of the root image, and do not include unchanged blocks; and
- caching blocks of said root image that have been accessed by at least one compute node in a cache memory.
- The complaint also references independent claims 1, 14, 19, and 23 in its non-infringement arguments Compl. ¶ 280
Multi-Patent Capsule
Patent Identification: U.S. Patent No. 8,407,722, "ASYNCHRONOUS MESSAGING USING A NODE SPECIALIZATION ARCHITECTURE IN THE DYNAMIC ROUTING NETWORK," issued March 26, 2013.
Technology Synopsis: The patent describes a network that routes update messages for "live objects" from input sources to clients Compl. ¶¶ 354-355 The system is designed to provide real-time, dynamically-updateable objects to client devices over a network ('722 Patent, col. 5:27-31).
Asserted Claims: Independent claim 14 Compl. ¶ 352
Accused Features: Defendants allege infringement by First Horizon's use of "Kafka" Compl. ¶ 352 The complaint argues that Kafka sends data as "events" or "records," which are not the "real-time dynamically-updateable objects" required by the claim Compl. ¶ 357
Patent Identification: U.S. Patent No. 10,567,391, "GRADUATED AUTHENTICATION IN AN IDENTITY MANAGEMENT SYSTEM," issued February 18, 2020.
Technology Synopsis: The patent relates to an identity management system that utilizes different levels of authentication security based on the type of transaction being performed ('391 Patent, abstract). The system can select a specific "transaction mechanism" based on the "transaction security level" required '391 Patent, claim 18
Asserted Claims: Independent claim 18 Compl. ¶ 424
Accused Features: Defendants allege infringement by First Horizon's "Secure Payment Processing" services, specifically the Clover® platform using the 3-D Secure protocol Compl. ¶ 424 The complaint argues that this system provides multiple authentication methods for a single transaction, whereas the patent claims require receiving information about "a first type of transaction" and "a second type of transaction" that is different from the first Compl. ¶¶ 426-429
Patent Identification: U.S. Patent No. 7,464,862, "APPARATUS & METHOD FOR POS PROCESSING," issued December 16, 2008.
Technology Synopsis: The invention is an apparatus, such as a removable flash memory device, that extends the capability of a Point-of-Sale (POS) device ('862 Patent, fig. 1). The apparatus includes a software application stored in non-volatile memory that can function as a "key" to unlock the POS device when connected and lock it when disconnected '862 Patent, claim 1
Asserted Claims: Independent claim 1 Compl. ¶ 512
Accused Features: Defendants allege infringement by First Horizon's use of "Point-of-Sale Systems," specifically the Clover® platform Compl. ¶ 512 The complaint argues the accused Clover devices do not include the claimed "portable housing" containing a software application that functions as a lock/unlock key Compl. ¶ 515
Patent Identification: U.S. Patent No. 8,352,584, "SYSTEM FOR HOSTING CUSTOMIZED COMPUTING CLUSTERS," issued January 8, 2013.
Technology Synopsis: The patent describes a computer system with multiple computing clusters linked to a private communications network. The system includes separate gateways for each cluster to isolate communications between them ('584 Patent, claim 1).
Asserted Claims: Independent claim 1 Compl. ¶ 592
Accused Features: Defendants allege infringement by First Horizon's use of Kubernetes Compl. ¶ 592 The complaint alleges that Kubernetes architecture does not include the claimed structure of a "first gateway communicatively linked between a first cluster and a private communications network, and a second gateway communicatively linked between a second cluster and the private communications network" Compl. ¶¶ 594-595
Patent Identification: U.S. Patent No. 9,678,967, "INFORMATION SOURCE AGENT SYSTEMS AND METHODS FOR DISTRIBUTED DATA STORAGE AND MANAGEMENT USING CONTENT SIGNATURES," issued June 13, 2017.
Technology Synopsis: The patent describes a method for deleting files across a network. The method involves generating a "content signature" (e.g., a hash) for a file to be deleted, identifying other devices on the network that have files with an identical signature, and transmitting a delete instruction to those devices ('967 Patent, claim 1).
Asserted Claims: Independent claim 1 Compl. ¶ 668
Accused Features: Defendants allege infringement by First Horizon's use of Hadoop Compl. ¶ 668 The complaint makes the factual assertion that First Horizon "does not make, use, offer for sell, or sell the Hadoop product, and further does not deploy Hadoop's framework in any First Horizon product or system" Compl. ¶ 670
Patent Identification: U.S. Patent No. RE48,894, "DISAGGREGATED RESOURCES AND ACCESS METHODS," issued January 11, 2022.
Technology Synopsis: This patent describes a method for a "resource consumer device" to interact with a "plurality of resource nodes." The method involves determining an "organizational structure" of the resource nodes based on received node names and then messaging those nodes based on that structure ('894 Patent, claim 8).
Asserted Claims: Claim 15 (dependent on independent claim 8) Compl. ¶ 735
Accused Features: Defendants allege infringement by First Horizon's use of Kafka Compl. ¶ 735 The complaint alleges that Kafka does not perform the claimed step of determining "an organizational structure of the plurality of resource nodes based on the received node names" Compl. ¶ 737
III. The Accused Instrumentality
- Product Identification: The instrumentalities are not First Horizon products but rather third-party, primarily open-source, software platforms that Defendants allege First Horizon uses in an infringing manner Compl. ¶¶ 142-143 Compl. ¶¶ 165-166 These include:
- Kubernetes: An open-source platform for managing containerized applications and services Compl. ¶ 200
- Docker: A platform for developing, shipping, and running applications in containers Compl. ¶ 282
- Kafka: A distributed event streaming platform used for data pipelines and streaming analytics Compl. ¶ 357
- Hadoop: A framework for distributed processing of large data sets across clusters of computers Compl. ¶ 670
- Clover® with 3-D Secure: A point-of-sale hardware and software platform, specifically in its use of the 3-D Secure protocol for authenticating online card transactions Compl. ¶ 424
- Functionality and Market Context:
- The complaint describes Kubernetes, Docker, Kafka, and Hadoop as foundational technologies for modern cloud computing, data processing, and microservices architecture, widely used across the technology and financial services industries Compl. ¶ 126
- First Horizon's defense relies on technical documentation from the official websites for these platforms to argue that their actual operation does not align with the specific requirements of the patent claims Compl. ¶ 200 Compl. ¶ 282 Compl. ¶ 357 The complaint includes a diagram from a Docker documentation website illustrating how a container is constructed from multiple read-only image layers and a top writable layer Compl. ¶ 284
- Clover® is identified as a third-party branded point-of-sale system Compl. ¶ 512 The 3-D Secure protocol is described as a security layer for online credit and debit card transactions, which can approve transactions without cardholder interaction or require additional authentication if risk is high Compl. ¶ 427
IV. Analysis of Infringement Allegations
U.S. Patent No. 7,949,785 Infringement Allegations
| Claim Element (from Independent Claim 30) | Plaintiff's Alleged Non-Infringing Functionality (re: Kubernetes) | Complaint Citation | Patent Citation |
|---|---|---|---|
| a virtual network manager, comprising: ... a register module configured to register devices in a virtual network... | The complaint alleges that the accused Kubernetes system registers "Pods," which are described as the smallest deployable units of computing in Kubernetes, not "devices" Compl. ¶¶ 203-205 A diagram from the Kubernetes website illustrates the architecture of traditional, virtualized, and container deployments Compl. ¶ 200, p. 61 | ¶¶205-207 | col. 30:17-19 |
| a DNS server for the virtual network, the DNS server configured to receive a DNS request from a first device in the virtual network... | The complaint argues that since Kubernetes does not register "devices," it consequently does not have a DNS server configured to handle DNS requests from such claimed "devices" within the virtual network Compl. ¶ 207 | ¶207 | col. 30:26-29 |
| and return a network address associated with a network route director, a private network address associated with a second device... | Because the prerequisite of registering "devices" is allegedly not met, the subsequent function of returning addresses associated with a "second device" is also not performed as claimed (Compl. ¶¶ 199, 207). | ¶¶199, 207 | col. 30:29-32 |
- Identified Points of Contention:
- Scope Questions: The central dispute may turn on the construction of the term "device." The complaint raises the question of whether a "Pod" in Kubernetes—a logical construct comprising one or more application containers—can be considered a "device" as understood in the context of the '785 Patent, which was filed in 2003 Compl. ¶ 206
- Technical Questions: An evidentiary question may be how DNS and service discovery actually function within a Kubernetes cluster and whether that functionality meets the claim requirement of a DNS server that returns a specific combination of route director, private, and virtual network addresses for a registered "device" Compl. ¶ 204
U.S. Patent No. 8,332,844 Infringement Allegations
| Claim Element (from Independent Claim 7) | Plaintiff's Alleged Non-Infringing Functionality (re: Docker) | 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... | The complaint alleges that a Docker "container" is not a "leaf image" as claimed because it includes both read-only "image layers" (analogous to the root image) and a writable "container layer," rather than containing only the changes or additional blocks Compl. ¶¶ 284-285 | ¶¶284-286 | col. 14:14-19 |
| wherein said leaf images of respective compute nodes do not include blocks of said root image that are unchanged by respective compute nodes... | Citing a diagram from Docker's technical documentation, the complaint alleges that a Docker container inherently includes the underlying, unchanged image layers and is not limited to only the delta, thereby failing to meet this negative limitation Compl. ¶ 284 A diagram from the Docker website illustrates the layered structure of a container Compl. ¶ 284, p. 86 | ¶285 | col. 14:19-22 |
- Identified Points of Contention:
- Scope Questions: The infringement analysis may hinge on the construction of "leaf image," particularly the limiting term "only." The court will need to determine if this term strictly excludes any part of the original "root image" from the "leaf image," as the complaint argues Compl. ¶ 280
- Technical Questions: A key factual question will be whether the technical operation of Docker's layered filesystem, where a container is an aggregation of a writable layer on top of multiple read-only layers, is functionally equivalent to the claimed "leaf image" structure, or if there is a fundamental operational difference.
V. Key Claim Terms for Construction
For U.S. Patent No. 7,949,785:
- The Term: "device"
- Context and Importance: This term is critical because First Horizon's non-infringement defense is premised on the argument that the accused Kubernetes "Pods" are not "devices" Compl. ¶ 206 The construction of this term will determine whether the foundational element of the asserted claims reads on the accused system's architecture.
- Intrinsic Evidence for Interpretation:
- Evidence for a Broader Interpretation: The claims themselves refer to "devices" being registered, and the specification discusses "computing devices" generally, which could support a broad interpretation that includes any logical or physical computing entity '785 Patent, col. 1:58
- Evidence for a Narrower Interpretation: The specification often refers to "machines," "servers," and "computing devices" in the context of distinct hardware entities on a network '785 Patent, col. 9:41-45 This might support an argument that a "device" implies a physical or virtual machine, rather than a more abstract software construct like a "Pod."
For U.S. Patent No. 8,332,844:
- The Term: "leaf images including only additional data blocks not previously contained in said root image and changes made... to the blocks of the root image"
- Context and Importance: The word "only" is central to the non-infringement argument. First Horizon alleges that a Docker container includes both the original layers and the new writable layer, and thus does not contain "only" the changes Compl. ¶ 285 The interpretation of this limitation will likely be dispositive for the '844 patent.
- Intrinsic Evidence for Interpretation:
- Evidence for a Broader Interpretation: A defendant might argue that "including only" should be interpreted functionally, meaning the leaf image's purpose is to store the delta, even if its technical implementation involves pointers or references back to the original root image blocks. The patent's abstract describes leaf images as storing "changes made by respective compute nodes," which focuses on the function rather than strict exclusion. '844 Patent, abstract
- Evidence for a Narrower Interpretation: The plain language of the claim, "including only," suggests strict exclusion. The specification describes the leaf image as containing "blocks of new data, blocks of changed data, or other blocks of data unique to the individual compute node," which supports the idea that it is a separate entity containing just the differences '844 Patent, col. 5:40-44
VI. Other Allegations
- Indirect Infringement: Defendants have accused First Horizon of both direct and indirect infringement Compl. ¶ 143 Compl. ¶ 167 The complaint does not provide the specific factual basis for Defendants' indirect infringement allegations beyond asserting that First Horizon "encourages its customers and partners to make, use, sell, offer to sell and/or import" the accused technologies (Compl. ¶ 142).
- Willful Infringement: The complaint does not explicitly mention willfulness, but it references Defendants' accusation of "Efficient infringement" Compl. ¶ 193 This term implies a deliberate choice to infringe rather than license, which is a common predicate for a willfulness allegation. The long history of communication and licensing offers detailed in the complaint, starting from 2014, could be used by Defendants to establish pre-suit knowledge Compl. ¶¶ 85-91 Compl. ¶¶ 123-141
VII. Analyst’s Conclusion: Key Questions for the Case
This declaratory judgment action will likely focus on whether modern, widely-adopted open-source software platforms fall within the scope of patent claims filed years before these platforms became ubiquitous. The central questions for the court appear to be:
- A core issue will be one of definitional scope and technological evolution: Can the term "device," as used in a 2003-filed patent ('785 Patent), be construed to cover modern software abstractions like a Kubernetes "Pod"? Similarly, does the "leaf image" structure claimed in the '844 Patent, which requires storing "only" changes, read on the layered filesystem architecture of Docker containers?
- A second key question will be one of factual and technical mapping: Beyond claim construction, the case will require a detailed technical comparison. For example, does the 3-D Secure protocol as used by Clover® actually involve two different types of transactions as required by the '391 Patent, or is it a multi-step authentication process for a single transaction?
- A final procedural question may arise from the complaint's extensive narrative regarding licensing history and litigation threats Compl. ¶¶ 84-188 While this establishes the basis for declaratory judgment jurisdiction, it also frames the dispute as one involving a large-scale licensing campaign, which could influence case management and settlement dynamics.