Common Open Policy Service

Description

The Common Open Policy Service (COPS) is a query-response protocol standardized by the IETF in RFC 2748 and RFC 3084, which 3GPP adopted as a key protocol for policy control interfaces. It operates on a client-server model where the Policy Enforcement Point (PEP) acts as the client, requesting policy decisions from the Policy Decision Point (PDP) server. The protocol uses TCP for reliable transport and supports both outsourcing and provisioning models. In the outsourcing model, the PEP delegates decision-making to the PDP for each event, while in the provisioning model, the PDP pushes policy rules to the PEP for local enforcement.

COPS architecture in 3GPP networks typically involves the Policy and Charging Rules Function (PCRF) as the PDP and various network elements like the P-GW, S-GW, or Application Function (AF) as PEPs. The protocol defines several message types: Request (REQ), Decision (DEC), Report State (RPT), and Delete Request State (DRQ). When a PEP encounters an event requiring policy decisions (like a new IP-CAN session establishment), it sends a REQ message containing context information. The PDP processes this request against policy rules and subscriber profiles, then returns a DEC message with instructions for the PEP to enforce.

Key components of COPS include the Client-Type identifier, which distinguishes different policy clients (like QoS policy versus access control), and the Context object, which specifies the type of request (e.g., configuration, admission control, resource allocation). The protocol maintains stateful connections between PEP and PDP, allowing the PDP to track the state of each PEP client and push policy updates when conditions change. This stateful nature enables efficient synchronization and reduces message overhead compared to stateless protocols.

In 3GPP implementations, COPS is primarily used for the Gq interface between the PCRF and the Application Function (AF) in IMS networks, and for the Gx interface between PCRF and PCEF in PCC architecture. The protocol supports extensibility through vendor-specific objects (VSOs), allowing operators to implement custom policy extensions. COPS also includes mechanisms for error handling, keep-alive messages (KA), and synchronization between PEP and PDP to ensure consistent policy enforcement even after connection failures.

The protocol's design emphasizes scalability and reliability through its connection-oriented approach and support for multiple policy domains. Each COPS connection can handle multiple policy contexts simultaneously, reducing the need for multiple TCP connections between the same PEP and PDP. The PDP can install, update, or remove policy decisions dynamically based on changing network conditions, subscriber status, or external triggers from applications, enabling real-time policy adaptation in mobile networks.

Purpose & Motivation

COPS was created to address the need for a standardized, interoperable protocol for policy control in IP networks, which became critical as 3GPP networks evolved toward all-IP architectures. Before COPS, policy control mechanisms were often proprietary or based on simple protocols like RADIUS that lacked the stateful, bidirectional communication required for dynamic policy management. The IETF developed COPS to provide a flexible framework where policy decisions could be centralized while enforcement remained distributed across network elements.

In 3GPP networks, COPS solved several key problems: it enabled consistent application of QoS policies across different network domains (access, core, IMS), provided a mechanism for real-time policy updates based on changing network conditions or subscriber actions, and created a clean separation between policy decision logic and enforcement mechanisms. This separation allowed operators to implement sophisticated policy rules in centralized servers while keeping enforcement efficient at the edge devices. The protocol's adoption in 3GPP R99 was motivated by the need for policy control in the newly introduced IP Multimedia Subsystem (IMS), where dynamic QoS and charging policies were essential for multimedia services.

The limitations of previous approaches that COPS addressed included the lack of stateful communication in protocols like RADIUS, which made real-time policy updates difficult; the proprietary nature of many policy control solutions, which hindered multi-vendor interoperability; and the inability to support both outsourcing and provisioning models in a single protocol. COPS provided a standardized solution that could scale to large networks while maintaining the flexibility needed for evolving service requirements. Its adoption by 3GPP ensured that policy control could be implemented consistently across different releases and network architectures.

Key Features

• Client-server architecture with PEP (client) and PDP (server) roles
• Stateful connection management enabling efficient policy synchronization
• Support for both outsourcing (event-based) and provisioning (rule-based) models
• Extensible through vendor-specific objects (VSOs) for custom implementations
• Reliable transport over TCP with built-in error handling and keep-alive mechanisms
• Multiple client-type support for different policy domains (QoS, access control, etc.)

Evolution Across Releases

Defining Specifications