DCT
1:26-cv-01100
Datasphere LLC v. Fox Corp
Key Events
Complaint
Table of Contents
complaint Intelligence
I. Executive Summary and Procedural Information
- Parties & Counsel:
- Plaintiff: DataSphere, LLC (Georgia)
- Defendant: FOX Corporation (Delaware); FOX Sports Productions, LLC (Delaware)
- Plaintiff's Counsel: Farnan LLP
- Case Identification: 1:26-cv-01100, D. Del., 08/31/2026
- Venue Allegations: Venue is asserted based on both Defendants being incorporated or organized under the laws of Delaware and their infringing activities allegedly occurring within the District.
- Core Dispute: Plaintiff alleges that Defendant's enterprise networking and storage systems infringe three patents related to distributed packet routing, storage input/output decoupling, and long-distance Fibre Channel flow control.
- Technical Context: The technologies at issue concern high-performance data routing and storage area network (SAN) management, which are foundational for large-scale media production, broadcasting, and content distribution operations.
- Key Procedural History: The complaint notes that U.S. Patent No. 7,782,778 expired on October 27, 2025, and Plaintiff seeks damages for infringement that occurred before that date. No other significant procedural events are mentioned.
Case Timeline
| Date | Event |
|---|---|
| 2002-12-24 | '778 Patent Priority Date |
| 2004-02-24 | '239 Patent Priority Date |
| 2005-10-07 | '381 Patent Priority Date |
| 2009-05-05 | '239 Patent Issue Date |
| 2009-12-29 | '381 Patent Issue Date |
| 2010-08-24 | '778 Patent Issue Date |
| 2022-03-20 | Accused Product Mention: Senior Systems Engineer job posting date |
| 2025-09-16 | Accused Product Mention: Post Production Engineer job posting date |
| 2025-10-27 | '778 Patent Expiration Date |
| 2026-07-17 | Accused Product Mention: Principal Network Engineer job posting date |
| 2026-08-31 | Complaint Filing Date |
II. Technology and Patent(s)-in-Suit Analysis
U.S. Patent No. 7,529,239 - Distributed Dynamic Routing (Issued May 5, 2009)
The Invention Explained
- Problem Addressed: The patent describes conventional packet routing as inefficient, noting that requiring every router in a network path to make an independent, Layer 3 (network layer) routing decision introduces complexity and slowness, particularly for fault detection and recovery '239 Patent, col. 2:5-18
- The Patented Solution: The invention proposes a distributed routing method where a "source edge device," upon receiving a packet, makes a single, comprehensive routing decision '239 Patent, col. 3:3-7 This decision determines not only the immediate next hop but also the final "target edge device" for the packet's transit across the internal network. The source device then generates a new "transmission packet" that encapsulates the original data packet along with the determined next-hop address and the target edge device's network interface information '239 Patent, col. 3:8-15 This transmission packet is then switched across the internal network at the faster data link layer (Layer 2) directly to the target edge device, bypassing intermediate Layer 3 routing decisions '239 Patent, abstract '239 Patent, col. 4:47-54
- Technical Importance: This architecture aimed to accelerate packet forwarding and improve fault tolerance by centralizing the complex routing intelligence at the network edge and leveraging simpler, faster Layer 2 switching for transport across the network core.
Key Claims at a Glance
- The complaint asserts independent Claim 1 Compl. ¶¶50-51
- Key elements of Claim 1 include:
- Receiving a data packet at a source edge device from an external network.
- Determining, in the source edge device, the next-hop address for the packet.
- Determining, in the source edge device, the address and network interface of a target edge device from a plurality of such devices, in response to the next-hop address.
- Generating, in the source edge device, a transmission packet containing the original packet, the next-hop address, and the target's network interface.
- Transmitting the transmission packet from the source to the target edge device at the data link layer level.
- The target edge device then uses the determined next-hop address to forward the original packet.
- The complaint does not explicitly reserve the right to assert other claims.
U.S. Patent No. 7,640,381 - Input/Output Decoupling System Method Having a Cache for Exchanging Data Between Non-Volatile Storage and Plurality of Clients Having Asynchronous Transfers (Issued Dec. 29, 2009)
The Invention Explained
- Problem Addressed: The patent identifies performance bottlenecks in storage systems caused by the high latency of mechanical disk drives and competition among multiple clients for storage access '381 Patent, col. 1:20-25 This can lead to inefficient "disk drive 'thrashing'" and degraded performance '381 Patent, col. 1:59-64
- The Patented Solution: The invention describes an "I/O accelerator" apparatus positioned between host clients and a non-volatile storage system '381 Patent, abstract The apparatus contains a cache with buffers associated with each client '381 Patent, col. 8:13-16 The core of the solution is circuitry that identifies a data rate for transferring data to a client based on the amount of data already existing in that client's buffer. This client-facing data transfer is "decoupled" from the asynchronous data transfers occurring between the apparatus and the slower, non-volatile storage component '381 Patent, col. 8:17-23 This decoupling allows the system to manage data flows more intelligently, insulating fast clients from the delays of the underlying storage system '381 Patent, Fig. 5
- Technical Importance: This I/O decoupling approach was designed to smooth data streams, improve overall system throughput, and reduce latency by using an intermediate cache to manage and buffer data flows independently for different clients.
Key Claims at a Glance
- The complaint asserts independent Claim 25 Compl. ¶¶72-73
- Key elements of Claim 25 include:
- An apparatus comprising a storage interface, a host interface, and a cache.
- The cache is configured to cache communications and associate a buffer with each client.
- Circuitry is configured to identify a data rate for transferring data over the host interface to a client.
- The identified data rate is based on an amount of data existing in the buffer for the receiving client.
- The identified data rate is "decoupled from asynchronous transfers over the storage interface."
- The complaint does not explicitly reserve the right to assert other claims.
U.S. Patent No. 7,782,778 - Apparatus and Method for Fibre Channel Distance Extension Embedded Within an Optical Transport System (Issued Aug. 24, 2010)
Technology Synopsis
The patent addresses the inherent distance limitations of Fibre Channel Storage Area Networks (SANs), which are constrained by the protocol's "buffer credit" flow control mechanism '778 Patent, col. 2:3-12 The invention provides a method for extending these distances by having an ingress terminal track memory availability at a remote egress terminal. The ingress terminal determines whether to allow more data into the long-distance optical path based on the amount of data it has already transmitted and the known capacity of the remote endpoint, thus implementing a form of remote-capacity-aware flow control '778 Patent, abstract '778 Patent, claim 25
Asserted Claims
The complaint asserts independent Claim 25 Compl. ¶¶97-98
Accused Features
The complaint accuses FOX's "Long-Distance Optical Fibre Channel Systems," which allegedly used paired Brocade SAN-extension endpoints to move data between geographically separated FOX SANs before the patent's expiration (Compl. ¶44; Compl. ¶45).
III. The Accused Instrumentality
Product Identification
The complaint identifies three categories of accused instrumentalities operated by FOX:
- "EVPN-VXLAN Routed Overlays" Compl. ¶36
- "Brocade Gen 7 Fibre Channel SAN Systems" Compl. ¶40
- "Long-Distance Optical Fibre Channel Systems" Compl. ¶44
Functionality and Market Context
- The complaint alleges, based on public job postings and technical documents, that FOX operates a nationwide technology environment for its media production and broadcast operations Compl. ¶32 The "EVPN-VXLAN" overlays are described as systems that extend network connectivity across FOX facilities like studios and data centers, using VXLAN Tunnel Endpoints (VTEPs) as edge devices between the overlay and other networks Compl. ¶¶36-37 The Brocade Gen 7 SAN systems are alleged to be used for connecting storage arrays to servers, workstations, and virtual machines, managing data flow via internal frame buffers and buffer-credit mechanisms Compl. ¶¶40-41 The Long-Distance Optical FC Systems are alleged to have been used before October 27, 2025, to connect geographically separate SANs over wide-area optical paths Compl. ¶¶44-45
No probative visual evidence provided in complaint.
IV. Analysis of Infringement Allegations
U.S. Patent No. 7,529,239 Infringement Allegations
| Claim Element (from Independent Claim 1) | Alleged Infringing Functionality | Complaint Citation | Patent Citation |
|---|---|---|---|
| receiving a data packet at a source edge device from an external telecommunication network; | When traffic enters the accused fabric, FOX's ingress VTEP receives the original data packet at the boundary of the EVPN-VXLAN overlay. | ¶55 | col. 5:61-63 |
| determining in the source edge device the next-hop address corresponding to the destination address prefix of the received data packet; | FOX's ingress VTEP determines a next-hop address via a destination-IP-prefix lookup in the applicable IP-VRF. | ¶57 | col. 5:64-67 |
| determining in the source edge device the address and network interface of a target edge device, from among a plurality of target edge devices, in response to the determined next-hop address, wherein the next-hop address corresponds to a device in another external telecommunication network; | In response to the determined next-hop address, the ingress VTEP determines the address and network interface of a selected target VTEP by recursively resolving the overlay next hop to a remote VTEP. | ¶59 | col. 6:3-7 |
| generating in the source edge device a transmission packet addressed to the target edge device, the transmission packet comprising the received data packet and the determined next-hop address and the determined network interface of the target edge device; | The ingress VTEP generates a VXLAN transmission packet addressed to the selected target VTEP that includes the original data packet, the determined next-hop address, and the determined network interface. | ¶61 | col. 6:8-15 |
| transmitting the generated transmission packet from the source edge device to the determined target edge device via one or more internal telecommunication networks at the data link layer level, | The ingress VTEP transmits the packet to the target VTEP at the data-link layer by carrying the original Ethernet frame between the edge devices. | ¶63 | col. 6:15-18 |
| wherein the target edge device uses the determined next-hop address to forward the received data packet to the next-hop. | The target VTEP uses the determined next-hop address from the transmission packet to forward the original packet into the attached external network. | ¶65 | col. 6:21-24 |
- Identified Points of Contention:
- Scope Question: A central issue may be whether the components of a modern EVPN-VXLAN overlay network (e.g., "ingress VTEP", "target VTEP", "VNI") map onto the claimed terms "source edge device", "target edge device", and "network interface" as understood in the context of the '239 Patent's disclosure. The patent's figures and description suggest a specific physical or logical topology '239 Patent, Fig. 2a, and a dispute may arise over whether the more dynamic, virtualized nature of VXLAN overlays falls within the claim scope.
- Technical Question: The claim requires determining a next-hop address that "corresponds to a device in another external telecommunication network." The complaint alleges the accused system does this Compl. ¶59 A key factual question will be what the "next-hop address" determined by the ingress VTEP technically represents and whether it directly corresponds to a device external to the target VTEP's local network, as the claim requires.
U.S. Patent No. 7,640,381 Infringement Allegations
| Claim Element (from Independent Claim 25) | Alleged Infringing Functionality | Complaint Citation | Patent Citation |
|---|---|---|---|
| a storage interface configured to communicate with a storage system having a non-volatile storage component; | The accused Brocade switches have storage-facing Fibre Channel F_Ports connected to storage arrays with non-volatile media. | ¶77 | col. 3:45-48 |
| a host interface configured to communicate with a plurality of clients; | The accused switches have host-facing F_Ports connected to multiple clients (servers, workstations, virtual machines). | ¶79 | col. 3:55-58 |
| a cache configured to cache communications exchanged between the non-volatile storage component and the plurality of clients, the cache configured to associate a buffer with each client; | ASICs within the accused switches provide volatile frame-buffer memory that caches communications. The system associates buffers with clients via port, queue, or buffer-credit state. | ¶81; ¶82 | col. 5:1-12 |
| and circuitry configured to: identify a data rate for transferring data from the apparatus, over the host interface, to one of the plurality of clients, | The switch ASICs and Fabric OS provide circuitry that identifies a data rate for transmission to a client based on factors like available credit and queue state. | ¶86 | col. 7:2-8 |
| wherein the identified data rate is based on an amount of data existing in the buffer for the receiving client | The circuitry allegedly identifies the data rate based on measures such as queue occupancy, queued-frame count, or the number of frames awaiting transmission for that client. | ¶88 | col. 7:10-15 |
| and decoupled from asynchronous transfers over the storage interface. | The identified data rate is allegedly decoupled from storage-side transfers through the use of separate storage-facing and host-facing buffers, queues, and schedulers. | ¶90 | col. 7:42-50 |
- Identified Points of Contention:
- Scope Question: The analysis will likely focus on the meaning of "decoupled." A question for the court will be whether the standard operation of a modern Fibre Channel switch, which inherently uses buffers and flow control (like buffer-to-buffer credits), constitutes the specific "decoupling" described in the patent, or if the patent requires a more specialized architectural separation not present in the accused systems.
- Technical Question: Does the accused system's circuitry actively "identify a data rate" based on the "amount of data existing in the buffer," as claimed? The complaint alleges this is based on metrics like queue occupancy Compl. ¶88 A factual dispute may arise over whether the accused switches' operation is more accurately described as a standard credit-based flow control mechanism, rather than a dynamic "data rate identification" process as contemplated by the claim.
V. Key Claim Terms for Construction
'239 Patent
- The Term: "target edge device"
- Context and Importance: This term is foundational to the patent's routing architecture, which relies on a source device pre-determining a target device for layer-2 transit. The complaint equates this with a "target VTEP" in an EVPN-VXLAN overlay Compl. ¶59 The construction of this term will be critical to determining if the accused modern, virtualized network architecture maps onto the patent's claims.
- Intrinsic Evidence for Interpretation:
- Evidence for a Broader Interpretation: The specification provides a functional definition: "The term 'target edge device' refers to the edge device to which the generated transmission packet is addressed" '239 Patent, col. 3:11-14 This could support an interpretation covering any logical endpoint that fits this function, including a virtual one like a VTEP.
- Evidence for a Narrower Interpretation: The embodiment shown in Figure 2a depicts edge devices as distinct hardware entities (e.g., RL1, RL3) in a specific topology. A defendant may argue that the term, read in light of the specification, is limited to a physical or logical device in a non-overlay context, and does not read on a virtual tunnel endpoint that is part of a logical overlay on top of an existing network.
'381 Patent
- The Term: "decoupled from asynchronous transfers"
- Context and Importance: This phrase captures the essence of the "I/O decoupling" invention. The infringement case for the '381 patent hinges on whether the accused Brocade switches implement this specific form of decoupling. Practitioners may focus on this term because nearly all modern switches use buffers, and the case will turn on whether the accused system's operation rises to the level of "decoupling" required by the patent.
- Intrinsic Evidence for Interpretation:
- Evidence for a Broader Interpretation: The claim language itself does not specify a particular mechanism for decoupling. Plaintiff may argue that the presence of separate host-facing and storage-facing buffers, queues, and schedulers, as alleged in the complaint Compl. ¶90, is sufficient to meet the plain meaning of "decoupled."
- Evidence for a Narrower Interpretation: The specification describes the invention as solving the problem of "disk drive 'thrashing'" and enabling "uninterrupted transfer of complete large files" '381 Patent, col. 7:36-41 A defendant may argue that "decoupled" should be construed to require a specific, sophisticated management function designed to solve these particular problems, rather than just the inherent buffering and queuing present in any high-performance switch architecture.
VI. Other Allegations
- Indirect Infringement: The complaint alleges that Fox Corporation induced infringement by its subsidiary, Fox Sports Productions, LLC, for both the '239 and '381 patents. The alleged acts of inducement include providing "centralized architecture, configuration standards, training, support, and instructions" that direct the use of the accused EVPN-VXLAN and Gen 7 SAN functionalities in an infringing manner Compl. ¶69 Compl. ¶94
- Willful Infringement: For both the '239 and '381 patents, the complaint alleges that Defendants' infringement will be willful based on having actual knowledge of the patents and their infringement "at least as of service of this Complaint" Compl. ¶68 Compl. ¶93 This frames the willfulness claim as being based on post-suit conduct.
VII. Analyst's Conclusion: Key Questions for the Case
This dispute presents several key questions for the court that go to the heart of how legacy patent claims are applied to modern, evolving technologies.
- A primary issue will be one of architectural mapping: Does the architecture of a modern, virtualized EVPN-VXLAN overlay, with its logical tunnel endpoints (VTEPs), fall within the scope of the '239 Patent's claims, which describe a system of distinct "source" and "target edge devices" for Layer 2 transport?
- A second core issue is one of functional definition: Does the standard operation of a Brocade Gen 7 SAN switch-using ASICs, frame buffers, and credit-based flow control-perform the specific function of identifying a client data rate that is "decoupled" from storage-side transfers, as that term is defined by the '381 Patent?
- Finally, for the expired '778 Patent, the case will present a historical evidentiary question: Can Plaintiff prove that FOX's long-distance Fibre Channel systems, prior to October 2025, in fact operated using the claimed method of remote memory-aware flow control?
Analysis metadata