Base Station System Application Part

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.

Key Features

• Standardized signaling between SMLC and BSC for location services
• Support for Enhanced Observed Time Difference (E-OTD) positioning method
• Transport over BSSAP protocol stack using SCCP connections
• Definition of message types for measurement requests, responses, and abort procedures
• Inclusion of Quality of Service (QoS) parameters for positioning accuracy
• Handling of ciphering indications and error conditions

Evolution Across Releases

Defining Specifications