Menu
Latest
12 meetings · Prague, Jeju · 12–16 Oct
Reports
RAN1#126-bis · SA2#177

Glossary term · Protocol

LCS-AP

LCS Application Protocol

Protocol →

LCS-AP is the 3GPP control plane protocol used for communication between network entities to request and deliver location information for a target UE.

Introduced
Rel-9
Where
Radio Access Network › E-UTRAN (LTE)
Specifications
3 specs
LCS-AP Description Purpose What changed Family Neighbours Detected Changes Specifications

Description

The LCS Application Protocol (LCS-AP) is a critical control plane protocol within the 3GPP architecture, specifically designed to support Location Services (LCS). It operates over the SLg interface, connecting the Gateway Mobile Location Centre (GMLC) with the core network's mobility management entities—namely the Mobility Management Entity (MME) for LTE/EPC and the Serving GPRS Support Node (SGSN) for 2G/3G GPRS networks. The protocol defines a set of procedures and messages that allow the GMLC, which acts as the external interface for location requests, to communicate with the network nodes that can initiate and manage the location determination process for a User Equipment (UE).

Architecturally, LCS-AP is an application layer protocol that typically uses SCTP (Stream Control Transmission Protocol) as its transport layer for reliable message delivery. Its primary function is to convey location service requests from the GMLC to the MME/SGSN. Upon receiving a request, the MME/SGSN interacts with the Radio Access Network (RAN) and potentially the UE itself (e.g., for UE-based or UE-assisted positioning methods) to obtain location measurements or a calculated position. The protocol carries essential information such as the target UE's identifier (e.g., IMSI, MSISDN), the required Quality of Service (QoS) for the location estimate (like accuracy and response time), and the location event (e.g., immediate location, deferred location for periodic reporting).

The protocol supports various positioning methods, including network-based (e.g., Observed Time Difference of Arrival - OTDOA in LTE), UE-based (where the UE calculates its own position), and UE-assisted methods. LCS-AP messages are used to transfer the resulting location estimate (e.g., geographic coordinates) back to the GMLC, which then delivers it to the external LCS Client (e.g., an emergency services center or a commercial application server). The protocol also handles error conditions, subscriber privacy verification (checking if the LCS client is authorized to locate the subscriber), and supports deferred location reporting for tracking applications. Its role is strictly in the control plane, managing the signaling required to set up, execute, and tear down a location session without carrying the actual positioning measurement data, which is handled by other protocols in the user plane in later 3GPP releases.

Purpose & Motivation

LCS-AP was introduced to standardize the control signaling for Location Services across 3GPP networks, addressing the growing need for reliable and efficient mobile device positioning. Prior to its standardization, location services were often implemented using proprietary interfaces, which hindered interoperability between network equipment from different vendors and between different network operators. The creation of LCS-AP as part of the overall LCS architecture in 3GPP Release 9 provided a unified protocol for core network entities to communicate location requests and responses, which was essential for the commercial rollout of location-based services and for meeting regulatory mandates like Enhanced 911 (E911) in North America and its equivalents globally.

The protocol solves the problem of how an external entity (the LCS Client) can request the network to locate a subscriber's device in a standardized manner. It abstracts the complexities of the underlying radio access technology (e.g., UMTS, LTE) from the service layer. By defining clear primitives for location invocation, cancellation, and reporting, LCS-AP enables a wide range of services including emergency caller location, asset tracking, location-based charging, and friend-finder applications. Its development was motivated by the telecommunications industry's shift towards service-oriented architectures and the need to expose network capabilities like positioning through open, standardized interfaces to foster innovation in the application layer.

What changed in its specifications

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

TS 29.171Rel-13 → Rel-14

Rel-14 added RAT Type and Coverage Level information elements, new clauses, message tables, and ASN.1 definitions for extended CIoT architecture support.

Full comparison in TS 29.171 →
TS 36.305Rel-11 → Rel-12

Added BeiDou Navigation Satellite System (BDS) support for UTRA and LTE. Added GERAN and UTRAN measurement results to RF pattern matching positioning data transferred from eNodeB to E-SMLC.

Full comparison in TS 36.305 →

Technology family

Location services architecture · Services

  1. R98 BSSAP-LE, BSSLAP, GMLC, LMU, RRLP, SMLC
  2. Rel-5 PCAP, SAS
  3. Rel-6 PPR, R-GMLC
  4. Rel-7 LRF, SUPL
  5. Rel-9 E-SMLC, LCS-AP, LPP, LPPa
  6. Rel-15 LMF, NRPPa
  7. 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

Detected Changes Across Releases

verified against 3GPP sources

Documented changes in 6 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-9 introduced

LCS-AP is specified for the first time as the protocol on the SLs interface between MME and E-SMLC, with its procedures, transport (SCTP) and encoding defined in TS 29.171.

  • “The LCS-AP message set is applicable to the SLs interface between the E-SMLC and the MME.” TS 29.171 v9.4.0
  • “SCTP (see IETF RFC 4960 [4]) shall be supported as the transport layer of LCS-AP messages.” TS 29.171 v9.4.0
  • “LCS-AP shall use the ASN.1 Basic Packed Encoding Rules (BASIC-PER) Aligned Variant as transfer syntax” TS 29.171 v9.4.0
Rel-10 1 CR

LCS-AP PDUs carrying LPPa messages between E-SMLC and MME now include the Correlation ID corresponding to the UE, and CRs define LCS-AP message transfer syntax and protocol layering.

  • “The E-SMLC then sends an LCS-AP PDU (as specified in [27]) to the MME including the Correlation ID corresponding to the UE” TS 36.305 v10.5.0
  • “in an LCS-AP PDU (as specified in [27]) including the Correlation ID corresponding to the UE.” TS 36.305 v10.5.0
  • Define message transfer syntax in LCS-AP TS 29.171CR0006
Rel-11 specification text

LCS-AP Reset Request now carries an LCS Cause parameter, and reset and Location Response handling is tied to the SCTP association used for the request.

  • “The message contains a LCS Cause parameter indicating the reason for the reset.” TS 29.171 v11.4.0
  • “shall then return a LCS-AP Reset Acknowledge message using the same SCTP association as the Reset Request.” TS 29.171 v11.4.0
  • “the E-SMLC shall return a LCS-AP Location Response to the initiator of the location request using the same SCTP association” TS 29.171 v11.4.0
Rel-13 1 CR

LCS-AP was extended in Rel-13 with support for indoor positioning, as shown by the added text and an approved CR on 29.171.

Rel-14 1 CR

LCS-AP location request handling was extended so the MME sends the request to the E-SMLC for the current or last known serving cell, and the E-SMLC can return a last known location estimate.

  • “sends a LCS-AP Location Request message to the E-SMLC associated with the current or last known serving cell for the target UE” TS 29.171 v14.3.0
  • “if a last known location estimate is requested, the E-SMLC obtains a geographic location estimate using only the information provided in the LCS-AP Location Request message” TS 29.171 v14.3.0
  • LCS-AP corrections TS 29.171CR0039
Rel-15 specification text

LCS-AP gained new Ciphering Key Data and Ciphering Key Data Result messages, used by the E-SMLC to give ciphering keys with validity time and area to the MME.

  • “7.3.8 LCS-AP Ciphering Key Data message” TS 29.171 v15.5.1
  • “7.3.9 LCS-AP Ciphering Key Data Result message” TS 29.171 v15.5.1
  • “The MME returns a LCS-AP Ciphering Key Data Result message back to the E-SMLC indicating whether the MME was able to successfully store the ciphering data sets.” TS 36.305 v15.6.0

Defining Specifications

3GPP specifications that define or reference LCS-AP, with the latest known release. Sourced from the 3GPP document catalog — see methodology.

SpecificationTitleRelease
TS 29.171 vj10 LCS-AP between MME and E-SMLC (SLs) Rel-19 read
TS 36.305 vj00 UE Positioning in E-UTRAN Stage 2 Rel-19 read
TS 37.857 vd10 Indoor Positioning Enhancements for UTRA and LTE Rel-13 read