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.
Classification
Release Timeline
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (3 CRs across 2 releases). Complements the general historical overview above with the evidence-based evolution of this function.
In Release 15, the PCEF was enhanced with the "Data Off phase 2" capability. This introduces new mechanisms for the PCEF to enforce policy and charging control during specific service conditions, as indicated by the Change Request title. The technical implementation leverages the existing PCEF framework for applying online charging actions and policy control on a per-service data flow basis.
- 23.203 PCEF Support for Data Off phase 2 TS 23.203CR1099
In Release 19, enhancements were made to improve the reliability of the Policy and Charging Enforcement Function (PCEF) by introducing a new condition for the PCRF to detect PCEF failure in a timely manner. Furthermore, the procedure for an Application Function (AF) to trigger PCEF failure checking was updated, refining the interaction mechanisms defined for the Gx reference point and event reporting between network functions.
Explore further
Broader topics and technologies where PCEF plays a role.
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 vj20 | Policy and charging control architecture | Rel-19 |
| TS 23.207 vj00 | End-to-End QoS Framework for GPRS | Rel-19 |
| TS 23.228 vj50 | IMS Stage-2 Service Description | Rel-19 |
| TS 23.468 vj00 | Group Communication System Enablers for LTE | Rel-19 |
| TS 23.701 vc00 | WebRTC Access to IMS Architecture Study | Rel-12 |
| TR 26.924 vj00 | MTSI QoS Improvement Study | Rel-19 |
| TS 29.154 vj00 | Nt Reference Point Protocol | Rel-19 |
| TS 29.201 vj00 | RESTful Rx Interface for AF-PC Communication | Rel-19 |
| TS 29.212 vj00 | Gx/Gxx/Sd/St Diameter Protocol | Rel-19 |
| TS 29.213 vj20 | PCC Signalling Flows and QoS Mapping | Rel-19 |
| TS 29.214 vj20 | Policy and Charging Control over Rx | Rel-19 |
| TS 29.215 vj00 | S9 Reference Point Stage 3 Specification | Rel-19 |
| TS 29.219 vj00 | Sy Reference Point Stage 3 Specification | Rel-19 |
| TS 29.244 vj40 | PFCP Specification for Control/User Plane Separation | Rel-19 |
| TS 29.250 vj00 | Nu Reference Point Stage 3 Specification | Rel-19 |
| TS 29.251 vj00 | Gw/Gwn Reference Points Stage 3 Specification | Rel-19 |
| TS 29.810 vd00 | Diameter Load Control Study | Rel-13 |
| TS 29.816 va00 | PCRF Failure & Restoration Study | Rel-10 |
| TS 29.817 vc10 | Study on XML-based Rx interface for PCC | Rel-12 |
| TS 29.827 vg00 | Policy and Charging for Volume Based Charging | Rel-16 |
| TS 32.240 vj40 | Charging Management Architecture & Principles | Rel-19 |
| TS 32.251 vj00 | PS Domain Charging Management | Rel-19 |
| TS 32.296 vj00 | Online Charging System (OCS) Architecture | Rel-19 |
| TS 32.409 vj00 | IMS Performance Management Measurements | Rel-19 |
| TS 32.843 vd00 | PS Domain Online Charging in Roaming | Rel-13 |