Requesting Gateway Mobile Location Centre

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.

Key Features

• Serves as the entry point and gateway for external LCS Client location requests
• Performs authentication and authorization of the requesting LCS Client
• Enforces subscriber privacy policy by interfacing with the HSS
• Routes location requests to the appropriate network (home or visited)
• Formats and returns location responses to the external client
• Interfaces with other core network nodes via standardized Lg and SLh interfaces

Evolution Across Releases

Defining Specifications