BSSAP

Base Station Subsystem Application Part

Protocol →
Introduced in Rel-5

BSSAP is the signaling protocol used in GSM and UMTS networks to manage communication between the Base Station Subsystem and the Mobile Switching Center for functions like call setup and handover.

Category
Protocol
Introduced
Rel-5
Where
Management
Specifications
5 specs
BSSAP Description Purpose Related Classification Specifications

Description

The Base Station Subsystem Application Part (BSSAP) is a critical signaling protocol within the GSM and UMTS network architecture, operating over the A-interface between the Base Station Subsystem (BSS) and the Mobile Switching Center (MSC). It is part of the Signaling System No. 7 (SS7) protocol stack, specifically residing at the Application Layer (Layer 7) and utilizing the Signaling Connection Control Part (SCCP) for connection-oriented and connectionless services. BSSAP is responsible for conveying all application-specific signaling information required for managing radio resources and mobility between the MSC, which handles call control and switching, and the BSS, which manages the radio interface with mobile stations.

BSSAP is divided into two main sub-components: the Base Station Subsystem Management Application Part (BSSMAP) and the Direct Transfer Application Part (DTAP). BSSMAP handles messages that are processed by the BSS itself, such as those related to radio resource management, including handover requests, resource assignment, and paging. These messages are interpreted and acted upon by the Base Station Controller (BSC) within the BSS. In contrast, DTAP is used for the transparent transfer of messages between the MSC and the Mobile Station (MS), such as those for call control (e.g., setup, alerting, disconnect), mobility management (e.g., location updating, authentication), and session management. The BSS simply relays DTAP messages without interpreting their content, ensuring end-to-end signaling integrity between the core network and the subscriber device.

The protocol operates through a series of defined procedures and message flows. For instance, during a mobile-originated call, the MS sends a setup request via the radio interface to the BSS, which packages it into a DTAP message sent over BSSAP to the MSC. The MSC then processes the request, allocates resources, and may use BSSMAP to instruct the BSS to assign a traffic channel. Similarly, for handovers, BSSMAP facilitates the exchange of measurement reports and handover commands between the BSS and MSC to enable seamless transitions between cells. BSSAP's design ensures reliable, in-sequence delivery of signaling messages, supporting essential network functions like ciphering control, overload management, and equipment status reporting.

In the broader network architecture, BSSAP is a cornerstone for circuit-switched services, enabling interoperability between network elements from different vendors by standardizing the A-interface. It works in conjunction with other SS7 protocols like MTP (Message Transfer Part) and SCCP to provide routing and transport. While its primary domain is GSM, BSSAP also found use in UMTS for compatibility and inter-RAT (Radio Access Technology) operations, though 3GPP later introduced more advanced protocols like RANAP for the Iu interface in pure UMTS networks. Understanding BSSAP is key to grasping legacy network signaling, troubleshooting, and the evolution toward all-IP networks.

Purpose & Motivation

BSSAP was created to provide a standardized, reliable signaling mechanism between the Base Station Subsystem (BSS) and the Mobile Switching Center (MSC) in GSM networks, addressing the need for efficient management of radio resources and mobility in early digital cellular systems. Prior to its introduction, proprietary interfaces between base stations and switches hindered interoperability and multi-vendor deployments, increasing costs and complexity for operators. BSSAP, as part of the SS7-based signaling framework, solved this by defining a clear protocol stack on the A-interface, enabling seamless communication for call control, handover, and subscriber management.

The protocol was motivated by the requirements of circuit-switched voice and data services, where real-time coordination between the radio access and core network was essential. It allowed the MSC to delegate radio-specific tasks to the BSS while maintaining overall control, optimizing network performance and resource utilization. For example, BSSAP facilitated features like handover between cells, which was critical for maintaining call quality as users moved, and location updating, which supported roaming and service continuity. By separating BSSMAP (for BSS-level management) and DTAP (for transparent MS-MSC signaling), it provided a flexible architecture that could evolve with network enhancements.

Historically, BSSAP emerged with GSM standardization in the late 1980s and early 1990s, becoming a foundational element for 2G networks. It addressed limitations of analog systems, which lacked robust signaling for advanced mobility and security. As networks evolved to UMTS, BSSAP was retained for backward compatibility and interworking between GSM and UMTS, ensuring smooth transitions during technology migration. Its creation laid the groundwork for later signaling protocols in 3GPP, emphasizing the importance of standardized interfaces in telecommunications.

Classification

Part ofSCCP
Related approachesMSC

Evolution Across Releases

Rel-5 Initial

Introduced BSSAP as part of the GSM standards, defining the initial architecture for signaling between the Base Station Subsystem (BSS) and Mobile Switching Center (MSC). It established core capabilities including BSSMAP for radio resource management (e.g., handover, paging) and DTAP for transparent transfer of mobility and call control messages, enabling basic circuit-switched services and interoperability in 2G networks.

Explore further

Broader topics and technologies where BSSAP plays a role.

Defining Specifications

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

SpecificationTitleRelease
TR 21.905 vj00 3GPP Technical Terms and Definitions Rel-19
TS 32.401 vj00 Performance Management Concept & Requirements Rel-19
TR 43.901 vj00 Generic Access to A/Gb Interface Feasibility Study Rel-19
TS 49.008 vj00 BSSAP on E-interface for inter-MSC handover Rel-19
TS 52.402 vj00 GSM Performance Management Measurements Rel-19