Description
The Requesting Gateway Mobile Location Centre (R-GMLC) is a critical functional element within the 3GPP standardized Location Services (LCS) architecture, introduced with the Control Plane location solution for LTE. It serves as the gateway between external Location-Based Service (LBS) clients—known as LCS Clients—and the mobile network's internal location determination infrastructure. The R-GMLC is typically located in the subscriber's home network. Its primary function is to act as the first point of contact for an incoming location request, handling all client-facing aspects of the transaction.
Operationally, the R-GMLC receives a standardized location service request (e.g., using MLP or SUPL protocols) from an external LCS Client. It first performs crucial network access functions: it authenticates the LCS Client to verify its identity, authorizes the request against the target subscriber's privacy profile (checking LCS privacy settings stored in the HSS), and may handle charging triggers. Once the request is validated, the R-GMLC determines how to route it. If the target User Equipment (UE) is roaming, the R-GMLC forwards the request to the Gateway Mobile Location Centre in the visited network (V-GMLC). If the UE is in its home network, the R-GMLC may forward the request directly to the Home Gateway Mobile Location Centre (H-GMLC) or, in some architectures, assume the H-GMLC role itself. The R-GMLC does not directly engage in positioning calculations; instead, it orchestrates the request through the network and eventually receives the location estimate (e.g., geographic coordinates) from the network-side GMLC (H-GMLC or E-SMLC via MME). It then formats this result according to the client's requested response type and sends it back to the external LCS Client.
Architecturally, the R-GMLC interfaces with the HSS (for subscriber privacy data), other GMLCs (via the Lg interface), and external LCS Clients. Its role is pivotal for scalability and security, as it centralizes client authentication, privacy verification, and request routing, shielding the internal network elements from direct external access. In 5G systems, the analogous function is performed by the Location Management Function (LMF) in conjunction with the Network Exposure Function (NEF), but the R-GMLC remains a key concept in the evolution of control-plane positioning.
Purpose & Motivation
The R-GMLC was introduced to formalize and secure the interface between external service providers and the network's location capabilities in LTE. Prior to its explicit definition, location architectures like those in GSM and UMTS often combined gateway functions in a single GMLC node. The separation of the Requesting GMLC role was motivated by the need for clearer architectural separation, enhanced security, and better support for roaming scenarios in an all-IP network (EPS).
It solves several key problems: First, it provides a dedicated, secure entry point for third-party LBS applications, allowing for robust authentication and policy enforcement before any location request enters the core network. Second, it centralizes privacy checking against the subscriber's profile stored in the HSS, which is a critical regulatory and consumer trust requirement. Third, it simplifies routing logic in complex roaming situations by having a well-defined 'home' entity that decides whether to proxy the request to a visited network. This architecture addresses limitations of earlier, more monolithic designs by improving scalability, enabling more granular charging for location services, and providing a cleaner interface for network exposure, which became increasingly important with the growth of commercial LBS.
What changed in its specifications
The latest release-to-release comparison of specifications that define R-GMLC. Each summary describes the whole specification, not only this term.
Rel-14 updated routing rules, protocol references, command-code handling, and AVP treatment in the Diameter base specification.
Full comparison in TS 29.173 →Updated normative references for AVPs in the Debit/Reserve Units Response message to 3GPP TS 32.299.
Full comparison in TS 32.271 →Technology family
Location services architecture · Services
- R98 BSSAP-LE, BSSLAP, GMLC, LMU, RRLP, SMLC
- Rel-5 PCAP, SAS
- Rel-6 PPR, R-GMLC
- Rel-7 LRF, SUPL
- Rel-9 E-SMLC, LCS-AP, LPP, LPPa
- Rel-15 LMF, NRPPa
- 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 sourcesDocumented changes in 2 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.
TS 32.271 first specifies R-GMLC roles in LCS charging: it receives client requests, obtains the H-GMLC address, forwards requests, returns responses, and produces LCS-RGMT CDRs.
- “The R-GMLC requests the H-GMLC address by sending a MAP Send Routing Info for LCS message to the home HLR/HSS” TS 32.271 v6.2.0
- “a LCS Requesting GMLC Mobile terminated Charging Data Record (LCS-RGMT-CDR) shall be produced for each mobile a terminated location request is performed via the R-GMLC” TS 32.271 v6.2.0
- “The external LCS client requests the location of a target UE from the R-GMLC” TS 32.271 v6.2.0
TS 29.173 in Rel-9 lists R-GMLC (Requesting Gateway Mobile Location Centre) for the first time, as an abbreviation in the specification.
- “R-GMLC Requesting-Gateway Mobile Location Centre” TS 29.173 v9.4.0
Defining Specifications
3GPP specifications that define or reference R-GMLC, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TR 23.730 ve00 | Study on extended CIoT architecture | Rel-14 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 |