Adeia Media Holdings Inc v. fuboTV Inc

I. Executive Summary and Procedural Information

• Parties & Counsel:
  • Plaintiff: Adeia Media Holdings Inc. (Delaware)
  • Defendant: FuboTV Inc., Fubo Operations LLC, Fubo Services LLC, & FuboTV Media LLC (Delaware)
  • Plaintiff's Counsel: Farnan LLP
• Case Identification: 1:26-cv-00776, D. Del., 06/30/2026
• Venue Allegations: Venue is alleged to be proper in the District of Delaware because each Defendant resides in, has committed acts of infringement in, and has a regular and established place of business in the District.
• Core Dispute: Plaintiff alleges that Defendants' Fubo over-the-top streaming service infringes four patents related to dynamic mobile program guides, access control for segmented streaming, cloud data persistence, and multi-CDN manifest file configuration.
• Technical Context: The technologies at issue relate to the backend architecture and delivery mechanisms for modern video streaming services, addressing challenges in user experience, content security, and network efficiency.
• Key Procedural History: The complaint asserts that the patents-in-suit originate from a history of innovation by Plaintiff's predecessors (including TiVo, Rovi, and MobiTV) and from strategic acquisitions of patent portfolios from streaming technology companies Brightcove (Unicorn Media), DLVR Inc., and MobiTV. Plaintiff notes that many major pay-TV and streaming companies have licensed its media patent portfolio.

Case Timeline

Date	Event
2006-10-02	U.S. Patent No. 7,818,769 Priority Date
2010-10-19	U.S. Patent No. 7,818,769 Issued
2011-01-31	U.S. Patent No. 8,280,987 Priority Date
2011-09-26	U.S. Patent No. 8,239,546 Priority Date
2012-08-07	U.S. Patent No. 8,239,546 Issued
2012-10-02	U.S. Patent No. 8,280,987 Issued
2014-10-29	U.S. Patent No. 10,911,509 Priority Date
2021-02-02	U.S. Patent No. 10,911,509 Issued
2026-06-30	Complaint Filing Date

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

U.S. Patent No. 7,818,769 - Methods and Apparatus for Implementing Dynamic Program Guides on Mobile Devices (Issued Oct. 19, 2010)

The Invention Explained

• Problem Addressed: The patent describes the problem of providing comprehensive electronic program guides (EPGs) to mobile devices, which often had limited memory, storage, and network bandwidth Compl. ¶116 Conventional methods that required downloading the entire guide at once could disrupt the user's experience and strain mobile networks Compl. ¶117 '769 Patent, col. 1:25-26
• The Patented Solution: The patent proposes a two-phase data retrieval method. First, a mobile device sends a request for "program guide structure information," such as a list of channels Compl. ¶119 '769 Patent, col. 5:2-6 After receiving this structural data, the device can display a basic guide framework. As the user navigates to a specific portion of the guide (e.g., a block of channels or a time period), the device sends a second, on-demand request for "program guide content information," such as program titles and descriptions for that specific portion Compl. ¶119 '769 Patent, col. 7:24-34 This allows for a responsive EPG experience without requiring a complete upfront download.
• Technical Importance: This method improved the functionality of EPGs on early mobile devices by reducing initial load times and conserving limited device and network resources, making interactive guides more practical in a constrained environment Compl. ¶120

Key Claims at a Glance

• The complaint asserts at least independent Claim 1 Compl. ¶126
• The essential elements of independent method Claim 1 include:
  • sending a first request from the mobile device to a server for program guide structure information;
  • receiving a first response at the mobile device including a plurality of channel identifiers;
  • sending a second request from the mobile device for program guide content information, where the request indicates a channel block or time period and is sent in response to navigation of the guide; and
  • receiving a second response at the mobile device including a plurality of program titles for channels in the navigated portion of the guide.
• Plaintiff reserves the right to assert additional claims Compl. ¶125

U.S. Patent No. 8,239,546 - Global Access Control for Segmented Streaming Delivery (Issued Aug. 7, 2012)

The Invention Explained

• Problem Addressed: The patent identifies a vulnerability in early streaming systems where authentication was performed only at the beginning of a session '546 Patent, col. 5:50-6:21 This created an inability to monitor the ongoing status of a stream, which could allow a single subscription account to be used for concurrent streaming on multiple devices, thereby undermining access control and subscription models Compl. ¶¶159-160
• The Patented Solution: The patent claims a method for controlling access during streaming by using "beaconing data" sent from the user's device during transmission '546 Patent, Abstract Compl. ¶161 This data is used to create and store "session information" that indicates an active stream for a specific user and device. When a second device on the same account attempts to stream, the system uses this stored session information to determine whether to permit the new stream and, if necessary, to cease transmission to the first device Compl. ¶165 The specification notes that beaconing data can be inferred from the timing of client requests for media segments, not just explicit status reports '546 Patent, col. 10:51-53
• Technical Importance: This technology provided a concrete technical architecture for enforcing limits on simultaneous streams, a critical feature for the business models of subscription-based video services Compl. ¶161

Key Claims at a Glance

• The complaint asserts at least independent Claim 1 Compl. ¶168
• The essential elements of independent method Claim 1 include:
  • commencing transmission of a media asset in sequential segments to a first user device;
  • receiving, during transmission, beaconing data from the first user device;
  • storing session information based on the beaconing data that indicates the first device has an active session;
  • receiving authentication information for a second user device on the same account while the first device's transmission is occurring;
  • determining the first user device is no longer permitted to receive the media asset based on the session information; and
  • ceasing transmission of the remainder of the media segments to the first user device.
• Plaintiff reserves the right to present alternative infringement explanations for other claims Compl. ¶167

U.S. Patent No. 8,280,987 - Cloud Data Persistence Engine (Issued Oct. 2, 2012)

• Technology Synopsis: The patent addresses the inefficiency of storing all data on every server in a geographically distributed network Compl. ¶208 It proposes a "cloud data persistence" system where the data objects stored on each server vary based on historical client request data, which serves to reduce storage requirements and increase access speed '987 Patent, col. 4:64-5:5 Compl. ¶209 The architecture involves a hierarchy of application centers, cache servers, and an origin server Compl. ¶214 '987 Patent, Fig. 5A
• Asserted Claims: At least Claim 14 Compl. ¶218
• Accused Features: Fubo's alleged use of a cloud-based, multi-tiered architecture for delivering manifests and media content, employing Content Delivery Networks (CDNs) like Fastly and Akamai as application centers, cache servers, and origin servers Compl. ¶¶219, 221, 229, 231, 241

U.S. Patent No. 10,911,509 - Configuring Manifest Files Including Redirect Uniform Resource Locators (Issued Feb. 2, 2021)

• Technology Synopsis: The patent addresses the problem of a streaming service operator's lack of visibility into the performance of third-party CDNs in a multi-CDN environment Compl. ¶277 The proposed solution involves configuring manifest files with URLs that direct a user's device to a first CDN, which in turn issues redirect messages to a second, independent CDN that serves the content. This allows the first CDN to observe data metrics about the transaction, enabling the streaming operator to measure the performance of the second CDN Compl. ¶¶278-279 '509 Patent, Abstract
• Asserted Claims: At least Claim 7 Compl. ¶284
• Accused Features: Fubo's alleged use of a multi-CDN system (e.g., Fastly and Google's CDN) where its manifest file serving system selects a first CDN to serve redirect messages that point to a second CDN for delivery of video segment files Compl. ¶¶289, 291

III. The Accused Instrumentality

Product Identification

• The Fubo over-the-top streaming service ("Fubo" or the "Accused Service") Compl. ¶29

Functionality and Market Context

• Fubo is a service that broadcasts live and on-demand television content over the internet to a variety of user devices, including computers, mobile devices, and smart TVs Compl. ¶¶30-31 Compl. ¶35 The service provides access to over 200 channels and is marketed as an alternative to traditional cable TV (Compl. ¶31; Compl. ¶36). Functionally, the service implements an electronic program guide (EPG) for navigating content Compl. ¶127 The complaint also alleges that Fubo's service controls access to streaming by limiting the number of simultaneous streams permitted for a given user account, based on factors like subscription plan and device location Compl. ¶¶170, 183 Fubo's support page, depicted in the complaint, explains that certain plans allow up to 10 simultaneous streams on a "Home Network" and 3 additional streams "outside the home" Compl. p. 39

IV. Analysis of Infringement Allegations

'769 Infringement Allegations

Claim Element (from Independent Claim 1)	Alleged Infringing Functionality	Complaint Citation	Patent Citation
A method for implementing a program guide on a mobile device.	Fubo implements an electronic program guide (EPG) in the Fubo app on mobile devices like tablets and phones.	¶127	col. 1:11-14
sending a first request from the mobile device to a server, the first request associated with program guide structure information	When a user selects "Guide" in the Fubo app, the app sends an HTTP GET request to a Fubo server to retrieve a list of channels for the user's profile. A screenshot in the complaint shows the Fubo app interface on an iPad. Compl. p. 30	¶129	col. 5:2-6
receiving a first response at the mobile device from the server, the first response associated with program guide structure information, the program guide structure information including a plurality of channel identifiers	The Fubo app receives a response to the HTTP GET request which includes a channel listing, where each channel has a "channel_id." The EPG is then structured based on this listing.	¶131; ¶132	col. 5:10-15
sending a second request from the mobile device to the server, the second request associated with program guide content information, wherein the second request indicates a requested channel block or time period and is sent to the server in response to navigation to a first portion of the program guide...	When the user navigates the EPG grid, the Fubo app sends a second HTTP GET request to the server to receive program listings for a specific time period.	¶134	col. 5:16-21
receiving a second response at the mobile device from the server, the second response associated with the program guide content information, wherein the program guide content information includes a plurality of program titles for a first plurality of channels in the first portion of the program guide.	The Fubo app receives a response to the second HTTP GET request that includes program listings and associated attributes for the channels accessible to the user.	¶136; ¶137	col. 5:22-26

• Identified Points of Contention:
  • Scope Question: A central question for claim construction may be whether the terms "program guide structure information" and "program guide content information" are distinct categories as claimed. The dispute may focus on whether Fubo's initial fetch of a channel list (allegedly "structure") is technically separate from the subsequent fetching of program titles for those channels (allegedly "content"), or if they are fetched together in a more conventional on-demand manner.
  • Technical Question: An evidentiary question will be whether Fubo's backend architecture actually implements the claimed two-phase request sequence. The analysis will depend on evidence showing that the initial data received is limited to "structure" and that "content" is only requested and delivered in a distinct second step tied to user navigation.

'546 Infringement Allegations

Claim Element (from Independent Claim 1)	Alleged Infringing Functionality	Complaint Citation	Patent Citation
...commencing transmission of a media asset to a first user device...transmission of the media asset comprises sequential transmission of a plurality of media segments.	When a user selects content, Fubo transmits it to the user's device in sequential chunks.	¶172; ¶174	col. 1:17-27
receiving during transmission of the media asset to the first user device, beaconing data from the first user device.	During media transmission, Fubo collects information from the user's device, such as IP address, location, and device IDs, at configured intervals.	¶176; ¶177	col. 10:47-53
storing session information linked with the first user device and the user account, wherein...the session information indicates the first user device and the user account have an active session...	Fubo stores session information based on the collected data, linking it with the user's account and device and indicating that the device has an active streaming session.	¶179	col. 12:56-13:7
receiving authentication information linked with a second user device and the user account while transmission of the media asset to the first user device is occurring.	A second device can log into Fubo using matching credentials while the first device is in an active streaming session.	¶181	col. 18:45-19:16
determining the first user device is no longer permitted to receive the media asset...based on at least the session information.	When the second device seeks to stream, Fubo determines the user account is not authorized to begin another stream because it would exceed the permitted number of concurrent streams.	¶183	col. 19:48-20:19
ceasing transmission of a remainder of the plurality of media segments to the first user device...	If the user of the second device chooses to continue streaming, Fubo ceases transmission of the content to the first user device. The complaint includes a screenshot of a "Limit reached" warning message presented to the user. Compl. p. 43	¶186; ¶187	col. 14:28-40

• Identified Points of Contention:
  • Scope Question: The definition of "beaconing data" will be critical. The infringement analysis raises the question of whether Fubo's periodic collection of general device and network information (e.g., IP address, location) Compl. ¶176 meets the patent's definition, particularly as the specification provides examples of deriving beaconing data more specifically from the timing of media segment requests '546 Patent, col. 10:51-65
  • Technical Question: A key evidentiary issue will be the precise mechanism by which Fubo enforces stream limits. The complaint alleges a causal link: the "session information" from the first device is used to "determin[e]" that it is no longer permitted to stream. The case may turn on evidence demonstrating this specific data flow and logic within Fubo's servers, as opposed to a simpler system that merely counts active logins without reference to ongoing data from an existing stream.

V. Key Claim Terms for Construction

From U.S. Patent No. 7,818,769

• The Term: "program guide structure information"
• Context and Importance: The infringement theory relies on a two-step process where "structure" information is fetched before "content" information. The viability of the infringement claim depends on whether the initial channel list data Fubo allegedly fetches Compl. ¶129 can be properly categorized as "structure information" as distinct from the program titles fetched later. Practitioners may focus on this term because the distinction is fundamental to the claimed method.
• Intrinsic Evidence for Interpretation:
  • Evidence for a Broader Interpretation: The claim itself simply requires the information to include "a plurality of channel identifiers" '769 Patent, Claim 1, and the specification notes that it "includes lineup data" '769 Patent, col. 2:2-3, suggesting it could be any data that provides a channel framework.
  • Evidence for a Narrower Interpretation: The specification explicitly contrasts "structure information" with "content information," which includes "program titles, times, icons, and links" '769 Patent, col. 1:12-14 A defendant may argue that this contrast implies "structure information" must be devoid of any "content," limiting its scope to just the bare channel list.

From U.S. Patent No. 8,239,546

• The Term: "beaconing data"
• Context and Importance: The claimed method requires "receiving... beaconing data from the first user device" during transmission to monitor the session. The infringement allegation is that Fubo's collection of general user data like IP addresses and device IDs constitutes "beaconing" Compl. ¶176 The construction of this term will determine if this general data collection is sufficient, or if a more specific, stream-related signal is required.
• Intrinsic Evidence for Interpretation:
  • Evidence for a Broader Interpretation: The term is not explicitly defined in the claim itself, which may support an argument that it should be given its plain and ordinary meaning, which could encompass any data sent from the device to report its status.
  • Evidence for a Narrower Interpretation: The specification provides specific examples of what can constitute beaconing data, such as data derived from the "pattern and timing of the end user device's requests for media segments and index files" '546 Patent, col. 10:51-53 and inferring a pause if the time between successive requests exceeds a certain threshold '546 Patent, col. 15:60-16:8 A party could argue that these specific examples define and limit the scope of the term to data directly related to the streaming process itself.

VI. Other Allegations

• Indirect Infringement: The complaint alleges that Defendants induce infringement by operating the Fubo website, which provides instructions to end-users on how to use the allegedly infringing features, such as the program guide and the Cloud DVR recording function Compl. ¶¶104-108 Compl. ¶143 The complaint includes screenshots from Fubo's support website titled "How do I use the Fubo channel guide?" and "How can I record a program?" as evidence of these instructions Compl. p. 17 Compl. p. 25
• Willful Infringement: The complaint alleges that Defendants' infringement is willful based on their awareness of the infringement, with knowledge alleged to exist "at least as of the filing of this Complaint" Compl. ¶109 Compl. ¶151 Compl. ¶201 Compl. ¶269 Compl. ¶313 This constitutes an allegation of post-suit willfulness, as no facts supporting pre-suit knowledge are pleaded.

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

1. A central issue will be one of definitional scope and evidence: Can the data retrieved by the Fubo app be factually and legally segregated into the '769 patent's distinct categories of "program guide structure information" and "program guide content information"? The case will likely require a technical deep dive into Fubo's data-fetching architecture to resolve this.
2. A key question will be one of functional mechanism: Does Fubo's system for enforcing concurrent stream limits use "beaconing data" from an active stream to determine that another device is no longer permitted access, as required by the '546 patent? Or does it employ a simpler mechanism, such as merely counting total active logins for an account, that may not map onto the claim's specific sequential steps?
3. A significant dispute may arise over the multi-CDN architecture alleged to infringe the '987 and '509 patents. The infringement theories depend on a highly specific, tiered data-request and redirect-based monitoring architecture. A primary question will be whether Fubo's use of multiple CDNs actually operates according to these claimed unconventional methods or if it uses more conventional, industry-standard load-balancing and content delivery techniques.