Description
BSSAP-LE (Base Station System Application Part Location Services Extension) is a critical protocol within the GSM architecture that extends the standard BSSAP protocol to support Location Services (LCS). It operates as an application layer protocol within the Base Station System (BSS) that enables communication between the Serving Mobile Location Center (SMLC) and the Base Station Controller (BSC) for mobile device positioning. The protocol is defined in 3GPP specifications 03.071 and 43.059, which detail the functional requirements and signaling procedures for location services in GSM networks.
The protocol architecture positions BSSAP-LE as an extension to the existing BSSAP protocol stack, utilizing the same underlying transport mechanisms while adding specialized messages and procedures for location services. It operates over the A-interface between the BSC and Mobile Switching Center (MSC), with the MSC acting as a routing point for location-related messages between the SMLC and BSC. The protocol defines specific message types for positioning requests, measurement reporting, and location result delivery, enabling precise coordination between network elements during positioning operations.
BSSAP-LE supports multiple positioning methods including Enhanced Observed Time Difference (E-OTD), Assisted GPS (A-GPS), and Cell-ID based positioning. The protocol handles the complete positioning transaction lifecycle, from initial location request to final location delivery. Key components include the BSSMAP-LE component for non-circuit related messages and the DTAP-LE component for direct transfer application part messages. The protocol manages timing synchronization, measurement collection, and positioning calculation coordination between network elements.
In operation, BSSAP-LE facilitates the exchange of positioning-related information between the SMLC (which manages positioning calculations) and the BSC (which controls radio resources and measurement collection). When a location request is initiated, BSSAP-LE messages coordinate the setup of positioning measurements, collection of timing information from multiple base stations, and delivery of calculated position estimates. The protocol includes error handling mechanisms, quality of service parameters for positioning accuracy, and support for both mobile-terminated and mobile-originated location requests.
The protocol's design ensures backward compatibility with existing BSSAP implementations while providing the specialized functionality needed for location services. It includes security features for authentication and authorization of location requests, particularly important for emergency services and lawful interception scenarios. BSSAP-LE represents a crucial evolution in GSM networks, enabling them to meet regulatory requirements for emergency caller location while supporting commercial location-based services.
Purpose & Motivation
BSSAP-LE was created to address the growing need for accurate mobile device positioning in GSM networks, driven by regulatory requirements for emergency services and commercial demand for location-based services. Prior to its introduction, GSM networks lacked standardized mechanisms for precise location determination, limiting their ability to support emergency caller location (E911/E112 requirements) and commercial location applications. The protocol solved the fundamental problem of coordinating positioning measurements and calculations across different network elements in a standardized way.
The development of BSSAP-LE was motivated by several key factors: regulatory mandates requiring network operators to provide accurate location information for emergency calls, commercial opportunities in location-based services, and the need for standardized interfaces between positioning system components. Before BSSAP-LE, proprietary solutions existed but lacked interoperability and scalability. The protocol provided a standardized way for the SMLC to communicate with the BSC, enabling consistent implementation across different vendor equipment.
Historically, the creation of BSSAP-LE in Release 7 represented a significant advancement in GSM network capabilities, allowing 2G networks to meet evolving location service requirements while maintaining compatibility with existing infrastructure. The protocol addressed limitations in earlier approaches by providing a comprehensive framework for all aspects of location service delivery, from measurement coordination to result delivery. It enabled GSM networks to support the same location service capabilities being developed for 3G networks, ensuring service continuity during network evolution.
What changed in its specifications
The latest release-to-release comparison of specifications that define BSSAP-LE. Each summary describes the whole specification, not only this term.
Added BDS support for LCS, new PS positioning procedures for A/Gb and Iu modes, and TA and U-TDOA steps.
Full comparison in TS 43.059 →Technology family
Location services architecture · Services
- R98 BSSAP-LE, BSSLAP, GMLC, LMU, RRLP, SMLC
- Rel-5 PCAP, SAS
- Rel-6 PPR, R-GMLC
- Rel-7 LRF, SUPL
- Rel-9 E-SMLC, LCS-AP, LPP, LPPa
- Rel-15 LMF, NRPPa
- 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
- BSSAP-LE used together with BSSLAP
“the BSC returns the current TA value and current serving cell for the target MS to the SMLC in a BSSLAP TA response contained within a BSSAP-LE Connection Oriented Information message.” TS 43.059
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 sourcesDocumented changes in 7 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.
Introduced in R98 (release dating of the term; no individual change cited).
TS 43.059 v4.7.0 first specifies BSSAP-LE Perform Location Request, Response and Abort between BSC and SMLC, carried over an SCCP connection for GSM location services.
- “The BSC sends the BSSAP-LE Perform Location Request to the SMLC inside an SCCP Connection Request message.” TS 43.059 v4.7.0
- “If the SMLC receives a BSSAP-LE Perform Location Abort indication for a previous location service request from the BSC, it shall immediately terminate” TS 43.059 v4.7.0
- “3GPP TS 49.031: Location Services (LCS); Base Station System Application Part LCS Extension (BSSAP-LE)” TS 43.059 v4.7.0
BSSAP-LE Perform Location procedures were extended to the PS domain, with the BSS sending Perform Location Request over SCCP and sending Perform Location Abort on cell change or radio loss.
- “The BSS establishes this connection when a request is received for a location estimate for a target MS in the PS domain.” TS 43.059 v5.5.0
- “it shall abort the positioning procedure by sending the BSSAP-LE Perform Location Abort to the SMLC.” TS 43.059 v5.5.0
- “The SMLC shall be notified with a BSSAP-LE Perform Location Abort if no BSSLAP procedure is currently active.” TS 43.059 v5.5.0
BSSAP-LE Perform Location Request usage was extended: BSS can include Timing Advance, Packet Measurement Report and LCS Capability, and completion handling now covers the BSSAP-LE Perform Location response for U-TDOA.
- “The BSS sends the BSSAP-LE Perform Location Request message to request the SMLC to start the positioning procedure.” TS 43.059 v6.6.0
- “The BSC considers the location determinations complete if; it receives a BSSAP-LE Perform Location response message; or the delta timer expires” TS 43.059 v6.6.0
- “Signaling between the SMLC and target MS, if required, is then relayed by the BSC between this SCCP connection and the main signaling link to the MS.” TS 43.059 v6.6.0
BSSAP-LE Perform Location Request now carries A-GNSS Assistance Data instead of GPS Assistance Data, and Perform Location Response may now include a velocity estimate.
- “A location estimate, velocity estimate, positioning data, deciphering keys, or LCS Cause may be included.” TS 43.059 v7.3.0
- “LCS Quality of Service, and A-GNSS Assistance Data.” TS 43.059 v7.3.0
The BSSAP-LE Perform Location Request description now says optional parameters depend on both the type of location request and the MS capability, rather than on the request type alone.
- “Depending on the type of location request and the MS capability, additional parameters may be included to provide Measurement Report” TS 43.059 v13.3.0
- “Depending on the type of location request, additional parameters may be included to provide Measurement Report” TS 43.059 v13.3.0
BSSAP-LE Connection Oriented and Connectionless Information messages were extended for multilateration positioning, including new parameters, forwarding via the MSC, and BSSLAP reject handling when the BSS cannot support the procedure.
- “The non-serving BSS sends the MSC a “BSSAP-LE Connectionless Information” message containing “Multilateration Timing Advance”” TS 43.059 v14.3.0
- “For the Multilateration based positioning methods, the BSC does not include an embedded BSSLAP message” TS 43.059 v14.3.0
- “the BSS cannot support the procedure it will send a BSSLAP reject message to the SMLC” TS 43.059 v14.3.0
Defining Specifications
3GPP specifications that define or reference BSSAP-LE, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 03.071 v890 | GSM Location Services Stage 2 | R99 read |
| TS 43.059 vj00 | GERAN LCS Stage 2 Specification | Rel-19 read |