Visitor Location Register

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.

Key Features

• Temporary storage of roaming subscriber profiles fetched from the HLR
• Co-location with and dedicated service to a specific MSC
• Assignment and management of Temporary Mobile Subscriber Identities (TMSI) for privacy
• Management of Location Areas and handling of location update procedures
• Provision of roaming numbers (MSRN) for inbound call routing
• Handles authentication and ciphering by interfacing with the AuC

Evolution Across Releases

Defining Specifications