Wireless end-user device with differentiated network access status for different device applications

Patent No. US9179359 (titled "Wireless end-user device with differentiated network access status for different device applications") on Mar 30, 2015. The application was issued on Nov 3, 2015.

What is this patent about?

’359 is related to the field of wireless network management and device-level traffic control. As mobile devices increasingly rely on both high-capacity local networks and resource-constrained wide-area networks, service providers face challenges in maintaining network performance during periods of high demand. Traditional network-side solutions often struggle to manage granular application behavior, leading to congestion and inefficient resource allocation when background processes or data-heavy applications compete for limited bandwidth.

The underlying idea behind ’359 is to implement intelligent, application-specific traffic management directly on the end-user device rather than relying solely on core network equipment. By utilizing a device-based service processor, the system can distinguish between different types of data traffic at the application layer. This allows the device to apply a differential traffic control policy that selectively restricts or enables network access for specific applications based on the type of wireless connection currently in use, such as a cellular wide-area network versus a local Wi-Fi connection.

The claims of ’359 focus on a wireless device equipped with both a WWAN modem and a WLAN modem that utilizes an internal processor to enforce specific data access rules. The core mechanism involves an application program interface (API) that communicates network availability status to individual applications. Specifically, the independent claims cover the ability of the device to indicate to a particular application that the Internet service is unavailable, even while that same service remains active and accessible to other applications on the same device.

In practice, the invention functions as a gatekeeper that manages the device's interaction with the cellular network. When the device is connected to a WWAN, the service processor evaluates the active applications against a stored policy. If an application is classified as a background service or a non-essential data consumer, the API sends a signal—such as a spoofed network error or an unavailability notification—to that specific application. This prevents the application from initiating data transfers that would otherwise contribute to network congestion or exhaust the user's data plan.

This approach differs from prior solutions by moving the enforcement point from the network core to the device edge, allowing for much higher granularity. Unlike standard Quality of Service (QoS) methods that prioritize traffic types across the entire pipe, this system can completely hide the network's existence from specific software entities. By managing these connections at the source, the invention reduces signaling overhead and prevents unnecessary radio power cycles, protecting the capacity of the wireless wide-area network more effectively than centralized filtering.

How does this patent fit in bigger picture?

Technical Landscape

In the mid-2010s when ’359 was filed, wireless network architectures were increasingly strained by a transition where mobile devices began to function as general-purpose internet nodes at a time when network capacity was typically implemented using purely centralized or core-network-based management. When systems commonly relied on core network equipment to block or throttle traffic after over-the-air spectrum resources had already been consumed, the resulting signaling overhead often outpaced actual data traffic growth. During this era, hardware and software constraints made it non-trivial to manage the high frequency of background signaling and inefficient network access attempts generated by always-on applications, which frequently triggered resource-intensive modem power state transitions and session establishments even when no active user interaction was occurring.

Prosecution Position

The disclosed invention represents a meaningful technical advancement through an architectural shift toward device-assisted service (DAS) management that protects network capacity at the source of demand. By integrating a service processor directly on the device to monitor and classify network service usage activities—such as background synchronization, software updates, and signaling-heavy applications—the system enables differential network access control based on a dynamic network busy state. This structural solution achieves the technical effect of reducing over-the-air resource consumption and signaling flooding by implementing local traffic control policies, such as delaying, throttling, or windowing background tasks. This approach overcomes the technical constraint of centralized network solutions that cannot prevent the initial consumption of radio access bearer resources or provide real-time user interface feedback regarding capacity-based traffic restrictions.

Claims

This patent contains 29 total claims, with claim 1 serving as the sole independent claim. The independent claim focuses on a wireless end-user device equipped with both wide area and local area network modems and a processor configured to enforce differential traffic control policies, specifically using an application program interface to signal network unavailability to specific applications even when data services remain active for others. The dependent claims further elaborate on this system by specifying methods for emulating network messaging, incorporating user interface notifications for policy changes, defining multimode profiles for different network types, and detailing various triggers for dynamic policy adjustments such as device power states, roaming status, and user interaction levels.

Key Claim Terms New

Definitions of key terms used in the patent claims.

Term (Source)Support for SpecificationInterpretation
Application program interface (API)
(Claim 1)
In some embodiments, a QoS API is provided in the device service processor that applications use to request a QoS class or QoS channel connection. The API accepts QoS requests from an application, formats the QoS channel request into a protocol appropriate for transmission to network equipment, and informs the application that the desired QoS channel can be created or not. The API can be used to communicate network access conditions, network busy state, or network availability state of one or more networks to a network service activity.A software interface that facilitates communication between the device's service processor and applications to convey network access conditions, grants, or constraints based on the current service policy.
Network access conditions
(Claim 1)
The API facilitates communication of one or more of the following: network access conditions, network busy state or network availability state of one or more networks or alternative networks. In some embodiments, an emulated network API can intercept, modify, block, remove, and/or replace network socket application interface messages. Before a connection is allowed to be opened, it is blocked and a message is sent back to the application to indicate that the network access attempt was not allowed/blocked, that the network is not available, and/or to try again later.Information provided to an application regarding the status or availability of network resources, which may include emulated or spoofed messages indicating the network is unavailable even if a physical connection exists.
Unavailability to the particular application
(Claim 1)
In some embodiments, the determination of which devices or applications to throttle back can be made based on the device traffic usage patterns. Higher QoS level traffic cannot be throttled in such circumstances, such as VOIP traffic, while lower priority traffic such as interactive browsing and/or background download are throttled and/or blocked. This allows for differential control where one application is blocked or delayed while another is allowed to complete its data transfer.A state where a specific application is restricted from accessing the Internet data service based on policy, while other applications on the same device are simultaneously permitted to access the same service.
WWAN differential traffic control policy
(Claim 1)
Techniques are needed to preserve network capacity by, for example, differentially controlling these types of network service usage activities in various ways depending on the type of service activity requesting network access. The device service processors connected to an overly busy base station can be instructed to reduce the traffic control priority for one or more classes of QoS traffic, reducing the queuing priority, throttling rate, delay and/or access allowance for some or all of one or more classes of traffic. In some embodiments, the various techniques described herein related to DAS for providing network capacity and/or QoS for DAS are applied to dynamic QoS related techniques.A set of rules stored on the device used to treat Internet data traffic differently based on the specific application or service activity requesting network access, specifically applied to wireless wide area network connections to protect network capacity.
WWAN modem
(Claim 1)
Wireless devices that browse the Internet often use specialized protocols rather than standard HTTP protocols. The device behavior can consume a proportionally large amount of resources such that the network ability to support multiple devices is diminished. In some embodiments, the modem subsystem power cycling or transitions from one power save state to another can impact network performance.A hardware component (Wireless Wide Area Network modem) enabling the device to communicate Internet data over cellular-type networks such as 3G, 4G, or LTE.

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

US9179359

Application Number
US14673625A
Filing Date
Mar 30, 2015
Publication Date
Nov 3, 2015
External Links
Slate, USPTO , Google Patents