Home Gateway Mobile Location Centre

Description

The Home Gateway Mobile Location Centre (HGMLC) is a central component of the 3GPP Location Services (LCS) architecture, defined as part of the control plane. It resides within the subscriber's Home Public Land Mobile Network (HPLMN). The HGMLC serves as the primary entry point for external Location Service Clients (LCS clients) requesting the location of a User Equipment (UE). Its fundamental role is to authorize and authenticate these external requests based on the client's identity and the subscriber's privacy settings, ensuring compliance with regulatory requirements like those for emergency services (e.g., E911) and lawful intercept.

Architecturally, the HGMLC interfaces with several network entities. It communicates with the Visited Gateway Mobile Location Centre (VGMLC) in a visited network when the target UE is roaming, using the Lh interface. For subscribers within its home network, it interacts with the Mobile Switching Centre (MSC) or Mobility Management Entity (MME)/Access and Mobility Management Function (AMF) via the Lg interface. The HGMLC also interfaces with the Home Subscriber Server (HSS) to retrieve subscriber data and routing information. The core protocol for these communications is the Mobile Application Part (MAP) for circuit-switched networks or Diameter for packet-switched networks, as specified in 3GPP TS 29.503.

The HGMLC's operation involves several key steps. Upon receiving a location request from an LCS client, it verifies the client's service authorization. It then checks the target subscriber's privacy profile, which defines who is permitted to locate the UE and under what conditions. If authorized, the HGMLC determines the UE's current serving node (e.g., MSC, SGSN, MME, AMF). If the UE is in its home network, the HGMLC forwards the location request directly to the appropriate node. If the UE is roaming, it routes the request to the VGMLC in the visited network. The HGMLC subsequently receives the location estimate (e.g., geographic coordinates) from the network and returns it to the requesting LCS client.

Its role extends beyond simple request routing. The HGMLC is responsible for billing correlation for location transactions, maintaining logs for auditing, and supporting deferred location requests (e.g., periodic or triggered location reporting). In the context of 5G, the HGMLC's functions are integrated into the Location Management Function (LMF) and Network Exposure Function (NEF) architecture, but the logical separation between home and visited network responsibilities remains a key concept for inter-operator and roaming scenarios.

Purpose & Motivation

The HGMLC was introduced to provide a standardized, secure, and scalable architecture for providing location services in mobile networks. Prior to its standardization, location services were often proprietary, limiting interoperability between network equipment vendors and between different operators' networks. The HGMLC addresses the need for a centralized, home-network-controlled entity to manage external access to subscriber location data, which is a highly sensitive resource.

The primary problems it solves are privacy, security, and inter-operator coordination. It enforces subscriber privacy policies, preventing unauthorized tracking. It provides a single, secure gateway for third-party LCS clients, simplifying network security policies. For roaming subscribers, it enables the home network to maintain control over location service authorization and billing, while delegating the location determination itself to the visited network's infrastructure via the VGMLC. This model is crucial for global roaming agreements.

Its creation was motivated by the growing demand for commercial location-based services (e.g., navigation, friend-finders) and stringent regulatory mandates for emergency caller location (E-911 in the US, E-112 in Europe). The HGMLC architecture allows operators to offer these services in a controlled, billable manner while protecting subscriber rights and meeting legal obligations for emergency service provisioning.

Key Features

• Acts as the primary gateway for external Location Service Clients (LCS clients) in the home network
• Enforces subscriber privacy verification and LCS client authorization
• Routes location requests to the appropriate network node (MSC, SGSN, MME, VGMLC)
• Supports inter-PLMN location services through interface with the Visited GMLC (VGMLC)
• Handles billing correlation and logging for location service transactions
• Facilitates both immediate and deferred (periodic/triggered) location reporting

Evolution Across Releases

Defining Specifications