ATIS J-STD-110-2015 Joint ATIS TIA Native SMS to 9-1-1 Requirements and Architecture Specification Release 2.pdf

《ATIS J-STD-110-2015 Joint ATIS TIA Native SMS to 9-1-1 Requirements and Architecture Specification Release 2.pdf》由会员分享，可在线阅读，更多相关《ATIS J-STD-110-2015 Joint ATIS TIA Native SMS to 9-1-1 Requirements and Architecture Specification Release 2.pdf（94页珍藏版）》请在麦多课文档分享上搜索。

1、J-STD-110.v002 Joint Standard on Joint ATIS/TIA Native SMS/MMS Text to 9-1-1 Requirements and Architecture Specification Release 2 Approved May 2015 Abstract This Standard defines the requirements, architecture, and procedures for text messaging to 9-1-1 emergency services using native Commercial Mo

2、bile Service Provider CMSP SMS or MMS text capabilities for the existing generation and next generation (NG9-1-1) Public Safety Answering Points (PSAPs). J-STD-110.v002 ii Foreword As a leading technology and solutions development organization, the Alliance for Telecommunication Industry Solutions (

3、ATIS) brings together the top global information and communications technology (ICT) companies to advance the industrys most-pressing business priorities. ATIS serves the public through improved understanding between service providers, customers, and manufacturers. The Wireless Technologies and Syst

4、ems Committee (WTSC) develops and recommends standards and technical reports related to wireless and/or mobile services and systems, including service descriptions and wireless technologies. WTSC develops and recommends positions on related subjects under consideration in other North American, regio

5、nal, and international standards bodies. The Emergency Services Interconnection Forum (ESIF) provides a forum to facilitate the identification and resolution of technical and/or operational issues related to the interconnection of wireline, wireless, cable, satellites, Internet and emergency service

6、s networks. The Telecommunications Industry Association (TIA) is the leading trade association representing the global information and communications technology (ICT) industries through standards development, government affairs, business opportunities, market intelligence, certification and world-wi

7、de environmental regulatory compliance. Engineering Committee TR-45 develops performance, compatibility, interoperability and service standards for mobile and personal communications systems. These standards pertain to, but are not restricted to, service information, wireless terminal equipment, wir

8、eless base station equipment, wireless switching office equipment, ancillary apparatus, auxiliary applications, inter-network and intersystem operations, interfaces, and wireless packet data technologies. Suggestions for improvement of this document are welcome. They should be sent to the Alliance f

9、or Telecommunications Industry Solutions, WTSC, 1200 G Street NW, Suite 500, Washington, DC 20005. The mandatory requirements are designated by the word shall and recommendations by the word should. Where both a mandatory requirement and a recommendation are specified for the same criterion, the rec

10、ommendation represents a goal currently identifiable as having distinct compatibility or performance advantages. The word may denotes a optional capability that could augment the standard. The standard is fully functional without the incorporation of this optional capability. The ATIS WTSC-SN and ES

11、IF-NGES Subcommittees and the TIA TR-45.8 Subcommittee were responsible for the development of this document. J-STD-110.v002 iii Table of Contents 1 SCOPE, PURPOSE, Technical Specification Group Core Network and Terminals; IP Multimedia Call Control Protocol based on Session Initiation Protocol (SIP

12、) and Session Description Protocol (SDP); Stage 3.6Ref 14 TIA-41-E, Wireless Radiotelecommunications Intersystem Operations.4Ref 15 3GPP TS 23.040, 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Technical realization of the Short Message Service (SMS).6

13、Ref 16 NENA 00-001, NENA Master Glossary of 9-1-1 Terminology, Version 16, August 21, 2011.1 Ref 17 NENA 03-002, NENA Standard for the Implementation of Enhanced MF Signaling, E9-1-1 Tandem to PSAP, Version 3, January 17, 2007.1 Ref 18 NENA 04-001, E9-1-1 PSAP Equipment, Version 2, March 30, 2001.1

14、Ref 19 NENA 04-002, ALI Query Service, Version 1, November 21, 2006.1 Ref 20 NENA 03-005, NENA Standard Generic Requirements for an Enhanced 9-1-1 Selective Routing Switch, Version 1, January 15, 2004.1 Ref 21 3GPP TS 24.341, 3rd Generation Partnership Project; Technical Specification Group Core Net

15、work and Terminals; Support of SMS over IP networks; Stage 3.6Ref 22 GR-350-CORE, E911 Public Safety Answering Point: Interface Between a 1A/1ESSTM Switch and Customer Premises Equipment, Issue 1, June 2003.7Ref 23 GR-2953-CORE, Enhanced MF Signaling: E9-1-1 Tandem to PSAP Interface, Issue 1 With Re

16、vision 1, December 1998.7Ref 24 GR-2956-CORE, CCS/SS7 Generic Requirements in Support of E9-1-1 Service, Version 5, December 2002.7Ref 25 ITU-T Recommendation V.18, Operational and Interworking Requirements for DCE:s Operating in the Text Telephone Mode, November 2000.8Ref 26 NENA 03-003, NENA Recom

17、mendation for the implementation of Inter-Networking, E9-1-1 Tandem to Tandem, Version 1, February 1, 2000.1Ref 27 NENA 05-001, NENA Standard for the Implementation of the Wireless Emergency Service Protocol E2 Interface, Version 1, December 2, 2003.14This document is available from the Telecommunic

18、ations Industry Association. 5This document is available from the Internet Engineering Task Force (IETF). 6This document is available from the 3rdGeneration Partnership Project (3GPP) 7This document is available from Telcordia 8This document is available from the International Telecommunications Uni

19、on J-STD-110.v002 3 Ref 28 NENA 77-501, NG9-1-1 Transition Planning Considerations, Version 1, February 24, 2011.1Ref 29 FCC 13-64, Federal Communications Commission First Report and Order In the Matter of Facilitating the Deployment of Text-to-911 and Other Next Generation 911 Applications; May 17,

20、 2013.9Ref 30 J-STD-110.01.v002, Implementation Guidelines for J-STD-110, Joint ATIS/TIA Native SMS/MMS Text to 9-1-1 Requirements and Architecture Specification, Release 2; November 2013.10Ref 31 CSRIC IV Working Group 1, Final Report Investigation into Location Improvements for Interim SMS (Text)

21、to 9-1-1, June 2014.9 Ref 32 3GPP TS 22.140, Technical Specification Group Services and System Aspects; Multimedia Messaging Service (MMS) Stage 1.6Ref 33 3GPP TS 23.140, Technical Specification Group Core Network and Terminals; Multimedia Messaging Services (MMS); Functional Description; Stage 2.6

22、Ref 34 3GPP TS 23.204, Technical Specification Group Core Network and Terminals; Support of Short Message Service (SMS) over generic 3GPP Internet Protocol (IP) access; Stage 2.6Ref 35 3GPP TS 24.008, Technical Specification Group Core Network and Terminals; Mobile radio interface Layer 3 specificat

23、ion Technical Specification Group Core Network and Terminals; Core network protocols; Stage 3.6Ref 36 3GPP TS 24.011, Technical Specification Group Core Network and Terminals; Point-to-Point (PP) Short Message Service (SMS) support on mobile radio interface.6Ref 37 3GPP TS 24.301, Technical Specific

24、ation Group Core Network and Terminals; Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3.6Ref 38 3GPP TS 23.401, Technical Specification Group Services and System Aspects; General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Networ

25、k (E-UTRAN) access; Stage 2.6Ref 39 3GPP TS 23.272, Technical Specification Group Services and System Aspects; Circuit Switched (CS) fallback in Evolved Packet System (EPS); Stage 2.6Ref 40 3GPP TS 29.002, Technical Specification Group Core Network and Terminals; Mobile Application Part (MAP) specif

26、ication.63 Definitions, Acronyms, text to 911 is not available.” 29. If conditions warrant the return of a bounce-back message, no additional messaging should be offered. 30. Messages generated by the PSAP are out of scope of this Standard. 31. Only plain text media type in the body of an MMS messag

27、e is accepted for delivery to the PSAP. This treats the scenario where the handset sent an MMS message even though the message only contained plain text media type. The delivery of non-plain text media to the PSAP is out of scope in this Standard. 32. The TCC receives an MMS message with a single ad

28、dress corresponding to 9-1-1 emergency services. 33. When the TCC receives an MMS message, the TCC will respond back toward the user with an SMS message. 5 Use Cases This clause defines the following end user view Use Cases that applies to this Standard: Use Case 1 Text Message to Emergency Services

29、. Use Case 2 PSAP Not Supporting Text Message to Emergency Services. Use Case 3 Error Routing Text Message to Emergency Services. Use Case 4 Text Message to Emergency Services with Different TCC Providers. Note that the term SMS is used in the Use Cases; however MMS plain text media type messaging a

30、pplies for all the Use Cases. J-STD-110.v002 9 5.1 Use Case 1 Text Message to Emergency Services 5.1.1 Short Description Steve is a wireless service user with a mobile device. In an emergency situation, Steve sends an SMS message to the PSAP. 5.1.2 Actors Steve Mobile device user. Carol Public Safet

31、y Telecommunicator (PST). 5.1.3 Pre-Conditions Steves Service Providers network supports SMS to 9-1-1 capabilities. Steves mobile device supports SMS functionality to the three-digit code 911. Steve is subscribed to SMS services via his Service Provider. Steve is connected to his Service Providers h

32、ome network. Steve is aware that he can send SMS messages to a PSAP (and receive messages sent by a PSAP via SMS) while he is not roaming. Steves mobile device does not have any active sessions (e.g., voice, data, messaging) prior to Steve sending SMS to 9-1-1. PSAP covering a region within Steves S

33、ervice Provider network is capable of receiving end-users SMS messages in some form. Coarse location information (e.g., cell site location) is available for the determination of the appropriate PSAP for routing of the text message content. 5.1.4 Post-Conditions Steve will be able to communicate to t

34、he PSAP successfully via SMS using his mobile device. 5.1.5 Normal Flow 1. Steve already has his mobile device turned on. 2. Steve encounters an emergency situation and decides to send an SMS message to the PSAP. 3. Steve composes an SMS message describing the emergency and sends this SMS message to

35、 9-1-1. 4. The appropriate PSAP is selected based upon the cell site serving Steve, and the message in text format is delivered to the specified PSAP. 5. Carol is a PST and receives Steves message. Carol responds back and Steve receives Carols messages via SMS. 6. Carol and Steve may exchange messag

36、es in order for Steve to describe the overall emergency situation. Equally, Steve may describe his location in a message if asked by Carol. 7. Carol determines that dispatching emergency services is warranted and creates a request for service in her PSAPs dispatch system. 8. Carol ends the text dial

37、ogue according to the PSAPs policies and procedures. J-STD-110.v002 10 5.2 Use Case 2 PSAP Not Supporting Text Message to Emergency Services 5.2.1 Short Description Sharon is a wireless service user with a mobile device and, in an emergency situation, sends an SMS to 9-1-1. However, in this scenario

38、, the PSAP associated with Sharons current location does not support the text messaging to emergency services capability and there is no alternative PSAP which does support text messaging to emergency services. NOTE: If there is an alternative PSAP which does support text messaging to emergency serv

39、ice, this would be the same as Use Case 1 from the users perspective. 5.2.2 Actors Sharon Mobile device user. 5.2.3 Pre-Conditions Sharons Service Providers network supports SMS to 9-1-1 capabilities. Sharons mobile device supports SMS functionality to the three-digit code 911. Sharon is subscribed

40、to SMS services via her Service Provider. Sharon is connected to her Service Providers home network. Sharon is aware that she can send SMS messages to a PSAP (and receive messages sent by PSAP via SMS) while she is not roaming. Sharons mobile device does not have any active sessions (e.g., voice, da

41、ta, messaging) prior to Sharon sending SMS to 9-1-1. Coarse location information (e.g., cell site location) is available for the determination of the appropriate PSAP for routing of the text message content. PSAP covering a region within Sharons Service Provider network is not capable of receiving e

42、nd-users SMS messages and there are no alternative PSAP(s) which support text messaging. 5.2.4 Post-Conditions Sharon will be informed that text messaging to emergency services is not available in her current location and that she will need to place a voice call to emergency services. 5.2.5 Normal F

43、low 1. Sharon already has her mobile device turned on. 2. Sharon encounters an emergency situation and decides to send an SMS message to the PSAP. 3. Sharon composes an SMS message describing the emergency and sends this SMS message to 9-1-1. 4. The associated PSAP is determined based upon the cell

44、site serving Sharon. However, the associated PSAP does not support text messaging to emergency services and there is no alternative PSAP which does support text messaging to emergency services. 5. Sharon receives a bounce-back message that indicates that text messaging to emergency services is not a

45、vailable in her current location and that she should place a voice call to 9-1-1. J-STD-110.v002 11 5.3 Use Case 3 Error Routing Text Message to Emergency Services 5.3.1 Short Description Tom is a wireless service user with a mobile device. In an emergency situation, Tom sends an SMS message to the

46、PSAP. However, an error condition exists which prevents either the determination of the associated PSAP or the routing of the text message to the associated PSAP. The following are examples of these potential error conditions: No coarse location information (e.g., cell site location) for the mobile

47、device can be obtained or determined. No PSAP configuration information is available for the subscribers current location. PSAP configuration information for subscribers current location is incomplete, invalid, or cannot be retrieved. An error occurs when trying to route the text message signaling t

48、o the associated PSAP. This Use Case only applies to the point in the network where the SMS to 9-1-1 service functionality is performed and to its routing of the text message to the appropriate PSAP. 5.3.2 Actors Tom Mobile device user. 5.3.3 Pre-Conditions Toms Service Providers network supports SM

49、S to 9-1-1 capabilities. Toms mobile device supports SMS functionality to the three-digit code 911. Tom is subscribed to SMS services via his Service Provider. Tom is connected to his Service Providers home network. Tom is aware that he can send SMS messages to a PSAP (and receive messages sent by PSAP via SMS) while he is not roaming. Toms mobile device does not have any active sessions (e.g., voice, data, messaging) prio