Description
The Cell Broadcast Channel (CBCH) is a fundamental broadcast mechanism within the GSM and UMTS radio access network architecture, designed for efficient, unidirectional information distribution. It operates as a logical channel mapped onto physical resources, specifically utilizing a dedicated timeslot on the Broadcast Control Channel (BCCH) carrier in GSM or appropriate transport channels in UMTS. The system is orchestrated by the Cell Broadcast Centre (CBC), a core network entity that originates broadcast messages and forwards them via the Base Station Controller (BSC) in GSM or Radio Network Controller (RNC) in UMTS to the Base Transceiver Station (BTS) or Node B for transmission over the air interface. Each broadcast message is tagged with a message identifier and serial number, allowing mobile stations to filter and display relevant information based on user preferences or network mandates.
From a technical perspective, CBCH messages are formatted as short strings of up to 93 characters (in GSM) and are broadcast repetitively within a defined geographical area, known as a cell or group of cells forming a Location Area (LA) or Routing Area (RA). The broadcast is performed on a specific CBCH logical channel, which is multiplexed with other control channels. Mobile devices continuously monitor this channel when camped on a cell, decoding messages without establishing a dedicated connection, thus operating in an idle mode. This design ensures minimal impact on network capacity and device battery life, as no uplink transmission or acknowledgment is required.
The architecture involves key interfaces: the CBC connects to the BSC via the CBC-BSC interface (standardized in 3GPP TS 48.049) using the Cell Broadcast Protocol (CBP). In the radio access network, the BSC maps CBCH data onto the Slow Associated Control Channel (SACCH) for transmission, utilizing a pre-defined timeslot structure. Message scheduling and repetition rates are configurable, allowing network operators to prioritize critical alerts. Security aspects include message integrity through serial numbering, but traditional CBCH lacks encryption, making it suitable for public information rather than confidential data. Its role extends beyond mere messaging; it supports Cell Broadcast Service (CBS), enabling applications like the Earthquake and Tsunami Warning System (ETWS) and Commercial Mobile Alert System (CMAS), which are critical for public safety.
Purpose & Motivation
CBCH was created to address the need for efficient, wide-area information dissemination in mobile networks without causing congestion associated with point-to-point Short Message Service (SMS). Prior to its introduction, broadcasting information required individual SMS deliveries to each subscriber, overwhelming network resources during emergencies or high-demand events. CBCH solves this by leveraging a one-to-many paradigm, ensuring that a single message transmission reaches all devices in a targeted cell simultaneously, regardless of the number of users. This capability is crucial for time-sensitive alerts, such as natural disaster warnings, where rapid and reliable communication is essential for public safety.
Historically, CBCH was standardized in 3GPP Release 4 as part of GSM Phase 2+ enhancements, evolving from earlier GSM specifications to support value-added services. Its development was motivated by growing demands for location-based services and regulatory requirements for public warning systems across various countries. By offloading broadcast traffic from dedicated signaling channels, CBCH improves network efficiency and scalability, allowing operators to offer commercial services like advertising and news updates without degrading voice or data performance. The technology laid the groundwork for later advancements in LTE's Warning Notification and 5G's Public Warning System, maintaining backward compatibility across generations.
What changed in its specifications
The latest release-to-release comparison of specifications that define CBCH. 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 adds definitions for Key Performance Indicator (KPI), Performance metric, and the KPI abbreviation in clause 3 of TS 32.401. That is the only addition named in the overview provided.
Full comparison in TS 32.401 →Technology family
Broadcast and multicast · Services
- Phase 1 CBC, CBCH, CBS, SMS-CB
- Phase 2 CBE
- R99 BMC, SABP
- Rel-6 ALC, BM-SC, FDT, FLUTE, LCT, MBMS, MBMS Bearer Service, MBMS download delivery method, MBMS streaming delivery method, MBMS User Service, TMGI
- Rel-7 MBSFN
- Rel-8 ETWS, MCE, PWS
- Rel-9 CBSP, CMAS, eMBMS, MBMS-GW
- Rel-10 KPAS
- Rel-11 EU-Alert
- Rel-12 MooD
- Rel-13 MBMS group communication delivery method, SC-PTM
- Rel-14 MBMS transparent delivery method, Receive Only Mode
- Rel-15 CBCF, PWS-IWF
- Rel-16 5G Broadcast
- Rel-17 5MBS, Broadcast MBS session, MB-SMF, MB-UPF, MBS, MBS Distribution Session, MBS User Service, MBSF, MBSSF, MBSTF, Multicast MBS session, Object Distribution Method, Packet Distribution Method
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 4 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).
GPRS RLC/MAC (44.060) gains PSI8 signalling carrying the CBCH channel description and CBCH frequency storage in packet idle mode; 43.051 adds a CBCH section for GERAN.
- “The PSI8 message may be broadcast on the PBCCH if additional information (i.e. CBCH configuration and dynamic ARFCN mapping) shall be provided” TS 44.060 v4.23.0
- “If the mobile station supports SMSCB, is shall be able to store the frequency information for the CBCH, to be used in packet idle mode.” TS 44.060 v4.23.0
The CBCH Channel Description, when available, must be included in exactly one instance of PSI8 within the consistent set of PSI8 messages; CBCH frequency storage now also covers MAC-Idle state.
- “the CBCH Channel Description construction shall be included in one and only one instance of the PSI8 message within the consistent set of PSI8 messages” TS 44.060 v5.21.0
- “store the frequency information for the CBCH to be used in packet idle mode or MAC-Idle state.” TS 44.060 v5.21.0
TS 48.049 v9.4.0 gains CBCH load status enquiry (LOAD QUERY procedure with Radio Resource Load values) and priority-based CBS message scheduling on the basic or extended CBCH.
- “The purpose of the Load Status Enquiry procedure is to obtain the current load status of the CBCH radio resources within a cell.” TS 48.049 v9.4.0
- “Two CBCH radio resource load values per cell shall be provided by the BSC.” TS 48.049 v9.4.0
- “The CBCH can be of type basic or extended (see 3GPP TS 45.002 [11]).” TS 48.049 v9.4.0
Defining Specifications
3GPP specifications that define or reference CBCH, 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 32.401 vj00 | Performance Management Concept & Requirements | Rel-19 read |
| TS 43.051 vj00 | GERAN Stage 2 Service Description | Rel-19 read |
| TS 44.060 vj00 | GERAN RLC/MAC Protocol Specification | Rel-19 read |
| TS 44.160 vg00 | GERAN Iu Mode RLC/MAC Protocol Specification | Rel-16 read |
| TS 48.049 vj00 | Cell Broadcast Service Protocol Specification | Rel-19 read |
| TS 52.402 vj00 | GSM Performance Management Measurements | Rel-19 read |