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

Glossary term · Services

CMAS

Commercial Mobile Alert Service

Services →

CMAS is a 3GPP standardized public warning system that delivers geographically targeted emergency alerts to mobile users via cellular broadcast, ensuring rapid public safety communication without network congestion.

Introduced
Rel-9
Where
Radio Access Network › E-UTRAN (LTE)
Specifications
16 specs
Also in
Services, User Equipment
CMAS Description Purpose What changed Family Neighbours Detected Changes Specifications

Description

The Commercial Mobile Alert Service (CMAS) is a 3GPP standardized service for delivering public warning messages to mobile devices via cellular broadcast mechanisms. It is designed to operate over existing 3GPP networks (from 3G onwards) using the Cell Broadcast Service (CBS) architecture. CMAS leverages the existing Broadcast/Multicast Service Center (BM-SC) and Cell Broadcast Center (CBC) entities to disseminate alerts. The BM-SC receives alert messages from authorized government agencies, processes them, and forwards them to the CBC. The CBC then maps these alerts to the appropriate geographical areas (cells) and delivers them to the Radio Access Network (RAN) for broadcast. In the RAN, the alerts are transmitted over the air interface using System Information Blocks (SIBs) in LTE or System Information (SI) messages in 5G NR, specifically via SIB12 in LTE and SIB6/SIB8 in 5G NR for earthquake and tsunami warning system (ETWS) and CMAS alerts.

CMAS messages are broadcast to all devices within a targeted cell or set of cells, ensuring simultaneous delivery without point-to-point signaling overhead. Devices must be CMAS-capable and configured to receive such alerts. Upon receiving a CMAS broadcast, compatible devices interrupt ongoing user activities (e.g., with a distinctive sound and vibration) to display the alert text. The service supports message prioritization, with different alert categories such as Presidential, Extreme, Severe, AMBER, and Test alerts, each with specific handling requirements. Message content includes a warning type, severity, urgency, certainty, and recommended actions, formatted according to the Common Alerting Protocol (CAP) standard.

Key network components involved include the Cell Broadcast Entity (CBE), which originates alerts from public safety authorities, the CBC for area targeting and message distribution, and the BM-SC for managing broadcast sessions in LTE/5G. In the core network, the CBC interfaces with the Mobility Management Entity (MME) in LTE or the Access and Mobility Management Function (AMF) in 5G Core via the SBc interface. The RAN then broadcasts the alert using RRC signaling. CMAS ensures reliable delivery even in congested networks by using broadcast channels, avoiding the pitfalls of SMS-based systems. It also supports multilingual alerts and geotargeting down to the cell level, enabling precise warning dissemination. The service is integrated with other warning systems like ETWS, sharing similar broadcast mechanisms but differing in message types and origins.

Purpose & Motivation

CMAS was created to address the critical need for a reliable, fast, and scalable public warning system over mobile networks. Prior to CMAS, emergency alerts were often delivered via TV, radio, or SMS, which had limitations in speed, reach, and targeting. SMS-based alerts, for example, could cause network congestion and delays due to point-to-point delivery, failing during high-traffic emergencies. CMAS leverages cellular broadcast technology to overcome these issues, enabling simultaneous delivery to all devices in a threat area without overloading the network.

The development of CMAS was motivated by regulatory requirements and public safety initiatives, particularly in the United States where the Warning, Alert, and Response Network (WARN) Act mandated such a service. 3GPP standardized CMAS starting in Release 9 to ensure interoperability across networks and devices globally. It solves the problem of timely and accurate emergency communication, providing authorities with a tool to warn the public about imminent threats like natural disasters, terrorist attacks, or child abductions (AMBER alerts). By using existing cellular infrastructure, CMAS offers a cost-effective and widely accessible solution.

CMAS also addresses the limitations of earlier warning systems by supporting geotargeting, which ensures alerts are only sent to affected areas, reducing unnecessary public alarm. It integrates with international standards like CAP, allowing compatibility with other alerting systems. The service enhances public safety by delivering alerts in multiple languages and with distinct visual/audible cues, ensuring they are noticed even in noisy environments. Overall, CMAS represents a significant advancement in emergency communication, leveraging mobile technology to save lives and improve community resilience.

What changed in its specifications

The latest release-to-release comparison of specifications that define CMAS. 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
  • CMAS builds on PWS
    “PWS enables the distribution of ETWS, CMAS (aka WEA), KPAS and EU-Alert warning messages in GSM, UMTS, E-UTRAN and NG‑RAN, and CPAS warning messages in NG‑RAN.” TS 23.041

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 12 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.

Rel-9 introduced

CMAS is specified for the first time in Rel-9: PWS requirements, CBS message identifiers for CMAS alert classes, and E-UTRAN paging and SIB12 delivery of CMAS notifications.

  • Introduction of CMAS TS 36.331CR0252
  • “CMAS notification can occur at any point in time. The Paging message is used to inform CMAS capable UEs” TS 36.331 v9.18.0
  • “Commercial Mobile Alert System: Public Warning System that delivers Warning Notifications provided by Warning Notification Providers to CMAS capable PWS-UEs.” TS 22.268 v9.5.0
Rel-10 1 CR

CMAS notification handling in E-UTRA changed in Rel-10: the Paging cmas-Indication procedure and scheduling information were specified or corrected, and KPAS was added as a variant using CMAS AS mechanisms.

  • “If the UE receives a Paging message including the cmas-Indication, it shall start receiving the CMAS notifications according to schedulingInfoList contained in SystemInformationBlockType1.” TS 36.331 v10.22.0
  • Change in Scheduling Information for CMAS TS 36.331CR0916
  • “Korean Public Alert System (KPAS): Public Warning System that delivers Warning Notifications provided by Warning Notification Providers using the same AS mechanisms as defined for CMAS.” TS 36.331 v10.22.0
Rel-11 1 CR

CMAS gained multi-language support: new CBS Message Identifiers for additional languages, ME language-based reception rules, and CMAS-related behaviour in system information handling and limited service state.

  • “the ME shall attempt to receive this CBS message dependent on the language indicated in the CBS message and the language indicator settings in the ME” TS 23.041 v11.6.0
  • “CMAS CBS Message Identifier for CMAS Presidential Level Alerts for additional languages.” TS 23.041 v11.6.0
  • Receive CMAS notification in the limited service state TS 25.304CR0355
Rel-12 specification text

Rel-12 text states the Data Coding Scheme IE is mandatory for CMAS warning messages when Warning Message Content is present, and adds CMAS notification wording in TS 36.331.

  • “it is mandatory for ETWS secondary notification and CMAS warning messages when Warning Message Content E-UTRAN IE is present” TS 23.041 v12.8.0
  • “to inform about a CMAS notification and/ or;” TS 36.331 v12.20.0
Rel-13 specification text

CMAS notification handling in RRC was modified for Rel-13 to exclude NB-IoT and to restrict paging-based CMAS notification to UEs other than NB-IoT, BL UEs and UEs in CE.

  • “ETWS and/or CMAS capable UEs in RRC_CONNECTED, other than BL UEs and UEs in CE, shall attempt to read paging at least once every defaultPagingCycle” TS 36.331 v13.17.0
  • “to inform UEs in RRC_IDLE other than NB-IoT UEs, and UEs in RRC_CONNECTED other than NB-IoT UEs, BL UEs and UEs in CE, about a CMAS notification” TS 36.331 v13.17.0
  • “Including ETWS notification, CMAS notification (not applicable for NB-IoT);” TS 36.331 v13.17.0
Rel-14 1 CR

CMAS gained new CBS Message Identifiers (Public Safety Alerts, State/Local WEA Test, additional languages) and a new State/Local WEA Test class in the requirements, aligning with FCC WEA enhancements.

  • “CMAS CBS Message Identifier for CMAS State/Local WEA Test.” TS 23.041 v14.2.0
  • Addition of new Message Identifiers for FCC mandated Wireless Emergency Alert (WEA, aka CMAS) enhancements TS 23.041CR0161
  • “CMAS defines the following classes of Warning Notifications: Presidential, Imminent Threat, Public Safety, Child Abduction Emergency, and State/Local WEA Test.” TS 22.268 v14.1.0
Rel-15 specification text

CMAS gained geo-fencing support in Rel-15: new message identifier to trigger UE geo-fencing, warning area coordinates in SIB12, new CMAS notification requirements, and NR (SIB8) CMAS delivery.

  • “Additional Message Identifier to direct UEs to perform geo-fencing of CMAS messages” TS 23.041 v15.5.0
  • “carries a segment, with one or more octets, of the geographical area where the CMAS warning message is valid” TS 36.331 v15.24.0
  • “SIB8 contains a CMAS notification.” TS 38.331 v15.30.0
Rel-16 specification text

Rel-16 extends CMAS reception: UEs in coverage enhancement can receive CMAS indications in RRC_CONNECTED via control channels, and NG-RAN CMAS-capable UEs use defined procedures.

  • “For UEs in CE supporting reception of CMAS indication in RRC_CONNECTED mode, control channels associated with the shared data channel are used to inform the UE” TS 36.331 v16.21.0
  • “monitors control channels associated with the shared data channel to acquire ETWS notification and/or CMAS notification;” TS 36.331 v16.21.0
  • “In NG-RAN, an ETWS capable UE or a CMAS capable UE uses the procedures as outlined in subclause 9.1.3.5.” TS 23.041 v16.4.0
Rel-17 specification text

CMAS scope in TS 22.268 was extended to warning message delivery via satellite E-UTRAN and satellite NG-RAN, and CMAS-capable UE monitoring of PWS notifications was adapted for SDT in RRC_INACTIVE.

  • “warning message delivery via E-UTRAN, satellite E-UTRAN, NG-RAN and Satellite NG-RAN” TS 22.268 v17.2.1
  • “ETWS or CMAS capable UEs in RRC_INACTIVE while SDT procedure is ongoing shall monitor for indication about PWS notification” TS 38.331 v17.18.0
Rel-18 1 CR

In Rel-18, UE handling of CMAS changed: SIB33 reception was added alongside SIB31 for ETWS/CMAS in E-UTRA, and the CMAS-capable UE requirements and scope in TS 22.268 were extended with EU-ALERT and KPAS.

  • “except for ETWS/CMAS, SIB31(-NB) and SIB33(-NB) reception where applicable” TS 36.331 v18.11.0
  • “For ETWS or CMAS capable UEs in RRC_INACTIVE while SDT procedure is ongoing:” TS 38.331 v18.11.0
  • Clarification on SIB1 reception for ETWS/CMAS TS 38.331CR4820
Rel-19 specification text

RRC specs changed CMAS handling: ETWS/CMAS paging monitoring now covers NB-IoT UEs and UEs in CE or RRC_INACTIVE, SIB12-NB carries CMAS notifications, and 38.331 excludes paging-adaptation-only occasions.

  • “The IE SystemInformationBlockType12-NB contains a CMAS notification.” TS 36.331 v19.4.0
  • “ETWS and/or CMAS capable UEs in RRC_CONNECTED, other than BL UEs and UEs in CE and NB-IoT UEs, shall attempt to read paging” TS 36.331 v19.4.0
  • “ETWS or CMAS capable UEs in RRC_CONNECTED shall monitor for indication about PWS notification in any paging occasion except those only for UEs that support paging adaptation” TS 38.331 v19.4.0
Rel-20 specification text

CMAS gained silent-alert support (Message Code suppressing tones/vibration) and template-based multilingual alert requirements, with CMAS-capable UE procedures extended to CPAS in Rel-20.

  • “Warning Notifications shall support the ability to instruct a CMAS capable UE whether to present the alerts by suppressing the alerting tones or vibration cadence or both.” TS 22.268 v20.3.0
  • “enabling a CMAS-capable UE to support template-based multilingual CMAS alerts” TS 22.268 v20.3.0
  • “For CPAS, Warning Message Delivery procedure for CMAS is used.” TS 23.041 v20.0.0

Defining Specifications

3GPP specifications that define or reference CMAS, 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 25.304 vj10 UE Idle Mode Procedures Rel-19 read
TS 26.804 vk10 5G Media Delivery Architecture Extensions Rel-20 read
TS 29.168 vj00 SBc-AP Protocol Specification Rel-19 read
TR 33.969 vj00 Security for Public Warning System (PWS) Rel-19 read
TS 36.300 vj20 E-UTRAN Radio Interface Protocol Architecture Rel-19 read
TS 36.302 vj00 E-UTRA Physical Layer Services Rel-19 read
TS 36.304 vj30 LTE UE Idle Mode Procedures Rel-19 read
TS 36.331 vj40 E-UTRA Radio Resource Control (RRC) Protocol Rel-19 read
TS 36.401 vj00 E-UTRAN Overall Architecture Description Rel-19 read
TS 36.410 vj00 S1 Interface: General Aspects and Principles Rel-19 read
TS 38.300 vj40 NR and NG-RAN Overall Description Rel-19 read
TS 38.304 vj30 NR UE Idle and Inactive State Procedures Rel-19 read
TS 38.331 vj40 NR Radio Resource Control (RRC) Rel-19 read
TS 38.401 vj30 NG-RAN Architecture Description Rel-19 read