SMS to Overview

Transcription

1 SMS to Overview Peter McHale, ENP Verizon Wireless HQ Operations Team Lead Last update: 2/28/14

2 SMS to Voluntary Agreement 2 December 6, 2012 Agreement between four major carriers, APCO and NENA April 2, 2013 J-STD-110 released NENA is currently in the final stages of completing and posting their SMS Text-to Information and Planning Guide June 30, 2013 National bounce back (Auto-Reply) May 15, 2014 General service availability

3 Why Offer an SMS Interim Solution? 3 SMS text-to Solution Benefits Deaf, Hard of Hearing and Speech Disability Communities as well as General Public Texting Standards and Service Capabilities Already Exist and Are Extensively In Use on Wireless Carrier s Networks Location Based Routing (LBS) Similar to Phase 1 Agreement Intent: Ensure Carrier SMS Architectures Would Not Be Modified At Least One Service Choice Would Provide Text Capability to PSAPs Without Additional Equipment or Software Cost to the PSAP Allow for Additional Training Related to SMS Text-to by NENA and APCO PSAP Training and Standard Operating Procedures for Handling Text are Consistent with Current Call Processing for TTY Calls Interim Solution in Preparation for NG-911

4 Customer Availability Availability? 4

5 Key Features of SMS Options Offered 5 SMS to PSAP via Web browser PSAP must have public internet connectivity from workstations PSAP workstations must have web browser capability (IE 8 or 9, Chrome or Firefox) PSAP is responsible for CPE equipment (upgrades/maintenance/technical support) SMS to TTY SMS converted to TTY before sent to public safety 911 network TTY messages sent to PSAP Selective Router PSAP should bid ALI with ESRK/P-ANI for location of the subscriber SMS to PSAP via Direct IP (Currently in development) PSAP installs dedicated and redundant IP circuits to SMS911 Gateway at own expense PSAP premise equipment must be capable of receiving IP messages PSAP Opt Out

6 SMS to Service Network 6 Wireless Carrier Service Provider-Hosted SMS911 Gateway PSAP PSAP Determination LoST Server Web GW GEM 911 PSAP Subscriber LBS SMSC SMS-911 Server Direct IP GW Converts To SS7/TDM Direct Circuit PSAP TTY GW SR Phase II ALI PSAP

7 7 Web Portal User Interface The MDN and the call taker s username are shown in each message next to the timestamp New Incoming Messages Active Sessions HUNC is Graphically Represented by the Size of the Circle Other Call Takers Sessions Drop-down with Canned Responses, or Free Type LAT/LON and HUNC Values Transfer PSAP: XYZ County Rebid Functionality

8 SMS via TTY 8 SMS-to-911 messages received on existing TTY interface Prepends SMS: to the 1 st message SMS messages delivered via wireless trunks Provides Lat/Lon, Call Back Number, pani Does not provide tower address Supports rebids for updated location No new equipment or upgrades needed.

9 Direct IP SMS911 SIP MSRP Options 9 Direct IP PSAP Requirements: - PSAP must support SIP MSRP ingress via either one of the following two methods: o o Connected to an ESInet with i3 SIP MSRP capability (preferred) CPE with full i3 (NENA) + SIP + MSRP + HELD capability - SIP MSRP stack must support TCP, UDP, IPv4. - PSAP/ESInet must have established IP connectivity with Service Provider s TCC. o o IP connectivity between TCS and PSAP/ESInet must be over MPLS/dedicated circuits. It is the PSAP s responsibility to establish the MPLS circuits. - Verify/Provide GIS boundary for PSAP

10 Web versus TTY Options SMS to PSAP via Web Browser Pros Modern interface Accessed via web portal Requires no additional CPE augmentation Uses existing workstations or separate workstations Provides more useful information than TTY Does not tie up a voice trunk(s) Cons Requires recent versions of web browser Currently one interface per WSP (developing) Security rules may require a separate workstation(s) for web 10

11 Web versus TTY Options SMS to TTY Pros Utilizes existing TTY infrastructure Converts SMS to TTY Text messages traverse call path via selective router Cons there is no background noise Requires dedicated voice trunk per dialog (texter) Additional ESRK range for ALI bid Half-duplex conversation TTY syntax (Q, GA, SK, SKSK) not recognized by non-tty users Some characters do not translate (i.e. #, etc.) 11

12 SMS TEST CASES PSAP is expect to administer and utilize Test Cases to completed deployment activity. 11 Test Cases Approximately 1 hour to complete test cases Sign off on test plan after testing is complete Carrier and Service Provider will assist with conference bridge and testing as required. Allows PSAP Personnel to gain familiarity with sending and receiving messages over platform 12

13 Deployment Process Express Interest via / Submit Formal RFS Carrier Responds with Questionnaire PSAP Returns Completed Questionnaire Carrier Schedules Kick Off Call Meet Participants- WSP, Service Provider, PSAP Review SMS Platform and Set Expectations Exchange Pertinent Information (IT, timeline, Q&A) Set Administrative Rights and Provide Training Turn SMS Platform Live Complete Test Cases Soft Launch Hard Launch 13

14 14 Phase I vs. Coarse Location Phase I vs. Commercial (e.g. SMS911) Location B A C B A C E911 Phase I Cell Sector assigned to fixed MSAG address. Each Cell Sector (e.g. A, B, C) can be assigned to specific PSAP s CLBS Coarse Location calculated by center point of the sector RF footprint Coarse Location address may not match the sector assigned PSAP for Voice e911

15 15 PSAP Boundary PSAP Boundary PSAP A PSAP PSAP A Boundary Area PSAP B Boundary Area Border sites have the potential to send SMS 911 to PSAP A and Voice 911 calls to PSAP B, even if the call is placed in the same location

16 Questions 16 QUESTIONS

17 SMS TEST CASES 17 Description SMS to from within PSAP Boundary SMS response from PSAP to Texter SMS response from PSAP using pre-populated messages Updated Location Request (rebid) during SMS session Multiple SMS to sessions simultaneously Expected Result SMS Test message received at PSAP SMS Response message received by tester Pre-populated SMS response received by tester PSAP receives updated location for tester Multiple SMS sessions are received and handled by separate consoles/responders SMS to from outside PSAP Boundary Texter receives Auto Bounce Back message SMS to with no users logged in Texter receives Auto Bounce Back message

18 SMS TEST CASES 18 Description SMS to for GEM Admin Policy Routing Functionality (PRF) Test Time of Day Settings Test Deny List Settings Test Alternate PSAP Settings Expected Result SMS Test messages are routed based current on PRF rules for the PSAP Messages are answered or received Bounce back message based on time of day Messages are answered or received Bounce back message based on Caller's number and deny list Messages are answered by the PSAP or routed to the Alternate PSAP based on Alt PSAP setting