Location System Control Function

Description

The Location System Control Function (LSCF) is a core logical component within the 3GPP standardized Location Services (LCS) architecture. It serves as the primary controller and coordinator for all location determination activities within a Public Land Mobile Network (PLMN). The LSCF receives location requests from various sources, authenticates and authorizes these requests, manages the positioning session with the relevant network elements, and finally returns the estimated location or a failure indication. Its functionality is critical for both regulatory services like emergency calling and commercial value-added services.

Architecturally, the LSCF sits at the heart of the LCS system. In earlier 3GPP releases, this function was often realized as part of the Gateway Mobile Location Centre (GMLC). The LSCF interfaces with several key entities: 1) The LCS Client (external application or network entity requesting location), 2) The Home Subscriber Server (HSS) or Home Location Register (HLR) for subscriber authorization and routing information, 3) The Mobile Switching Centre (MSC) or Mobility Management Entity (MME) in the core network to reach the target User Equipment (UE), and 4) The Serving Mobile Location Centre (SMLC) or Evolved Serving Mobile Location Centre (E-SMLC) in the radio access network, which performs the actual positioning calculations using measurements from the UE and/or base stations.

The operation of the LSCF follows a defined sequence. Upon receiving a location request, it first performs validation, checking the client's identity and the subscriber's privacy settings (LCS privacy profile) to ensure the request is permitted. It then queries the HSS/HLR to determine the UE's current serving node (MSC/MME). The LSCF forwards the request to this serving node, which in turn engages the appropriate positioning node (SMLC/E-SMLC) in the RAN. The LSCF manages this dialogue, potentially translating between different protocol stacks (e.g., from the external MLP protocol to internal RANAP or LPP/LPPa protocols). It receives the positioning measurements or final location estimate from the SMLC, may apply additional processing (like coordinate transformation), and then formats and returns the result to the requesting client.

Its role in the network is indispensable for enabling a wide range of location-based applications. For emergency services, the LSCF ensures that a caller's location is determined rapidly and reliably, often with network-initiated high-priority requests. For commercial services, it provides a secure, privacy-aware, and standardized gateway. The LSCF abstracts the complexities of the underlying radio access technology (be it GSM, UMTS, or LTE positioning methods) from the external client, presenting a uniform interface. This allows service providers to request location without needing detailed knowledge of the network topology or positioning techniques, thereby simplifying service development and deployment.

Purpose & Motivation

The LSCF was created to provide a standardized, centralized control point for location services within cellular networks. Before its standardization, location capabilities were often proprietary, vendor-specific solutions that were difficult to integrate with external applications and could not guarantee interoperability across multi-vendor networks or for roaming subscribers. The LSCF solves the fundamental problem of how to coordinate a complex, multi-step process involving core network entities, radio access network resources, and external clients in a consistent and secure manner.

Historically, the driver for LCS standardization—and thus the LSCF—was dual: regulatory mandates for emergency caller location and market demand for commercial location-based services. Regulators required a reliable, network-based mechanism to locate emergency callers. This necessitated a control function that could override normal procedures, prioritize resources, and interface with emergency service networks. Simultaneously, operators and third-party service providers sought a common API to build applications for navigation, asset tracking, and location-based information. The LSCF was designed to fulfill both roles, providing a single point of control that enforces privacy, performs authorization, and manages the technical session.

The motivation for its design was to separate the control logic from the positioning calculation itself. This modular architecture allows the positioning methods (handled by the SMLC/E-SMLC) to evolve independently with new radio technologies (e.g., from Cell-ID to OTDOA to NR positioning), while the control and service logic in the LSCF remains more stable. It addresses the limitations of earlier, monolithic systems by defining clear reference points (interfaces) between the LSCF and other network functions. This enables operators to source different components from different vendors and ensures that a subscriber can be located regardless of whether they are in their home network or roaming, as the visited network's LSCF (or a GMLC containing it) can handle the request.

Key Features

• Acts as the central controller and coordinator for all location service requests within a PLMN.
• Authenticates and authorizes location requests against subscriber privacy profiles and client privileges.
• Determines the UE's serving network node (MSC/MME/AMF) by querying the HSS/HLR/UDM.
• Orchestrates the positioning session with the RAN-based positioning node (SMLC/E-SMLC/LMF).
• Provides a standardized interface (e.g., via GMLC) for external LCS Clients to request location.
• Manages protocol translation between external application protocols (e.g., MLP) and internal network signaling protocols.

Evolution Across Releases

Defining Specifications