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
Phase 1
Where
Services › IMS
Specifications
60 specs
Also in
Core Network, Management, Security, Radio Access Network
HLR Description Purpose What changed Family 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

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
  • HLR decomposed into HLR-FE
    “The application that is handled by an AFE determines the type of AFE, e.g. HLR-FE or HSS-FE.” TS 23.002
  • HLR counterpart in another generation: HSS
    “For EPS, the HLR functionality is provided via HSS.” TS 23.002

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 13 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.

Phase 1 introduced

Introduced in Phase 1 (release dating of the term; no individual change cited).

R99 1 CR

In R99 the HLR gains CAMEL-related responsibilities: storing CSI data (O-CSI, D-CSI, T-CSI, VT-CSI, TIF-CSI), sending them to the VLR and GMSC, applying trigger criteria, and supporting LCS data restoration.

  • “For subscribers requiring CAMEL support, the HLR stores the information relevant to the current subscription regarding O-CSI, D‑CSI, T-CSI, VT-CSI and TIF-CSI.” TS 23.078 v3.19.0
  • “The HLR shall include the information for this TDP in the CAMEL subscription information sent to the GMSC only if the criteria are met.” TS 23.078 v3.19.0
  • Inclusion of D-CSI check in HLR/VLR TS 23.018CR032
Rel-4 specification text

The HLR gains new LCS roles: it stores LCS subscription and privacy class data and provides routing information (VMSC/SGSN addresses, IMSI) to the GMLC over the new Lh interface.

  • “The HLR contains LCS subscription data and routing information. The HLR is accessible from the GMLC via the Lh interface.” TS 23.271 v4.13.0
  • “For each LCS privacy class, the HLR shall store the logical state of the class on a per-subscriber” TS 23.271 v4.13.0
  • “Lh interface: interface between GMLC and HLR. This interface is used by the GMLC to request the address of the visited MSC or SGSN” TS 23.271 v4.13.0
Rel-5 specification text

HLR behaviour was extended in Rel-5: it handles CAMEL phase 4 CSI offers and trigger criteria, provides subscriber info for SGSN, supports SCUDIF in routing-info handling, and acts as an LCS routing source.

  • “A functional entity shall indicate to the HLR all the CSIs it offers.” TS 23.078 v5.12.0
  • “If the HLR does not support SCUDIF, the test "Result = Fail ?" applies to the result of the Subscription_Check_HLR procedure.” TS 23.018 v5.10.0
  • “The MSC/VLR may inform HLR/HSS about the UE’s LCS Capabilities in the MAP UPDATE LOCATION message” TS 23.271 v5.13.0
Rel-6 specification text

The HLR's role changed: it may now retrieve and return IMEI and MS Class to the gsmSCF as well as location and state, and returns V-GMLC and PPR addresses for LCS routing.

  • “If any of location information, subscriber state information, IMEI and MS Class is requested by the gsmSCF, then the HLR may retrieve this information” TS 23.078 v6.10.0
  • “The HLR/HSS returns the address of the H-GMLC. The HLR/HSS also returns the address of the PPR, if available.” TS 23.271 v6.13.0
  • “may include the IP address of the V-GMLC associated with the MSC/VLR in the MAP UPDATE LOCATION message” TS 23.271 v6.13.0
Rel-7 specification text

The HLR gained new behaviour in Rel-7: IP-SM-GW registration and deregistration handling, and a mobile terminating roaming retry feature in which it delays the PRN until Location Update completes.

  • “A HLR implementing the Mobile Terminating Roaming Retry feature (see sub-clause 5.2.1) shall delay the sending of the PRN message till completion of any on-going Location Update procedure.” TS 23.018 v7.7.0
  • “This IF is used to register the IP-SM-GW for a subscriber in the HLR.” TS 23.078 v7.10.0
  • “A HLR supporting the "mobile terminating roaming retry" feature includes the Call Reference Number, the GMSC address and the MT Roaming Retry Supported IE in the PRN” TS 23.018 v7.7.0
Rel-8 specification text

HLR behaviour was extended: it may return eMLPP priority and paging area in SRI/PRN signalling, indicate Location Information in EPS support, and its restart actions were reworded as normative ('shall').

  • “Shall be present if the Paging Area function is supported and if the paging area is stored in HLR” TS 23.018 v8.5.0
  • “This parameter should be present if the HLR supports this parameter and if the Call Priority was received” TS 23.018 v8.5.0
  • “When an HLR restarts after failure it shall perform the following actions for the subscriber data records” TS 23.007 v8.9.0
Rel-9 specification text

HLR behaviour changed: it now handles MT Roaming Retry (relaying 'mtRoamingRetry' SRI negative responses, passing call reference and GMSC address in PRN) and, for LCS, returns MME addresses to the GMLC.

  • “A HLR supporting the "mobile terminating roaming retry" feature includes the Call Reference Number and the GMSC address in the PRN sent to the MSC/VLR” TS 23.018 v9.4.0
  • “the HLR shall relay a SRI negative response with the error "absent subscriber" including the reason "mtRoamingRetry" to the GMSC” TS 23.018 v9.4.0
  • “the HLR shall send to the VLR the MME name or/and the SGSN Number if the subscriber is registered on this VLR” TS 23.007 v9.10.0
Rel-10 specification text

HLR gained new responsibilities: notifying gsmSCFs of more data types, and authorising MT Roaming Forwarding via MAP Update Location and Cancel Location flags, including always sending Cancel Location to the old VLR.

  • “The HLR maintains a list of gsmSCF address(es) for Call Forwarding Data, Call Barring Data, ODB, Call Waiting data, Call Hold data” TS 23.078 v10.1.0
  • “an HLR supporting the MTRF feature decides whether to authorise MTRF call between the old and the new MSCs based on roaming agreements” TS 23.018 v10.4.0
  • “shall always send a MAP Cancel Location message message to the old VLR upon receipt of the MAP Update Location from the new VLR” TS 23.018 v10.4.0
Rel-11 1 CR

HLR gained a domain selection function (Domain_Selection_HLR procedure) for CS/IMS subscribers and MTRF Supported handling, and restoration procedures now also cover CSS data alongside HLR data.

  • “7.2.2.12 Procedure Domain_Selection_HLR” TS 23.018 v11.4.0
  • “If the GMSC performs domain selection through HLR interrogation and the HLR supports domain selection functionality, HLRB executes domain selection functionaility.” TS 23.018 v11.4.0
  • HLR/HSS domain selection function alignment with Stage 2 requirement TS 23.018CR0182
Rel-12 specification text

HLR behaviour changed: it now includes GMSC address and call reference in MAP Provide Roaming Number, and HLR/HSS returns an 'Optimized Lgd' indicator in LCS routing information responses.

  • “The HLR shall include these parameters in the MAP Provide Roaming Number if received in the MAP Send Routing Information.” TS 23.018 v12.2.0
  • “"Optimized Lgd" indicator if enabled according to the criteria in clause 5.7” TS 23.271 v12.1.0
  • “When an HLR/HSS restarts after failure it shall perform the following actions for the subscriber data records” TS 23.007 v12.9.0
Rel-13 1 CR

HLR/HSS restoration procedures were revised: periodic backup of HLR/HSS data to non-volatile storage became mandatory, and restart and reset handling now covers VLRs, SGSNs and MMEs.

  • “The periodic backup of HLR/HSS data to non-volatile storage is mandatory.” TS 23.007 v13.7.0
  • “Restoration of the data in the HLR/HSS requires co-operation from all the VLRs, SGSNs and MMEs at which its mobiles are registered.” TS 23.007 v13.7.0
  • Update HSS/HLR functionality to support non-IP data delivery via SCEF TS 23.682CR0165
Rel-15 2 CRs

CRs to 33.107 and 33.108 corrected HLR-related behaviour: the Subscriber Record Change event by HLR (CS and PS) and HLR-triggered IRI messages for PS.

  • Stage 2 Corrections to the Subscriber Record Change event by HLR for CS TS 33.107CR0288
  • Stage 3 Corrections to the HLR triggered IRI messages for PS TS 33.108CR0390

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 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 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 NRM Rel-11 read
TS 32.808 v800 Common Profile Storage Framework for User Data Rel-8 read
TS 32.833 vb00 Fixed-Mobile Convergence 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