Description
The Public Warning System - Interworking Function (PWS-IWF) is a specialized network node defined within the 3GPP architecture, specified primarily in TS 29.168. Its primary role is to serve as the entry point and adaptation layer for public warning messages entering the 3GPP network from external alerting authorities, such as government agencies. The PWS-IWF receives warning messages via standardized interfaces, typically from a Cell Broadcast Entity (CBE), which is the source of the alert content. Upon receipt, the PWS-IWF performs several key functions: it authenticates the message source to ensure legitimacy, validates the message format and content, and then adapts the message for delivery over the 3GPP network. This adaptation involves mapping the incoming alert information into the specific protocol data units (PDUs) required by the core network, such as those for the Cell Broadcast Center (CBC).
The PWS-IWF interfaces with the Cell Broadcast Center (CBC) using the SBc interface, which is the standard interface for warning message distribution within the 3GPP network. The PWS-IWF's architecture is designed to be access-agnostic, meaning it can support the delivery of warnings to User Equipments (UEs) connected via Evolved Packet Core (EPC) for 4G/LTE, 5G Core (5GC) for 5G, and even legacy systems. It handles the necessary protocol conversions and session management to ensure the warning message is correctly forwarded to the CBC, which then orchestrates the broadcast of the message to the targeted geographic areas via the relevant base stations (eNBs, gNBs).
A critical technical aspect of the PWS-IWF is its support for different warning system types, primarily ETWS and CMAS. For ETWS, it handles primary and secondary notification messages, which require very low latency. For CMAS, it manages a wider range of alert categories and severities. The PWS-IWF also plays a role in message prioritization, ensuring that critical warnings preempt other network traffic. It may log message delivery for auditing and provide delivery reports back to the alerting authority. Its implementation is crucial for meeting regulatory mandates for public warning systems in many countries, providing a standardized, reliable, and secure gateway for life-saving information.
Purpose & Motivation
The PWS-IWF was created to address the critical need for a standardized, reliable, and secure mechanism to deliver public warning messages to mobile subscribers. Prior to its standardization, warning systems were often proprietary, fragmented, and unable to leverage the ubiquitous coverage of cellular networks effectively. The 2004 Indian Ocean tsunami and other disasters highlighted the limitations of existing alerting methods, driving regulatory bodies worldwide to mandate that mobile networks be capable of broadcasting emergency alerts.
3GPP developed the Public Warning System (PWS) framework to fulfill these regulatory requirements. The PWS-IWF specifically solves the problem of interoperability between external, non-3GPP alerting systems (like government warning platforms) and the internal 3GPP network architecture. It provides a single, standardized point of entry, ensuring that alerts from any authorized source can be ingested, authenticated, and formatted correctly for broadcast across the entire network. This eliminates the need for multiple, custom integrations between alert providers and each mobile network operator, reducing complexity and increasing reliability.
Furthermore, the PWS-IWF enables the support for advanced warning features like geotargeting (alerts for specific cells), message prioritization, and support for multiple warning types (earthquake, tsunami, amber alert, etc.) within a unified framework. Its creation was motivated by the goal of saving lives through timely communication, making it a fundamental component of modern cellular networks' contribution to public safety.
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
- PWS-IWF used together with CBC
“This Indication is sent by an AMF via the PWS-IWF to report to the CBC the Broadcast Scheduled Area List(s) NG-RAN the AMF has received from the NG-RAN node(s) as Broadcast Completed Area List.” TS 23.041
Messaging services · Services
- Phase 1 CBC, MO-SMS, MT-SMS, SMS, SMS-CB
- Phase 2 CBE, SMS-GMSC, SMS-IWMSC
- R99 EMS, MMS, MMS User Agent, MMSE
- Rel-4 MMS Relay/Server
- Rel-6 IP-SM-GW, MSCF
- Rel-7 SMS over IP, SMS Router
- Rel-8 SMS over SGs
- Rel-15 CBCF, PWS-IWF, SMS over NAS, SMSF
- Rel-17 Legacy 3GPP Message Gateway, MSGin5G, MSGin5G Client, MSGin5G Server, Non-3GPP Message Gateway
- Rel-18 Broadcast Message Gateway
- PWS-IWF used together with CBCF
“The WRITE-REPLACE-WARNING-REQUEST Request/Indication primitive shall then be forwarded to the AMF.” 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 sourcesDocumented changes in 3 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.
The PWS-IWF is specified for the first time as a logical function translating between N50 (AMF) and SBc (CBC) for 5GS public warning, with its architecture, primitives and SBc-AP procedures.
- “The PWS-IWF is a logical function which functionality is to translate from N50 to SBc.” TS 23.041 v15.5.0
- “between the Public Warning System – Inter Working Function (PWS-IWF) and the CBC.” TS 29.168 v15.1.0
- “when PWS-IWF is used. This option is further described in Annex B.” TS 23.041 v15.5.0
PWS-IWF gained subscription management for N50 notifications and became a possible NF Service Consumer of the AMF's non-UE N2 message transfer and info subscribe/notify services.
- “the PWS-IWF shall manage the subscriptions for the corresponding notifications that may be received over N50.” TS 23.041 v16.4.0
- “shall be invoked by the NF Service Consumer (e.g. CBCF or PWS-IWF) to subscribe to the delivery of non-UE specific PWS information” TS 23.041 v16.4.0
- Subscription management in PWS-IWF TS 23.041CR0214
PWS-IWF reporting behaviour changed: the AMF reports the gNodeB ID in the Broadcast Empty Area List NG-RAN via the PWS-IWF when a response has no Broadcast Completed Area List.
- “If the AMF has received a WRITE-REPLACE WARNING RESPONSE without a Broadcast Completed Area List, then the gNodeB ID shall be included in the Broadcast Empty Area List NG-RAN instead.” TS 23.041 v17.6.0
- “This IE may only be included in the WRITE-REPLACE WARNING-REQUEST if the CBC sends the request to a PWS-IWF.” TS 29.168 v17.1.0
Defining Specifications
3GPP specifications that define or reference PWS-IWF, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 29.168 vj00 | SBc-AP Protocol Specification | Rel-19 read |