|
|
Interconnection & Security Committee
|
|
|
This committee is focused on the technical development, maintenance and evolution of NG9-1-1 systems architecture, both for real-time interfaces within the ESInet as well as those external interfaces into the system. These would include aspects such as system management, architecture and interfaces definitions. The committee also oversees the technical integration and operational impacts of existing and newly formed security (encryption, authentication etc.) technologies on the overall ‘system’.
Sub-Committees- Originating / Access Networks - Chair, John Garner; Vice-Chair, Jim Lockard
The mission of the Originating/Access Networks Subcommittee is to work on issues relating to sources of calls that are external to the ESInet and their ability to interface with the ESInet in a manner that is consistent with existing standards and deployment strategies.
- Workgroups
- Wireless - Femtocells / unlicensed spectrum
- Quality Assurance and Network Design
- Mass Calling
- Geographic Number Portability
- OSP Issue
- NG9-1-1 Architecture Evolution- Chair, Terry Reese; Vice-Chair, TBD
The mission of the NG9-1-1 Evolution Sub defines issues that involve the ESInet architecture, as well as the i3 functional elements that ride on it and their associated interfaces. It is also expected to handle both the evolution of the i3 ESInet and interconnection with evolving originating and PSAP networks.
- Workgroups
- Long Term Definition (i3)
- Network Design for NG9-1-1 (ESIND)
- Emerging Topics - Chair, Paul McLaren; Vice-Chair, Collette Crabill
The mission of the Emerging Topics Subcommittee is to handle topics involving technology that is new or different in terms of how it impacts or interacts with emergency call handling systems.
- Security Topics - Chair, Brian Knueppel; Vice-Chair, TBD
The mission of the security Topics Subcommittee is to handle all issues relating to security of all components, systems and subsystems of current and future 9-1-1 call handling systems.
- Workgroups
- NG9-1-1 Security (NG-SEC)
- Certificate Policy - Certificate Practice Statement (CP-CPS)
|
| The button to the left will take you to a form where you may volunteer to serve on this Committee. Become part of the solution and join NENA's Committee work today!
|
Standards & Documents for this Committee
This committee is focused on the technical development, maintenance and evolution of NG9-1-1 systems architecture, both for real-time interfaces within the ESInet as well as those external interfaces into the system.
These would include aspects such as system management, architecture and interfaces definitions. The committee also oversees the technical integration and operational impacts of existing and newly formed security (encryption, authentication etc.) technologies on the overall ‘system’.
|
75-001 v1 - NG Security Link
[ more ]
[ hide ]
|
Administration
|
3/7/2013
|
|
The purpose of this document is to establish the minimal guidelines and requirements for the protection of NG9-1-1(?) assets or elements within a changing business environment.
|
|
75-502 v1 - NG9-1-1 Security (NG-SEC) Checklist Link
[ more ]
[ hide ]
|
Administration
|
3/7/2013
|
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 provide the educated user a method to document a NG-SEC Audit.
|
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.
|
03-002 v2 Enhanced MF Signaling, Tandem to PSAP Link
[ more ]
[ hide ]
|
Administration
|
12/5/2011
|
|
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 InterNetworking, E9-1-1 Tandem to Tandem Link
[ more ]
[ hide ]
|
Administration
|
12/5/2011
|
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.
This Technical Reference is a guide for designers and manufacturers of selective routing tandems and similar equipment. It may also be of value to purchasers, maintainers and users of such equipment.
|
|
03-004 v2 E9-1-1 Functional Entity Model Link
[ more ]
[ hide ]
|
Administration
|
12/5/2011
|
|
This document contains a set of Functional Entities (FEs) that address a portion of the Functional Entity Model for E9-1-1 Services. The FEs defined in this document address the functionality applied by a wireline network and a PSAP to an incoming Emergency Call. These FEs are applicable to Emergency Calls originating from variety of networks including wireline networks, wireless networks under Phase 1 and Phase II, and Voice over Internet Protocol (VoIP) networks.
|
|
03-005 v1 E9-1-1 Selective Routing Switch Link
[ more ]
[ hide ]
|
Administration
|
12/5/2011
|
|
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 Link
[ more ]
[ hide ]
|
Administration
|
12/5/2011
|
|
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 Link
[ more ]
[ hide ]
|
Administration
|
12/5/2011
|
|
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 & Call Routing Link
[ more ]
[ hide ]
|
Administration
|
12/5/2011
|
|
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 Link
[ more ]
[ hide ]
|
Administration
|
12/5/2011
|
|
This document provides recommendations which can be a resource for technicians, administrators and managers who are charged with maintaining quality assurance over the network and help them better manage network performance.
|
|
03-502 v1 Trunking for Private Switch 9-1-1 Svc Link
[ more ]
[ hide ]
|
Administration
|
12/5/2011
|
|
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 for Wireline and VoIP Link
[ more ]
[ hide ]
|
Administration
|
12/5/2011
|
|
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) Link
[ more ]
[ hide ]
|
Administration
|
12/5/2011
|
|
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 Link
[ more ]
[ hide ]
|
Administration
|
12/5/2011
|
|
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 Link
[ more ]
[ hide ]
|
Administration
|
12/5/2011
|
|
This document is intended to provide information and straightforward instructions to determine the number of trunks required in a 9-1-1 trunk group to provide a P.01 Grade of Service (GOS). This method will apply between any of the following: End Office to Selective Router (SR); SR to PSAP; E9-1-1 gateway to the SR; Mobile Switching Center (MSC) to SR.
|
|
03-507 v1 ESQK Guidelines for VoIP Link
[ more ]
[ hide ]
|
Administration
|
12/5/2011
|
|
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 Link
[ more ]
[ hide ]
|
Administration
|
12/5/2011
|
|
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 Link
[ more ]
[ hide ]
|
Administration
|
12/5/2011
|
|
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.
|
|
03-509 v1 Femtocell and UMA Appendix Link
[ more ]
[ hide ]
|
Administration
|
12/5/2011
|
|
Appendix for Carrier Implementation Detail.
|
|
05-001 v1 E2 Interface Link
[ more ]
[ hide ]
|
Administration
|
12/5/2011
|
|
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 SR Link
[ more ]
[ hide ]
|
Administration
|
12/5/2011
|
|
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.
|
|
NENA-INF-002 Effect of Mass Calling Events Link
[ more ]
[ hide ]
|
Administration
|
9/6/2012
|
|
This NENA Information Document (NID) discusses a situation that was observed when a Mass Calling Event to 9-1-1 occurred within a Legacy 9-1-1 system provider platform. Investigation by the Network Reliability Steering Committee (NRSC) determined that certain types of Legacy Selective Routers (SR) are susceptible to removing SR to PSAP trunks from service during high call volume events. This document will discuss certain procedures, and policies that NENA, Legacy SR Operators, Public Safety agencies, and other equipment and network providers can do, alone or together, to prevent the SR from removing trunks from service. The Network Reliability Steering Committee (NRSC) created a document outlining their findings. It is ATIS-0100034, which can be located at www.atis.org in the document center. A copy of the recommendations made in ATIS-0100034 is included in Appendix A of this NENA Information Document (NID).
|
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.
|
NENA-INF-003 NG9-1-1 Potential Points of Demarcatn
PDF (331.2 KB)
[ more ]
[ hide ]
|
Administration
|
4/3/2013
|
|
Potential Points of Demarcation in NG9-1-1 Networks Information Document, NENA-INF-003, March 23, 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
|
|
08-001 v2 - Interim VoIP Architecture - i2
PDF (1.81 MB)
[ more ]
[ hide ]
|
Administration
|
5/8/2011
|
|
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.
|
|
08-002 v1 - Interface Standards NG91-1 (i3)
PDF (1.46 MB)
[ more ]
[ hide ]
|
Administration
|
11/18/2011
|
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.
|
|
08-003 v1 - Detailed Func & Interface Specs (i3)
PDF (2.07 MB)
[ more ]
[ hide ]
|
Administration
|
2/7/2012
|
|
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.
|
|
08-501 v1 - Network Interface to IP Capable PSAP
PDF (928.88 KB)
[ more ]
[ hide ]
|
Administration
|
5/8/2011
|
|
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.
|
|
08-502 v1 - E9-1-1 Requirements
PDF (421.97 KB)
[ more ]
[ hide ]
|
Administration
|
5/8/2011
|
|
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.
|
|
08-503 v1 - VoIP Characteristics
PDF (284.29 KB)
[ more ]
[ hide ]
|
Administration
|
5/8/2011
|
|
The purpose of this document is to procure, create and publish a VoIP primer document to be used by individuals not familiar with VoIP technology.
|
|
08-504 v1 - VoIP Stds Development Organizations
PDF (49.19 KB)
[ more ]
[ hide ]
|
Administration
|
5/8/2011
|
|
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.
|
|
08-505 v1 - Locn Determination IP-Based EmergSvcs
PDF (789.37 KB)
[ more ]
[ hide ]
|
Administration
|
5/8/2011
|
|
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.
|
|
08-506 v1 - IP Network Design for NG9-1-1
PDF (807.78 KB)
[ more ]
[ hide ]
|
Administration
|
1/5/2012
|
|
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.
|
|
08-751 v1 - i3 Requirements Long Term Definition
PDF (364.96 KB)
[ more ]
[ hide ]
|
Administration
|
5/8/2011
|
|
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.
|
|
08-752 v1 - Locn Info Support IP Based Emerg Svcs
PDF (616.37 KB)
[ more ]
[ hide ]
|
Administration
|
5/7/2011
|
|
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.
|
|
57-750 V1 NG9-1-1 System & PSAP Operational Feat.
PDF (125.95 KB)
[ more ]
[ hide ]
|
Administration
|
10/5/2012
|
|
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.
|
|
58-502 VoIP Funding & Regulatory Issues
PDF (207.01 KB)
[ more ]
[ hide ]
|
Administration
|
8/3/2011
|
|
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.
|
|
73-501 v1 - Non-Voice-Centric Emergency Svcs
PDF (168.21 KB)
[ more ]
[ hide ]
|
Administration
|
8/3/2011
|
|
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).
|
The Non-Traditional Committee is responsible for developing standards, Technical Requirements Documents or Technical Information Documents for all issues related to future products and services that may affect 9-1-1. The committee’s goal is to monitor industry, science and technology activities for any such items, research possible impact and draft appropriate documents that can be forwarded to other NENA Committee's or regulatory and industry standard organizations in order to ensure all devices may access 9-1-1 anytime and anywhere.
|
07-501 v11 - Future 9-1-1 Models
PDF (96.72 KB)
[ more ]
[ hide ]
|
Administration
|
5/7/2011
|
|
The purpose of this document is to develop models of 9-1-1 systems that will provide the features and functionalities that the public safety organizations need to do their job of responding to 9-1-1 calls. The models have been developed with a view to the future in that each model represents either a view of what currently exists or what is expected to exist at a predefined point in the future.
|
|
07-502 v1 - Non-Trad Communications to PSAP Eqpt
PDF (371.83 KB)
[ more ]
[ hide ]
|
Administration
|
5/7/2011
|
|
This document will identify, define, discuss and offer potential solutions or alternatives to interfaces required to bring non-traditional sources of information into Enhanced 9-1-1 Public Safety Answering Point (PSAP).
|
|
07-503 v1 - Ntwk Interfaces for 911 & Emerg Tech
PDF (231.08 KB)
[ more ]
[ hide ]
|
Administration
|
5/7/2011
|
|
This NENA Technical Information Document (TID) provides a reference to network interfaces for users, manufactures and providers of E9-1-1 in an Emerging Technologies such as Voice over Packet (VoP), Voice over Internet Protocol (VoIP)and Voice over Digital Subscriber Line (VoDSL).
|
|
07-504 v1 - Collision Notification & Telematics
PDF (473.68 KB)
[ more ]
[ hide ]
|
Administration
|
5/7/2011
|
|
The purpose of this "Automatic Collision Notification and Vehicle Telematics Technical Information Document” is to understand and describe in both technical and operational terms the current telematics industry and telematics emergency calls and associated information delivered to Public Safety Answering Points (PSAPs). The document scope also reflects on the current 9-1-1 infrastructure, the next generation emergency networks, and it discusses the integration of telematics emergency calls and information into those networks. This Technical Information Document (TID) will provide information to allow the National Emergency Number Association (NENA) and other interested parties to develop new communications methodologies and protocols to facilitate emergency communications between Telematics Service Providers (TSP) and PSAPs.
|
The Non-Traditional Committee is responsible for developing standards, Technical Requirements Documents or Technical Information Documents for all issues related to future products and services that may affect 9-1-1. The committee’s goal is to monitor industry, science and technology activities for any such items, research possible impact and draft appropriate documents that can be forwarded to other NENA Committee's or regulatory and industry standard organizations in order to ensure all devices may access 9-1-1 anytime and anywhere.
|
07-501 v11 - Future 9-1-1 Models Link
[ more ]
[ hide ]
|
Administration
|
12/5/2011
|
|
The purpose of this document is to develop models of 9-1-1 systems that will provide the features and functionalities that the public safety organizations need to do their job of responding to 9-1-1 calls. The models have been developed with a view to the future in that each model represents either a view of what currently exists or what is expected to exist at a predefined point in the future.
|
|
07-502 v1 - Non-Trad Communications to PSAP Eqpt Link
[ more ]
[ hide ]
|
Administration
|
12/5/2011
|
|
This document will identify, define, discuss and offer potential solutions or alternatives to interfaces required to bring non-traditional sources of information into Enhanced 9-1-1 Public Safety Answering Point (PSAP).
|
|
07-503 v1 - Ntwk Interfaces for 911 & Emerg Tech Link
[ more ]
[ hide ]
|
Administration
|
12/5/2011
|
|
This NENA Technical Information Document (TID) provides a reference to network interfaces for users, manufactures and providers of E9-1-1 in an Emerging Technologies such as Voice over Packet (VoP), Voice over Internet Protocol (VoIP)and Voice over Digital Subscriber Line (VoDSL).
|
|
07-504 v1 - Collision Notification & Telematics Link
[ more ]
[ hide ]
|
Administration
|
12/5/2011
|
|
The purpose of this "Automatic Collision Notification and Vehicle Telematics Technical Information Document” is to understand and describe in both technical and operational terms the current telematics industry and telematics emergency calls and associated information delivered to Public Safety Answering Points (PSAPs). The document scope also reflects on the current 9-1-1 infrastructure, the next generation emergency networks, and it discusses the integration of telematics emergency calls and information into those networks. This Technical Information Document (TID) will provide information to allow the National Emergency Number Association (NENA) and other interested parties to develop new communications methodologies and protocols to facilitate emergency communications between Telematics Service Providers (TSP) and PSAPs.
|
|
58-001 - IP-Capable PSAP Minimum Requirements
PDF (158.83 KB)
[ more ]
[ hide ]
|
Administration
|
1/29/2011
|
his document is intended to be a guide for the NENA Technical and Operations Committees to use in establishing additional standards in preparation for the installation of IP-based 9-1-1 systems in the PSAP. The 9-1-1 equipment, software, and service vendors should use this standard 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 equipment to IP-based systems, and to update internal policy and procedures to work with Voice over IP 9-1-1 calls.
The standards necessary to implement some of the features and functions described herein do not yet exist; therefore this document is not intended to be used as a specification for the acquisition of products or services until those Technical Standards have been developed. Instead, this document is intended to be used by the NENA Technical Committee to determine what technical standards need to be developed an
|
|
58-501 - IP PSAP Features and Capabilities
PDF (113.17 KB)
[ more ]
[ hide ]
|
Administration
|
1/29/2011
|
This document is intended to be a guide for the NENA Technical and Operations Committees to use in preparation for and installation of IP based 9-1-1 systems in the PSAP. PSAP administrators may also find this document useful for planning purposes, as they prepare to transition from their current equipment to IP based systems.
This document contains a list of capabilities or features that are expected to be supported in a public safety answering point (PSAP)(?) using Internet protocol (IP) based 9-1-1 equipment and software. These capabilities and features should be considered a minimum level of functionality, developed in an open architecture environment that will allow interoperability at all levels of the 9-1-1 network, regardless of vendor. Nothing in this document should be interpreted as limiting the development of additional capabilities or features by 9-1-1 equipment and software developers.
|
|
58-502 - VoIP Funding & Regulatory Issues
PDF (207.01 KB)
[ more ]
[ hide ]
|
Administration
|
1/29/2011
|
|
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.
|
|
|
