Location Management Server

Description

The Location Management Server (LMS) is a functional entity within the 3GPP Location Services (LCS) architecture, introduced as part of the broader evolution towards more flexible and service-based core networks. It is defined as a component that can be deployed within the 5G Core (5GC) or adapted for other architectures. The LMS centralizes the management of location-related data and logic that was previously more distributed among other Network Functions (NFs) like the Gateway Mobile Location Centre (GMLC). Its primary role is to store and handle location service subscriptions, user privacy settings (LCS Client authorizations), and subscriber location data or pointers to such data.

Architecturally, the LMS interacts with other core network functions via service-based interfaces (e.g., Nlmf interface). Key interactions include communication with the Access and Mobility Management Function (AMF) for obtaining location estimates from the access network, with the Unified Data Management (UDM) for subscriber data, and with external Location Service Clients (e.g., from a third-party application or an internal network service). The LMS may store permanent or temporary location information, geofencing definitions, and triggering events for periodic or event-driven location reporting. It implements the logic for evaluating location-based triggers and notifying authorized clients when conditions are met.

How it works: When a location request is received from an authorized LCS Client, the LMS validates the request against the target user's privacy profile. If authorized, it determines the appropriate method to obtain the location. This could involve querying the AMF, which in turn may initiate signaling with the Radio Access Network (RAN) and the UE (using protocols like LTE Positioning Protocol (LPP)) to generate a location estimate using GNSS, OTDOA, or other positioning methods. The LMS then formats and returns the location information to the requesting client. For deferred or triggered location requests, the LMS stores the trigger criteria and manages the ongoing monitoring, initiating location retrievals as needed and sending notifications. By centralizing this management, the LMS simplifies service logic, enhances scalability, and provides a unified point for applying privacy policies and service-level agreements for location information.

Purpose & Motivation

The LMS was created to address the growing complexity and demand for location-based services in mobile networks, which extended far beyond basic emergency caller location. Previous LCS architectures, centered on the GMLC, were often monolithic and tightly coupled with circuit-switched or early packet core elements. As networks evolved towards cloud-native, service-based architectures (SBA) with 5GC, there was a need to decompose functions for greater flexibility, scalability, and independent innovation. The LMS embodies this decomposition by extracting the location management, subscription, and privacy logic into a dedicated, scalable network function.

This separation solves several problems: it allows for more efficient handling of massive numbers of location requests from IoT devices and commercial applications; it provides a clear, standardized interface for application developers to access network location capabilities; and it centralizes the critical privacy control function, which is increasingly important due to regulations like GDPR. The creation of the LMS was motivated by use cases such as connected vehicles, asset tracking, location-based alerts, and enhanced emergency services (e.g., Advanced Mobile Location), which require reliable, low-latency, and policy-controlled access to device location. It enables network operators to offer location as a managed platform service with differentiated QoS and security levels, often in conjunction with network slicing for specific vertical industries.

Key Features

• Centralized management of location service subscriptions and user privacy settings (LCS privacy)
• Support for immediate, deferred, and triggered location request scenarios
• Interworking with various positioning methods (UE-based, UE-assisted, network-based) via the core network
• Service-based interface (e.g., Nlmf) for integration within 5G Core architecture
• Storage and processing of location data and geofencing triggers
• Authorization and policy enforcement for external and internal Location Service Clients

Evolution Across Releases

Defining Specifications