Technical Committee - Network

The Network Committee (NTC) is the hierarchical parent of Working Groups formed to address (non-VoIP) technical issues that impact network elements that are part of the overall E9-1-1 architecture.  As technical issues are identified they are handled via Working Groups that are formed to accomplish specific goals, which usually result in some type of official NENA documentation (Standard, TID, TRD, liaison to other groups etc.).

Scroll Down or Click to Go To:

Network Committee working groups:

  • Network Quality Assurance & Design
  • Geographic Number Portability
  • Wireless
  • Text to NG911
  • Multiple Service Types Over Common Trunk Groups

Any NENA member interested in joining any Network Working Groups, please review the Scopes & Goals at the bottom of the page and then contact the Committee Chair or Vice Chair to be added to a specific working group.

Anand Akundi
Anand Akundi is currently the Program Manager for E9-1-1 Services at Telcordia Technologies. Anand has over 8 years in telecommunications experience. Anand provides E9-1-1 and VoIP expertise to large carriers and government agencies in the United States. In addition, Anand is also Telcordia’s representative to Wireless Standards groups such as 3GPP2 which define Standards in support of next generation wireless networks. Anand is currently serving as the Co-Chair for the Next Generation Emergency Services (NGES) Subcommittee in ATIS Emergency Services Interconnection Forum (ESIF).

John Garner, ENP
Cingular Wireless,
The New AT&T
John Garner, ENP, is Program Director for Public Safety Relations at Cingular Wireless, LLC.  He was previously the Chair of the Network Technical Committee's Wireless Subcommittee and is active at the Emergency Services Interconnection Forum and the Congressional E911 Institute.  John has over 25 years experience in public safety and was formerly the Director of the Shelby County, Tennessee E911 District and chair of the Tennessee Emergency Communications Board.  John has also served as a member of the Mississippi Commercial Mobile Radio Services Board.  John has earned the Bachelor of Arts and the Master of Public Administration degrees from the University of Memphis.



                                                                                                                    Return to Top

20110613_NTC-Scope-Goal-Direction-Status.pdf32 KB
NENA Technical Standards & Documents
  • 00-001 v16 Master Glossary

    The NENA Master Glossary is a guide for readers of NENA publications and a tool for members of the NENA committees that prepare them. It defines the terms, acronyms and definitions associated with the 9-1-1 industry. Intended users of this document are any person needing NENA’s definition/description of a 9-1-1 related term.

  • 01-001 v4.1 Organization & Document Approval Processes

    This document is written for NENA Technical Committee leadership and members. A requirement for participating in the Technical Committee process is to adhere to all procedures outlined in this document.

  • 03-002 v3 Enhanced MF Signaling, E9-1-1 Tandem to PSAP

    This NENA Standard defines the use of a Feature Group D like signaling protocol between the E9-1-1 selective routing tandem and E9-1-1 customer premises equipment (CPE) which is called “Enhanced MF Signaling”. This document does not suggest the implementation of Feature Group D trunking - there are tariff issues associated with FGD that do not apply to 91-1. Rather, it recommends borrowing the “off the shelf” MF signaling protocol from Feature Group D in order to facilitate the delivery of one or two ten-digit ANI’s to the PSAP over existing facilities, without creating an entirely new protocol.

  • 03-003 v1 Inter-Networking, E9-1-1 Tandem to Tandem

    This NENA Technical Reference defines the use of an Integrated Services Digital Network (ISDN) User Part (ISUP) signaling protocol between E9-1-1 selective routing tandems, and similar equipment, for the purpose of allowing 9-1-1 calls to be transferred or routed across E9-1-1 networks.

  • 03-004 v2 E9-1-1 Functional Entity Model

    Recent changes in telephony technology along with corresponding changes in the regulatory environment with respect to E9-1-1 Service are impacting the service architectures being defined for E9-1-1 Services. Support of Wireless Phase II and NENA i2 for VoIP are making enhancements to existing E9-1-1 functionality necessary.

    The definition of service architectures to support Wireless Phase II and NENA i2 for VoIP functionality will impact both wireless and wireline networks. Since both wireless and wireline networks will play a role in processing an increasing number of Emergency Calls, it is critical that the interconnection for these networks be based on a common understanding of the functions and interfaces supported by each network.

  • 03-005 v1 E9-1-1 Selective Routing Switch

    This document is intended to define the Generic Feature Requirements of an Enhanced 9-1-1 Selective Routing switch. For legibility, this document describes the Selective routing switch as a single switching element even though the NENA Functional Entity Model describes the Selective Routing function as it fits into the E9-1-1 network as a whole. This allows the developer to create the E9-1-1 function as a centrally located switching entity, or as distributed network elements. It also distinguishes which features and characteristics are fundamental to an Enhanced 9-1-1 system, and which, through either current or anticipated advancement of the industry, are deemed optional or additional features of the 9-1-1 network.

  • 03-006 v1 E9-1-1 Call Congestion Management

    This document provides a framework for consideration of the various factors impacting the management of call congestion and traffic engineering for E9-1-1 networks. A network reference model is provided for use in referring to generic E9-1-1 network entities. This is followed by a section that outlines generally accepted industry practices for traffic engineering for E9-1-1 networks.

  • 03-007 v1 ESCO Code Selection

    This NENA Recommended Standard for Emergency Service Central Office (ESCO) Code Selection, Assignment and Display Management discusses the Emergency Service Central Office (ESCO) code specifications as it relates to the incoming trunk groups in the E9-1-1 Control Office. It is a guide for designers, manufacturers, 9-1-1 Service Providers, 9-1-1 Database Authorities and 9-1-1 Public Safety Answering Points (PSAPs). It identifies some of the issues involved with the selection, assignment, processing and management of the ESCO codes used for trunk group origination identification during an Automatic Number Identification (ANI) failure.

  • 03-008 v1 E9-1-1 Default Assignment and Call Routing Functions

    This “NENA Recommended Standard for E9-1-1 Default Assignment and Call Routing Functions” document provides an overview of various database and network specifications and requirements related to Default Routing of 9-1-1 calls. It is intended to help local authority; database and/or network administrators select a model in the development of standard default routing arrangements. It identifies and defines methods used to assign defaults and route 9-1-1 calls when circumstances prevent normal selective routing. Each approach is used during a specific set of circumstances; similarly a specific set of circumstances shall determine which approach is most appropriate.

  • 03-501 v4 Network Quality Assurance

    Single points of failure in the 9-1-1 network should not be tolerated. Network and Emergency Services providers should design and deploy fault tolerant systems which will eliminate, as much as possible, single points of failure that prevent routing 9-1-1 calls successfully. The solution should be capable of delivering a 9-1-1 call to a designated default Public Safety Answering Point (PSAP)(?) during times of network failure through either alternate routing, Emergency Stand Alone (ESA) / Emergency Transport Backup (ETB) / Emergency Line Access (ELA) capabilities, cellular networks, etc. and should be automated when/where possible. Very clearly, the first priority is to route the call to a designated PSAP.

  • 03-502 v1 Trunking for Private Switch 9-1-1 Service

    This NENA TID defines three distinct alternative trunking configurations to accomplish the provisioning of Private Switch 9-1-1 Service (PS/911) in conjunction with the use of Private Branch Exchange (PBX) telephone systems. For PBX systems that use digital trunks, Primary Rate Interface Integrated Services Digital Network (PRI-ISDN) trunks, the provisioning of PS/911 may be accommodated without the requirement of dedicated trunks for transporting 9-1-1 calls. For PBX systems that use analog trunks (i.e. they are not compatible with PRI and/or PRI trunks are not available from local service providers), the provisioning of PS/911 may be accommodated by using dedicated circuits that operate with the Centralized Automated Message Accounting (CAMA) signaling protocol.

  • 03-503 v1 SS7 Guidelines

    This document is a guide to orient the SS7 translation engineer/technician on the nature of translations required in the SS7 messaging between the E9-1-1 Selective Router and the various network elements that seek to connect to the router. These elements can include both wireline end offices and VoIP Emergency Services Gateways (ESGW) owned or operated by local exchange carriers (ILECs and CLECs), VoIP Service Providers (VSPs) and/or the E9-1-1 Service System Providers (SSPs). It is not in the scope of this document to explain exact details of any particular 9-1-1 SR, but to act as a way to understand the dynamics of these types of translations. This document is secondary to any network disclosure or other translation policy guides from any 9-1-1 Service System Provider. The reader of this document is encouraged to contact the 9-1-1 Service System Provider for any detailed questions on SS7 translations or policy details.

  • 03-504 v1 Mobile Emergency Service (E911M)

    This document contains standards requirements for providing the PSAP with a working callback number to all wireless phones that call 9-1-1. It brings with it the solution to a number of other open issues.

  • 03-505 v1 Rate Center Consolidation

    This document is a guide for E9-1-1 Subject Matter Experts (SMEs) and Regulatory Agencies in determining a rate center consolidation configuration that minimizes the impact of E9-1-1 call delivery in a failure condition. Specifically, this document addresses the impacts of rate center consolidation in an environment served by multiple service providers.

  • 03-506 v1 E9-1-1 Voice Circuit Requirements

    The purpose in determining voice circuit requirements for an E9-1-1 Trunk Group is to provide a transmission Grade of Service (GOS) for each 9-1-1 caller that is at least P.01 (probability that no more than one call out of 100 attempts made during the average busy hour will be blocked) and that, where available, physically diverse routing is being used between nodes.

    In no case is it ever recommended that voice circuits be designed at less than P.01 Grade of Service (GOS). Note that P.01 can also be described as P0.01 in the industry. In this document that are to be considered as synonymous.

  • 03-507 v1 ESQK Guidelines for VoIP
    This document is a guide to orient VSPs, ESGW operators, and VPC operators on the use and assignment of ESQKs for 9-1-1 Emergency Services Gateway (ESGW) to Selective Router (SR) connectivity and call routing.
  • 03-508 v1 Multiple Service Type Calls

    This document provides a review of the topics that are associated with the practice of delivering more than one type of an emergency call over the same trunk group into a legacy type E9-1-1 selective router.   It describes the market forces leading to the implementation of the practice as well as the technological pros and cons associated with it. The technical and operational implications of the practice are addressed from the perspective of many separate areas, including groups such as the originating service provider, network aggregator, E9-1-1 system service provider, Public Safety Agency (i.e., PSAP management/call takers), and regulatory bodies that govern 9-1-1 operations. 

  • 03-509 v1 Femtocell and UMA

    The purpose of this “Femtocel/UMA Technical Information Document” is to describe in technical as well as operational terms the current state of femtocell and UMA deployments with respect to call processing of E9-1-1 calls, and to identify the impacts to Public Safety Answering Points (PSAPs) of receiving and processing calls from femtocells. This TID also describes the current 9-1-1 infrastructure, next generation emergency networks, and discusses integration of femtocells and UMA technologies into those networks. This TID will provide information to allow the National Emergency Number Association (NENA) and other interested parties to develop new communications methodologies, standards, and protocols to facilitate emergency communications between users of femtocells/UMA and PSAPs.

  • 05-001 v1 E2 Interface

    This “NENA Standard for the Implementation of the Wireless Emergency Service Protocol E2 Interface” document provides explicit protocols and parameters for interoperable operation of the E2 interface over TCP/IP. 1This interface is between the MPC/GMLC and the EMSE as defined in TR45.2’s TIA/EIA/J-STD-036-A . This document defines the methods that MPC/GMLC and ESME use to interact, allowing for the concept of geographically redundant nodes and the inherent link management. It defines how the TCAP-based application protocol is to be encapsulated upon the TCP/IP stack.

  • 05-501 v1 SS7 Guidelines for MSC to Selective Router Connectivity

    This document is a guide to orient the SS7 translation engineer/technician on the nature of 9-1-1 Mobile Switching Center (MSC) to SR translations. It is not in the scope of this document to explain exact details of any particular 9-1-1 SR, but to act as a way to understand the dynamics of these types of translations.