Description
Cell Broadcast Service (CBS) is a standardized messaging service within 3GPP networks that enables the simultaneous delivery of short, unacknowledged messages to all User Equipment (UE) within a defined geographical area, known as a Cell Broadcast Area (CBA). Unlike point-to-point SMS, CBS operates on a unidirectional broadcast model where messages are sent once by the network and received by all compatible devices in the target area without requiring individual addressing or establishing dedicated connections. This makes it inherently efficient for mass notification scenarios. The service is managed by the Cell Broadcast Centre (CBC), a core network entity responsible for message origination, scheduling, and area targeting.
The architectural implementation of CBS involves several key network elements. The CBC interfaces with the Core Network, specifically the Mobility Management Entity (MME) in LTE or the Access and Mobility Management Function (AMF) in 5GC, via the SBc interface. The core network node then forwards the Cell Broadcast Messages to the relevant Radio Access Network (RAN) nodes—such as the eNodeB in LTE or gNB in 5G NR—serving the targeted geographical area. The RAN broadcasts these messages over the air interface using specific logical channels and system information blocks. In LTE, for example, messages are broadcast on the SC-MCCH (Single Cell Multicast Control Channel) and SC-MTCH (Single Cell Multicast Traffic Channel) for SC-PTM (Single Cell Point-to-Multipoint) delivery, or via System Information Block Type 20 (SIB20).
From the UE perspective, CBS reception is typically a background process. Devices monitor the designated broadcast channels for messages tagged with specific Message Identifiers and Serial Numbers. Each message is associated with a Geographical Scope (e.g., cell, PLMN, or tracking area) and a CBS Message Identifier (Message ID), which categorizes the message type (e.g., 4370 for Earthquake and Tsunami Warning System, ETWS). Users can typically enable or disable reception for different message categories in their device settings. A key technical feature is the use of a 16-bit Serial Number, which allows the UE to identify and ignore duplicate broadcasts of the same message, conserving battery life.
The service's role in the network extends beyond simple messaging to become a critical component of Public Warning Systems (PWS), as mandated by regulators in many countries. It provides guaranteed delivery mechanisms for emergency alerts like tsunami warnings (ETWS) and commercial mobile alerting (CMAS). Its broadcast nature ensures it does not contribute to signaling congestion during emergencies—a significant limitation of SMS-based alerting. The protocol supports message concatenation for longer alerts, multiple language indications, and different priority levels to ensure critical warnings can interrupt device operation.
Purpose & Motivation
CBS was created to address the fundamental need for efficient, simultaneous communication to a massive number of mobile users within a specific geographic area, a capability lacking in traditional point-to-point services. Prior to CBS, the only widespread method for mass mobile notification was SMS, which suffers from severe limitations during emergencies: it requires individual addressing for each recipient, generates massive signaling load that can congest the network, and delivers messages with significant and unpredictable delays due to queuing. In disaster scenarios where timely warnings are critical, these limitations render SMS-based alerting ineffective and potentially dangerous.
The historical context for CBS development includes increasing regulatory requirements for public safety. Following major disasters, governments worldwide recognized the need for reliable mobile-based warning systems. 3GPP standardized CBS to provide a network-native broadcast capability that operates independently of the call and SMS traffic. It solves the problem of network congestion by using a one-to-many broadcast model that consumes minimal additional radio resources regardless of the number of recipients. The service also addresses the need for location-based targeting, allowing warnings to be sent only to areas affected by an emergency (like a flood zone or severe weather cell), avoiding unnecessary alerts to users outside the risk area.
Furthermore, CBS enables commercial and service provider applications beyond emergency alerts, such as broadcasting traffic information, weather updates, or local advertising to subscribers in a particular city or neighborhood. Its creation was motivated by the vision of turning the cellular network into a versatile broadcast medium, leveraging the existing infrastructure to deliver both critical public information and value-added services without impacting the capacity for individual voice and data communications.
Classification
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (1 CRs across 1 releases). Complements the general historical overview above with the evidence-based evolution of this function.
Studied in Rel-4, normative work from Rel-17.
In Release 17, the CBS function was enhanced by introducing a procedure to broadcast an Empty Area List for a Write-Replace-Warning Request. This new capability allows for the explicit definition of geographical areas where a warning should not be distributed, refining the geographical routing of broadcast messages.
- Broadcast Empty Area List for Write-Replace-Warning Request TS 29.168CR0075
Explore further
Broader topics and technologies where CBS plays a role.
Defining Specifications
3GPP specifications that define or reference CBS, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TR 21.905 vj00 | 3GPP Technical Terms and Definitions | Rel-19 |
| TS 22.268 vk00 | Public Warning System (PWS) Requirements | Rel-20 |
| TS 23.048 v1400 | Secured Packets for UICC Remote Management | Rel-5 |
| TS 23.700 vk00 | XR Services Application Enablement Layer | Rel-20 |
| TS 25.324 vj00 | Broadcast/Multicast Control Protocol | Rel-19 |
| TS 25.401 vj00 | UTRAN Overall Architecture | Rel-19 |
| TS 25.410 vj00 | Iu Interface Introduction for UTRAN | Rel-19 |
| TS 25.419 vj00 | Service Area Broadcast Protocol (SABP) | Rel-19 |
| TS 25.703 vc00 | HNB Emergency Warning Area Study for UTRA | Rel-12 |
| TS 29.168 vj00 | SBc-AP Protocol Specification | Rel-19 |
| TS 29.199 v1900 | Multimedia Messaging Web Services | Rel-9 |
| TS 31.115 vj00 | Secured Packet Structure for UICC Applications | Rel-19 |
| TS 32.102 vj00 | Telecom Management Physical Architecture Framework | Rel-19 |
| TR 43.901 vj00 | Generic Access to A/Gb Interface Feasibility Study | Rel-19 |
| TS 44.318 vj00 | Generic Access Network (GAN) Interface Procedures | Rel-19 |
| TS 48.049 vj00 | Cell Broadcast Service Protocol Specification | Rel-19 |