NG9-1-1 Project
In the past 20 years, advancements in modern communications technology have created the need for a more advanced system to access emergency care. While the existing 9-1-1 system has been a success story for more than 30 years, it has been stretched to its limit as technology advances.
New wireless and IP-based communications devices are being developed at a rapid rate, offering capabilities such as text and video messaging. Unfortunately, the current 9-1-1 system was never intended to receive calls and data from these new and emerging technologies.
As a result, through cumbersome adaptations, E9-1-1 is being asked to perform functions it was not designed to handle. In short, the nation’s 9-1-1 systems are in need of a significant overhaul.

NENA identified this need in 2000, published the Future Path Plan in 2001, and began development activities toward this end in 2003.

Documents available at the bottom of this page:
  • Why NG9-1-1?
  • What is NG9-1-1? excerpt from the document on this page
  • NG9-1-1 Transition Policy Maker Blueprint
  • Policy Statement on NG9-1-1 Transition
  • 9-1-1: The Next Generation NENA's Blueprint Steers 9-1-1 Into the Future

There are also a listing of NENA Standards and Documents at the bottom of this page as well, which Includes NENA 08-003, the NG9-1-1 architecture standard.


NENA's NG9-1-1 Project Structure

  • The NG9-1-1 Project Lead Team provides overall project activity identification, prioritization and management. Project leader is Brandon Abley, ENP, NENA Technical Issues Director.
  • NENA Development Group provides Committee support for all areas of development for NG9-1-1.
  • Next Generation Partner Program (NGPP): policy issues around NG 9-1-1 and NG emergency communications, coordinating with the NENA national Reg/Leg Committee
  • NG9-1-1 Transition Planning Committee (NGTPC): transition & implementation guidelines
  • A NENA Certification and Accreditation Program is pending

Project Results and Status

Currently, we are expecting that most NENA Requirements, Standards and Information documents for NG9-1-1 will be completed by 4Q2015. The primary architectural and database standards were posted prior to 2014. Specific results, both current and pending, will be available at the Overall NG9-1-1 Status page.

Why NG9-1-1 ?

  • Fully replace Enhanced 9-1-1, with all capabilities and functions in place today

It is essential that all standard features of E9-1-1 are maintained as we change over to a new base technology (IP) using entirely different software and database control mechanisms to perform 9-1-1 system capabilities and features, both for the callers and PSAPs. This applies to seldom used but critical features for dealing automatically with real time call routing and delivery problems, or troubleshooting call and data issues. All current originating service types must continue to be supported seamlessly, with no service dropout during the transition from E9-1-1 to NG9-1-1.

  • Add capabilities to support changes for current and new types of Originating Service Providers

E9-1-1 supports voice calling for wireline, cellular, and VoIP service providers today. There are current and certainly future needs for different and new calling technologies, including non-voice messaging of various types, devices generating data-only messages (such as sensors), photo and video transmission, and unknown future services. A primary objective is to establish a common IP based interface that developers can design to as they develop new services, so that 9-1-1 can be planned for and then connected to quickly as 9-1-1 call and message generating services are introduced to the public.

  • Add flexibility for the PSAPs and 9-1-1 Authorities

These range from the ability to transfer calls, messages, and data between any PSAPs on any interconnected NG9-1-1 system anywhere in the country (and beyond), ability to directly activate alternate routing much more quickly, to controlling data flow. The PSAP will be able to access a wide range of supportive databases and share new and more robust forms of data to facilitate call processing, emergency response and comprehensive incident management. Basic tools to support disaster related 9-1-1 call control and to handle non-voice call types are also involved.

  • Add capabilities to integrate and interoperate with emergency entities beyond the PSAP

Other emergency and public safety related entities will be able to interconnect to the NG9-1-1 network and system, and be able to receive calls and data sent by the NG9-1-1 system or PSAPs, as well as (with access controls) acquire and pass data between all entities. Inherent in this portion is support for disaster management and intercommunications with and between PSAPs, EOCs, DHS, and other emergency management entities.

All of the above four areas of system development also require that many policy, educational and operations issues be treated as part of the overall Project prior to implementation. The addition of capabilities beyond those of today’s E9-1-1 systems, for instance, drive needs in these areas that are not easily derived from past practice or experience.

System and procedural tools are required to support 9-1-1 Authorities and PSAPs, and to deal with additional data sources, different types of calling technologies and changes in call processing times at the PSAP, and new features that require new procedures. A variety of educational products are required to allow understanding, and support preparation, smooth transition and ongoing operation of NG9-1-1.

Guidelines and recommendations for the transition of stakeholders to NG9-1-1 are critical. All of these aspects are represented and, as additional perspectives occur, periodically updated in the development activities in the NG9-1-1 Project plan.

Next Generation 9-1-1Summary Description

A system comprised of Emergency Services IP networks (ESInets), IP-based Software Services and Applications, Databases and Data Management processes that are interconnected to Public Safety Answering Point premise equipment. The system provides location-based routing to the appropriate emergency entity. The system uses additionally available data elements and business policies to augment PSAP routing. The system delivers geodetic and/or civic location information and the call back number.

The system supports the transfer of calls to other NG9-1-1 capable PSAPs or other authorized entities based on and including accumulated data. NG9-1-1 provides standardized interfaces for call and message services, processes all types of emergency calls including non-voice (multi-media) messages, acquires and integrates additional data useful to call routing and handling for appropriate emergency entities. NG9-1-1 supports all E9-1-1 features and functions and meets current and emerging needs for emergency communication from caller to Public Safety entities.

For a more detailed and potentially more up to date description of NG9-1-1 see
"What is NG9-1-1?" This document covers structure and components of NG9-1-1 and the overall roles that NENA plays in the development of NG9-1-1. All questions and comments should be addressed to Brandon Abley, NENA Technical  Director.

Return to Top

Documents Related to NG9-1-1 - Not listed as Standards

NG9-1-1 & VoIP Standards & Other Documents

More InfoHide Info ]
The Voice over Internet Protocol (VoIP) / Packet Committee’s goal is to identify and solve technical issues relating to call delivery from VoIP sources and migrate existing 9-1-1 technologies into a packet environment for both voice and data. Identified technical issues are handled via Working Groups that are formed to accomplish specific goals, which usually result in some type of official NENA documentation.
Item Name Posted By Date Posted
75-502 v1 - NG9-1-1 Security (NG-SEC) Checklist Link  more ] Administration 9/4/2013
75-001 v1 - NG Security Link  more ] Administration 9/4/2013
04-503 v1 - PSAP Security Link  more ] Administration 9/4/2013
INF-003 NG9-1-1 Potential Points of Demarcation Link  more ] Administration 9/4/2013
08-001 v2 - Interim VoIP Architecture - i2 Link  more ] Administration 12/5/2011
08-002 v1 - Func Interface StandardsNG91-1 (i3) Link  more ] Administration 12/5/2011
08-003 v1 - Detailed Func & Interface Specs (i3) Link  more ] Administration 12/12/2011
08-501 v1 - Network Interface to IP Capable PSAP Link  more ] Administration 12/5/2011
08-502 v1 - E9-1-1 Requirements Link  more ] Administration 12/5/2011
08-503 v1 - VoIP Characteristics Link  more ] Administration 12/5/2011
08-504 v1 - VoIP Stds Development Organizations Link  more ] Administration 12/5/2011
08-505 v1 - Location Determination IP 9-1-1 Link  more ] Administration 12/5/2011
08-506 v1 - Emer. Serv. IP Network Design NG91-1 Link  more ] Administration 1/25/2012
08-751 v1 - i3 Requirements Long Term Definition Link  more ] Administration 12/5/2011
08-752 v1 - Location Info to Support IP 9-1-1 Link  more ] Administration 12/5/2011
57-503 Notification ERDB-VPC of ESN Changes Link  more ] Administration 7/17/2013
57-750 V1 NG9-1-1 System & PSAP Operational Feat. Link  more ] Administration 10/5/2012
58-001 IP PSAP (replaced by 57-750) Link  more ] Administration 12/5/2011
58-501 IP PSAP Features (replaced by 57-750) Link  more ] Administration 12/5/2011
58-502 VoIP Funding & Regulatory Issues Link  more ] Administration 12/5/2011
73-501 v1 - Non-Voice-Centric Emergency Svcs Link  more ] Administration 12/5/2011

NG9-1-1 Transition Planning Standards & Documents

More InfoHide Info ]
NG Transition Planning Documents.
Item Name Posted By Date Posted
INF-008.1 (prev. 77-501) NG9-1-1 Transition Plan Link  more ] Administration 11/21/2013