Text-to-9-1-1

Report
The Process Explained
TECHNICAL PANEL INTRODUCTIONS
Wireless Providers
Jeanna Green, Sprint
Text Control Centers
Jason Ramsey, Intrado
Doug Kesser, TCS
SPRINT TEXT-TO-911 OVERVIEW
PA NENA
Jeanna Green
Voice Services Development: 9-1-1
September 2014
Milestones: Text-to-911
 December 6, 2012 - Tier 1 Carriers signed a voluntary commitment letter to the
FCC to make available on their networks Text-to-911 service via SMS by May 15,
2014. Commitment included:
 June 30,2013 – provide a “bounce-back message” indicating that text-to911 service is not available.
•
If a handset is capable of dialing the short code 9-1-1; a Sprint
consumer is receiving the following message from the network:
“For emergency only, CALL 9-1-1. Text-to-911 not
available.”
©2014 Sprint. This information is subject to Sprint policies regarding use and is the property of Sprint and/or its relevant affiliates and may contain restricted,
confidential or privileged materials intended for the sole use of the intended recipient. Any review, use, distribution or disclosure is prohibited without authorization.
4
Milestones: Text-to-911
 Sprint provided quarterly reports summarizing the status of the
deployment of national Text-to-911 service capability to :
 Federal Communications Commission (FCC),
 National Emergency Numbering Association (NENA)
 Association of Public-Safety Communications Officials
(APCO).
 Sprint completed TCC vendor evaluations April 2013
 May 17, 2013 - FCC released Text-to-911 Bounce-back Order
 Requires all wireless carriers and interconnected text providers to
provide a message by September 30, 2013.
 Does not require other carriers to provide Text-to-911 service by a
specified date.
 Holds Tier 1 carriers to original commitments made in the
December 2012 letter.
©2014 Sprint. This information is subject to Sprint policies regarding use and is the property of Sprint and/or its relevant affiliates and may contain restricted,
confidential or privileged materials intended for the sole use of the intended recipient. Any review, use, distribution or disclosure is prohibited without authorization.
5
Milestones: Text-to-911
 Sprint migrated to providing the Bounce-back message from the Sprint SMS
network nationally, on May 31, 2013.
 Completed LAB certification for April 11, 2014

Signed agreement with TCC Vendor, Intrado, April 21, 2014.
 Completed Field Integration Testing (FIT) for ATIS/TIA J-STD 110 routing
scenarios:




HTTPs – 4/23/2014 & 4/24/2014
 Durham, NC & State of Vermont
NENA i3 – 5/07/2014
 State of Indiana (Indigital)
TCC to TCC – 05/08/2014
 (Intrado/TCS) York County, VA
TTY – 05/09/2014 & 05/14/2014
 Cabarrus, NC 5/09/2014
 State of Maine 05/14/2014
 Sprint Network Ready Declaration (NRD): May 9, 2014
 Sprint Production Ready May 15, 2014.
©2014 Sprint. This information is subject to Sprint policies regarding use and is the property of Sprint and/or its relevant affiliates and may contain restricted,
confidential or privileged materials intended for the sole use of the intended recipient. Any review, use, distribution or disclosure is prohibited without authorization.
6
ATIS/TIA J-STD #110
Text-to-911 Routing Options
©2014 Sprint. This information is subject to Sprint policies regarding use and is the property of Sprint and/or its relevant affiliates and may contain restricted,
confidential or privileged materials intended for the sole use of the intended recipient. Any review, use, distribution or disclosure is prohibited without authorization.
7
SMS to 911 Delivery Options
High-level Routing Solutions from Text Control Center (TCC) to PSAP
PSAP should understand the roles and responsibilities associated with each of the four
options for SMS-to-911 Text Control Center (“TCC”) interconnectivity.
There are four options for interconnectivity with SMS911 Gateway Service Offering:
1. HTTPS - SMS using the web browser




PSAP must have public internet connectivity into workstations readily available
PSAP workstations must have web browser capability (Internet Explorer 8, Chrome or Firefox)
PSAP is responsible for CPE equipment (upgrades/maintenance/technical support)
PSAP must provide point of contact for CPE customer support
2. TTY - utilizing existing PSAP TTY connectivity from TCC.




SMS converted to TTY before being sent to the public safety 911 network
TTY messages sent via PSAP Selective Router trunk to the PSAPs selected TTY equipment
PSAP is responsible for CPE equipment (upgrades/maintenance/technical support)
PSAP must provide point of contact for CPE customer support
3. NENA i3 - Direct integration with CPE equipment via ESINET
•
Work directly with ESInet provider and CPE equipment vendors
4. PSAP SMS Opt Out
 Chooses not to request service
©2014 Sprint. This information is subject to Sprint policies regarding use and is the property of Sprint and/or its relevant affiliates and may contain restricted,
confidential or privileged materials intended for the sole use of the intended recipient. Any review, use, distribution or disclosure is prohibited without authorization.
ATIS Standards #110 - SMS-9-1-1 Routing
Options
There are four options for interconnectivity with SMS911:
•
•
•
•
MSC
Subscriber
Radio
Tower
HTTPs - web browser
TTY – using existing PSAP TTY connectivity
NENA i3
PSAP SMS Opt Out
SMSC
Location
Services
SMPP
MLP
TTY over existing trunking
Sprint
PSAP with TTY
Selective
Router
HTTPs – TCC to TCC
ToIP GW
HTTPS
HTTPs – Intrado
integrated
GIS DB
SMS E9-1-1
CallServer
Provisioning
HTTPs – Intrado nonintegrated
SIP SIMPLE
ESRP
Report
Portal
PSAP API
Backend
SIP PIDF-LO
ESINet
©2014 Sprint. This information is subject to Sprint policies regarding use and is the property of Sprint and/or its relevant affiliates and may contain restricted,
confidential or privileged materials intended for the sole use of the intended recipient. Any review, use, distribution or disclosure is prohibited without authorization.
NENA i3 - PSAP
connected via ESINet
PSAPs
ATIS/TIAText-to-911
J-STD #110
PSAPs ‘Live” in Sprint
Network
©2014 Sprint. This information is subject to Sprint policies regarding use and is the property of Sprint and/or its relevant affiliates and may contain restricted,
confidential or privileged materials intended for the sole use of the intended recipient. Any review, use, distribution or disclosure is prohibited without authorization.
10
PSAPs Request for Service
(RFS)
• Sprint request totaling 539 PSAPs as of Friday 9/05/2015:
 208 - Deployed
 361- Readiness Verification & testing pending
 254 - Pending PSAP Readiness
 57 - Scheduled/Pending Scheduling
 9 - On Hold per PSAP request
 1 - No Sprint Service
• Intrado, Sprint’s Text Control Center Vendor is currently working
with PSAP to verify PSAP readiness for pending requests
©2014 Sprint. This information is subject to Sprint policies regarding use and is the property of Sprint and/or its relevant affiliates and may contain restricted,
confidential or privileged materials intended for the sole use of the intended recipient. Any review, use, distribution or disclosure is prohibited without authorization.
11
PSAPs Request for Service
(RFS)
Sprint appreciates your interest in our commitment to provide Text-to-911.
The Text Control Center (TCC) Vendor Sprint is utilizing for Text-to-911 is Intrado.
Please provide your formal request for Text-to-911 directly to Intrado @ either
address below:
email: [email protected]
or USPS:
INTRADO
Attn: Sprint Text-to-911
C/O: Dan Neu
INTRADO
1601 Dry Creek Dr
LONGMONT CO 80503
Upon receipt, Intrado will reach out to you to begin discussion on your chosen routing
solution and readiness. Based on the carrier commitment to the FCC carriers have 6
months to implement once a PSAP is ready and able to received messaging.
©2014 Sprint. This information is subject to Sprint policies regarding use and is the property of Sprint and/or its relevant affiliates and may contain restricted,
confidential or privileged materials intended for the sole use of the intended recipient. Any review, use, distribution or disclosure is prohibited without authorization.
12
PA PSAPs “LIVE” Text-to-911
State County
Authority/Jurisdi
ction
FCC id PSAPs Accepting Texts
PA
Dauphin county
Dauphin county
PA
Lancaster County Lancaster County 5900
Dauphin County Emergency
Management Agency
Lancaster County-Wide
Communications
PA
Lehigh County
PA
STATUS
TTY
05/22/2014
05/22/2014 06/16/2014 LIVE
WEB
05/27/2014
05/27/2014 07/09/2014 LIVE
Allentown 9-1-1
WEB
05/29/2014
05/29/2014 07/14/2014 LIVE
Allegheny County Allegheny County 5849
Allegheny County 9-1-1
WEB
02/13/2014
05/16/2014 07/15/2014 LIVE
PA
Lackawanna
County
Lackawanna
County
5899
Lackawanna County Department of
Emergency Services
Power 9-1-1 06/25/2014
06/25/2014 07/31/2014 LIVE
PA
Elk County
Elk County
5885
TTY
PA
Berks County
Berks County
5854
PA
Chester County
Montgomery
County
Chester County
Montgomery
County
5867
Bucks County
Northampton
County
Bucks County
Northampton
County
5859
Berks County 9-1-1
Chester County Department of
Emergency Services
Montgomery County Emergency
Dispatch Services
Bucks County Emergency
Communications
5914
Northampton County 9-1-1 Center
07/18/2014 08/25/2014 LIVE
Pending PSAP
07/07/2014
Readiness
Pending PSAP
07/07/2014
Readiness
Pending PSAP
07/07/2014
Readiness
Pending PSAP
07/07/2014
Readiness
Pending PSAP
08/06/2014
Readiness
Lehigh County
5880
TEXT to 911
Routing
Date RFS Deployed
Solution
Inquiry Date Received Date
5850
Elk County Communications
PA
PA
PA
5912
07/18/2014
06/01/2014
Power 9-1-1 06/01/2014
06/01/2014
06/01/2014
08/06/2014
“For emergency only, CALL 9-1-1. Text-to-911 not available.”
©2014 Sprint. This information is subject to Sprint policies regarding use and is the property of Sprint and/or its relevant affiliates and may contain restricted,
confidential or privileged materials intended for the sole use of the intended recipient. Any review, use, distribution or disclosure is prohibited without authorization.
13
PA PSAPs Text-to-911 Stats
State
PA
PA
PA
PA
PA
County
Dauphin
Lancaster
Lehigh
Allegheny
Lackawanna
PA
Elk
PA
PA
PA
Berks
Bucks
Chester
PSAPs Accepting Texts
Dauphin County Emergency Management Agency
Lancaster County-Wide Communications
Allentown 9-1-1
Allegheny County 9-1-1
Lackawanna County Department of Emergency Services
Elk County Communications
Berks County 9-1-1
Bucks County Emergency Communications
Chester County Department of Emergency Services
Total
Conversations
20
6
11
24
4
Total
Messages
113
41
70
214
21
Count of
Successful
Conversations
18
5
9
24
4
Count of
Bounceback
2
1
2
0
0
TEXT to 911
Routing
Solution
TTY
WEB
WEB
WEB
Power 9-1-1
Deployed Date
06/16/2014
07/09/2014
07/14/2014
07/15/2014
07/31/2014
STATUS
LIVE
LIVE
LIVE
LIVE
LIVE
26
166
19
7
TTY
08/25/2014
LIVE
17
17
3
34
37
6
17
Pending PSAP
Readiness
Pending Connectivity to Power 91-1, Wants Montgomery to go
first.
17
Pending PSAP
Readiness
Pending Connectivity to Power 91-1, Wants Montgomery to go
first.
3
Pending PSAP
Readiness
Pending Connectivity to Power 91-1, Wants Montgomery to go
first.
Pending PSAP
Readiness
Pending PSAP
Readiness
Pending Connectivity to Power 91-1, Wants Montgomery to go
first.
Pending return of survey and
questionnaire
PA
Montgomery
Montgomery County Emergency Communications
20
41
20
PA
PA
PA
PA
PA
PA
PA
PA
PA
PA
PA
PA
PA
PA
PA
PA
PA
PA
Northampton
Northampton
Beaver
Blair
Cambria
Clarion
Columbia
Delaware
Erie
Fayette
Lawrence
Lehigh
Luzerne
Mercer
Monroe
Philadelphia
Westmoreland
York
Northampton County 9-1-1 Center
Bethlehem Police Department
Beaver County Emergency Services Center
Blair County 9-1-1
Cambria County Department of Emergency Services
Clarion County Office of Emergency Services
Columbia County Department of Public Safety
Delaware County Emergency Communications Center
Erie County 9-1-1 Center
Fayette County Emergency Management Agency
Lawrence County 9-1-1 Center
Lehigh County Communications Center
Luzerne County 9-1-1
Mercer County Department of Public Safety
Monroe County Control Center
City of Philadelphia
Westmoreland County Department of Public Safety
York County 9-1-1
0
2
2
1
1
1
1
9
7
5
2
3
1
1
2
127
2
4
0
4
4
2
2
2
2
19
15
10
4
6
3
2
4
255
5
8
0
2
2
1
1
1
1
9
7
5
2
3
1
1
2
127
2
4
319
1090
Totals
79
Notes
Power 9-1-1
Power 9-1-1
240
©2014 Sprint. This information is subject to Sprint policies regarding use and is the property of Sprint and/or its relevant affiliates and may contain restricted,
confidential or privileged materials intended for the sole use of the intended recipient. Any review, use, distribution or disclosure is prohibited without authorization.
14
SMS Key Points Points
©2014 Sprint. This information is subject to Sprint policies regarding use and is the property of Sprint and/or its relevant affiliates and may contain restricted,
confidential or privileged materials intended for the sole use of the intended recipient. Any review, use, distribution or disclosure is prohibited without authorization.
15
SMS Key Points
 SMS is a store-and-forward messaging technology that was never designed nor
deployed to provide any time-sensitive, mission-critical service.
 It is being offered as an interim “best-efforts service” to meet the near term
objective of providing a text-based emergency communications until the
comprehensive NG9-1-1 system (e.g. ESINet) is developed, deployed and adopted
by the wireless industry, public safety community and public.
 Although the national carriers are to have their networks production ready to
provide Text-to-911 service by May 15, 2014, a valid PSAP requests for Text-to-91-1 service will still need to be requested by PSAP to implemented.
 Implementation will be conducted within a reasonable amount of time of
receiving such request, not to exceed six months.
©2014 Sprint. This information is subject to Sprint policies regarding use and is the property of Sprint and/or its relevant affiliates and may contain restricted,
confidential or privileged materials intended for the sole use of the intended recipient. Any review, use, distribution or disclosure is prohibited without authorization.
SMS Key Points cont.
 A request for service will be considered valid if, at the time the request is made:
a) the requesting PSAP represents that it is technically ready to receive 9-1-1
text messages in the format requested; and
b) the appropriate local or State 9-1-1 service governing authority has
specifically authorized the PSAP to accept and, by extension, the signatory
service provider to provide, text-to-9-1-1 service (and such authorization is not
subject to dispute).
 Consistent with the ATIS Standard for Interim Text-to-9-1-1 service, the PSAPs will
select the format for how messages are to be delivered. Incremental costs for
delivery of text messages (e.g. additional trunk groups to the PSAP’s premises
required to support TTY delivery) will be the responsibility of the PSAP, as
determined by individual analysis.
©2014 Sprint. This information is subject to Sprint policies regarding use and is the property of Sprint and/or its relevant affiliates and may contain restricted,
confidential or privileged materials intended for the sole use of the intended recipient. Any review, use, distribution or disclosure is prohibited without authorization.
SMS Key Points cont.
The signatory service providers will implement a ‘9-1-1’ short code that can be used by
customers to send text messages to 9-1-1.
The signatory service providers (whether individually or through a third party) will work
with APCO, NENA, and the FCC to develop an outreach effort to set and manage consumer
expectations regarding the availability/limitations of the Text-to-9-1-1 service (including
when roaming) and the benefits of using voice calls to 9-1-1 whenever possible, and
support APCO and NENA’s effort to educate PSAPs on Text-to-9-1-1 generally.
A voluntary SMS-to-9-1-1 solution will be limited to the capabilities of the existing SMS
service offered by a participating wireless service provider on the home wireless network
to which a wireless subscriber originates an SMS message.
SMS-to-9-1-1 will not be available to wireless subscribers roaming outside of their home
wireless network.
Each implementation of SMS-to-9-1-1 will be unique to the capabilities of each signatory
service provider or it’s Text Control Center (TCC) provider.
©2014 Sprint. This information is subject to Sprint policies regarding use and is the property of Sprint and/or its relevant affiliates and may contain restricted,
confidential or privileged materials intended for the sole use of the intended recipient. Any review, use, distribution or disclosure is prohibited without authorization.
Texting to 9-1-1
Jason Ramsay, Sales Engineer
Company Confidential
Copyright Intrado Inc. 2014– All rights reserved
Intrado TXT29-1-1® Carrier Aggregation
Intrado NextGen PSAP
(i3 Integrated Voice / Text)
Carrier A
Intrado
TCC
Text
Intrado
Proxy
I3 Text
Gateway
Gateway
(ESRP)
(i3 ESRP)
i3
TCC
Carrier B
i3
WEB
Intrado Transitional PSAP
(WEB Text)
TTY
J-STD-110 Inter-TCC
Interface
Text
Intrado
Proxy
I3
Gateway
WEB
(ESRP)
Gateway
Public Internet
or
Private IP Network
Legacy TTY PSAP
S/R
Existing 9-1-1 Voice Circuit
Other Vendor
TCCs
Carrier C
Other Solutions
TTY
SMPP / MLP
TCC
HTTP
Public Internet
WEB
i3
TTY
Gateway
Copyright Intrado, Inc. 2014 – All rights reserved
PSAP Interfaces
Integrated (CPE and/or CAD)
•
•
•
•
•
•
•
•
•
Ultimate NextGen 9-1-1 i3 Solution
Simple PSAP training / low transition effort
Integrated work flow with voice calls
Integrated reports and record management
Dedicated, Secure NextGen Network
Does not impact voice trunk capacity
i3 interface
Currently supports Intrado Viper / power 9-1-1
Back-up/Failover
• Transfer
• Private chat
• Location update
Copyright Intrado, Inc. 2014 – All rights reserved
Intrado Web Viewer
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
i3 Implementation vs. carrier-based TCC
All carriers supported, not exclusive
Allows rapid implementation
No cost to PSAP with internet option
Supports multiple carriers
i3 interface will allow i3 transfer capability
Built in transcripts
High security / 2 factor authentication
Back-up/Failover
Location update
Bread crumb
Private chat
I3 interface supports public internet and ESInet
connectivity
Transitional approach
Separate reports for voice and text
New screen for text calls
New training
Copyright Intrado, Inc. 2014 – All rights
reserved
SMS Delivery Over TTY
•
•
•
•
•
•
Developed in early 1960’s
Does not require any technical change at PSAP
Competes with voice traffic
Limited character sets
Very slow
Error handling issues
•
•
•
•
•
•
•
Message-based to character- based conversion
Half duplex
Message collision
Lost shift character – garbled text
Unknown message integrity
SMS users do not understand TTY issues
Requires PSAP training
TXT29-1-1® How To Get Started
Choose initial technology
1. Integrated with CPE
2. I3-based web
3. SMS-to-TTY
PSAP data collection form:
http://www.intrado.com/webform/txt29-1-1-psap-profile-questionnaire
Copyright Intrado, Inc. 2014 – All rights reserved
Requesting Wireless Carrier Service
Request service from Wireless Carriers
Sample Template-
Copyright Intrado, Inc. 2014 – All rights reserved
SMS9-1-1
PA NENA Conference – State College
September 12, 2014
Current Regulatory Environment
•
December 2012: Tier 1-NENA-APCO Voluntary Agreement
o Tier 1 General Availability per Carrier Agreement out by May 15, 2014
•
FCC NPRM – Notice of Proposed Rule Making
o All Carriers to Support Bounce Back Messages as of September 2013
•
FCC FNPRM – Further NPRM
o Identified Anticipated Issues with Text to 911
o Targets December 31, 2014 for All Carriers to Support Text to 911
•
FCC Report and Order and Third FNPRM
o FCC Ruled on August 8, 2014




All “Covered Text Providers” MUST Make SMS911 Available by End of Year
MUST Provide Service within a 6 Month Period of Request (Must have Service Up
and Running by June 30, 2015)
All Interconnected OTT Providers MUST Support SMS911
Creation of a PSAP to indicate their Readiness and Desire to Receive Service
o FNPRM Continues to Drive Position on Ongoing Challenges
o Enhanced Location
o Roaming
o Future Text-to-911 Services
30
30
NENA SMS911 Resource Page
» NENA General Information Page:
https://www.nena.org/?page=textr
esources



Carrier Contacts
Carrier Questionnaire
Request for Service (RFS) Letter
• TCS Can Provide



Implementation and Testing Information
Training
ETC.
If You Have a Preference of TCC Vendor, Please Note it on
Your RFS Letter to the Carriers
31
FCC Deployment Tracker
TCS provides text-to-911 to > 85% of all PSAPs in the US……
http://transition.fcc.gov/cgb/text-to-911-deployments.pdf
32
TCS Deployment Update
• 154 PSAPs
•
•
•
•
•
•
•
•
GEM = 64
TTY = 15
Direct SIP MSRP = 59
TCC Hand Off = 16
21 States
More than 100 Deployments in Progress
More than 300 PSAPs in Queue
First Fully Compliant (ATIS/NENA/i3) TCC-to-ESInet (Indiana) and
TCC-to-TCC (Vermont) Integration via MSRP
• Approximately 15,000,000 US Citizens within Serving Area of at
Least One Wireless Carrier Supporting SMS911
Current SMS 9-1-1 Statistics
59,998 public
attempts to text
911 from
1/01/2014 to
7/31/2014
Public demand is
there, but its not
overwhelming
Reference: TCS national 911 report
Chairman Genachowski (10/10/11) stated
“It’s hard to imagine that airlines can send text messages if your flight is delayed, but you can’t send a text message
to 9-1-1 in an emergency. The unfortunate truth is that the capability of our emergency response communications has
not kept pace with commercial innovation – has not kept pace with what ordinary people now do every day with
communications devices. The shift to NG9-1-1 can’t be about if, but about when and how.”
34
Pennsylvania SMS 9-1-1 Attempts (VzW + T Mobile)
Total: 2,259
500
450
400
350
300
250
200
150
100
50
0
Jan
Feb
Mar
Apr
May
Jun
Jul
35
Where is it Currently Deployed in PA?
Of Deployed, Lancaster and Allentown = GEM, all others TTY
Allentown City
Intrado
Web
All Tier 1s - Deployed
VZW Only - Deployed
VZW+TMO - Pending
TMO Only - Pending
All, but No AT&T - Deployed
Current TCS Architecture Overview
Options for interconnectivity with SMS911
Gateway Service Offering:
MSC
» SMS using the TCS GEM 9-1-1 client
(web browser)
» SMS to TTY Conversion
» Direct integration with CPE equipment (NENA i3)
» PSAP SMS Opt Out
Radio
Tower
Subscriber
SMSC
Location MLP
Services
SMPP
TTY over existing trunking
Carrier
PSAP with TTY
Selective
Router
ToIP GW
PSAP with CPE, Web, TTY
MSRP
“Other” TCC
HTTPS
GIS DB
SMS E9-1-1
CallServer
Provisioning
Report
Portal
MSRP
PSAP API
Backend
TCS Text Control Center
ESRP
ESInet
PSAP with GEM 9-1-1 Web
Portal
PSAP connected via ESInet
PSAPs
TCS GEM911 User Interface
Frequently Asked Questions
» What is text-to-911?

Per FCC Ruling: In general, “text messaging” refers to any
service that allows a mobile device to send information
consisting of text to other mobile devices by using domestic
telephone numbers. Examples of text messaging include
Short Message Service (SMS), Multimedia Messaging Service
(MMS), and two-way interconnected text applications.
» Are PSAPs required to support text-to-911?

No. The FCC regulates carriers, not Public Safety.
» Once I request the service, how long before I receive
it?

Per FCC, the Carriers MUST provide within 6 months of the
request.
» What delivery options are available for me to receive
text-to-911?

There are three standards defined delivery options: TTY,
Secure Web Portal, and NENA i3 SIP/MSRP
39
FAQs Continued
» Does text-to-911 include picture and video
delivery?

No. The FCC does not require the carriers to deliver
multimedia.
» Can non-service initiated devices send a text
to 911?

No. The user’s device must be initiated and have an
active texting plan.
» Will we receive Phase 1 and Phase 2
location with text-to-911?

No. Text-to-911 uses a different location platform,
which provides a course and enhanced location.
» Will text-to-911 work with my existing CPE?

Yes, it is possible to have text-to-911 to work with your
existing CPE.
40
41
Other Helpful Technical Points
Important for PSAPs considering text – their equipment
- Is the CPE ready for an integrated i3 solution?
- Is the TCC provider they are considering passing i3 integrated data?
Costs
- Costs for software version upgrade to i3 integrated solution
- Perhaps start with web based solution until the budgeting cycle allows
Additional equipment
– Verify with CPE provider
Other Helpful Technical Points
J-Std-110(a)
TCC to TCC communications
Three J-Std-110
- i3 integrated solution
- Web
- TTY
CPE provider must authorize use of web browser for
secure connection to the TCC.
Other Helpful Technical Points
TTY
- Dedicated CAMA trunks installed to their CPE for text may need to
be a consideration.
- TTY (text) calls significantly longer in length.
i3 compliance – protocol for SIP / HELD (HTTP-Enabled Location
Delivery Protocol) are being recognized
HELD - A protocol defined by the IETF to deliver location using
HTTP transport
Over-The-Top/Apps
Technical Panel Q&A
Session Break
Panel Switch
OPERATIONAL PANEL INTRODUCTIONS
Gary Thomas, Allegheny County
Michael Hilbert, City of Allentown
Tim Baldwin, Lancaster County
John Haynes, Chester County
Project Overview
Revised: 15-Aug-14
Process
 Evaluated the Reasons for Text to 9-1-1 in Allentown
 Excellent Research Sources >> NENA, APCO, FCC
 Other Early Adopters input invaluable !
 Evaluated our (current) options for delivery
 Evaluated our (current) options for delivery partners
 After the Decisions
 Requested Service from the (4) Major Carriers
 Installed, Tested and Verified the solutions
 Extensive Training for the Staff
 Live Cutover on a carrier by carrier basis
Solution and Provider Selected
How Will it Work Here?
 GEM911 Software installed and tested
 Policy and Procedures Developed >>NENA Standards
 Training for all staff will be conducted >> Challenges
 Technical Differences from Wireless
 Concerns over Process and Workload
 Soft Cutover
 Testing & Evaluation
 Training takes place
 Live Cutover with Public Notification
How Will It Work
Allentown Path
How Will It Work ?
How Will It Work ?
• Course Routing (=WP0)
• Base on the location of the
Sector Centroid >
• If the Centroid of the Sector is
located within the geographic area
of the PSAP accepting Text to 9-1-1,
texts from the ENTIRE Sector will
be routed to that PSAP
• Map Location displayed during a
Text Session is the CENTROID, not
the Tower / Sector (WP1) or actual
Location of the Texter (WP2)
• Will Track if Texter moves to
another Tower / Sector
To PSAP
How Will It Work ?
• Course Routing (=WP0)
• Base on the location of the
Sector Centroid >
• If the Centroid of the Sector is
located outside the geographic area
of the PSAP accepting Text to 9-1-1,
texts from the ENTIRE Sector will
receive the bounce back message
•
(Or Route to Adjacent PSAP)
BOUNCE
BACK
How Will It Work ?
• NEW TERM
• HOR = Horizontal Uncertainty
• Similar to COP, COF on
WP2
• Centered on the Centroid
• Expressed in Meters
• T-Mobile Difference
• Due to their wireless location
methods, at times will provide
a HOR very close to WP2
accuracy
To PSAP
How Will It Work ?
• Location Display Example (VZW)
• Centroid of the Sector
• Centroid Location =
• HOR = 2,979
• Tower Site* =
• Actual Location* =
*
Not Actually Displayed
How Will It Work ?
• Location Display Example > T-MOBILE
• Centroid of the Sector Prior to Refresh =
• HOR = 1,222
• Tower Site* =
• Actual Location* =
*
Not Actually Displayed
How Will It Work ?
• Location Display Example > T-MOBILE
• Location of the Texter AFTER Refresh =
• HOR = 31
• Tower Site* =
• Actual Location* =
*
Not Actually Displayed
What will the Public Know?
 Public Announcement / Press Conference
 NENA Message
 9-1-1: Call if you can, Text if you can’t
 Citizens should be encouraged to text only when calling
9-1-1 is not an option
 Stress first thing 9-1-1 will need is location information
and nature of the emergency.
 Text abbreviations or slang should never be used so that
the intent of the dialogue can be as clear as possible.
Production Timeline
• Begin Investigation Process >> June 2014
• First Kickoff Call with VZW & TCS >> November 22, 2013
• Live Cutover with Verizon Wireless >> February 12th, 2014
• Testing and Training (Process Delays due to SNOW)
• Public (LIVE) Announcement >> April 17th, 2014
• Live Cutover with T-Mobile >> April 24th, 2014
• Live Cutover with AT&T >> July 14th, 2014
• Live Cutover with Sprint >> July 28th, 2014
Workload Since Cutover
63
OPERATIONAL PANEL Q&A
65
Building an Implementation Check List
 Getting Started
• Current CPE capability assessment
• Current operation capability assessment
• Funding considerations
• Individual or regional project?
• Points-of-contact (early adopters, experienced consultant)
 Text solution selection
• Vendor
• Solution Level – web, TTY, integrated
 Contacting the wireless providers
 Policy/procedure review
 Training needs assessment
 Public Education/Public Relations
THANKS FOR YOUR PARTICIPATION
John W Geib, ENP
Deputy Director of Public Safety
Emergency Communications Division
Montgomery County Department of Public Safety
[email protected]
O: (610) 631-6538

similar documents