Menu
Latest
12 meetings · Prague, Jeju · 12–16 Oct
Reports
RAN1#126-bis · SA2#177

Glossary term · Core Network

PCRF

Policy and Charging Rules Function

Core Network →

PCRF is the network function that makes real-time policy and charging decisions based on subscriber data and provisions those rules to enforcement points for dynamic service control.

Introduced
Rel-7
Where
Core Network › Evolved Packet Core
Specifications
58 specs
Also in
Services, Management
PCRF Description Purpose What changed Family Neighbours Detected Changes Specifications

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.

What changed in its specifications

The latest release-to-release comparison of specifications that define PCRF. Each summary describes the whole specification, not only this term.

TS 23.060Rel-18 → Rel-19

Rel-19 brings only minor changes to TS 23.060: 0 clauses changed, with no change attributed to a release feature.

Full comparison in TS 23.060 →
TS 23.203Rel-16 → Rel-17

NB-IoT/eMTC support for Non-Terrestrial Networks: adds QCI characteristic for satellite access, note on GEO/LEO delays, and PCRF policy control for satellite PDN connections.

Full comparison in TS 23.203 →

Architecture

Where it sits in the network

Evolution Lineage

Technology family

Core network elements and functions · Core Network

  1. Phase 1 AuC, EIR, GMSC, HLR, IWF, MSC, VLR
  2. Phase 2 SMS-GMSC, SMS-IWMSC
  3. R96 GGSN, SGSN
  4. R99 3G-SGSN, GLR, IM-GSN, IM-MSC
  5. Rel-4 CS-MGW, GMSC Server, MSC Server
  6. Rel-5 HSS, SLF
  7. Rel-6 3GPP AAA Server
  8. Rel-7 PCEF, PCRF
  9. Rel-8 ANDSF, BBERF, ePDG, MME, PGW, SGW
  10. Rel-9 HLR-FE, HSS-FE, UDR
  11. Rel-10 L-GW
  12. Rel-11 TDF
  13. Rel-14 PGW-C, PGW-U, SGW-C, SGW-U, TDF-C, TDF-U
  14. Rel-15 AMF, AUSF, PCF, SMF, SMF+PGW-C, UDM, UPF
  • PCRF counterpart in another generation: PCF
    “policy interactions between PDN GW and PCRF specified in TS 23.402 [26] are replaced by equivalent interactions between SMF+PGW-C and PCF” TS 23.502
  • PCRF used together with PCEF
    “The PCC functionality is comprised by the functions of the Policy and Charging Enforcement Function (PCEF), the Bearer Binding and Event Reporting Function (BBERF), the Policy and Charging Rules Function (PCRF)” TS 23.203

Members and relations were proposed independently by several models and kept only where at least two agree; quotes are verified verbatim against the specifications. Release = first approved version of the defining specification.

Release Timeline

Detected Changes Across Releases

verified against 3GPP sources

Documented changes in 14 releases, each verified against the text of 3GPP specifications or approved change requests and shown with the exact wording. The release timeline above shows the same releases. A release without an entry has no documented change for this term.

Rel-7 introduced

The PCRF is specified for the first time in Rel-7, combining the Rel-6 PDF and CRF roles, with Gx provisioning of PCC rules to the PCEF and Rx interaction with the AF.

  • “The PCRF (Policy Control and Charging Rules Function) is a functional element that encompasses policy control decision and flow based charging control functionalities.” TS 29.212 v7.16.0
  • “The PCRF shall provision PCC Rules to the PCEF via the Gx reference point.” TS 29.212 v7.16.0
  • “policy control: The process whereby the PCRF indicates to the PCEF how to control the IP-CAN bearer.” TS 23.203 v7.14.1
Rel-8 specification text

PCRF behaviour was extended in Rel-8: it provisions PCC/QoS rules over Gx and Gxx, authorizes UE-requested QoS and traffic mapping filters, and can reject conflicting requests with new Gx result codes.

  • “the PCRF may reject the request using a CC-Answer with the Gx experimental result code DIAMETER_ERROR_CONFLICTING_REQUEST (5147)” TS 29.212 v8.24.0
  • “When both a Gx and a Gxx interface exist for an IP‑CAN session, the PCRF shall generate QoS rules for all the authorized PCC rules” TS 23.203 v8.15.0
  • “The PCRF shall provision PCC/QoS Rules to the PCEF/BBERF via the Gx/Gxx reference point.” TS 29.214 v8.19.0
Rel-9 specification text

PCRF gained new behaviour in Rel-9: emergency APN detection and handling without subscription data, usage monitoring control with thresholds and monitoring keys, and revised session linking.

  • “The PCRF shall detect that a Gx session is restricted to IMS Emergency services when a CCR command is received” TS 29.212 v9.19.0
  • “The PCRF shall not remove the “USAGE_REPORT” Event-Trigger AVP while usage monitoring is still active in the PCEF.” TS 29.212 v9.19.0
  • “At Indication of IP-CAN Session Establishment that includes a PDN-id that identifies an Emergency APN the PCRF ignores subscription information from the SPR.” TS 23.203 v9.14.0
Rel-10 specification text

PCRF gained new behaviour in Rel-10: selecting the bearer binding function from IP flow mobility routing rules, handling MPS priority EPS bearer service, and providing usage monitoring thresholds.

  • “The PCRF shall select either the PCEF or any applicable BBERF as the bearer binding function for each service data flow” TS 29.212 v10.17.0
  • “the PCRF shall make the corresponding policy decisions (i.e. ARP and/or QCI change) and, if applicable, shall initiate a RAR command” TS 29.212 v10.17.0
  • “the PCRF shall provision QoS rules only to the appropriate BBERF based on IP flow mobility routing rules received from the PCEF” TS 23.203 v10.10.0
Rel-11 specification text

PCRF gained new responsibilities in Rel-11: application detection and control via TDF/Sd and ADC rules, PCC rule provisioning to PCEF enhanced with ADC, and access network information reporting to the AF.

  • “PCRF may control redirection by provisioning and modifying dynamic ADC rules over the Sd interface for a TDF” TS 23.203 v11.15.0
  • “The PCRF shall decide whether application traffic detection is applicable, as per operator policies, based on user profile configuration” TS 23.203 v11.15.0
  • “The PCRF provisions the applicable ADC Rules for the corresponding TDF session by sending a Diameter TS-Request to the TDF” TS 29.213 v11.16.0
Rel-12 specification text

PCRF gained new behaviour in Rel-12: it can provide time-based usage monitoring thresholds and an inactivity detection time, and it handles P-CSCF restoration and presence reporting area subscription.

  • “Usage is defined as volume or time of user plane traffic. Monitoring for traffic volume and traffic time can be performed in parallel.” TS 29.212 v12.14.0
  • “the PCRF may optionally indicate to the PCEF, along with other usage monitoring information provided, the Inactivity Detection Time within the Quota-Consumption-Time AVP” TS 29.212 v12.14.0
  • “the PCRF may subscribe to Change of UE presence in Presence Reporting Area at any time during the life time of the IP-CAN session” TS 23.203 v12.11.0
Rel-13 1 CR

In Rel-13 the PCRF gained new behaviour: traffic steering policy selection and provisioning, resource-release reporting, transfer-policy-based decisions, resource sharing, conditional APN policy info, and RAN congestion information handling.

  • “The PCRF may instruct the PCEF to apply a traffic steering control which consists of applying a specific (S)Gi-LAN traffic steering policy” TS 29.212 v13.13.0
  • “the PCRF may request the PCEF to report the outcome of the release of resources related to a PCC rule” TS 29.212 v13.13.0
  • Correction on the PCRF procedures TS 29.212CR1439
Rel-14 1 CR

PCRF behaviour was extended in Rel-14: it can bind PCC rules to the default bearer, provide time-conditioned policy info sets, and apply PS Data Off and presence reporting area handling.

  • “The PCRF shall provide the Default-Bearer-Indication AVP within the Charging-Rule-Definition AVP set to BIND_TO_DEF_BEARER (0)” TS 29.212 v14.11.0
  • “To replace a set of time conditioned policy info(s), the PCRF shall include a complete set of Conditional-Policy-Information AVP(s)” TS 29.212 v14.11.0
  • Dynamic PCC rules controlled by PCRF to be bound to the default bearer TS 29.212CR1544
Rel-15 specification text

PCRF behaviour was extended in Rel-15: UE-Status-Change suspend/resume handling, PS Data Off with uplink blocking, Max packet loss rate provisioning for QCI 1, and extended bandwidth AVPs.

  • “During IP-CAN session establishment or modification procedure, the PCRF shall subscribe to the "UE_STATUS_RESUME" Event-Trigger if not subscribed yet” TS 29.212 v15.9.0
  • “the PCRF shall, for those flows associated with QCI of 1, send the downlink maximum packet loss rate” TS 29.212 v15.9.0
  • “the PCRF shall configure the PCEF to block any downlink and optionally uplink IP flows not relating to a service” TS 29.212 v15.9.0
Rel-16 specification text

In Rel-16 the PCRF's behaviour changed: it derives and provisions Max-PLR-DL/UL for QCI 1 rules from CHEM-proposed packet loss rates, and it supports RLOS policies and QoS hints over Rx.

  • “When the PCRF receives IMS service information over Rx interface with CHEM proposed packet loss rate, the PCRF sets the downlink and uplink maximum packet loss rates to the received values.” TS 29.212 v16.4.0
  • “the PCRF provides the PDN GW with the QoS parameters, based on operator policy, including an ARP value reserved for the Restricted Local Operator Services” TS 29.212 v16.4.0
  • “Upon receiving the information from the P-CSCF and if the QoSHint feature is supported, the PCRF shall derive the QoS information” TS 29.214 v16.8.0
Rel-17 1 CR

PCRF gained MPS for DTS handling: on AF invocation/revocation it makes ARP/QCI policy decisions, provisions them via RAR, and reports success or failure of the outcome back to the AF.

  • “the PCRF shall make the corresponding policy decisions (i.e. ARP and/or QCI change) and, if applicable, shall initiate a RAR command to provision the modified data.” TS 29.212 v17.3.0
  • “the PCRF shall request the PCEF using an RAR command to confirm that the resources associated to the MPS for DTS invocation/revocation are successfully allocated” TS 29.212 v17.3.0
  • PCRF control of MPS for DTS TS 29.213CR0743
Rel-18 specification text

In TS 29.214 Rel-18, the PCRF must check the UE's MPS subscription before enabling MPS for AF signalling, signalled via the MPS-Action AVP, and QoSHint handling now covers SIP responses as well as requests.

  • “The PCRF shall check the user's MPS subscription and enable MPS for AF signalling.” TS 29.214 v18.4.0
  • “support for use of the MPS-Action AVP to signal that the UE's MPS subscription shall be checked by the PCRF” TS 29.214 v18.4.0
Rel-19 specification text

PCRF gained new behaviour in Rel-19: EPC health monitoring and PCEF failure detection via Gx/Rx RAR, plus MPS for Messaging handling, with session recovery prioritization.

  • “if the PCRF decides to monitor PCEF failure based on operator configuration, the PCRF sends Gx-Re-Auth-Request to the PCEF.” TS 29.213 v19.3.0
  • “the PCRF shall provide the received information to the AF within the PC-Session-Recovery-Status AVP in a RAR command.” TS 29.214 v19.3.0
  • “the PCRF shall check if the AF Signalling IP flows are already prioritized.” TS 29.214 v19.3.0
Rel-20 specification text

PCRF gains new behaviour in Rel-20 to report and handle the UDP/IP Header Removal & Restoration (UHRR) capability of the IP-CAN, subscribing to an event trigger and passing the capability to the AF.

  • “If an AF requests the PCRF to report the UDP/IP Header Removal & Restoration capability of the IP-CAN session, then the PCRF shall provide” TS 23.203 v20.1.0
  • “the PCRF shall subscribe to the Event-Trigger AVP with the value UHRR_CAP_REPORT (58), if not subscribed yet.” TS 29.212 v20.0.0
  • “Upon receipt of the AA-Request, the PCRF shall include the UHRR-Capability AVP in the AA-Answer if the UHRR capability information is available” TS 29.214 v20.0.0

Defining Specifications

3GPP specifications that define or reference PCRF, with the latest known release. Sourced from the 3GPP document catalog — see methodology.

SpecificationTitleRelease
TS 23.060 vj00 GPRS Stage 2 Service Description Rel-19 read
TS 23.139 vj00 3GPP-Fixed Broadband Interworking Stage 2 Rel-19 read
TS 23.203 vk10 Policy and Charging Control Architecture Rel-20 read
TS 23.207 vj00 End-to-End QoS Framework for GPRS Rel-19 read
TS 23.228 vk10 IP Multimedia Core Network Subsystem Rel-20 read
TS 23.282 vk31 Mission Critical Data Architecture Rel-20 read
TS 23.379 vk40 Mission Critical Push-to-Talk Architecture Rel-20 read
TS 23.380 vk00 IMS Restoration Procedures Rel-20 read
TS 23.401 vk10 Evolved Packet System Architecture Rel-20 read
TS 23.682 vj30 Architecture for MTC and SCEF Enhancements Rel-19 read
TS 23.701 vc00 WebRTC Access to IMS Study Rel-12 read
TS 23.722 vf10 Common API Framework (CAPIF) for 3GPP Northbound APIs Rel-15 read
TS 23.768 vc10 GCSE_LTE Architecture Study Rel-12 read
TS 23.795 vg10 V2X Application Architecture Study Rel-16 read
TR 23.799 ve00 Study on Next Generation System Architecture Rel-14 read
TS 23.803 v700 PCC Architecture Harmonization Study Rel-7 read
TS 24.229 vk10 IMS SIP/SDP Call Control Protocol Rel-20 read
TR 24.930 vj00 IMS Session Setup Signalling Flows Rel-19 read
TS 25.467 vj00 UTRAN Architecture for 3G Home Node B Rel-19 read
TS 26.233 vf00 3GPP Packet-Switched Streaming Service (PSS) Rel-15 read
TR 26.924 vj00 MTSI QoS Improvement Study Rel-19 read
TS 28.708 vj00 EPC NRM Integration Reference Point Information Service Rel-19 read
TS 28.709 vj00 EPC NRM IRP Solution Set Definitions Rel-19 read
TS 29.061 vk10 Packet Domain Interworking Requirements Rel-20 read
TS 29.122 vk10 T8 SCEF Service Exposure APIs Rel-20 read
TS 29.154 vj00 Nt Reference Point Protocol Rel-19 read
TS 29.155 vj00 REST-based St Reference Point Protocol Rel-19 read
TS 29.165 vk00 Inter-IMS Network-to-Network Interface (II-NNI) Rel-20 read
TS 29.201 vj00 RESTful Rx Interface for AF-PC Communication Rel-19 read
TS 29.212 vk00 Diameter-Based PCC Reference Points Rel-20 read
TS 29.213 vj30 PCC Procedures and Flows Rel-19 read
TS 29.214 vk00 Rx Interface for Policy and Charging Control Rel-20 read
TS 29.215 vj00 S9 Reference Point Stage 3 Specification Rel-19 read
TS 29.217 vj00 Policy and Charging Control (PCC) for Np Interface Rel-19 read
TS 29.219 vj00 Sy Reference Point Stage 3 Specification Rel-19 read
TS 29.244 vk10 PFCP for Control and User Plane Separation Rel-20 read
TS 29.468 vj00 MB2 Reference Point Protocol Definition Rel-19 read
TS 29.522 vk10 NEF Northbound Interface Rel-20 read
TS 29.806 vc10 P-CSCF Restoration Analysis & Solutions Rel-12 read
TS 29.809 vc00 Diameter Overload Control Study Rel-12 read
TS 29.810 vd00 Diameter Load Control Study Rel-13 read
TS 29.816 va00 PCRF Failure and Restoration Study Rel-10 read
TS 29.817 vc10 Study on XML-based Rx interface for PCC Rel-12 read
TS 29.826 vd10 P-CSCF Restoration Enhancements for WLAN Rel-13 read
TS 29.827 vg00 Policy and Charging for Volume Based Charging Rel-16 read
TS 29.866 vj00 IMS Disaster Prevention & Restoration Enhancement Rel-19 read
TR 29.949 vj00 VoLTE IMS Roaming Architecture & Procedures Rel-19 read
TS 32.240 vk10 3GPP Charging Architecture and Principles Rel-20 read
TS 32.260 vk10 IMS Charging Management Rel-20 read
TS 32.296 vj00 Online Charging System (OCS) Architecture Rel-19 read
TS 32.409 vj00 IMS Performance Management Measurements Rel-19 read
TS 32.752 vb01 EPC Network Resource Model Information Service Rel-11 read
TS 32.753 v920 EPC NRM IRP CORBA Solution Set Rel-9 read
TS 32.756 vb00 EPC NRM IRP Solution Set Definitions Rel-11 read
TS 32.843 vd00 Inter-PLMN Online Charging for Roaming Rel-13 read
TS 33.107 vj00 Lawful Interception Architecture & Functions Rel-19 read
TS 36.868 vc00 Study on Group Communication for E-UTRA Rel-12 read
TS 37.579 vi50 Mission Critical (MC) services Rel-18 read