PEF

Policy Enforcement Function

Core Network →
Introduced in Rel-2

PEF is the network function that enforces policy decisions for user sessions, such as QoS, charging, and access control, to ensure network resources are allocated according to operator policies.

Category
Core Network
Introduced
Rel-2
Where
Core Network › 5G Core
Specifications
1 specs
PEF Description Purpose Related Classification Detected Changes Specifications

Description

The Policy Enforcement Function (PEF) is a core network component defined in 3GPP specifications, notably in TS 23.228, as part of the IP Multimedia Subsystem (IMS) and policy control architecture. It operates within the Policy and Charging Control (PCC) framework, where it works in conjunction with the Policy and Charging Rules Function (PCRF) to apply policy decisions to user data sessions. The architecture typically positions the PEF at the gateway level, such as in the Packet Data Network Gateway (PGW) in 4G or the Session Management Function (SMF) in 5G, where it can intercept and manipulate data flows based on policies received from the PCRF.

In operation, the PEF receives policy rules from the PCRF via the Gx interface (in 4G) or the N7 interface (in 5G). These rules include instructions for Quality of Service (QoS) parameters (e.g., bandwidth limits, priority levels), charging actions (e.g., online or offline charging triggers), and access control (e.g., blocking or allowing specific services). The PEF then enforces these rules by configuring the user plane functions, such as traffic detection, gating (allowing or denying packets), and QoS marking. For example, it might apply a guaranteed bit rate for a video stream or throttle bandwidth for a low-priority application. Key components of the PEF include the Traffic Detection Function (TDF) for identifying application flows and the Enforcement Point (EP) where policies are physically applied to packets.

The role of the PEF in the network is crucial for dynamic policy management, enabling operators to offer differentiated services and optimize network performance. It ensures that policy decisions are translated into actionable changes in the data path, supporting use cases like sponsored data, parental controls, and network slicing. By enforcing policies in real-time, the PEF helps maintain service level agreements (SLAs), manage congestion, and implement charging schemes. In evolved architectures, such as 5G's Service-Based Architecture (SBA), the PEF functionality is integrated into network functions like the SMF and User Plane Function (UPF), providing more flexible and scalable policy enforcement across diverse services.

Purpose & Motivation

The PEF was created to address the need for dynamic and granular policy control in mobile networks, as services evolved beyond basic voice and SMS to include multimedia, internet access, and IoT applications. Before its standardization, policy enforcement was often static, hard-coded into network equipment, limiting operators' ability to adapt to changing traffic patterns or offer personalized services. The limitations included inflexible QoS management, lack of real-time charging integration, and difficulty in enforcing service-specific rules, leading to inefficient resource use and reduced revenue opportunities.

Motivated by the growth of IMS and data services in 3GPP Release 2 and beyond, the PEF emerged as part of the PCC framework to enable operators to control network behavior based on policies. It solves problems such as how to allocate bandwidth dynamically for different applications, how to implement fair usage policies, and how to integrate charging with service delivery. Historically, early mobile networks had basic policy mechanisms, but the PEF provided a standardized, interoperable approach that separated policy decision-making (in PCRF) from enforcement (in PEF), allowing for more flexible and scalable network management.

The PEF also addresses operational challenges like network congestion and service differentiation. For instance, with the rise of over-the-top (OTT) applications, operators needed tools to manage traffic without degrading user experience. The PEF enables this by enforcing policies that prioritize critical services or limit non-essential ones. Its evolution through releases like Rel-5 and Rel-6 added enhancements for deeper packet inspection and integration with charging systems, reflecting the ongoing need to balance network efficiency with service innovation. By providing a centralized enforcement point, the PEF helps operators monetize services, ensure quality, and maintain control over their networks.

Classification

Part ofPCRF
Related approachesQoSIMS

Detected Changes Across Releases

from 3GPP Change Requests

Specific changes extracted from the „Change history“ tables of 3GPP specifications (1 CRs across 1 releases). Complements the general historical overview above with the evidence-based evolution of this function.

Studied in Rel-2, normative work from Rel-17.

Rel-17 1 change

In Release 17, the Policy Enforcement Function's capabilities were expanded to support Paging Policy Differentiation for IMS conversational voice. This enhancement allows the PEF to apply operator-configured policies, specifically for setting the paging cause, based on the service type. These policies are integrated into the overall Policy and Charging Control framework, influencing how network resources are managed for specific IMS communication services.

  • Use of Paging Policy Differentiation for setting the Paging Cause TS 23.228CR1242

Explore further

Broader topics and technologies where PEF plays a role.

Defining Specifications

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

SpecificationTitleRelease
TS 23.228 vj50 IMS Stage-2 Service Description Rel-19