Policy and Charging Rules Function

Description

The Policy and Charging Rules Function (PCRF) is a core network element within the 3GPP Policy and Charging Control (PCC) framework, introduced in EPS (Evolved Packet System) and continued in 5G System (5GS). It operates as the central policy decision point. The PCRF receives input from multiple sources: subscriber data from the Subscription Profile Repository (SPR) or Unified Data Repository (UDR), service information from the Application Function (AF) like the P-CSCF, and network status from the Traffic Detection Function (TDF) or its own monitoring. It combines this information with predefined operator policies to make real-time, binding decisions on how individual service data flows should be treated.

These decisions are encapsulated in PCC rules, which are sent to the Policy and Charging Enforcement Function (PCEF), typically co-located with the Packet Data Network Gateway (PGW) in 4G or the Session Management Function (SMF) in 5G. A PCC rule contains identifiers for the service data flow (e.g., IP 5-tuple), the required QoS parameters (QCI, ARP, bit rates), and charging instructions (online, offline, charging key). The PCEF then installs these rules, enforcing them by applying corresponding packet filters, QoS marking (DSCP), and metering traffic for charging. The PCRF can modify or remove rules dynamically during a session in response to events like a change in subscriber tier, network congestion, or the start/stop of a sponsored data service.

Architecturally, the PCRF interfaces with numerous network functions via standardized reference points. The Rx interface connects to the AF (for service-based policy), the Gx interface to the PCEF (for rule provisioning), the Sp interface to the SPR/UDR (for subscriber data), and the Sy interface to the Online Charging System (OCS). In 5G, the PCRF's role is largely subsumed by the Policy Control Function (PCF), which follows a similar service-based architecture but with enhanced capabilities for network slicing and edge computing. The PCRF/PCF is a critical enabler for advanced business models, allowing operators to move from flat-rate billing to granular, service-differentiated charging and quality assurance.

Purpose & Motivation

The PCRF was developed to solve the limitations of static, pre-configured policy control in earlier mobile data networks (GPRS, early 3G). In those networks, QoS and charging were largely determined by the subscriber's static APN (Access Point Name) configuration, offering little flexibility to adapt to specific applications or real-time network conditions. This 'one-size-fits-all' approach hindered the monetization of new services (like VoIP, video streaming) and efficient network resource utilization.

The driving motivation was to create a dynamic, application-aware policy framework. The PCRF enables operators to implement sophisticated service plans (e.g., zero-rating for social media, premium QoS for cloud gaming, bandwidth throttling after a data cap). It addresses the need for real-time interaction between the service layer (applications) and the transport layer (bearer network). By centralizing policy decisions, the PCRF provides a consistent control point, ensuring that policy is applied uniformly regardless of the user's access technology (3G, 4G, non-3GPP). Its creation was closely tied to the all-IP architecture of EPS, where the traditional circuit-switched domain for voice was replaced by packet-switched IMS (IP Multimedia Subsystem), requiring tight integration between service signaling and bearer management for quality assurance.

Key Features

• Centralized, real-time policy decision-making based on subscriber, service, and network data.
• Dynamic provisioning of PCC rules to enforcement points (PCEF) via the Gx interface.
• Support for service-aware QoS control, defining parameters like QCI, GBR, and MBR per data flow.
• Integration with charging systems, determining online and offline charging rules and triggers.
• Interaction with Application Functions (AF) via the Rx interface for service-based policy (e.g., IMS).
• Capability for event-triggered policy updates (e.g., on location change, time-of-day, or usage threshold).

Evolution Across Releases

Defining Specifications