Description
The Home Location Register (HLR) is a fundamental, centralized database within the Circuit-Switched (CS) domain of GSM and UMTS networks. It is the primary repository for all permanent subscriber information and service profiles. Each subscriber in a network is associated with a unique record in the HLR, keyed by their International Mobile Subscriber Identity (IMSI). The data stored includes the IMSI, Mobile Station International Subscriber Directory Number (MSISDN), subscribed services (e.g., call forwarding, barring, supplementary services), authentication information (like the authentication triplet: RAND, SRES, Kc), and the subscriber's current location at the level of the Visitor Location Register (VLR) or SGSN (for GPRS/UMTS). The HLR is not involved in the real-time path of a voice call or SMS but is queried by other network elements to retrieve critical routing and subscription data.
Architecturally, the HLR interfaces with several core network nodes via SS7 (Signaling System No. 7) signaling in 2G/3G, often using the Mobile Application Part (MAP) protocol. Key interfaces include the HLR-VLR interface (the D interface), where the HLR updates the VLR with subscriber data when the subscriber roams into its area and receives location updates. The HLR also interfaces with the Mobile Switching Center (MSC) for call routing and with the Authentication Center (AuC), which is often integrated with the HLR, to obtain authentication vectors. When a mobile-terminated call arrives, the Gateway MSC (GMSC) queries the HLR via the Send Routing Information (SRI) MAP operation. The HLR, in turn, queries the current VLR for a temporary routing number called the Mobile Station Roaming Number (MSRN), which is then returned to the GMSC to route the call to the correct MSC/VLR serving the subscriber.
In the evolution to 4G LTE and 5G, the functions of the HLR (and the AuC) are subsumed by the Home Subscriber Server (HSS) in the IP Multimedia Subsystem (IMS) and Packet Core. However, for legacy 2G/3G CS services, the HLR remains operational, often integrated with the HSS in a combined HLR/HSS node. Its role is absolutely critical for mobility: it tracks the subscriber's approximate location (VLR/SGSN address) as they move, enabling the network to route calls and messages correctly. It also acts as the authoritative source for determining what services a subscriber is allowed to use, enforcing subscription-based controls.
Purpose & Motivation
The HLR was created to solve the fundamental problem of subscriber mobility and service portability in early digital cellular networks (GSM). Prior cellular systems had limited or cumbersome mechanisms for handling roaming. The HLR, as a centralized, intelligent database, provided a scalable solution. It decouples the subscriber's permanent identity and profile from their temporary physical location. This allows a subscriber to move anywhere within network coverage (and even to other operator networks via roaming agreements) while the network can always locate them to deliver services.
The historical context is the GSM architecture's clear separation between the home network (where the HLR resides) and the visited network (where the VLR resides). This model enabled global roaming. The HLR solves the problems of: 1) **Call Routing**: Determining the current serving switch for an incoming call without broadcasting queries network-wide. 2) **Authentication**: Providing the visited network with the credentials to verify the subscriber's identity securely. 3) **Service Consistency**: Ensuring that a subscriber's personalized services (like call forwarding) work consistently regardless of location. Before such a centralized repository, implementing these features across a large, distributed network would have been highly complex and inefficient. The HLR, along with the VLR, established the blueprint for mobility management that later evolved into more IP-centric models in 4G/5G.
Key Features
- Centralized permanent storage of subscriber identity (IMSI), number (MSISDN), and service profile
- Maintains dynamic subscriber location information (current VLR/SGSN address)
- Generates and stores authentication data (integrated with or connected to AuC)
- Provides critical routing information for mobile-terminated calls and SMS via MSRN retrieval
- Manages subscription-based service provisioning and barring
- Interfaces with network elements (MSC, VLR, GMSC, SGSN) using MAP over SS7 signaling
Evolution Across Releases
The HLR was a mature, foundational component from GSM, carrying forward into the 3G UMTS Release 99 architecture. In this release, it continued to serve as the primary CS domain subscriber database, with enhanced MAP protocols to interface with both 2G MSC/VLR and new 3G SGSN nodes for combined CS/PS subscriber data management.
Defining Specifications
| Specification | Title |
|---|---|
| TS 21.905 | 3GPP TS 21.905 |
| TS 21.978 | 3GPP TS 21.978 |
| TS 22.121 | 3GPP TS 22.121 |
| TS 22.945 | 3GPP TS 22.945 |
| TS 22.949 | 3GPP TS 22.949 |
| TS 22.980 | 3GPP TS 22.980 |
| TS 23.066 | 3GPP TS 23.066 |
| TS 23.078 | 3GPP TS 23.078 |
| TS 23.127 | 3GPP TS 23.127 |
| TS 23.141 | 3GPP TS 23.141 |
| TS 23.171 | 3GPP TS 23.171 |
| TS 23.179 | 3GPP TS 23.179 |
| TS 23.221 | 3GPP TS 23.221 |
| TS 23.234 | 3GPP TS 23.234 |
| TS 23.251 | 3GPP TS 23.251 |
| TS 23.271 | 3GPP TS 23.271 |
| TS 23.379 | 3GPP TS 23.379 |
| TS 23.804 | 3GPP TS 23.804 |
| TS 23.851 | 3GPP TS 23.851 |
| TS 23.923 | 3GPP TS 23.923 |
| TS 23.976 | 3GPP TS 23.976 |
| TS 24.206 | 3GPP TS 24.206 |
| TS 24.234 | 3GPP TS 24.234 |
| TS 24.259 | 3GPP TS 24.259 |
| TS 24.292 | 3GPP TS 24.292 |
| TS 25.305 | 3GPP TS 25.305 |
| TS 28.622 | 3GPP TS 28.622 |
| TS 29.198 | 3GPP TS 29.198 |
| TS 31.900 | 3GPP TR 31.900 |
| TS 32.101 | 3GPP TR 32.101 |
| TS 32.102 | 3GPP TR 32.102 |
| TS 32.140 | 3GPP TR 32.140 |
| TS 32.141 | 3GPP TR 32.141 |
| TS 32.240 | 3GPP TR 32.240 |
| TS 32.250 | 3GPP TR 32.250 |
| TS 32.251 | 3GPP TR 32.251 |
| TS 32.270 | 3GPP TR 32.270 |
| TS 32.271 | 3GPP TR 32.271 |
| TS 32.272 | 3GPP TR 32.272 |
| TS 32.276 | 3GPP TR 32.276 |
| TS 32.278 | 3GPP TR 32.278 |
| TS 32.293 | 3GPP TR 32.293 |
| TS 32.401 | 3GPP TR 32.401 |
| TS 32.622 | 3GPP TR 32.622 |
| TS 32.808 | 3GPP TR 32.808 |
| TS 32.833 | 3GPP TR 32.833 |
| TS 33.102 | 3GPP TR 33.102 |
| TS 33.107 | 3GPP TR 33.107 |
| TS 33.220 | 3GPP TR 33.220 |
| TS 33.223 | 3GPP TR 33.223 |
| TS 33.820 | 3GPP TR 33.820 |
| TS 33.863 | 3GPP TR 33.863 |
| TS 33.924 | 3GPP TR 33.924 |
| TS 41.033 | 3GPP TR 41.033 |
| TS 43.020 | 3GPP TR 43.020 |
| TS 43.318 | 3GPP TR 43.318 |
| TS 43.901 | 3GPP TR 43.901 |
| TS 43.902 | 3GPP TR 43.902 |
| TS 44.318 | 3GPP TR 44.318 |
| TS 52.402 | 3GPP TR 52.402 |