PUI

Public User Identity

Identifier →
Introduced in Rel-8

PUI is a globally routable identifier, such as a SIP URI or TEL URI, used in the IMS as an external address for others to initiate multimedia communication sessions toward a subscriber.

Category
Identifier
Introduced
Rel-8
Where
Services
Specifications
2 specs
PUI Description Purpose Related Classification Specifications

Description

The Public User Identity (PUI) is a fundamental concept within the 3GPP IP Multimedia Subsystem (IMS) architecture, serving as the public-facing address of a user. It is the identifier used by other users or applications to initiate communication sessions, such as Voice over LTE (VoLTE) calls, video calls, or instant messaging sessions. A PUI is distinct from private identifiers and takes the form of either a SIP Uniform Resource Identifier (SIP URI, e.g., sip:[email protected]) or a TEL URI (e.g., tel:+1234567890), which maps to a traditional telephone number.

Architecturally, PUIs are stored in the IMS subscriber's profile within the Home Subscriber Server (HSS). A single IMS subscriber (represented by a private user identity) can be associated with multiple PUIs, allowing for one person to have several contact addresses (e.g., a business number and a personal number). During IMS registration, the UE registers its associated PUIs with the network via the Serving-Call Session Control Function (S-CSCF). The S-CSCF downloads the subscriber's service profile, including the list of PUIs, from the HSS to authorize and provide services for those identities.

In operation, when a session is initiated towards a user, the originating IMS network routes the request based on the target PUI. The interrogating-CSCF (I-CSCF) queries the HSS to determine which S-CSCF is serving that PUI, enabling the request to be forwarded correctly. PUIs are essential for service invocation, as IMS application servers (AS) trigger services based on the called or calling PUI. They are also used for identity presentation (Caller ID) and are a key element in IMS charging mechanisms. The management of PUIs, including their registration, deregistration, and barring, is a core part of IMS session control.

Purpose & Motivation

The PUI was created to solve the problem of addressing users in an all-IP, multimedia-centric network like IMS, which decouples services from the underlying access technology. Prior to IMS, telephony used primarily the Mobile Subscriber ISDN Number (MSISDN) as the sole address. This was insufficient for the rich multimedia and multi-identity scenarios envisioned for IMS, where a user might have email-like addresses (SIP URIs) alongside telephone numbers.

Its creation was motivated by the need for a flexible, Internet-standard compliant addressing scheme that could work globally across operator boundaries. The SIP URI format, aligned with IETF standards, allows for seamless interworking with non-3GPP IP-based communication services. The PUI provides the necessary abstraction layer, separating the user's public contact identity from their network-level private identity and their physical device. This solves the problem of service portability and enables advanced features like simultaneous ringing of multiple devices under one public identity, identity sharing (e.g., a department number), and the convergence of telephony and web-based communication paradigms.

Classification

Part ofIMS
Specific typesSIP-URI
Related approachesHSSCSCF

Evolution Across Releases

Rel-8 Initial

Introduced the Public User Identity as a core component of the EPS/IMS architecture for LTE. Defined its formats (SIP URI and TEL URI), its storage in the HSS, and its role in IMS registration and session establishment. This established the foundation for VoLTE and other IMS-based services.

Enhanced IMS features, leading to refinements in PUI handling for services like IMS Centralized Services (ICS) and emergency sessions. Improved procedures for PUI registration and deregistration.

Further optimizations for IMS, potentially involving SRVCC (Single Radio Voice Call Continuity) where the association between a PUI (TEL URI) and the radio bearer is critical for handover from LTE to legacy circuitswitched networks.

Continued IMS evolution with features like RCS (Rich Communication Services), which rely heavily on PUIs for messaging and chat services. Enhanced support for multiple PUIs and identity management.

Introduced VoWiFi (Voice over Wi-Fi) and further IMS enhancements, requiring robust PUI handling across non-3GPP access. Ensured PUI-based service continuity between cellular and Wi-Fi access.

Support for ViLTE (Video over LTE) and other advanced communication services, reinforcing the PUI's role as the anchor for multimedia session addressing.

IMS evolution for LTE-Advanced Pro, including enhancements for mission-critical communication, which may involve specific PUI handling for group communication and priority services.

Integration of IMS and PUI concepts into the 5G System (5GS) for Voice over NR (VoNR). The PUI remains the core user address for IMS-based telephony services in 5G, with support over the new 5GC architecture.

5G phase 2 enhancements, including IMS support for Industrial IoT and ultra-reliable low-latency communication (URLLC) scenarios, requiring deterministic handling of sessions identified by PUIs.

Further 5G evolution, potentially involving integration with new edge computing architectures where IMS application servers might be deployed closer to the user, impacting PUI resolution and routing.

5G-Advanced work items, focusing on AI/ML for network optimization, may include intelligent routing or spam prevention based on PUI analytics. Continued support for converged communication services.

Ongoing evolution of IMS and communication services in the 5G-Advanced timeframe, ensuring PUI mechanisms support future service innovations and network architectures.

Future-looking enhancements for 6G preparation or advanced 5G features, likely maintaining the PUI as a stable, foundational identifier for user-facing IMS services while adapting to new architectural paradigms.

Explore further

Broader topics and technologies where PUI plays a role.

Defining Specifications

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

SpecificationTitleRelease
TS 22.173 vk00 IMS Multimedia Telephony Service Definition Rel-20
TS 22.894 vb00 IMS Network-Independent Public User Identities Study Rel-11