Menu
Latest
12 meetings · Prague, Jeju · 12–16 Oct
Reports
RAN1#126-bis · SA2#177

Glossary term · Core Network

HSS

Home Subscriber Server

Core Network →

HSS is the central master database in 3GPP networks that stores user profiles, performs authentication and authorization, and manages service provisioning and mobility.

Introduced
Rel-5
Where
Core Network › Evolved Packet Core
Specifications
78 specs
Also in
Security
HSS Description Purpose What changed Family Neighbours Detected Changes Specifications

Description

The Home Subscriber Server (HSS) is the primary subscriber data repository and authentication center in 3GPP packet-switched core networks, including the IP Multimedia Subsystem (IMS). Architecturally, it is the evolution and fusion of the Home Location Register (HLR) and Authentication Center (AuC) from GSM networks, extended for IP-based services. It resides within the Home Public Land Mobile Network (HPLMN) and interfaces with numerous core network entities via the Diameter-based Cx, Sh, and S6a/S6d interfaces. Its central role is to manage the user's identity, service profile, and location information, making it indispensable for session establishment, mobility management, and service authorization.

The HSS stores a comprehensive set of permanent data for each subscriber, known as the User Profile. This includes the International Mobile Subscriber Identity (IMSI), Mobile Subscriber Integrated Services Digital Network Number (MSISDN), subscribed Quality of Service (QoS) parameters, and access point names (APNs) for data connectivity. For IMS services, it also stores the user's Private User Identity (IMPI), Public User Identity (IMPU), and associated service profiles that define telephony and multimedia service capabilities. During network attachment and session setup, the HSS works in tandem with other nodes: it provides authentication vectors (RAND, XRES, AUTN, CK, IK) to the Mobility Management Entity (MME) or Serving-Call Session Control Function (S-CSCF) to verify the user's identity and generate ciphering and integrity keys for secure communication.

Beyond authentication, the HSS is central to mobility management. It tracks the user's current serving node (e.g., MME in LTE, AMF in 5G) and, upon request, provides this information to entities like the Gateway Mobile Switching Center (GMSC) for mobile-terminated call routing. It also supports service provisioning by notifying application servers (via the Sh interface) of user profile changes or registration status. In 5G networks, its functions are partly assumed by the Unified Data Management (UDM), but the HSS remains crucial for legacy and interworking scenarios. Its robustness and high availability are paramount, as it is a single point of failure for subscriber management; therefore, it is often deployed in redundant, geographically separated configurations.

Purpose & Motivation

The HSS was created to address the limitations of the GSM-era HLR/AuC in the context of all-IP networks and the introduction of the IP Multimedia Subsystem (IMS). The traditional HLR was designed primarily for circuit-switched voice and SMS, using the MAP protocol. As 3GPP networks evolved to support high-speed packet data and rich multimedia services (VoIP, video calling, presence), a more flexible, IP-centric, and service-aware subscriber database was required. The HSS was standardized in 3GPP Release 5 as part of the IMS architecture to fulfill this need, providing a unified data store that could support both legacy circuit-switched mobility and new packet-switched IMS services.

Its creation solved several key problems. First, it consolidated subscriber data, eliminating the need for separate, synchronized databases for circuit-switched, packet-switched, and IMS domains, which reduced complexity and operational costs. Second, it introduced the Diameter protocol (replacing SS7 MAP for many interfaces), which is more suitable for IP networks, offering improved security, scalability, and support for attribute-value pairs (AVPs) for flexible data exchange. Third, it enabled sophisticated service profiles and triggers for IMS, allowing operators to offer personalized, multimedia services. The HSS became the cornerstone for enabling fixed-mobile convergence, roaming agreements for data and IMS services, and secure access to network resources, forming the foundation for the modern mobile broadband experience.

What changed in its specifications

The latest release-to-release comparison of specifications that define HSS. Each summary describes the whole specification, not only this term.

TR 21.905Rel-17 → Rel-18

Rel-18 brings only minor changes to TS 21.905: 0 clauses changed, with no change attributed to a release feature.

Full comparison in TR 21.905 →
TS 23.127Rel-4 → Rel-5

Rel-5 added IMS provisioning with new network element definitions (HSS, IMS, ISC, MRF). It also added OSA enhancements covering HE-VASP support, policy management, presence, and removing User Profile Management.

Full comparison in TS 23.127 →

Architecture

Where it sits in the network

Evolution Lineage

Technology family

Core network elements and functions · Core Network

  1. Phase 1 AuC, EIR, GMSC, HLR, IWF, MSC, VLR
  2. Phase 2 SMS-GMSC, SMS-IWMSC
  3. R96 GGSN, SGSN
  4. R99 3G-SGSN, GLR, IM-GSN, IM-MSC
  5. Rel-4 CS-MGW, GMSC Server, MSC Server
  6. Rel-5 HSS, SLF
  7. Rel-6 3GPP AAA Server
  8. Rel-7 PCEF, PCRF
  9. Rel-8 ANDSF, BBERF, ePDG, MME, PGW, SGW
  10. Rel-9 HLR-FE, HSS-FE, UDR
  11. Rel-10 L-GW
  12. Rel-11 TDF
  13. Rel-14 PGW-C, PGW-U, SGW-C, SGW-U, TDF-C, TDF-U
  14. Rel-15 AMF, AUSF, PCF, SMF, SMF+PGW-C, UDM, UPF
  • HSS counterpart in another generation: UDM
    “During the TAU or Attach procedure the HSS+UDM cancels any AMF registration associated with the 3GPP access” TS 23.501
  • HSS decomposed into HSS-FE
    “The application that is handled by an AFE determines the type of AFE, e.g. HLR-FE or HSS-FE.” TS 23.002
  • HSS counterpart in another generation: HLR
    “For EPS, the HLR functionality is provided via HSS.” TS 23.002
  • HSS counterpart in another generation: AuC
    “The AuC can be considered a subset of the HSS that holds the following functionality for the CS Domain and PS Domain:” TS 23.002

Security functions and anchors · Security

  1. Phase 1 AuC
  2. R99 HLR/AuC
  3. Rel-5 HSS
  4. Rel-6 3GPP AAA Server, BSF
  5. Rel-8 ASME, MME
  6. Rel-9 HSS-FE
  7. Rel-15 AMF, ARPF, AUSF, SEAF, SEPP, SIDF
  8. Rel-16 AAnF
  • HSS used together with BSF
    “The reference point Zh used between the BSF and the HSS allows the BSF to fetch the required authentication information and all GBA user security settings from the HSS.” TS 33.220
  • HSS counterpart in another generation: HLR/AuC (not stated verbatim in the specifications)

Members and relations were proposed independently by several models and kept only where at least two agree; quotes are verified verbatim against the specifications. Release = first approved version of the defining specification.

Release Timeline

Detected Changes Across Releases

verified against 3GPP sources

Documented changes in 16 releases, each verified against the text of 3GPP specifications or approved change requests and shown with the exact wording. The release timeline above shows the same releases. A release without an entry has no documented change for this term.

Rel-5 introduced

Rel-5 specifies HSS behaviour for IMS: Cx/Sh interactions, pushing subscription data to the S-CSCF, storing the S-CSCF name, barring identities, roaming checks and S-CSCF capability return.

  • “HSS shall use the Push model for downloading the subscription data to the S-CSCF.” TS 23.228 v5.15.0
  • “The HSS shall indicate whether the user is allowed to register in that P-CSCF network” TS 23.228 v5.15.0
  • Clarification of the HSS behaviour in REGISTRATION and DE_REGISTRATION procedures at IMPU checking time. TS 29.228CR024
Rel-6 1 CR

HSS behaviour in IMS registration changed: it now handles registration state per Public User Identity within an IMS subscription, returns server capabilities satisfying all service profiles, and supports wildcarded PSIs and HSS-initiated deregistration.

  • “The returned capabilities shall satisfy all the requirements of all the service profiles associated with the IMS Subscription.” TS 29.228 v6.17.0
  • “the S‑CSCF may do the wildcard matching using the wildcarded PSI received in this first Server-Assignment-Answer” TS 29.228 v6.17.0
  • HSS initiated deregistration with user profile removal for permanent termination TS 29.228CR140
Rel-7 1 CR

HSS behaviour on Cx changed: UAR handling now checks for IMS Emergency Registration and skips roaming checks, and the HSS keeps or clears the S-CSCF name depending on emergency registration status.

  • “If it is an IMS Emergency Registration, authorization shall be granted and the HSS shall not perform any check regarding roaming.” TS 29.228 v7.18.0
  • “If included, the HSS shall keep the S-CSCF name associated with the Public User Identity and set the registration state of the Public User Identity to Unregistered.” TS 29.228 v7.18.0
  • Correction of the HSS behaviour in UAR/UAA command pair TS 29.228CR0342
Rel-8 1 CR

HSS behaviour changed in Rel-8: new S6a/S6d Update Location handling in TS 29.272, plus IMS Cx changes such as returning the stored S-CSCF name for de-registration and Diameter Proxy Agent HSS resolution.

  • “When receiving an Update Location request the HSS shall check whether subscription data exists for the IMSI.” TS 29.272 v8.14.0
  • “the HSS shall return the stored S-CSCF name and Experimental-Result-Code set to DIAMETER_SUCCESS.” TS 29.228 v8.19.0
  • HSS behaviour after PPA with unknown user TS 29.228CR0457
Rel-9 specification text

HSS behaviour in S6a/S6d procedures changed in Rel-9: it returns Unknown EPS Subscription with Error Diagnostic, handles Active-APN lists, clears URRP-SGSN, and handles combined MME/SGSN nodes.

  • “the HSS shall return a Result Code of DIAMETER_ERROR_UNKNOWN_EPS_SUBSCRIPTION.” TS 29.272 v9.14.0
  • “the HSS shall delete all the stored dynamic PDN GW information, if there are any, and then replace them” TS 29.272 v9.14.0
  • “the HSS shall clear the URRP-SGSN parameter and send an indication to the corresponding Service Related Entities.” TS 29.272 v9.14.0
Rel-10 specification text

HSS behaviour in TS 29.272 changed: partial purge handling with PUA flags, ODB roaming error handling, storage of UE SRVCC capability, and conditions for setting IDR flags.

  • “if the HSS supports the Partial Purge feature (see clause 7.3.10), and the combined MME/SGSN indicated that the UE was purged in only one” TS 29.272 v10.10.0
  • “The HSS shall check whether roaming is not allowed in the VPLMN due to ODB.” TS 29.272 v10.10.0
  • “The HSS shall store the new terminal information and/or the new UE SRVCC capability, if they are present in the request.” TS 29.272 v10.10.0
Rel-11 1 CR

HSS behaviour changed in Rel-11: it registers MMEs for SMS in MME, handles additional MSISDN, CSG lists per equivalent PLMN, Local Time Zone requests, and IMS restoration handling in LIR.

  • “the HSS shall register the MME for MT SMS, store the "MME number for SMS" as the corresponding MSC number to be used for MT SMS” TS 29.272 v11.14.0
  • “the HSS shall send the provisioned additional MSISDN together with the MSISDN.” TS 29.272 v11.14.0
  • Behaviour of HSS not supported IMS Restoration Procedures to LIR TS 29.228CR0553
Rel-12 1 CR

HSS behaviour was extended: it now handles P-CSCF restoration indications and clears stale MME/SGSN location data on Update Location, and it registers the MME for SMS with the MME number for MT SMS.

  • “the HSS supporting the P-CSCF-Restoration-mechanism feature shall check whether at least one of the serving node(s) for corresponding user support this feature.” TS 29.228 v12.10.0
  • “The HSS shall reset the "UE purged in MME" flag and delete any stored last known MME location information of the (no longer) purged UE.” TS 29.272 v12.11.0
  • HSS behaviour when P-CSCF Restoration indication is received TS 29.228CR0628
Rel-13 1 CR

In Rel-13 the HSS gained new behaviour: handling Monitoring event configuration, Dedicated Core Network UE usage type, Non-IP PDN APNs, adjacent PLMN access restrictions, and third-party-managed IMS users.

  • “the HSS shall include Monitoring-Event-Configuration AVP(s) in the Subscription-Data AVP sent within the IDR.” TS 29.272 v13.12.0
  • “the HSS shall return a Result Code of DIAMETER_ERROR_UNKNOWN_EPS_SUBSCRIPTION.” TS 29.272 v13.12.0
  • HSS supports IMS subscriptions corresponding to users managed by third parties TS 29.228CR0652
Rel-14 specification text

The HSS gained new behaviour in Rel-14: it includes V2X-Subscription-Data and External-Identifier AVPs in ULA/IDR, and handles monitoring-event cancellation on NOR; new Load AVP reporting was also added on Cx.

  • “the HSS shall include V2X-Subscription-Data AVP into Subscription-Data AVP within the ULA command.” TS 29.272 v14.9.0
  • “the HSS shall trigger a Monitoring event cancelation procedure for the monitoring events that were not successfully configured at the MME/SGSN” TS 29.272 v14.9.0
  • “The HSS may report its current load by including a Load AVP of type HOST in answer commands” TS 29.228 v14.6.0
Rel-15 specification text

HSS behaviour was extended in Rel-15: it checks Core Network Restrictions before allowing EPC access, sends them in IDR, withdraws subscription accordingly, and handles NR secondary RAT and External-Identifier data.

  • “The HSS shall check whether access to EPC is allowed, based on the active Core Network Restrictions of the subscriber.” TS 29.272 v15.10.0
  • “the HSS shall include the Core-Network-Restrictions AVP in the Subscription-Data AVP sent within an IDR.” TS 29.272 v15.10.0
  • “the HSS shall not send (in ULA) or update (in IDR) subscription data related to NR as Secondary RAT.” TS 29.272 v15.10.0
Rel-16 1 CR

Rel-16 introduces service-based (SBI) HSS capabilities for IMS, with HSS services over Nhss, HSS discovery and selection via NRF, and HSS NF profiles.

  • “All scenarios shown in the following clauses assume that the SBI capable HSS is stateful and stores information in local memory.” TS 29.562 v16.10.0
  • “When an SBI capable IMS entity receives an NRF response that HSS supports SBI and stores the information received from the HSS” TS 23.228 v16.7.0
  • SBA HSS Services for IMS TS 23.228CR1200
Rel-17 1 CR

In Rel-17 the HSS gained new behaviour: HSS Group ID handling for SBI discovery and IMS signalling, GBA services over Nhss SBI, and HSS-initiated PSI direct routing and P-CSCF restoration support.

  • “every IMS node receiving an HSS Group ID in SIP signalling (e.g. S-CSCF and IMS AS) should store it as part of the UE information” TS 23.228 v17.3.0
  • “the HSS responds with "200 OK" with the GBA subscriber data (containing, e.g. the GBA User Security Settings, GUSS)” TS 29.562 v17.10.0
  • HSS GBA SBI Services Definition TS 29.562CR0090
Rel-18 specification text

HSS gained new Rel-18 functionality: it now serves the DCSF over the Nhss/N72/Sc interface, stores IMS Data Channel subscription data, and handles monitoring event suspension errors and EPS-5GS PDN context sync with UDM.

  • “In order to support data channel service, the HSS is additionally enhanced with the following functionalities:” TS 23.228 v18.12.0
  • “the HSS offers services to the S-CSCF, I-CSCF, IMS-AS and DCSF (on the IP Multimedia Subsystem) and GBA BSF via the Nhss service based interface” TS 29.562 v18.8.0
  • “triggers a Monitoring event suspension procedure in HSS;” TS 29.272 v18.7.0
Rel-19 1 CR

HSS gained new behaviour in Rel-19: satellite store-and-forward ULR timestamp handling, disaster roaming handling, IMS AS registration and event subscription services (Nhss_ImsEE), and MPS for Messaging priority handling.

  • “If the HSS supports "Satellite S&F" feature, when it receives ULR from the MME:” TS 29.272 v19.6.0
  • “the HSS may allow to provide disaster roaming service to the UE and include the subscription data for disaster roaming service in the ULA to the MME.” TS 29.272 v19.6.0
  • Add Nhss_imsEE service in HSS TS 29.562CR0163
Rel-20 1 CR

HSS gains new behaviour: forwarding exposure event subscription requests to registered IMS AS instances, and handling Cx requests with priority (DRMP set) for MPS for Messaging.

  • “The HSS shall forward the subscribe, unsubscribe and modification of subscription requests to the IMS AS (if and when registered) by means of the IMS AS's offered service.” TS 29.562 v20.1.0
  • “the HSS shall handle the request with priority and shall set the DRMP in the response to a value appropriate for MPS” TS 29.228 v20.0.0
  • HSS handling of Cx procedures with priority for MPS for Messaging TS 29.228CR0703

Defining Specifications

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

SpecificationTitleRelease
TR 21.905 vj20 3GPP Terminology and Definitions Rel-19 read
TR 22.980 vj00 Network Composition Feasibility Study Rel-19 read
TS 23.127 v610 Virtual Home Environment Stage 2 Specification Rel-6 read
TS 23.141 vj00 Presence Service Stage 2 Architecture Rel-19 read
TS 23.179 vd50 MCPTT Functional Architecture Rel-13 read
TS 23.198 v900 Open Service Access (OSA) Stage 2 Rel-9 read
TS 23.218 vj00 IMS Call Model Specification Rel-19 read
TS 23.228 vk10 IP Multimedia Core Network Subsystem Rel-20 read
TS 23.234 vd10 3GPP-WLAN Interworking Index Rel-13 read
TS 23.251 vj00 Network Sharing Stage 2 Specification Rel-19 read
TS 23.271 vj00 LCS Stage 2 Specification Rel-19 read
TS 23.278 vj00 CAMEL for IMS Stage 2 Specification Rel-19 read
TS 23.280 vk51 Mission Critical Services Architecture Rel-20 read
TS 23.379 vk40 Mission Critical Push-to-Talk Architecture Rel-20 read
TS 23.701 vc00 WebRTC Access to IMS Study Rel-12 read
TR 23.732 vg00 User Data Interworking, Coexistence, Migration Study Rel-16 read
TS 23.804 v710 SMS/MMS over IP Access Networks Rel-7 read
TR 23.973 vj00 Separate HSS/UDM Deployment Scenarios & Solutions Rel-19 read
TS 24.109 vj00 HTTP Digest AKA & GAA Stage 3 Rel-19 read
TS 24.141 vj00 Presence Service Protocol Details Rel-19 read
TS 24.147 vj00 IMS Conferencing Protocol Details Rel-19 read
TS 24.206 v750 Voice Call Continuity Between CS and IMS Rel-7 read
TS 24.228 v590 IP Multimedia Call Control Signaling Flows Rel-5 read
TS 24.229 vk10 IMS SIP/SDP Call Control Protocol Rel-20 read
TS 24.234 vc20 3GPP-WLAN Interworking Procedures Rel-12 read
TS 24.259 vj00 Personal Network Management (PNM) Protocol Details Rel-19 read
TS 24.292 vj00 IMS Centralized Services (ICS) Protocol Rel-19 read
TS 24.315 vj00 Operator Determined Barring (ODB) for IMS Rel-19 read
TS 24.523 vj00 NGCN-NGN Interconnection Scenarios Rel-19 read
TS 24.525 vj00 Business Trunking Architecture & Requirements Rel-19 read
TS 24.819 v700 IMS Services via Fixed Broadband Access Rel-7 read
TS 24.841 v600 Presence Service IP Multimedia Subsystem Rel-6 read
TR 24.930 vj00 IMS Session Setup Signalling Flows Rel-19 read
TS 26.119 vj10 Device Media Capabilities for AR Services Rel-19 read
TR 26.944 vj00 QoE, ESQoS and SQoS metrics for 3G multimedia services Rel-19 read
TS 29.109 vj00 GAA Bootstrapping Interfaces (Zh, Dz, Zn, Zpn) Rel-19 read
TS 29.175 vk10 Nimsas Service Based Interface for IMS AS Rel-20 read
TS 29.228 vk00 IMS Cx and Dx Interface Procedures Rel-20 read
TS 29.229 vj10 Diameter Protocol for Cx/Dx Interfaces Rel-19 read
TS 29.234 vb20 WLAN-3GPP Interworking Protocols Rel-11 read
TS 29.272 vj60 MME and SGSN Diameter interfaces to HSS/CSS/EIR Rel-19 read
TS 29.309 vk00 Nbsp Service Based Interface for GBA BSF Rel-20 read
TS 29.328 vk00 IMS Sh, Dh and Ph Interface Procedures Rel-20 read
TS 29.329 vj10 Diameter Protocol for Sh Interface Rel-19 read
TS 29.562 vk10 HSS Nhss Services for IMS and GBA Rel-20 read
TS 29.563 vk00 Nhss Services for 5G SBA Stage 3 Rel-20 read
TS 29.866 vj00 IMS Disaster Prevention & Restoration Enhancement Rel-19 read
TS 32.101 vj00 PLMN Management Principles and Requirements Rel-19 read
TS 32.102 vj00 Telecom Management Physical Architecture Framework Rel-19 read
TS 32.140 vj00 Subscription Management (SuM) requirements Rel-19 read
TS 32.141 vj00 Subscription Management (SuM) Architecture Rel-19 read
TS 32.271 vj20 3GPP LCS Charging Management Spec Rel-19 read
TS 32.272 vj00 Charging for Push-to-Talk over Cellular (PoC) Rel-19 read
TS 32.277 vj20 Charging Management for Proximity Services (ProSe) Rel-19 read
TS 32.278 vj00 Monitoring Events Offline Charging Specification Rel-19 read
TS 32.280 vj00 Advice of Charge (AoC) Framework Rel-19 read
TS 32.409 vj00 IMS Performance Management Measurements Rel-19 read
TS 32.808 v800 Common Profile Storage Framework for User Data Rel-8 read
TR 32.901 vj00 UDC Application Data Models Study Rel-19 read
TS 33.107 vj00 Lawful Interception Architecture & Functions Rel-19 read
TS 33.108 vj00 LI Handover Interface Specification Rel-19 read
TS 33.203 vk00 IMS Security Features and Mechanisms Rel-20 read
TS 33.220 vj10 Generic Authentication Architecture (GAA) Security Rel-19 read
TS 33.221 vj00 Subscriber Certificate Distribution via GBA Rel-19 read
TS 33.222 vj00 Secure HTTP Access in GAA Rel-19 read
TS 33.223 vj00 GBA Push Function Specification Rel-19 read
TS 33.259 vj00 Key Establishment between UICC Hosting & Remote Device Rel-19 read
TS 33.401 vj20 EPS Security Architecture Rel-19 read
TS 33.545 vk10 NR Femto Security Architecture Rel-20 read
TS 33.804 vc00 Non-UICC SSO using SIP Digest credentials Rel-12 read
TS 33.820 v830 H(e)NB Security Threats and Countermeasures Rel-8 read
TS 33.835 vg10 Study on authentication and key management for apps Rel-16 read
TS 33.859 vb10 UTRAN Key Hierarchy Study Rel-11 read
TS 33.863 ve20 Security for Battery-Efficient IoT Device to Enterprise Rel-14 read
TR 33.919 vj00 GAA Overview TR Rel-19 read
TR 33.924 vj00 GBA-OpenID Interworking Specification Rel-19 read
TS 33.978 v800 Early IMS Security Interim Solution Rel-8 read
TR 33.980 vj00 GAA & Liberty Alliance Interworking Guidelines Rel-19 read