Common Alerting Protocol

Last updated

The Common Alerting Protocol (CAP) is an XML-based data format for exchanging public warnings and emergencies between alerting technologies. CAP allows a warning message to be consistently disseminated simultaneously over many warning systems to many applications, such as Google Public Alerts and Cell Broadcast. CAP increases warning effectiveness and simplifies the task of activating a warning for responsible officials.

Contents

Standardized alerts can be received from many sources and configure their applications to process and respond to the alerts as desired. Alerts from the Department of Homeland Security, the Department of the Interior's United States Geological Survey, and the United States Department of Commerce's National Oceanic and Atmospheric Administration (NOAA), and state and local government agencies can all be received in the same format by the same application. That application can, for example, sound different alarms, based on the information received.

By normalizing alert data across threats, jurisdictions, and warning systems, CAP also can be used to detect trends and patterns in warning activity, such as trends that might indicate an undetected hazard or hostile act. From a procedural perspective, CAP reinforces a research-based template for effective warning message content and structure.

The CAP data structure is backward-compatible with existing alert formats including the Specific Area Message Encoding (SAME) used in NOAA Weather Radio and the broadcast Emergency Alert System as well as new technology such as the Wireless Emergency Alerts (WEA), while adding capabilities such as the following:

Background

The US National Science and Technology Council (NSTC) November 2000 report on "Effective Disaster Warnings" recommended that "standard method should be developed to collect and relay instantaneously and automatically all types of hazard warnings and reports locally, regionally and nationally for input into a wide variety of dissemination systems." [1]

In 2001, an international independent group of over 120 emergency managers that was convened online by California emergency telecommunications expert Art Botterell began specifying and prototyping the Common Alerting Protocol data structure based on the recommendations of the NSTC report. The project was embraced by the non-profit Partnership for Public Warning and a number of international warning system vendors. [2] A series of field trials and long-term demonstration projects during 2002-03 led to the submission of a draft CAP specification to the OASIS standards process for formalization.

The CAP 1.0 specification was approved by OASIS in April 2004. Based on experience with CAP 1.0, the OASIS Emergency Management Technical Committee adopted an updated CAP 1.1 specification in October 2005. [3] [4] At a meeting in Geneva in October 2006 the CAP 1.1 specification was taken under consideration by the International Telecommunication Union's Standardization Sector for adoption as an ITU-T recommendation. CAP was subsequently adopted as Recommendation X.1303. [5]

CAP specification version 1.2 has been available since July 2010 at the OASIS website. [6]

Implementation

Worldwide

In 2007, the International Telecommunication Union, Telecommunication Standardization Sector (ITU-T) adopted the Common Alerting Protocol as Recommendation X.1303. [7] [8] The recommendation annex contains an authoritative ASN.1 module translation of the CAP XML schema that may be useful for some implementations. Rec. X.1303 is within the remit of ITU‑T Study Group 17 (Security), Rapporteur Group on Cybersecurity (Q.4/17) for purposes of further evolution of the standard. [9]

Australia

The Australian Government Standard for Common Alerting Protocol (CAP-AU-STD, 2012) was developed by a CAP-AU-STD stakeholder group comprising federal agencies Emergency Management Australia, the Bureau of Meteorology, GeoScience Australia, Department of Agriculture, Fisheries and Forestry and the Department of Health as well as a number of State Government authorities and emergency services agencies. The project was co-ordinated by the Australian Government Attorney-General's Department (Australian Emergency Management). [10] [11]

Canada

In Canada, a working group composed of public alerting practitioners and government agencies has developed a CAP Canadian Profile (CAP-CP) based on CAP but specialized to address the needs of Canadian public alerting stakeholders, such as bilingualism, geocoding for Canada, managed lists of locations and events, etc. The Canadian government has adopted CAP-CP for its National Public Alerting System (NPAS) project. The CAP‑CP working group, along with stakeholders and projects such as the Canadian Public Safety Operations Organization (CanOps) and Netalerts' Sarnia Lambton trial, are now working with and refining CAP‑CP for national application in Canada.[ citation needed ]

CAP has been implemented for a small-scale, grassroots hazard information system in Sri Lanka following the 2004 Indian Ocean Tsunami. This implementation was part of the "HazInfo Project", funded by Canada's International Development Research Centre. [12]

The province of Alberta adopted CAP as part of its Alberta Emergency Alert system. In March 2015, Alert Ready, a national public warning system based upon CAP-CP, was officially launched. Participation in the system by all broadcasters and television providers is mandated by the Canadian Radio-television and Telecommunications Commission. [13] [14] [15]

Germany

The Federal Office for Citizen Protection and Disaster Support (Bundesamt für Bevölkerungsschutz und Katastrophenhilfe, BBK) is working on an implementation based on CAP 1.2, which will allow for Internet-based access to data provided by the nation's modular warning system MoWaS. [16] The development of MoWaS is based on the satellite-based warning system SatWaS from 2001, which only provides information to less than 150 state and media entities. In case no broadcast receiver, like a radio or television, is running nearby, the resulting warning effect of SatWaS would be severely limited, because many state-run emergency sirens have been left unmaintained or were dismantled altogether. The use of CAP support in MoWaS should alleviate this problem.

Italy

The Department of Firefighters, Public Rescue and Civil Defence (Dipartimento dei Vigili del Fuoco, del Soccorso Pubblico e della Difesa Civile ) of the Italian Ministry of the Interior adopted the CAP protocol with two Ministerial Decrees in 2008 and 2011. Since then, its 100 provincial control rooms, 18 regional control rooms and the national control centre exchange a daily average of 25,000 CAP private messages concerning rescue operations in real time. As per the decrees, any emergency stakeholder in Italy which wants to exchange or share data with the Fire Corps in the course of large scale emergency or rescue operations has to adopt the CAP protocol.

The first use of CAP protocol in a civil protection activity in Italy was recorded in 2009, in the aftermath of the Central Italy Earthquake, when the Fire Corps exchanged data with the Ministry for Cultural Heritage to coordinate their efforts in designing and implementing provisional measures for monuments and historical buildings.

On April 5, 2017, an agreement between the "Corpo Nazionale dei Vigili del Fuoco" and the "Arma dei Carabinieri" has been signed to improve the forest fire fighting activities. The interoperability of data exchange that the agreement allows is based on the use of the CAP protocol.

United States

On September 30, 2010, the Federal Emergency Management Agency (FEMA) officially adopted CAP as the protocol for its new Integrated Public Alert and Warning System (IPAWS), which is designed to disseminate emergency messages via various platforms, including broadcast media (Emergency Alert System), wireless devices (Wireless Emergency Alerts), and other platforms. [17] [18]

Related Research Articles

<span class="mw-page-title-main">OSI model</span> Model of communication of seven abstraction layers

The Open Systems Interconnection model is a conceptual model that 'provides a common basis for the coordination of [ISO] standards development for the purpose of systems interconnection'. In the OSI reference model, the communications between a computing system are split into seven different abstraction layers: Physical, Data Link, Network, Transport, Session, Presentation, and Application.

Signalling System No. 7 (SS7) is a set of telephony signaling protocols developed in the 1970s, which is used to set up and tear down telephone calls in most parts of the world-wide public switched telephone network (PSTN). The protocol also performs number translation, local number portability, prepaid billing, Short Message Service (SMS), and other services.

The Organization for the Advancement of Structured Information Standards is a nonprofit consortium that works on the development, convergence, and adoption of open standards for cybersecurity, blockchain, Internet of things (IoT), emergency management, cloud computing, legal data exchange, energy, content technologies, and other areas.

Specific Area Message Encoding (SAME) is a protocol used for framing and classification of broadcasting emergency warning messages. It was developed by the United States National Weather Service for use on its NOAA Weather Radio (NWR) network, and was later adopted by the Federal Communications Commission for the Emergency Alert System, then subsequently by Environment Canada for use on its Weatheradio Canada service. It is also used to set off receivers in Mexico City and surrounding areas as part of the Mexican Seismic Alert System (SASMEX).

<span class="mw-page-title-main">NOAA Weather Radio</span> 24-hour network of VHF FM weather radio stations in the United States

NOAA Weather RadioNWR; also known as NOAA Weather Radio All Hazards is an automated 24-hour network of VHF FM weather radio stations in the United States (U.S.) that broadcast weather information directly from a nearby National Weather Service office. The routine programming cycle includes local or regional weather forecasts, synopsis, climate summaries or zone/lake/coastal waters forecasts. During severe conditions the cycle is shortened into: hazardous weather outlooks, short-term forecasts, special weather statements or tropical weather summaries. It occasionally broadcasts other non-weather related events such as national security statements, natural disaster information, environmental and public safety statements, civil emergencies, fires, evacuation orders, and other hazards sourced from the Federal Communications Commission's (FCC) Emergency Alert System. NOAA Weather Radio uses automated broadcast technology that allows for the recycling of segments featured in one broadcast cycle seamlessly into another and more regular updating of segments to each of the transmitters. It also speeds up the warning transmitting process.

The Message Transfer Part (MTP) is part of the Signaling System 7 (SS7) used for communication in Public Switched Telephone Networks. MTP is responsible for reliable, unduplicated and in-sequence transport of SS7 messages between communication partners.

Connectionless-mode Network Service (CLNS) or simply Connectionless Network Service is an OSI network layer datagram service that does not require a circuit to be established before data is transmitted, and routes messages to their destinations independently of any other messages. As such it is a "best-effort" rather than a "reliable" delivery service. CLNS is not an Internet service, but provides capabilities in an OSI network environment similar to those provided by the Internet protocol suite. The service is specified in ISO/IEC 8348, the OSI Network Service Definition

OMA SpecWorks, previously the Open Mobile Alliance (OMA) is a standards organization which develops open, international technical standards for the mobile phone industry. It is a nonprofit Non-governmental organization (NGO), not a formal government-sponsored standards organization as is the International Telecommunication Union (ITU): a forum for industry stakeholders to agree on common specifications for products and services.

<span class="mw-page-title-main">H.248</span>

The Gateway Control Protocol is an implementation of the media gateway control protocol architecture for providing telecommunication services across a converged internetwork consisting of the traditional public switched telephone network (PSTN) and modern packet networks, such as the Internet. H.248 is the designation of the recommendations developed by the ITU Telecommunication Standardization Sector (ITU-T) and Megaco is a contraction of media gateway control protocol used by the earliest specifications by the Internet Engineering Task Force (IETF). The standard published in March 2013 by ITU-T is entitled H.248.1: Gateway control protocol: Version 3.

<span class="mw-page-title-main">Prosigns for Morse code</span> Predefined shorthand signals

Procedural signs or prosigns are shorthand signals used in Morse code radio telegraphy procedure, for the purpose of simplifying and standardizing radio communication protocol. They are separate from Morse code abbreviations, which consist mainly of brevity codes that convey messages to other parties with greater speed and accuracy.

<span class="mw-page-title-main">H.323</span> Audio-visual communication signaling protocol

H.323 is a recommendation from the ITU Telecommunication Standardization Sector (ITU-T) that defines the protocols to provide audio-visual communication sessions on any packet network. The H.323 standard addresses call signaling and control, multimedia transport and control, and bandwidth control for point-to-point and multi-point conferences.

<span class="mw-page-title-main">Cell Broadcast</span> Method of sending messages to multiple mobile telephone users in a defined area at the same time

Cell Broadcast (CB) is a method of sending messages to multiple mobile telephone users in a defined area at the same time. It is defined by the ETSI’s GSM committee and 3GPP and is part of the 2G, 3G, 4G LTE (telecommunication) and 5G standards. It is also known as Short Message Service-Cell Broadcast (SMS-CB) or CB SMS.

CANALERT was one of the names for the Government of Canada's series of initiatives between 2003–2009 to develop an all-channel national public alerting system. Work began on CANALERT in 2003 with the First Canadian Public Alerting Forum and Workshop and continued with another forum in 2005. Industry Canada was the lead federal agency for this initiative and worked closely with provincial and territorial governments to define guidelines, procedures, and protocols, including a Canadian profile for the Common Alerting Protocol (CAP) standard for exchanging alert messaging across communications technologies.

<span class="mw-page-title-main">Centre for Development of Telematics</span>

The Centre for Development of Telematics (C-DOT) is an Indian Government owned telecommunications technology development centre. It was established in 1984 with initial mandate of designing and developing digital exchanges. C-DOT has expanded to develop intelligent computer software applications. It has offices in Delhi, Bangalore and Kolkata. It is one of the few government organisations in India which have been appraised at Maturity Level 5 of CMMI-DEV v1.3.

The HEARO Local Alert Receiver was an emergency management tool to relay and display informational text messages in English, Spanish, French and German using RDS technology. It notified local residents in the event of an emergency within a matter of seconds. HEARO carried NOAA weather warnings and other public safety text alerts, using FM radio infrastructure with a 60-hour battery life, HEARO was able to work when electricity, telephone and Internet were unavailable. viaRadio Corporation of Melbourne, Florida manufactured and distributed HEARO receivers.

Next Generation 9-1-1 refers to an initiative aimed at updating the 9-1-1 service infrastructure in the United States and Canada to improve public emergency communications services in a growing wireless mobile society. In addition to calling 9-1-1 from a phone, it intends to enable the public to transmit text, images, video and data to the 9-1-1 center. The initiative also envisions additional types of emergency communications and data transfer. This NG9-1-1 infrastructure is intended to replace the current services over time. The National Emergency Number Association (NENA) first identified the need for NG9-1-1 in 2000, and started development actions in 2003, and is nearing full definition and standards for NG9-1-1. Since 2006, the US Department of Transportation (DOT) in the United States and the Canadian Radio-television and Telecommunications Commission (CRTC) in Canada have been leading their respective initiatives, which include research and development projects aimed at advancing NG9-1-1. On January 24, 2013, the CRTC announced the first step toward a Canadian implementation of NG9-1-1 and, in March 2016, began a consultation with the public to discuss what services should be offered, who will play a role in offering these services and how these services should be paid for. Several US states have implemented versions of NG9-1-1, as of October 2013.

The Emergency Data Exchange Language (EDXL) is a suite of XML-based messaging standards that facilitate emergency information sharing between government entities and the full range of emergency-related organizations. EDXL standardizes messaging formats for communications between these parties. EDXL was developed as a royalty-free standard by the OASIS International Open Standards Consortium.

The Integrated Public Alert and Warning System (IPAWS) is an architecture that unifies the United States' Emergency Alert System, National Warning System, Wireless Emergency Alerts, and NOAA Weather Radio, under a single platform. IPAWS was designed to modernize these systems by enabling alerts to be aggregated over a network and distributed to the appropriate system for public dissemination.

Operations support systems (OSS), operational support systems in British usage, or Operation System (OpS) in NTT, are computer systems used by telecommunications service providers to manage their networks. They support management functions such as network inventory, service provisioning, network configuration and fault management.

<span class="mw-page-title-main">Alert Ready</span> National alerting system of Canada

The National Public Alerting System, branded as Alert Ready, is the national warning system in Canada, broadcast to Canadian television, radio, and wireless devices.

References

  1. ↑ "Archived copy" (PDF). Archived from the original (PDF) on 2006-05-13. Retrieved 2006-05-03.{{cite web}}: CS1 maint: archived copy as title (link)
  2. ↑ http://www.ppw.us Archived 2002-09-28 at the Wayback Machine
  3. ↑ "OASIS - Committees - OASIS Emergency Management TC". Archived from the original on 2003-02-07.
  4. ↑ http://www.oasis-open.org/committees/download.php/14759/emergency-CAPv1.1.pdf [ bare URL PDF ]
  5. ↑ "X.1303 : Common alerting protocol (CAP 1.1)". International Telecommunication Union. Retrieved 2019-04-30.
  6. ↑ http://docs.oasis-open.org/emergency/cap/v1.2/CAP-v1.2-os.pdf [ bare URL PDF ]
  7. ↑ "ITU Telecommunication Standardization Sector". ITU.
  8. ↑ tsbmail. "X.1303 : Common alerting protocol (CAP 1.1)". itu.int.
  9. ↑ "ITU-T Study Group 17 (Study Period 2013-2016)". itu.int.
  10. ↑ "Emergency Management Capabilities - Attorney General's Department". ag.gov.au. Archived from the original on 2018-01-15. Retrieved 2018-01-15.
  11. ↑ "Common Alerting Protocol – Australia (CAP-AU-STD) - Data.gov.au". data.gov.au.
  12. ↑ "Evaluating Last-Mile Hazard Information Dissemination (HazInfo)". lirneasia.net. Archived from the original on 2007-07-09. Retrieved 2007-01-31.
  13. ↑ "Public Alerting Bulletin to Last Mile Distributors" (PDF). Pelmorex. Archived from the original (PDF) on 6 May 2015. Retrieved 9 June 2015.
  14. ↑ "Alberta emergency system goes digital". CBC News. Retrieved 9 June 2015.
  15. ↑ "Digital alert system hard to decipher: critics". CBC News. Retrieved 9 June 2015.
  16. ↑ "Bundesamt für Bevölkerungsschutz und Katastrophenhilfe - Warnmultiplikatoren".
  17. ↑ Oxenford, Davis Wright Tremaine LLP-David D.; Tol, Jennifer; Frewer (10 February 2012). "FCC revises emergency alert system rules; reminds participants of June 30, 2012 CAP compliance deadline". Lexology.com. Retrieved 2019-08-24.
  18. ↑ "FEMA Adopts Digital Message Format for EAS CAP Standard, Triggering 180-Day Clock for Compliance". Broadcast Law Blog. 2010-09-30. Retrieved 2019-08-24.
This page is based on this Wikipedia article
Text is available under the CC BY-SA 4.0 license; additional terms may apply.
Images, videos and audio are available under their respective licenses.