Description
The Policy and Charging Enforcement Function (PCEF) is a critical logical entity within the 3GPP Policy and Charging Control (PCC) framework, introduced in Release 7. It resides at the border between the mobile core network and external packet data networks (e.g., the internet). Functionally, the PCEF is embedded within the gateway that handles the user plane traffic, such as the Gateway GPRS Support Node (GGSN) in GPRS/UMTS, the Packet Data Network Gateway (P-GW) in EPS (LTE), and the User Plane Function (UPF) in 5GC. Its primary role is to enforce in real-time the policy and charging control decisions made by the Policy and Charging Rules Function (PCRF).
The PCEF operates by intercepting user data flows (identified by IP 5-tuple or other filters) and applying the specific rules instructed by the PCRF. These rules are conveyed via the Gx reference point (or N7 in 5GC) and are encapsulated in Policy and Charging Control (PCC) rules. Each PCC rule contains information for enforcement and charging. For enforcement, the PCEF performs functions like gating (blocking or allowing flows), bandwidth control (setting uplink/downlink maximum bit rates, QoS Class Identifier), priority management, and redirection. For charging, the PCEF applies the charging method (online, offline, or both), identifies the relevant charging key, and reports usage events (e.g., volume, duration) to the Online Charging System (OCS) via the Gy interface or the Offline Charging System (OFCS) via the Gz interface.
Its operation is dynamic and session-aware. The PCEF interacts with the PCRF during session establishment, modification, and termination. It can also trigger updates by informing the PCRF of events it detects in the user plane, such as a change in user location, depletion of quota, or the start of a new service data flow. This closed-loop feedback allows for highly granular and responsive policy control. For example, when a user starts a video stream, the PCEF, upon instruction from the PCRF, can dynamically open a dedicated bearer with guaranteed bit rate, apply specific charging rates, and later downgrade the QoS when the stream ends. This architecture centralizes policy logic in the PCRF while decentralizing high-performance enforcement to the traffic-chokepoint gateways via the PCEF.
Purpose & Motivation
The PCEF was created to solve the limitations of static, pre-configured policy and charging mechanisms in earlier mobile data networks (pre-Release 7). Initially, policy control (like access control and QoS) and charging were largely separate, static functions configured directly on the gateway. This made it difficult to implement dynamic, service-aware, and user-specific policies in real-time. Operators could not easily offer tiered service plans, real-time spending controls, or optimized QoS for specific applications like VoIP or video.
The introduction of the PCC architecture, with the PCEF as its enforcement arm, was motivated by the need for a standardized, flexible, and centralized policy control framework. It separated the policy decision logic (PCRF) from the enforcement (PCEF), enabling real-time interaction between the network's control plane and user plane. This solved key business and technical problems: it allowed for sophisticated service differentiation, enabling new revenue models like sponsored data, zero-rating, and quality-on-demand. Technically, it provided the tools for efficient network resource management, ensuring critical services received necessary bandwidth while preventing any single user or service from overwhelming the network.
Furthermore, it integrated charging directly with policy enforcement, enabling accurate, flow-based charging that could align with marketing offers (e.g., social media data packs). The PCEF's role at the gateway makes it the ideal point for enforcement, as all user traffic must pass through it, allowing for comprehensive visibility and control. Its creation was a foundational step towards the service-aware, monetizable, and efficiently managed mobile broadband networks that followed.
What changed in its specifications
The latest release-to-release comparison of specifications that define PCEF. Each summary describes the whole specification, not only this term.
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 →Rel-7 replaced PDF/Go/Gq with PCRF-based policy control, added new Gx/Rx interfaces, and introduced PCC terminology.
Full comparison in TS 23.207 →Technology family
Core network elements and functions · Core Network
- Phase 1 AuC, EIR, GMSC, HLR, IWF, MSC, VLR
- Phase 2 SMS-GMSC, SMS-IWMSC
- R96 GGSN, SGSN
- R99 3G-SGSN, GLR, IM-GSN, IM-MSC
- Rel-4 CS-MGW, GMSC Server, MSC Server
- Rel-5 HSS, SLF
- Rel-6 3GPP AAA Server
- Rel-7 PCEF, PCRF
- Rel-8 ANDSF, BBERF, ePDG, MME, PGW, SGW
- Rel-9 HLR-FE, HSS-FE, UDR
- Rel-10 L-GW
- Rel-11 TDF
- Rel-14 PGW-C, PGW-U, SGW-C, SGW-U, TDF-C, TDF-U
- Rel-15 AMF, AUSF, PCF, SMF, SMF+PGW-C, UDM, UPF
- PCEF used together with PCRF
“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 sourcesDocumented changes in 13 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.
The PCEF is specified for the first time in Rel-7: it selects and enforces PCC rules, performs bearer binding, gates flows, requests credit, and exchanges CC-Requests with the PCRF over Gx.
- “The PCEF shall select a PCC rule for each received packet by evaluating received packets against service data flow filters of PCC rules” TS 29.212 v7.16.0
- “For a service data flow that is under policy control the PCEF shall allow the service data flow to pass through the Gateway if and only if the corresponding gate is open.” TS 29.212 v7.16.0
- “The PCEF performs the bearer binding, unless specified differently in Annex A and Annex D” TS 23.203 v7.14.1
PCEF behaviour changed in Rel-8: it reports tunnelling header info and Default-EPS-Bearer-QoS, sends resource modification requests with Packet-Filter-Operation, and handles bearer binding and credit management differently.
- “In case the SDF is tunnelled at the BBERF, the PCEF shall inform the PCRF about the mobility protocol tunnelling header” TS 29.212 v8.24.0
- “the PCEF shall include within the CC-Request the Event-Trigger AVP set to RESOURCE_MODIFICATION_REQUEST” TS 29.212 v8.24.0
- “the PCEF may provide the Default-EPS-Bearer-QoS AVP including the ARP and QCI values” TS 29.212 v8.24.0
PCEF gained new behaviour: usage monitoring with volume measurement and threshold reporting, plus an emergency-session inactivity timer that terminates the IP-CAN session when emergency PCC rules are removed.
- “The PCEF shall support usage monitoring as specified in clause 4.4.” TS 23.203 v9.14.0
- “the PCEF shall start a configurable inactivity timer (e.g., to enable PSAP Callback session)” TS 23.203 v9.14.0
- “the PCEF shall measure the volume of all traffic for the IP-CAN session or the corresponding service data flows and notify the PCRF” TS 29.212 v9.19.0
The PCEF gained new behaviour for IP flow mobility: it derives routing rules from UE flow bindings and installs, modifies and removes them at the PCRF over Gx using Routing-Rule AVPs and the ROUTING_RULE_CHANGE event trigger.
- “The PCEF shall provide IP flow mobility routing rules and report IP flow mobility routing rules related events to the PCRF via the Gx reference point.” TS 29.212 v10.17.0
- “the PCEF shall derive IP flow mobility routing rules based on the IP flow mobility binding information provided by the UE.” TS 29.212 v10.17.0
- “The PCEF includes the ROUTING_RULE_CHANGE event trigger to indicate that a change in the IP flow mobility routing rules has occurred.” TS 29.213 v10.15.0
In Rel-11 the PCEF gained optional Application Detection and Control support, with new reporting of application start/stop, redirection of detected application traffic, and revised bearer binding and precedence handling.
- “NOTE 1: The PCEF may support Application Detection and Control feature.” TS 29.212 v11.19.0
- “The PCEF shall detect Start and Stop of the application traffic for the PCC rules used for application detection” TS 23.203 v11.15.0
- “If Redirect-Information AVP is provided for a dynamic PCC rule, the PCEF shall implement the redirection for the detected application's uplink traffic.” TS 29.212 v11.19.0
PCEF behaviour was extended in Rel-12: it stores and enforces conditional APN-AMBR policy by RAT/IP-CAN type, reports RAN/NAS release causes, and measures time as well as volume for usage monitoring.
- “The PCEF stores this information and enforces the APN policy info corresponding to the RAT” TS 29.212 v12.14.0
- “the PCEF shall provide the received cause(s) in the RAN-NAS-Release-Cause AVP included in the Charging-Rule-Report AVP” TS 29.212 v12.14.0
- “The PCEF shall be able to support volume and time measurements simultaneously for a given IP-CAN session or service data flows.” TS 29.212 v12.14.0
PCEF behaviour was extended in Rel-13 for NBIFOM: it derives NBIFOM routing rules from UE requests, reports them to the PCRF, and performs access-aware bearer binding, plus traffic steering support.
- “the PCEF shall derive NBIFOM routing rules based on the NBIFOM routing rules or the IP flow mapping provided by the UE.” TS 29.212 v13.13.0
- “The bearer binding mechanism in the PCEF shall, in addition to the requirements defined in 6.1.1.4, ensure that a PCC Rule is associated” TS 23.203 v13.10.0
- “The PCEF shall support traffic steering as specified in clause 6.1.17.” TS 23.203 v13.10.0
PCEF behaviour was extended in Rel-14: time-conditioned APN and default bearer QoS enforcement, binding of rules to the default bearer, 3GPP PS Data Off support, and decomposition into user and control plane functions.
- “At the time indicated in the Execution-Time AVP, the PCEF shall perform the requested change without interaction with the PCRF.” TS 29.212 v14.11.0
- “If the Default-Bearer-Indication AVP set to BIND_TO_DEF _BEARER (0) within the Charging-Rule-Definition AVP is received in the PCEF, the PCEF shall bind the related PCC rule to the default bearer.” TS 29.212 v14.11.0
- “The PCEF shall support 3GPP PS Data Off as specified in clause 6.1.21.” TS 23.203 v14.6.0
PCEF behaviour was extended in Rel-15: it reports UE resume from suspend state to the PCRF, enforces conditional APN-AMBR with extended bitrate AVPs, and handles Max-PLR for QCI=1 bearers.
- “If the UE’s status is resumed from suspend state, the PCEF shall inform the PCRF of the UE status including the Event-Trigger AVP sets to "UE_STATUS_RESUME".” TS 29.212 v15.9.0
- “the PCEF shall set the downlink and/or uplink maximum packet loss rate value(s) to the lowest one for each direction among all of the values sharing the QCI=1 bearer.” TS 29.212 v15.9.0
- 23.203 PCEF Support for Data Off phase 2 TS 23.203CR1099
PCEF behaviour was extended: after PCRF restart it may tear down the PDN connection except for emergency, RLOS and eMPS sessions, and RLOS PDN connection duration is controlled by local policy in the PCEF.
- “Emergency, RLOS and eMPS sessions should not be torn down.” TS 29.212 v16.4.0
- “Duration of PDN connection for RLOS is controlled through local policies in PCEF.” TS 23.203 v16.3.0
- “sends it to PCEF along with the PCC rule for the voice media.” TS 23.203 v16.3.0
PCEF behaviour changed: it now provides IMEI(SV) via User-Equipment-Info-Extension, confirms MPS for DTS resource allocation via SUCCESSFUL_QOS_UPDATE, and indicates satellite access for PDN connections.
- “The PCEF shall also provide IMEI(SV) (if available) within the User-Equipment-Info AVP or the User-Equipment-Info-Extension AVP” 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
- “If PCEF indicates that a PDN connection is carried over satellite access” TS 23.203 v17.2.0
PCEF gains EPC health monitoring behaviour: on a Gx RAR from the PCRF it reports session restoration status in the RAA, or returns DIAMETER_UNKNOWN_SESSION_ID if the session is not found.
- “The PCEF shall provide the required EPC health monitoring information to the PCRF in the Gx RAA command as follows:” TS 29.212 v19.1.0
- “the PCEF shall send a Gx RAA command with DIAMETER_UNKNOWN_SESSION_ID result code.” TS 29.212 v19.1.0
- Update the procedure of AF trigger the PCEF failure checking TS 29.213CR0753
PCEF now reports the UDP/IP Header Removal & Restoration (UHRR) capability of the IP-CAN session to the PCRF, at session establishment and on change, via a new event trigger and UHRR-Capability AVP on Gx.
- “The PCEF shall report the UHRR capability of the IP-CAN to the PCRF by including the UHRR-Capability AVP in the Gx RAA command” TS 29.212 v20.0.0
- “The PCEF reports when the UDP/IP Header Removal & Restoration capability of the IP-CAN session has changed.” TS 23.203 v20.1.0
- “the PCEF shall provide the updated UHRR capability of the IP-CAN to the PCRF by including the UHRR-Capability AVP in the Gx CCR command” TS 29.212 v20.0.0
Defining Specifications
3GPP specifications that define or reference PCEF, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| 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.468 vj00 | Group Communication System Enablers for LTE | Rel-19 read |
| TS 23.701 vc00 | WebRTC Access to IMS Study | Rel-12 read |
| TR 26.924 vj00 | MTSI QoS Improvement Study | Rel-19 read |
| TS 29.154 vj00 | Nt Reference Point Protocol | Rel-19 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.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.250 vj00 | Nu Reference Point Stage 3 Specification | Rel-19 read |
| TS 29.251 vj00 | Gw/Gwn Reference Points Stage 3 Specification | Rel-19 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.827 vg00 | Policy and Charging for Volume Based Charging | Rel-16 read |
| TS 32.240 vk10 | 3GPP Charging Architecture and Principles | Rel-20 read |
| TS 32.251 vj00 | PS Domain Charging Management | Rel-19 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.843 vd00 | Inter-PLMN Online Charging for Roaming | Rel-13 read |