Menu
Latest
12 meetings · Prague, Jeju · 12–16 Oct
Reports
RAN1#126-bis · SA2#177

Glossary term · Services

CBS

Cell Broadcast Service

Services →

CBS is a point-to-multipoint service that broadcasts short messages to all mobile devices in a specific geographical area for public warnings and emergency notifications without causing network congestion.

Introduced
Phase 1
Where
Radio Access Network › UTRAN (3G)
Specifications
16 specs
Also in
Services
CBS Description Purpose What changed Family Neighbours Detected Changes Specifications

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.

What changed in its specifications

The latest release-to-release comparison of specifications that define CBS. Each summary describes the whole specification, not only this term.

TR 21.905Rel-17 → Rel-18

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 →
TS 22.268Rel-11 → Rel-12

Rel-12 adds regulatory conditional integrity protection requirements for Warning Notifications. It also removes text about USIM-based VPLMN settings changes.

Full comparison in TS 22.268 →

Technology family

Broadcast and multicast · Services

  1. Phase 1 CBC, CBCH, CBS, SMS-CB
  2. Phase 2 CBE
  3. R99 BMC, SABP
  4. Rel-6 ALC, BM-SC, FDT, FLUTE, LCT, MBMS, MBMS Bearer Service, MBMS download delivery method, MBMS streaming delivery method, MBMS User Service, TMGI
  5. Rel-7 MBSFN
  6. Rel-8 ETWS, MCE, PWS
  7. Rel-9 CBSP, CMAS, eMBMS, MBMS-GW
  8. Rel-10 KPAS
  9. Rel-11 EU-Alert
  10. Rel-12 MooD
  11. Rel-13 MBMS group communication delivery method, SC-PTM
  12. Rel-14 MBMS transparent delivery method, Receive Only Mode
  13. Rel-15 CBCF, PWS-IWF
  14. Rel-16 5G Broadcast
  15. 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
  • CBS reused as SMS-CB
    “3GPP TS 44.012: "Short Message Service Cell Broadcast (SMSCB) support on the mobile radio interface"” TS 23.041

Messaging services · Services

  1. Phase 1 CBC, MO-SMS, MT-SMS, SMS, SMS-CB
  2. Phase 2 CBE, SMS-GMSC, SMS-IWMSC
  3. R99 EMS, MMS, MMS User Agent, MMSE
  4. Rel-4 MMS Relay/Server
  5. Rel-6 IP-SM-GW, MSCF
  6. Rel-7 SMS over IP, SMS Router
  7. Rel-8 SMS over SGs
  8. Rel-15 CBCF, PWS-IWF, SMS over NAS, SMSF
  9. Rel-17 Legacy 3GPP Message Gateway, MSGin5G, MSGin5G Client, MSGin5G Server, Non-3GPP Message Gateway
  10. Rel-18 Broadcast Message Gateway

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 sources

Documented changes in 14 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.

Phase 1 introduced

Introduced in Phase 1 (release dating of the term; no individual change cited).

R99 specification text

Release 99 specifies CBS for GSM and UMTS, defining the cell broadcast network structure, the CBS message and page format, and the UMTS RNS and radio interface requirements.

  • “The present document describes the Cell Broadcast short message service (CBS) for GSM and UMTS.” TS 23.041 v3.5.0
  • “CBS messages are broadcast to defined geographical areas known as cell broadcast areas.” TS 23.041 v3.5.0
  • “A UE supporting Cell Broadcast Service (CBS) shall be capable to receive BMC messages in the Idle mode” TS 25.324 v3.9.0
Rel-5 specification text

Rel-5 specifies CBS behaviour further: BMC schedule message timing was reworded (UE need not receive a CBS schedule period earlier than 100ms after the schedule message) and CBS messages can carry SMS-style IEs via a User Data Header.

  • “The UE is not required to start receiving a CBS Schedule Period earlier than 100ms after UE has received the complete BMC Schedule message.” TS 25.324 v5.6.0
  • “User Data Header support over CBS” TS 23.038 v5.1.0
  • “The CBS message information field will contain the IEs as described in 3GPP TS 23.040.” TS 23.038 v5.1.0
Rel-6 specification text

The BMC protocol for CBS gained new information elements (CBS Schedule Message Extension, CBS Message Serial Numbers, CTCH BS Index) and revised schedule-message reception timing wording.

  • “11.12 CBS Schedule Message Extension” TS 25.324 v6.6.0
  • “The CBS Message Serial Number of the BMC CBS Message referred to by the CTCH BS Index.” TS 25.324 v6.6.0
  • “The CTCH BS Index IE indicates the index of the CTCH BS within the BMC Schedule Period which contains the start of the BMC CBS Message.” TS 25.324 v6.6.0
Rel-8 specification text

CBS in TS 23.041 gained public warning/ETWS roles: emergency indication, paging-triggered CBS reception, remote activation of terminals, and separate duplicate detection for CBS messages.

  • “the cell broadcast service can be used to transfer CBS messages related to public warning.” TS 23.041 v8.11.0
  • “Sending paging messages to mobile terminals upon receiving CBS transmission request from CBC including the Paging-ETWS-Indicator.” TS 23.041 v8.11.0
  • “shall start to broadcast the Secondary Notification message as a CBS message on the Cell Broadcast channel” TS 23.041 v8.11.0
Rel-9 specification text

TS 23.041 now separates ETWS emergency messages from CBS messages in GERAN, with distinct WRITE-REPLACE contents (Paging ETWS Indicator vs Channel Indicator), and TS 48.049 CBSP is specified.

  • “When containing a CBS message the WRITE-REPLACE message includes the "Channel Indicator" to differentiate it from an ETWS emergency message” TS 23.041 v9.11.0
  • “When the WRITE-REPLACE message contains a CBS message the BSC/BTS shall start to broadcast the CBS message on the Cell Broadcast channel” TS 23.041 v9.11.0
  • “Duplicate message detection shall be performed independently for ETWS Primary Notifications and warning messages broadcasted as CBS messages (Secondary Notifications).” TS 23.041 v9.11.0
Rel-10 specification text

The PLMN-wide scope of a CBS message was clarified: the Message Code or Update Number must change in the next cell of the PLMN, and a change of PLMN, including to an ePLMN, makes the message new.

  • “The CBS message is only relevant to the PLMN in which it is broadcast, so any change of PLMN (including a change to another PLMN which is an ePLMN) means the CBS message is "new"” TS 23.041 v10.6.0
Rel-11 specification text

CBS requirements were extended to the CBC connecting to MMEs and eNodeBs (E-UTRAN), and MS/UE must discard CBS messages in the A000-AFFF identifier range unless received from the HPLMN or an equivalent PLMN.

  • “The CBC may be connected to several BSCs/RNCs/MMEs. The CBC may be connected to several CBEs.” TS 23.041 v11.6.0
  • “Discard CBS messages in Message Identifier value range "A000hex-AFFFhex" unless received from HPLMN, EHPLMN or PLMN that is equivalent to HPLMN or EHPLMN.” TS 23.041 v11.6.0
  • “initiating broadcast by sending fixed length CBS messages to a BSC/RNC/eNodeB for each language provided by the cell” TS 23.041 v11.6.0
Rel-14 specification text

CBS Message Identifier handling was extended: new CMAS identifiers (4396-4399) were added, and the mandatory and optional language ranges were widened, with rules for ME language filtering of CBS warning messages.

  • “CMAS CBS Message Identifier for CMAS Public Safety Alerts.” TS 23.041 v14.2.0
  • “The ME shall not use any language filter mechanisms or use the language(s) selected through the MMI to determine whether a particular CBS message should be displayed” TS 23.041 v14.2.0
  • “Intended as CMAS and/or EU-Alert range in future versions of this document.” TS 23.041 v14.2.0
Rel-15 specification text

CBS procedures and message handling were extended to NG-RAN: a new CBCF connected to AMFs manages CBS messages, and NG-RAN nodes are added to the broadcast, modification and message identification procedures.

  • “The CBCF may be connected to several AMFs. The CBCF may be connected to several CBEs.” TS 23.041 v15.5.0
  • “in NG-RAN within the CBCF-AMF interface and CBC – PWS-IWF interface, a CBS message is uniquely identified by the triplet” TS 23.041 v15.5.0
  • “warning messages of up to 9600 octets in E-UTRAN, or NG-RAN.” TS 23.041 v15.5.0
Rel-16 specification text

New CBS Message Identifier values were added for warning and test messages dedicated to UEs with no user interface and with ePWS functionality, covering ETWS and non-ETWS and several disaster types.

  • “Non-ETWS CBS Message Identifier for warning message dedicated to UEs with no user interface and with ePWS functionality.” TS 23.041 v16.4.0
  • “Non-ETWS CBS Message Identifier for test message dedicated to UEs with no user interface and with ePWS functionality.” TS 23.041 v16.4.0
  • “ETWS CBS Message Identifier for warning message dedicated to UEs with no user interface and with ePWS functionality.” TS 23.041 v16.4.0
Rel-17 specification text

CBS in TS 23.041 was extended to cover SNPNs: cell broadcast areas may span an entire SNPN, operators of SNPNs allocate Message Codes, and A000-AFFF messages are accepted from a subscribed SNPN.

  • “Discard CBS messages in Message Identifier value range "A000hex-AFFFhex" unless received from HPLMN, EHPLMN, PLMN that is equivalent to HPLMN or EHPLMN, or a subscribed SNPN.” TS 23.041 v17.6.0
  • “These areas may comprise of one or more cells, or may comprise the entire PLMN or SNPN.” TS 23.041 v17.6.0
  • “Message Codes are for allocation by PLMN or SNPN operators.” TS 23.041 v17.6.0
Rel-18 2 CRs

CBS handling changed: MS/UE discard rules for operator-specific message identifiers now cover equivalent SNPNs, new CBS Message Identifiers were added for additional KPAS services, and CBS language handling was corrected.

  • “In an SNPN, the MS shall discard a CBS message in Message Identifier value range "A000hex-AFFFhex" unless it is received from the subscribed SNPN or an SNPN equivalent to the subscribed SNPN.” TS 23.041 v18.8.0
  • CBS Message Identifiers for additional KPAS services TS 23.041CR0233
  • Corrections to language handling in CBS TS 23.038CR0238
Rel-20 1 CR

CBS gained a new data coding scheme for languages identified by 3-letter indicators, and a Message Code part can now command terminals to suppress alert tones or vibration for CMAS CBS messages.

  • “a part of Message Code can be used to command mobile terminals whether to present the alerts by suppressing the alerting tones or vibration cadences” TS 23.041 v20.0.0
  • CBS data coding scheme for languages identified by language indicator of 3 letters TS 23.038CR0243

Defining Specifications

3GPP specifications that define or reference CBS, with the latest known release. Sourced from the 3GPP document catalog — see methodology.

SpecificationTitleRelease
TR 21.905 vj20 3GPP Terminology and Definitions Rel-19 read
TS 22.268 vl00 Public Warning System Requirements Rel-21 read
TS 23.048 v590 Secured Packets Structure for SMS and UICC Management Rel-5 read
TS 23.700 vk10 AI/ML Application Layer Support Phase 2 Rel-20 read
TS 25.324 vj00 Broadcast/Multicast Control Protocol Rel-19 read
TS 25.401 vj00 UTRAN Overall Architecture Rel-19 read
TS 25.410 vj00 Iu Interface Introduction for UTRAN Rel-19 read
TS 25.419 vj00 Service Area Broadcast Protocol (SABP) Rel-19 read
TS 25.703 vc00 HNB Emergency Warning Area Study for UTRA Rel-12 read
TS 29.168 vj00 SBc-AP Protocol Specification Rel-19 read
TS 29.199 3GPP TS 29.199 Rel-4 read
TS 31.115 vj00 Secured Packet Structure for UICC Applications Rel-19 read
TS 32.102 vj00 Telecom Management Physical Architecture Framework Rel-19 read
TR 43.901 vj00 Generic Access to A/Gb Interface Feasibility Study Rel-19 read
TS 44.318 vj00 Generic Access Network (GAN) Interface Procedures Rel-19 read
TS 48.049 vj00 Cell Broadcast Service Protocol Specification Rel-19 read