DCT

2:23-cv-00379

Headwater Research LLC v. T-Mobile US Inc

I. Executive Summary and Procedural Information

  • Parties & Counsel:
  • Case Identification: 2:23-cv-00379, E.D. Tex., 09/16/2025
  • Venue Allegations: Plaintiff alleges venue is proper in the Eastern District of Texas because T-Mobile has committed acts of infringement in the District, maintains a regular and established place of business in the District, and conducts extensive business including selling the accused products and advertising its network coverage within the District.
  • Core Dispute: Plaintiff alleges that Defendant’s mobile electronic devices and cellular networks infringe patents related to device-assisted management of wireless network capacity and traffic control.
  • Technical Context: The technology addresses the management of data traffic on cellular networks, a field of increasing importance due to the exponential growth in mobile data consumption driven by smartphones and applications.
  • Key Procedural History: The complaint alleges a multi-year pre-suit relationship (2010-2016) between Plaintiff’s predecessor-in-interest, ItsOn Inc., and Defendant Sprint (now part of T-Mobile). This alleged collaboration included non-disclosure agreements, technical meetings to implement Headwater's patented technology on Sprint’s network and Samsung devices, and the disclosure of the patents-in-suit. This history forms the basis for Plaintiff's allegations of pre-suit knowledge and willful infringement.

Case Timeline

Date Event
2009-01-28 Earliest Priority Date for ’541 Patent and ’613 Patent
2010-04-01 ItsOn and Sprint enter into an NDA
2011-01-01 Plaintiff Headwater was formed
2013-01-01 ItsOn and Sprint begin implementing use cases of Headwater's technologies
2013-11-19 U.S. Patent No. 8,589,541 Issues
2015-10-01 Sprint and Samsung allegedly plan to implement technology without ItsOn
2015-12-15 U.S. Patent No. 9,215,613 Issues
2020-04-01 T-Mobile and Sprint merger closes
2025-09-16 Complaint Filed

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

U.S. Patent No. 8,589,541 - Device-assisted services for protecting network capacity

  • Patent Identification: U.S. Patent No. 8589541, “Device-assisted services for protecting network capacity,” issued November 19, 2013. (Compl. ¶41).

The Invention Explained

  • Problem Addressed: The patent’s background describes a growing “network capacity crunch” in wireless networks, where increasing data demand from mobile devices degrades overall network performance and user experience. (’541 Patent, col. 9:56-10:21).
  • The Patented Solution: The invention proposes a system of “Device-Assisted Services” (DAS) where a “service processor” on the end-user device cooperates with a network-based “service controller.” (’541 Patent, Abstract). This device-side processor monitors network service usage, classifies the activity (e.g., as foreground or background), and applies differential traffic control policies based on factors like network congestion, allowing for more granular management of network resources directly at the source of the demand. (’541 Patent, col. 16:50-17:2; Fig. 3).
  • Technical Importance: This approach moves network management intelligence from being purely centralized in the carrier’s core network to the edge of the network (the device itself), enabling more responsive and efficient traffic shaping to mitigate congestion. (Compl. ¶¶9-10).

Key Claims at a Glance

  • The complaint asserts independent claim 1. (Compl. ¶67).
  • The essential elements of independent claim 1 are:
    • A non-transitory computer-readable storage medium with machine-executable instructions for a wireless end-user device.
    • The instructions cause one or more processors to identify a service usage activity of the device.
    • Determine at least an aspect of a policy based on user input, where the policy applies if the service usage activity is a background activity.
    • Determine if the service usage activity is the background activity.
    • If it is a background activity, apply the policy.
  • The complaint alleges infringement of "multiple claims," including independent claim 1, thereby reserving the right to assert other claims. (Compl. ¶70).

U.S. Patent No. 9,215,613 - Wireless end-user device with differential traffic control policy list having limited user control

  • Patent Identification: U.S. Patent No. 9215613, “Wireless end-user device with differential traffic control policy list having limited user control,” issued December 15, 2015. (Compl. ¶42).

The Invention Explained

  • Problem Addressed: The patent addresses the technical challenge of allowing a network operator to enforce traffic control policies on a user's device to preserve network capacity, while still providing the user with a degree of control over their device's applications. (’613 Patent, Background, col. 7:56-8:20).
  • The Patented Solution: The invention is a wireless device that maintains a “differential traffic control policy list.” This list distinguishes a first set of applications (e.g., user-installed apps) from a second set of applications or services (e.g., core OS functions). (’613 Patent, Abstract). The device provides a user interface that allows the user to “augment” or modify the traffic control policy for the first set of applications, but does not allow the user to control the policy for the second set, thereby giving the network operator ultimate control over essential services while offering limited flexibility to the user. (’613 Patent, col. 71:43-72:42).
  • Technical Importance: This patented solution provides a technical framework for balancing the competing interests of network operators (who need to manage traffic) and end-users (who desire control over their devices), a central issue in the operation of modern mobile ecosystems. (Compl. ¶39).

Key Claims at a Glance

  • The complaint asserts independent claim 1. (Compl. ¶80).
  • The essential elements of independent claim 1 are:
    • A wireless end-user device with WWAN and WLAN modems and a non-transient memory.
    • The memory stores a "differential traffic control policy list" that distinguishes between a first set of applications and a second set of applications/services.
    • The memory also stores a policy applicable to the first set of applications.
    • An interface allows a user to "augment" the policy for the first set of applications but not for the second set.
    • Processors are configured to classify the network type, classify application activity as foreground/background, and selectively allow/deny service activities based on the policy list, policy, and user augmentation.
  • The complaint alleges infringement of "multiple claims," including independent claim 1. (Compl. ¶83).

III. The Accused Instrumentality

Product Identification

  • The Accused Instrumentalities include mobile electronic devices (e.g., phones, tablets) and the associated cellular networks, servers, and services sold and operated by Defendants T-Mobile and Sprint. (Compl. ¶15, 49).

Functionality and Market Context

  • The complaint alleges that the accused products and services incorporate functionalities that help manage data consumption and network connectivity, such as "roaming controls, background controls, data offloading, family device management," and on-demand data purchasing. (Compl. ¶19). These features are positioned as solutions to help customers "save data, reduce power consumption, and stay connected" in a market characterized by explosive mobile data growth. (Compl. ¶39). The complaint provides a chart from Ericsson illustrating the dramatic increase in mobile data traffic from 2011 projected through 2027. (Compl. p. 6).

IV. Analysis of Infringement Allegations

The complaint references claim charts attached as Exhibits 3 and 4 purporting to detail the infringement of claim 1 of the ’541 Patent and claim 1 of the ’613 Patent, respectively. (Compl. ¶¶67, 80). As these exhibits were not provided, the infringement theories are summarized below in narrative form.

  • '541 Patent Infringement Allegations: The complaint's narrative suggests that Defendants' mobile devices infringe claim 1 by implementing features that manage background data. This technology is alleged to identify an application's data usage (a "service usage activity"), determine if the user is actively engaged with it (i.e., if it is a "background activity"), and then apply a network operator or user-defined "policy" (e.g., restricting or blocking data) to that activity. (Compl. ¶¶19, 39, 65). The complaint points to T-Mobile's advertising of its network coverage in the Eastern District of Texas, including a coverage map, as evidence of infringing use in the district. (Compl. p. 13).

  • '613 Patent Infringement Allegations: The infringement theory for the ’613 Patent appears to focus on data-saver or application-control settings on Defendants' devices. The complaint alleges these devices use a "differential traffic control policy list" that separates user-installed applications from other system services. It is alleged that the device's user interface allows a user limited control to "augment" the policy for the user-installed apps (e.g., by allowing or disallowing background data for a specific app) but prevents the user from modifying the policy for the other system services. (Compl. ¶¶19, 39, 78). The complaint includes a screenshot of T-Mobile's store locator for Marshall, Texas, as an example of where accused devices are sold within the district. (Compl. p. 14).

  • Identified Points of Contention:

    • Scope Questions: For the ’541 Patent, a central question may be whether a general-purpose "data saver" mode, which may apply a single rule to all applications not in the foreground, meets the claim limitation of identifying a specific "service usage activity" and then determining if it is a "background activity" before applying a policy. For the ’613 Patent, a dispute may arise over whether the accused devices' settings menu constitutes the claimed "differential traffic control policy list" that formally distinguishes between a first and second set of applications, and whether user control is limited in the specific manner recited.
    • Technical Questions: Evidentiary questions may focus on the technical implementation of the accused features. For the ’541 Patent, what evidence shows that the accused devices perform the specific step of determining if an activity is "background" before applying a policy, as opposed to simply applying a policy to all non-foreground processes? For the ’613 Patent, what technical mechanisms prevent a user from altering the data policies for the alleged "second" set of applications and/or services?

V. Key Claim Terms for Construction

  • The Term: "background activity" (’541 Patent, Claim 1)

  • Context and Importance: The infringement analysis for the ’541 Patent depends on whether a "service usage activity" is determined to be a "background activity." The scope of this term will be critical in determining if standard data-saving features in modern mobile operating systems fall within the claim.

  • Intrinsic Evidence for Interpretation:

    • Evidence for a Broader Interpretation: The specification suggests a broad definition, contrasting it with activity in the "foreground of user interaction." (’541 Patent, col. 110:35-39). This could support an interpretation covering any application or process not currently on the user's screen.
    • Evidence for a Narrower Interpretation: The patent provides several specific examples of background services, including "a software update, a firmware update, a file download, streaming media... a web browser or a sync, or a synchronization service." (’541 Patent, col. 110:57-62). This language may support a narrower construction limited to automated or non-interactive processes.
  • The Term: "differential traffic control policy list" (’613 Patent, Claim 1)

  • Context and Importance: Infringement of the ’613 Patent requires the presence of this "list." Practitioners may focus on whether this term requires a specific data structure received from the network or if it can read on the functional grouping of applications presented in a device's settings menu.

  • Intrinsic Evidence for Interpretation:

    • Evidence for a Broader Interpretation: The specification describes the list using functional identifiers, such as "application identifiers, OS function identifiers, aggregate service activity identifiers," which could support construing the term to cover a logical grouping of applications, however implemented. (’613 Patent, col. 72:51-54).
    • Evidence for a Narrower Interpretation: The specification describes the list in the context of a "launch intercept manager," which may suggest a more formal, pre-defined data structure used by the operating system to check an application's status before it runs, rather than just a menu for user settings. (’613 Patent, col. 72:47-50).

VI. Other Allegations

  • Indirect Infringement: The complaint alleges both induced and contributory infringement. Inducement allegations are based on Defendants instructing customers on how to use the accused data-saving and traffic-control features. (Compl. ¶¶65, 71, 78). The allegations of knowledge and intent for both forms of indirect infringement are heavily based on the alleged pre-suit business relationship between ItsOn and Sprint, during which Headwater’s technology and patents were allegedly disclosed and implemented on Sprint devices. (Compl. ¶¶68, 81).
  • Willful Infringement: Willfulness allegations are predicated on pre-suit knowledge of the patents. The complaint specifically alleges that ItsOn software installed on millions of Sprint devices between 2013-2016 contained a patent marking notice listing the ’541 Patent and patents in the same family as the ’613 Patent. (Compl. ¶¶68, 81). This is supplemented by allegations of direct communications between ItsOn, Sprint, and Samsung regarding Headwater's intellectual property. (Compl. ¶¶68, 81).

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

  • A core issue will be one of claim scope: can claim terms like "background activity" and "differential traffic control policy list", which are described with specific technical context in the patents, be construed broadly enough to read on the general-purpose data management and data saver features common in modern mobile operating systems?
  • A central evidentiary question will be one of historical conduct: what was the precise nature of the technology and intellectual property disclosed during the ItsOn-Sprint relationship, and to what extent does that evidence demonstrate that Defendants had pre-suit knowledge of the patents and subsequently incorporated the patented technology into their own systems, which is critical for the allegations of indirect and willful infringement?
  • A key technical question will be one of operational mapping: does the actual software logic of T-Mobile’s accused features, such as background data restriction, perform the specific, ordered steps required by the asserted method claims, or does it achieve a similar outcome through a technically distinct process that falls outside the literal scope of the claims?