ATIS 0500023-2013 Applying Common IMS to NG9-1-1 Networks.pdf

1、 ATIS-0500023 ATIS Standard on - APPLYING COMMON IMS TO NG9-1-1 NETWORKS As a leading technology and solutions development organization, ATIS brings together the top global ICT companies to advance the industrys most-pressing business priorities. Through ATIS committees and forums, nearly 200 compan

2、ies 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 development lifecycle from design and innovation through solutions that in

3、clude 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 Partner for the 3rd Generation Partnership Project (3GPP), a founding

4、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 information, visit . Notice of Disclaimer Service aspects; Service princip

5、les, Release 12, Section 10, December 2012.51This document is available from the National Emergency Number Association. 2This document is available from the Alliance for Telecommunications Industry Solutions (ATIS), 1200 G Street N.W., Suite 500, Washington, DC 20005 . 3This document is available fr

6、om the Alliance for Telecommunications Industry Solutions (ATIS), 1200 G Street N.W., Suite 500, Washington, DC 20005 . 4This document is available from the Alliance for Telecommunications Industry Solutions (ATIS), 1200 G Street N.W., Suite 500, Washington, DC 20005 . ATIS-0500023 2 9 NENA 08-506,

7、Version 1, NENA Emergency Services IP Network Design for NG9-1-1, December 14, 2011.1 3 Definitions, Acronyms, further routing may occur beyond the common URI. Routing 1400-200: It shall be possible that certain routing information only be accessible by authorized entities. Routing 1500-0100: It sha

8、ll be possible to change routing may change on short notice due to local conditions, traffic, failures, schedule, etc. Routing 1700-0100: Routing information must be secured against unauthorized modification. PSAPs (or perhaps a higher level civic authority such as a county, state/province, or natio

9、nal body) must be the only entities who can authorize a change to routing information. Clarification: Higher authorities can chose how calls are routed to a PSAP. Routing within the NG911SA network is up to the operator. This requirement applies to routing information in the ECRF. Routing 1800-0100:

10、 It must be possible to supply contingency routing information for example, an alternate URI or an E.164 to be used when normal routing fails. Routing 1900-0100: Multiple types of failures may have different contingency routes. Routing 2000-0100: It must be possible to provide more than one continge

11、ncy route for the same type of failure. 10Errors are likely if it is possible that two conversions of data are made. For example, if conversion is made from civic to geo for routing, and the resulting geo is converted back to civic for dispatch, an “off-by-one” error can occur. These errors can be m

12、itigated by using the same database for each conversion. By making the PSAPs database available for conversion, such an approach could be used. ATIS-0500023 18 Routing 2100-0100: A procedure must be specified to handle “default route” capability when no location is available or the location informat

13、ion is corrupted. Routing 2200-0100: Location available at the time the call is routed may not be accurate. Updates to location may result in a different route and the system must accommodate this. If the call has not been answered before the update is available, the system may reroute the call auto

14、matically. After the call is answered, the PSAP may request the call be rerouted as part of a transfer operation. Routing 2500-0100: Entities routing emergency calls shall retain information used to choose a route for subsequent error resolution. Routing 2700-0100: There shall be mechanisms to route

15、 calls to one or more alternate PSAPs when a PSAP receives a very large number of calls (which is an instance of alternate-routing). Routing 2800-0100: Alternate-routing shall be able to be initiated by an authority designated by the PSAP. Routing 2900-0100: There shall be mechanisms to allow PSAPs

16、to accept or refuse such alternate-routed calls. No calls shall be alternate routed to another PSAP where the destination PSAP does not accept such routing. Routing 3000-0100: Prior arrangements for alternate-routing calls shall be possible, but provisions must be made for dynamically changing such

17、arrangements. Routing 3100-0100: Alternate-routed calls shall be capable of being bridged back to the original destination PSAP if appropriate. Routing 3200-0100: Alternate-routed calls shall be recognizable as alternate-routed before they are answered at a PSAP. Routing 3300-0100: Alternate-routing

18、 mechanisms should be designed to function well in disaster situations where loss of connectivity will be common. Routing 3400-0100: There shall be mechanisms to carry the reason for alternate routing (differentiating for example on incoming call queue busy from failure of an element) and make diffe

19、rent routing decisions based on the reason. Routing 3500-0100: PSAPs shall be able to specify treatment of its calls in all abnormal situations, where treatment includes return of busy indication, answering at an alternate PSAP, connection to an Interactive Voice Response Unit, etc. NENA 4.1.9 Conne

20、ctions to the Emergency Services IP Network Connections 0100-0100: If there is network connectivity between the emergency caller and a PSAP, and routing information is available, the call should go through, even if other parts of the network are not reachable. Connections 0200-0100: PSAPs shall have

21、 functions to determine the status of the Emergency Services IP Network. Clarification: The NG911SA network shall provide the ability for the PSAP to determine the status of the network. Connections 0300-0100: It must be possible to connect directly, via IP, to the Emergency Services IP Network, or

22、indirectly via the Internet. NENA 4.1.10 Support of existing wireline and wireless callers Existing 0100-0100: Backwards compatibility of existing wireline and wireless callers must be implemented. Existing 0200-0100: Support mechanisms for backwards compatibility may evolve, but at all times it mus

23、t be possible to accommodate existing originating offices and mobile switching centers without requiring changes to such switches. NENA 4.2.1 Information Access and Services Awareness ServiceBasic 0100-0100: Databases and services shall have globally unique identifiers. ATIS-0500023 19 ServiceBasic

24、0200-0100: Mechanisms for discovery of, and connection to, services which MAY be used by services provided shall be specified. Clarification: Each service must have a discovery mechanism. ServiceBasic 0300-0100: Where there are multiple instances of the same service (same id), there must be a mechan

25、ism to identify each instance. ServiceBasic 0400-0100: There shall be a mechanism by which an entity can determine if a particular database or service is provided, and, if so, how to contact the database or service within a domain. ServiceBasic 0500-0100: There should be a mechanism by which multipl

26、e service providers providing the same service but differentiated by a qualifier can be selected based on a specific value of the qualifier. ServiceBasic 0600-0100: It should be possible to have the exact same service offered by multiple, competing service providers. Clarification: The NG911SA netwo

27、rk shall provide standard interfaces that allow access to external databases. ServiceBasic 0700-0100: PSAPs must always opt-in to services provided on the network. No services shall be provided which a PSAP does not explicitly request, regardless of whether or not the service is free or has a cost a

28、ssociated with it. ServiceBasic 0800-0100: Services must inform PSAPs of its availability or non-availability, both planned and unplanned. ServiceBasic 0800-0100: Provisioning of new services to a PSAP must be graceful and not require non-related services to be affected. Clarification: These were du

29、plicate numbers in the NENA TRD, but they are two different requirements. NENA 4.2.2 Incidents Incident.0100-0100: It shall be possible to uniquely identify an agency within the national Emergency Services IP Network. Incident.0200-0100: It shall be possible to uniquely identify an agent within an a

30、gency. Incident.0300-0100: It shall be possible to uniquely identify a Call Request throughout its life cycle, across multiple transfers of the call among agencies. Incident.0400-0100: A PSAP or a service on the ESInet may declare an Incident. Clarification: The NG911SA network needs to assign a uni

31、que Incident Identifier for each call. Incident 1000-0100: It shall be possible to interleave messages for multiple active incidents in any order. NENA 4.2.3 Bridge Services Bridge 0100-0100: Bridge services may be provided as a service on the ESInet, or may be provided internal to the PSAP. Bridge

32、0200-0100: All participants in the bridge must have access to the call identifier of the original call. Clarification: All PSAPs associated with the bridge must have access to conference services to support this. Bridge 0300-0100: Information gathered by one agency on the call request must be availa

33、ble to other agencies being bridged. It must be possible for the bridged agency to be made aware such information exists. Bridge 0400-0100: Any agency on the call must be made aware of any other agencies (or external participant) bridged to the call. Clarification: All PSAPs associated with the brid

34、ge must have access to conference services to support this. Bridge 0500-0100: Provision for bridging agencies that are only accessible via Selective Router or PSTN must be defined. ATIS-0500023 20 Bridge 0600-0100: An i3 PSAP must be able to transfer or bridge a call to or from any PSAP, including i

35、nternationally, with all data that accompanied the call (e.g., location). Bridge 0700-0100: The call-taker must be able to control what the caller hears while bridge/transfer operations are completed. NENA 4.2.5 Report and Status Services For future study. NENA 4.2.6 Network Requirements Network.010

36、0-0100: The Network connectivity between the PSAP and the ESInet shall be a private or virtual private network based upon TCP/IP. Network.0200-0100: The protocols and the corresponding networks shall be capable of supporting the transmission of images, video, high resolution graphics, non-real-time

37、voice, and other capabilities. Network.0300-0100: Connections between the PSAP and ESInet shall be secured TCP/IP connections such that advanced authorization, authentication, and security features can be implemented. Network.0400-0100: DiffServ Code Points to be used for PSAP needs shall be specifi

38、ed. Network.0500-0100: NAT may be required in some jurisdictions between the Emergency Services IP Network and the Internet, so all services intending to use Internet connections must assume NAT. Network.0600-0100: i3 defined service applications must be capable of operating on IPv4 and IPv6 network

39、 infrastructures. Clarification: ESInet shall support both IPV4 and IPV6, but an application may support one or the other. NENA 4.2.7 Protocol Requirements Protocol.0100-0100: Domain names (DNS) should be used in preference to IP addresses. Protocol.0200-0100: Application interfaces should have vers

40、ions, and versions should be negotiable. Protocol.0300-0100: Mechanisms used in failure and recovery situations shall be capable of being exercised to ensure they are operating properly. Protocol.0400-0100: Services should be designed such that making a service available or unavailable shall not aff

41、ect any other service not dependent on it. This may be an obligation on both the client and the server. Protocol 0500-0100: Reliable services should be designed such that failure of a server shall not affect the service. NENA 4.2.8 Security/Privacy Security.0100-0100: Elements connected to the ESIne

42、t which provide access to sensitive data or services shall require users and/or their agencies to be authenticated prior to being granted access to such element. Security 0200-0100: Authentication shall be by agency or by person, depending on the nature of the database or service provided. Person au

43、thentication is preferred in order to provide accountability for actions taken by personnel in the network. Security 0300-0100: The specific authentication mechanisms for the Emergency Services IP Network should be that agreed to among public safety agencies. The specific credentialing mechanisms em

44、ployed should be as agreed to. Security 0400-0100: i3 shall define credentialing mechanisms for agencies and employees/contractors within those agencies. ATIS-0500023 21 Security 0500-0100: Credentials issued per Security 0400-0100: should be used for database access and service authentication. Secu

45、rity 0600-0100: Person-based authentication mechanisms shall be provided to support password-only (weak) or two-factor (strong) user authentication between a PSAP CPE and ESInet based on the configuration of the ESInet. Security 0700-0200: Password based authentication mechanisms shall protect the p

46、assword such that it is possible for the user to prove knowledge of the password without transmitting the password. Security 0800-0100: It must be possible for security-sensitive actions taken within the network to be associated with a person or agency in a manner that provides non-repudiation by th

47、e responsible party. Such actions must be historically traceable back to the responsible party in a manner that provides non-repudiation by the responsible party of the accuracy of the historical information. Security 0900-0100: Proxy authentication should be used so that “Single Sign On“ can be ach

48、ieved. Security 1000-0100: All sensitive communications over the Emergency Services IP Network that directly relate to emergency databases and services shall be protected by suitable Integrity Protection mechanisms. Security 1100-0100: All sensitive communications over the Emergency Services IP Netw

49、ork that directly relate to emergency databases and services shall be protected by suitable Privacy mechanisms. Security 1200-0100: The mechanisms chosen for Security requirements above shall use multiagency standards wherever possible. Security 2100-0100: i3 implementations should adhere to existing national standards and best practices in security. Security 2100-0200: Signaling and control elements of i3 implementations should conform to the standards and practices set forth in Generic Signaling and Control Plane Security Requirements for Evolving Networks American Nation