Description
The UE Policy Section Code (UPSC) is a concept introduced in 5G System (5GS) architecture, defined in specifications such as 3GPP TS 24.501 (UE procedures) and TS 29.525 (PCF services). It is a key element in the UE Policy Control framework, which governs how the UE connects to networks and routes traffic. The PCF (Policy Control Function) is responsible for generating and providing policy information to the UE. This policy is not sent as one monolithic block but is structured into distinct sections, each identified by a unique UPSC. The primary policy sections are the UE Route Selection Policy (URSP), the Access Network Discovery and Selection Policy (ANDSP), and V2X-related policies.
The UPSC acts as a handle or index. When the PCF needs to provision, modify, or remove a specific piece of policy for a UE, it references the corresponding UPSC in its communication with the AMF (Access and Mobility Management Function) and ultimately the UE. For instance, the PCF may send a Npcf_UEPolicyControl_UpdateNotify service operation to the AMF, indicating an update for a policy section identified by a specific UPSC value. The AMF then forwards this indication to the UE via a UE Configuration Update or DL NAS TRANSPORT message. The UE, upon receiving the notification for a given UPSC, can then request the updated policy content for that specific section from the PCF, often via a UE policy delivery procedure.
This segmented approach, enabled by the UPSC, is crucial for efficiency. It allows for fine-grained policy management where only the changed section of policy needs to be transmitted, reducing signaling overhead and UE processing. Each UPSC is associated with a specific policy type and format. For example, URSP rules (which determine how the UE routes traffic to specific applications to different network slices or DNNs) are managed under their designated UPSC. This modular structure supports the dynamic and service-driven nature of 5G, where policies for network slicing, edge computing, or V2X communications can be updated independently without affecting other policy domains.
Purpose & Motivation
The UE Policy Section Code was created to address the limitations of monolithic policy management in previous generations and to support the enhanced, slice-aware policy framework of 5G. In 4G/EPS, ANDSP was delivered but the mechanisms for policy update were less granular. 5G introduced the comprehensive URSP concept, which is far more complex and likely to change frequently based on user subscription, application needs, and network slice availability. A mechanism was needed to manage these diverse and dynamic policies efficiently.
The UPSC solves the problem of inefficient policy updates. Without section codes, any policy change would require the entire policy set to be retransmitted to the UE, consuming significant radio resources and UE battery life. By enabling targeted updates per section, the UPSC minimizes signaling overhead. It also provides a clear structure for the UE to organize and store different policy types. This was motivated by the 5G design principles of flexibility and efficiency, supporting use cases where policies for IoT, enhanced mobile broadband, and ultra-reliable low-latency communications might need independent and rapid adaptation.
Key Features
- Unique numeric code identifying a section of UE policy (e.g., URSP, ANDSP)
- Enables targeted provisioning, modification, and removal of specific policy sections
- Referenced in PCF-to-network (Npcf) and network-to-UE (NAS) signaling
- Reduces signaling overhead by allowing partial policy updates
- Supports key 5G policy types: URSP, ANDSP, and V2X policies
- Integral part of the UE policy delivery and update procedures in 5GS
Evolution Across Releases
Initial definition as part of the 5G Phase 1 standards. Established the UPSC as the mechanism for identifying UE policy sections like URSP and ANDSP. Defined the procedures in TS 24.501 for UE handling and in TS 29.525 for PCF service-based interactions, forming the foundation for granular UE policy management.
Defining Specifications
| Specification | Title |
|---|---|
| TS 24.501 | 3GPP TS 24.501 |
| TS 29.525 | 3GPP TS 29.525 |