1、 1 2 Document Type: Technical Report 3 TITLE: Emergency Services Network Interfaces Framework 4 DOCUMENT NUMBER: ATIS-0500008. 5 SOURCE: Emergency Services Interconnection Forum 6 CONTACT: Mike Fargano, Qwest, (303) 896-3618, Christian Militeau, Intrado (720) 864-7 5245 8 9 1.1 Abstract 10 This docu
2、ment defines the framework and structure of the Emergency Services Network 11 Interfaces (ESNI) suite of standards. The ESNI suite of standards includes the Emergency 12 Services Messaging Interface (ESMI) that provides interconnections between next 13 generation PSAPs and the Emergency Services Net
3、work (ESNet), the Emergency 14 Information Services Interface (EISI) which provides access to services within or external 15 to the ESNet and the Emergency Services Network to Emergency Services Network 16 (ENEN) interface that allows the interconnection and exchange of services between 17 ESNets. 1
4、8 Services supported by these standards may either be mediated or unmediated. Mediated 19 services are provided to a PSAP or authorized agency through an Emergency Services 20 Network Response Gateway (RG). Unmediated services are accessed directly from the 21 next generation PSAP to the service. Th
5、e Emergency Services Network Interface suite is 22 the evolution of the Emergency Service Network that provides sophisticated and robust 23 services to the PSAP and other authorized agencies. This suite enables a direction 24 toward a next generation Emergency Services Network. 25 26 27 1.2 Notice 2
6、8 This document may be changed or modified. Neither ATIS nor ESIF makes any representation or warranty, express of implied, with respect to 29 the sufficiency, accuracy or utility of the information or opinion contained or reflected in the material utilized. ATIS and ESIF further expressly 30 advise
7、 that any use of or reliance upon the material in question is at your risk and neither ATIS nor ESIF shall be liable for any damage or injury, 31 of whatever nature, incurred by any person arising out of any utilization of the material. It is possible that this material will at some future date be 3
8、2 included in a copyrighted work by ATIS. 33 34 35 Document ATIS-0500008. 36 Prepared by 37 Emergency Services Interconnection Forum 38 Working Group 39 Emergency Services Network Interface Task Force 40 1 ATIS-0500008 2 3 4 ATIS Technical Report 5 6 Emergency Services Network Interfaces Framework 7
9、 8 Secretariat 9 Alliance for Telecommunications Industry Solutions 10 11 Approved October 5, 2006 12 13 14 Abstract 15 This document defines the framework and structure of the Emergency Services Network 16 Interfaces (ESNI) suite of standards. The ESNI suite of standards includes the Emergency 17 S
10、ervices Messaging Interface (ESMI) that provides interconnections between next 18 generation PSAPs and the Emergency Services Network (ESNet), the Emergency 19 Information Services Interface (EISI) which provides access to services within or external 20 to the ESNet and the Emergency Services Networ
11、k to Emergency Services Network 21 (ENEN) interface that allows the interconnection and exchange of services between 22 ESNets. 23 Services supported by these standards may either be mediated or unmediated. Mediated 24 services are provided to a PSAP or authorized agency through an Emergency Service
12、s 25 Network Response Gateway (RG). Unmediated services are accessed directly from the 26 next generation PSAP to the service. The Emergency Services Network Interface suite is 27 the evolution of the Emergency Service Network that provides sophisticated and robust 28 services to the PSAP and other
13、authorized agencies. This suite enables a direction 29 toward a next generation Emergency Services Network. 30 31 32 33 1.3 Foreword 1 The information contained in this foreword is not part of an American National Standard 2 (ANS) and has not been processed in accordance with ANSIs requirements for
14、an ANS. 3 As such, Foreword may contain material that has not been subjected to public review or a 4 consensus process. In addition, it does not contain requirements necessary for 5 conformance to a standard. 6 This Technical Report is titled Emergency Services Network Framework. The framework 7 wil
15、l incrementally replace the existing data retrieval (i.e. ALI) infrastructure with a next 8 generation network that offers advanced services and interoperates with PSAPs and other 9 public safety agencies. Other public safety agencies may include medical service 10 providers, fire stations, poison a
16、ssistance centers, police, etc. 11 Suggestions for improvement of this Technical Report are welcome. Send suggestions to 12 the Alliance for Telecommunications Industry Solutions, ESIF Secretariat, 1200 G Street, 13 NW, Suite 500, Washington DC 20005. 14 This Technical Report was processed and appro
17、ved by the Emergency Services 15 Interconnection Forum. Forum approval of this report does not necessarily imply that all 16 committee members voted for its approval. 17 1.4 Revision History 18 Revision Date Remarks .01 Version .01 is a contribution and should not be considered baseline text. .02 Ma
18、rch 22, 2006 Baseline version 1.0 August 18, 2006 Version for Approval 1.0 October 5, 2006 Publication Version ATIS-0500008 2Table of Contents 1 1.1 Abstract 1 2 1.2 Notice .1 3 1.3 Foreword 1 4 1.4 Revision History .1 5 2 Introduction/Executive Summary.4 6 2.1 Overcoming Legacy Shortcomings5 7 3 Sc
19、ope, Purpose, and Application.6 8 4 References.7 9 5 Definitions 7 10 6 Abbreviations, Acronyms, and Symbols 9 11 7 ESNI Framework9 12 7.1 Emergency Services Messaging Interface.11 13 7.2 Emergency Information Services Interface12 14 7.3 Emergency Services Network to Emergency Services Network Proto
20、col.13 15 7.4 Features, Profiles and Interfaces.13 16 7.5 ESNet Environment14 17 7.6 Example PSAP Configurations 15 18 8 ESNI Sequence Diagrams.19 19 8.1 Service Registration and Service Discovery19 20 8.2 Emergency Event.20 21 8.3 Notification Services.21 22 23 24 Table of Figures 25 26 Figure 2-1
21、ESNI Suite Structure .4 27 Figure 2-2 ESNI Context Diagram 5 28 Figure 7-1 ESNI Reference Model11 29 Figure 7-2 Features, Profiles and Interfaces.14 30 Figure 7-3 Mediated Data Services Delivery to Clients 15 31 Figure 7-4 Unmediated Data Service Delivery to Clients .15 32 Figure 7-5 PSAP Call Taker
22、 Positions Configured as CESEs Connected to an ESNet.16 33 Figure 7-6 PSAP CPE Proxy Connection to an ESNet.16 34 Figure 7-7 PSAP CPE Call Takers with Additional CESE System Component .17 35 Figure 7-8 CESE Connection to Multiple ESNets.17 36 Figure 7-9 PSAP CPE Implementation of RG-EISI Functional
23、Entity.18 37 ATIS-0500008 3Figure 7-10 Non-mediated EISI Protocol Interaction Model .19 1 Figure 8-1 Mediated Service Publish and Subscribe19 2 Figure 8-2 Unmediated Service Publish and Discovery .20 3 Figure 8-3 ALI Bid and Response Mediated20 4 Figure 8-4 ALI Bid and ResponseNon-mediated 21 5 Figu
24、re 8-5 Mediated Notification Service22 6 Figure 8-6 Unmediated Notification Service .22 7 8 ATIS-0500008 41 2 Introduction/Executive Summary 2 The Emergency Information Services Interface (EISI), Emergency Service Messaging 3 Interface (ESMI) and ESNet to ESNet Interface (ENEN) comprises a suite of
25、standards 4 under the umbrella of Emergency Services Network Interfaces (ESNI) that enables an 5 evolutionary migration from existing PSAP ALI services and interfaces to next generation 6 services (Figure 2-1). This framework document defines the context of each standard in 7 the suite and illustrat
26、es interactions and interworkings between and among the standard 8 interfaces. 9 10 Figure 2-1 ESNI Suite Structure 11 ESMI enables interactions between a next generation PSAP called a Conforming 12 Emergency Services Entity (CESE) and the ESNet element called a Response Gateway 13 (RG). ESMI provid
27、es a common and uniform face from the next generation PSAP or 14 authorized agency to elements providing emergency services via EISI. 15 EISI provides access to services within or external to the ESNet through a network 16 function called an Entity Providing Emergency Services (EPES). A function cal
28、led the 17 Entity Consuming Emergency Services (ECES)1is the requestor of these services2. EISI 18 provides enhanced service providers a uniform set of profiles and interfaces using web 19 services. EISI may provide access to services to the PSAP in a mediated fashion from the 20 EPES through the RG
29、. It may also provide unmediated access to services directly to a 21 PSAP, not using the RG to mediate interactions. In this case the EPES communicates 22 directly with an ECES at the PSAP. 23 The ENEN interface allows the interconnection and exchange of services between 24 ESNets. ENEN is still in
30、the process of definition. In general it may be thought of as a 25 replacement for the PSAP to ALI (PAM) messaging that is use to steer requests between 26 ESNets to retrieve location information. However, the role of ENEN may expand beyond a 27 PAM replacement. 28 The next generation of emergency s
31、ervices is realized through the capabilities that can be 29 provided by the combination of the ESNet, EPESs, ECESs, RGs, gateway services and 30 the additional value added services. The context diagram is shown in Figure 2-2. The 31 1For mediated services the RG may assume the role of the ECES. For
32、this document, in discussing mediated services the reader should understand that the RG plays the role of the ECES. 2Note that it is not always true that the EPES is provider and the ECES is the requester. More detail regarding this topic may be found in the EISI standard. For discussion in this doc
33、ument the EPES and ECES are used in those roles. ATIS-0500008 5suite of protocols enables flexibility among elements such as PSAPs, ALI data sources, 1 wireless call processing, telematics, gateway services and various enhanced services. 2 EPESs may include medical service providers, poison assistan
34、ce centers, hazardous 3 material sources, situation command center coordinators, telematics, etc. 4 5 Figure 2-2 ESNI Context Diagram 6 Several instances of the ESNet may exist across North America within different service 7 provider areas. These ESNet instances will interoperate through both legacy
35、 interfaces 8 and gateway protocols such as ENEN. A single ESNet instance could encompass PSAPs 9 across many states, counties within a state, a single PSAP or some other collection of 10 PSAPs. 11 The Emergency Information Services Interface (EISI), Emergency Service Messaging 12 Interface (ESMI) a
36、nd ESNet to ESNet Interface (ENEN) enable an evolutionary migration 13 from existing PSAP ALI interfaces. Such future infrastructures must co-exist with legacy 14 interfaces and current PSAP interoperability features must be preserved across legacy 15 and next generation deployments. 16 2.1 Overcomi
37、ng Legacy Shortcomings 17 The existing protocol and network architecture between the PSAP and Emergency Service 18 Network that provides ALI data has not substantially changed since its introduction 19 approximately 30 years ago. This legacy protocol is a barrier to advancing and evolving 20 emergen
38、cy services. The legacy protocol and the network architecture that it implies, 21 present significant challenges in introducing new features and advanced emergency 22 services. In addition, maintenance, as it relates to PSAP notification of planned outages, 23 requires undue administrative overhead.
39、 24 The existing architecture does not support the needs defined in the NENA Future Path 25 Plan, as referenced in the document “NENA Technical Information Document on Future 9-26 1-1 Models”. Furthermore, the possible solutions to meet this need can build upon 27 technology and conventions establis
40、hed through NENA, such as the NENA XML schema 28 specifications. However, the future protocols must go beyond simply adding XML syntax 29 to the existing data exchanged between PSAPs and ALI Hosts. A protocol and network 30 ATIS-0500008 6architecture that supports more robust dialogs and modern netw
41、ork configurations must be 1 engineered. The future protocols must be specified in a way, and to a level of detail, that 2 drives consistency across emergency service network implementations for both core 3 services and value-add features. 4 The protocols need to be engineered to go beyond the tradi
42、tional E9-1-1 PSAP Call-Taker 5 role and consider a broader environment of emergency services. This should include 6 cooperation among PSAP Call-Takers, across PSAPs, inclusive of all Emergency Service 7 Providers, and inclusive of oversight and management at various jurisdictional levels. 8 The fut
43、ure protocol implementations should recognize that the role of the Emergency 9 Service Provider has changed and is continuing to change as technology has expanded 10 beyond traditional wireline fixed location telephones. Also, the need for information at the 11 PSAP is increasing beyond simple displ
44、ay information. At the same time, service, 12 reliability, availability and survivability must be maintained for the distributed Emergency 13 Service Providers. Communications Service Providers, e.g. local telephone carriers, 14 independent telephone companies and wireless carriers, will continue to
45、 depend upon an 15 Emergency Service Provider for insulation of internals in the 9-1-1 network, migration, 16 evolution and PSAP interactions. In some cases, a Communications Service Provider will 17 be the Emergency Service Provider or a PSAP or jurisdiction may choose to be its own 18 Emergency Se
46、rvice Provider. 19 The Emergency Services Network requires new functionality beyond simple PSAP 20 queries. The ESNI protocol suite will enable flexibility, additional services, and more 21 advanced interaction models. The ESNI suite of protocols must enable an ESNet 22 architecture that enhances th
47、e reliability and survivability of national emergency services. 23 These protocols and ESNet architecture must allow for management and distribution of 24 enriched data types such as graphics, images, voice and video. 25 The evolving ESNet enables collaboration services between service providing ent
48、ities. It 26 enables broader communication capabilities such as notification of regional emergencies, 27 national security events and other services based upon a community of interest, 28 geography and public entity. 29 The ESNI protocol suite and corresponding network based architecture provides ad
49、vanced 30 services ubiquitously across PSAPs of varying size and location. Rural PSAPs can utilize 31 the same services as large metro PSAPs without requiring large individual investments. 32 3 Scope, Purpose, and Application 33 The scope of this document is to set a framework for the context, application and 34 interactions of the ESNI protocol suite. It shows how each protocol, ESMI, EISI and ENEN 35 relates to the other. It will describe how services may be accessed in a mediated or 36 unmediated fashion. In doing this it will use some examples of services for each 37 environment. This
