Wikipedia

Next Generation 911

(Redirected from Next Generation 9-1-1)

Next Generation 911 (abbreviated NG911) refers to an initiative aimed at updating the 911 service infrastructure in the United States and Canada to improve public emergency communications services in a growing wireless mobile society. In addition to calling 911 from a phone, it intends to enable the public to transmit text (see Text-to-911), images, video and data to the 911 center (referred to as a public safety answering point, or PSAP). The initiative also envisions additional types of emergency communications and data transfer.[1] This NG911 infrastructure is intended to replace the current services over time. The National Emergency Number Association (NENA) first identified the need for NG911 in 2000, and started development actions in 2003, and is nearing full definition and standards for NG911.[citation needed] 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 NG911.[2][3] On January 24, 2013, the CRTC announced the first step toward a Canadian implementation of NG911[4] 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.[5] Several US states have implemented versions of NG911, as of October 2013.[citation needed]

Purpose and history

edit

Planning for NG911 started in 2000 and was published in NENA's Future Path Plan in 2001.[6] NENA's NG911 Project began in 2003 and continues to an ultimate goal of establishing national NG911 architecture and operations standards, and implementation plans to accomplish advanced 911 systems and services. Public safety communications experts recognized that the nation's current 911 system was not capable of handling the text, data, images and video that are increasingly common in personal communications. The stated goal of a related USDOT project is: "To enable the general public to make a 911 “call” (any real-time communication – voice, text, or video) from any wired, wireless, or IP-based device, and allow the emergency services community to take advantage of advanced call delivery and other functions through new internetworking technologies based on open standards."[7] The project is aimed at supporting establishment of a national architecture for an NG911 system that would meet these goals, and to create a transition plan for NG911.

The "Proof of Concept" phase of the DOT project, using the architecture designed by NENA, was completed in 2008, and a report was issued on the results of a proof of concept demonstration conducted over the course of that year.[8] That report has served as a basic blueprint for planning and implementation of these capabilities. Actual implementation of these capabilities is expected to take several years, and will require changes to existing communications infrastructure, as well as changes to the way PSAPs operate.[9]

In 2000 Palm Beach County, FL (the largest county east of the Mississippi) implemented the first ESInet in the US. AT&T connecting multiple PSAPs utilizing the SIP protocol. In 2012, the State of Washington completed the first Statewide ESInet implementation in the US.[10]

In 2015 the FCC initiated a nationwide task force. The FCC Task Force on Optimal Public Safety Answering Point (PSAP) Architecture (Task Force or TFOPA) has been directed to study and report findings and recommendations on structure and architecture in order to determine whether additional consolidation of PSAP infrastructure and architecture improvements would promote greater efficiency of operations, safety of life, and cost containment, while retaining needed integration with local first responder dispatch and support.

Enabling technology

edit

The NG911 vision relies on 911 specific application functionality on an Emergency Services IP Network (ESInet) to deliver voice, video, text and data "calls" to the PSAP. The protocol used for delivering these "calls" will be the Session Initiation Protocol (SIP), or IP Multimedia Subsystem (IMS, which incorporates SIP).[11] The functional and interface standards developed by NENA describe general SIP and IMS-based architectures that allow responsible 911 Authorities flexibility in developing an infrastructure to support the envisioned features of NG911.[12]

Statutory authorization

edit

The 911 Improvement Act of 2008 [13] requires IP-enabled voice service providers to provide 911 service, allows state and tribal fees to pay for such services, and directs the Federal Communications Commission to gather information to facilitate these services. The Act also provides for grants to public agencies, and requires the 911 Implementation Coordination Office to develop a national plan for migrating to a national IP-enabled emergency network.

Today's 911 vs. Next Generation 911

edit

In today's 911 environment, the public can primarily make only emergency voice calls and Teletype calls (by deaf or hearing impaired persons). Only minimal data is delivered with these calls, such as automatic number identification, subscriber name and Automatic Location Identification, when available.

In the Next Generation 911 environment, the public will be able to make voice, text, or video emergency "calls" from any communications device via Internet Protocol-based networks. The PSAP of the future will also be able to receive data from personal safety devices such as Advanced Automatic Collision Notification systems, medical alert systems, and sensors of various types. The new infrastructure envisioned by the NG911 project will support national internetworking of 911 services, as well as transfer of emergency calls to other PSAPs—including any accompanying data. In addition, the PSAP will be able to issue emergency alerts to wireless devices in an area via voice or text message, and to highway alert systems.[14]

Example scenarios

edit
  • Deaf and hard of hearing people in the U.S. today sometimes use telecommunications devices for the deaf (TTYs or TDDs) or interpreting services to contact 911. Many deaf people use text messaging and instant messages to communicate with others, but unfortunately, today's 911 is not equipped to accept these media. This under-serviced demographic accounts for approximately 10% of the general population in Canada and the US (20% of those over 65 and 40% of those over 75).[15] In the NG911 environment, hearing and speech impaired individuals will be able to place such a call by sending a text message from their cell phone. They will be able to carry on a text conversation with 911 center personnel, and even send pictures or video when necessary.[16] In 2013, the Canadian Radio-television and Telecommunications Commission (CRTC) in Canada, announced the first phase of the country's NG911 services, implementation of Text with 911 (T911) for the deaf, hard of hearing, and speech impaired community.[17]
  • In the event of a major highway accident involving multiple vehicles, including a hazardous material vehicle, the local 911 center may receive many calls from different motorists. This can cause the center to be overloaded with calls, leading to initial confusion of the locations of the multiple crashes. The confusion can delay response times for the necessary equipment and services, which can, in turn, cost lives and delay return to normal traffic flow. In the NG911 environment, everyone in the vicinity with an Internet-connected device can be automatically notified to avoid the area. Highway message signs, and the 5-1-1 system can also display the warning. Any involved vehicle with an Advanced Automatic Collision Notification system automatically sends important crash data to the 911 center, which can dispatch emergency responders even if the passengers are unable to respond.[18]

Stakeholders and technologies involved

edit

Many pieces of the existing communications and data infrastructure will require modification to make NG911 a reality. The private companies and public agencies that provide these goods and services will be significantly affected. Chief among these are:

Other major stakeholders include:

  • State and local 911 agencies
  • Public safety and emergency management agencies
  • Emergency services industry
  • Federal departments, including Transportation, Commerce, Homeland Security, Justice and the Federal Communications Commission
  • National organizations with active interests in 911
  • IT research community
  • Standards community

Major contributors and stakeholders in the standards community include:

The NENA NG911 Project and the DOT's NG911 Initiative look to facilitate the involvement of all these stakeholders going forward in order to develop the architecture and migration plan necessary to make NG911 a functional reality.[20]

Public network infrastructure impacts

edit

In order for a useful connection to be made between the Public Safety Answering Point and person reporting the emergency, a number of changes need to be made to the existing infrastructure. For example, if a user is sending a text message, perhaps with video attached, the data needs to be routed to the PSAP that serves the area where the person is currently, and the location of the wireless device must accompany the message. The person's wireless carrier will receive the message first, then forward the message to the appropriate NG911 system, which routes to the appropriate PSAP along with the location information. Since several different protocols may be used by the wireless device (SMS or XMPP text messaging, MMS (Multimedia Messaging Service) or Wireless Application Protocol for multimedia), translation to a common protocol may be required prior to forwarding. In the case of Advanced Automatic Collision Notification data, the service provider must be able to similarly route this data, along with location data toward the PSAP serving the area where the collision occurred. For the PSAP to be able to send out automatic notifications to all wireless devices currently operating in the area of an emergency, a similar routing mechanism must exist in the opposite (outgoing) direction. Here again, the wireless carrier will be forwarding information.[21]

PSAP infrastructure impacts

edit

Local PSAP network impacts

edit

A High availability IP infrastructure interface will be needed at the PSAP for it to be able to send and receive all this data. A key element of this will be equipment and software to support IP communications. Internal routing of the emergency communications to the appropriate systems (i.e., text, picture and video data to the Computer-assisted dispatch system, and simultaneously to the communications recording system) will require modifications to the existing PSAP network equipment and software. Some of these changes will be non-trivial.

Local wireless infrastructure impacts

edit

Since some of the emergency communications data will have to be forwarded to field units such as police and fire vehicles, changes will be required to the software running on the terminals that receive the data, and on those that transmit the data.[2] If the existing wireless communications system is Project 25 compliant, little or no change will be required to the transmit/receive equipment itself, since it already supports transmission of any type of data.[22]

Communications recording system impacts

edit

NG911 requires that these new types of emergency communications (text, pictures, video) be recorded along with the voice communications that have traditionally been recorded. Most existing communications recorders are not capable of recording anything other than audio, and major changes may be required to bring these devices into NG911 compliance. This may require a significant investment on the part of the PSAPs if the existing equipment cannot be modified to support the new requirements.

Human resource impacts

edit

There will also be significant operational impacts on the PSAP "call takers", dispatchers (those who dispatch emergency vehicles and personnel), and on their managers. Workloads are expected to increase, and significant new training will be required for those responsible for responding to these new communication types. Similar impacts on both public and private emergency response providers, and on Telematics and medical services providers are also anticipated.[2][23]

Accessibility

edit

Various features of NG911, including text messaging and video messaging, provide accessible features for those who cannot use a regular telephone. It is also considered as a long-term replacement for the use of TDD/TTY devices for the deaf, currently in use with 911. TDD/TTY devices are considered legacy systems, and may be replaced by other real-time text technologies that transmit text as it is being typed. In Europe, real-time text is used in Reach 112 emergency service trials. Reach 112 is a European equivalent of the accessible features of NG911.

See also

edit

References

edit
  1. ^ U.S. Dept. Of Transportation NG911 initiative
  2. ^ a b c Mission Critical Magazine: "Greater Expectations"
  3. ^ "T9-1-1 CRTC INTERCONNECTION STEERING COMMITTEE REPORT"
  4. ^ "CRTC announces enhancements to 911 services for Canadians with hearing or speech impairments"
  5. ^ "CRTC reviewing next-generation 9-1-1 services"
  6. ^ "NENA NG911 Future Path Plan". Archived from the original on 2009-03-27. Retrieved 2009-03-23.
  7. ^ NG911 Initiative Overview
  8. ^ NG911 Proof Of Concept Test Report
  9. ^ DOT NG911 Overview
  10. ^ In 2009, Washington State signed a contract (contract number E09-196) with Qwest Communications to implement a statewide Next Generation 911 ESInet. This implementation was completed with the connection of the last PSAP in April 2012.
  11. ^ NENA i3 TECHNICAL REQUIREMENTS DOCUMENT
  12. ^ NENA Functional and Interface Standards for Next Generation 9-1-1
  13. ^ 911 Improvement Act of 2008
  14. ^ Today's 9-1-1 vs. Future 9-1-1
  15. ^ World Health Organization: "Global burden of hearing loss"
  16. ^ Next Generation 9-1-1 System Preliminary Concept of Operations
  17. ^ Cellular News: "Canada's Wireless Industry Commends CRTC Decision to Implement Text with 911"
  18. ^ NG911 Examples and Scenarios
  19. ^ NG911 technologies
  20. ^ NG911 stakeholder involvement
  21. ^ NG911 Operational Needs Archived September 16, 2008, at the Wayback Machine
  22. ^ Telecommunications Industry Association standard "TIA.102" (series) Archived 2011-11-06 at the Wayback Machine
  23. ^ Operational Impacts and Needs
edit
Retrieved from "https://en.wiki.x.io/w/index.php?title=Next_Generation_911&oldid=1242971755"