Visited-Gateway Mobile Location Centre

Description

The Visited-Gateway Mobile Location Centre (V-GMLC) is a critical functional node within the 3GPP standardized architecture for Location Services (LCS). It is deployed in the Visited Public Land Mobile Network (VPLMN) when a target User Equipment (UE) is roaming. The V-GMLC serves as the primary entry point in the visited network for location requests originating from external Location Based Service (LBS) clients or from the Home-GMLC (H-GMLC) in the subscriber's home network. Its fundamental role is to manage the location retrieval process within the visited network's domain, ensuring that privacy, security, and regulatory requirements are met.

Operationally, when a location request for a roaming subscriber is received (often routed via the H-GMLC), the V-GMLC performs several key functions. First, it validates the request against local policies and may interact with the Home Location Register (HLR) or Home Subscriber Server (HSS) for subscriber authorization. Following this, the V-GMLC selects an appropriate positioning method based on the requested Quality of Service (QoS), such as Cell-ID, Observed Time Difference of Arrival (OTDOA), or Assisted GNSS (A-GNSS). It then communicates with the visited network's core elements, primarily the Mobile Switching Centre (MSC) or Mobility Management Entity (MME)/Access and Mobility Management Function (AMF), which in turn engages the radio access network and potentially the UE itself to obtain positioning measurements.

Once the location estimate is calculated (either in the network or by the UE), the result is delivered back to the V-GMLC. The V-GMLC is responsible for formatting this result, which may include latitude, longitude, altitude, and accuracy estimates, into a standardized shape. It then routes the location answer back to the requesting entity, typically the H-GMLC, which subsequently delivers it to the external LCS client. The V-GMLC also handles charging data generation for the location transaction performed in the visited network, which is essential for inter-operator settlement. Its architecture ensures that the visited network maintains control over its positioning resources and subscriber data while cooperating with the home network to provide a seamless LCS experience for roaming users.

Purpose & Motivation

The V-GMLC was introduced to enable lawful and commercial Location-Based Services (LCS) for subscribers when they are roaming outside their home network. Prior to its standardization, providing the location of a roaming user was complex and non-standardized, often requiring direct, proprietary interfaces between operators or limiting services to home network coverage only. This was inadequate for emergency services (e.g., E112/E911), which require reliable location regardless of network, and for commercial applications like fleet tracking or location-based advertising that need to function seamlessly across borders.

Its creation in Release 6 as part of the mature LCS architecture solved the critical problem of access control and network resource management in a roaming scenario. The V-GMLC allows the visited network operator to authenticate and authorize location requests, protecting subscriber privacy and ensuring compliance with local regulations. It also enables the visited operator to utilize its own, potentially more accurate, positioning infrastructure and to charge for the use of its network resources. By defining a clear gateway function in the visited network, 3GPP established a scalable, secure, and interoperable model for global LCS, which became foundational for emergency services, value-added services, and network optimization tools worldwide.

Key Features

• Gateway for location requests targeting roaming subscribers
• Authorization of location requests based on subscriber privacy profiles
• Interaction with visited network core (MSC/MME/AMF) and positioning systems
• Support for multiple positioning methods (e.g., Cell-ID, OTDOA, A-GNSS)
• Generation of charging data records (CDRs) for visited network usage
• Secure interworking with the Home-GMLC (H-GMLC) via standardized interfaces

Evolution Across Releases

Defining Specifications