1、 JOINT STANDARD J-STD-110.01.v002 JOINT ATIS/TIA IMPLEMENTATION GUIDELINE FOR J-STD-110, 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 Solu
2、tions (ATIS) brings together the top global ICT companies 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, emerg
3、ency services, M2M, cyber security, network evolution, quality 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 so
4、urce solutions, and interoperability testing. ATIS is accredited 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 m
5、ajor U.S. contributor to the International Telecommunication 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 glob
6、al information and communications technology (ICT) industries 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
7、 companies involved in telecommunications, broadband, mobile wireless, information technology, networks, cable, satellite, unified communications, emergency communications and the greening of technology. TIA is accredited by ANSI. Notice of Disclaimer Release 2, May 2015.1Ref 2 FCC 13-64, Federal Co
8、mmunications Commission First Report and Order In the Matter of Facilitating the Deployment of Text-to-911 and Other Next Generation 911 Applications; May 17, 2013.21This document is available from the Alliance for Telecommunications Industry Solutions (ATIS), 1200 G Street N.W., Suite 500, Washingt
9、on, DC 20005 . 2This document is available from the Federal Communications Commission. J-STD-110.01.v002 2 Ref 3 J-STD-036-C, Enhanced Wireless 9-1-1 Phase II, 2009.3Ref 4 IETF RFC 4975, Message Session Relay Protocol (MSRP), September 2007.43 Definitions, Acronyms, or (b) to such classes of eligibl
10、e users as to be effectively available to a substantial portion of the public, as specified by regulation by the Federal Communications Commission. 3.1.3 Location-Based Services (LBS): Location-Based Services (LBS) refers to a framework that specifies all the necessary network elements and entities,
11、 their functionalities, interfaces, and the communication messages that are required to implement the positioning functionality in a wireless network. LBS are network capabilities that enable the deployment of location-based (value added) services. LBS are separate and distinct from E9-1-1 location
12、services. 3.1.4 Text Control Center Provider: A Text Control Center Provider provides the interworking between the SMS messages from/to a CMSP and to/from the PSAP and MMS messages from a CMSP. 3.2 Acronyms and For the MMS message being routed to the non-9-1-1 recipients, “911” will be removed from
13、the recipient address field. 7 Guidelines for Text Control Center Providers The TCC is the controlling functional element specified within J-STD-110 Ref 1. The TCC has the responsibility to: (1) convert various protocols and act as a gateway; (2) request location that may be used for routing; (3) re
14、quest routing instructions; and (4) initiate a dialogue with the PSAP through the appropriate interworking function of the TCC. 7The purpose of this binding is to link the SMSC and TCC, and request an SMPP session over the network connection for the submission or delivery of messages. (For more deta
15、iled information, see Annex B of J-STD-110 Ref 1.) T9eSuvINJaMTtwIfPPIfddw1foIfdtohe reference-1-1 messagmergency seervices Appltimately suparious intercon addition, thENA i3 ESIn-STD-110 Rnticipated thultimedia Emhe TCC will hose containithout text. the TCC rSAP/emergeSAP/emergethe TCC reetermines
16、thialogue with ill respond b-1. The TCCforwarded. the TCC reetermines tho the mobile architecture es to a PSArvices netwolication direcports deliverynnection arre reference aets (see Clauef 1 only sat delivery ofergency Serneed to consing text and eceives an ncy servicesncy servicesceives an Mat the
17、 PSAPthe PSAP anack to the mowill also proceives an Mat the PSAP/device with aFigure illustrated in P. There ark via a TTY tly from the of SMS/MMangements. rchitecture ilse 7.9), as wupports the additional mvices are depider three coadditional mMMS messanetwork is network andMS message/emergency d p
18、ass the pbile device wvide a courtMS messageemergency scourtesy textJ-STD7.1 High LeFigure 7.1 shre three maInterworkingHTTP IWF; aS text to 9-1lustrates supell as from ledelivery to thedia (e.g., grloyed. mbinations oultimedia attge that concapable of pass the plathat containservices netlain text m
19、edith a courtesesy text mesthat only coervices netwmessage sta-110.01.v007 vel Referenows a varietyin types of Function (IWnd (c) deliv-1 messagesport for locatigacy ALI syse PSAP of aphics, photof media in Machments, antains only preceiving Tein text media s plain text work is capaia type to thy te
20、xt messasage to the ntains multimork is capablting that mu2 ce Architectof approachdelivery mecF); (b) deliveery to a NENto legacy, tron dereferentems (see Cthe plain texs/pictures, vMS messaged 3) those lain text mext to 9-1-1, type to the Pmedia and able of receivhe PSAP/emege stating thPSAP indic
21、aedia types oe of receivingltimedia conteure es for delivehanisms: (ary to a transitA i3 ESInetansitional, ancing from elelause 7.7). t portion of ideos, etc.) ws: 1) those ocontaining media, after itit will createSAP/emergedditional muving Text to rgency servichat only the teting that addther than
22、plText to 9-1nt is not supry of SMS/MM) delivery to ional PSAP v(via the i3 d NENA i3 Pments assocMMS messaill be suppornly containinultimedia attdeterminesa dialoguency services ltimedia type9-1-1, it willes network. xt was forwaitional mediaain text med-1, it will respported. S text to a legacy ia
23、 a Web IWF) that SAPs via iated with ges. It is ted when g text, 2) achments that the with the network. s, after it create a The TCC rded to 9-was not ia, after it ond back J-STD-110.01.v002 8 When the PSAP responds to an incoming message that was originated via MMS, the TCC will send the response b
24、ack toward the user using SMS. 7.1 Location Services As defined in J-STD-110 Ref 1, SMS/MMS text to 9-1-1 messages are routed to the PSAP based upon location. That location may be a coarse location of the serving cell tower, cell sector centroid, or a more refined location that is provided via Locat
25、ion Based Services (LBS). Therefore, location provided to the PSAP is not guaranteed to be a dispatchable location, but a best-effort location based upon the capabilities of the CMSP network. When the TCC receives an SMS/MMS text to 9-1-1 text from the SMSC or a MMS to 9-1-1 text from the MMSC, the
26、TCC must query the Location Server to obtain a location that it uses to determine the PSAP/emergency services network; and eventually sends to the PSAP. It does so by passing the MSISDN of the caller to the Location Server. The Location Server must map the MSISDN to a routable location based upon th
27、e capabilities of the network. If the CMSP does not provide LBS, the Location Server must map the MSISDN to either a cell site address or a cell sector centroid. This location will be geodetic. If the CMSP provides LBS, it may use that location service to provide the location of the users device. Th
28、is location will be geodetic. When the CMSP is using commercial LBS, the relevant policy rules apply as to the availability of the users location. For example, if the user has privacy enabled, the Location Server may not be able to obtain location. If the CMSP is using LBS for its SMS/MMS text to 9-
29、1-1 service, it may be possible to obtain an updated location. This may be useful if the user is moving. The TCC must provide a capability for the PSAP to request a location update. When it does, the TCC must query the Location Server for location. If inter-TCC communication is invoked as described
30、in Clause 7.4, it is the responsibility of the TCC that connects to the SMSC/MMSC (i.e., the Originating TCC) to query the Location Server in the CMSP network. If the TCC that interconnects with the transitional PSAP or legacy or NENA i3 Emergency Services Network (i.e., the Terminating TCC) receive
31、s a location update request, it must forward that request to the Originating TCC; which then acquires the location. A NENA i3 PSAP dereferences a location URI at the target TCC, which may be the Originating TCC. 7.2 Routing Database When a PSAP or 9-1-1 Authority deploys SMS/MMS text to 9-1-1, they
32、must provide the CMSP (and the TCC service provider) with the coverage area that will be accepting SMS/MMS text to 9-1-1 messages. That process can be similar to (or the same as) the method used to provide wireless Phase II information. PSAP/emergency services network boundaries, in the form of poly
33、gons, are provisioned in the Routing Server (RS). Then, routing information (e.g., Route URI) is assigned to each polygon. Although J-STD-110 Ref 1 enables the RS to be queried with either civic or geodetic location, only a geodetic location will be used in the query from the TCC for the interim SMS
34、/MMS text to 9-1-1 solution. When the RS receives a routable location (either coarse or a more refined location) and a services urn (urn:service:sos), it correlates the location with one of the provisioned polygons and returns the Route URI associated with that polygon. That URI allows the TCC to de
35、termine the type of PSAP/emergency services network and to set up a dialogue with the target PSAP. If inter-TCC communication is invoked, the URI allows the originating TCC to determine the terminating TCC, and the URI retrieved in the terminating TCC will determine the type of PSAP/emergency servic
36、es network. If the RS cannot correlate the location with a provisioned polygon, it returns an error. This allows the TCC to generate a bounce-back message indicating service not available. If inter-TCC communication has been invoked, and the Terminating TCC receives an error indication from the RS i
37、t notifies the Originating TCC, which generates a bounce-back message. Specific error scenarios are discussed in Clause 7.10. J-STD-110.01.v002 9 7.3 High Availability Considerations To provide high availability, TCCs should be deployed in a 1:1 redundant manner in geographically diverse configurati
38、ons. This allows the mated TCCs to provide flexibility in implementation and offer effective failover and recovery during error conditions. The LS should be deployed using redundant servers, subject to operator policy. If so, each of the redundant TCCs must have connectivity to each LS. The RS shoul
39、d be deployed in redundant, geographically diverse configurations. Each TCC must have connectivity to each RS. Each TCC must have connectivity to the operator SMSCs and MMSCs. For example, SMSC to TCC connectivity may be via a Virtual Private Network (VPN) or other transport methods, or provided thr
40、ough an SMS aggregator. Each operator SMSC/MMSC should be able to deliver the SMS/MMS text messages to the redundant TCC. TCC service provider and emergency services provider operating policies dictate the connectivity between the TCC and the PSAP/emergency services network. Clauses 7.7, 7.8, and 7.
41、9 discuss functionality and connectivity for the various options. 7.4 TCC to TCC Interconnectivity Inter-TCC communication may be used when the TCC that interconnects with the SMSC/MMSC in the originating operator network (referred to as the “Originating TCC”) is not the same as the TCC that interco
42、nnects with a transitional PSAP or legacy or NENA i3 Emergency Services Network (referred to as the “Terminating TCC”). An Originating TCC uses information received from the SMSC/MMSC in incoming signaling (i.e., the MSISDN of the caller) to query a LS for location. The TCC then uses that location i
43、nformation to query the RS. If the routing information returned by the RS indicates that the text message needs to be sent to a different (i.e., Terminating) TCC, it establishes a session with the other TCC. The Terminating TCC uses location information provided by the Originating TCC to query its R
44、S to determine the next hop (i.e., the transitional PSAP or Emergency Services Network). If the location information provided by the Originating TCC is in the form of a Location by Value (LbyV), the Terminating TCC can use that location information to query its RS. If the location information provid
45、ed by the Originating TCC is in the form of a Location by Reference (LbyR), the Terminating TCC must first send a dereference request to the Deref IWF of the Originating TCC to obtain the location value before it can query its RS. Based on the routing information provided by its RS, the Terminating
46、TCC creates a dialogue with the transitional PSAP or Emergency Services Network. Note that TCC-to-TCC interconnectivity provides the flexibility to invoke those components of the TCC that are needed to support text communications between a given origination and destination point via the desired path
47、. The IWFs within a given TCC that actually get invoked for a specific SMS/MMS text to 9-1-1 text dialogue depends on where the text comes from, where it is going, and what connections and agreements exist to get it from its source to its destination. With respect to PSAP suspend and resume, when th
48、ere are Originating and Terminating TCCs, the Originating TCC service provider may not have a relationship with the PSAP. In this case, when the PSAP requests a suspension, it will inform the Terminating TCC service provider. The Terminating TCC service provider may have to inform the Originating TC
49、C service provider (e.g., if no alternate PSAP has been specified). The Originating TCC service provider may inform the CMSP. When the PSAP requests resumption, the Terminating TCC service provider may inform the Originating TCC service provider. The Originating TCC service provider may inform the CMSP. The following two scenarios apply for suspend and resume:8 The first scenario is where the PSAP has already specified an alternate PSAP to receive SMS/MMS text to 9-1-1 messages and is requesting suspension of service to the Terminating TCC service provider. When th
