CAPTION Interim Text to 9?1?1 Working Group Update October 12, 2012 Co?Chairs: Brian Daly, AT&T Gregg Vanderheiden, TRACE 1 CAPTION Interim Text to 9?1?1 Subcommittee • This group is charged with developing a recommendation and draft language for the full  committee with regard to Pre?NG9?1?1 Mobile Text to 9?1?1 Solution(s).  • March 2012 EAAC recommendation:   – EAAC Supports as an interim solution for text to 9?1?1, at a minimum, SMS, and other  technologies as appropriate, with a three digit short code 9?1?1 • Additional provisions from the EAAC recommendations that relate to the  subcommittee work: – Text to 911 before NG911 enabled – Recommendation T1.2: Interim Mobile Text Solution:  The EAAC recommends that the FCC work with Department of Justice, industry,  academia, consumer groups and public safety entities to develop an interim  solution that can be rapidly deployed to provide nationwide access to 9?1?1  services through industry standards?based mobile text communications solution(s)  to provide critical coverage for this important constituency during the transition to  NG9?1?1. 2 CAPTION Subcommittee Assumptions • Using any number besides 9?1?1 creates the problem that the user will probably  never remember it when they have an emergency, if they ever knew that there  was a number besides 9?1?1.  • This short?term solution should not necessarily be subject to all of the  requirements of either voice 9?1?1 calls or long?term solutions so that it can be  implemented in the near term and without extensively reworking the carrier,  handset, or PSAPs systems.  • The FCC should work with consumers and industry to secure any needed  additional liability protection for all entities that are implementing these new text  to 9?1?1 calls.  3 CAPTION Subcommittee Assumptions • The EAAC believes that if the text message to 9?1?1 solution is not available to all  people, with and without disabilities, that it would be too complicated for carriers  and others to qualify some people as eligible and others as ineligible to make an  SMS/text message call to 9?1?1 during emergency situations. The liability issues  from denying access to unregistered callers would complicate it further. • The EAAC directed for this subcommittee to take this topic up in 2012 and submit  a separate report on this important topic. • From a consumer standpoint, direct access via mobile text to 9?1?1 is a critical  goal. 4 CAPTION Transport Network High Level Architecture User  &  User  Device Originating  Network E9?1?1 PSAP NG?9?1?1 PSAP PSAP  Capability  Databases  C  Gateway Interim PSAP E   Gateway 5 CAPTION Interim Text to 9?1?1 Subgroups • Subcommittee created 4 subgroups – Each to focus on one section of the problem • Subgroups were defined as follows: – User View – Originating Devices – Originating Devices & Networks – Transport Networks – PSAP end 6 CAPTION Subcommittee Progress • Presented draft set of findings at the September EAAC  meeting • Several conference calls held since last meeting  • Developed outline for the report from the  subcommittee • First pass at identifying common ground across the four  subteam’s findings • Developed timeline to complete report 7 CAPTION DRAFT REPORT OUTLINE 8 CAPTION Draft Report Outline 1. EXEC SUMMARY  2. Overview  1. How it relates to long term  2. What the charge was  3. What it became and why  4. USE CASES ? summary and pointer to appendix 3. User Needs and Constraints 1. Text communication Method 2. Devices 3. User experience or the user's call flow 9 CAPTION Draft Report Outline 4. Origi9nating Devices and Networks 1. Though the 9?1?1 call may originate with the user in the "originating Network" ? users will  both originate calls, and receive callbacks from the PSAP. So users must be able to receive  emergency calls as well as make them. 2. Includes any conversions needed at border of originating networks where they meet  transport network(s) 5.     Transport Networks, including TCC  1. Includes any conversions needed at border of Transport networks where they  interface with PSAPs or PSAP networks.   6. PSAP end  1. Legacy PSAPS  2. NG 9?1?1 PSAPS  3. PSAP networks 10 CAPTION Draft Report Outline 7. Issues   1. Proprietary interim solutions – Proprietary  1. Opportunities, issues 2. Responsibilities and policy  1. Decision on who is responsible for what   1. to get this built  2. to maintain  3. to pay for 8. Actions needed to build this (what is not already in place)   1. Education and Outreach  2. Ensure that a 3 digit 911 SMS can be sent  3. Need some standards in place to make it work ? interoperate   4. PSAP request to receive services from participating entities 11 CAPTION Draft Report Outline 9.Conclusion  10. Recommendations  11. APPENDICES  1.USE CASES 12 CAPTION FIRST PASS AT IDENTIFYING  COMMON GROUND 13 CAPTION Common Ground Process • Based on the sub?team findings presented at  the September EAAC meeting, develop a  spreadsheet showing the areas identified in  the draft findings to identify common  – As well as areas of difference 14 CAPTION 15 Area Subteam 1 Subteam 2 Subteam 3 Subteam 4 Direct Access Users have DIRECT access to 9- 1-1 services. There are no third parties sitting in the path between callers and telecommunicators Order of short-term interim solutions Implement native SMS first, followed by over-the-top SMS, then native messenger applications, and real-time text Interim Text-to-911 must use the Existing Standards-based Network Architectures and Capabilities SHALL initially handle only SMS text originations but be standards-based and extendable to handle other text protocols The FCC should require Short Message Service (SMS) as the initial deployment priority for text to 9-1-1. Other forms of interim media and text for 9-1-1 services already in- place should be considered for national level support/delivery and worked in parallel to SMS Method of Contact Sending a text message using the three-digit code 9-1-1 network SHALL convey text messages directed to the short code “9-1-1” from a user’s terminals to the routing service which will select the geographically appropriate PSAP Should use digits 9-1-1 and not require a 9-1-1 voice call to be placed first CAPTION TIMELINE & NEXT STEPS FOR  SUBCOMMITTEE 16 CAPTION 17 Subcomittee 1 Activity Start Compl ete Responsible Notes 1. Complete the list of issues to be addressed 1. Brian completes list of issues 10/5Brian D 2. subleaders review and add issues and post to list 10/8 BD & Subleader  group 3. Full sub-committee reviews and finalizes as first draft of list of issues 10/9EAAC1 2. Review annotated report outline with full EAAC1 subcommittee 10/9EAAC1 1. Review draft slides for EAAC1 subcommitte presentation to full EAAC 10/9 GV&BD slides;  EAAC1 review Include schedule in  presentation 3. Present any results to date at the EAAC full committee 10/12GV&BD  4. Drafting team start on a draft 10/10 GV, BD, RH, CV,  KM,others? 5. Full sub-committee debates the issues and comes to consensus (in parallel with Drafting) 10/10 10/17EAAC1 Includes evaluation of options for proprietary solutions in place or near future 10/10 10/17EAAC1 6. Drafting committee brings draft to full subcommittee for discussion 10/17EAAC1 Include any rationale for  SC1 extension to plan  managed deployment CAPTION 18 7. Iteration of steps five and six 10/1710/31 Report draft finalized 11/5 8. Sub-committee submits report to the EAAC for review and comment 11/9EAAC1 1. Comments due back to subcommittee for discussion 11/26EAAC  9. Sub-committee resolves any comments 12/7EAAC1 1. EAAC1 prepares and approves final report 12/12EAAC1 12/13 Face to face prior  to EAAC? 10. Sub-committee submits report to full EAAC 12/12GV&BD 1. Address any comments from EAAC to the final report 1/9EAAC1 Prior to 1/11/2013 EAAC  meeting 11. Final report discussion at EAAC 1/11GV&BD CAPTION A Way Ahead • Interim Text to 9?1?1 Subcommittee will work to gain  consensus on each of the subgroup recommendations as it  prepares its final report and recommendations– Each subgroup will finalize draft conclusions and recommendations – Similar recommendations across subgroups will be consolidated into a  single overall recommendation • Final Interim Text to 9?1?1 Subcommittee Report &  Recommendations document to be presented in the  December EAAC meeting 19