Patent 8667571
Obviousness
Combinations of prior art that suggest the claimed invention would have been obvious under 35 U.S.C. § 103.
Active provider: Google · gemini-2.5-pro
Obviousness
Combinations of prior art that suggest the claimed invention would have been obvious under 35 U.S.C. § 103.
Technical Analysis of US Patent 8,667,571: Obviousness
To: File
From: Senior Patent Analyst
Date: 2026-05-12
Subject: Obviousness Analysis of U.S. Patent No. 8,667,571
1. Introduction
This report provides an analysis of the potential obviousness of key claims of U.S. Patent No. 8,667,571 ("the '571 patent") under 35 U.S.C. § 103. The analysis is based on the state of the art at the time of the invention, as suggested by the patent's own classification codes and a general understanding of the technology landscape preceding its priority date of January 28, 2009.
A person of ordinary skill in the art (POSITA) at the time of the invention would be a software or network engineer with several years of experience in mobile telecommunications, including familiarity with cellular network architectures (e.g., 3GPP standards), device-side application development, and network management and billing systems.
The core concept of the '571 patent appears to be a system and method for managing a wireless device's access to network services through a combination of a device-side component (a "service processor") and a network-side component (a "service controller"). The service controller provides a "service profile" containing policy rules, and the service processor enforces these rules directly on the device. This architecture enables automated provisioning, granular service control, and verifiable usage reporting.
2. Analysis of Obviousness
The claims of the '571 patent, particularly the independent claims, appear to be a combination of several well-known elements in the fields of telecommunications, network management, and software architecture. An argument for obviousness can be constructed by combining prior art teachings that address separate components of the claimed invention.
Obviousness Combination 1: Combining Network Policy Control with a Device-Side Agent
A primary inventive concept of the '571 patent is the offloading of policy enforcement from the core network to the end-user device. This would have been an obvious development to a POSITA seeking to improve the scalability and granularity of service management.
Prior Art Element A: Network-Based Policy and Charging Control (PCC).
The telecommunications industry, particularly under 3GPP standards, had already established sophisticated network-based systems for policy and charging control. Systems like the Policy and Charging Rules Function (PCRF) were known. These systems allowed network operators to define rules for quality of service (QoS), data caps, and service access based on a subscriber's profile. This is evidenced by classifications such as H04L41/5003 (Managing SLA; Interaction between SLA and QoS) and H04W4/24 (Accounting or billing). However, these systems were located deep within the carrier's core network and often relied on Deep Packet Inspection (DPI) to identify traffic, which was becoming increasingly difficult with the rise of encrypted protocols (e.g., HTTPS).Prior Art Element B: Device Management and Configuration.
The concept of a software agent residing on a device to manage its configuration and enforce policies was also well-established. Mobile Device Management (MDM) solutions were used in enterprise settings to enforce security policies, configure settings (like email and Wi-Fi), and manage applications. Furthermore, Over-The-Air (OTA) provisioning was standard practice for carriers to send basic network settings (like APNs) to new devices. This prior art is reflected in classifications like G06F15/177 (Initialisation or configuration control) and H04L41/0806 (Configuration setting for initial configuration or provisioning, e.g. plug-and-play).Motivation to Combine:
A POSITA would have been motivated to combine the network-based policy control of Element A with the on-device agent concept of Element B for several compelling reasons:- Scalability and Performance: As mobile data traffic grew exponentially, performing DPI and policy enforcement for every data packet in the core network created significant performance bottlenecks and required massive, expensive hardware. Moving this function to the device itself would distribute the processing load, reducing the burden on the core network. This is a classic client-server optimization strategy.
- Granularity and Context-Awareness: A network-based system has limited visibility into the device's state (e.g., which application is generating the traffic, whether the screen is on, what Wi-Fi networks are available). An on-device agent (the "service processor") has access to this rich contextual information, allowing for much more intelligent and fine-grained policy enforcement (e.g., "allow video streaming only over Wi-Fi" or "throttle background data for app X"). This directly addresses the need for more sophisticated service plans as described in G06Q10/06315 (Needs-based resource requirements planning).
- Encryption: With the increasing use of encrypted protocols like HTTPS, the effectiveness of network-based DPI was declining. A POSITA would recognize that an agent on the device could identify traffic at the application layer before it gets encrypted, solving the visibility problem.
Combining a central policy server (the "service controller" from A) with a local enforcement agent (the "service processor" from B) would have been an obvious design choice to address these known industry challenges.
Obviousness Combination 2: Automating Service Activation and Profile Management
Another key aspect of the patent is the automated activation process, where the device contacts a server, provides an identifier, and receives a service profile.
Prior Art Element C: Secure Elements and Device Identity.
The use of a Subscriber Identity Module (SIM) or a Universal Integrated Circuit Card (UICC) as a secure identifier for a device on a mobile network was fundamental to GSM and UMTS technology. These secure elements were used for authentication with the network's Home Location Register (HLR). This is reflected in classifications such as H04W12/06 (Authentication) and H04L63/0853 (authentication using an additional device, e.g. smartcard, SIM).Prior Art Element D: Web Service Provisioning.
The paradigm of a client application connecting to a remote server, authenticating, and downloading a configuration profile or data was ubiquitous. Users were accustomed to logging into applications or websites to activate services or customize their profiles. This is broadly covered by classifications like G06Q30/06 (Buying, selling or leasing transactions) and H04L67/51 (Discovery or management of network services).Motivation to Combine:
A POSITA tasked with improving the "out-of-box experience" for new mobile devices would find it obvious to combine these elements. The goal of automating device setup to reduce customer support calls and streamline activation was a well-known business objective.The combination would work as follows: A new device, upon first connection, uses its secure identifier (Element C) to authenticate with a provisioning server (the "service controller" from Element D). This server, having access to the user's account and service plan, then delivers a complete service profile to the device, automating the setup process described in the claims. This is a straightforward application of web-service principles to the mobile provisioning problem, representing a predictable evolution of existing OTA provisioning systems.
3. Conclusion
While the '571 patent describes a comprehensive and well-architected system, its core concepts appear to be an obvious combination of pre-existing technologies and practices. A person of ordinary skill in the art, faced with the problems of network congestion, the need for more flexible service plans, and the desire for a seamless user activation experience, would have been motivated to:
- Combine network-based policy management with a device-side enforcement agent to gain a more scalable and granular control over service usage.
- Leverage existing secure device identifiers and web service paradigms to create an automated provisioning and activation system.
The combination of these known elements to achieve the claimed system would have been a predictable step forward in the field of mobile network and service management. The extensive litigation history, while indicating the patent's commercial value, does not preclude a finding of obviousness based on the technical merits of the prior art.
Generated 5/12/2026, 11:44:07 PM