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

Glossary term · Services

V-GMLC

Visited-Gateway Mobile Location Centre

Also written as: VGMLC

Services →

V-GMLC is the Gateway Mobile Location Centre in a visited network that provides location information for roaming subscribers by interfacing with local positioning systems and the home network's GMLC.

Where
Services › IMS
Specifications
6 specs
Also in
Core Network
V-GMLC Description Purpose What changed Family Neighbours Detected Changes Specifications

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.

What changed in its specifications

The latest release-to-release comparison of specifications that define V-GMLC. Each summary describes the whole specification, not only this term.

TS 23.271Rel-18 → Rel-19

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

Full comparison in TS 23.271 →
TS 29.173Rel-13 → Rel-14

Rel-14 updated routing rules, protocol references, command-code handling, and AVP treatment in the Diameter base specification.

Full comparison in TS 29.173 →

Technology family

Location services architecture · Services

  1. R98 BSSAP-LE, BSSLAP, GMLC, LMU, RRLP, SMLC
  2. Rel-5 PCAP, SAS
  3. Rel-6 PPR, R-GMLC
  4. Rel-7 LRF, SUPL
  5. Rel-9 E-SMLC, LCS-AP, LPP, LPPa
  6. Rel-15 LMF, NRPPa
  7. Rel-18 LCS-UPP, RSPP, SLPP

Also in this family (introduction release not pinned to a single defining specification): H-GMLC, LMC, MLP, V-GMLC

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 7 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.

Rel-6 specification text

The V-GMLC is specified for the first time, with procedures for MT-LR, deferred location requests, cancellation and MO-LR handling, and a charging record (LCS-VGMT-CDR) for location requests via the V-GMLC.

  • “The V-GMLC sends the location service response to the H-GMLC in accordance with the requested LCS QoS Class.” TS 23.271 v6.13.0
  • “The V-GMLC sends a Deferred Location Request to the SGSN/MSC by means of Provide Subscriber Location” TS 23.271 v6.13.0
  • “a LCS Visited GMLC Mobile terminated Charging Data Record (LCS-VGMT-CDR) shall be produced for each mobile a terminated location request is performed via the V-GMLC” TS 32.271 v6.2.0
Rel-7 specification text

The V-GMLC gained new or changed procedures in TS 23.271 Rel-7, such as forwarding location cancellation for periodic requests even when not involved in setup, and combining concurrent MT-LR and NI-LR requests.

  • “The V-GMLC shall transfer the location cancellation even when the V-GMLC was not involved in establishing the periodic location request” TS 23.271 v7.10.0
  • “A V‑GMLC may combine concurrent MT‑LR and NI‑LR related location requests for the same target UE” TS 23.271 v7.10.0
  • “The V-GMLC sends an LCS Service Response to the H-GMLC with an indication of the periodic event occurrence, the LDR reference number” TS 23.271 v7.10.0
Rel-9 specification text

V-GMLC gains EPC/MME-related behaviour: it receives MME and SGSN addresses with ISR, handles Subscriber Location Report from the MME with charging, and its address is provided via MME and HSS.

  • “If the V-GMLC receives the Subscriber Location Report from the MME and it is not required to send to any LCS Client” TS 23.271 v9.8.0
  • “If ISR is active for LTE access, the V-GMLC receives both an SGSN and MME address.” TS 23.271 v9.8.0
  • “may include the IP address of the V-GMLC associated with the MME in the Update Location Request message” TS 23.271 v9.8.0
Rel-12 specification text

V-GMLC behaviour changed in Rel-12: it now handles Optimized Lgd (activation from HSS, support or not) when instigating MT-LR procedures, and receives an 'Optimized Lgd' indicator from the HLR/HSS.

  • “The VGMLC which hasn't received activation of Optimized Lgd procedures (see clause 5.7) from HSS and which doesn't support Optimized Lgd procedures” TS 23.271 v12.1.0
  • “the V-GMLC address associated with the serving nodes, if available, "Optimized Lgd" indicator if enabled according to the criteria in clause 5.7” TS 23.271 v12.1.0
Rel-14 specification text

V-GMLC now handles area event reporting toward the MME, converting target areas to cell identities and/or tracking areas and forwarding event details, and cancels periodic and triggered requests via the serving MME.

  • “the V-GMLC converts the target area into a corresponding list of cell identities and/or tracking areas” TS 23.271 v14.4.0
  • “sends the Provide Subscriber Location request to the serving MME, indicating a cancellation of a deferred location request for periodic and triggered location” TS 23.271 v14.4.0
Rel-16 specification text

A new clause specifies how a V-GMLC combines location requests, and the V-GMLC takes part in releasing resources after Namf_Location_CancelLocation.

Rel-18 specification text

The V-GMLC (if used) is now specified to receive forwarded user plane reporting request, user plane address, security information and cumulative event report criteria in the procedure.

  • “the request for user plane reporting, the user plane address, the security information and the criteria for sending cumulative events reports over control plane are forwarded in sequence to the V-GMLC (if used)” TS 23.273 v18.12.0

Defining Specifications

3GPP specifications that define or reference V-GMLC, with the latest known release. Sourced from the 3GPP document catalog — see methodology.

SpecificationTitleRelease
TS 23.271 vj00 LCS Stage 2 Specification Rel-19 read
TS 29.173 vj00 Diameter-based SLh Interface for LCS Rel-19 read
TS 32.271 vj20 3GPP LCS Charging Management Spec Rel-19 read
TS 32.272 vj00 Charging for Push-to-Talk over Cellular (PoC) Rel-19 read
TS 23.273 vj70 5G Location Services Architecture Stage 2 Rel-19 read
TS 33.814 vg01 Security aspects of enhanced Location Services (eLCS) Rel-16 read