ANSI ATIS 0500006-2008 Emergancy Information Services Interface (EISI) Ali Service.pdf

《ANSI ATIS 0500006-2008 Emergancy Information Services Interface (EISI) Ali Service.pdf》由会员分享，可在线阅读，更多相关《ANSI ATIS 0500006-2008 Emergancy Information Services Interface (EISI) Ali Service.pdf（21页珍藏版）》请在麦多课文档分享上搜索。

1、 AMERICAN NATIONAL STANDARD FOR TELECOMMUNICATIONS ATIS-0500006.2008(R2013) Emergency Information Services Interfaces (EISI) ALI Service As a leading technology and solutions development organization, ATIS brings together the top global ICT companies to advance the industrys most-pressing business p

2、riorities. Through ATIS committees and forums, nearly 200 companies address cloud services, device solutions, emergency services, M2M communications, cyber security, ehealth, network evolution, quality of service, billing support, operations, and more. These priorities follow a fast-track developmen

3、t lifecycle from design and innovation through solutions that include standards, specifications, requirements, business use cases, software toolkits, and interoperability testing. ATIS is accredited by the American National Standards Institute (ANSI). ATIS is the North American Organizational Partne

4、r for the 3rd Generation Partnership Project (3GPP), a founding Partner of oneM2M, a member and major U.S. contributor to the International Telecommunication Union (ITU) Radio and Telecommunications sectors, and a member of the Inter-American Telecommunication Commission (CITEL). For more informatio

5、n, visit. AMERICAN NATIONAL STANDARD Approval of an American National Standard requires review by ANSI that the requirements for due process, consensus, and other criteria for approval have been met by the standards developer. Consensus is established when, in the judgment of the ANSI Board of Stand

6、ards Review, substantial agreement has been reached by directly and materially affected interests. Substantial agreement means much more than a simple majority, but not necessarily unanimity. Consensus requires that all views and objections be considered, and that a concerted effort be made towards

7、their resolution. The use of American National Standards is completely voluntary; their existence does not in any respect preclude anyone, whether he has approved the standards or not, from manufacturing, marketing, purchasing, or using products, processes, or procedures not conforming to the standa

8、rds. The American National Standards Institute does not develop standards and will in no circumstances give an interpretation of any American National Standard. Moreover, no person shall have the right or authority to issue an interpretation of an American National Standard in the name of the Americ

9、an National Standards Institute. Requests for interpretations should be addressed to the secretariat or sponsor whose name appears on the title page of this standard. CAUTION NOTICE: This American National Standard may be revised or withdrawn at any time. The procedures of the American National Stan

10、dards Institute require that action be taken periodically to reaffirm, revise, or withdraw this standard. Purchasers of American National Standards may receive current information on all standards by calling or writing the American National Standards Institute. Notice of Disclaimer Pedigo (VA) Elect

11、ronic and Telecommunications Jidem Mok Embarq Sandra Lott Christina Smith (VA) Ericsson Walter White Tina Diem (VA) Greater Harris County 9-1-1 Mike Hayes Stan Heffernan (VA) Organization Represented Name of Representative HBF Group Jim Shepard John Sines (VA) Intrado Christian Militeau Robert Sherr

12、y (VA) L. Robert Kimball Joe McCarnley Gordon VanAucken (VA) The Melcher Group, LLC Jim Goerke National Emergency Number Association (NENA) Ron Bloom Roger Hixson (VA) NeuStar Barry Bishop Openwave Mark Drennan Steve Howser (VA) Polaris Wireless Martin Feuerstein Bob Dressler (VA) Qualcomm Jim DeLoa

13、ch Randy Gellens (VA) Qwest Mike Fargano Steve Chittick (VA) Red Sky Bill Mertka Brian Schwarz (VA) Rural Cellular Association (RCA) Art Prest Tim Raven (VA) Sprint Robert Montgomery Jim Propst (VA) ATIS-0500006.2008 iii Organization Represented Name of Representative Tarrant County 9-1-1 District B

14、ill Horne Kevin Kleck (VA) Telecommunication Systems (TCS) Richard Diskinson Roger Marshall (VA) TechnoCom Khaled Dessouky Janice Partyka (VA) Telcordia Anand SkundiEric Arolickl (VA) Texas Commission on State Emergency Communications Paul Mallett T-Mobile USA Jim Nixon Organization Represented Name

15、 of Representative TruePosition Gustavo Pavon Matthew Ward (VA) Verizon Maureen Napolitano Verizon Wireless Susan Sherwood Robert Uwaszji (VA) Virginia Information Technologies Agency (VITA) Steve Marzolf Dorothy Spears-Dean (VA) Vonage Martin Hakim Din Washington DC PSAP Susan Nelson Washington Sta

16、te Military Department EMD 9-1-1 Davis Irwin Bob Oenning (VA) Windstream Jackson Mobbs The Next Generation Emergency Services (NGES) Subcommittee was responsible for the development of this document. ATIS-0500006.2008 iv TABLE OF CONTENTS 1 INTRODUCTION/EXECUTIVE SUMMARY. 1 2 NORMATIVE REFERENCES 1

17、3 XML NAMESPACES 2 4 DEFINITIONS. 2 5 ABBREVIATIONS, ACRONYMS, & SYMBOLS . 2 6 ALI SERVICE AS AN EISI ENTITY 2 7 ALI SERVICE FUNCTIONAL INTERFACES . 2 7.1 QUERY AND ADVISORY 3 7.1.1 Interface Specification: Query . 3 7.1.2 Interface Specification: Advisory . 3 7.2 ALI DISCREPANCY 3 7.2.1 Interface S

18、pecification: ALI Discrepancy 3 7.3 PSAP MISROUTE . 4 7.3.1 Interface Specification: PSAP Misroute. 4 8 ALI SERVICE USE CASES. 4 8.1 STANDARD QUERY. 4 8.2 KEY QUALIFIED REGISTRATION . 4 8.3 KEY QUALIFIED RESOLUTION 5 8.4 INFORMATION DISCREPANCY REPORTING. 5 8.5 MISROUTE . 6 9 CONFORMANCE REQUIREMENT

19、S . 6 9.1 EISI CONFORMANCE PROFILE 6 9.2 ALI SERVICE FUNCTIONAL INTERFACES. 7 10 BINDINGS . 7 10.1 FUNCTIONAL INTERFACE: QUERY AND ADVISORY 7 10.2 FUNCTIONAL INTERFACE: ALI DISCREPANCY. 7 10.3 FUNCTIONAL INTERFACE: PSAP MISROUTE 8 A WSDL DESCRIPTIONS 9 A.1 *DISCREPANCY* 9 A.2 *MISROUTE* . 10 B XML S

20、CHEMAS. 13 B.1 *EISI ALI SERVICE* . 13 TABLE OF FIGURES FIGURE 1 - SYNCHRONOUS QUERY RESPONSE 4 FIGURE 2 - KEY REGISTRY . 5 FIGURE 3 - KEY RESOLUTION AND PROVIDER QUERY . 5 FIGURE 4 - INFORMATION DISCREPANCY 6 FIGURE 5 - MISROUTE 6 TABLE OF TABLES TABLE 1 XML NAMESPACES. 2 TABLE 2 - DISCREPANCY STAT

21、US RESPONSE STATUS CODES 7 TABLE 3 - MISROUTE STATUS RESPONSE STATUS CODES . 8 AMERICAN NATIONAL STANDARD ATIS-0500006.2008 American National Standard for Telecommunications Emergency Information Services Interfaces (EISI) ALI Service 1 1 INTRODUCTION/EXECUTIVE SUMMARY This document contains standar

22、ds for an ALI Service implementing the Emergency Information Services Interface (EISI) in an Emergency Services Network. An EISI consumer of this ALI Service can retrieve location information (ALI) and also report ALI discrepancy and misroute errors. The EISI consumer is an ESMI.RG (Response Gateway

23、) entity in an ESMI-mediated configuration as defined in 1. Otherwise any EISI entity may be an ALI Service consumer - i.e., EPES or ECES entities. This standard builds on the NENA ALI Query Service (AQS) interface specification as defined in 3, and more specifically on the SOAP binding of that inte

24、rface (also defined as part of 3). The location information (i.e., ALI) retrieved by the ALI Service is structured according to the NENA XML ALI standard as defined in 4. 2 NORMATIVE REFERENCES The following standard contains provisions which, through reference in this text, constitute provisions of

25、 this American National Standard. At the time of publication, the edition indicated was valid. All standards are subject to revision, and the parties to agreements based on this American National Standard are encouraged to investigate the possibility of applying the most recent edition of the standa

26、rd indicated below. 1 ATIS-0500008, Emergency Services Network Interfaces Framework, October 2006.12 ATIS-0500007.2008, Emergency Information Services Interface (EISI) Implemented with Web Services, May 2008.13 NENA 04-005, NENA ALI Query Service Standard, November 21, 2006.24 ALI Response & GIS Map

27、ping 02-010, NENA Standard Formats & Protocols for ALI Data Exchange3. 1This document is available from the Alliance for Telecommunications Industry Solutions (ATIS), 1200 G Street N.W., Suite 500, Washington, DC 20005. 2This document is available at: . 3Available at: . ATIS-0500006.2008 2 3 XML NAM

28、ESPACES The following XML namespaces are used throughout this document to reference objects defined in XML Schema and WSDL documents associated with Table 1: Prefix Namespace URI Description aqs urn:nena-org:dtc:aqs NENA ALI Query Service namespace XML Schema type definitions and AQS message types a

29、qsi urn:nena-org:dtc:aqs:ws NENA ALI Query Service Interface (WSDL) namespace WSDL abstract and concrete (SOAP) service descriptionsTable 1 XML Namespaces 4 DEFINITIONS Please refer to Reference 1. 5 ABBREVIATIONS, ACRONYMS, & SYMBOLS Please refer to Reference 1. 6 ALI SERVICE AS AN EISI ENTITY The

30、ALI Service defines and exposes a native set of functional interfaces related to ALI retrieval and error reporting. As an EISI entity it is also required to comply with EISI conformance requirements. More specifically, the EISI ALI Service complies with the EISI Information Delivery Profile includin

31、g the following additional constraints: 1. The Key Qualified Source Feature is optional by default, but becomes mandatory when the ALI Service is used in an ESMI environment - i.e., when the ALI Service consumer entity is an ESMI.RG entity. 2. The Service Availability Feature is optional by default,

32、 but becomes mandatory when the ALI Service is used in an ESMI environment - i.e., when the ALI Service consumer entity is an ESMI.RG entity. 7 ALI SERVICE FUNCTIONAL INTERFACES The ALI Service defines and exposes the following functional interfaces that abstract ALI retrieval and error reporting ca

33、pabilities. ATIS-0500006.2008 3 7.1 Query and Advisory The Query functional interface supports the retrieval of ALI while the Advisory functional interface allows one party to send an advisory to the other. The defining interface specifications actually expose a subset of the NENA ALI Query Service

34、(AQS) interface specification rather than introduce native definitions. Consequently, ALI Service consumer entities must behave as AQS Consumers, and ALI Service provider entities must behave as AQS Providers as defined by the AQS standard 3. 7.1.1 Interface Specification: Query This interface speci

35、fication exposes the aqsi:Query operation4- a basic request-response interaction wherein an XML formatted ALI 4 is returned in response to a query request. Provider entity: ALI Service Provider 7.1.2 Interface Specification: Advisory This interface specification exposes the aqsi:Advisory operation5-

36、 a one-way interaction wherein an ALI Service consumer advises an ALI Service provider that processing related to a given call is terminated so that associated resources can be released for example. Provider entity: ALI Service Provider 7.2 ALI Discrepancy The ALI Discrepancy interface is invoked by

37、 an EISI Consumer Entity to inform a service provider of a discrepancy with the ALI information it received. 7.2.1 Interface Specification: ALI Discrepancy There are two request messages and correlated responses. The first request message is the ReportDiscrepancy message issued by the EISI Consumer.

38、 This message contains the Key received, the received data and the data in discrepancy. In response to this message, a ReturnDiscrepancy message is returned with a Tracking_Key that can be used by the EISI Consumer to request status. The second request message is the DiscrepancyStatus message that r

39、equests the disposition of the discrepancy. This message includes the Tracking_Key as the parameter. In response, the EISI Provider issues the DiscrepancyStatus message with the DiscrepancyStatus parameter that provides the status of the discrepancy. 4This section references the abstract definition.

40、 5This section references the abstract definition. ATIS-0500006.2008 7.3 PSAP Misroute The PSAP Misroute interface is invoked by an EISI Consumer Entity to inform a service provider of a misrouted call. 7.3.1 Interface Specification: PSAP Misroute There are two request messages and correlated respon

41、ses. The first request message is the ReportMisroute message issued by the EISI Consumer. This message contains the Key received. In response to this message, a ReturnDiscrepancy message is returned with a Tracking_Key that can be used by the EISI Consumer to request status. The second request messa

42、ge is the MisrouteStatus message that requests the disposition of the discrepancy. This message includes the Tracking_Key as the parameter. In response, the EISI Provider issues the MisrouteStatusResponse message with the DiscrepancyStatus parameter that provides the status of the discrepancy. 8 ALI

43、 SERVICE USE CASES This section provides the use cases for the ALI service and then illustrates how the service is constructed through features and profiles. Features represent all of the capabilities supported by a service and profiles define when a feature is required in order to be conformant. Re

44、fer to the EISI specification 2 for more description of features, profiles, and conformance. 8.1 Standard Query For this sequence diagram, the EISI consumer queries the ALI Service using the NENA ALI Query Service to obtain location information. ANI or a Key is passed in the AQS request and the loca

45、tion information is returned in an XML format. That location information is then displayed at an Emergency Call Takers position. Figure 1 - Synchronous Query Response 8.2 Key Qualified Registration Some services only to apply to a certain set of Keys and may be queried only for those keys. For a fur

46、ther definition of Key resolution, see 2. An example would be a data base that contains Hazmat information for a location where the Keys are the TN(s) associated with that location. Therefore, as shown in Figure 2, the ALI Service registers the Keyset with the Key Registry. 4 ATIS-0500006.2008 Figur

47、e 2 - Key Registry 8.3 Key Qualified Resolution The EISI consumer that wants to obtain location information for a service that supports Key qualified information must first determine which service providers offer a service, and then query all of the service providers that have information. As shown

48、in Figure 3, the EISI consumer queries the Key Registry with the Key of interest. The Key registry returns the list of providers that have information regarding the Key. The consumer then queries all providers that match for that Key. Figure 3 - Key Resolution and Provider Query 8.4 Information Disc

49、repancy Reporting It is possible that the location information received in 8.1 contained information in error. In that case, the consumer would report this error to the provider. In return, the provider would provide a tracking key. At some point later, the consumer may interrogate for the disposition of the error report. 5 ATIS-0500006.2008 Figure 4 - Information Discrepancy 8.5 Misro