Description
The Base Station System Application Part (BSSLAP) is a critical signaling protocol defined within the 3GPP standards for GSM and early UMTS networks, specifically for Location Services (LCS). It operates as an application-layer protocol over the Base Station System Application Part (BSSAP) protocol stack, facilitating communication between the Serving Mobile Location Centre (SMLC) and the Base Station Controller (BSC). The SMLC is the network node responsible for computing the location of a mobile station (MS), while the BSC manages radio resources and controls multiple Base Transceiver Stations (BTSs). BSSLAP provides the dedicated messaging necessary for the SMLC to request and receive measurement data from the BSC and BTSs, which is essential for performing positioning calculations.
Architecturally, BSSLAP messages are transported via the BSSAP protocol, which itself uses the Signaling Connection Control Part (SCCP) over the A-interface (between MSC and BSC) or the Iu-interface in UMTS. However, BSSLAP specifically defines the point-to-point signaling between the SMLC and BSC for location-specific procedures. The protocol supports various positioning methods, with its primary design focused on the Enhanced Observed Time Difference (E-OTD) method. In E-OTD, the mobile station measures the observed time differences of arrival of signals from multiple geographically dispersed BTSs. The BSC, via BSSLAP, collects these measurements from the MS and forwards them to the SMLC. The SMLC then uses this data, along with known BTS location coordinates and timing information, to triangulate the MS's position.
Key components of BSSLAP include message types for location measurement requests, responses, and abort procedures. For instance, the SMLC sends a BSSLAP Connection Oriented Information message to the BSC to initiate a positioning request, specifying parameters like the required Quality of Service (QoS) for accuracy. The BSC then coordinates with the MS and BTSs to gather the necessary radio measurements, such as timing advances or observed time differences. These measurements are encapsulated in BSSLAP messages and sent back to the SMLC. The protocol also handles error conditions and resource management, ensuring that positioning requests do not unduly impact normal voice and data services. BSSLAP's role is integral to enabling network-based and mobile-assisted positioning, providing the foundational signaling for emergency services, location-based services, and lawful interception in 2G and early 3G networks.
In operation, BSSLAP works in conjunction with other LCS protocols like the Radio Resource LCS Protocol (RRLP) and the Mobile Application Part (MAP). While RRLP handles signaling between the MS and SMLC over the radio interface, BSSLAP manages the fixed-network signaling between SMLC and BSC. This separation allows for efficient distribution of processing: the BSC handles radio resource coordination, while the SMLC performs the complex location calculations. BSSLAP messages are typically small and infrequent, optimized to minimize signaling load. The protocol includes features for ciphering indication and support for various positioning methods, though its capabilities are more limited compared to later protocols like the LTE Positioning Protocol (LPP) in 4G networks. Despite its age, understanding BSSLAP is important for legacy network maintenance and for comprehending the evolution of mobile positioning technologies.
Purpose & Motivation
BSSLAP was created to address the growing need for accurate mobile device location determination in GSM networks, driven primarily by regulatory requirements for emergency services (e.g., E911 in the United States) and the commercial demand for location-based services (LBS). Prior to its introduction, GSM networks lacked a standardized, efficient signaling mechanism between the network entities responsible for positioning. Early location methods were rudimentary, often relying on Cell-ID (which provides only the serving cell area) or required proprietary implementations that hindered interoperability between equipment from different vendors. BSSLAP provided a standardized protocol within the 3GPP framework, enabling consistent and reliable communication between the SMLC and BSC for advanced positioning techniques like E-OTD.
The protocol solved key technical problems by defining a clear interface for requesting and delivering radio measurement data necessary for triangulation-based positioning. Without BSSLAP, the SMLC would have no standardized way to instruct the BSC to collect specific timing measurements from the mobile station and base stations, nor to receive that data in a structured format. This standardization was crucial for network operators deploying multi-vendor networks, as it ensured that location services could work seamlessly across different BSC and SMLC implementations. BSSLAP also helped optimize network resources by allowing the SMLC to specify positioning QoS parameters, so the BSC could prioritize location requests appropriately without disrupting voice calls or other services.
Historically, BSSLAP's development in 3GPP Release 7 (though based on earlier GSM specifications) coincided with the maturation of GSM networks and the initial rollout of UMTS. It represented a significant step forward from basic Cell-ID location, enabling more accurate positioning (typically within 50-150 meters for E-OTD) needed for emergency response and commercial applications like navigation and asset tracking. While later technologies like U-TDOA (Uplink Time Difference of Arrival) and GNSS-assisted methods eventually offered better accuracy, BSSLAP laid the groundwork for network-based positioning architectures. Its creation was motivated by the limitations of prior ad-hoc approaches, providing a scalable, standards-based solution that supported the regulatory and commercial imperatives of the early 2000s mobile industry.
What changed in its specifications
The latest release-to-release comparison of specifications that define BSSLAP. 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
- BSSLAP used together with BSSAP-LE
“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 8 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).
The BSC's Reject for a BSSLAP TOA Command is now sent in a "BSSMAP Connection Oriented Information" message instead of a "BSSMAP Location Information Report" when TOA positioning cannot be performed.
- “a Reject will be sent with proper cause value from BSC to SMLC in "BSSMAP Connection Oriented Information"” TS 03.071 v8.9.0
- “a Reject will be sent with proper cause value from BSC to SMLC in "BSSMAP Location Information Report"” TS 03.071 v8.9.0
TS 43.059 v4.7.0 specifies BSSLAP use between SMLC and BSC: carried in BSSAP-LE messages over SCCP, with MS Position Command/Response, segmentation, and Reject/Abort/Reset handling.
- “The same SCCP connection is also used to transfer BSSLAP messages between the SMLC and serving BSC.” TS 43.059 v4.7.0
- “If the request is rejected, the BSC shall return a BSSLAP Reject to the SMLC containing the cause of rejection.” TS 43.059 v4.7.0
- “The SMLC passes a BSSAP-LE Connection Oriented Information message to the serving BSC containing an embedded BSSLAP MS Position Command” TS 43.059 v4.7.0
RRLP pseudo-segmentation is now required when a BSSLAP message is too large, with BSSAP-LE layer segmentation allowed only for legacy SMLCs; BSSLAP positioning is also added for the PS domain via the SGSN.
- “RRLP pseudo‑segmentation shall be used. Legacy SMLC may utilize BSSAP-LE layer segmentation instead of RRLP pseudo-segmentation.” TS 43.059 v5.5.0
- “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
BSSLAP gained U-TDOA messages (Request, Response, Reset, Reject, Abort) and BSC handling of them, including delta timer supervision and RR procedure treatment, plus use in PS domain location.
- “There are three (3) BSSLAP messages defined to handle error scenarios that occur during the U-TDOA location process: Reset, Reject and Abort.” TS 43.059 v6.6.0
- “If the BSC receives the BSSLAP U-TDOA Request message during one of the identified RR procedures in Table 9.5.1, it will complete the ongoing RR procedure” TS 43.059 v6.6.0
- “it will respond to the BSSLAP U-TDOA Request message with the BSSLAP Reject message.” TS 43.059 v6.6.0
BSSLAP Abort handling now allows the SMLC to return a location estimate with an optional velocity estimate, and the RRLP request case now covers A-GNSS instead of GPS.
- “return any location estimate (with optional velocity estimate) already derived” TS 43.059 v7.3.0
- “When the RRLP request comes to BSC for E-OTD and A-GNSS” TS 43.059 v7.3.0
The BSSLAP U-TDOA Response message now also carries the intended Power-Up Starting Time when the power-up procedure for U-TDOA is supported.
- “the intended Power-Up Starting Time (if the power-up procedure for U-TDOA is supported)” TS 43.059 v8.1.0
BSSLAP usage was extended for Multilateration positioning: the BSC omits embedded BSSLAP in info messages, the SMLC sends a BSSLAP MS Position Command, and the BSS returns BSSLAP Reject or Abort.
- “embedded BSSLAP MS Position Command with an RRLP message parameter including the RRLP Positioning Multilateration Timing Advance Request 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
- “the BSS shall send a BSSLAP Abort to the SMLC” TS 43.059 v14.3.0
Defining Specifications
3GPP specifications that define or reference BSSLAP, 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 |