Description
The Public Warning System (PWS) in 3GPP standards defines the mechanisms for broadcasting cell-wide emergency information to all User Equipments (UEs) in a defined warning area. It operates as a point-to-multipoint service that is network-initiated and does not require any subscription or prior registration from the UE to receive alerts. Architecturally, the system involves a Cell Broadcast Entity (CBE), which is the interface for warning authorities to inject alerts. The CBE communicates with a Cell Broadcast Center (CBC) in the core network. The CBC is responsible for managing the warning message distribution and interfaces with the Radio Access Network (RAN) via the appropriate network node—the Base Station Controller (BSC) for 2G, the Radio Network Controller (RNC) for 3G, or the Mobility Management Entity (MME) for 4G, which then instructs the eNodeBs.
How it works involves a standardized message format and delivery protocol. The warning message includes content (text), a warning type (e.g., tsunami, earthquake), severity level, and a target geographical area defined by a list of cells or tracking areas. The CBC uses the Cell Broadcast Service (CBS) to deliver this information to the RAN. The RAN then schedules and broadcasts the message over the air interface using System Information Blocks (SIBs) on a dedicated logical channel, the Cell Broadcast Channel (CBCH) in 2G/3G or via SIB12 in LTE and SIB12/SIB10 in NR. UEs continuously monitor these channels. Upon receiving an alert with a new message identifier, the UE decodes it, checks the geographical relevance (if supported), and presents it to the user with a distinctive sound and vibration pattern.
Its role is paramount for public safety and is often a regulatory requirement. The PWS ensures alerts bypass normal network congestion, as they use broadcast channels. It supports message repetition for reliability and allows for multiple, simultaneous alerts. Advanced implementations support enhanced PWS (ePWS) with multimedia content, location-based filtering on the UE, and compatibility with other warning systems like the Earthquake and Tsunami Warning System (ETWS) and the Commercial Mobile Alert System (CMAS).
Purpose & Motivation
The PWS was created to address the critical need for a rapid, reliable, and widespread method to disseminate emergency information to the public via their mobile phones. The motivation stemmed from lessons learned during major disasters where traditional communication channels (TV, radio) failed or were inaccessible, but cellular networks often remained partially functional. It solves the problem of how to reach virtually every person in a threatened area within seconds, regardless of whether they are locals or visitors.
Historically, before standardized PWS, methods were ad-hoc, such as SMS-based blast, which are slow, congest networks, and lack guaranteed delivery. The limitations of SMS include point-to-point nature, network signaling overload, and dependency on subscriber registration. The 3GPP PWS, based on Cell Broadcast technology, was designed to overcome these by using a one-to-many broadcast mechanism that does not load the control plane, works independently of user subscription state (even roaming UEs can receive alerts), and provides geographical targeting.
The creation and continuous evolution of PWS in 3GPP were also driven by regulatory mandates in many countries (e.g., EU's EU-Alert, USA's CMAS, Japan's ETWS). It provides a standardized, interoperable framework that allows device manufacturers and network operators to implement a consistent warning service globally, ensuring that a phone purchased in one country can receive alerts in another, enhancing public safety for travelers.
What changed in its specifications
The latest release-to-release comparison of specifications that define PWS. 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-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 →Release Timeline
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (12 CRs across 6 releases). Complements the general historical overview above with the evidence-based evolution of this function.
Defining Specifications
3GPP specifications that define or reference PWS, 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.268 vl00 | Public Warning System Requirements | Rel-21 read |
| TR 22.968 vj00 | Study on Public Warning System (PWS) | Rel-19 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.304 vj30 | LTE UE Idle Mode Procedures | 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 36.413 vj20 | S1 Application Protocol (S1AP) for E-UTRAN | Rel-19 read |
| TR 37.941 vj20 | RF Conformance Testing Background for Radiated BS Requirements | Rel-19 read |
| TS 38.141 vj40 | BS Conformance Testing (TR 38.141) | Rel-19 read |
| TS 38.300 vj40 | NR and NG-RAN Overall Description | 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 |
| TR 38.882 vi00 | Technical Report on UE Location Service | Rel-18 read |