OMA Messaging Workshop Brooklyn, New York July 12, 2012 Peter Musgrove AT&T

Transcription

1 Messaging and Emergency Services OMA Messaging Workshop Brooklyn, New York July 12, 2012 Peter Musgrove AT&T /2012 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property.

2 Outline NG911 (with focus on messaging) ATIS role in NG911 in the USA ATIS IMSESINET ATIS INES Key requirements for Interim Text Solution FCC EAAC ATIS/TIA Joint Project on SMS to 911 Sample requirements for SMS to 911 Challenges Architecture Proposal FCC CSRIC WG10 on 911 Prioritization 3GPP Multimedia Messaging Emergency Service (MMES) Transition Opportunity from SMS to 911 to MMES 2

3 Today s expectation AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property.

4 NG 911 Terminology (per NENA) National Emergency Number Association (NENA) Emergency Services IP Network (ESInet) A privately managed IP transport network that may be shared by multiple agencies NENA i3 Standard requirements, architecture and functions Including the Emergency Services Routing Proxy (ESRP) and the Emergency Call Routing Function (ECRF). NG9-1-1 The set of network elements, software applications, databases, CPE components, and operations & management procedures required to provide Next Generation emergency services. 8

5 NENA NG9-1-1 i3 Elements Inputs Pictures, Video, Graphics Outputs Gateway Call Routing Control PRF Policy Routing Function Gateway Location Info Border Control Subscriber Info /2012 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property.

6 3GPP Basis for NG911 3GPP IMS Emergency Sessions stage two specification Emergency services are independent from the IP-CAN with respect to the detection and routing of emergency sessions. The emergency services shall be possible over at least a cellular access network, a fixed broadband access, I-WLAN access and a nomadic access. Emergency sessions should be prioritized over non-emergency sessions by the system. Special indications for emergency sessions within the SIP signalling shall be supported. The case where the UE does not have sufficient credentials to authenticate with the IMS shall also be supported if required by local regulation. 6

7 Where is NG911 standardized in ATIS? Emergency Services Interconnection Forum (ESIF): specialists in emergency services; work closely with NENA and APCO Packet Technologies and Systems Committee (PTSC): keeper of ATIS NGN architecture Wireless Technologies and Systems Committee (WTSC): specialists in wireless; lead ATIS committee for ATIS Organizational Partner to 3GPP Next Generation Interconnection Interoperability Forum (NGIIF): operational procedures and testing among network operators 7

8 What is the ATIS IMSESINET Group? IMSESINET is an ATIS joint effort among WTSC (lead), PTSC, ESIF, and NGIIF. ATIS WTSC Issue P0030 ATIS Standard for Implementation of 3GPP Common IMS Emergency Procedures for IMS Origination and ESInet/Legacy Selective Router Termination. Uses 3GPP IMS Emergency Sessions as the basis for work, and applies to wireless and wireline accesses to common IMS. Considers North American specifics/requirements to define which options are chosen in 3GPP specs and to clarify use cases, call flows, etc. 8

9 Second IMSESINET project ATIS WTSC Issue P0034: Automating Location Acquisition for Emergency Services VoIP Calls. Identify technical methods by which an operator of a user access network can acquire and convey location for an Over-the-Top VoIP emergency call (push or pull methods). Example Over-the-Top providers are Vonage and Skype. Today: Customer manually enters their service address. Tomorrow: Automated Location Acquisition for wireless or wireline. Phase One handles voice only; Phase Two adds messaging 9

10 ATIS Interim Non-Voice Emergency Services (INES) Incubator ATIS INES Incubator report completed in late 2011 (free download on Analyzed multiple interim text to 911 solutions. Key criterion was possible implementation by June 30,

11 Interim Solutions Evaluated in ATIS INES Incubator Video American Sign Language (ASL) Video Relay Service IP Relay Service Instant Messaging Short Message Service (SMS) Direct to PSAP Voice Emergency Call, Then SMS National SMS Relay Center Real time Text (RTT) Direct to PSAP RTT with TTY Direct to PSAP RTT to Relay Center TTY Emulation Home PSAP Voice 911 Call, Then web-based non-voice communications Central All Text (CAT) /2012 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property.

12 Key Requirements for Interim Text Solution (Slide 1 of 2) 1. Recommended solution is targeted for deployment by June 30th Solution should have minimal impact to mobile phones, network equipment, network service providers, PSAPs, application service providers, and 3rd party providers. 3. No new hardware or device platform software requirements for mobile phones (including OS). 4. Text-based solution for emergency services targeted for the persons with disabilities (may or may not be usable by the general public). 5. A common solution which will be supported nationally. 6. Meets specified non-proprietary technical, interoperability, and performance standards. 7. Use commercially available Information Communications Technology (ICT) mobile terminals with no hardware or platform software changes. 12

13 Key requirements for Interim Text Solution (Slide 2 of 2) 8. Software solutions made through a downloadable application shall have no negative impact to handset embedded software. 9. Nominal end user cost for the feature. 10. This feature is not expected to work on non-service initialized phones. 11. Platform independent solution available on capable new or existing commercially available ICT. 12. Support availability of at least coarse end user location information to allow an emergency call to be routed. 13. Resolution of the following policy issues is required prior to the deployment of the interim solution: a. Removal of the TTY mandate for future ATIS INES solution (and ultimately MMES) enabled mobile phones. b. Coordinated education effort between all stakeholders including Public Safety, consumer groups, wireless industry and the FCC. c. Liability protection equivalent to current policies and extended as needed to support non-voice methods. d. Rules to permit non-voice methods acknowledgement of regulatory paradigm shift, differing from voice (e.g, location and reliability) /2012 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property.

14 Results of ATIS INES Incubator IP Relay was the chosen solution (already available today). National SMS Relay solution was a potential alternate solution but with longer time frame due to establishment of relay center. Long story short: Disability community does not favor IP relay and does not favor relay solutions for SMS. 2011/2012 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property.

15 FCC EAAC Emergency Access Advisory Committee (EAAC) Provided recommendations on NG911 to FCC in Dec., 2011 Continuing work on interim text to 911 solution in 2012 Disability community driving SMS to 911 as interim text to 911 solution. 15

16 New ATIS Project on SMS-to The FCC EAAC adopted resolution on March 30, 2012 to support an SMS-to solution ASAP and certainly ahead of the availability of 3GPP Multimedia Messaging Emergency Services (MMES) in next gen. Solution available to everyone (not just registered folks with disabilities). User dials 3 digit 911 short code as SMS destination address. No relay services (i.e., direct to PSAP). ATIS approved WTSC Issue P0037 as joint JSMS911 project among ATIS WTSC (lead), ATIS ESIF, and TIA TR45.8 (cdma2000). 16

17 Sample Requirements for SMS to 911 Non-service initialized mobile devices are not supported. SMS to 911 should be available on existing and new SMS-capable mobile devices which have a valid two-way text messaging subscription at the time of the initiation of SMS to 911 text message and which can support the 911 short code. SMS to 911 must be capable of supporting delivery of the message content to both legacy and next generation PSAPs in a text format that is specified by the PSAP. The wireless operator is not responsible for the translation of the SMS message to the format specified by the receiving PSAP (since there are over 6,000 PSAPs). Support of SMS to 911 for international roamers to the United States is not required. SMS to 911 is not supported for US subscribers roaming outside of the US. Coarse location information (e.g., cell site location) is available for the determination of appropriate PSAP for routing of the text message content. E911 Phase 1 and Phase 2 location accuracy requirements are not applicable to SMS to 911. In order to get location for dispatch by the PSAP, additional location information may need to be provided by or confirmed by the subscriber in the SMS message exchange with the PSAP text taker. Location Based Services (LBS) may provide supplemental location information if LBS capabilities are supported by the wireless network operator, the subscriber s subscription, the mobile device settings, and/or by the subscriber s mobile device capabilities /2012 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property.

18 Additional Sample Requirements for SMS to 911 SMS to 911 is not required to be recognized as an emergency call or an emergency communication by the mobile device. Within the mobile device, any special processing and service restrictions associated with voice emergency calls may not be applicable to SMS to 911. An association between the subscriber which initiated the SMS to 911 and the PSAP text taker must be maintained so that multiple SMS messages in the same dialogue are delivered between the same PSAP text taker and subscriber. If the subscriber initiates a voice to 911 call while a SMS to 911 communication is in progress, there is no requirement to route the voice to the same PSAP call taker that is handling the SMS messages. For SMS message content from the responding PSAP to the subscriber, the From address in the SMS message should be the three digits 911 to indicate to the subscriber that this is an inbound SMS message from the responding PSAP. Non-CMRS-originated SMS, such as portal-based SMS messaging, is not supported. MMS to 911 is for further study, as sometimes including multiple recipients in an SMS message results in an MMS message /2012 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property.

19 Technical Challenges of SMS to 911 Assumptions: Consumers will expect SMS to 911 to work everywhere Consumers will expect all SMS-like clients, including third party messaging applications, to work for 911 Only native SMS will be supported. SMS look-alike applications and over-the-top messaging clients (including thirdparty applications) will not be supported by ATIS effort Many PSAPs will not be ready to receive SMS messages directly for some time PSAPs will not flash cut to support SMS to 911 nationwide overnight if ever If a vendor-specific solution is envisioned, it will be a hard to get all PSAPs (or carriers) to support the same vendor specific solution Carriers and third party applications need somewhere to route the 911 SMS message, and know what format to use to deliver the text Direct SMS? Web access? TTY? Something else? Challenge will be to figure out which PSAPs support what capability at any given point in time SMS to 911 has to work end to end from the mobile device to the PSAP This is mostly an issue on the PSAP side SMS cannot be redesigned it will work as a best effort store and forward service as it was designed 19

20 AT&T Proposal: SMS to 911 Router(s) & Gateway(s) One approach and possibly the cleanest option is Nationwide SMS to Router*(s) & Gateway(s) Similar to CMAS, there is a need for SMS to 911 Router(s) and Gateway(s) to receive, process, and route all SMS to 911 text messages in this dynamic environment Supports the consumers expectation for SMS to everywhere Supports PSAPs in their evolution to supporting SMS and NG911 Supports PSAPs choice in vendor solutions National 911 SMS Gateway(s) will provide a single entry point for SMS to messages from both the carrier s native SMS and can support third party SMSlike messaging applications National 911 SMS Gateway(s) will know how to route the SMS to the Public Safety SMS to 911 Gateway based on where the subscriber is located Public Safety SMS to 911 Gateway determines routing to the appropriate PSAP based on the subscribers location information and provides protocol conversion to a format that is supported by the PSAP in the consumer s area, such as TTY Provides a natural and seamless migration path for PSAPs as they convert from legacy to NG911. PSAP Capability Database Carrier s Native SMS Destination Gateway Database Third Party SMS-like Application Standards-based interfaces Standards-based interfaces Interface per PSAP Preference National 911 SMS Router(s) PSAP SMS to 911 Gateway(s) 20 Non-text Capable PSAP Text Capable PSAP

21 FCC CSRIC Working Group 10 Description: The working group shall explore ways to ensure that 911 is available when emergencies or disasters cause a surge in mobile network use. The work will include considerations of how 911 traffic might be prioritized in such situations. It also includes related operational issues, including ways for PSAPs to address operational issues. The WG may consider ways to reduce traffic load during emergencies, such as encouragement of use of 911 text as a lower throughput alternative to 911 voice. If the WG pursues arrangements that give 911 calls higher priority than most consumer wireless calls, the WG may consider how to coordinate 911 priority with other priority calling arrangements, including Wireless Priority Service (WPS), and other arrangements that may provide priority for calls for emergency and first responders. The WG will address implementations in 4G and earlier generation wireless networks; and will consider both E911 and NG911 implementations. Duration: March 6, 2013 CSRIC = Communications Security Reliability and Interoperability 21 Council

22 Problem with Prioritizing 911 Calls Problem with providing any priority for 911 calls is that major bottlenecks exist at Selective Router and at PSAP itself. Vast majority of PSAPs in USA have only 2-6 call takers. What good does it do to have hundreds or thousands of prioritized 911 calls converging on a typical PSAP during crisis? 22

23 Opportunities for NG Priority Messaging SMS originally designed in Europe in early 1990s. SMS has no priority mechanisms today. 3GPP Multimedia Messaging Emergency Services (MMES) working next gen messaging for use by public to reach emergency services. Such messaging may be given priority (e.g., SIP Invite with sos:urn). Messaging protocols for next gen should be enhanced to allow for priority capabilities for emergency services messaging and for 3GPP Multimedia Priority Service (MPS) users (e.g., government priority services users). 23

24 3GPP Multimedia Emergency Services (MMES) Messaging component first introduced as Non-Voice Emergency Services (NOVES) in 3GPP SA1 (see study report in TR ). 3GPP TS Section 10 contains SA1 requirements added for IMS Multimedia Emergency Sessions (MES). Includes long-term vision of messaging for Next Gen emergency services. First version completed in 3GPP Release /2012 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property.

25 3GPP MMES Issues to be Resolved Real-Time Text (RTT) for real-time (character-ata-time) service. SIP Message for message-at-a-time (IM) service. Message Session Relay Protocol (MSRP) or Extensible Messaging and Presence Protocol (XMPP) to assist with session management for MMES?? There is a need for the industry to standardize as quickly as possible the media formats and protocols on which an MMES texting service will be based /2012 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property.

26 Transition Opportunity from SMS to 911 to MMES Ideally, the protocol choices for MMES (e.g., SIP Message, RTT, MSRP, XMPP) could be decided quickly to be able to be used in network supporting SMSto-911 (e.g, between routers and gateways). This would allow operators to make steps toward NG911 messaging even in an implementation supporting SMS-to /2012 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property.

27 27