Description
The Subscription Permanent Identifier (SUPI) is a critical concept in 5G system architecture, defined initially in 3GPP Release 15. It is a globally unique, non-changing identifier that permanently represents a user's subscription within the 3GPP ecosystem. The SUPI is used by the network for identification, authentication, authorization, and accounting purposes. It is stored securely in the Unified Data Management (UDM) and the Universal Subscriber Identity Module (USIM) on the user's device. The SUPI itself is never transmitted in clear text over the air interface to protect user privacy; instead, it is concealed using a privacy-preserving identifier called the Subscription Concealed Identifier (SUCI).
Architecturally, the SUPI is a key input to the 5G Authentication and Key Agreement (5G AKA) and Extensible Authentication Protocol (EAP)-AKA' procedures. During initial registration, the User Equipment (UE) generates a SUCI by encrypting the SUPI with the home network's public key, using the Elliptic Curve Integrated Encryption Scheme (ECIES). This SUCI is sent to the serving network (e.g., visited network in roaming scenarios). The serving network forwards the SUCI to the home network's Authentication Server Function (AUSF), which, with the help of the Subscription Identifier De-concealing Function (SIDF) in the UDM, decrypts it to retrieve the SUPI. The SUPI is then used to fetch the authentication vector and subscription profile from the UDM.
The SUPI can be in two main formats: an IMSI-based format or a Network Access Identifier (NAI) format. The IMSI-based SUPI follows the structure of an International Mobile Subscriber Identity (IMSI), consisting of a Mobile Country Code (MCC), Mobile Network Code (MNC), and Mobile Subscription Identification Number (MSIN). This ensures backward compatibility with legacy systems. The NAI-based SUPI is used for non-3GPP access (e.g., Wi-Fi) and follows the format username@realm. The SUPI's role extends beyond authentication; it is used in policy control (via the Policy Control Function (PCF)), charging (via the Charging Function (CHF)), and network slice selection (via the Network Slice Selection Function (NSSF)). Its permanent nature ensures consistent identification across sessions and mobility events, forming the backbone of subscription management in 5G.
Purpose & Motivation
The SUPI was introduced in 5G Release 15 to address privacy and security shortcomings of previous subscription identifiers, particularly the IMSI used in 4G LTE. In LTE, the IMSI was sometimes transmitted in clear text during initial attach procedures, making it vulnerable to eavesdropping and tracking attacks. This allowed malicious actors to identify and locate users, compromising privacy. The SUPI, combined with the SUCI mechanism, was designed to provide strong subscriber identity privacy by ensuring the permanent identifier is never exposed over the air.
Another motivation was to create a unified subscription identifier that works seamlessly across different access types (3GPP and non-3GPP) and supports emerging services like network slicing and IoT. The legacy IMSI was primarily designed for cellular access, whereas 5G envisions convergence with fixed and wireless local area networks. The SUPI's flexible formats (IMSI-based and NAI-based) accommodate this convergence, enabling consistent subscription management in heterogeneous networks.
Furthermore, the SUPI supports enhanced security protocols and home-routed traffic models in roaming scenarios. By keeping the SUPI concealed until it reaches the home network, it reduces the trust burden on visited networks and mitigates risks associated with international roaming. This aligns with 5G's design principles of security-by-design and privacy-by-design, addressing regulatory requirements like the General Data Protection Regulation (GDPR). The SUPI thus solves the dual problem of providing a robust, permanent subscription anchor while ensuring user privacy in an increasingly connected and scrutinized digital environment.
Classification
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (37 CRs across 5 releases). Complements the general historical overview above with the evidence-based evolution of this function.
- UDM Discovery with SUPI as input TS 23.501CR0091
- Subscription Permanent Identifier TS 23.501CR0189
- SUPI based paging TS 23.501CR0199
- SUPI definition and NAI format TS 23.501CR0653
- SUPI and SUCI as user identities TS 24.502CR0045
- Allow retrieval of AMF registrations with SUPI TS 29.503CR0123
+ 7 more changes
- IMSI based SUPI support when access an SNPN using credentials owned by CH TS 23.501CR2919
- Format of SUCI/SUPI used for Onboarding TS 23.501CR3097
- Handling of SUPI/SUCI format when accessing to a SNPN TS 23.501CR3045
- Update BSF NF profile to support SUPI and GPSI TS 23.501CR3108
- Mapping GPSIs and Group Identifiers to a SUPI list TS 29.503CR0956
- SUPI in UECM GET Responses TS 29.503CR0609
+ 1 more changes
Explore further
Broader topics and technologies where SUPI plays a role.
Defining Specifications
3GPP specifications that define or reference SUPI, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 23.003 vk00 | Numbering, Addressing and Identification | Rel-20 |
| TS 23.501 vk20 | 5G System Architecture Stage 2 | Rel-20 |
| TS 23.700 vk10 | AI/ML Application Layer Support Phase 2 | Rel-20 |
| TS 24.501 vk00 | 5G System (5GS) Non-Access Stratum (NAS) Protocol | Rel-20 |
| TS 24.502 vk00 | Non-3GPP Access Network Discovery and Selection | Rel-20 |
| TS 24.526 vj40 | UE Policies for 5G System (5GS) | Rel-19 |
| TS 28.204 vi11 | Charging management | Rel-18 |
| TR 28.840 vi10 | Technical Report | Rel-18 |
| TS 29.503 vk00 | UDM Service Based Interface Stage 3 | Rel-20 |
| TS 29.504 vk00 | 5G Unified Data Repository (UDR) Service Based Interface | Rel-20 |
| TS 29.505 vk00 | UDR Services for Subscription Data | Rel-20 |
| TS 29.507 vk00 | Access and Mobility Policy Control Service Stage 3 | Rel-20 |
| TS 29.508 vk00 | Session Management Event Exposure Service | Rel-20 |
| TS 29.514 vk00 | 3GPP TS 29514 vk00: Policy Authorization Service | Rel-20 |
| TS 29.515 vk00 | Ngmlc Service Based Interface (GMLC) | Rel-20 |
| TS 29.517 vk00 | AF Event Exposure Service Stage 3 | Rel-20 |
| TS 29.518 vk00 | 3GPP TS 29518 vk00: Namf Service Based Interface | Rel-20 |
| TS 29.519 vk00 | UDR Policy, Application & Exposure Data Service | Rel-20 |
| TS 29.520 vk00 | 5G Network Data Analytics Function Services | Rel-20 |
| TS 29.521 vk00 | BSF Binding Support Management Service | Rel-20 |
| TS 29.523 vk00 | Policy Control Event Exposure Service | Rel-20 |
| TS 29.525 vk00 | UE Policy Control Service Stage 3 | Rel-20 |
| TS 29.541 vk00 | NEF South-Bound Interfaces for NIDD and SMS | Rel-20 |
| TS 29.550 vk00 | Nsoraf Service Based Interface for SOR-AF | Rel-20 |
| TS 29.571 vk00 | Common Data Types for 5G SBI APIs | Rel-20 |
| TS 29.591 vk00 | Nnef Southbound SBI Stage 3 Protocol | Rel-20 |
| TS 29.594 vj30 | 5G Spending Limit Control Service Stage 3 | Rel-19 |
| TS 29.890 vg00 | CT3 5G System Technical Report | Rel-16 |
| TS 31.102 vj50 | USIM Application for 3GPP Telecom Networks | Rel-19 |
| TS 32.255 vk20 | 5G Data Connectivity Charging | Rel-20 |
| TS 32.256 vk00 | 5G Connection and Mobility Charging | Rel-20 |
| TS 32.291 vk00 | 3GPP TS 32.291 vk00: Service Based Interface for Charging | Rel-20 |
| TS 33.126 vj30 | Lawful Interception Requirements | Rel-19 |
| TS 33.127 vj70 | Lawful Interception Architecture and Functions | Rel-19 |
| TS 33.501 vk20 | 5G Security Architecture and Procedures | Rel-20 |
| TS 33.514 vk10 | 3GPP TS 33514 vk10: UDM Network Product Security Requirements | Rel-20 |
| TR 33.741 vi01 | Home Network Triggered Authentication | Rel-18 |
| TS 33.749 vj00 | Study on security aspects of edge computing enhancement | Rel-19 |
| TS 33.835 vg10 | Study on authentication and key management for apps | Rel-16 |
| TR 33.841 vg10 | Security aspects; Study on 256-bit algorithms for 5G | Rel-16 |
| TR 33.938 vj20 | 3GPP Cryptographic Inventory for 5G System | Rel-19 |