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

Glossary term · Core Network

HLR

Home Location Register

Core Network →

HLR is the central database in 2G and 3G circuit-switched networks that stores permanent subscriber data and location information for mobility management, authentication, and call routing.

Introduced
R99
Where
Services › IMS
Specifications
60 specs
Also in
Core Network, Management, Security, Radio Access Network
HLR Description Purpose What changed Neighbours Detected Changes Specifications

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.

What changed in its specifications

The latest release-to-release comparison of specifications that define HLR. 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 →

Evolution Lineage

Release Timeline

Detected Changes Across Releases

from 3GPP Change Requests

Specific changes extracted from the „Change history“ tables of 3GPP specifications (2 CRs across 1 releases). Complements the general historical overview above with the evidence-based evolution of this function.

Rel-15 2 changes
  • Stage 2 Corrections to the Subscriber Record Change event by HLR for CS TS 33.107CR0288
  • Stage 2 Corrections to the Subscriber Record Change event by HLR for PS TS 33.107CR0289

Defining Specifications

3GPP specifications that define or reference HLR, 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 21.978 v300 CAMEL Control of VoIP Services Feasibility Study R99 read
TS 22.121 v531 Virtual Home Environment Service Requirements Rel-5 read
TR 22.945 v300 Fax Services Guidance for GSM/UMTS R99 read
TR 22.949 vj00 Privacy Requirements Study for 3GPP Services Rel-19 read
TR 22.980 vj00 Network Composition Feasibility Study Rel-19 read
TS 23.066 vj00 Mobile Number Portability Technical Realization Rel-19 read
TS 23.078 vj00 CAMEL Phase 4 Stage 2 Specification 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.171 v390 LCS Stage 2 for UMTS R99 read
TS 23.179 vd50 MCPTT Functional Architecture Rel-13 read
TS 23.221 vj00 3GPP System Architectural Requirements Rel-19 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.379 vk40 Mission Critical Push-to-Talk Architecture Rel-20 read
TS 23.804 v710 SMS/MMS over IP Access Networks Rel-7 read
TS 23.851 v610 Network Sharing Architecture for 3G Systems Rel-6 read
TR 23.923 v300 Mobile IP+ Feasibility Study for UMTS/GPRS R99 read
TR 23.976 vj00 Push Service Requirements Analysis Rel-19 read
TS 24.206 v750 Voice Call Continuity Between CS and IMS Rel-7 read
TS 24.234 vc20 3GPP-WLAN Interworking Network Selection 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 25.305 vj00 UTRAN UE Positioning Stage 2 Rel-19 read
TS 28.622 vk40 Generic Network Resource Information Service Rel-20 read
TS 29.198 v340 OSA R99 API Stage 3 Specification R99 read
TR 31.900 vj00 3GPP TS 31.900: Security Interworking Guidance 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.240 vk10 3GPP Charging Architecture and Principles Rel-20 read
TS 32.250 vj00 Circuit Switched Offline Charging Rel-19 read
TS 32.251 vj00 PS Domain Charging Management Rel-19 read
TS 32.270 vj00 MMS Charging Management Specification 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.276 vj00 VCS Online Charging from Proxy Function Rel-19 read
TS 32.278 vj00 Monitoring Events Offline Charging Specification Rel-19 read
TS 32.293 vj00 Proxy Function in Domestic Service Provider Rel-19 read
TS 32.401 vj00 Performance Management Concept & Requirements Rel-19 read
TS 32.622 vb10 Generic Network Resources IRP NRM Rel-11 read
TS 32.808 v800 Common Profile Storage Framework for User Data Rel-8 read
TS 32.833 vb00 Converged OSS End-to-End Management Study Rel-11 read
TS 33.102 vj10 3G Security Architecture Specification Rel-19 read
TS 33.107 vj00 Lawful Interception Architecture & Functions Rel-19 read
TS 33.220 vj10 Generic Authentication Architecture (GAA) Security Rel-19 read
TS 33.223 vj00 GBA Push Function Specification Rel-19 read
TS 33.820 v830 H(e)NB Security Threats and Countermeasures Rel-8 read
TS 33.863 ve20 Security for Battery-Efficient IoT Device to Enterprise Rel-14 read
TR 33.924 vj00 GBA-OpenID Interworking Specification Rel-19 read
TS 41.033 ve00 GSM Lawful Interception Interface Requirements Rel-14 read
TS 43.020 vj00 Security Procedures for GSM Rel-19 read
TS 43.318 vj00 Generic Access Network (GAN) Stage 2 Rel-19 read
TR 43.901 vj00 Generic Access to A/Gb Interface Feasibility Study Rel-19 read
TR 43.902 vj00 GAN Enhancements Feasibility Study Rel-19 read
TS 44.318 vj00 Generic Access Network (GAN) Interface Procedures Rel-19 read
TS 52.402 vj00 GSM Performance Management Measurements Rel-19 read