DCT
4:26-cv-00348
Gaea LLC v. Meta Platforms Inc
Key Events
Complaint
Table of Contents
complaint Intelligence
I. Executive Summary and Procedural Information
- Parties & Counsel:
- Plaintiff: Gaea, LLC (Colorado)
- Defendant: Meta Platforms, Inc. (Delaware)
- Plaintiff's Counsel: Folio Law Group PLLC; Cherry Johnson Siegmund James, PLLC
- Case Identification: 4:26-cv-00348, N.D. Tex., 03/23/2026
- Venue Allegations: Plaintiff alleges venue is proper in the Northern District of Texas because Defendant Meta Platforms, Inc. maintains a regular and established place of business in the district, specifically its Fort Worth data-center campus, and has allegedly committed acts of infringement there.
- Core Dispute: Plaintiff alleges that Defendant's data center infrastructure, which uses the proprietary "CacheLib" caching software, infringes four patents related to configurable, policy-based data storage device behavior.
- Technical Context: The technology concerns methods and apparatuses for allowing a host system to define policies that control how a storage device, such as a solid-state drive (SSD), internally manages the writing and reading of data, which is significant for optimizing performance and efficiency in large-scale data centers.
- Key Procedural History: The complaint does not mention any prior litigation, Inter Partes Review (IPR) proceedings, or licensing history related to the patents-in-suit.
Case Timeline
| Date | Event |
|---|---|
| 2016-11-07 | Earliest Priority Date for all Patents-in-Suit |
| 2020-09-15 | U.S. Patent No. 10,776,023 Issued |
| 2021-09-02 | Date of Meta engineering blog post on CacheLib |
| 2022-05-10 | U.S. Patent No. 11,327,669 Issued |
| 2024-02-20 | U.S. Patent No. 11,907,553 Issued |
| 2025-04-01 | U.S. Patent No. 12,265,715 Issued |
| 2026-03-23 | Complaint Filed |
II. Technology and Patent(s)-in-Suit Analysis
U.S. Patent No. 10,776,023 - "Data Storage Device with Configurable Policy-Based Storage Device Behavior"
The Invention Explained
- Problem Addressed: The patent's background describes that conventional data storage devices provide "only extremely minimal configuration of read/write policies," preventing users from directing the internal read/write process to optimize for specific needs (e.g., reliability versus storage volume) '023 Patent, col. 3:26-29
- The Patented Solution: The invention is a storage apparatus where a "device controller" receives a "storage device policy" from an external host. This policy dictates the recording method for storing content. The controller then stores the content on the storage media according to this policy, records associated metadata such as a content identifier, and later uses that information to retrieve the content upon request. This architecture moves storage management intelligence from the host to the device itself, but under the host's policy-based direction '023 Patent, abstract '023 Patent, col. 3:4-15 '023 Patent, Fig. 8B
- Technical Importance: This approach allows application-level software to customize the low-level behavior of a storage device, enabling fine-tuned performance optimizations for different data types and priorities within large, complex systems like cloud storage arrays '023 Patent, col. 7:13-8:24
Key Claims at a Glance
- The complaint asserts at least independent claim 1 Compl. ¶18
- Claim 1 of the '023 Patent recites the following essential elements for an apparatus:
- A storage media.
- A device controller operatively coupled with the storage media.
- The device controller is configured to:
- receive, from a host, at least one storage device policy indicating a recording method.
- receive a storage request from the host to store content.
- store the content on the storage media using the indicated recording method.
- record storage information for the content (including a content identifier) on a memory of the device controller.
- subsequently, receive a content request comprising the content identifier.
- in response, retrieve the storage information from the controller's memory.
- recover the content from the storage media according to the storage information.
- respond to the request by returning the content to the host.
- The complaint does not explicitly reserve the right to assert dependent claims but refers to "one or more claims" Compl. ¶18
U.S. Patent No. 11,327,669 - "Data Storage Device with Configurable Policy-Based Storage Device Behavior"
The Invention Explained
- Problem Addressed: Similar to the '023 Patent, the technology addresses the lack of user-configurable control over the internal read/write processes within conventional storage devices '669 Patent, col. 3:26-29
- The Patented Solution: The '669 Patent claims an apparatus where the device controller has a memory storing an "application." This application contains instructions that, when executed, direct the device controller to perform the policy-based storage and retrieval steps: receiving a policy, receiving a content request, storing the content according to the policy, recording metadata, and later retrieving the content. This framing emphasizes the software- or firmware-driven nature of the configurable behavior within the device controller '669 Patent, abstract '669 Patent, claim 1
- Technical Importance: By defining the configurable logic as an "application" on the device controller, the invention reinforces the concept of a "smart" storage device whose behavior can be programmed and updated to meet evolving application needs '669 Patent, col. 11:2-12:54
Key Claims at a Glance
- The complaint asserts at least independent claim 1 Compl. ¶37
- Claim 1 of the '669 Patent recites the following essential elements for an apparatus:
- A storage device.
- A device controller operatively coupled with the storage device, comprising a memory.
- An application stored on the memory comprising instructions that, when executed, direct the device controller to at least:
- receive a storage device policy.
- receive a storage request, comprising content.
- store the content on the storage device according to the policy.
- record storage information for the content on the memory, comprising a content identifier.
- subsequently, receive a content request comprising the content identifier.
- in response, retrieve the storage information.
- recover the content, at least in part, according to the storage information.
- respond to the content request by returning the content.
- The complaint refers to "one or more claims" but focuses its allegations on claim 1 Compl. ¶37
U.S. Patent No. 11,907,553 - "Data Storage Device with Configurable Policy-Based Storage Device Behavior"
- Technology Synopsis: This patent claims an apparatus with a distinct architecture comprising a "programmable processor" coupled to a "device memory" and a separate "device controller" coupled to the solid-state memory. The application runs on the programmable processor to process content based on a policy and then transfers the processed content to the device controller for storage, creating a two-stage system '553 Patent, claim 9 Compl. ¶16
- Asserted Claims: Independent claim 9 Compl. ¶57
- Accused Features: The complaint alleges that Meta's SSDs, which use a controller Integrated Circuit (IC) containing a processor, memory, and an I/O block (device controller), meet the elements of this claim structure Compl. ¶59
U.S. Patent No. 12,265,715 - "Data Storage Device with Configurable Policy-Based Storage Device Behavior"
- Technology Synopsis: This patent claims a method of operating a solid-state drive. The method includes processing content based on a storage policy, storing it, and then, in response to a read request, reading the content and processing it again for transfer based on the same policy. This covers a full, policy-driven read-write lifecycle '715 Patent, claim 11 Compl. ¶17
- Asserted Claims: Independent claim 11 Compl. ¶76
- Accused Features: The complaint alleges that the operation of Meta's CacheLib-based infrastructure, including receiving store requests, processing content per policy, storing it, and later processing read requests based on the same policy, infringes this method claim Compl. ¶78
III. The Accused Instrumentality
Product Identification
The accused instrumentalities are Meta's "CacheLib-based storage and caching apparatuses," specifically identified as "all software services running on a host server that use the CacheLib C++ library" Compl. ¶8 Compl. ¶18 This includes the "CacheLib HybridCache" component and the Solid State Drives (SSDs) it utilizes Compl. ¶21
Functionality and Market Context
- CacheLib is described as a "proprietary, general-purpose caching and storage engine" used in over 70 internal Meta services, including its Content Delivery Network (CDN) and social-graph cache Compl. ¶13 Compl. ¶14 The complaint alleges that CacheLib-enabled software uses SSDs, including NVMe SSDs, for long-term storage Compl. ¶15
- The "HybridCache" component allegedly uses an SSD-optimized engine called "Navy" to extend cache size by transparently caching objects in Non-Volatile Memory (NVM) Compl. ¶22 A cited CacheLib architecture guide, attached as Exhibit 11, describes this "Navy" engine Compl. ¶22
- The complaint alleges that these systems use "storage policies managing the placement of write data in the SSD tier" and control the read/write paths using "content identifiers, and placement directives" Compl. ¶15 It further alleges these policies are implemented using features of the NVMe standard, such as Flexible Data Placement (FDP) Compl. ¶24 An overview document for FDP is referenced as Exhibit 17 to support this allegation Compl. ¶24
IV. Analysis of Infringement Allegations
10,776,023 Infringement Allegations
| Claim Element (from Independent Claim 1) | Alleged Infringing Functionality | Complaint Citation | Patent Citation |
|---|---|---|---|
| a storage media; | Non-Volatile Memory (NVM) devices within the SSDs used by the HybridCache component of the CacheLib library. | ¶22 | col. 3:29-34 |
| a device controller operatively coupled with the storage media configured to at least: | The device controller within the SSDs used to manage read and write requests to the coupled NVM devices. | ¶23 | col. 3:43-44 |
| receive, from a host, at least one storage device policy, wherein the at least one storage device policy indicates at least a recording method for writing content to the storage media; | The Flash Translation Layer (FTL) software on the device controller receives policies from the host server, which include data placement functions like Flexible Data Placement (FDP) logical regions defined in the NVMe standard. | ¶24 | col. 8:15-24 |
| receive a storage request, from the host, to store content; | A CacheLib instance on a host server issues requests to store content, which are received by the SSD tier's device controller. | ¶25 | col. 8:25-29 |
| store the content on the storage media by utilizing the recording method indicated by the at least one storage device policy; | The FTL software on the device controller stores content in the NVM using the FDP placement functions and received logical region identifiers to implement the policies. | ¶26 | col. 10:19-24 |
| record storage information for the content on a memory of the device controller, comprising at least a content identifier for the content; | The FTL software stores a logical-to-physical address mapping on the device controller's memory. The logical address is alleged to be the host-visible "content identifier." | ¶27 | col. 8:35-44 |
| subsequent to storing the content, receive a content request for the content, comprising at least the content identifier for the content; | The device controller receives subsequent content-read requests from the host's HybridCache component, which include the logical address identifier. | ¶28 | col. 8:35-44 |
| in response to the content request, retrieve from the memory of the device controller, the storage information for the content; | The device controller retrieves the stored logical-to-physical mapping from its memory in response to a read request. | ¶29 | col. 8:45-51 |
| recover the content from the storage media, at least in part according to the storage information; and | The device controller uses the retrieved mapping and the logical address from the read request to determine the physical address and recover the content from the NVM. | ¶30 | col. 8:52-58 |
| respond to the content request at least by returning the content to the host. | The SSD returns the recovered data to the host server, which directs it to the CacheLib instance that initiated the request. A document on CacheLib user guides is cited as Exhibit 8 to show reading data from the cache Compl. ¶28 Compl. ¶31 | ¶31 | col. 8:59-63 |
Identified Points of Contention
- Scope Questions: A central issue may be whether the "device controller" is truly the entity performing the claimed intelligent actions. The complaint alleges that FTL software on the controller receives policies (e.g., FDP logical regions) from the host and executes them. A defense may argue that the controller is merely executing low-level commands dictated by the host-side CacheLib software, and that the "policy" intelligence resides entirely on the host, not on the claimed "device controller."
- Technical Questions: The complaint equates a "content identifier" with a "logical address" used in a logical-to-physical address mapping scheme Compl. ¶27 The case may turn on whether a logical address, a standard component of modern storage interfaces, is legally equivalent to the "content identifier for the content" as required by the claim, or if the claim requires a different type of identifier.
11,327,669 Infringement Allegations
| Claim Element (from Independent Claim 1) | Alleged Infringing Functionality | Complaint Citation | Patent Citation |
|---|---|---|---|
| a storage device; | Non-Volatile Memory (NVM) integrated circuits (ICs) used by the HybridCache component of the CacheLib library. | ¶41 | col. 3:29-34 |
| a device controller operatively coupled with the storage device, comprising a memory; | The device controller in the SSDs, which includes a processor running firmware stored in a program memory on the device controller. | ¶42 | col. 3:43-46 |
| an application stored on the memory...direct the device controller to at least: | The FTL firmware functions, comprising CPU instructions fetched from stored firmware on the device controller, are alleged to be the "application." | ¶43 | col. 4:15-21 |
| receive a storage device policy; | The FTL firmware application receives policies from the host, including FDP logical region identifiers supplied by the CacheLib instance via NVMe protocols. | ¶44 | col. 12:1-14 |
| receive a storage request, comprising content; | A CacheLib instance issues requests to store content, which are received by the SSD tier and the device controllers. | ¶45 | col. 11:21-24 |
| store the content on the storage device according to the storage device policy; | The FTL firmware causes content to be stored in the NVM ICs using the FDP placement functions and received logical region identifiers to implement the configured policies. | ¶46 | col. 11:32-38 |
| record storage information for the content on the memory, comprising at least a content identifier for the content; | The FTL firmware stores a logical-to-physical address mapping. The logical address is alleged to be the unique, host-visible "content identifier." | ¶47 | col. 15:1-6 |
| subsequent to storing the content, receive a content request for the content...; | The device controller receives subsequent read requests from the host's HybridCache component, which include the logical address identifier. | ¶48 | col. 18:2-7 |
| in response to the content request, retrieve storage information for the content; | The device controller retrieves the stored logical-to-physical mapping in response to read requests. | ¶49 | col. 18:8-12 |
| recover the content, at least in part according to the storage information; and | The device controller uses the retrieved mapping and the logical address in the read request to determine the physical address and recover the content from the coupled NVM. | ¶50 | col. 18:13-17 |
| respond to the content request at least by returning the content. | The SSD returns the recovered data to the host server, which directs it to the CacheLib instance. | ¶51 | col. 18:18-19 |
Identified Points of Contention
- Scope Questions: Similar to the '023 Patent, the core dispute will likely involve the division of functionality between the host and the device. For the '669 Patent, this is focused on whether the "FTL firmware" on the SSD controller qualifies as an "application" that directs the controller, as claimed. A defense may argue the FTL is a low-level, conventional component that is itself directed by the host, rather than an "application" that directs the device.
- Technical Questions: The analysis of whether a "logical address" constitutes a "content identifier" remains a key technical question, as described in the analysis of the '023 Patent.
V. Key Claim Terms for Construction
The Term: "device controller" (Asserted in Claim 1 of '023 Patent and Claim 1 of '669 Patent)
Context and Importance: This term is the central actor in the asserted claims. The infringement case depends on whether the accused SSD controller, which receives commands from Meta's host-side CacheLib software, is legally considered the "device controller" performing the claimed policy-driven functions. Practitioners may focus on this term because its construction will determine whether the functions executed by the accused system are attributable to the claimed component.
Intrinsic Evidence for Interpretation:
- Evidence for a Broader Interpretation: The specification states the "device controller 130 is significantly more than a traditional hard disk controller," possessing "additional functionality allowing it to run additional code and/or applications" '023 Patent, col. 3:45-54 This may support an interpretation that includes a controller configured by a host to perform complex, policy-based actions.
- Evidence for a Narrower Interpretation: The specification contrasts the claimed invention with a traditional controller that is "only capable of responding to host controller commands" '023 Patent, col. 3:47-50 This language may support an argument that if the accused controller is merely responding to commands from the host (even if those commands embed policy information like an FDP region), it does not meet the inventive definition.
The Term: "storage device policy" (Asserted in Claim 1 of '023 Patent and Claim 1 of '669 Patent)
Context and Importance: The definition of this term is critical for determining what information qualifies as a "policy." The complaint alleges that an "identifier indicating the logical region" for a write, based on the NVMe FDP standard, is part of the policy (Compl. ¶24; Compl. ¶44). The viability of the infringement claim may depend on whether such an identifier falls within the construed scope of "storage device policy."
Intrinsic Evidence for Interpretation:
- Evidence for a Broader Interpretation: The specification describes the policy as potentially covering "many or all aspects of operation" and gives a range of examples including "layout," "defect avoidance," and "read/write control" '023 Patent, col. 3:8-12 '023 Patent, Fig. 7A This suggests the term could encompass a wide variety of directives, including a placement identifier.
- Evidence for a Narrower Interpretation: The specification also provides examples of a policy as a "collection of cooperating libraries" or even a script-like code snippet that defines complex, conditional logic '023 Patent, col. 12:25-54 '023 Patent, col. 13 This could support an argument that a "policy" must be an algorithmic or rule-based construct, not merely a simple parameter or tag like a logical region identifier.
VI. Other Allegations
- Willful Infringement: The complaint alleges that "despite notice" of the patents-in-suit, Meta "has and continues to infringe" Compl. ¶34 Compl. ¶54 Compl. ¶73 Compl. ¶88 This allegation provides a basis for willful infringement based on knowledge of the patents, which at a minimum would be established by the filing of the lawsuit itself.
VII. Analyst's Conclusion: Key Questions for the Case
- A core issue will be one of architectural scope: does Meta's system, which divides functionality between host-side software (CacheLib) and a device-side SSD controller, meet the claim requirements for an apparatus where the "device controller" itself receives policies and performs the intelligent storage and retrieval operations? The case will likely require a determination of which entity-the host or the device-is legally performing the claimed invention.
- A second key question will be one of definitional equivalence: can a low-level command parameter, such as a "logical region" identifier used in the NVMe Flexible Data Placement standard, be construed as the claimed "storage device policy" that "indicates at least a recording method"? The outcome may depend on whether the court views the "policy" as a high-level set of rules or as any directive that influences storage behavior.
Analysis metadata
Loading Complaint
Suggested improvements