Description
The Base Station Subsystem (BSS) is a critical architectural component within the GSM system, forming the entirety of the 2G radio access network (RAN). Its primary function is to manage all radio-related aspects of communication between mobile stations (MS) and the core network. The BSS is physically and logically divided into two main elements: the Base Transceiver Station (BTS) and the Base Station Controller (BSC). The BTS, often referred to as a cell site or base station, contains the radio transceivers, antennas, and signal processing equipment that define a radio cell. It performs modulation/demodulation, channel coding/decoding, encryption/decryption for the air interface (the Um interface), and handles the physical layer transmission and reception.
The Base Station Controller (BSC) is the intelligent control node for one or more BTSs. It manages radio resources (RR) for its associated cells, including the allocation and release of radio channels (timeslots and frequencies). The BSC is responsible for critical mobility management functions such as handover initiation and execution between cells under its control (intra-BSC handover) and measurement reporting from the MS. It also performs power control to optimize signal quality and minimize interference, and it concentrates and routes traffic and signaling between the BTSs and the core network's Mobile Switching Center (MSC) via the A interface.
Operationally, the BSS works by the BTS continuously broadcasting system information on broadcast control channels. When a mobile station requests a connection, the BTS relays the request to the BSC. The BSC then authenticates the request with the core network, allocates a traffic channel (TCH) or signaling channel via the BTS, and manages the ongoing call or data session. For mobility, the BSC receives measurement reports from the MS via the BTS, evaluates signal strength and quality from neighboring cells, and decides when to execute a handover, either within its own pool of BTSs or by coordinating with another BSC or the MSC.
The BSS interfaces are well-defined: the Um interface is the air interface to the MS; the Abis interface is the internal, often proprietary, interface between the BTS and BSC; and the A interface is the standardized interface connecting the BSC to the MSC in the core network. This clear separation of radio transmission (BTS) and control/management (BSC) allowed for scalable and efficient network deployment. The BSS's architecture and principles of centralized radio resource control directly influenced the design of later 3GPP RANs, such as the UMTS Radio Network Subsystem (RNS) with its Node B and RNC.
Purpose & Motivation
The BSS was created to provide the standardized radio access network for the GSM digital cellular system, which was developed in the 1980s to replace analog first-generation (1G) networks. Its primary purpose was to solve the problems of limited capacity, poor voice quality, lack of security, and incompatibility between national systems that plagued 1G networks. By defining a digital, circuit-switched access subsystem with centralized control, GSM and its BSS enabled secure, high-quality voice services, international roaming, and vastly improved spectral efficiency.
The architectural separation into BTS and BSC addressed key operational and economic challenges. Placing the relatively simple, radio-focused BTS at the cell site allowed for cost-effective deployment and maintenance. Centralizing the intelligence and control functions in the BSC enabled efficient management of radio resources across multiple cells, sophisticated handover algorithms, and traffic concentration, which reduced transmission costs back to the core network. This division of labor was a foundational concept for cellular network design.
Furthermore, the standardization of the A interface between the BSS and the core network was a revolutionary step. It decoupled the RAN from the core network, allowing equipment from different vendors to interoperate. This broke vendor lock-in, fostered competition, and accelerated the global deployment and success of GSM. The BSS thus provided the reliable, scalable, and standardized radio access layer that made GSM the world's dominant 2G technology.
What changed in its specifications
The latest release-to-release comparison of specifications that define BSS. Each summary describes the whole specification, not only this term.
Rel-18 brings only minor changes to TS 21.905: 0 clauses changed, with no change attributed to a release feature.
Full comparison in TR 21.905 →Rel-19 brings only minor changes to TS 23.009: 0 clauses changed, with no change attributed to a release feature.
Full comparison in TS 23.009 →Technology family
Base stations and RAN nodes · Radio Access Network
- Phase 1 BSC, BSS, BTS
- R99 Node B, RNC, RNS
- Rel-8 eNB, HeNB, HNB, HNB-GW
- Rel-10 DeNB, HeNB-GW, RN
- Rel-15 en-gNB, gNB, gNB-CU, gNB-CU-CP, gNB-CU-UP, gNB-DU, ng-eNB
- Rel-16 IAB-donor, IAB-DU, IAB-MT, IAB-node
- Rel-18 Mobile IAB-node
- BSS decomposed into BSC
“the BSS consists of one Base Station Controller (BSC) and one or more Base Transceiver Station (BTS)” TS 23.002
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 13 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 Phase 1 (release dating of the term; no individual change cited).
TS 48.018 and TS 51.021 first appear in this release, specifying BSS behaviour: BSSGP procedures with the SGSN, BSS packet flow contexts, and BSS radio test requirements.
- “the BSS may send a DOWNLOAD-BSS-PFC PDU to an SGSN.” TS 48.018 v4.7.0
- “The required procedures between BSS and SGSN are defined in detail in the present document.” TS 48.018 v4.7.0
- “The Manufacturer shall declare whether the BSS supports Slow Frequency Hopping (SFH)” TS 51.021 v4.7.0
BSSGP (48.018) gained BSS behaviour: a fourth pre-defined packet flow (TOM8), per-PFC flow control, and BSS-initiated PFC create, modify and delete procedures.
- “There are four pre-defined packet flows identified by four reserved packet flow identifier values.” TS 48.018 v5.14.0
- “If the PFC Flow Control feature is negotiated, the BSS may control the flow of BSSGP UNITDATA PDUs” TS 48.018 v5.14.0
- “The BSS may request modification of the contents of an existing BSS PFC at any time via the MODIFY-BSS-PFC PDU” TS 48.018 v5.14.0
BSS behaviour on the Gb interface changed: it handles MBMS service contexts and uplink MBMS signalling, and it follows revised PFC download, create and ARP-based resource handling procedures.
- “The SGSN can provide a BSS with information related to ongoing MBMS user data transmission.” TS 48.018 v6.20.0
- “The BSS shall provide the TMGI and, if present in the MBMS Service Context, the MBMS Session Identity to the SGSN” TS 48.018 v6.20.0
- “The BSS shall consider the priority level of the requested PFC, when deciding on the resource allocation.” TS 48.018 v6.20.0
BSS behaviour changed: it now sends Reliable INTER RAT HANDOVER INFO in PS Handover Required, requests handover info on completion, and handles DTM Handover procedures towards the SGSN.
- “When a BSS initiates a PS handover or DTM Handover it shall initiate the PS Handover Required procedure and send the PS-HANDOVER-REQUIRED PDU to the SGSN.” TS 48.018 v7.13.0
- “The source BSS should always include the ‘Reliable INTER RAT HANDOVER INFO’ indicator set to ‘1’ in the PS Handover Required message” TS 43.129 v7.3.0
- “For DTM Handover to UTRAN, the source BSS shall set the Number of Iu Instances IE equal to 2” TS 48.018 v7.13.0
BSS gained new behaviour in Rel-8: PS handover to E-UTRAN with new container IEs, and a new 'BSS Internal Handover with MSC Support' procedure for A-interface over IP.
- “If PS handover to E-UTRAN is required, the source BSS shall include the Source to Target Transparent Container IE and the Target eNB Identifier IE” TS 48.018 v8.11.0
- “then it shall generate and send an A-INTERNAL-HANDOVER-COMMAND message to the BSS and stop timer T105.” TS 23.009 v8.3.0
- “If AoIP is supported by MSC-A and BSS, then the BSS or the MSC-A may initiate a "BSS Internal Handover with MSC Support"” TS 23.009 v8.3.0
Rel-9 adds BSS behaviour for PS handover to UTRAN CSG or hybrid cells, including the CSG Identifier IE and Cell Access Mode, and handles the SON Transfer Application Identity IE in RIM error PDUs.
- “If PS handover to a UTRAN CSG cell or hybrid cell is required, the source BSS shall include the Source to Target Transparent Container IE, Target RNC Identifier IE and the CSG Identifier IE” TS 48.018 v9.10.0
- “or if the RIM container contains an unknown value in the SON Transfer Application Identity IE in case the RIM Application Identity IE is set to "SON Transfer"” TS 48.018 v9.10.0
BSS gained MOCN rerouting behaviour on the Gb interface: it selects an SGSN, initiates rerouting, handles Redirection Indication and Completed IEs, and the RIM procedure for SON Transfer containers was generalised.
- “BSS shall choose a SGSN and initiate a rerouting procedure.” TS 48.018 v10.12.0
- “Upon reception of the downlink Redirection Completed IE, the BSS shall send back the included LLC-PDU to the MS and terminate the Rerouting procedure.” TS 48.018 v10.12.0
- “The BSS shall not initiate the PS handover required procedure in the case of an MOCN configuration if the Rerouting procedure is ongoing.” TS 48.018 v10.12.0
BSS behaviour in the Gb interface (TS 48.018) was extended: it handles SCI and GGSN/P-GW location IEs, includes the selected PLMN ID for network sharing, and must not initiate PS handover required during CS to PS SRVCC.
- “The BSS uses the Home PLMN ID contained within the IMSI and the GGSN/P-GW location information to determine whether or not it can handle the SCI information” TS 48.018 v11.8.0
- “The BSS shall not initiate the PS handover required procedure in case CS to PS SRVCC from GERAN to UTRAN or to E-UTRAN [25] is ongoing.” TS 48.018 v11.8.0
- “then the BSS shall assume that the GGSN/P-GW is located in the VPLMN” TS 48.018 v11.8.0
RIM procedures in TS 48.018 were extended so BSS exchanges information with eHRPD eAN via the S121 interface, and BSS-related conformance requirements added ER-GSM 900 band support.
- “The RIM PDUs shall be conveyed transparently by the core network toward the destination BSS, RNS, eNodeB or eHRPD eAN.” TS 48.018 v12.4.0
- “a BSS may support DCS 1800, GSM 450, GSM 480, PCS 1900, MXM 1900, GSM 850, MXM 850, GSM 700, T-GSM 810, ER-GSM 900” TS 51.021 v12.3.0
- “the term "BSS" should be understood as "RNC, eNodeB or eAN" in the relevant situations” TS 48.018 v12.4.0
BSS behaviour changed: it handles EC-GSM-IoT in UL-UNITDATA, supports CS/PS coordination enhancements in rerouting for network sharing, and is covered by new EC-GSM-IoT conformance requirements.
- “If EC-GSM-IoT is supported by the BSS and the SGSN, then the BSS shall provide in the UL-UNITDATA PDU:” TS 48.018 v13.6.0
- “then the BSS shall initiate the MS Registration Enquiry procedure in the CS domain (see [14]);” TS 48.018 v13.6.0
- “If the BSS supports EC-GSM-IoT, the measured equivalent combined power shall exceed the maximum GMSK output power declared by the manufacturer” TS 51.021 v13.9.0
BSS behaviour in TS 48.018 changed: it now selects a DCN and reroutes uplink LLC PDUs with a Redirect Attempt Flag, and handles multilateration positioning requests with extra timing information.
- “the BSS selects an available SGSN and adds the Redirect Attempt Flag IE to the UL-UNITDATA message used to forward the uplink LLC PDU” TS 48.018 v14.5.0
- “The BSS selects a DCN for the selected PLMN based on DCN-ID information received from the MS and configuration information” TS 48.018 v14.5.0
- “the BSS sends a positioning request to the SMLC, includes the “MultilaterationTiming Advance”, “MS Sync Accuracy” and “BTS Reception Accuracy Level” information elements therein” TS 48.018 v14.5.0
BSS gains new behaviour in Rel-15: triggering EC-PICH paging indications for CC3/CC4 MSs and handling MTA Access Security, including forwarding SMLC-provided signature and sequence to the SGSN.
- “the BSS triggers for cells in the area targeted for paging and broadcasting the support of EC-PICH, the sending of a paging indication in the EC-PICH block” TS 48.018 v15.0.0
- “BSS upon receipt of this IE shall request SMLC to perform the location request.” TS 48.018 v15.0.0
- “This parameter is provided by BSS to SGSN. The BSS obtains this parameter from SMLC.” TS 48.018 v15.0.0
Defining Specifications
3GPP specifications that define or reference BSS, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TR 21.905 vj20 | 3GPP Terminology and Definitions | Rel-19 read |
| TS 22.100 v370 | UMTS Service Requirements for Release '99 | R99 read |
| TR 22.945 v300 | Fax Services Guidance for GSM/UMTS | R99 read |
| TS 23.009 vj00 | Handover Procedures in PLMNs | Rel-19 read |
| TS 23.050 | 3GPP TS 23.050 | R99 read |
| TS 23.171 v390 | LCS Stage 2 for UMTS | R99 read |
| TS 23.271 vj00 | LCS Stage 2 Specification | Rel-19 read |
| TR 23.923 v300 | Mobile IP+ Feasibility Study for UMTS/GPRS | R99 read |
| TS 25.222 vj00 | UTRA TDD Multiplexing & Channel Coding | Rel-19 read |
| TS 25.304 vj10 | UE Idle Mode Procedures | Rel-19 read |
| TS 25.331 vj01 | UTRAN Radio Resource Control Protocol | Rel-19 read |
| TS 25.401 vj00 | UTRAN Overall Architecture | Rel-19 read |
| TS 25.420 vj00 | Iur Interface Introduction for UTRAN | Rel-19 read |
| TS 25.423 vj00 | UTRAN RNSAP Specification | Rel-19 read |
| TR 25.931 vj00 | UTRAN Signalling Procedures Examples | Rel-19 read |
| TS 26.093 vj00 | SCR operation of AMR codec for UMTS | Rel-19 read |
| TS 26.193 vj00 | AMR-WB Source Controlled Rate (SCR) Operation | Rel-19 read |
| TS 28.062 vj00 | Tandem Free Operation (TFO) Service Description | Rel-19 read |
| TS 28.661 vj00 | Generic RAN NRM IRP Requirements | Rel-19 read |
| TS 28.662 vj20 | Generic RAN Network Resource Model (NRM) | Rel-19 read |
| TR 28.824 vi01 | Technical Report on Network Slice Capability Exposure | Rel-18 read |
| TS 28.849 vj10 | CAPIF Phase2 Charging Study | Rel-19 read |
| TR 28.925 vj00 | Enhancement of Service Based Management Architecture | Rel-19 read |
| TR 31.900 vj00 | 3GPP TS 31.900: Security Interworking Guidance | Rel-19 read |
| TS 32.102 vj00 | Telecom Management Physical Architecture Framework | Rel-19 read |
| TS 32.111 vj00 | Fault Management Alarm IRP Solution Sets | Rel-19 read |
| TS 32.240 vk10 | 3GPP Charging Architecture and Principles | Rel-20 read |
| TS 32.272 vj00 | Charging for Push-to-Talk over Cellular (PoC) | Rel-19 read |
| TS 32.401 vj00 | Performance Management Concept & Requirements | Rel-19 read |
| TS 32.791 vb00 | Common RAT NRM IRP Requirements | Rel-11 read |
| TS 32.792 vb10 | Generic RAN NRM Information Service | Rel-11 read |
| TR 32.901 vj00 | UDC Application Data Models Study | Rel-19 read |
| TS 33.127 vj80 | Lawful Interception Architecture | Rel-19 read |
| TR 33.848 vi00 | Technical Report on Virtualisation Security | Rel-18 read |
| TR 33.926 vk20 | Generic Network Product Security Assurance | Rel-20 read |
| TS 34.124 vj00 | EMC Requirements for 3G UTRA Terminals | Rel-19 read |
| TS 36.124 vj00 | EMC for E-UTRA User Equipment | Rel-19 read |
| TS 36.304 vj30 | LTE UE Idle Mode Procedures | Rel-19 read |
| TS 43.020 vj00 | Security Procedures for GSM | Rel-19 read |
| TS 43.051 vj00 | GERAN Stage 2 Service Description | Rel-19 read |
| TS 43.129 vj00 | PS Handover in GERAN A/Gb and GAN Modes | Rel-19 read |
| TS 43.130 vj00 | Iur-g Interface Overview | Rel-19 read |
| TS 43.318 vj00 | Generic Access Network (GAN) Stage 2 | Rel-19 read |
| TR 43.901 vj00 | Generic Access to A/Gb Interface Feasibility Study | Rel-19 read |
| TR 43.902 vj00 | GAN Enhancements Feasibility Study | Rel-19 read |
| TS 44.060 vj00 | GERAN RLC/MAC Protocol Specification | Rel-19 read |
| TS 44.068 vj00 | Group Call Control (GCC) Protocol for VGCS | Rel-19 read |
| TS 44.160 vg00 | GERAN Iu Mode RLC/MAC Protocol Specification | Rel-16 read |
| TS 44.318 vj00 | Generic Access Network (GAN) Interface Procedures | Rel-19 read |
| TR 45.913 vj00 | Optimized Transmit Pulse Shape for EGPRS2-B | Rel-19 read |
| TR 45.914 vj00 | MUROS Feasibility Study for Voice Capacity | Rel-19 read |
| TS 46.002 vj00 | Introduction to GSM Half-Rate Speech Processing | Rel-19 read |
| TS 46.021 vj00 | GSM Half Rate DTX Frame Substitution & Muting | Rel-19 read |
| TS 46.022 vj00 | GSM Half Rate DTX Comfort Noise Specification | Rel-19 read |
| TS 46.041 vj00 | GSM Half Rate Speech DTX Operation | Rel-19 read |
| TS 46.051 vj00 | GSM Enhanced Full Rate Speech Processing Intro | Rel-19 read |
| TS 46.062 vj00 | GSM EFR DTX Comfort Noise Specification | Rel-19 read |
| TS 46.081 vj00 | GSM Enhanced Full Rate DTX Operation | Rel-19 read |
| TS 48.103 vj00 | A Interface User Plane Transport Protocols | Rel-19 read |
| TS 49.008 vj00 | BSSAP on E-interface for inter-MSC handover | Rel-19 read |
| TS 51.021 vj00 | RF test methods and conformance requirements for GSM BSS | Rel-19 read |
| TS 52.021 vj00 | GSM A-bis Interface Network Management | Rel-19 read |
| TS 52.402 vj00 | GSM Performance Management Measurements | Rel-19 read |