DCT

2:25-cv-00908

Headwater Research LLC v. Comcast Cable Communications LLC

Log In
Key Events
Complaint
complaint Intelligence

I. Executive Summary and Procedural Information

  • Parties & Counsel:
  • Case Identification: 2:25-cv-00908, E.D. Tex., 08/28/2025
  • Venue Allegations: Plaintiff alleges venue is proper in the Eastern District of Texas because Defendants have a regular and established place of business in the District, have committed acts of infringement in the District, and maintain a permanent physical presence in counties within the District.
  • Core Dispute: Plaintiff alleges that mobile devices and services offered by Defendant's Xfinity Mobile MVNO infringe three patents related to managing wireless data consumption and network access for applications.
  • Technical Context: The technology addresses methods for managing mobile device data usage to cope with exponential growth in data demand on wireless networks.
  • Key Procedural History: The complaint asserts that the primary inventor, Dr. Gregory Raleigh, founded multiple influential wireless technology companies, including Clarity Wireless (acquired by Cisco) and Airgo Networks (acquired by Qualcomm). Plaintiff alleges that Defendants had pre-suit knowledge of the asserted patents because patents assigned to Defendants cite family members of the asserted patents.

Case Timeline

Date Event
2009-02-04 Priority Date for '364 Patent
2011-07-23 Priority Date for '918 Patent
2012-11-15 Priority Date for '976 Patent
2014-03-04 '364 Patent Issued
2015-09-22 '976 Patent Issued
2017-05-09 '918 Patent Issued
2025-08-28 Complaint Filed

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

U.S. Patent No. 8,666,364 - "Verifiable device assisted service usage billing with integrated accounting, mediation accounting, and multi-account"

  • Patent Identification: U.S. Patent No. 8,666,364, "Verifiable device assisted service usage billing with integrated accounting, mediation accounting, and multi-account," issued on March 4, 2014. Compl. ¶17

The Invention Explained

  • Problem Addressed: As mobile data demand grows, there is a need for more granular control over service usage on wireless devices to manage service plans and costs, a problem that purely network-based solutions struggle to solve effectively (Compl. ¶9; Compl. ¶10; Compl. ¶11; Compl. ¶12, Compl. ¶¶col. 5:28-6:11).
  • The Patented Solution: The patent describes a wireless device containing software "agents" that apply "service policies" to control data usage Compl. ¶35 '364 Patent, abstract These policies can be specific to different wireless networks (e.g., applying stricter data-saving rules on a cellular network than on a Wi-Fi network) and can be modified based on user input obtained through the device's user interface '364 Patent, col. 28:2-20 A chart in the complaint shows the exponential growth of mobile data traffic, highlighting the market problem the technology addresses Compl. p. 6
  • Technical Importance: The invention provides a device-centric method for managing data consumption, enabling users and carriers to implement flexible policies to control costs and network resources in an era of increasingly complex and metered data plans (Compl. ¶15).

Key Claims at a Glance

  • The complaint asserts independent claim 1. Compl. ¶38
  • The essential elements of Claim 1 are:
    • A wireless device comprising: one or more modems for at least two wireless networks; a user interface; and a memory configured to store a first service policy for a first wireless network.
    • The policy is for reducing data usage and is controlled differently on the first network than on a second network.
    • The device also includes one or more processors executing agents configured to: obtain a user input specifying an aspect of the policy; identify that the device is connected to the first wireless network; identify a data communication associated with the policy; and apply the policy.
  • The complaint does not explicitly reserve the right to assert dependent claims.

U.S. Patent No. 9,143,976 - "Wireless end-user device with differentiated network access and access status for background and foreground device applications"

  • Patent Identification: U.S. Patent No. 9,143,976, "Wireless end-user device with differentiated network access and access status for background and foreground device applications," issued on September 22, 2015. Compl. ¶18

The Invention Explained

  • Problem Addressed: Background applications on mobile devices can consume significant network resources (particularly on cellular networks) and battery life, even when the user is not actively interacting with them '976 Patent, col. 1:15-38
  • The Patented Solution: The patent proposes a wireless device that can distinguish between applications running in the foreground (interacting with the user) and those in the background (not interacting) '976 Patent, abstract It then applies a "differential traffic control policy" that, for example, disallows Internet activity over a cellular (WWAN) connection for background applications, while also using an API to inform the application of the network's availability or unavailability '976 Patent, col. 106:1-36
  • Technical Importance: This technology provides a system-level mechanism for conserving metered cellular data and extending battery life by managing how background processes access the network, a core feature in modern mobile operating systems (Compl. ¶15).

Key Claims at a Glance

  • The complaint asserts independent claim 1. Compl. ¶49
  • The essential elements of Claim 1 are:
    • A wireless end-user device with a WWAN modem, a WLAN modem, and a display.
    • One or more processors configured to classify whether an application is interacting in the device display foreground.
    • The processors are further configured to, when on the WWAN, apply a policy to disallow Internet activity for applications classified as not interacting in the foreground.
    • The processors are also configured to indicate, via an API, network access conditions to the application based on the applied policy.
  • The complaint does not explicitly reserve the right to assert dependent claims.

U.S. Patent No. 9,647,918 - "Mobile device and method attributing media services network usage to requesting application"

  • Patent Identification: U.S. Patent No. 9,647,918, "Mobile device and method attributing media services network usage to requesting application," issued on May 9, 2017. Compl. ¶19
  • Technology Synopsis: The patent addresses the difficulty of attributing network data usage to the correct application, particularly for media downloads handled by a separate system service rather than the requesting app itself '918 Patent, col. 1:21-2:3 The invention describes using a first API for general data packet flows and a second, distinct API for media object data transfers, with a "media service manager" and "service classification and measurement agents" that reconcile the data usage to ensure it is attributed to the application that initiated the media request '918 Patent, abstract
  • Asserted Claims: The complaint asserts independent claim 1. Compl. ¶60
  • Accused Features: The complaint alleges infringement by Android-based devices that use a ConnectivityManager API for general network access, a MediaPlayer or Media3 API for media objects, and data usage monitoring tools like TrafficStats and eBPF to attribute network usage to specific applications. Compl. ¶60 Compl. Ex. 8, pp. 8, 11, 16

III. The Accused Instrumentality

Product Identification

  • The accused instrumentalities are "mobile electronic devices, including mobile phones and tablets used, made, offered for sale, sold, and/or imported by Defendants" that operate on the Xfinity Mobile network Compl. p. 1 The infringement exhibits specifically identify "Google Chromebooks and Google Pixel phones, tablets, and wearables" as examples. Compl. Ex. 4, p. 2 Compl. Ex. 6, p. 2 A visual from the complaint's exhibits shows a Google Pixel phone, identified as an example of an accused "wireless device." Compl. Ex. 4, p. 3

Functionality and Market Context

  • The complaint alleges these devices incorporate features, such as Android's "Data Saver" mode, that manage data consumption by restricting background data access over cellular networks while allowing it over Wi-Fi Compl. Ex. 4, p. 8 Compl. Ex. 6, p. 8 The complaint frames these features as essential for users on limited data plans, which are common in the mobile marketplace supplied by Comcast's Xfinity Mobile MVNO service Compl. p. 1 Compl. ¶12 The complaint provides a screenshot from a Google support page explaining how to turn the "Data Saver" feature on or off via the device's settings menu Compl. Ex. 4, p. 8

IV. Analysis of Infringement Allegations

'364 Patent Infringement Allegations

Claim Element (from Independent Claim 1) Alleged Infringing Functionality Complaint Citation Patent Citation
a wireless device, comprising: one or more modems for enabling the wireless device to communicate over at least two wireless networks, the at least two wireless networks comprising a first wireless network and a second wireless network; The accused Google Pixel 9 includes wireless modems for communicating over Bluetooth, Wi-Fi, and cellular networks. ¶38 col. 28:21-28
a user interface; The accused Google Pixel 9 includes a user interface, such as the device's main screen and settings menus. ¶38 col. 28:54-60
a first service policy associated with the first wireless network, the first service policy for at least assisting in reducing data usage over the first wireless network... the first service policy for enabling control of the first service activity on the first wireless network that is different from how the first service activity is controlled on the second wireless network; The accused devices include a "Data Saver" mode, which constitutes a service policy that reduces data usage over a cellular network (the first network) by restricting background data, a control that is different from how data is handled on a Wi-Fi network (the second network). ¶38 col. 10:1-17
one or more processors for executing one or more agents... configured to: obtain, through the user interface, a user input specifying at least an aspect of the first service policy; The accused devices run an Android OS with processors executing agents (e.g., system services) that obtain user input via the settings menu to turn "Data Saver" on or off. ¶38 col. 28:2-20
identify that the wireless device is connected to the first wireless network; The accused devices' operating system, through agents like the ConnectivityManager API, identifies when the device is connected to a metered network, such as a cellular network. ¶38 col. 9:15-28
identify an intended, attempted, or successful data communication over the first wireless network, the intended, attempted, or successful data communication being associated with the first service activity; The accused devices' operating system agents identify data communications, such as background app data requests, that are associated with the "Data Saver" service policy. ¶38 col. 9:43-57
apply the first service policy. When "Data Saver" is enabled and the device is on a cellular network, the operating system agents apply the policy by restricting background data for most apps. ¶38 col. 9:58-62
  • Identified Points of Contention:
    • Scope Questions: A central question may be whether Android's user-toggleable "Data Saver" feature constitutes a "service policy" as contemplated by the patent. The defense may argue that the patent describes a more complex, carrier-provisioned policy system, whereas "Data saver" is a simple operating system feature.
    • Technical Questions: The analysis may focus on whether general Android OS components, such as the ConnectivityManager API, function as the specific "application interface agent" required by the claims. The patent's figures depict a dedicated agent architecture (e.g., '364 Patent, FIG. 16), and a court may need to determine if the accused general-purpose OS functions meet this structural limitation.

'976 Patent Infringement Allegations

Claim Element (from Independent Claim 1) Alleged Infringing Functionality Complaint Citation Patent Citation
one or more processors configured to classify, for a first end-user application... whether or not the first end-user application, when running, is interacting in the device display foreground with the user; The Android OS on the accused devices classifies applications as running in the foreground or background. ¶49 col. 1:15-23
for a time period when data for Internet service activities is communicated through a WWAN modem connection... apply a first differential traffic control policy... such that Internet service activity on behalf of the first end-user application is disallowed when the one or more processors classify the first end-user application as not interacting in the device display foreground with the user; When "Data Saver" mode is active, the Android OS applies a policy that disallows background data activity for most applications over the WWAN (cellular) network. ¶49 col. 1:24-36
indicate to the first end-user application, via an application program interface (API), one or more network access conditions based on the applied first differential traffic control policy, including a first network access condition that indicates the unavailability... of Internet data service that is available via the WWAN modem; The Android ConnectivityManager.NetworkCallback API allegedly indicates to applications that the network is unavailable via the onBlockedStatusChanged() method when background data is disallowed by the "Data Saver" policy. ¶49 col. 1:37-56
  • Identified Points of Contention:
    • Scope Questions: A question for claim construction may be whether Android's system-wide foreground/background classification meets the claim limitation of classifying "for a first end-user application," which could be interpreted to require a more individualized, application-specific classification process.
    • Technical Questions: An evidentiary question will be whether the general onBlockedStatusChanged() callback in the Android API "indicates" the specific condition required by the claim-that is, unavailability based on the applied... policy. The defense may argue this is a generic "network is blocked" signal, not a specific indication tied to the policy of disallowing background data.

V. Key Claim Terms for Construction

Terms from the '364 Patent

  • The Term: "first service policy"
  • Context and Importance: The viability of the infringement case for the '364 Patent depends on whether the accused "Data Saver" feature, a user-controlled OS setting, can be construed as a "service policy." Practitioners may focus on this term because the patent's specification repeatedly describes complex, carrier-integrated service management systems, which may suggest a narrower definition than what is accused.
  • Intrinsic Evidence for Interpretation:
    • Evidence for a Broader Interpretation: The patent abstract describes the policy as being for "at least assisting in applying the first service policy," which may support an interpretation that includes simpler, user-facing features. '364 Patent, abstract
    • Evidence for a Narrower Interpretation: The specification describes embodiments where policies are deeply integrated with a "Service Controller" and central billing systems, suggesting a more complex, carrier-managed system than a simple OS toggle. ('364 Patent, FIG. 16; '364 Patent, col. 9:1-10:55).

Terms from the '976 Patent

  • The Term: "indicate to the first end-user application... a first network access condition that indicates the unavailability... of Internet data service"
  • Context and Importance: The infringement allegation hinges on construing a general Android API callback (onBlockedStatusChanged) as providing the specific indication required by the claim. The case may turn on whether this generic callback is sufficient to meet the claim's requirement that the "unavailability" is indicated as being "based on the applied first differential traffic control policy."
  • Intrinsic Evidence for Interpretation:
    • Evidence for a Broader Interpretation: The patent states the processor is configured to "indicate... one or more network access conditions," which could be read broadly to include any signal that informs the app about network status changes. ('976 Patent, col. 106:21-25).
    • Evidence for a Narrower Interpretation: The claim explicitly links the "network access condition" to the "applied first differential traffic control policy." ('976 Patent, claim 1). This language may support an argument that the API must communicate not just that the network is unavailable, but that it is unavailable because of the policy, a level of specificity a generic callback may not provide.

VI. Other Allegations

  • Indirect Infringement: The complaint alleges that Defendants induce infringement by actively encouraging and instructing customers to use the accused instrumentalities (e.g., through user manuals and marketing for features like "Data Saver") in ways that directly infringe the asserted patents. (Compl. ¶¶37, 42, 48, 53, 59, 64).
  • Willful Infringement: The complaint alleges willful infringement based on both post-suit and alleged pre-suit knowledge. It asserts knowledge "at least as of the filing and service of this Complaint" and also alleges pre-suit knowledge by stating that patents assigned to Defendants cite family members of the asserted patents. (Compl. ¶¶39, 41, 50, 52, 61, 63).

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

  1. A primary issue will be one of definitional scope: Can the term "service policy," as described in the '364 Patent in the context of complex, carrier-integrated systems, be construed broadly enough to cover a simple, user-controlled operating system feature like Android's "Data Saver" mode?
  2. A central question of functional operation will be: Does a general-purpose Android API callback, which signals a generic "blocked" network status, perform the specific function of "indicating... unavailability... based on the applied... policy" as required by claim 1 of the '976 Patent, or is there a mismatch in the specificity of the information conveyed?
  3. A key architectural question across all patents will be: Do the general-purpose components of the Android operating system (such as ConnectivityManager, MediaPlayer, and TrafficStats) constitute the specific, interconnected "agents" and "managers" described in the patents' more structured architectures, or does this represent a fundamental architectural divergence that precludes literal infringement?
Loading Complaint