Description
The Visited Gateway Mobile Location Centre (VGMLC) is a core network entity defined in 3GPP for location-based services (LBS), specifically operating within the visited Public Land Mobile Network (VPLMN) when a mobile subscriber is roaming. Architecturally, it functions as a type of Gateway Mobile Location Centre (GMLC) that resides in the network where the subscriber is currently located, as opposed to the Home GMLC (HGMLC) in the subscriber's home network. The VGMLC serves as a privacy and regulatory enforcement point, intercepting location requests from external Location Service Clients (LCS clients) or from the HGMLC before they reach the visited network's positioning systems. Its primary role is to authenticate and authorize location queries, apply local privacy rules, and ensure compliance with the visited country's legal requirements for location disclosure.
When a location request is initiated for a roaming subscriber, the HGMLC first identifies that the subscriber is in a visited network and forwards the request to the VGMLC via standardized interfaces like Lg or SLh. The VGMLC then performs privacy checks based on the subscriber's profile and local regulations, which may include verifying consent, checking for barring settings, or applying additional authentication. If authorized, the VGMLC interacts with the visited network's Mobile Switching Centre (MSC) or Mobility Management Entity (MME) and Serving Mobile Location Centre (SMLC) to obtain the subscriber's location using methods like Cell-ID, OTDOA, or A-GPS. The retrieved location data is then formatted and returned to the HGMLC, which forwards it to the LCS client, ensuring that sensitive location information does not directly exit the visited network without proper controls.
Key components involved with VGMLC include the HGMLC, which initiates requests; the SMLC, which computes location estimates; and the MSC/MME, which provides subscriber context. The VGMLC implements interfaces such as Lg for circuit-switched domains and SLh for IP-based domains, aligning with 3GPP's evolving architecture. It supports various LCS service types, including emergency, value-added, and lawful interception services, with tailored procedures for each. By acting as a gatekeeper, the VGMLC prevents unauthorized location tracking, mitigates security risks, and ensures that roaming subscribers' location data is handled according to the policies of both home and visited networks, facilitating cross-border LBS while maintaining trust and compliance.
Purpose & Motivation
VGMLC was introduced to address privacy, security, and regulatory challenges in providing location-based services to roaming subscribers across different network operators and countries. Prior to its standardization, location requests for roaming users were often handled directly by the home network's GMLC, which could bypass local privacy laws and regulations of the visited country. This posed legal risks, as countries have varying requirements for location data disclosure, such as for emergency services or lawful interception. VGMLC solves this by ensuring that location retrieval occurs under the jurisdiction of the visited network, where local rules can be enforced, protecting both subscribers and operators from compliance violations.
The motivation stems from the growing demand for LBS like emergency calling (e.g., E911 in the US), navigation, and fleet tracking, which require accurate location even when users roam internationally. Without a VGMLC, visited networks might lack control over location queries, leading to potential misuse or unauthorized access. By deploying a VGMLC, visited operators can implement their own privacy policies, authenticate external requests, and log location transactions for auditing, enhancing security. This is particularly critical for emergency services, where location must be provided quickly and accurately to local authorities, regardless of the subscriber's home network.
Historically, VGMLC emerged in 3GPP Release 16 as part of broader enhancements to LCS architecture, reflecting increased focus on privacy regulations like GDPR. It addresses limitations of earlier approaches where HGMLC directly accessed visited network elements, which could compromise subscriber privacy and regulatory compliance. By introducing VGMLC, 3GPP enabled seamless and secure cross-border LBS, supporting global roaming while ensuring that location data processing adheres to local legal frameworks, thereby fostering trust and interoperability in mobile networks.
Key Features
- Acts as privacy enforcement point in visited network for roaming subscriber location services
- Authenticates and authorizes location requests from home network or external clients
- Applies local regulatory and privacy policies before disclosing location information
- Interfaces with visited network SMLC and MSC/MME to retrieve positioning data
- Supports emergency, commercial, and lawful interception location service types
- Ensures compliance with cross-border data protection regulations like GDPR
Evolution Across Releases
Introduced VGMLC as a new entity in the LCS architecture to enhance privacy and regulatory compliance for roaming subscribers. Defined its role as an intermediary in the visited network, with interfaces to HGMLC and visited network elements, ensuring local control over location data retrieval and disclosure.
Defining Specifications
| Specification | Title |
|---|---|
| TS 23.273 | 3GPP TS 23.273 |
| TS 33.814 | 3GPP TR 33.814 |