Mobile Location Center

Description

The Mobile Location Center (MLC) is a critical functional entity within the 3GPP Location Services (LCS) architecture. Its primary role is to determine the geographical location of a Mobile Station (MS) or User Equipment (UE) and to provide this location information to authorized clients, known as Location Based Service Clients (LCS Clients). The MLC is not a single physical node but a logical function that can be distributed; it is typically split into a Gateway MLC (GMLC) and a Serving MLC (SMLC). The GMLC acts as the interface between the mobile network and external LCS Clients. It handles authentication, authorization, and accounting for location requests, routes requests to the appropriate network (if the target UE is roaming), and delivers the final location estimate to the client. The SMLC, on the other hand, resides closer to the radio access network and is responsible for the actual positioning calculation. It selects the positioning method, collects the necessary measurement data from the UE and/or the network (e.g., base stations), and computes the location estimate.

The MLC operates through a series of standardized interfaces and protocols. The GMLC communicates with external clients via the Le interface, often using protocols like MLP (Mobile Location Protocol). Within the core network, the GMLC interacts with the HLR or HSS via the Lh interface to retrieve routing information (e.g., which MSC or MME is currently serving the target UE). It then forwards the location request to the appropriate MSC, SGSN, or MME via the Lg interface. The request is passed to the SMLC (via the Lb interface in GERAN, Iupc in UTRAN, or SLs in E-UTRAN). The SMLC orchestrates the positioning session. Depending on the method—such as Cell-ID, OTDOA (Observed Time Difference of Arrival), U-TDOA, or A-GPS—the SMLC instructs the UE and/or the radio network (e.g., BSC, RNC, eNB) to perform specific measurements. These measurements (e.g., timing advances, signal strengths, GPS pseudoranges) are reported back to the SMLC, which processes them using positioning algorithms to derive latitude, longitude, and accuracy estimates.

Key components within the MLC function include the Location Request Handler (in GMLC), the Positioning Function (in SMLC), and the Privacy Profile Register, which stores subscriber consent and privacy rules. The MLC's role extends beyond simple calculation; it is central to the entire LCS ecosystem. It ensures that location retrieval is secure, privacy-compliant, and efficient. It supports a variety of positioning methods to balance accuracy, response time, and network impact. For emergency services (e.g., E911, E112), the MLC works in a prioritized mode to provide rapid location information to the Public Safety Answering Point (PSAP). In commercial applications, it enables services like navigation, friend-finder, location-based advertising, and fleet tracking. The MLC's architecture has evolved to support seamless location services across 2G (GERAN), 3G (UTRAN), and 4G (E-UTRAN) access technologies.

Purpose & Motivation

The MLC was created to standardize and enable Location-Based Services (LBS) in mobile networks, a capability that became a regulatory requirement and a major commercial opportunity. Initially, the primary driver was emergency services; governments mandated that mobile networks must be able to provide the location of a caller making an emergency call (e.g., 911, 112). This public safety requirement necessitated a reliable, accurate, and network-integrated positioning system, which the MLC architecture provided. Before standardized LCS, any location service would have been a proprietary, non-interoperable solution, limiting its scalability and reliability for critical services.

Commercially, the rise of mobile data and smartphones created a vast market for location-enabled applications. The MLC solved the problem of how to expose the network's inherent ability to locate a device (via cell towers, etc.) to third-party service providers in a controlled, secure, and billable manner. It addressed key challenges: privacy (ensuring the subscriber's location is not disclosed without consent), security (authenticating clients), interoperability (working across different network vendors and generations), and accuracy (supporting multiple positioning techniques). The MLC separated the business logic and client interface (GMLC) from the radio-specific positioning technology (SMLC), allowing each to evolve independently. This modular design allowed operators to introduce new, more accurate positioning methods (like A-GPS) in the radio network without disrupting the service delivery to existing LCS clients.

Key Features

• Provides gateway functionality (GMLC) for external LCS client authentication, authorization, and request routing.
• Hosts the serving functionality (SMLC) for selecting positioning methods and calculating location estimates.
• Supports multiple positioning techniques (Cell-ID, OTDOA, U-TDOA, A-GPS) for varying accuracy needs.
• Enforces subscriber privacy policies and consent checks before disclosing location information.
• Interworks with core network elements (HLR/HSS, MSC, SGSN, MME) to locate roaming subscribers.
• Facilitates emergency services location (e.g., E911) with high priority and reliability.

Evolution Across Releases

Defining Specifications