Obviousness

Under 35 U.S.C. § 103, a patent claim is obvious if the differences between the claimed invention and the prior art are such that the subject matter as a whole would have been obvious at the time the invention was made to a person having ordinary skill in the art (PHOSITA). For this analysis, a PHOSITA in the context of US patent 9609544 would possess expertise in telecommunications, wireless network engineering, mobile device software and hardware, network traffic management, and potentially billing systems. The prior art date for this patent is 2009-01-28.

The patent itself describes the existing problems and conventional approaches that constitute the implicit prior art against which the invention is set. It notes a "network capacity crunch" due to increasing network congestion on wireless networks, with a small number of users demanding a disproportionately significant amount of capacity.

The independent claims (1, 18, and 24) of US patent 9609544 broadly cover a method, a communications device, and a system for protecting network capacity by controlling network service usage activities at the device level through monitoring, classification, and policy association.

Implicit Prior Art References from the Patent's Background

Based on the patent's own description of the state of the art and the problems it seeks to solve, two main areas of prior art can be identified:

1. Centralized Network Capacity Management Systems (PA1):

• Description: Prior to the invention, network carriers commonly employed centralized systems to manage network capacity, traffic, and Quality of Service (QoS). The patent explicitly states that "Network carriers have typically attempted to manage network capacity using various purely central/core network based approaches." These systems were capable of monitoring network traffic, classifying it (e.g., into QoS classes like conversational, streaming, interactive, and background), and enforcing policies (e.g., throttling, prioritizing different traffic types) to protect network capacity and ensure desired service levels. The concepts of QoS, various QoS classes, and how they differentiate services were well-understood in telecommunications. Furthermore, the patent mentions that "network performance measures can be advantageously maintained or improved as network loading increases if capacity management and/or network resource management is employed," indicating a known desire and existing methods for capacity management.
• Relevance: PA1 teaches centralized monitoring, classification, policy-based differential control, and the goal of network capacity protection.

2. Device-Side Network Connection Management for Device Optimization (PA2):

• Description: Devices, particularly mobile devices, were known to implement features that influenced their network interactions, often for local benefits such as power saving. The patent notes that "mobile devices typically have specialized designs that are optimized to preserve network capacity and protect network resources from being over taxed." A specific example provided is the "fast dormancy feature, which allows the mobile device to quickly make a query to the radio network controller to release the connection so that it can return to the idle state faster" to "save battery life on their devices." This demonstrates that devices possessed the capability to monitor their own state and initiate actions that affect network resource usage, even if the primary motivation was device-centric rather than network-centric capacity protection.
• Relevance: PA2 teaches device-side monitoring and control over network connections, albeit for device-specific goals.

Obviousness Analysis

Motivation to Combine PA1 and PA2:
A PHOSITA, observing the "network capacity crunch" and the inherent inefficiencies of "purely centralized network solutions", would have been motivated to find more effective ways to protect network capacity. The patent itself highlights a key problem: "if the activity is blocked somewhere in the network behind the base station after over the air (OTA) spectrum bandwidth is consumed to open or begin to open a communication socket, then there can still be an appreciable amount of network capacity or resources consumed even though the data transfer is not allowed to complete." This problem demonstrates that purely centralized control can lead to wasted network resources because traffic is only managed after it has already consumed some network resources.

Recognizing the device's capability for self-management regarding network connections (as shown by fast dormancy in PA2), it would be obvious to a PHOSITA to extend this device-side intelligence, previously used for device-specific benefits (like battery life), to assist in the broader goal of network capacity protection (as addressed by PA1). The motivation would be to improve overall network efficiency and reduce wasted network resources by preventing unnecessary or low-priority network access attempts and data transfers at the source—the device itself. This approach addresses the inefficiency of centralized control by shifting some management closer to the traffic origin.

Application to Independent Claims:

Claim 1 (Method):

• Monitoring network service usage activity of a communications device: Given that network systems (PA1) monitor service usage for QoS and billing, and devices (PA2) monitor their connection states for features like fast dormancy, it would have been obvious for a PHOSITA to enable a device to monitor its own specific service usage activities (e.g., by application, operating system function, or at the packet level). This simply involves applying known monitoring techniques at a different point in the network architecture.
• Classifying the network service usage activity for differential network access control for protecting network capacity: PA1 teaches the classification of network traffic for differential treatment based on QoS. The goal of "protecting network capacity" was a known problem. It would be an obvious step to apply these known classification principles at the device level (as in PA2) to enable differentiated control over the device's own traffic, particularly for applications identified in the patent as "greedy" or consuming significant resources (e.g., background updates, frequent signaling).
• Associating the network service usage activity with a network service usage control policy based on a classification of the network service usage activity to facilitate differential network access control for protecting network capacity: PA1 teaches that network management relies heavily on policies for QoS and traffic control. The patent itself acknowledges that "access service control policies" can be "implemented in the device". Therefore, if devices can monitor and classify their activities, it would be obvious to a PHOSITA to associate these classified activities with specific control policies (e.g., deferring or throttling background downloads when the network is busy, as a means to protect network capacity). This transfers a known network management paradigm (policy-based control) to the device, driven by the motivation to improve efficiency by controlling traffic at the source.

Claim 18 (Communications Device):
A communications device (PA2) inherently includes a processor and memory. Implementing the method of Claim 1 on such a device would be an obvious engineering choice for a PHOSITA. The modification involves configuring existing hardware and software to perform the monitoring, classification, and policy enforcement functions for network capacity protection, which are extensions of capabilities already present in devices (e.g., self-monitoring, local control over network access). The patent broadly states that the invention can be implemented as a computer program product or a processor configured to execute instructions, reinforcing the idea that such a device adaptation is within the skill of the art.

Claim 24 (System):
The system combines a service controller (representative of centralized network management in PA1) and a communications device with a device-based service processor (representative of the extended capabilities of PA2).

• Service controller: This element is a standard component in centralized network management (PA1) responsible for managing network policies and usage.
• Communications device with device-based service processor: As argued for Claim 18, equipping a device with a processor to perform monitoring, classification, and policy enforcement for network capacity protection would be obvious.
• Communication between service controller and device-based service processor: Given that centralized network management systems (PA1) communicate policies to network elements, and devices (PA2) already communicate with the network (e.g., for connection management), it would be an obvious design choice to establish a communication mechanism for the service controller to relay capacity protection policies to the device's service processor, or for the device to report relevant information back. The patent explicitly describes "communicating it over a network connection to a network element (e.g., a service controller or another network element/function)," further highlighting the obviousness of this interaction in the context of device-assisted services.

In conclusion, the claimed invention in US patent 9609544, which involves device-assisted services for protecting network capacity through monitoring, classification, and policy-based differential network access control, would have been obvious to a person having ordinary skill in the art by combining the known concepts of centralized network capacity management (PA1) with existing device-side network control capabilities (PA2). The motivation for this combination is directly found in the acknowledged "network capacity crunch" and the desire to overcome the inefficiencies of purely centralized network management approaches by leveraging the device's ability to control its network interactions at the source.