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

Glossary term · Core Network

GMLC

Gateway Mobile Location Center

Core Network →

GMLC is the core network node that provides location-based services by managing positioning requests and acting as the interface between external location service clients and the mobile network to retrieve a UE's position.

Introduced
R98
Where
Core Network
Specifications
39 specs
Also in
Services, Management, Radio Access Network
GMLC Description Purpose What changed Family Neighbours Detected Changes Specifications

Description

The Gateway Mobile Location Center (GMLC) is a fundamental component of the 3GPP Location Services (LCS) architecture, serving as the gateway between external applications and the mobile network for obtaining the location of user equipment (UE). It functions as the first point of contact for external Location Service Clients (LCS clients), which are entities requesting UE positioning data for purposes such as emergency services (e.g., E911), commercial applications, or lawful interception. The GMLC handles authentication, authorization, and routing of location requests, ensuring that only authorized clients can access positioning information and that privacy regulations are adhered to. Upon receiving a request, the GMLC interacts with core network elements like the Home Subscriber Server (HSS) or Unified Data Management (UDM) to resolve the UE's serving node (e.g., MME, AMF, SGSN) and then forwards the request to the appropriate Mobile Switching Center (MSC), Serving GPRS Support Node (SGSN), or Access and Mobility Management Function (AMF) for positioning execution.

Architecturally, the GMLC consists of several logical functions, including the Requesting GMLC (R-GMLC) and Home GMLC (H-GMLC), depending on the UE's roaming status. In a home network scenario, the H-GMLC resides in the UE's home network and manages subscription and privacy checks. When a UE is roaming, the R-GMLC in the visited network may interface with the H-GMLC to coordinate location retrieval. The GMLC communicates via standardized interfaces: the Le interface connects to external LCS clients, the Lh interface links to the HSS/UDM for subscriber data, and the Lg/Lg+ interfaces connect to MSC, SGSN, or AMF for positioning requests. The positioning itself is performed by the Radio Access Network (RAN) using methods like Observed Time Difference of Arrival (OTDOA) in LTE/NR or Assisted GPS (A-GPS), with results returned to the GMLC for delivery to the client.

How it works involves a multi-step procedure: first, the LCS client sends a location request to the GMLC via the Le interface, specifying the target UE (e.g., by MSISDN or IMSI) and required quality of service (e.g., accuracy). The GMLC authenticates the client and checks privacy settings based on the UE's subscriber profile. It then queries the HSS/UDM to determine the UE's current serving node and network location. Next, the GMLC forwards the request to that serving node (e.g., AMF in 5G), which triggers positioning measurements in the RAN. Once the position is calculated, it is relayed back through the serving node to the GMLC, which formats and sends the result to the LCS client. This process supports both real-time positioning and deferred (historical) location retrieval, with the GMLC managing session state and error handling. Specifications such as 3GPP TS 23.271 and TS 29.172 detail the protocols and procedures, ensuring interoperability from 3G to 5G.

Purpose & Motivation

The GMLC was introduced in 3GPP Release 99 to standardize location-based services across mobile networks, addressing the growing demand for positioning capabilities driven by regulatory requirements (e.g., emergency call location) and commercial applications. Prior to its standardization, proprietary solutions existed, but they lacked interoperability and scalability, making it difficult for external applications to access UE location consistently across different operators and regions. The GMLC provided a unified gateway that abstracted network complexities, enabling seamless integration of location services.

Historically, the push for enhanced emergency services, such as the U.S. E911 mandate, was a key motivator for GMLC development. It solved the problem of quickly and accurately locating mobile callers in distress, regardless of their network attachment. By centralizing request handling and privacy management, the GMLC ensured that only authorized entities (e.g., public safety answering points) could access location data, balancing utility with user privacy. Over releases, its role expanded to support commercial use cases like navigation, fleet tracking, and location-based advertising, driven by the proliferation of smartphones and IoT devices.

Furthermore, the GMLC addressed limitations in earlier positioning systems by providing a flexible architecture that evolved with network technologies. From circuit-switched networks in 2G/3G to packet-switched in 4G/5G, the GMLC adapted through interfaces like Lg for MSC and Lg+ for AMF, ensuring backward compatibility and forward compatibility. Its creation enabled operators to monetize location data while complying with regulations, fostering a ecosystem of LCS applications. In 5G, the GMLC integrates with the Network Exposure Function (NEF) to expose location capabilities to third-party applications, highlighting its ongoing relevance in the service-based architecture.

What changed in its specifications

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

TR 21.905Rel-17 → Rel-18

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

Full comparison in TR 21.905 →
TS 23.078Rel-18 → Rel-19

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

Full comparison in TS 23.078 →

Architecture

Where it sits in the network

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

R98 introduced

Introduced in R98 (release dating of the term; no individual change cited).

Rel-4 specification text

The GMLC is specified for the first time in TS 23.271 as the first node an external LCS client accesses, handling routing queries, positioning requests via Lg, and location responses.

  • “The GMLC is the first node an external LCS client accesses in a GSM PLMN (i.e. the Le reference point is supported by the GMLC).” TS 23.271 v4.13.0
  • “The GMLC runs a timer while in the INTERROGATION state to limit the amount of time waiting for an interrogation response from the HLR.” TS 23.271 v4.13.0
Rel-5 specification text

GMLC in Rel-5 may request routing information from the HSS as well as the HLR, and the LCS Service Response to the client may now include the positioning method used.

  • “The LCS Service Response from the GMLC to the LCS client may contain the information about the positioning method used.” TS 23.271 v5.13.0
  • “The GMLC may request routing information from the HLR or HSS via the Lh interface.” TS 23.271 v5.13.0
Rel-6 specification text

Rel-6 extends the GMLC with the Lr interface between GMLCs (requesting, visited and home GMLC roles), PMD pseudonym handling and CS/PS selection, and adds GMLC charging functions in the new TS 32.271.

  • “Information needed for authorisation, location service requests and location information may be communicated between GMLCs, located in the same or different PLMNs, via the Lr interface.” TS 23.271 v6.13.0
  • “The Requesting GMLC can be the Visited GMLC, and either one or both of which can be the Home GMLC at the same time.” TS 23.271 v6.13.0
  • “LCS online charging is based on GMLC functionality that is further specified in the present document.” TS 32.271 v6.2.0
Rel-7 specification text

GMLC behaviour was extended: R-, H- and V-GMLC may combine concurrent location requests, the GMLC may have or connect to an SLP, and GMLC procedures were updated, including emergency SGSN determination.

  • “An R‑GMLC may combine concurrent MT‑LR requests for the same target UE‑LCS Client pair.” TS 23.271 v7.10.0
  • “NOTE 3: The GMLC can have the SLP functionality or GMLC can be connected to the SLP.” TS 23.271 v7.10.0
  • “The GMLC may store the information received in step 4: e.g. may store the UE identity and the address of the SGSN.” TS 23.271 v7.10.0
Rel-9 specification text

The GMLC was extended to support EPC: it may query the HSS via SLh, send positioning requests to the MME over SLg, and handle MME addresses and responses in MT-LR procedures.

  • “The GMLC may request routing information from the HLR via the Lh interface or HSS via the SLh/Lh interface.” TS 23.271 v9.8.0
  • “After the GMLC receives a location estimate response from the VMSC, MSC Server, SGSN, MME or V_GMLC” TS 23.271 v9.8.0
  • “If the GMLC receives only the MME address, the MT LR proceeds as the EPC-MT-LR procedure described in clause 9.1.15.” TS 23.271 v9.8.0
Rel-10 specification text

NEW adds that the numbers assigned to service types are defined in an annex, a sentence not present in OLD's GMLC/PPR privacy class storage text.

Rel-11 specification text

In emergency-call handover, the source MME now sends the 1xRTT Reference Cell ID to the source GMLC instead of the target 1xRTT MSC address, and the Subscriber Location Report may convey that ID.

  • “Either (a) Source side MME transfers the 1xRTT Reference Cell ID to the source side GMLC” TS 23.271 v11.3.0
  • “Either (a) Source side MME transfers the target side 1xRTT MSC address to the source side GMLC” TS 23.271 v11.3.0
  • “In the case of handover to 1xRTT, the Subscriber Location Report may convey the Reference Cell ID.” TS 23.271 v11.3.0
Rel-12 1 CR

GMLC gained a Diameter-based Lgd interface towards the SGSN and an optional Optimized Lgd feature that lets it send a single Provide Subscriber Location request to a combined MME/SGSN.

  • “Lgd is the interface that is used by the GMLC to convey a location request to the SGSN currently serving a particular target UE” TS 23.271 v12.1.0
  • “then the GMLC shall send only a single Provide Subscriber Location request to the combined MME/SGSN.” TS 23.271 v12.1.0
  • Introduction of Diameter interface between SGSN and GMLC (Lgd) TS 23.271CR0400
Rel-13 specification text

GMLC procedures gained delayed location reporting for UEs transiently not reachable: the GMLC indicates support in the request and acknowledges the Subscriber Location Report sent by SGSN or MME.

  • “If step 10a was executed, the GMLC shall acknowledge receipt of the Subscriber Location Report.” TS 23.271 v13.1.0
  • “the GMLC supports delayed location reporting for UEs transiently not reachable as indicated in step 2” TS 23.271 v13.1.0
  • “If step 9a was executed, the GMLC shall acknowledge receipt of the Subscriber Location Report.” TS 23.271 v13.1.0
Rel-14 specification text

GMLC behaviour in MT-LR procedures changed: it can indicate support of delayed location reporting, and the MME returns an ack or error depending on its own support.

  • “If the GMLC indicates support of delayed location reporting in step 2, and the MME does not support delayed location reporting” TS 23.271 v14.4.0
  • “the GMLC returns an LCS Service Response to the LCS Client by instigating steps 5, 6 and 7” TS 23.271 v14.4.0
Rel-15 2 CRs

The GMLC URI was added for Namf_Location EventNotify in NRF (29.510) and AMF (29.518) specifications, so the GMLC can receive location event notifications.

  • GMLC URI for Namf_Location EventNotify TS 29.510CR0140
  • GMLC URI for Namf_Location EventNotify TS 29.518CR149
Rel-16 1 CR

The 5GC GMLC is specified for the first time: it is the first node an external LCS client accesses, performs authorization and privacy checks, and exposes the Ngmlc service interface.

  • “A GMLC is the first node an external LCS client accesses in a PLMN (i.e. the Le reference point is supported by the GMLC).” TS 23.273 v16.13.0
  • “The Gateway Mobile Location Centre (GMLC) is the network entity in the 5G Core Network (5GC) supporting Location Services (LCS).” TS 29.515 v16.8.0
  • Addition of missing GMLC and its service TS 23.501CR1543
Rel-17 1 CR

GMLC behaviour was extended in Rel-17: it handles multiple QoS classes and scheduled location time, and it checks stored location timestamps. Its Ngmlc service also gained local location and integrity results.

  • “Multiple QoS Class (lcsQosClass sets to "MULTIPLE_QOS") shall only be used when GMLC support MUTIQOS feature.” TS 29.515 v17.10.0
  • “If a scheduled location time is not included and the requested type of location is "current or last known location"” TS 23.273 v17.11.0
  • Schedule location time for GMLC TS 29.515CR0072
Rel-18 specification text

GMLC gained new behaviour in Rel-18: it may select and provide the LMF ID to the AMF, and NWDAF and LMF became consumers of its Ngmlc services.

  • “The LMF selection functionality may also be supported by the GMLC and the GMLC provides the selected LMF ID to AMF.” TS 23.273 v18.12.0
  • “When the GMLC receives a MT location request from LCS client/AF, GMLC determines the LMF ID based on the configured parameters” TS 23.273 v18.12.0
  • “the GMLC offers services to the AMF, GMLC, NEF, NWDAF and LMF via the Ngmlc service based interface” TS 29.515 v18.8.0
Rel-19 specification text

In Rel-19 the GMLC gains new behaviour: it stores the NRPPa periodic indication, skips the privacy check on an MWAB indication, serves cached results to multiple emergency clients, and performs converged charging with the CHF.

  • “(H)GMLC stores NRPPa periodic indication.” TS 23.273 v19.7.0
  • “If the MWAB indication is received, the (H-)GMLC of the MWAB UE shall skip the privacy check based on the MWAB indication.” TS 29.515 v19.6.0
  • “The GMLC shall be able to perform converged charging by interacting with CHF, for charging data related to 5GS LCS.” TS 32.271 v19.2.0

Defining Specifications

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

SpecificationTitleRelease
TR 21.905 vj20 3GPP Terminology and Definitions Rel-19 read
TS 22.935 vd00 LCS Feasibility Study for 3GPP-WLAN Interworking Rel-13 read
TS 23.078 vj00 CAMEL Phase 4 Stage 2 Specification Rel-19 read
TS 23.127 v610 Virtual Home Environment Stage 2 Specification Rel-6 read
TS 23.141 vj00 Presence Service Stage 2 Architecture Rel-19 read
TS 23.171 v390 LCS Stage 2 for UMTS R99 read
TS 23.228 vk10 IP Multimedia Core Network Subsystem Rel-20 read
TS 23.271 vj00 LCS Stage 2 Specification Rel-19 read
TS 23.273 vj70 5G Location Services Architecture Stage 2 Rel-19 read
TS 23.501 vk30 5G System Architecture Rel-20 read
TS 23.700 vk10 AI/ML Application Layer Support Phase 2 Rel-20 read
TR 23.730 ve00 Study on extended CIoT architecture Rel-14 read
TS 24.571 vj50 5G NAS Location Services (LCS) Rel-19 read
TS 25.305 vj00 UTRAN UE Positioning Stage 2 Rel-19 read
TS 28.702 vj00 Core Network NRM IRP Information Service Rel-19 read
TS 29.060 vj00 GPRS Tunnelling Protocol (GTP) version 1 Rel-19 read
TS 29.172 vj00 EPC LCS Protocol (ELP) specification Rel-19 read
TS 29.199 3GPP TS 29.199 R99 read
TS 29.503 vk10 UDM Service Based Interface Rel-20 read
TS 29.515 vk10 Ngmlc Location Services API Rel-20 read
TS 29.520 vk10 5G NWDAF Services Rel-20 read
TS 29.522 vk10 NEF Northbound Interface Rel-20 read
TS 29.552 vk10 5G Network Data Analytics Procedures Rel-20 read
TS 29.574 vk10 DCCF Service Based Interface Rel-20 read
TS 29.575 vk10 ADRF Service Based Interface Rel-20 read
TS 29.591 vk10 NEF Southbound Services Rel-20 read
TS 29.810 vd00 Diameter Load Control Study Rel-13 read
TS 32.102 vj00 Telecom Management Physical Architecture Framework Rel-19 read
TS 32.240 vk10 3GPP Charging Architecture and Principles Rel-20 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 32.296 vj00 Online Charging System (OCS) Architecture Rel-19 read
TS 32.297 vj00 Charging Data Record File Transfer Rel-19 read
TS 32.632 vb00 Core Network Resources NRM Rel-11 read
TS 32.732 vb00 IMS Network Resource Model Information Service Rel-11 read
TS 33.814 vg01 Security aspects of enhanced Location Services (eLCS) Rel-16 read
TS 36.305 vj00 UE Positioning in E-UTRAN Stage 2 Rel-19 read
TS 38.305 vj30 NG-RAN UE Positioning Stage 2 Rel-19 read
TS 38.856 vg00 Study on local NR positioning in NG-RAN Rel-16 read