Serving Base Station Subsystem

Description

The Serving Base Station Subsystem (SBSS) is a functional and architectural concept within 3GPP specifications that refers to the collective radio access network entities responsible for providing service to a specific Mobile Station (MS) or User Equipment (UE) during a connection. In the context of GSM and its evolution (GERAN), the SBSS consists of the Serving Base Station Controller (SBSC) and one or more Base Transceiver Stations (BTSs). In the context of UMTS and its UTRAN architecture, the analogous concept involves the Serving Radio Network Controller (SRNC) and its controlled Node Bs, though the term SBSS is more historically tied to GSM terminology.

The SBSS is not a single physical device but a logical grouping defined per subscriber session. Its composition is dynamic; for a mobile in a call or data session, the SBSS includes the BSC that is currently controlling the connection (the serving BSC) and the specific BTS (or BTSs, in the case of soft handover in later technologies) that is actively communicating with the mobile. The SBSC acts as the brain, performing radio resource management, handover decisions, and connection to the core network. The BTS(s) provide the physical radio interface, handling modulation, demodulation, and the transmission/reception of radio signals.

From a network signaling and mobility management perspective, the identity of the SBSS is crucial. The core network nodes, like the Mobile Switching Center (MSC) and Serving GPRS Support Node (SGSN), interact with the SBSS (via the SBSC) to manage the subscriber's session. During mobility events like handovers, the SBSS may change. For example, in an inter-BSC handover, the mobile's connection is transferred from one SBSS (the source SBSS) to another (the target SBSS). The SBSS is also central to location-based services and charging, as it identifies the geographical area where the subscriber is being served. In specifications, parameters like the Cell Global Identity (CGI) and the BSC identifier are part of defining the SBSS context for a user.

Purpose & Motivation

The concept of the Serving Base Station Subsystem was developed to provide a clear, standardized way for the core network to identify and interact with the specific set of radio equipment serving a mobile user. In early cellular systems, it was necessary to abstract the complexity of the radio access network for the core network switches. The MSC needed to know 'where' the subscriber was attached in the radio network to route calls and manage mobility, but it did not need to manage individual radio cells.

The SBSS serves as this abstraction layer. It solves the problem of correlating a subscriber's session with the controlling radio network element (BSC) and its resources. This is essential for functions like call setup (the MSC contacts the correct BSC to allocate a radio channel), handover coordination (signaling between MSCs and BSCs), and lawful interception. It also provides a scope for operational and maintenance functions, allowing network operators to track which subsystem is serving which users.

Its definition was motivated by the modular architecture of GSM, which cleanly separated the Base Station Subsystem (BSS) from the Network Switching Subsystem (NSS). The 'Serving' aspect highlights the dynamic, per-user nature of the association, which was a key advancement over fixed wireline networks. This conceptual model proved robust and was carried forward into 3G UMTS with the Serving RNC (SRNC) concept, ensuring consistent principles for mobility and session management across generations.

Key Features

• Logical grouping of serving radio network elements (BSC and BTSs) per user
• Dynamic entity that changes during subscriber mobility and handover
• Serves as the point of control and interface between the radio access and core network
• Identified by parameters like BSC ID and Cell Global Identity (CGI)
• Central to mobility management procedures (location updating, handover)
• Provides context for charging and lawful interception in the radio domain

Evolution Across Releases

Defining Specifications