Glossary term · Identifier

GPSI

Generic Public Subscription Identifier

Identifier →

GPSI is a globally unique, public identifier for a 3GPP subscription, such as an MSISDN, used to address a user across different network domains and with external applications.

Introduced
Rel-15
Specifications
46 specs
Category
Identifier
Introduced
Rel-15
Specifications
46 specs
GPSI Description Purpose Related Classification Detected Changes Specifications

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.

Classification

Part ofSUPI
Related approachesMSISDN

Detected Changes Across Releases

from 3GPP Change Requests

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

Rel-15 3 changes
  • Replace PUI with GPSI TS 23.501CR0049
  • Add GPSI in N5 TS 29.514CR0074
  • Sending of GPSI (MSISDN) in Initial Spenidng Limit retrieval TS 29.594CR0019
Rel-17 4 changes
  • GPSI for AIC - State 2 TS 33.127CR0156
  • Update BSF NF profile to support SUPI and GPSI TS 23.501CR3108
  • GPSI format TS 23.558CR0033
  • Event Exposure subscription revocation due to removal of GPSI TS 29.503CR0821
Rel-18 8 changes
  • Add GPSI and Application Layer ID mapping information TS 29.519CR0490
  • Updates to GPSI and Application Layer ID mapping information TS 29.519CR0513
  • Including GPSI attribute support TS 29.535CR0037
  • Add GPSI and Application Layer ID mapping information TS 29.591CR0173
  • Delimiting the GPSI values to be fetched to UDM TS 29.503CR1242
  • GPSI and SUPI Support for Related UEs in GMLC API TS 29.515CR0145

+ 2 more changes

Rel-19 4 changes
  • Support for Multiple SUPI to GPSI Conversion in UDM TS 29.503CR1305
  • Enabling GPSI/PEI-based ID Association Query – Stage 2 TS 33.127CR0304
  • AF Specific GPSI Generation TS 29.503CR1492
  • GPSI Missing from IEF Event Parameters at Stage 2 TS 33.127CR0258

Explore further

Broader topics and technologies where GPSI plays a role.

Defining Specifications

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

SpecificationTitleRelease
TS 23.255 vk00 UAS Application Enabler Architecture Rel-20
TS 23.286 vk00 V2X Application Enabler Architecture Rel-20
TS 23.434 vk10 Service Enabler Architecture Layer (SEAL) for Verticals Rel-20
TS 23.501 vk20 5G System Architecture Stage 2 Rel-20
TS 23.540 vj20 5G Service Based SMS Stage 2 Rel-19
TS 23.558 vk20 Edge Computing Application Layer Architecture Rel-20
TR 23.758 vh00 Study on Edge Application Architecture Rel-17
TS 24.257 vj40 UAS Application Enabler (UAE) Layer Rel-19
TS 24.583 vj10 Application layer support for Personal IoT Network Rel-19
TS 26.510 vj20 5G Media Streaming and Real-Time Communication APIs Rel-19
TS 26.512 vj30 5G Media Streaming Protocols and APIs 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.521 vk00 BSF Binding Support Management Service Rel-20
TS 29.522 vk00 NEF Northbound Interface Specification 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.530 vk00 AF AI/ML Services Stage 3 Protocol Rel-20
TS 29.535 vk00 AAnF AKMA Service Interface Rel-20
TS 29.558 vj70 Edge Applications over 3GPP Networks APIs Rel-19
TS 29.561 vk00 5G Network Interworking Procedures Rel-20
TS 29.562 vk00 5G Service-Based Architecture for Nhss Services 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
TR 29.829 vh10 SMS Service-Based Interfaces for 5G Core Rel-17
TS 29.890 vg00 CT3 5G System Technical Report Rel-16
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.127 vj70 Lawful Interception Architecture and Functions Rel-19
TR 33.739 vi10 Study on security enhancement of support for 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.867 vh10 User Consent for 3GPP Services Rel-17
TS 38.473 vj30 F1 Application Protocol (F1AP) for 5G Rel-19