Wireless Emergency Alerts

From Infogalactic: the planetary knowledge core
Jump to: navigation, search
File:Screenshot-of-CMAS-test-dialogue-19-Feb-2014.png
(Old) example of a CMAS test alert as shown on an Android phone.

Wireless Emergency Alerts (WEA, formerly known as the Commercial Mobile Alert System (CMAS), and prior to that as the Personal Localized Alerting Network (PLAN)),[1] is an alerting network in the United States designed to disseminate emergency alerts to mobile devices such as cell phones and pagers.

Background

The Federal Communications Commission proposed and adopted the network structure, operational procedures and technical requirements in 2007 and 2008 in response to the Warning, Alert, and Response Network (WARN) Act passed by Congress in 2006, which allocated $106 million to fund the program.[2] CMAS will allow federal agencies to accept and aggregate alerts from the President of the United States, the National Weather Service (NWS) and emergency operations centers, and send the alerts to participating wireless providers who will distribute the alerts to their customers with compatible devices via Cell Broadcast, a technology similar to SMS text messages that simultaneously delivers messages to all phones using a cell tower instead of individual recipients.[3][4]

The government plans to issue three types of alerts through this system:

  • Alerts issued by the President of the United States.
  • Alerts involving imminent threats to safety of life, issued in two different categories: extreme threats and severe threats
  • AMBER Alerts.[3]

When the alert is received, a sound is played if the ringer is on. On nearly all devices, the Emergency Alert System radio/TV attention signal sounds in a predetermined pattern.[5]

The system is a collaborative effort between the Federal Emergency Management Agency (FEMA), the Department of Homeland Security Science and Technology Directorate (DHS S&T), the Alliance for Telecommunications Industry Solutions (ATIS), and the Telecommunications Industry Association (TIA),[6]

Participation

Within ten months of FEMA making the government’s design specifications for this secure interface for message transfer available, wireless service providers choosing to participate in CMAS must begin development and testing of systems which will allow them to receive alerts from alert originators and distribute them to their customers.[7] Systems must be fully deployed within 28 months of the December 2009 adoption of such standards and are expected to be delivering alert messages to the public by 2012.[6] Although not mandatory, several wireless providers, including T-Mobile, AT&T, Sprint, and Verizon have announced their willingness to participate in the system.[2] Providers who do not wish to participate must notify their customers. Some phones which are not CMAS-capable may require only a software upgrade; while others may need to be replaced entirely.[3]

CMAS messages, although displayed similarly to SMS text messages, are always free and are routed through a separate service which will give them priority over voice and regular text messages in congested areas.[3] Customers who have the capability of receiving CMAS alerts (also known as PLAN[citation needed] and WEA) will be automatically signed up by their carrier.[8] If they do not want to participate they may opt to block most CMAS messages, however CMAS regulations[9] prohibit participating carriers from configuring phones to allow users to opt out of messages issued by the President.[3]

Public television stations are also required by the FCC to act as a distribution system for CMAS alerts. Within 18 months of receiving funding from the Department of Commerce, all public television stations must be able to receive CMAS alerts from FEMA and transmit them to participating wireless service providers.[7]

National Weather Service

The Commercial Mobile Alert System (CMAS), interface to the Wireless Emergency Alerts (WEA) service, went live in April 2012.[10] The NWS began delivering its Wireless Emergency Alerts on June 28, 2012.[11][12]

Warning types sent via CMAS include tornado, flash flood, dust storm, hurricane, and extreme wind warnings; severe thunderstorm warnings are not included due to their frequency in many areas of the United States. Also, until November 2013, blizzard and ice storm warnings were also included in CMAS; they were discontinued based on customer feedback[13] due to such warnings typically issued well in advance of approaching winter storms, thus not representing an immediate hazard. While blizzard and ice storm warnings are no longer sent to phones by the National Weather Service, some local authorities continue to send winter weather related alerts at their discretion; for example in New York City during the January 2015 North American blizzard, alerts were sent to people's cell phones to warn users of a travel ban on New York City streets.[14]

Notable uses

  • Boston Marathon bombings — A shelter-in-place warning was issued via CMAS by the Massachusetts Emergency Management Agency[15]
  • A child abduction alert in the New York City region in July 2013 for a 7-month-old boy who had been abducted. The massive inconvenience caused by the 4:00 am timing raised concerns that many cellphone users would choose to disable alerts.[16]
  • A blizzard warning in February 2013 for New York City.[17] (Note: As of November 2013, blizzard warnings are no longer included in the CMAS program).[13]
  • A shelter-in-place warning for New York City in October 2012 due to Hurricane Sandy.[18]
  • A child abduction alert in the New York City Region on June 30th 2015 for a 3 year old girl who had been abducted.[19]

See also

References

  1. Lua error in package.lua at line 80: module 'strict' not found.
  2. 2.0 2.1 Lua error in package.lua at line 80: module 'strict' not found.
  3. 3.0 3.1 3.2 3.3 3.4 Lua error in package.lua at line 80: module 'strict' not found.
  4. Lua error in package.lua at line 80: module 'strict' not found.
  5. Lua error in package.lua at line 80: module 'strict' not found.
  6. 6.0 6.1 [1][dead link]
  7. 7.0 7.1 Lua error in package.lua at line 80: module 'strict' not found.
  8. Lua error in package.lua at line 80: module 'strict' not found.
  9. [2][dead link]
  10. Lua error in package.lua at line 80: module 'strict' not found.
  11. Lua error in package.lua at line 80: module 'strict' not found.
  12. Lua error in package.lua at line 80: module 'strict' not found.
  13. 13.0 13.1 Lua error in package.lua at line 80: module 'strict' not found.
  14. Lua error in package.lua at line 80: module 'strict' not found.
  15. Lua error in package.lua at line 80: module 'strict' not found.
  16. Lua error in package.lua at line 80: module 'strict' not found.
  17. Lua error in package.lua at line 80: module 'strict' not found.
  18. Lua error in package.lua at line 80: module 'strict' not found.
  19. Lua error in package.lua at line 80: module 'strict' not found.

External links