Edit This Favorite

Name:

Category:

Share:

YesNo, Keep Private

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.

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 Roger Hixson, NENA Technical Issues Director.

NG9-1-1 & VoIP Standards & Other Documents

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.

This document is the NENA recommended standard for the i2 architecture to support the interconnection of VoIP domains with the existing Emergency Services Network infrastructure in support of the migration toward end-to-end emergency calling over the VoIP networks between callers and PSAPs.

Major changes in the existing emergency services architecture are being driven by the rapid evolution of the types of devices and services that can be used to call for help. Also there is an increasing volume and diversity of information that can be made available to assist PSAPs and responders in an emergency. NENA recognizes this is a fundamental update to the North American 9-1-1 system, and is addressing the challenge with a system design called “Next Generation 9-1-1” (NG9-1-1). NG9-1-1 is the evolution of Enhanced 9-1-1 to an all-IP-based emergency communications system. This technical specification, commonly referred to as i3, is the first version of the NG9-1-1 system design.

This “NENA Technical Information Document on the Network Interface to IP Capable PSAP” document provides technical information to guide manufacturers of network equipment and Public Safety answering Point (PSAP) Customer Premises Equipment (CPE) in the development of Internet Protocol based interfaces between the network and PSAP CPE and to assist E9-1-1 Network Service Providers and PSAP’s in implementing such interfaces. It defines a service description for the capabilities that will need to be supported by the VoIP signaling on the interface, as well as the necessary network and CPE elements needed in the supporting architecture. The Appendices to this TID include specific assumptions/issues for individual candidate Voice over Internet Protocol (VoIP) signaling protocols, that will need to be considered in the specification of (separate) technical reference document(s) that provide signaling requirements for the individual VoIP protocol alternatives identified.

This document is intended to provide a resource that describes the features and functions of the E9-1-1 system that is currently deployed in the United States. These features and functions are a compilation of different regional networks and some may not be present in any particular E9-1-1 network.

This “NENA VoIP Standards Development Organizations” is a reference for NENA technical committees to use for determining the various standards setting bodies involved in the implementation and on going development of VoIP protocols and procedures as they relate to emergency calling.

This document is the first edition of what will be a comprehensive document addressing many access network configurations. This edition has a narrow solutions focus and will address only the automated mechanisms for the residential broadband market, manually configured location mechanisms for end-points are not discussed. User-provided location information is beyond the scope of this document. Revised editions of this document will add new sections to address enterprise, hosted and mobile access configurations.

This “NENA i3 Technical Requirements Document” is intended to specify the requirements the i3 (Long Term Definition) Standard should meet. This document is issued to guide the development of the i3 Standard.

This Technical Reference document provides the NENA requirements for providing location information to support emergency calling. It also provides example scenarios and use cases that need to be supported. This is being provided to support organizations that are defining solutions for determining, acquiring and conveying location information to support emergency calling.

Included in this document is a broad planning methodology that PSAPs can use as a conceptual framework in developing their own strategic approaches to the potential financial and regulatory impact of VoIP. The intention of this document is not to provide a single definitive solution to the funding and regulatory issues related to VoIP. Rather, this document is presented as a survey of the major topical areas related to VoIP funding and regulatory issues tangent to 9-1-1 services.

Non-Voice-Centric Emergency Services as defined in this document focuses on Next Generation Network (NGN) technology and does not include legacy messaging services, such as Short Messaging Service (SMS) . In addition, Non-Voice-Centric Emergency Services does not include support of calls from non-human initiated devices (e.g., fire alarms).

Getting to the i3 solution from where we are today means that we will have to go through a transition from existing legacy originating network and 9-1-1 PSAP interconnections to next generation interconnections. This document describes how NG9-1-1 works after transition, including ongoing interworking requirements for IP-based and TDM-based PSAPs and origination networks . It does not provide solutions for how PSAPs, origination networks, selective routers and ALI systems evolve. Rather, it describes the end point where conversion is complete. At that point, selective routers and existing ALI systems are decommissioned and all 9-1-1 calls are routed by the ECRF and arrive at the ESInet via SIP. The NENA NG9-1-1 Transition Planning Committee (NGTPC) will produce documents covering transition options and procedures.

Many 9-1-1 entities have built, are building, or will build in the near future an Emergency Services IP network (ESInet) to connect PSAPs and other public safety agencies within a region and provide interconnect to other ESInets and originating service providers within a region or state. The effort and expense required to build these facilities is significant. The purpose of this document is to provide network architects, consultants, 9-1-1 entities, and state authorities with the information that will assist them in developing the requirements for and/or designing ESInets today that will be capable of meeting the requirements of an NG9-1-1 system.

This document is intended to be a guide for the NENA Technical and Operations Committees, as well as other national and international standards organizations, to use in developing and finalizing standards in preparation for implementation of standards-based NG9-1-1 systems. The IP network, 9-1-1 equipment, software vendors, as well as service providers should use this requirements document as a guide during their product research and development. PSAP administrators may also find this document useful for planning purposes, as they prepare to transition from their current 9-1-1 system to NG9-1-1 systems, and to update internal policy and procedures to leverage the new features, requirements, and capabilities in the NG environment.

This document was developed as a recommendation for distribution of ESN changes and additions initiated by 9-1-1 Administrators to ERDB, VPC and ESGW operators in the i-2 VoIP environment, which assumes the use of wireline ESNs for the routing of VoIP calls. Its primary goal is to set expectations and improve communications amongst the parties involved to facilitate the timely implementation of VoIP ESN changes and additions, thereby facilitating the proper routing of VoIP E9-1-1 calls. It also makes recommendations as to how to provide the GIS files that reflect the ESN addition or changes requested. This procedural recommendation will involve technical development work. As such, a short term recommendation is also outlined.

Potential Points of Demarcation in NG9-1-1 Networks Information Document, NENA-INF-003, March 21, 2013, has been NENA Board approved and posted to the NENA website. In NG9-1-1 networks, demarcation is not defined exclusively by a physical point of interconnection. NG9-1-1 is built on Internet Protocol (IP) networks which follow the Open Systems Interconnection (OSI) layered model where points of demarcation can occur independently at different places in different OSI layers. This document’s purpose is to identify points of demarcation, and not to advise on the relative merits of different demarcation options from a regulatory or financial perspective.

Today’s Public Safety Answering Points (PSAPs) face more threats than ever before. In a post 9/11 world, the 9-1-1 community must recognize the reality of increased threats and vulnerabilities. New product paradigms are being designed and implemented by the PSAP community at a rapid pace. Today's call-centers are challenged to keep pace with the rapid shifts in technology.

This Information Document is a companion to the NENA 75-001 - NENA Security for Next-Generation 9-1-1 Standard (NG-SEC) Standard. To effectively use this document the user should have a clear understanding of the concepts and procedures described therein.

This checklist provides a summary of the requirements and recommendations detailed in the NG-SEC standard and provides the educated user a method to document a NG-SEC Audit.