Description
The Generic Public Subscription Identifier (GPSI) is a critical identifier in the 5G System (5GS) defined in 3GPP TS 23.501. It serves as a public-facing, globally unique address for a subscription, used by external Application Functions (AFs) and within the network to reference a user. There are two primary formats: an MSISDN (Mobile Subscriber Integrated Services Digital Network Number), which is a telephone number in E.164 format, and an External Identifier, which is a string formatted as 'username@realm'. The GPSI is stored in the Unified Data Management (UDM) as part of the subscription data and is associated with the SUPI (Subscription Permanent Identifier). Its key role is in service exposure via the Network Exposure Function (NEF) and in edge computing scenarios. When an external AF needs to interact with the network for a specific user (e.g., to influence traffic routing for low-latency applications), it uses the user's GPSI in its requests to the NEF. The NEF then translates this public GPSI into the internal SUPI for network operations, ensuring privacy. The GPSI is also used in UE policy configuration, SMS over NAS, and as a parameter in the Nnef_ services. Its handling involves strict privacy measures; for example, the GPSI is not used over the radio interface and is mapped to the SUPI within the secure core network domain.
Purpose & Motivation
GPSI was introduced in 5GS to fulfill the need for a stable, public, and user-friendly identifier that can be used by third-party application providers and within network service APIs, decoupling service addressing from internal network identifiers. Previous systems used MSISDN for this purpose, but this tied services to a specific numbering format (E.164) and was less flexible for non-telephony services or users without a phone number. The GPSI, with its support for both MSISDN and External Identifier (like an email address), solves this problem by providing a generic scheme. This is essential for 5G's service-based architecture and edge computing, where external applications need a consistent way to identify subscribers without being aware of their private SUPI or temporary 5G-GUTI. It addresses the limitations of using internal identifiers externally (a privacy and security risk) and the inflexibility of relying solely on MSISDN, enabling new business models and seamless integration with internet-based services and identity federations.
What changed in its specifications
The latest release-to-release comparison of specifications that define GPSI. Each summary describes the whole specification, not only this term.
Rel-19 added real-time flight path reporting, QoS-based flight route selection, no-transmit zone management, and supporting APIs/procedures for UAS applications.
Full comparison in TS 23.255 →Rel-18 added VRU zone management, V2P communication support, and service adaptation QoS control procedures and APIs.
Full comparison in TS 23.286 →Technology family
Subscriber and device identifiers · User Equipment
- Phase 1 IMEI, IMSI, MSIN, MSISDN, TMSI
- Phase 2 IMEISV
- R96 TLLI
- R97 P-TMSI
- R98 CTSMSI
- Rel-5 IMPI, IMPU, Temporary Public User Identity
- Rel-8 GUTI, M-TMSI
- Rel-15 5G-GUTI, 5G-S-TMSI, 5G-TMSI, GPSI, NSI, PEI, SUCI, SUPI
- Rel-16 GCI, GLI, Truncated 5G-S-TMSI
- GPSI builds on MSISDN (not stated verbatim in the specifications)
Members and relations were proposed independently by several models and kept only where at least two agree; quotes are verified verbatim against the specifications. Release = first approved version of the defining specification.
Release Timeline
Detected Changes Across Releases
verified against 3GPP sourcesDocumented changes in 6 releases, each verified against the text of 3GPP specifications or approved change requests and shown with the exact wording. The release timeline above shows the same releases. A release without an entry has no documented change for this term.
GPSI is first specified in Rel-15 5G specs: defined in TS 23.003, included in AMF/SMF PDU session signalling, used for DN-AAA, and translated to SUPI by UDM via Nudm services.
- Definition of GPSI TS 23.003CR0521
- “The GPSI shall be included if available at AMF.” TS 23.502 v15.17.0
- “The NEF invokes Nudm_SDM_Get (Identifier Translation, GPSI and AF Identifier) to resolve the GPSI to SUPI” TS 23.502 v15.17.0
GPSI gains new roles in Rel-16: it is required for Network Slice-Specific Authentication and Authorization, and is used for PCF selection and SUPI/GPSI translation by UDM.
- “The Network Slice-Specific Authentication and Authorization procedure requires the use of a GPSI.” TS 23.502 v16.19.0
- GPSI used for PCF selection TS 29.513CR0184
- “sends a request to the UDM to receive the SUPI/GPSI that corresponds to the provided GPSI/SUPI” TS 29.503 v16.18.0
Rel-17 extends GPSI handling: UDM identity translation takes AF-specific parameters into account, GPSI is added to the SM policy association for ON-SNPN, and a GPSI_REMOVED revocation cause is defined.
- “the UDM shall take the provided AF specific information into account to determine the GPSI (i.e. External Identifier) to be returned for the UE.” TS 29.503 v17.22.0
- “a GPSI which is not longer associated to an individual subscription and the revocation cause shall be set to "GPSI_REMOVED".” TS 29.503 v17.22.0
- “The GPSI, PVS FQDN(s) and/or PVS IP address(es) and the Onboarding Indication shall be included if available at SMF in the case of ON-SNPN.” TS 23.502 v17.15.0
In Rel-18 GPSI gained new roles: it is added to the 5GC-MT-LR procedure, mapped to Application Layer IDs, resolved to the subscription network via NRF, and may be an MSISDN returned by the UDM.
- “If target is GPSI, the NEF determines PLMN owning the GPSI (i.e. HPLMN of the UE).” TS 23.502 v18.14.0
- Adding GPSI to 5GC-MT-LR Procedure without UDM Query procedure TS 23.273CR0509
- Provision mapping between Application Layer ID and GPSI TS 29.522CR1204
In Rel-19 the UDM gains handling of GPSI: AF-specific GPSI generation, multiple SUPI-to-GPSI translation, MSISDN-form GPSI retrieval, and static IP address provisioning per GPSI.
- “Any UDM (in the same UDM group) shall be able to extract the SUPI from the received AF specific GPSI.” TS 29.503 v19.7.0
- “the first GPSI in the list of GPSIs associated to the SUPI received from UDR.” TS 29.503 v19.7.0
- AF Specific GPSI Generation TS 29.503CR1492
For emergency MO-SMS, the SMSF must now provide the UE GPSI (the MSISDN) and the UE location information when delivering the message to the SMS-IWMSC/SC in the serving PLMN.
- “The SMSF provides the UE GPSI (i.e. the MSISDN) and UE ULI (e.g. Cell-ID) when sending the SMS message to the SMS-IWMSC/SC” TS 23.502 v20.3.0
- “The AAA-S triggers a re-authentication and re-authorization for a user associated with a GPSI in a certain network slice associated with a S-NSSAI.” TS 23.502 v20.3.0
Defining Specifications
3GPP specifications that define or reference GPSI, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 23.255 vk10 | UAS Application Enabler Architecture | Rel-20 read |
| TS 23.286 vk10 | V2X Application Enabler Architecture | Rel-20 read |
| TS 23.434 vk10 | Service Enabler Architecture Layer (SEAL) for Verticals | Rel-20 read |
| TS 23.501 vk30 | 5G System Architecture | Rel-20 read |
| TS 23.540 vk00 | 5G Service-Based SMS Architecture | Rel-20 read |
| TS 23.558 vk30 | Enabling Edge Applications | Rel-20 read |
| TR 23.758 vh00 | Study on Edge Application Architecture | Rel-17 read |
| TS 24.257 vj40 | UAS Application Enabler (UAE) Layer | Rel-19 read |
| TS 24.583 vj10 | Application layer support for Personal IoT Network | Rel-19 read |
| TS 26.510 vj20 | 5G Media Streaming and Real-Time Communication APIs | Rel-19 read |
| TS 26.512 vj30 | 5G Media Streaming Protocols and APIs | Rel-19 read |
| TS 28.204 vi11 | Charging management | Rel-18 read |
| TR 28.840 vi10 | Technical Report | Rel-18 read |
| TS 29.503 vk10 | UDM Service Based Interface | Rel-20 read |
| TS 29.504 vk10 | Nudr Unified Data Repository Services | Rel-20 read |
| TS 29.505 vk00 | UDR Services for Subscription Data | Rel-20 read |
| TS 29.507 vk10 | Access and Mobility Policy Control | Rel-20 read |
| TS 29.508 vk10 | Session Management Event Exposure Service | Rel-20 read |
| TS 29.514 vk10 | Policy Authorization Service | Rel-20 read |
| TS 29.515 vk10 | Ngmlc Location Services API | Rel-20 read |
| TS 29.517 vk10 | AF Event Exposure Service | Rel-20 read |
| TS 29.518 vk10 | AMF Service Based Interface | Rel-20 read |
| TS 29.519 vk10 | 5G UDR Policy and Application Data Services | Rel-20 read |
| TS 29.521 vk10 | Binding Support Management Service | Rel-20 read |
| TS 29.522 vk10 | NEF Northbound Interface | Rel-20 read |
| TS 29.523 vk10 | Policy Control Event Exposure Service | Rel-20 read |
| TS 29.525 vk10 | UE Policy Control Service | Rel-20 read |
| TS 29.530 vk10 | 5G AF AI/ML Services | Rel-20 read |
| TS 29.535 vk10 | AAnF Service Based Interface | Rel-20 read |
| TS 29.558 vk00 | Edge Application Enablement APIs | Rel-20 read |
| TS 29.561 vk10 | 5G Network Interworking Procedures | Rel-20 read |
| TS 29.562 vk10 | HSS Nhss Services for IMS and GBA | Rel-20 read |
| TS 29.571 vk10 | 5G Common Data Types | Rel-20 read |
| TS 29.591 vk10 | NEF Southbound Services | Rel-20 read |
| TS 29.594 vk00 | 5G Spending Limit Control Service (Nchf) | Rel-20 read |
| TR 29.829 vh10 | SMS Service-Based Interfaces for 5G Core | Rel-17 read |
| TS 29.890 vg00 | CT3 5G System Technical Report | Rel-16 read |
| TS 32.255 vk30 | 5G Data Connectivity Converged Charging | Rel-20 read |
| TS 32.256 vk10 | 5G Connection and Mobility Charging | Rel-20 read |
| TS 32.291 vk10 | 5G Charging Service-Based Interface | Rel-20 read |
| TS 33.127 vj80 | Lawful Interception Architecture | Rel-19 read |
| TR 33.739 vi10 | Study on security enhancement of support for | Rel-18 read |
| TS 33.749 vj00 | Study on security aspects of edge computing enhancement | Rel-19 read |
| TS 33.835 vg10 | Study on authentication and key management for apps | Rel-16 read |
| TR 33.867 vh10 | User Consent for 3GPP Services | Rel-17 read |
| TS 38.473 vj40 | F1 Application Protocol (F1AP) | Rel-19 read |