NG9-1-1 Deployments in U.S.A.

Transcription

1 NG9-1-1 Deployments in U.S.A. Presented to EU Emergency Services Workshop April 16, 2013 Byron L. Smith, Consultant Skype: Byron L Smith (psapman) byron@psapservice.com Mobile:

2 Disclaimers The contents of this presentation include my personal opinions I am not aware of all NG9-1-1 deployments occurring in the US Some facts have been rounded for ease of presentation and discussion

3 Outline Political / Funding History and Context Drivers for NG9-1-1 Migration Sampling of NG9-1-1 efforts in USA Three examples (with lessons learned) State of Kansas Pilot Project East Texas Council of Governments (ETCOG) State of Tennessee How do we get from here to there?

4 History and Funding Original deployments in U.S. were for local wireline telephone service (early 1990s) Local telephone company was service provider Funded and administered via local taxes at county or large city level State often provided enabling legislation NENA was only national-level organization, little national funding or involvement Re-addressing rural areas to tabular addresses, e.g Apple Road, rather than Rural Route Box 27, was a major effort

5 Wireless (Mobile) add-on Deployed early 2000 s, FCC requirements Technical solution required pani dynamically and temporarily assigned to call for compatibly with existing wire line network ALI servers required to forward requests Mostly funded at State level with Board/Committee administration of funds Lat/Lon position reporting required PSAPs to install mapping systems to plot caller location

6 Drivers to NG % or more emergency calls in the U.S. are now from mobile devices Seven to 17% of mobile emergency calls require inter-psap transfer, but legacy network not interconnected at service provider boundaries NG9-1-1 network may be 50% of legacy costs NG9-1-1 provides flexibility to accommodate new communications models & technologies

7 Sampling of NG9-1-1 efforts in the U.S. Majority of efforts at the state level Maine complete turnkey statewide system, RFP issued, vendor selected, in contract negotiation Connecticut like Maine, but state already deployed fiber-based IP infrastructure to all PSAP sites Palm Beech County Florida 27 PSAP sites, deployment in final stages Michigan state driven IP network planning, GIS, and PSAP consolidation studies

8 Sampling (continued) Idaho, New Mexico, Oregon, Florida, Colorado, Kentucky, Massachusetts, others various stages of state level NG9-1-1 planning South Dakota in process of procuring consulting services Projects differ in extent of state involvement with local PSAP equipment replacement Many state-level projects centralize some NG9-1-1 functions such as the ECRF

9 Kansas NG9-1-1 Pilot Project

10 Kansas Context Population approximately 2.8 million Area approximately 213,000 square kilometers Two major cities (Wichita and Kansas City) have more than 1/3 of state s population Most of state is very rural, very low population density One county in pilot project had PSAP serving 2,400, another county had PSAP serving 550,000.

11 9-1-1 Funding / Political Structure Local PSAP administration and funding Only state-level function was committee to distribute wireless (mobile) funds to PSAPs Little understanding of NG9-1-1 among public safety community Pilot effort funded by state funds with federal matching grants Pilot final report due September 2012

12 Scope of Pilot Build state-wide database of basic PSAP data: Addresses, contacts, call volumes, equipment types, operational characteristics, etc. NG9-1-1 education effort: what, why, how Investigate models for providing ESInet and NG9-1-1 services that fit state culture Select representative sites for NG9-1-1 pilot Implement a demonstration NG9-1-1 system

13 Pilot Outcomes State Office of Information Technology Systems (OITS) built and operated pilot ESInet (IP infrastructure) Shared WAN facilities with Kansas Criminal Justice Information System (KCJIS) to lower cost and provide redundancy and diversity (win-win) Performed GIS study to determine effort and cost to build state-wide NG9-1-1 GIS database, GIS effort is ongoing State legislature expanded scope of Advisory Council, changed political structures to accommodate NG9-1-1 Deployed centralized ( hosted model ) NG9-1-1 services, PSAP equipment just browser-based work stations

14 Lessons from Kansas Pilot Deploying NG9-1-1 may require changes at layer 8, the political layer Full NG9-1-1 (location-based routing) requires a public safety-quality GIS database Providing a quality ESInet (IP infrastructure) is straightforward, but providing quality NG9-1-1 services is more problematic Education of stakeholders is very important

15 East Texas Council of Governments

16 ETCOG Context 14 Counties in east Texas, mostly rural Approximately 810,000 people Approximately 26,000 square kilometers Approximately 600,000 emergency calls / year Approximately 60 staffed emergency call answering positions, 40 provided by the COG Several municipalities operate PSAPs independently of the COG

17 NG9-1-1 Deployment Three year effort, completed August 2012 Issued RFP for ESInet, awarded to a telco Issued RFP for CPE, awarded to a vendor Deployed two redundant host server sites (on-line/hot standby) Servers capable of accepting NENA i3-compliant signaling Server sites contain CAMA to SIP gateways, 48 ports at each site Replaced ETCOG-supplied PSAP CPE with SIP telephones and web-browser-based terminals

18 ETCOG NG9-1-1 Costs COG was facing significant legacy CPE replacement, upgrade, and maintenance costs NG9-1-1 CPE paid for by just a few years (3-4) of legacy MRC for maintenance services Monthly recurring charges (MRC) for network did not change much or increased slightly; new ESInet costs offset by elimination of ALI circuits and old GIS update network System is legacy (with all related costs) to the two server sites, the system is all IP from the server sites to the PSAPs

19 Lesson from ETCOG Existing CAMA trunks were re-provisioned from the PSAP sites to the server sites This involved three telcos, and was very painful, time-consuming, and expensive Telcos have limited resources that have knowledge of legacy CAMA technologies (in other words, all the old guys who know how this works have retired) If we were doing it again, we would gateway the legacy CAMA trunks at the PSAP sites onto the IP infrastructure, to avoid moving these trunks.

20 Tennessee Statewide NG9-1-1

21 Tennessee Context Population approximately 6,500,000 Area approximately 110,000 square kilometers Approximately 140 PSAPs Pre-existing statewide contract for WAN IP services with a major telco PSAPs provide own equipment locally NG9-1-1 deployment for wireless calls only (for now)

22 Tennessee Architecture Telco providing ESInet (NetTN), IP-based selective router services, and legacy to IP gateways RFP issued and awarded for separate company to maintain databases and manage NG9-1-1 deployment Location-based routing not deployed at this time NENA i3 compliant interfaces required at PSAP to NetTN interface Some PSAPs may gateway to legacy equipment, others have installed / are installing NENA i3 compliant local equipment

23 NG9-1-1 Deployment NG9-1-1 overlays legacy network which is left in place for now for wireline and backup Several fully NENA i3 PSAPs are in production State has developed list of CPE vendors with equipment tested and known to work on NetTN IPv4 address space limitations has been an issue due to ESInet provider policies Probably largest i3 compliant system (less location based routing) in US that is in production

24 Lessons from Tennessee Limit number of conversions between Legacy and VoIP to prevent voice quality problems Plan ahead for IPv4 address space limitations, or (even better) deploy with IPv6 Location-based routing may be cost effective only if/when legacy selective routers can be eliminated Wireless carrier trunk grouping / default routing differences and related issues

25 Lessons Learned Many Sources Various security issues PSAPs may have interconnected CAD / mapping systems which access public internet Must establish security zones / layers PSAP to ESInet firewalls are required Migration issues Legacy databases may contain obsolete data Recording system considerations legacy trunk based and captured pre-call-answer audio ESN numbering conflicts among legacy service providers Network design IP network providers may not understand highly reliable / available IP infrastructures MTU / UDP size limitations on SIP messages with PIDF-LO, must use TCP

26 How do we get to NG9-1-1? IETF-based standards, such as NENA i3 and EENA 112, appear to be viable, but not yet completely understood or accepted by all vendors Legacy and NG9-1-1 must coexist for a period of time Must carefully consider migration to minimize gateway requirements and conversion costs Intellectual Property issues appearing in U.S.