H-GMLC (Home-Gateway Mobile Location Centre) in 3GPP

Description

The Home-Gateway Mobile Location Centre (H-GMLC) is a critical node in the 3GPP Location Services (LCS) architecture, standardized across multiple releases starting from Rel-8. It resides in the subscriber's Home Public Land Mobile Network (HPLMN) and serves as the first point of contact for any external entity (known as an LCS Client) requesting the geographic location of a mobile subscriber. The H-GMLC's primary functions include requestor authentication, privacy verification, and session management. Upon receiving a location request, it validates the LCS Client's credentials and checks the target subscriber's privacy settings stored in the Home Subscriber Server (HSS) to ensure the request is permitted. If authorized, the H-GMLC determines the current serving network of the target user. If the user is in the home network, the H-GMLC forwards the request directly to the local Gateway Mobile Location Centre (GMLC) or Serving Mobile Location Centre (SMLC). If the user is roaming, the H-GMLC routes the request to the appropriate Visited-GMLC (V-GMLC) in the Visited Public Land Mobile Network (VPLMN). The H-GMLC interfaces with the HSS via the Lh interface to retrieve routing information and subscriber privacy profiles. It communicates with other GMLCs (V-GMLC or local GMLC) using the Lr/Lg interfaces. The H-GMLC also handles the formatting and secure delivery of the final location estimate (e.g., latitude, longitude, accuracy) back to the requesting LCS Client. Its architecture is designed to centralize control and privacy management in the home network, ensuring consistent policy application regardless of where the subscriber is physically located.

Purpose & Motivation

The H-GMLC was introduced to provide a standardized, secure, and privacy-conscious gateway for obtaining the location of mobile subscribers, which became increasingly important with the rise of location-based services and regulatory mandates like Enhanced 911 (E911) in the US and eCall in Europe. Before its standardization, methods for locating users were often proprietary and lacked robust privacy controls, especially for roaming scenarios. The H-GMLC solves the problem of how an external application or service can reliably and securely request a user's location while respecting the user's privacy preferences and the operator's security policies. It centralizes the authorization function in the home network, where the subscriber's contract and privacy rules are held. This allows operators to maintain control over location data disclosure and to offer LCS as a billable service. Its creation enabled a wide range of applications, from emergency services (where the network must locate a caller automatically) to commercial services like fleet tracking, location-based advertising, and friend-finder applications, by providing a well-defined, interoperable interface between the mobile network and external service providers.

What changed in its specifications

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

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 →

TS 32.271Rel-13 → Rel-14

Updated normative references for AVPs in the Debit/Reserve Units Response message to 3GPP TS 32.299.

Full comparison in TS 32.271 →

Key Features

Primary entry point in HPLMN for external Location Service (LCS) requests
Authentication and authorization of LCS Clients (requestors)
Privacy check verification against subscriber profiles in the HSS
Routing of location requests to the correct network (home or visited)
Session management and coordination for location retrieval procedures
Secure delivery of location estimates to authorized requestors

Now in 3GPP

Next · 16–20 Nov15 working groups in Calgary, Calgary, Canada, Calgary, CA 2 Nov · DigestNGMN asks vendors to prove MRSS works on deployed 5G hardware before RAN#114 26 OctSA2#177 agrees interim 6G core principles but postpones the architecture choice to November 22 Oct · Meeting reportSA2#177 in Prague: 6G core principles agreed, architecture choice moved to November Quarterly · September 2026What 3GPP decided last quarter, by topic

All reports →

3GPP QuarterlyThe next issue by email, at most eight a year.

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

Standardization timeline: release of introduction not established; documented changes in 7 releases (latest: Rel-19). Each point is a change verified against specification text or change requests; releases without a point have no documented change. Active across the 3G → 4G → 5G eras.

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

TS 32.271 v620 first specifies H-GMLC roles in LCS charging, including privacy check, request forwarding to V-GMLC, and the LCS-HGMT-CDR produced for mobile terminated location requests.

“a LCS Home GMLC Mobile terminated Charging Data Record (LCS-HGMT-CDR) shall be produced for each mobile a terminated location request is performed via the H-GMLC” TS 32.271 v6.2.0
“The H-GMLC forwards the Location Service Request to the V-GMLC” TS 32.271 v6.2.0
“After the H-GMLC has performed privacy check, the associated LCS HGMT CDR is processed as specified in TS 32.297 [52]” TS 32.271 v6.2.0

Rel-9 specification text

The SLh interface specification (TS 29173) first defines how the HSS returns the H-GMLC address to the GMLC in routing info for LCS, including the related AVP and result handling.

“The SLh interface is used by the GMLC to request routing information from the HSS i.e. the address of the H-GMLC” TS 29.173 v9.4.0
“The HSS returns the address of the H-GMLC.” TS 29.173 v9.4.0
“This information element shall contain the IP address of the H-GMLC.” TS 29.173 v9.4.0

Rel-12 specification text

The H-GMLC address IE in the SLh Routing Info answer is now only 'should' be present on success, and the HSS handling of MSISDN-less subscriptions was added.

“This IE should be present if the Result-Code is DIAMETER_SUCCESS; otherwise it shall be absent.” TS 29.173 v12.3.0
“This IE shall be present only when the Result-Code is DIAMETER_SUCCESS.” TS 29.173 v12.3.0

Rel-16 specification text

The H-GMLC is specified for the first time in 5GC location services, with roles including combining concurrent location requests, resolving SIP-URI/TEL-URL to SUPI, deriving LCS client type, and selecting a VGMLC.

“the H-GMLC of the UE shall be able to convert the SIP-URI/TEL-URL into SUPI of the target UE.” TS 23.273 v16.13.0
“An H-GMLC or NEF may combine concurrent location requests (e.g. 5GC-MT LR, 5GC-MO LR, 5GC-NI LR) for the same target UE” TS 23.273 v16.13.0
“If step 1a is received, H-GMLC derives the LCS client type of the LCS client.” TS 23.273 v16.13.0

Rel-17 specification text

Text on the NEF deriving the LCS client type of the AF and providing it to the H-GMLC, and on the H-GMLC deriving the LCS client type itself, was removed in Rel-17.

“NEF derives the LCS client type of the AF, and provides it to H-GMLC.” TS 23.273 v17.11.0
“If step 1a is received, H-GMLC derives the LCS client type of the LCS client.” TS 23.273 v17.11.0

Rel-18 specification text

In Rel-18 the H-GMLC gains new responsibilities: verifying user plane reporting subscription, determining cumulative event report criteria, and receiving location determination directly from the LMF with a contact address in PNI-NPN.

“The H-GMLC verifies that both the target UE and the LCS Client or AF are subscribed to user plane reporting.” TS 23.273 v18.12.0
“the H-GMLC also includes a contact address (Notification Target Address, e.g. a URI) and a Notification Correlation ID” TS 23.273 v18.12.0
“support the transfer of cumulative event reports from the target UE via control plane back to the H-GMLC and LCS Client or AF” TS 23.273 v18.12.0

Rel-19 specification text

The (H-)GMLC now assigns an EPS LDR reference number and passes it with its address to the LMF to support 5GS-to-EPS continuity of deferred periodic/triggered location.

“the (H-)GMLC also assigns the EPS LDR reference Number and include the EPS LDR reference number and the H-GMLC address” TS 23.273 v19.7.0
“EPC-(H)GMLC sends LCS Service Response to 5GC-(H)GMLC and 5GC-(H)GMLC using the H-GMLC address.” TS 23.273 v19.7.0

Defining Specifications

3GPP specifications that define or reference H-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
TS 23.273 vj70	5G Location Services Architecture Stage 2	Rel-19 read
TS 29.503 vk10	UDM Service Based Interface	Rel-20 read