Performance-oriented Congestion Control

Description

Performance-oriented Congestion Control (PCC) is a comprehensive framework within 3GPP standards that provides dynamic policy control and charging functionality for IP-based services. It is a cornerstone of the Evolved Packet Core (EPC) in LTE and 5G systems, though its origins trace back to Release 7. The PCC architecture centralizes decision-making for QoS and charging, allowing network operators to apply precise controls per user and per service flow. At its heart, PCC involves key functional entities: the Policy and Charging Rules Function (PCRF), the Policy and Charging Enforcement Function (PCEF), the Application Function (AF), and the Subscription Profile Repository (SPR) or Unified Data Repository (UDR). These elements work in concert to authorize resources, enforce policies, and ensure appropriate charging based on real-time inputs.

The PCC framework operates through a series of standardized interfaces, primarily the Gx interface between PCRF and PCEF, the Rx interface between PCRF and AF, and the Sy interface between PCRF and OCS (Online Charging System). How it works begins with the establishment of an IP-CAN (IP Connectivity Access Network) session by the User Equipment (UE). The PCEF, typically residing in the Packet Data Network Gateway (PGW) in LTE or the SMF/UPF in 5G, detects the session and requests policy rules from the PCRF via Gx. The PCRF then makes decisions by consolidating information from multiple sources: subscriber data from SPR/UDR (e.g., allowed services, QoS profiles), service information from AF (e.g., required bandwidth for a video stream), and network status from internal policies or the Traffic Detection Function (TDF). It then provisions these decisions as PCC rules to the PCEF for enforcement.

Key components of PCC include PCC rules, which are sets of information enabling the detection of a service data flow and defining parameters for its treatment. Each PCC rule contains a rule identifier, service data flow filters (e.g., 5-tuple IP filters), precedence, QoS parameters (QCI, ARP, bitrates), charging information (metering method, charging key), and enforcement actions. The PCEF uses these rules to perform deep packet inspection (DPI) to identify flows, apply QoS marking (setting DSCP or allocating bearer resources), rate limit, and generate charging data records (CDRs) or interact with online charging systems. This allows for granular control, such as prioritizing VoIP traffic over best-effort web browsing or applying zero-rating for specific applications.

PCC's role extends beyond basic QoS; it is integral to network slicing, edge computing, and network automation in 5G. In 5G Core, the Policy Control Function (PCF) assumes the PCRF role, interacting with the Session Management Function (SMF) via the N7 interface. PCC principles enable dynamic policy adjustments based on network slicing SLAs, location changes, or congestion events. For instance, during network congestion, PCC can throttle non-essential traffic or offer sponsored data services. The framework supports both static policies (pre-configured) and dynamic policies (session-specific), providing flexibility for operators to innovate with service offerings while maintaining network performance and monetization.

Purpose & Motivation

PCC was created to address the limitations of static, pre-configured policy and charging mechanisms in earlier mobile data networks (e.g., GPRS). Before PCC, QoS and charging were often based on simple APN (Access Point Name) settings or subscriber profiles without real-time adaptability. This rigidity made it difficult for operators to offer differentiated services, manage network congestion dynamically, or implement sophisticated charging models like tiered data plans, zero-rating, or sponsored data. The explosion of IP-based services (video streaming, VoIP, IoT) in the mid-2000s demanded a more agile system that could respond to application needs and network conditions in real time.

The primary problem PCC solves is the efficient and monetizable management of scarce network resources amidst diverse traffic types. It enables operators to enforce policies that align with business objectives—for example, ensuring premium subscribers experience high-quality video while limiting heavy users during congestion. PCC also facilitates service innovation by allowing third-party application providers to interact with the network via the AF (e.g., through the Rx interface) to request specific QoS for their services, enabling partnerships and new revenue streams. This was a paradigm shift from network-as-a-pipe to network-as-a-service.

Historically, PCC's development in Release 7 was motivated by the convergence of IMS (IP Multimedia Subsystem) and non-IMS services over packet-switched domains. It provided a unified policy control framework for both, replacing earlier disjointed mechanisms like the Go interface for IMS. As networks evolved to LTE and 5G, PCC became even more critical due to increased data volumes, low-latency requirements, and network slicing. It addressed the need for automation in policy decision-making, reducing operational overhead and enabling real-time charging for on-demand services. PCC thus underpins modern mobile broadband economics, allowing operators to balance performance, fairness, and profitability in a competitive landscape.

Key Features

• Dynamic policy decision and enforcement per service data flow
• Integration with subscriber data, application requests, and network status
• Support for both online and offline charging integration
• Granular QoS control including QCI, ARP, and bandwidth parameters
• Deep packet inspection capabilities for service flow detection
• Standardized interfaces (Gx, Rx, Sy) for multi-vendor interoperability

Evolution Across Releases

Defining Specifications