Prior art — US Patent 8667571

Analysis of Prior Art for U.S. Patent No. 8,667,571

To: File
From: Senior Patent Analyst
Date: May 12, 2026
Subject: Analysis of Prior Art Cited in U.S. Patent No. 8,667,571

This memorandum provides an analysis of the most relevant prior art cited on the face of U.S. Patent No. 8,667,571, titled "Automated device provisioning and activation." The analysis focuses on the potential for these references to anticipate one or more of the independent claims of the '571 patent under 35 U.S.C. § 102.

The core invention of the '571 patent, as understood from its independent claims, relates to a system and method for managing a wireless device's access to network services. This is achieved through a "service processor" on the device that enforces policies defined in a "service profile" received from a network-based "service controller." This architecture allows for dynamic, verifiable, and granular control over service usage, activation, and billing directly on the end-user device.

The following references, cited by the patent examiner, are considered particularly relevant to the patent's core claims.

1. U.S. Patent No. 7,284,271 B2 ("Bamburac")

Full Citation: US 7,284,271 B2, Bamburac, D., "Method and system for policy based service provisioning and activation."
Dates: Filed Oct. 20, 2004; Published Oct. 16, 2007.
Brief Description: The Bamburac patent discloses a system for dynamically provisioning and managing services on a network element. It describes a "Policy Decision Point" (PDP), analogous to the '571 patent's service controller, which makes policy decisions. These decisions are enforced by a "Policy Enforcement Point" (PEP), which can be located in a network device or on a client terminal. The system allows for services to be activated, deactivated, or modified based on policies without requiring manual reconfiguration of the device.
Potential Anticipation of Claims:
- This reference appears to be highly relevant to the foundational concepts of the '571 patent. The PDP/PEP architecture mirrors the '571 patent's service controller/service processor relationship.
- Claim 26 and Claim 40 (Server-side Method/System): Bamburac's PDP (service controller) stores service policies and communicates them to a PEP (service processor) for enforcement. This directly maps to the '571 claims of a server providing a service profile to a device to control network service access.
- Claim 1 and Claim 72 (Device-side Method): Bamburac's disclosure of a PEP on a client terminal that receives and enforces policies strongly suggests the method of a device-based agent controlling access based on rules received from a network server. The process of "activating" a service by downloading a policy is central to Bamburac's teaching and aligns with the activation method in claim 72.
- Claim 14 and Claim 57 (Device and System): To the extent that Bamburac's "policy enforcement point" can be interpreted as a "service processor" on a "wireless device," this reference potentially discloses the core elements of these system claims. The distinction may lie in the specific implementation of the "secure" nature of the service processor, which is a key limitation in claim 14 of the '571 patent.

2. U.S. Patent No. 7,890,637 B2 ("Mclean et al.")

Full Citation: US 7,890,637 B2, Mclean et al., "Method and system for managing policies on a wireless device."
Dates: Filed Jan. 26, 2006; Published Feb. 15, 2011.
Brief Description: Mclean et al. describes a system for centrally managing policies on wireless devices. A policy management server sends policy information to a client application on the wireless device. This client application then enforces the policies, which can control various aspects of the device's functionality, including application usage and network access. The system is designed to allow administrators (e.g., enterprise IT) to control a fleet of devices remotely.
Potential Anticipation of Claims:
- This reference is also highly relevant, particularly with its explicit focus on a client-server architecture for managing policies on a wireless device.
- Claim 1 (Method on a device): Mclean describes a client agent (service processor) on the device that receives policies (service profile) from a server (service controller) and manages access to resources based on these policies. This covers the core steps of claim 1.
- Claim 14 (A wireless device): The device described in Mclean inherently contains the components to perform the described method, including a processor and memory to store and execute the policy client, which is analogous to the '571 patent's service processor.
- Claim 57 (System): The combination of the policy management server and the client-equipped wireless device in Mclean appears to teach the system of claim 57, which requires a service controller and a service processor on a wireless device communicating over a control plane.

3. U.S. Patent Application Publication No. 2008/0281907 A1 ("Mimar")

Full Citation: US 2008/0281907 A1, Mimar, "Device Assisted Services."
Dates: Filed May 11, 2007; Published Nov. 13, 2008.
Brief Description: Mimar discloses a "device-assisted services" architecture where an agent on a communication device collects data about the device and its usage. This data is sent to a network-based server, which analyzes it and sends back configuration data or commands to manage the device's services. This enables services like billing, Quality of Service (QoS) control, and content delivery to be managed with the assistance of the on-device agent.
Potential Anticipation of Claims:
- This publication is particularly relevant as it uses the same "device-assisted" terminology and describes a very similar architecture and purpose to the '571 patent.
- Claim 1 and Claim 14 (Device-side): The "agent" in Mimar is functionally equivalent to the "service processor" in the '571 patent. It resides on the device, receives configuration/policy information from a server, and manages services accordingly.
- Claim 26 and Claim 40 (Server-side): The network-based server in Mimar acts as a "service controller," receiving device data and sending down policies. The concept of using device-reported data to verify service usage, as described in claim 40, is also contemplated by Mimar's architecture, which uses collected data to make decisions.
- Claim 72 (Activation): The process of a device first connecting to the network, being identified, and then receiving its service configuration (provisioning) from the server is a core aspect of the system described by Mimar.

4. U.S. Patent Application Publication No. 2008/0207167 A1 ("Willars et al.")

Full Citation: US 2008/0207167 A1, Willars et al., "System and Method for Policy and Charging Control."
Dates: Filed Nov. 28, 2007; Published Aug. 28, 2008.
Brief Description: Willars et al. describes a system based on the 3rd Generation Partnership Project (3GPP) Policy and Charging Control (PCC) architecture. This architecture uses a Policy and Charging Rules Function (PCRF) to define rules for service data flows, and a Policy and Charging Enforcement Function (PCEF) to enforce these rules. The PCEF typically resides within the network (e.g., at a gateway) and inspects data packets to control service access and gather billing information based on policies from the PCRF.
Potential Anticipation of Claims:
- While the PCC architecture described by Willars et al. achieves similar goals (policy and charging control), the key distinction lies in the location of the enforcement function. In the standard PCC architecture, the PCEF is a network element, not an agent on the end-user device.
- However, the reference is still highly relevant as it discloses the concept of a centralized policy controller (PCRF) sending detailed service rules (policies) to a distributed enforcement point (PCEF) to manage network traffic and apply charging rules. It establishes the state of the art for network-side policy control, which the '571 patent moves to the device side. While it may not directly anticipate claims requiring the processor to be on the device, it describes a very similar logical framework for service management.

Conclusion

The prior art cited against US 8,667,571, particularly the Bamburac, Mclean, and Mimar references, discloses the core architectural concept of a client-server system for managing services on a remote device. These references describe an agent (or "policy enforcement point") on a device that receives policies from a central server (a "policy decision point" or "service controller") and enforces them to control access to network services.

The potential novelty and non-obviousness of the '571 patent's claims, when viewed in light of this prior art, would likely depend on specific implementation details. These could include the "secure" nature of the service processor as recited in claim 14, the specific mechanisms for "verifying" service usage as detailed in claim 40, or the unique combination of features within the service policy profile. However, the foundational idea of device-assisted service and policy control appears well-established in the prior art.