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

Glossary term · Core Network

VLR

Visitor Location Register

Core Network →

VLR is a core network database that temporarily stores subscriber data from a user's home HLR to enable call routing, authentication, and service provisioning while they are roaming in a specific MSC service area.

Introduced
Phase 1
Where
Core Network › Legacy Core
Specifications
35 specs
Also in
Management, Security, Radio Access Network
VLR Description Purpose What changed Family Neighbours Detected Changes Specifications

Description

The Visitor Location Register (VLR) is a fundamental database within the Circuit-Switched (CS) domain of a 2G/3G mobile network. It is always co-located with, and serves, a specific Mobile Switching Center (MSC). When a mobile subscriber roams into the geographical area controlled by an MSC, the associated VLR queries the subscriber's Home Location Register (HLR) to obtain a copy of their service profile. This profile includes critical information such as the International Mobile Subscriber Identity (IMSI), subscribed services (like call forwarding or barring), and authentication parameters. The VLR stores this data for the duration of the subscriber's presence in its area, allowing the MSC to handle call setup, supplementary services, and mobility management (like location updates) without needing to query the distant HLR for every transaction, thereby reducing signaling load and latency.

From an architectural perspective, the VLR-MSC pair forms the primary service node for circuit-switched voice and SMS. The VLR interfaces with the HLR via the MAP (Mobile Application Part) protocol over the SS7 signaling network. It also communicates with other MSCs/VLRs for handover procedures and with the Authentication Center (AuC) to obtain security triplets (RAND, SRES, Kc) for subscriber authentication and ciphering. The VLR assigns a temporary identifier, the Temporary Mobile Subscriber Identity (TMSI), to the subscriber for enhanced privacy, masking the permanent IMSI over the radio interface.

Its role is pivotal for mobility. It tracks the subscriber's precise location within its service area, typically at the level of a Location Area (LA). When the subscriber moves, the VLR updates the HLR with the new location and may also inform the previous VLR to purge its temporary record. For incoming calls or SMS, the Gateway MSC (GMSC) queries the HLR for routing information. The HLR, in turn, queries the current VLR for a Mobile Station Roaming Number (MSRN), a temporary number used to route the call to the serving MSC. Thus, the VLR acts as the local anchor and session manager for visiting subscribers, enabling seamless roaming and service continuity across network boundaries.

Purpose & Motivation

The VLR was created to solve the fundamental problem of enabling subscriber mobility and roaming in cellular networks. In early mobile systems, a central database would be overwhelmed with queries for every call attempt or location update from every subscriber in the network, regardless of their location. The VLR architecture decentralizes subscriber data management by introducing a hierarchical structure with a permanent home database (HLR) and temporary visitor databases (VLRs). This design dramatically reduces signaling traffic across the core network and decreases call setup times.

Its creation was motivated by the need for efficient use of network resources and scalable subscriber growth. By caching subscriber data locally at the point of service (the MSC area), the network minimizes long-distance signaling to the HLR, which might be in a different country for roaming subscribers. This local caching is essential for providing real-time services like voice calls. Furthermore, the VLR enables the implementation of location-based procedures (like paging a subscriber only in their current Location Area) and temporary identity assignment (TMSI), which enhances subscriber privacy by preventing tracking of the permanent IMSI over the air interface.

Before the VLR/HLR split concept, simpler architectures could not scale to support nationwide or international roaming efficiently. The VLR, as defined from GSM onwards, became the cornerstone for managing visiting subscribers, a concept so successful it influenced later core network architectures, even as the network evolved towards IP-based systems in later 3GPP releases.

What changed in its specifications

The latest release-to-release comparison of specifications that define VLR. 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.078Rel-18 → Rel-19

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

Full comparison in TS 23.078 →

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

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

R99 specifies VLR behaviour in new text: it indicates supported CAMEL phases and Super-Charger capability to the HLR, handles LMU/LCS data restoration, and sends mobility management notifications to the gsmSCF.

  • “When requesting location updating or data restoration the VLR shall indicate to the HLR which CAMEL phases it supports.” TS 23.078 v3.19.0
  • “This parameter is used by the VLR to indicate to the HLR that the VLR supports the Super-Charger functionality” TS 29.002 v3.20.0
  • Support of VLR and HLR Data Restoration procedures with LCS TS 23.003CR011
Rel-4 specification text

TS 29.002 Rel-4 extends VLR behaviour: VLR/SGSN handling of LCS information and capability sets, VBS data and charging characteristics, with the VLR reporting unsupported SS-Codes to the HLR.

  • “If the VLR/SGSN detects that there is overlapping in the LCS information received within a dialogue, it shall send the error Unexpected Data Value.” TS 29.002 v4.18.0
  • “This parameter indicates which capability sets of LCS are supported in the VLR or SGSN.” TS 29.002 v4.18.0
  • “This parameter is used only by the SGSN and if the VLR receives this parameter it shall ignore it.” TS 29.002 v4.18.0
Rel-5 specification text

VLR behaviour changed in Rel-5: it must indicate supported CAMEL phases and downloadable CAMEL phase 4 CSIs to the HLR at location update or restoration, and receives MO-SMS-CSI and MT-SMS-CSI.

  • “When requesting a location update or data restoration the VLR shall indicate to the HLR which CAMEL phases it supports and which CAMEL phase 4 CSIs can be downloaded.” TS 23.078 v5.12.0
  • “The VLR receives the MO‑SMS‑CSI and MT‑SMS‑CSI for the subscriber from the HLR.” TS 23.078 v5.12.0
  • “The VLR uses the HLR number or the HLR identity list included in the MAP_RESET indication to identify the IMSI records which are affected by the HLR restart.” TS 29.002 v5.13.0
Rel-6 specification text

MAP in Rel-6 extends VLR behaviour: UMTS trace parameter support, Presence Network Agent mobility event reporting, VLR/SGSN handling of unsupported SS-codes, and Access Restriction handling.

  • “This service is also used between the VLR and the Presence Network Agent or between the SGSN and the Presence Network Agent” TS 29.002 v6.17.0
  • “If the VLR/SGSN supports the Access Restriction feature but does not receive the Access Restriction Data parameter from the HLR” TS 29.002 v6.17.0
  • “This parameter indicates that UMTS trace parameters are supported in the VLR or in the SGSN.” TS 29.002 v6.17.0
Rel-7 specification text

VLR behaviour changed in Rel-7: it now reports supported RAT types to the HLR, handles RAT-based roaming restriction causes, and takes part in mobile terminating roaming retry and super-charged network procedures.

  • “This parameter indicates, if present, which access technologies (e.g. GERAN and / or UTRAN) are served by the MSC/VLR (see clause 7.6.3)” TS 29.002 v7.15.0
  • “the old MSC/VLR stops paging, if paging was on-going, and if it supports the "mobile terminating roaming retry" feature” TS 23.018 v7.7.0
  • “The VLR in a Super-Charged network receives a Cancel Location message that indicates an "updateProcedure".” TS 23.007 v7.0.0
Rel-8 specification text

VLR behaviour was extended for EPS: it sends SGs paging requests to the MME, returns E-UTRAN location in Provide Subscriber Information, and sends SGs Reset messages to MMEs on restart.

  • “If the SGs interface is implemented and the conditions for paging over the SGs interface as specified in subclause 5.1.2.2 of 3GPP TS 29.118 [40] are fulfilled, the VLR shall send an SGs paging request to the MME.” TS 23.018 v8.5.0
  • “Based on configuration data, "Reset" messages are sent on the SGs-interface to the MMEs by the VLR as described in the 3GPP TS 29.118 [14].” TS 23.007 v8.9.0
  • “The VLR should return in the Provide Subscriber Information response the tracking area ID and E-UTRAN cell ID received from the MME” TS 23.018 v8.5.0
Rel-9 1 CR

In Rel-9 the VLR restoration procedure changed: the HLR now sends MME name or SGSN number to the VLR during data restoration, and the VLR may perform restoration for SMS and set indicators.

  • “During the data restoration procedure, the HLR shall send to the VLR the MME name or/and the SGSN Number” TS 23.007 v9.10.0
  • “If the VLR has no IMSI record, or if the record is marked "Subscriber Data Not Confirmed by HLR", the VLR may perform the data restoration procedure” TS 29.002 v9.13.0
  • Sending of MME name or SGSN Number to the VLR during the data restoration procedure TS 29.002CR0975
Rel-10 1 CR

VLR behaviour changed: it now handles Subscribed Periodic LAU Timer, MTRF (mobile terminating roaming forwarding) signalling with old/new VLR roles, and uses MME/SGSN names from the HLR for paging.

  • “The MSC/VLR shall handle the Subscribed Periodic LAU Timer as specified in subclause 3.7.3 of 3GPP TS 23.012 [23].” TS 29.002 v10.11.0
  • “it shall not trigger any MAP Provide Roaming Number request to the new terminating VLR until is has received the MAP Cancel Location message.” TS 23.018 v10.4.0
  • Use of recovered MME Name / SGSN Name in MSC/VLR TS 29.002CR1008
Rel-11 1 CR

VLR gained new CSG/VCSG behaviour in Rel-11: it runs the Update VCSG Location procedure towards the CSS, handles CSS Reset/Cancel messages, and has new restoration indicators and MAP parameters.

  • “the VLR shall start an "Update VCSG Location" procedure to the CSS if the roaming MS is still in the CSG cell” TS 23.007 v11.8.0
  • “The VLR uses the CSS number (filled in Sending Node number parameter) included in the MAP_RESET indication to identify the user's IMSI records” TS 29.002 v11.12.0
  • Retrieving CSG subscription data from the CSS to the VLR/SGSN TS 29.002CR1049
Rel-12 1 CR

New MSC/VLR acting also as GMSC can deliver mobile terminating calls directly (MTRF optimal routing), and VLR/SGSN/MME restoration behaviour after VLR failure was revised.

  • “the new MSC/VLR may check whether it also performs the GMSC function for the call by comparing the GMSC address” TS 23.018 v12.2.0
  • “When a VLR fails, all its associations with MMEs affected by the failure become invalid and may be deleted.” TS 23.007 v12.9.0
  • MTRF Optimal Routing when the GMSC and new MSC/VLR are the same node TS 23.018CR0198
Rel-13 specification text

Restoration procedures involving the VLR changed: MME/SGSN reset handling with NGAF/NEAF flags, paging with VLR-provided location info, and re-attach with a new SGs association to a possibly different VLR.

  • “the MME sends the paging request with the location information provided by the VLR.” TS 23.007 v13.7.0
  • “or upon receipt of a Service Reject with Cause #10 – Implicitly detached (when using S-TMSI paging)” TS 23.007 v13.7.0
  • “shall set Non-EPS Alert Flag (NEAF) if an MME - MSC/VLR association exists.” TS 23.007 v13.7.0
Rel-14 specification text

VLR reset handling was extended: MAP_RESET can carry Reset-IDs and shared subscription data updates, which the VLR uses to identify affected IMSI records and to update stored subscription profiles.

  • “When Reset-IDs are supported and present in the MAP_RESET indication, the VLR uses the Reset-IDs included in the MAP_RESET indication to identify the affected IMSI records.” TS 29.002 v14.5.0
  • “If the update of shared subscription data requires only local updates in the VLR” TS 29.002 v14.5.0
  • “processing/signalling actions resulting from data updates in the VLR may take a maximum operator configuration-depending time.” TS 29.002 v14.5.0

Defining Specifications

3GPP specifications that define or reference VLR, 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
TR 22.945 v300 Fax Services Guidance for GSM/UMTS R99 read
TS 23.078 vj00 CAMEL Phase 4 Stage 2 Specification Rel-19 read
TS 23.221 vj00 3GPP System Architectural Requirements Rel-19 read
TS 23.226 vj00 Global Text Telephony (GTT) Stage 2 Rel-19 read
TS 23.251 vj00 Network Sharing Stage 2 Specification Rel-19 read
TS 23.851 v610 Network Sharing Architecture for 3G Systems Rel-6 read
TR 23.910 v550 CS Bearer Services in UMTS Rel-5 read
TR 23.923 v300 Mobile IP+ Feasibility Study for UMTS/GPRS R99 read
TS 24.259 vj00 Personal Network Management (PNM) Protocol Details Rel-19 read
TR 26.944 vj00 QoE, ESQoS and SQoS metrics for 3G multimedia services Rel-19 read
TS 28.622 vk40 Generic Network Resource Information Service Rel-20 read
TS 28.702 vj00 Core Network NRM IRP Information Service Rel-19 read
TS 29.198 v340 OSA R99 API Stage 3 Specification R99 read
TS 31.102 vk00 USIM Application Specification Rel-20 read
TR 31.900 vj00 3GPP TS 31.900: Security Interworking Guidance Rel-19 read
TS 32.102 vj00 Telecom Management Physical Architecture Framework 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.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.632 vb00 Core Network Resources NRM Rel-11 read
TS 32.732 vb00 IMS Network Resource Model Information Service Rel-11 read
TS 32.808 v800 Common Profile Storage Framework for User Data Rel-8 read
TS 33.102 vj10 3G Security Architecture Specification Rel-19 read
TS 33.859 vb10 UTRAN Key Hierarchy Study Rel-11 read
TS 43.318 vj00 Generic Access Network (GAN) Stage 2 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