US 9609544

Here's a concise summary of US patent 9609544:

US Patent 9609544: Device-assisted services for protecting network capacity

• Title: Device-assisted services for protecting network capacity
• Assignee: Headwater Research LLC
• Inventors: Gregory G. Raleigh, Alireza Raissinia, James Lavine
• Filing Date: 2013-11-15
• Issue Date: 2017-03-28
• Abstract: Techniques are described for protecting network capacity by controlling network service usage activities of a communications device in wireless communication with a network. Such techniques include monitoring a network service usage activity of the communications device in network communication; classifying the network service usage activity for differential network access control for protecting network capacity; and 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.

Plain-Language Overview of Independent Claims:

• Claim 1 (Method): This claim describes a method for managing network capacity. It involves a communications device monitoring its own network activities. These activities are then categorized so that network access can be controlled differently for each category, specifically to prevent network overload. A specific set of rules (a control policy) is then applied to these categorized activities to regulate their network access and help preserve overall network capacity.
• Claim 18 (Communications Device): This claim describes a communications device (like a smartphone or tablet) equipped with a processor and memory. This device is designed to carry out the method of Claim 1. Specifically, it monitors its network activities, assigns them to different classifications to enable varied network access controls for capacity protection, and then enforces a control policy based on these classifications to manage its network usage.
• Claim 24 (System): This claim outlines a system for protecting network capacity. The system includes a central "service controller" that manages network usage rules and a "communications device" (as described in Claim 18) that connects to this controller. The device contains a "device-based service processor" which is responsible for monitoring its network activities, classifying them for differentiated network access control to protect network capacity, and applying a control policy based on this classification to manage network access. The system works by coordinating the device's local actions with the broader network policies.

CAFC 2026 Dockets:
A search of the CAFC 2026 dockets did not explicitly return any scheduled cases or specific litigation directly naming US patent 9609544 in the provided search snippets for May or June 2026. More detailed searching within the CAFC database would be required to definitively confirm the absence of any cases. However, information from Google Patents indicates that the patent family has litigation and that a PTAB case IPR2026-00138 was filed and is pending.

US Patent 9609544 is involved in the following known litigation:

Patent Trial and Appeal Board (PTAB) Cases:

• Case Number: IPR2023-01360

  • Status: Settlement
  • Petitioner: Not specified in the provided information.
  • Owner: Not specified in the provided information.
  • Filing Date: Not specified in the provided information.
  • Institution Date: Not specified in the provided information.
  • Termination Date: Not specified in the provided information.
  • Note: The Google Patents entry for US9609544 indicates "PTAB case IPR2023-01360 filed (Settlement)".

• Case Number: IPR2026-00138

  • Status: Pending
  • Petitioner: Not specified in the provided information.
  • Owner: Not specified in the provided information.
  • Filing Date: Not specified in the provided information.
  • Institution Date: Not specified in the provided information.
  • Termination Date: Not specified in the provided information.
  • Note: The Google Patents entry for US9609544 indicates "PTAB case IPR2026-00138 filed (Pending)".

District Court Cases:

• Jurisdiction: Texas Eastern District Court

  • Case Number: 2:25-cv-00904
  • Status: Not specified in the provided information.
  • Plaintiff(s): Not specified in the provided information.
  • Defendant(s): Not specified in the provided information.
  • Filing Date: Not specified in the provided information.
  • Outcome/Current Status: No outcome provided. Google Patents indicates "US case filed in Texas Eastern District Court".

• Jurisdiction: Texas Eastern District Court

  • Case Number: 2:22-cv-00467
  • Status: Not specified in the provided information.
  • Plaintiff(s): Not specified in the provided information.
  • Defendant(s): Not specified in the provided information.
  • Filing Date: Not specified in the provided information.
  • Outcome/Current Status: No outcome provided. Google Patents indicates "US case filed in Texas Eastern District Court".

• Jurisdiction: Texas Eastern District Court

  • Case Number: 2:25-cv-00905
  • Status: Not specified in the provided information.
  • Plaintiff(s): Not specified in the provided information.
  • Defendant(s): Not specified in the provided information.
  • Filing Date: Not specified in the provided information.
  • Outcome/Current Status: No outcome provided. Google Patents indicates "US case filed in Texas Eastern District Court".

• Jurisdiction: Texas Eastern District Court

  • Case Number: 2:25-cv-00909
  • Status: Not specified in the provided information.
  • Plaintiff(s): Not specified in the provided information.
  • Defendant(s): Not specified in the provided information.
  • Filing Date: Not specified in the provided information.
  • Outcome/Current Status: No outcome provided. Google Patents indicates "US case filed in Texas Eastern District Court".

• Jurisdiction: Texas Western District Court

  • Case Number: 7:25-cv-00518
  • Status: Not specified in the provided information.
  • Plaintiff(s): Not specified in the provided information.
  • Defendant(s): Not specified in the provided information.
  • Filing Date: Not specified in the provided information.
  • Outcome/Current Status: No outcome provided. Google Patents indicates "US case filed in Texas Western District Court".

Proceedings overview

There is currently one AIA trial proceeding on file for US patent 9609544. This proceeding, IPR2026-00138, is in a "Pending" status, meaning the PTAB has not yet issued a decision on institution. This indicates that the patent has not yet been substantively challenged through a final PTAB decision.

IPR2026-00138 — Google LLC et al. v. Headwater Research LLC

• Type: Inter Partes Review
• Filed: 2026-01-15
• Status: Pending. The petition has been filed, and the PTAB is reviewing it to decide whether to institute a trial.
• Judge panel: Not yet publicly available, as the institution decision is pending.
• Petition grounds: Details regarding the specific claims challenged, prior art cited, and statutory bases (§ 102 / § 103) are typically found in the public petition document. As the status is pending, these specifics would be in the filed petition, which is not immediately available in this summary but could be obtained from the USPTO PTAB E2E system.
• Institution decision: Not yet issued. The PTAB has a statutory deadline to decide whether to institute a trial, typically within six months of the preliminary response filing, or nine months from petition filing.
• Final Written Decision: Not issued, as the proceeding is still in the institution phase.
• Settlement / termination: No settlement or termination has been publicly indicated as the proceeding is pending.
• Appeal: Not applicable, as no Final Written Decision has been issued.
• Defensive value: This proceeding represents an active challenge to the patent. For a defendant, it indicates that Google LLC, a significant market player, is actively seeking to invalidate claims of US9609544. If the IPR is instituted and claims are subsequently canceled, it could significantly weaken the patent owner's assertion position. Conversely, if institution is denied or claims are upheld, it would strengthen the patent.

Strategic summary

Currently, the claims of US9609544 are largely UNTESTED through a final PTAB decision. While IPR2026-00138 has been filed by Google LLC, it is still in the preliminary "Pending" phase, awaiting an institution decision. This means no claims have been definitively canceled or sustained by the PTAB for this specific proceeding.

Regarding the estoppel landscape, since no trial has been instituted or concluded, there is no estoppel under 35 U.S.C. § 315(e)(2) for this proceeding. Should the IPR be instituted and proceed to a final written decision, Google LLC (and its privies) would be estopped from raising grounds they raised or reasonably could have raised in a subsequent civil action or ITC proceeding. However, for other potential defendants, prior art grounds remain generally available unless a specific IPR results in an institution denial or claims being upheld, and they are in privy with the petitioner.

A pattern signal is the petitioner, Google LLC. This suggests a potentially significant interest in challenging the patent, possibly due to an ongoing or anticipated assertion. The Google Patents page also indicates other litigation involving this patent family, including prior IPRs (e.g., IPR2023-01360, which settled) and district court cases in the Eastern and Western Districts of Texas. The filing of IPR2026-00138 by Google LLC as "Petitioner" (as noted on Google Patents) suggests a continued or renewed effort to challenge the patent's validity.

Recommended next steps

For a defendant facing assertion of US9609544:

• Monitor IPR2026-00138 closely: Since this proceeding is pending, the institution decision is a critical upcoming milestone. A decision to institute would confirm the PTAB's belief that there's a reasonable likelihood that at least one claim is unpatentable, providing a strong defensive argument. Conversely, a denial of institution would strengthen the patent owner's position. Track the USPTO PTAB E2E portal for updates on this IPR (IPR2026-00138).
• Review the Petition for IPR2026-00138: If accessible, carefully analyze the specific claims challenged, the prior art cited, and the unpatentability arguments presented by Google LLC. This provides insight into potential vulnerabilities of the patent and may inform your own defensive strategy, particularly regarding available prior-art grounds.
• Consider parallel litigation: The Google Patents page indicates ongoing district court litigation in Texas. Understanding the status and arguments in those cases may provide additional context and strategic insights.
• Evaluate potential estoppel: While not immediately applicable for IPR2026-00138, be mindful of the estoppel implications if you are in privy with Google LLC or if future IPRs are initiated and reach final decisions.

The status of IPR2026-00138 is "Pending" with the last modification on 2026-05-07. The PTAB typically issues an institution decision within 6 months of the filing of the patent owner's preliminary response.## Proceedings overview

There is currently one AIA trial proceeding on file for US patent 9609544. This proceeding, IPR2026-00138, is in a "Pending" status, meaning the PTAB has not yet issued a decision on institution. This indicates that the patent has not yet been substantively challenged through a final PTAB decision, leaving its claims largely untested by this mechanism.

IPR2026-00138 — Google LLC et al. v. Headwater Research LLC

• Type: Inter Partes Review
• Filed: 2026-01-15
• Status: Pending. The petition has been filed, and the PTAB is reviewing it to decide whether to institute a trial.
• Judge panel: Not publicly available yet, as the institution decision is pending. The panel will be assigned upon institution.
• Petition grounds: Specific details regarding the claims challenged, prior art cited, and statutory bases (§ 102 / § 103) are contained within the petition document, which is not immediately available in public search results. Access to the official filing in the USPTO's P-TACTS system (which replaced PTAB E2E) would be required to ascertain these specifics.
• Institution decision: Not yet issued. The PTAB typically issues a decision on institution within six months of the patent owner's preliminary response or nine months from the petition's filing date. Given the filing date of 2026-01-15, an institution decision is anticipated around October 15, 2026.
• Final Written Decision: Not issued, as the proceeding is still in the institution phase.
• Settlement / termination: No settlement or termination has been publicly indicated as the proceeding is pending.
• Appeal: Not applicable, as no Final Written Decision has been issued.
• Defensive value: This proceeding represents an active validity challenge initiated by Google LLC. Should the PTAB institute the IPR, it suggests that Google has presented a compelling argument of unpatentability for at least some claims. If claims are subsequently canceled in a Final Written Decision, it would significantly undermine the patent owner's ability to assert those claims. Conversely, if institution is denied or the claims are affirmed, it would strengthen the patent's presumption of validity against these specific challenges.

Strategic summary

The claims of US9609544 are currently UNTESTED by a final PTAB decision through IPR2026-00138, as this proceeding is still in the pre-institution phase. Therefore, no claims have been definitively canceled or sustained by the PTAB in this specific IPR.

Regarding estoppel, since no trial has been instituted or concluded, there is no estoppel under 35 U.S.C. § 315(e)(2) for this IPR. For a defendant not in privy with Google LLC, all prior-art grounds remain available for potential future challenges. If the IPR were to be instituted and proceed to a Final Written Decision, Google LLC (and its privies) would face estoppel on any grounds raised or that reasonably could have been raised in the IPR.

The filing by Google LLC signals a noteworthy challenge to the patent's validity. Recent policy shifts at the USPTO, particularly Director John Squires' memoranda from March 2025 and March 2026, have introduced new discretionary factors for institution, including a "domestic manufacturing gatekeeper." These changes emphasize factors like whether accused products are made in the US, whether the patent owner's competing products are made in the US, and whether the petitioner is a small business. These policies have led to a downward trend in IPR institution rates, falling from 66-68% in fiscal years 2022-2024 to 37% year-to-date in fiscal year 2026 through February 2026. This evolving landscape adds an additional layer of consideration for the institution decision of IPR2026-00138.

Recommended next steps

For a defendant facing assertion of US9609544:

• Monitor IPR2026-00138 for Institution Decision: The most critical immediate milestone is the PTAB's decision on whether to institute IPR2026-00138. This decision is expected around October 15, 2026. An institution would indicate a reasonable likelihood of unpatentability for at least some challenged claims, providing significant leverage. The USPTO's P-TACTS system is the authoritative source for monitoring the case.
• Obtain and Review the Petition: Gaining access to the full petition filed by Google LLC for IPR2026-00138 is crucial. This document will detail the specific claims challenged, the prior art asserted, and the unpatentability arguments, which can inform any independent validity analysis or defense strategy.
• Assess Impact of PTAB Policy Changes: Consider how the recent discretionary institution policies, particularly the "domestic industry" factor, might influence the institution decision for IPR2026-00138. This is an increasingly relevant consideration for IPRs filed in 2026.
• Consider Broader Litigation Context: The Google Patents listing indicates a history of litigation, including a settled IPR (IPR2023-01360) and several active district court cases. Understanding the full litigation landscape can provide strategic insights into the patent owner's enforcement strategy and the patent's perceived value.

Inventors

• Gregory G. Raleigh: Headwater Research LLC (assumed, based on being a principal inventor and director at Headwater Research LLC, leading its invention team, and the subsequent assignment of inventor interests to Headwater Partners I LLC, which then merged into Headwater Research LLC).
• Alireza Raissinia: Headwater Research LLC (assumed).
• James Lavine: Headwater Research LLC (assumed).

Original Assignee

The original assignee named on the issued patent is Headwater Research LLC. Headwater Research LLC's primary line of business is inventing and developing technological breakthroughs, particularly in mobile device operating systems and cloud technology, and subsequently licensing these technologies to partners and enabling spin-out companies. They describe their work as enabling products rather than shipping end-user products themselves. Headwater Research LLC is a privately held company and is currently operating and actively engaged in patent licensing and assertion.

Assignment timeline

• 2013-11-20 (executed) / recorded 2013-11-25 — Reel 032127/0638

  • Conveyance: ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS).
  • Assignor: LAVINE, JAMES, RAISSINIA, ALIREZA, RALEIGH, GREGORY G.
  • Assignee: HEADWATER PARTNERS I LLC
  • Correspondent: TROY J. DOZIER, CARR & FERRELL LLP, 120 CONSTITUTION DRIVE, MENLO PARK, CA 94025. This correspondent also appears in a subsequent recording in this chain.
  • Context: Transfer from inventors to a related holding entity.

• 2017-01-05 (executed) / recorded 2017-01-05 — Reel 038670/0411

  • Conveyance: MERGER AND CHANGE OF NAME
  • Assignor: HEADWATER MANAGEMENT LLC AND HEADWATER PARTNERS I LLC
  • Assignee: HEADWATER RESEARCH LLC
  • Correspondent: TROY J. DOZIER, CARR & FERRELL LLP, 120 CONSTITUTION DRIVE, MENLO PARK, CA 94025. This correspondent also appeared in an earlier recording in this chain.
  • Context: Internal reorganization/merger of holding entities into the ultimate asserting entity.

Timeline diagram

timeline
    title Ownership of US 9609544
    2013 : Inventors assigned to Headwater Partners I LLC
    2017 : Headwater Partners I LLC merged into Headwater Research LLC
    2017 : Patent issued to Headwater Research LLC
    2022 : First infringement suit filed (e.g. Samsung)
    2025 : Multiple infringement suits filed (e.g. Google, Verizon)
    2026 : PTAB case IPR2026-00138 filed

NPE / troll-pattern signals

1. Shell-entity transfer — present. The patent was initially assigned from the inventors to "HEADWATER PARTNERS I LLC" (Reel 032127/0638), a name suggesting a holding entity. Subsequently, Headwater Partners I LLC merged into Headwater Research LLC (Reel 038670/0411). Headwater Research LLC's business model is described as focusing on invention, development, and licensing, often enabling spin-outs, rather than direct manufacturing and sales of end-user products. Multiple legal news sources also explicitly identify Headwater Research LLC as an NPE.
2. Known asserter in the chain — present. Headwater Research LLC is a known patent asserter. Public records and news articles indicate that Headwater Research LLC has filed numerous patent infringement lawsuits against major technology companies such as Samsung, Google, Verizon, Apple, T-Mobile, and AT&T.
3. Repeat correspondent across the chain — present. TROY J. DOZIER of CARR & FERRELL LLP is listed as the correspondent for both recorded assignments (Reel 032127/0638 and Reel 038670/0411).
4. Cascading transfers — not present. The recorded assignments involve an initial transfer from inventors to Headwater Partners I LLC in 2013, followed by a merger/change of name into Headwater Research LLC in 2017. The time gap between these events is greater than 24 months, and they represent a corporate restructuring within a related group of entities rather than rapid transfers between distinct, unrelated shell LLCs.
5. Pre-litigation transfer — not present. The last assignment to Headwater Research LLC was recorded on 2017-01-05 (Reel 038670/0411), and the patent was issued on 2017-03-28. The earliest identified litigation related to Headwater Research LLC (e.g., against Samsung) appears to be from 2022. This gap is significantly longer than six months.
6. Bankruptcy fire-sale — not present. There is no evidence suggesting Headwater Research LLC or its predecessor entities underwent bankruptcy proceedings. PitchBook indicates Headwater Research is a privately held company that has raised funding.
7. Privateering — unclear. While Headwater Research LLC engages in licensing activities, there is no explicit information provided that indicates this specific patent was transferred from an operating company to Headwater Research LLC to assert on the operating company's behalf against competitors. Headwater Research LLC appears to originate its own patent portfolios through invention.
8. Defensive aggregator (anti-NPE) — not present. The current owner, Headwater Research LLC, is a patent asserter and not a defensive aggregator.

Verdict

NPE — high confidence
This verdict is supported by multiple strong signals: Headwater Research LLC is widely reported as a non-practicing entity (NPE) in legal news, actively engaged in asserting its patents against large technology companies. Its business model focuses on invention and licensing rather than producing end-user products, and the assignment chain includes transfers to entities with names (e.g., "Partners I LLC") that suggest holding or licensing purposes (Reel 032127/0638). Furthermore, the consistent use of the same correspondent, TROY J. DOZIER of CARR & FERRELL LLP, across the assignments (Reel 032127/0638, Reel 038670/0411) is a common pattern observed with NPEs who use a dedicated legal firm for managing their patent portfolio transfers.

USPTO Assignment Center search for US9609544: https://assignmentcenter.uspto.gov/

To identify the most relevant prior art for US patent 9609544, I need to access the "Cited By" section of the patent within the USPTO database. Since I cannot directly perform a live search of the USPTO database with real-time results and extract specific "Cited By" information as a human would, I will explain the general process for how this would be done and what information would be sought.

Process for Identifying Prior Art:

1. Access USPTO Patent Public Search: I would use the USPTO Patent Public Search tool (or similar databases like Google Patents) and specifically search for "US96095944".
2. Locate "Cited By" References: Once the patent record for US9609544 is found, I would navigate to the section that lists "Cited By" patents and other references. These are the documents that the patent examiner and/or the applicant identified as relevant prior art during the prosecution of the patent application.
3. Extract Information for Each Reference: For each listed prior art reference, I would extract the following:
   • Full citation (e.g., patent number, publication number, or other identifier, along with inventor/assignee and title if available).
   • Publication/Filing Date.
   • A brief description of the invention/disclosure in the prior art.
   • An analysis of which claims (from US9609544) are potentially anticipated under 35 U.S.C. § 102 by the prior art. This would involve comparing the elements of US9609544's claims against the disclosures of each prior art document.

Explanation of Anticipation under 35 U.S.C. § 102:

Under 35 U.S.C. § 102, a claim is anticipated if every element of the claim is found, either explicitly or inherently, in a single prior art reference. The prior art must disclose the claimed invention such that a person of ordinary skill in the art could have made the invention from that single reference.

Since I cannot execute the live USPTO database search, I cannot provide the specific list of prior art citations and their detailed analysis. The Google Patents link provided in the prompt's authoritative patent text does show a "Prior art date" of 2009-01-28 and lists "Prior art keywords" such as "network", "service", "qos", "service usage", and "policy". This indicates the general technical area in which prior art would be found, but it does not provide the specific citations.

To fulfill the request, a human analyst would perform the steps outlined above using the USPTO's Patent Public Search tool.

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.