Public Service Identity

Description

A Public Service Identity (PSI) is a logical identifier defined within the 3GPP IP Multimedia Subsystem (IMS) architecture. It represents a service or a service point, rather than an individual user subscription. A PSI takes the form of a Uniform Resource Identifier (URI), such as a SIP URI (e.g., sip:[email protected]) or a TEL URI, and is used to route service-related signaling (SIP messages) to the appropriate application server (AS) that hosts the service logic.

PSIs are stored and managed within the IMS core, specifically in the Home Subscriber Server (HSS) or a dedicated Subscription Locator Function (SLF). When a user initiates a session towards a PSI (e.g., joins a group chat), the Interrogating-Call Session Control Function (I-CSCF) or Serving-CSCF (S-CSCF) performs an HSS query to resolve the PSI to the address of the Application Server (AS) responsible for that service. This routing mechanism is distinct from routing to a user's Private User Identity (IMPI) or Public User Identity (IMPU).

PSIs are fundamental for services like Push-to-talk over Cellular (PoC), multimedia conference bridges, messaging group servers, broadcast/multicast service centers (e.g., eMBMS), and Machine-Type Communication (MTC) services. They allow a single identifier to represent a service endpoint accessible by many users. The AS hosting the PSI manages service state, participant lists, and service logic. PSIs can also be used in service discovery mechanisms, where a UE can resolve a generic service name to a specific PSI URI.

Purpose & Motivation

The PSI concept was introduced to facilitate service-oriented communication within the IMS framework. Prior to IMS, services were often tightly coupled with specific user directories or proprietary addressing schemes, making service discovery, scalability, and interoperability difficult. PSIs provide a standardized, network-routable address for services, decoupling the service logic from individual user identities.

This enables the creation of scalable group-based and broadcast services. For example, a corporate conference bridge can be assigned a single PSI, and all employees can invoke it without needing to know the underlying server's IP address or technical details. It solves the problem of how to efficiently route signaling to service platforms in a multi-vendor IMS environment. PSIs are also crucial for IoT/MTC applications, where a central service platform (e.g., for sensor data aggregation) needs a stable, public identity. Their standardization allows for consistent service invocation across different operator networks and device types.