Wireless end-user device with differentiated network access and access status for background and foreground device applications

Patent No. US9143976 (titled "Wireless end-user device with differentiated network access and access status for background and foreground device applications") on Apr 1, 2015. The application was issued on Sep 22, 2015.

What is this patent about?

’976 is related to the field of wireless network management and device-assisted traffic control. Specifically, it addresses the challenge of preserving network capacity on wireless wide-area networks (WWAN) by managing the data consumption of applications that may operate in the background without the user’s immediate knowledge or benefit. The technology focuses on end-user devices equipped with multiple modems, such as WWAN and WLAN, and provides a mechanism to intelligently regulate network access based on the operational state of an application.

The underlying idea behind ’976 is that network resources are often wasted by applications performing non-essential data transfers while they are not actively being used. The invention introduces a differential traffic control policy that distinguishes between an application interacting in the device foreground and one running in the background. By monitoring the user's interaction with the device display, the system can selectively block or allow network access, ensuring that high-cost or congested WWAN bandwidth is reserved for services that provide immediate value to the user.

The claims of ’976 focus on a wireless device that utilizes a specialized application program interface (API) to communicate network availability to individual applications based on their foreground or background status. The independent claims describe a processor configured to classify whether an application is interacting in the display foreground and, during WWAN usage, apply a policy that disallows data activity for that application if it is in the background. Crucially, the API provides a specific network access condition to the application, effectively signaling that the Internet is unavailable only when the application is not in the foreground.

In practice, the device implements this by monitoring application states and intercepting network requests. When the device is connected to a WWAN, the system uses the API to provide a spoofed or emulated network status to background applications. For example, if a background process attempts to sync data, the API returns a condition indicating that the data service is unavailable, even if the modem is active for other foreground tasks. This prevents the application from repeatedly attempting to connect and consuming signaling resources, thereby reducing unnecessary network chatter and preserving battery life.

This approach differs from prior solutions by moving the intelligence from the core network to the device itself, allowing for more granular control without the privacy concerns or overhead of Deep Packet Inspection (DPI). Unlike traditional Quality of Service (QoS) which manages traffic by priority levels, this invention uses foreground classification as a binary trigger for network access via a WWAN modem. By signaling unavailability through an API, the invention ensures that applications respond predictably to blocked access, preventing the aggressive re-try cycles that typically plague centralized blocking methods.

How does this patent fit in bigger picture?

Technical Landscape

In the mid-2010s when ’976 was filed, wireless network management was typically implemented using purely centralized core network solutions where traffic control occurred behind the base station. At a time when mobile devices were increasingly transitioning from specialized, carrier-certified designs to general-purpose Internet architectures, systems commonly relied on standard HTTP protocols that were not optimized for radio access constraints. This era faced a technical landscape where hardware and software constraints made the management of signaling-heavy background tasks—such as cloud synchronization, frequent widget updates, and aggressive modem power-state cycling—non-trivial, often leading to network resource exhaustion even when aggregate data throughput remained low.

Prosecution Position

The disclosed invention represents a technical advancement through an architectural shift from centralized network management to Device Assisted Services (DAS) that integrate device-side intelligence with network-based control. By implementing a service processor on the device, the system enables the differential classification and control of network service usage activities at the source of demand. This integration allows for the technical effect of mitigating network congestion by dynamically managing background traffic, signaling frequency, and modem power transitions based on real-time network busy states. The solution overcomes the technical constraint of 'blind' network-side blocking—which often consumes over-the-air resources before a connection is terminated—by intercepting and managing access requests locally, thereby preserving radio access network capacity and improving overall system availability.

Claims

This patent contains 29 claims, with claim 1 serving as the sole independent claim. The independent claim focuses on a wireless end-user device equipped with both WWAN and WLAN modems that utilizes a processor to classify whether an application is interacting in the foreground of the device display and applies a differential traffic control policy that disallows background Internet activity over the WWAN while communicating these network access conditions to the application via an API. The dependent claims further define the system by specifying classification criteria based on user benefit, providing user interfaces for policy management, detailing multimode profiles for different network types, and describing specific API functions such as emulating network messaging or instructing applications to transition to different states based on power levels or roaming status.

Key Claim Terms New

Definitions of key terms used in the patent claims.

Term (Source)Support for SpecificationInterpretation
Application program interface (API)
(Claim 1)
An API is provided so that application developers can use standard interface commands to request and set up QoS channels or receive network access conditions. The API can inform the application whether a desired channel can be created and coordinate the connection with the desired QoS class. This allows applications to optimize network service usage activities based on a current network busy state or access settings.A software interface that allows the device's service processor to communicate network status, access grants, or restrictions directly to an application, enabling the application to be 'aware' of capacity controls.
Device display foreground
(Claim 1)
Classification rules can include examining if the service usage activity UI content is in the foreground of the device UI. A service usage activity is determined to be an active application or process based on a user interaction with the device and/or network service usage activity. This facilitates identification of a snapshot of service class use at a given time based on user interaction.The active, visible state of a user interface on the device screen where an application is currently interacting with the user, as opposed to running in the background.
Differential traffic control policy
(Claim 1)
Techniques for protecting network capacity include differentially controlling these types of network service usage activities in various ways depending on the type of service activity requesting network access. Control policies can include block/allow, throttle, delay, priority queue, time window, suspend, quarantine, or kill. These policies facilitate differential control of certain services to reduce network congestion and increase network availability.A set of rules that applies different network access constraints (such as disallowing, throttling, or delaying data) to specific applications or service activities based on their classification or the current network state.
Interacting in the device display foreground
(Claim 1)
Classification rules can include examining if the service usage activity UI content is in the foreground of the device UI or if the user has interacted with the service usage activity. A service activity can be classified as a background service when the device has been inactive or the user has not interacted with it for a period of time. This distinguishes between active user interaction and background functions like cloud synchronization or RSS feeds.A state where an application is actively visible to the user on the device screen and is the primary focus of user input or engagement, as opposed to running as a background process.
Internet service activities
(Claim 1)
Examples of a network service usage activity include a voice connection, device application or widget connection, email text or download connection, file download, streaming media, and software updates. It also includes background signaling sequences to update widgets, synchronize user data, or check RSS feeds. These activities are monitored at the packet, network stack, or application level to manage network capacity.Data-related tasks performed by applications or the operating system, including background signaling, data synchronization, media streaming, or web browsing, that require a network connection.
Network access conditions
(Claim 1)
The API facilitates communication of network access conditions, such as network busy state, network availability state, or current network access settings like allow/block and defer. These conditions are based on the applied service usage control policy for the network service usage activities to protect network capacity. This informs the application of the performance level or congestion state of the network edge element.The status of network availability or specific constraints (such as 'unavailability' or 'availability') communicated to an application that dictate whether it can transmit or receive data over a specific modem connection.

Litigation Cases New

US Latest litigation cases involving this patent.

Case NumberFiling DateTitle
4:25-cv-09558Nov 5, 2025Google LLC v. Headwater Research LLC
3:25-cv-07591Sep 5, 2025Apple Inc v. Headwater Research LLC
5:25-cv-07453Sep 3, 2025Google LLC v. Headwater Research LLC

Patent Family

Patent Family

File Wrapper

The dossier documents provide a comprehensive record of the patent's prosecution history - including filings, correspondence, and decisions made by patent offices - and are crucial for understanding the patent's legal journey and any challenges it may have faced during examination.

  • Get instant alerts for new documents

US9143976

Application Number
US14676704A
Filing Date
Apr 1, 2015
Publication Date
Sep 22, 2015
External Links
Slate, USPTO , Google Patents