Description
Provide Subscriber Information (PSI) is a standardized service within the 3GPP core network architecture, defined as part of the Mobile Application Part (MAP) protocol and later the Diameter-based Sh and S6a/S6d interfaces. It is a network-initiated procedure where a requesting node, such as a Gateway Mobile Location Centre (GMLC), a Service Capability Exposure Function (SCEF), or a Lawful Interception node, queries the subscriber's home database – the Home Location Register (HLR) in 2G/3G or the Home Subscriber Server (HSS) in 4G/5G – to obtain specific information about a subscriber.
The procedure involves a well-defined request/response message exchange. The requesting entity sends a PSI message (e.g., MAP_PSI or Diameter PSI-Request) containing the subscriber's identifier (like MSISDN or IMSI) and an indication of the information required. The HSS/HLR processes the request, which typically involves checking the requester's authorization against subscriber privacy settings and regulatory requirements (e.g., for location services). Upon successful authorization, the HSS/HLR responds with a PSI-Answer message containing the requested data. This data can include a wide array of information: the subscriber's current serving network node (MSC, SGSN, MME, AMF), the subscriber's state (e.g., attached, detached), location information (if available and permitted), subscribed services, and IMSI-MSISDN mapping.
Key components in the architecture include the Requesting Node (the client of the service), the HSS/HLR (the server holding the data), and the relevant signaling interfaces. For 4G/5G, the primary interface is the S6a (between MME and HSS) and Sh (between Application Server/SCEF and HSS), using the Diameter protocol. The HSS acts as the central repository and policy enforcement point, ensuring that subscriber data is provided only to authorized network functions based on the subscriber's consent and network policies.
PSI's role is critical for enabling numerous value-added and regulatory services. It is the backbone procedure for network-based location services, allowing a GMLC to find out which Mobility Management Entity (MME) or Access and Mobility Management Function (AMF) is serving a target UE before issuing a location request. It is also used for restoring subscriber data in case of MME failure, supporting SMS delivery routing, facilitating lawful interception provisioning, and enabling service capability exposure for third-party applications. Its evolution across releases has seen it adapt from circuit-switched MAP to packet-switched Diameter, and its integration with new network functions like the SCEF and Network Exposure Function (NEF) in 5G, maintaining its position as a fundamental subscriber data access service.
Purpose & Motivation
The PSI service was created to address the fundamental need for authorized network entities to access centralized subscriber information in a standardized, secure, and controlled manner. In early cellular networks, different network nodes (like switches and service platforms) required subscriber data to perform their functions, but ad-hoc methods of sharing this data were inefficient and insecure. PSI provided a unified, protocol-based mechanism for querying the master subscriber database (HLR), solving problems related to service triggering, routing (e.g., for SMS or voice calls), and the nascent field of location-based services.
The historical motivation stems from the separation of the subscriber database (HLR) from the switching functions in GSM architecture. This separation created the need for a signaling service to connect them. PSI, as part of the MAP protocol, was one of the key services enabling this distributed architecture. It solved the limitation of having subscriber data siloed or replicated inconsistently across network elements. By centralizing data in the HLR and providing controlled access via PSI, network operators could ensure data consistency, simplify service deployment, and implement subscriber privacy controls.
As networks evolved through 3G, 4G, and 5G, the purpose of PSI expanded. It became essential for enabling regulatory services like lawful interception, where authorities require network attachment information. The drive towards service exposure and network APIs for third-party developers further leveraged PSI (via the SCEF/NEF) to provide subscriber status information to authorized applications, fueling the creation of new services. Thus, PSI has endured as a critical enabler, evolving from a basic network operations tool to a key component in service delivery, security, and innovation across the entire 3GPP system evolution.
Key Features
- Standardized procedure for querying HSS/HLR subscriber data
- Supports multiple information types: location, status, serving node, subscriber identity mapping
- Includes built-in authorization and privacy check mechanisms
- Works across multiple protocol generations (MAP for 2G/3G, Diameter for 4G/5G)
- Fundamental for location-based services, SMS routing, and lawful interception
- Enables subscriber data recovery and service continuity during network failures
Evolution Across Releases
Initial standardization of the Provide Subscriber Information (PSI) service within the MAP protocol for GSM/UMTS core networks. Defined the basic request/response mechanism for an external node (like a GMLC) to query the HLR for a subscriber's current serving MSC and subscriber state, primarily to enable location services.
Defining Specifications
| Specification | Title |
|---|---|
| TS 23.079 | 3GPP TS 23.079 |
| TS 23.179 | 3GPP TS 23.179 |
| TS 23.206 | 3GPP TS 23.206 |
| TS 23.228 | 3GPP TS 23.228 |
| TS 23.280 | 3GPP TS 23.280 |
| TS 23.379 | 3GPP TS 23.379 |
| TS 23.806 | 3GPP TS 23.806 |
| TS 23.979 | 3GPP TS 23.979 |
| TS 24.141 | 3GPP TS 24.141 |
| TS 24.147 | 3GPP TS 24.147 |
| TS 24.173 | 3GPP TS 24.173 |
| TS 24.186 | 3GPP TS 24.186 |
| TS 24.206 | 3GPP TS 24.206 |
| TS 24.229 | 3GPP TS 24.229 |
| TS 24.259 | 3GPP TS 24.259 |
| TS 24.406 | 3GPP TS 24.406 |
| TS 24.606 | 3GPP TS 24.606 |
| TS 24.819 | 3GPP TS 24.819 |
| TS 24.841 | 3GPP TS 24.841 |
| TS 24.930 | 3GPP TS 24.930 |
| TS 25.331 | 3GPP TS 25.331 |
| TS 25.413 | 3GPP TS 25.413 |
| TS 26.237 | 3GPP TS 26.237 |
| TS 26.506 | 3GPP TS 26.506 |
| TS 26.510 | 3GPP TS 26.510 |
| TS 26.522 | 3GPP TS 26.522 |
| TS 26.822 | 3GPP TS 26.822 |
| TS 26.827 | 3GPP TS 26.827 |
| TS 26.854 | 3GPP TS 26.854 |
| TS 26.917 | 3GPP TS 26.917 |
| TS 29.118 | 3GPP TS 29.118 |
| TS 29.165 | 3GPP TS 29.165 |
| TS 29.949 | 3GPP TS 29.949 |
| TS 31.829 | 3GPP TR 31.829 |
| TS 32.250 | 3GPP TR 32.250 |
| TS 38.300 | 3GPP TR 38.300 |
| TS 38.306 | 3GPP TR 38.306 |
| TS 38.321 | 3GPP TR 38.321 |
| TS 38.323 | 3GPP TR 38.323 |
| TS 38.331 | 3GPP TR 38.331 |
| TS 38.415 | 3GPP TR 38.415 |
| TS 38.473 | 3GPP TR 38.473 |
| TS 38.835 | 3GPP TR 38.835 |
| TS 43.064 | 3GPP TR 43.064 |