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

Glossary term · Core Network

Policy Control Request trigger

Policy Control Request Trigger

Core Network →

Policy Control Request trigger is a condition in a PCC rule that instructs the SMF to re-establish a policy session with the PCF when met, enabling dynamic policy updates.

Introduced
Rel-16
Where
Core Network › 5G Core
Specifications
2 specs
Policy Control Request trigger Description Purpose What changed Neighbours Detected Changes Specifications

Description

The Policy Control Request Trigger is a key concept in the 3GPP Policy and Charging Control (PCC) architecture, introduced in Release 16 for the 5G System. It defines a specific condition or event that, when detected by the Session Management Function (SMF), triggers the SMF to interact again with the Policy Control Function (PCF). This mechanism allows the PCF to dynamically update policy decisions based on changing network conditions or subscriber context without requiring continuous polling or persistent signaling.

In the 5G core network, the SMF is responsible for managing PDU sessions and enforcing policy rules received from the PCF. The PCF provides Policy Control Request Triggers as part of the PCC rules or as part of the session management policy association. These triggers are essentially event subscriptions that the SMF monitors. When a trigger condition is satisfied—such as a change in the user's location, a change in the access type, or the detection of a specific application—the SMF sends a notification to the PCF. The PCF can then make new policy decisions and provide updated rules to the SMF.

The triggers are defined in 3GPP TS 23.503 (Policy and Charging Control Framework for the 5G System) and TS 29.512 (5G System; Session Management Policy Control Service). TS 23.503 specifies the overall PCC architecture and the functional requirements for policy control, while TS 29.512 defines the stage 3 protocol details for the N7 interface between the SMF and PCF, including the representation of Policy Control Request Triggers in the HTTP/2-based service-based interface.

Examples of Policy Control Request Triggers include: "PLMN change" (when the UE moves to a different PLMN), "QoS change" (when the requested QoS parameters change), "EPS fallback" (when the UE falls back to EPS), "Access type change" (e.g., from 3GPP to non-3GPP access), and "Location change" (when the UE's location changes beyond a certain threshold). These triggers are typically provisioned by the PCF during the initial policy session establishment and can be updated dynamically.

The Policy Control Request Trigger mechanism is essential for enabling efficient and scalable policy control in 5G networks. It reduces unnecessary signaling by allowing the SMF to notify the PCF only when relevant events occur, rather than maintaining a persistent connection or periodic updates. This is particularly important in dense deployments with many UEs and diverse service requirements, such as network slicing and ultra-reliable low-latency communications (URLLC).

Purpose & Motivation

The Policy Control Request Trigger exists to enable dynamic and efficient policy control in the 5G core network. In earlier generations (e.g., 4G EPC), policy control was primarily based on static rules or periodic updates, which could lead to either stale policies or excessive signaling. The 5G System introduced a more flexible and service-based architecture, where the PCF can make real-time policy decisions based on network events. However, continuous communication between the SMF and PCF would be inefficient and could overload the control plane. The Policy Control Request Trigger solves this by defining specific conditions under which the SMF must notify the PCF, ensuring that policy updates occur only when necessary.

This mechanism also supports the diverse requirements of 5G services. For example, a URLLC service may require immediate policy changes when the UE's location changes to ensure low latency, while an enhanced Mobile Broadband (eMBB) service may only need updates when the QoS requirements change. By allowing the PCF to subscribe to specific triggers, the network can tailor policy control to the needs of each session, improving resource utilization and user experience.

Historically, the concept of event triggers in policy control was present in 4G (e.g., in the Gx interface between the PCRF and PCEF), but the 5G version is more granular and integrated with the service-based architecture. The introduction in Release 16 aligns with the broader 5G core specifications, which were first defined in Release 15 and enhanced in subsequent releases. The Policy Control Request Trigger is a testament to the 3GPP's ongoing efforts to optimize signaling and enable advanced use cases like network slicing and edge computing.

What changed in its specifications

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

TS 23.503Rel-18 → Rel-19

Rel-19 TS 23.503 adds Network Slice Replacement and Energy Saving Indicator reporting, Application Function influence on payload header handling, and Local Offloading Management Policy for edge computing. It also adds ATSSS Phase 4 multi-access steering (MPQUIC-E, ATSSS-LL), spending-limit policy for roaming, and PCF use of network analytics.

Full comparison in TS 23.503 →
TS 29.512Rel-18 → Rel-19

Rel-19 adds multi-access ATSSS capabilities, QoS monitoring with available-bitrate parameters, and XR/media policy provisioning such as data burst size and expedited transfer. It also adds local offloading management, non-3GPP device information, and URSP provisioning in EPS support.

Full comparison in TS 29.512 →

Release Timeline

Detected Changes Across Releases

from 3GPP Change Requests

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

Rel-16 3 changes
  • New UE Policy Control Request Trigger for V2X TS 23.503CR0285
  • Location change (serving cell) for Policy Control Request Trigger TS 23.503CR0491
  • Addition of Reallocation Of Credit missing Policy Control Request Trigger TS 23.503CR0349
Rel-17 5 changes
  • Satellite backhaul change policy control request trigger TS 29.512CR0681
  • Correction to policy control request trigger TS 29.512CR0764
  • Correction to the attribute name of policy control request trigger TS 29.512CR0979
  • Location change (serving cell) for Policy Control Request Trigger TS 29.512CR0631
  • Correction to the attribute name of policy control request trigger TS 29.512CR0976
Rel-18 2 changes
  • Applicability of the policy control request trigger for convergence scenario TS 29.512CR1060
  • Clarification of policy control request trigger TS 29.512CR1061

Defining Specifications

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

SpecificationTitleRelease
TS 23.503 vk30 5G Policy and Charging Control Framework Rel-20 read
TS 29.512 vk10 Session Management Policy Control Service Stage 3 Rel-20 read