Gateway Location Register

Description

The Gateway Location Register is a specialized network element defined in 3GPP specifications for GSM and UMTS core networks (circuit-switched domain). Its primary function is to serve as a temporary cache for subscriber data of inbound roaming users. When a subscriber roams into a visited network, instead of the Visited Mobile Switching Center (VMSC) querying the subscriber's Home Location Register (HLR) in the home network for every mobility or service event, the visited network's GLR assumes the role of the HLR for that subscriber. The GLR first fetches the subscriber's profile from the real HLR during the initial registration (location update) and stores it locally. Subsequently, the VMSC interacts with the GLR as if it were the HLR for procedures like call delivery, location updates within the visited network, and supplementary service interrogation.

Architecturally, the GLR is typically deployed at the network edge, often integrated with a Gateway MSC (GMSC) or as a standalone node. It interfaces with the VMSC using the standard B/ C / D interfaces (MAP protocols) and appears to the home network's HLR as a standard VLR. This transparency is key; the HLR is unaware of the GLR's presence and simply sees it as the VLR currently serving the subscriber. The GLR manages the subscriber's mobility within the entire visited network (which may contain multiple VLR areas). Only when the subscriber moves out of the entire visited network's coverage does the GLR inform the HLR of the new location, thereby minimizing international MAP signaling.

For mobile-terminated calls, the call is routed to the visited network's GMSC. The GMSC queries the HLR, which holds the GLR's address as the current "VLR." The HLR provides a roaming number from the GLR (not the VMSC). The GLR, holding the subscriber's current VMSC address, then itself requests a roaming number from that VMSC and forwards it to the GMSC to complete the call setup. This two-step process keeps the HLR out of the per-call signaling path within the visited network. The GLR also handles authentication, often by obtaining a batch of authentication vectors from the HLR and using them sequentially, further reducing signaling.

Purpose & Motivation

The GLR was developed to address the significant signaling cost and latency associated with international roaming in early GSM networks. Without a GLR, every mobility event (like moving between location areas) and every mobile-terminated call setup for a roaming subscriber required signaling exchanges between the visited MSC/VLR and the home HLR across often expensive and congested international signaling links (SS7). This resulted in high operational costs for operators, increased call setup delays, and a load on the HLR.

The introduction of the GLR solved this by localizing signaling within the visited network. By caching the subscriber's data, the visited network could handle most procedures autonomously. The primary motivations were economic (reducing international signaling traffic) and performance-related (improving service responsiveness for roaming users). It was particularly beneficial for operators in regions with high volumes of inbound tourism or business travel. The GLR concept allowed visited network operators to offer better service quality to roamers while controlling their own signaling infrastructure costs, making roaming agreements more efficient. It represented an optimization within the core network architecture before the widespread adoption of IP-based transport reduced some of the cost disparities.

Key Features

• Acts as a temporary HLR proxy for inbound roaming subscribers, caching their profiles locally.
• Significantly reduces international MAP signaling between visited and home networks.
• Handles mobility management (location updates) within the visited network without contacting the HLR.
• Manages call routing for mobile-terminated calls by interacting with the VMSC to obtain roaming numbers.
• Can batch-fetch authentication vectors from the HLR to perform local authentication.
• Transparent to the home HLR, which sees the GLR as a standard Visited Location Register (VLR).

Evolution Across Releases

Defining Specifications