UPSI

UE Policy Section Identifier

Management →
Introduced in Rel-15

UPSI is a unique identifier for a specific policy section within the UE Policy, enabling the UE to manage, store, and apply different sets of network policies for dynamic control.

Category
Management
Introduced
Rel-15
Where
Core Network › 5G Core
Specifications
4 specs
UPSI Description Purpose Detected Changes Specifications

Description

The UE Policy Section Identifier (UPSI) is a critical component within the 3GPP's Policy Control Framework, specifically defined for the 5G System (5GS). It functions as a unique label or key that identifies a discrete, self-contained block of policy rules—known as a UE Policy Section—that is provisioned to the User Equipment (UE) by the network's Policy Control Function (PCF). The UE Policy itself is a comprehensive document that can contain multiple such sections, each identified by its own UPSI. These sections can pertain to different policy domains, such as Access Network Discovery and Selection Policy (ANDSP) for selecting between 3GPP and non-3GPP access, or UE Route Selection Policy (URSP) for determining how application traffic is routed (e.g., to a specific Data Network Name (DNN) or Network Slice). The UE stores these policy sections locally, associating each with its UPSI.

Architecturally, the UPSI is generated and managed by the PCF. When the PCF determines that a UE requires a new or updated policy, it assembles the UE Policy container, which includes one or more UE Policy Sections, each tagged with a UPSI. This container is then delivered to the UE via the Access and Mobility Management Function (AMF) using the N1 NAS transport mechanism. The specification 24.501 details the NAS signaling procedures for this delivery. The PCF can also manage the lifecycle of these policy sections through the Npcf_UEPolicyControl service, defined in 29.525, allowing it to provision, update, or delete specific sections identified by their UPSI.

The role of the UPSI is to enable efficient and granular policy management. Instead of retransmitting the entire UE Policy document for every change, the network can target individual sections. The UE uses the UPSI to identify which stored policy section to apply for a given context. For instance, when the UE needs to select an access network, it will locate the ANDSP section using its specific UPSI. This modular approach reduces signaling overhead, conserves UE storage by allowing selective updates, and provides the network with fine-grained control over UE behavior. The management of these identifiers and their associated sections is further supported by services like the Network Repository Function (NRF) for discovery, as referenced in specs 29.513 and 29.519.

Purpose & Motivation

The UPSI was introduced in 5G (Release 15) to address the limitations of monolithic policy management in previous generations like 4G EPS. In EPS, policy information like ANDSP was delivered as a single, indivisible blob. Any change, no matter how small, required the entire policy to be re-sent, leading to inefficient use of radio resources and UE processing. As 5G introduced more complex policy domains (notably URSP for sophisticated traffic steering and network slice selection), the need for modular, granular policy control became paramount.

The creation of the UPSI enables a data-driven, service-based policy architecture aligned with 5G's core principles. It solves the problem of scalable policy distribution in a network supporting diverse use cases, from enhanced mobile broadband to massive IoT and ultra-reliable low-latency communications. Each use case or tenant (via network slicing) might require a distinct set of rules. The UPSI allows the PCF to compose a tailored policy from discrete, reusable sections, updating only the parts that change. This is essential for supporting dynamic network conditions, subscriber-specific services, and efficient UE resource management, forming a foundational element for automated network and service management.

Release Timeline

Detected Changes Across Releases

from 3GPP Change Requests

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

Studied in Rel-15, normative work from Rel-18.

Rel-18 2 changes

In Release 18, the UPSI function was enhanced to enable the storage of UPSIs associated with a wider range of policy types, specifically for ProSeP, V2XP, A2XP, RSLPP, and N3AN node configuration information of ANDSP. This release also introduced clarifications for UPSI determination and handling during access type changes. Furthermore, the specifications were updated to define the storage of UPSIs for persistently stored signalled URSP rules, ensuring the UE can correctly manage the policy sections identified by these UPSIs.

  • UPSI Encoding TS 29.519CR0509
  • Clarification to UPSI determination and Access Type Change TS 29.525CR0333
Rel-19 2 changes

In Release 19, the UPSI function was extended to require the storage of UPSIs for a wider set of stored policy and configuration information. Specifically, the UE must now store the UPSI associated with received policy sections containing ProSeP, V2XP, A2XP, and RSLPP information, as well as the UPSI for N3AN node configuration information from ANDSP. This ensures the UE can properly manage and reference these specific policy sections, which include URSP rules and configuration data for services like proximity, vehicle, and aerial communications.

  • Storage of UPSI(s) for stored signalled URSP rules TS 24.501CR6612
  • Storage of UPSI(s) for ProSeP, V2XP, A2XP, RSLPP, and N3AN node configuration information of ANDSP TS 24.501CR6665

Explore further

Broader topics and technologies where UPSI plays a role.

Defining Specifications

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

SpecificationTitleRelease
TS 24.501 vj50 5G NAS Protocols Specification Rel-19
TS 29.513 vj40 5G PCC Signalling Flows & QoS Mapping Rel-19
TS 29.519 vj40 UDR Usage for Policy & Exposure Data Rel-19
TS 29.525 vj40 5G UE Policy Control Service Stage 3 Rel-19
Patrick Zandl

About the author: Patrick Zandl (b. 1974)

Telecommunications specialist, technology journalist (founder of the Mobil server), and developer who has been running since 2025 — the largest Czech-language resource on AI-assisted programming. Formerly Chief Wizard Architect at Prusa3D and head of development for Turris at CZ.NIC; currently a consultant and instructor on AI implementation in companies.