GPSI

Generic Public Subscription Identifier

Identifier →
Introduced in Rel-15 Also in: Services

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.

Category
Identifier
Introduced
Rel-15
Where
Core Network › 5G Core
Also touches
1 segments
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 (570 CRs across 5 releases). Complements the general historical overview above with the evidence-based evolution of this function.

Rel-15 86 changes

In Release 15, the GPSI function was newly introduced to replace the PUI (Private User Identity) as a standardized external identifier for a subscription. This change was part of broader enhancements for subscription data management, including the retrieval of SMS management subscription data and subscription to resource allocation outcomes. The release also defined procedures for subscription and notification of events like out-of-credit conditions, integrating GPSI within these exposure and service frameworks.

  • Nudm_SDM retrieval of SMS Management Subscription data TS 29.503CR0037
  • Subscription and notification of resources allocation outcome, data model TS 29.514CR0007
  • Subscription to resources allocation outcome, service procedures TS 29.514CR0008
  • Subscription and notification of out of credit events, data model TS 29.514CR0010
  • Subscription to out of credit notification, service procedures TS 29.514CR0011
  • Subscription for Structured Data for Exposure TS 29.519CR0022

+ 80 more changes

Rel-16 113 changes

In Release 16, the GPSI function was expanded to serve as a key identifier for Unmanned Aerial Vehicles (UAVs) within the 5G system for UAS traffic management. Specifically, the GPSI is now formally defined as a valid identifier for a UAV (UAV ID) and can be used within UAS-related procedures such as registration, C2 communication mode management, and C2 operation mode switching. This integration enables the network to uniquely identify and manage UAV subscriptions and their associated command and control links.

  • TS 23.501: Introducing Non-public network TS 23.501CR0734
  • Introducing support for Non-Public Networks TS 23.501CR0757
  • Introducing Non-public network TS 23.501CR0734
  • SUPI and SUCI for wireline access TS 23.501CR0744
  • Introduction of the MSISDN-less MO SMS Service TS 23.501CR0826
  • FQDN format of N3IWF in a standalone non-public network TS 23.501CR0841

+ 107 more changes

Rel-17 138 changes

In Release 17, the GPSI function was extended to support new Uncrewed Aerial System (UAS) use cases, specifically for uniquely identifying a UAV or UAV-C. The GPSI is explicitly defined as a valid form for the UAV Identifier (UAV ID), enabling subscription and service procedures for aerial UEs. Furthermore, the concept of dual subscription functionality was introduced, allowing a UAS to operate with links belonging to the same or different networks.

  • SNPN with separate entity hosting subscription TS 23.501CR2625
  • 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
  • Authentication and Subscription information checking for Disaster Roaming service TS 23.501CR3251
  • Add 5G DDNMF and ProSe Subscription Data TS 29.503CR0613
  • Identifier Translation TS 29.503CR0654

+ 132 more changes

Rel-18 128 changes

In Release 18, the GPSI function was enhanced to support new Unmanned Aerial System (UAS) subscription and service capabilities. Specifically, new subscription data and procedures were introduced for managing Command and Control (C2) communication modes, including C2 operation mode management and switching between network-assisted and UTM-Navigated links. Furthermore, the release defined subscription mechanisms for dual connectivity scenarios, allowing a UAS to utilize links from the same or different networks based on subscription functionality.

  • VAL service area identifier usage TS 23.434CR0136
  • Adding time synchronization service based on subscription TS 23.501CR3762
  • PIN identifiers TS 23.501CR4287
  • EDGE-5 – Subscription TS 23.558CR0152
  • Updating UE Identifier API procedure to enable EEC invoke UE ID request for NATed IP address TS 23.558CR0156
  • Subscription for service provisioning information retrieval by ECS TS 23.558CR0316

+ 122 more changes

Rel-19 105 changes

In Release 19, the GPSI function was enhanced to support the conversion of multiple SUPIs to a single GPSI within the UDM, and to allow for AF-specific identifier selection during this translation. Furthermore, subscription data was expanded to include new parameters such as an Energy Saving Indicator for UEs and Required/Preferred UPF functionalities. The release also introduced support for MSISDN verification operations within the Nnef_UEId service.

  • Add Geofencing subscription/unsubscribe procedure TS 23.434CR0306
  • Subscription-based routing to a target core network TS 23.501CR5380
  • Enhancement of getting public UE IP address and port number TS 23.501CR5445
  • Supporting direct subscription of UPF event exposure using UE's IP address TS 23.501CR5540
  • KI#2: UE subscription and policy control for energy efficiency and energy saving TS 23.501CR5739
  • Updates to UPF data exposure for KI#2 direct subscription TS 23.501CR5452

+ 99 more changes

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 vj50 UAS Application Layer Support Rel-19
TS 23.286 vj00 V2X Application Enabler Architecture Rel-19
TS 23.434 vk00 Service Enabler Architecture for Verticals Rel-20
TS 23.501 vk00 5G System Architecture Stage 2 Rel-20
TS 23.540 vj20 5G Service Based SMS Stage 2 Rel-19
TS 23.558 vk00 Architecture for Edge Applications 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 vj00 Application Layer Support for Personal IoT Network Rel-19
TS 26.510 vj10 Media Delivery APIs for 5GMS and RTC Systems Rel-19
TS 26.512 vj10 5G Media Streaming Protocols & APIs Rel-19
TS 28.204 vi11 Charging management Rel-18
TR 28.840 vi10 Technical Report Rel-18
TS 29.503 vj50 UDM Service Based Interface Stage 3 Rel-19
TS 29.504 vj50 Nudr Service Based Interface Stage 3 Protocol Rel-19
TS 29.505 vj50 UDR Service for Subscription Data Usage Rel-19
TS 29.507 vj40 5G Access & Mobility Policy Control Service Rel-19
TS 29.508 vj40 5G Session Management Event Exposure Service Rel-19
TS 29.514 vj40 5G System; Policy Authorization Service; Stage 3 Rel-19
TS 29.515 vj50 Ngmlc Service Based Interface Protocol Rel-19
TS 29.517 vj40 5G AF Event Exposure Service Stage 3 Rel-19
TS 29.518 vj50 AMF Service Based Interface Protocol Rel-19
TS 29.519 vj40 UDR Usage for Policy & Exposure Data Rel-19
TS 29.521 vj40 5G Binding Support Management Service Stage 3 Rel-19
TS 29.522 vj40 5G NEF Northbound APIs Stage 3 Rel-19
TS 29.523 vj20 5G Policy Control Event Exposure Service Rel-19
TS 29.525 vj40 5G UE Policy Control Service Stage 3 Rel-19
TS 29.530 vj00 AF AI/ML Services Stage 3 Protocol Rel-19
TS 29.535 vj40 5G AKMA Anchor Services Stage 3 Protocol Rel-19
TS 29.558 vj40 Enabling Edge Applications Rel-19
TS 29.561 vj30 5G Interworking with External Data Networks Rel-19
TS 29.562 vj40 HSS Services for IMS & GBA Interworking Rel-19
TS 29.571 vj50 Common Data Types for 5G Service Based Interfaces Rel-19
TS 29.591 vj40 5G NEF Southbound Services Stage 3 Rel-19
TS 29.594 vj20 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 vk10 Telecom Management; Charging for 5G Data Connectivity Rel-20
TS 32.256 vj40 5G Connection & Mobility Charging Spec Rel-19
TS 32.291 vj40 Charging Management: Service-Based Interface Protocol Rel-19
TS 33.127 vj50 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 vj10 5G F1 Application Protocol (F1AP) Rel-19