1、 JOINT STANDARD J-STD-110.v002 JOINT ATIS/TIA NATIVE SMS/MMS TEXT TO 9-1-1 REQUIREMENTS AND ARCHITECTURE SPECIFICATION RELEASE 2 As a leading technology and solutions development organization, the Alliance for Telecommunications Industry Solutions (ATIS) brings together the top global ICT companies
2、to advance the industrys most pressing business priorities. ATIS nearly 200 member companies are currently working to address the All-IP transition, network functions virtualization, big data analytics, cloud services, device solutions, emergency services, M2M, cyber security, network evolution, qua
3、lity of service, billing support, operations, and much more. These priorities follow a fast-track development lifecycle from design and innovation through standards, specifications, requirements, business use cases, software toolkits, open source solutions, and interoperability testing. ATIS is accr
4、edited by the American National Standards Institute (ANSI). The organization is the North American Organizational Partner for the 3rd Generation Partnership Project (3GPP), a founding Partner of the oneM2M global initiative, a member of and major U.S. contributor to the International Telecommunicati
5、on Union (ITU), as well as a member of the Inter-American Telecommunication Commission (CITEL). For more information, visit www.atis.org. The Telecommunications Industry Association (TIA) is the leading trade association representing the global information and communications technology (ICT) industr
6、ies through standards development, government affairs, business opportunities, market intelligence, certification and world-wide environmental regulatory compliance. With support from its 600 members, TIA enhances the business environment for companies involved in telecommunications, broadband, mobi
7、le wireless, information technology, networks, cable, satellite, unified communications, emergency communications and the greening of technology. TIA is accredited by ANSI. Notice of Disclaimer Technical Specification Group Core Network and Terminals; IP Multimedia Call Control Protocol based on Ses
8、sion Initiation Protocol (SIP) 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
9、Short Message Service (SMS).6Ref 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,
10、 Version 2, March 30, 2001.1 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
11、 Specification Group Core Network 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 PS
12、AP Interface, Issue 1 With Revision 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.8R
13、ef 26 NENA 03-003, NENA Recommendation 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 av
14、ailable from the Telecommunications 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 Interna
15、tional Telecommunications Union 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 Generat
16、ion 911 Applications; May 17, 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 Improve
17、ments for Interim SMS (Text) 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); Funct
18、ional Description; Stage 2.6 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
19、 interface Layer 3 specification 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
20、TS 24.301, Technical Specification 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 Te
21、rrestrial Radio Access Network (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
22、Application Part (MAP) specification.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
23、 in the body of an MMS message 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
24、 MMS message with a single address 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
25、Message to Emergency Services. 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 plai
26、n text media type messaging applies 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 de
27、vice user. Carol Public Safety 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 connect
28、ed to his Service Providers home 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 cove
29、ring a region within Steves Service 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 wil
30、l be able to communicate to the 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
31、and sends this SMS message to 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
32、and Steve may exchange messages 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
33、. 8. Carol ends the text dialogue 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
34、-1. However, in this scenario, 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 tex
35、t messaging to emergency service, 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 co
36、de 911. Sharon is subscribed 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 act
37、ive sessions (e.g., voice, data, 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
38、is not capable of receiving end-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 emerg
39、ency services. 5.2.5 Normal Flow 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 de
40、termined based upon the cell 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 t
41、o emergency services is not available 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
42、 sends an SMS message to the 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 s
43、ite location) for the mobile 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
44、 the text message signaling to 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
45、Providers network supports SMS 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 (a
46、nd 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) prior to Tom sending SMS to 9-1-1. PSAP covering a region within Toms Service Provider network is capable of receiving end-users SMS messages in some
47、 form. An error condition exists which prevents either the determination of the associated PSAP or the routing of the text message to the associated PSAP. 5.3.4 Post-Conditions Tom will be informed that text messaging to emergency services is not available in his current location and that he will ne
48、ed to place a voice call to emergency services. 5.3.5 Normal Flow 1. Tom already has his mobile device turned on. 2. Tom encounters an emergency situation and decides to send an SMS message to the PSAP. 3. Tom composes an SMS message describing the emergency and sends this SMS message to 9-1-1. 4. A
49、n error condition exists which prevents either the determination of the associated PSAP or the routing of the text message to the associated PSAP. 5. Tom receives a bounce-back SMS message that indicates that text messaging to emergency services is not available in his current location and that he should place a voice call to 9-1-1. J-STD-110.v002 12 5.4 Use Case 4 Text Message to Emergency Services with Differe
