Home Subscriber Server

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.