BSSMAP

Base Station Subsystem Management Application Part

Protocol →
Introduced in Rel-4 Also in: Services

BSSMAP is a signaling protocol used between the Base Station Controller and Mobile Switching Center in GSM networks to manage radio resources, handover, and base station subsystem operations.

Category
Protocol
Introduced
Rel-4
Where
Radio Access Network › UTRAN (3G)
Also touches
1 segments
Specifications
9 specs
BSSMAP Description Purpose Related Classification Specifications

Description

BSSMAP (Base Station Subsystem Management Application Part) is a critical signaling protocol within the GSM architecture that operates between the Base Station Controller (BSC) in the Base Station Subsystem (BSS) and the Mobile Switching Center (MSC) in the Network Switching Subsystem (NSS). It functions as an application layer protocol that utilizes the underlying SCCP (Signaling Connection Control Part) transport mechanism over the A-interface. The protocol is responsible for managing the radio resources and coordinating mobility events, ensuring seamless communication between the radio access network and the core network switching functions.

Architecturally, BSSMAP messages are carried within SCCP connectionless or connection-oriented services depending on the specific procedure. The protocol defines numerous message types categorized into functional groups: radio resource management (including assignment, handover, and ciphering), mobility management (location updating and IMSI attach/detach), and operation and maintenance (BSS reset, overload control, and resource status reporting). Key components include the BSSMAP Service Access Point (BSAP) which provides the interface to the MSC's Call Control (CC) and Mobility Management (MM) entities, and various procedural elements that handle specific network functions like handover request, assignment, and paging.

BSSMAP operates through a well-defined set of procedures that coordinate activities between the BSC and MSC. For handovers, the MSC uses BSSMAP to request the target BSC to allocate resources and then commands the mobile station to switch to the new channel. For call setup, BSSMAP manages the assignment of traffic channels after the MSC receives the call request. The protocol also handles BSS management functions like reset procedures (when a BSC or MSC restarts), overload control (to prevent system congestion), and blocking/unblocking of radio resources. BSSMAP works in conjunction with the Direct Transfer Application Part (DTAP) which carries mobility management and call control messages transparently through the BSS between the mobile station and MSC.

In the overall network architecture, BSSMAP plays a pivotal role in separating radio-specific functions (managed by the BSC) from switching and service logic (managed by the MSC). This separation allows for independent evolution of radio access technologies while maintaining consistent core network interfaces. The protocol's design enables efficient resource utilization by allowing the MSC to make centralized decisions based on radio resource information provided by the BSC through BSSMAP messages. BSSMAP's comprehensive error handling and recovery mechanisms ensure network reliability during various failure scenarios.

Purpose & Motivation

BSSMAP was created to address the fundamental need for standardized signaling between the Base Station Subsystem (BSS) and Network Switching Subsystem (NSS) in GSM networks. Prior to GSM standardization, cellular systems often used proprietary interfaces between radio equipment and switching systems, which limited interoperability between equipment from different vendors and increased deployment costs. BSSMAP provided a standardized protocol that enabled multi-vendor interoperability while supporting the complex coordination required for mobility management and radio resource allocation in cellular networks.

The protocol specifically solves the problem of coordinating radio resource management decisions between the BSC (which has detailed knowledge of radio conditions and available channels) and the MSC (which manages call routing and subscriber services). Without BSSMAP, handovers between cells controlled by different BSCs would be extremely difficult to coordinate, and the MSC would lack visibility into radio resource availability when making call admission decisions. BSSMAP also addresses operational requirements by providing mechanisms for BSS maintenance, fault management, and overload control - essential functions for commercial network operations.

Historically, BSSMAP's creation was motivated by the GSM standardization effort's goal of creating a truly open, interoperable cellular system. By defining clear functional separation between the radio access network (BSS) and core network (NSS), with BSSMAP as the signaling interface, GSM enabled competition among infrastructure vendors while ensuring network reliability and service consistency. This architectural approach has influenced subsequent mobile generations, though BSSMAP itself is specific to GSM and early UMTS releases where it was adapted for the Iu-cs interface between RNC and MSC.

Classification

Part ofSCCP
Specific typesOVL
Related approachesDTAP

Evolution Across Releases

Rel-4 Initial

Introduced BSSMAP as part of the GSM Phase 2+ specifications, providing the initial protocol architecture for BSC-MSC signaling. Established core functions including handover management, assignment procedures, and BSS operation and maintenance capabilities. Defined the protocol's use of SCCP transport and message structures for all essential GSM mobility and resource management functions.

Explore further

Broader topics and technologies where BSSMAP plays a role.

Defining Specifications

3GPP specifications that define or reference BSSMAP, 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
TR 23.910 v1400 UMTS Circuit Switched Bearer Services Overview Rel-5
TS 25.410 vj00 Iu Interface Introduction for UTRAN Rel-19
TR 25.931 vj00 UTRAN Signalling Procedures Examples Rel-19
TS 43.318 vj00 Generic Access Network (GAN) Stage 2 Rel-19
TR 43.901 vj00 Generic Access to A/Gb Interface Feasibility Study Rel-19
TR 43.902 vj00 GAN Enhancements Feasibility Study Rel-19
TS 44.318 vj00 Generic Access Network (GAN) Interface Procedures Rel-19
TS 49.008 vj00 BSSAP on E-interface for inter-MSC handover Rel-19