Bridging the Gap from Static Infrastructure to IP-based Nomadic Emergency Services

Transcription

1 The Carrier s Migration Path to e911: Bridging the Gap from Static Infrastructure to IP-based Nomadic Emergency Services Webinar: November 17, 2010 COMPTEL WEBINAR PROGRAM POWERED BY:

2 AGENDA I. Introduction by Tracy MacDonald, COMPTEL II. Overview of dash Carrier Services III. Market snapshot: US migration to IP Telephony IV. State of Emergency Services Current 911 Call Flows and Challenges psali / ALI Management NG9-1-1 how do we get there? FCC mandates what you need to know V. Why dash Carrier Services is THE Industry Leader

3 I. Introduction Today s Speakers Kevin Breault, VP for Business Development & Sales, dash Carrier Services Craig Clausen, EVP of New Paradigm Resources Group

4 AGENDA I. Introduction by Tracy MacDonald, COMPTEL II. Overview of dash Carrier Services III. Market snapshot: US migration to IP Telephony IV. State of Emergency Services Current 911 Call Flows and Challenges psali / ALI Management NG9-1-1 how do we get there? FCC mandates what you need to know V. Why dash Carrier Services is THE Industry Leader

5 II. Overview: dash Carrier Services dash Carrier Services is the leading-edge E911 provider covering the end-toend architecture of emergency communications with specialized solutions for legacy and next generation environments. dash seamlessly supports all communications types on a single platform, quickly driving cost savings for customers and increasing the effectiveness of the Nation s public safety system. Dash manages and operates the most expansive, purpose built emergency services IP network throughout the United States dashemergency dash911 nomadic E911 for VoIP dashali - Static ALI Management dashesp: Managed Service for NG dashvoice - wholesale carrier solutions More than 300 Carrier and VSP Customers Across North America

6 Products Overview

7 AGENDA I. Introduction by Tracy MacDonald, COMPTEL II. Overview of dash Carrier Services III. Market snapshot: US migration to IP Telephony IV. State of Emergency Services Current 911 Call Flows and Challenges psali / ALI Management NG9-1-1 how do we get there? FCC mandates what you need to know V. Why dash Carrier Services is THE Industry Leader

8 NEW PARADIGM RESOURCES GROUP, Inc. (NPRG) is a telecommunications research and consulting firm. Their analysts author original reports that identify, analyze and forecast emerging trends and technologies in the communications industry. NPRG research is founded on intimate knowledge of the 2,000+ telecommunications companies detailed in their dynamic database. Additionally, through its continuous research on telecommunications service providers and carriers, NPRG's analysts prepare meaningful information and analysis on these companies. This information is found in the "Service Provider Profiles and Coverage" NPRG produces.

9 The Road to Service Provider Competition Israeli-based VocalTec Communications develops first Internet tphone and phone software MetaSwitch founded Vonage founded Global Crossing carries more than one billion VoIP MOU Time Warner Cable launches VoIP service through a partnership with MCI and Sprint Skype founded AT&T launches VoIP service, CallVantage ebay acquires Skype for $2.6 billion Comcast launches VoIP service XO serves VoIP to 100,000 business customer employees Comcast surpasses 2 million VoIP customers SunRocket reaches 200,000 VoIP subscribers VoIP Handsets Sold Passes TDM All-Things- IP 1970s- 80s 1990s : BBN Technologies develops the ARPANET, which h provided the fist secure traffic sent over a packet network First VON Conference held LEC landline erosion begins FCC extends Local number portability (LNP) rules to mobile phones MetaSwitch announces 50 th softswitch deployment SBC acquires AT&T Verizon acquires MCI Nov 2007: FCC extends Local number portability (LNP) rules to VoIP Carrier-grade Ethernet over Copper Matures

10

11

12 Figure 3 Wireline Retail Local Telephone Service Connections by Technology, Regulatory Status, and Customer Type as of June 30, 2009 (In Thousands)

13

14 AGENDA I. Introduction by Tracy MacDonald, COMPTEL II. Overview of dash Carrier Services III. Market snapshot: US migration to IP Telephony IV. State of Emergency Services Current 911 Call Flows and Challenges psali / ALI Management NG9-1-1 how do we get there? FCC mandates what you need to know V. Why dash Carrier Services is THE Industry Leader

15 IV. STATE OF EMERGENCY SERVICES CURRENT E911 INFRASTRUCTRE Legacy PSTN Network for Voice Delivery to PSAPs SS7 or CAMA from Originating Network Carrier to Selective Router Primarily CAMA from Selective Router to PSAP CPE Equipment Mix of Serial and IP Connectivity for Location Information Serial for Wireline ALI IP with Fixed Format E2 or PAM Compliant Connection Address Validation based on MSAG

16 Acronyms Defined ANI (Automatic Number Identification) the the calling party number Selective Router specialized telephone switch used for that routes calls based on calling number (ANI) instead of called number; a.k.a tandem switch PSAP (Public Safety Answer Point) First-tier triage call center for emergency calls PSAP operators may dispatch or conference medical/fire/police resources as necessary MSAG (Master Street Address Guide) maintained by a government agency; lists which PSAP serves a particular (postal) address range

17 More Acronyms ALI (Automatic ti Location Identification) a db record of telephone number to geographic location CAMA (Centralized Automated Message Accounting) designed for long distance trunks to carry billing information (ANI); information signaled in-band SS7 (System Signaling 7) utilizes out-of-band signaling for call setup and tear-down; separate data network, used by LECs and IXCs ESQK Emergency Services Query Key ESRK Emergency Services Routing Key ESRN Emergency Services Routing Number VPC VoIP Positioning Center

18 Types of Emergency Calls Today - i1 (Basic) and i2 (Enhanced 911) i1 911 (Basic 911) Call delivery to Public Service Answering Point (PSAP) with or without Automated Number Identification (ANI). No address delivery. Today represents less than 5% of PSAPs. i2 911 (Enhanced 911) Call delivery to PSAP with ANI. Additional delivery of address from Address Location Information (ALI) database.

19 Wire-line vs VoIP Call Flow i2/e911 Wire-line Call Flow 1. PSAP receives call over trunk. 2. PSAP CPE queries static ALI database (local or remote) with ANI 3. PSAP CPE obtains address information that has been statically provisioned by service provider. 4. PSAP CPE displays address information to PSAP operator.

20 i2/e911 VoIP Call Flow 1. E911 VPC (dash) replaces ANI with an ESQK number. ESQK is basically a proxy number used by VPC for an existing ALI shell record. 2. PSAP receives call over trunk likely via Selective Router. 3. PSAP CPE queries static ALI (local or remote) with ESQK and obtains a shell record. 4. Static ALI database queries VPC database over IP/frame network using the ESQK key. 5. Static ALI database obtains address information that dynamically exists in database managed by service provider and returns to the PSAP 6. PSAP CPE displays address information to PSAP operator.

21 VoIP versus Wire-line Summary 1. Instead of direct trunk from CO to PSAP, a majority of calls use access through a Selective Router that interconnects multiple PSAPs within the territory of an ILEC. 2. Dynamic nature of addresses requires ESQK and shell records to handle the ability for an address change within minutes. 3. i2/e911 coverage is less than wire-line i2/e911 coverage Inability for PSAP to leverage shell record mechanism system limit Cost structure to obtain trunking to PSAP

22 I2/E911 Shortcomings 1. Still requires PSTN connectivity to all PSAPs 6500 PSAPs some accessible via Selective Router Limits nature of communication mechanisms 2. Nomadic supported but not full mobile support. Requires association with a physical address instead of coordinates No ability to update during call Address entry a function of user compliance 3. Not fully real-time PSAP selection This issue is solved for initial PSAP routing but does not address PSAP status, failover paths, or emergency specific type routing. 4. MSAG Address Validation Timely updates are difficult and leaves many gaps in routing logic

23 Summary Adoption rates VoIP 911 rules and functionality have been in place since 2005 Penetration ti rates by Non-ILEC is expected to grow Many incumbent carriers have not, or now planning, support of nomadic (VoIP) 911 capabilities Incumbent carriers have deployed nomadic 911 for wireline and VoIP subscribers

24 AGENDA I. Introduction by Tracy MacDonald, COMPTEL II. Overview of dash Carrier Services III. Market snapshot: US migration to IP Telephony IV. State of Emergency Services Current 911 Call Flows and Challenges psali / ALI Management NG9-1-1 how do we get there? Operational considerations FCC mandates what you need to know V. Why dash Carrier Services is THE Industry Leader

25 IV. psali / ALI Management The growing demand of IP PBXs has led to a greater need to provide location information. States and local authorities are taking steps to provide oversight and guidelines to ensure improved emergency services Many PBX vendors, and third parties, are providing solutions to address this requirement Shift in responsibility from the carrier to the enterprise for compliance

26 U.S. State Regulation: MLTS Authority Implementation Cite Arkansas Broad Interpretation AR Code Colorado HB 1084 (2001) Notification Only Will Amend Connecticut Broad Interpretation CT Gen. Statutes 28-25b Florida Mandatory Compliance by Statute F.S. Illinois Mandatory Compliance by Statute and Regulation 50 ILCS 750/ IAC City of Chicago Compliance by Recommendations for PBX Systems N/A Kentucky Statute Residential Only KRS Louisiana ACT Compliance for PBX Systems Senate Bill 878 R.S. 33:9110 Maine Mandatory Compliance by Statutet t House Bill 1056, (LD 1444) Minnesota Mandatory Compliance by Statute Chapter 282 SF No. 653 Mississippi Mandatory Compliance by Statute Texas Mandatory Compliance by Statute House Bill 802, Amends Section of the Health and Safety Code Vermont Mandatory Compliance by Statute 30 VSA Virginia House Bill 1603 (adopted 2/19/2007) Amends the powers and duties code of Wireless E-911 Service Board Washington Mandatory Compliance by Statute RCW

27 Emergency Response Location (ERL) and Emergency Location Identification Number (ELIN) ERL: A location to which a Emergency Response Team may be dispatched; the location should be specific enough to provide a reasonable opportunity to quickly locate a caller ELIN: A valid North American Numbering Plan Format telephone number, assigned to the MLTS Operator by the appropriate authority, that is used to route the call to a PSAP and is used to retrieve the ALI for the PSAP; associates the ELIN with the ERL and which the PSAP can also use to call back the emergency caller

28 Emergency Response Location and Emergency Location Identification Number A way to summarize and refer to locations Advocated by the National Emergency Number Association (NENA) Puts phones in groups for the purposes of location identification Requires ranges of phone numbers to identify origin of call Allows non-did phones to be located ELIN is number used as key into routing and ALI database ELIN with ERL is loaded into ALI db one time Phones can move freely around campus ANI is changed to ELIN on outbound calls

29 NENA Guidelines NENA MLTS Model Legislation TechInfoDocs/MLTS_ModLeg_Nov2000.PDF At least one ERL needed for each floor of a building, except (only one ERL for): Workspaces less than 7,000 ft 2 on a single propertyp Workspaces less than 40,000 ft 2 on a single property if there are less than 49 stations One ERL for each unit in a hotel/motel (or provide auto- conference with knowledgeable hotel/motel staff and PSAP) At least one ERL for each tenant in a multi-tenant building Key Telephone Systems only require one ERL

30 AGENDA I. Introduction by Tracy MacDonald, COMPTEL II. Overview of dash Carrier Services III. Market snapshot: US migration to IP Telephony IV. State of Emergency Services Current 911 Call Flows and Challenges psali / ALI Management NG9-1-1 how do we get there? Operational considerations FCC mandates what you need to know V. Why dash Carrier Services is THE Industry Leader

31 IV. NG How do we get there? Next Generation capabilities are currently being planned and implemented. Carriers will have to comply with new database formats and call delivery Existing 911 call methods will have to be supported through the transition

32 What is NG9-1-1? 1? NG9 1 1 is a system comprised of hardware, software, data and operational policies and procedures to: Provide standardized interfaces from call and message services process all types of emergency calls including non voice (multimedia) messages Acquire and integrate additional data useful to call routing and handling deliver the calls/messages and data to the appropriate PSAPs and other appropriate emergency entities Support data and communications needs for coordinated incident response and management provide a secure environment for emergency communications

33 NG9-1-1 Network Core Emergency Services IP Network (ESInet) ESInets use broadband, packet switched technology capable of carrying voice plus large amounts of varying types of data using Internet Protocols and standards. ESInets are engineered, managed networks, and are intended to be multi purpose, supporting extended Public Safety communications services in addition to Databases and Data Management NG9 1 1 uses a set of database systems to house and provide management of the above data content. Some examples are: validation, routing control, policy/business i rules, and system wide detail call records.

34 NG9-1-1 Network Core. cont. Databases and Data Management Cont. NG9 1 1 provides the mechanisms to access external sources of data, either automatically or manually, via the ESInet, to support more knowledgeable and efficient handling of emergency calls/messages. Examples: telematics/acn data, hazardous material information, building plans, medical information, etc. Security NG9 1 1 provides extensive security methods at the hardware and software levels to replicate the privacy and reliability inherent in E9 1 1 services.

35 I3/NG Advantages 1. IP connectivity More cost effective interconnection Multiple methods of communication including voice, video, and SMS. 2. Mobile support Specifications for supporting both mobile devices as well as automatic location updates in place of end-user address provisioning 3. Full real-time routing Support for reroute based upon PSAP capacity, disaster recovery, and/or emergency call type 4. Delivery of more pertinent information to PSAP operators

36 Why is I3/NG not ubiquitous? 1. PSAP Autonomy/Funding PSAPs are locally controlled. NENA specifications are guidelines. PSAP funding is decreasing in the transition from wireline to VoIP/Wireless 2. NG9-1-1 is More Complicated PSAPs forced to integrate new systems, processes, and risks into their existing infrastructure. Early adopter issues. New knowledge base required that is not currently in place ILEC Inconsistency ILECs are protecting existing 911 infrastructure and associated revenue While trying to sell their own NG9-1-1 solutions in many cases Transition of i2/911 network to I3/NG9-1-1 is resource intensive

37 NENA s i3 Architecture Clients Access Networks Origination Networks Emergency Services IP Network (ESInet) Domains Government Services Legacy PSAP/Emergency Responders IM Clients LISs CSP Call Server Public Web Services DNS Legacy PSAP Gateway Multimedia Services NG9-1-1 (i3) PSAP SIP/H.323 clients Public Access IP Networks E-CSCF (IMS) Global Internet, Private Networks or IMS Location Validation Web Interface ECR Web Interfaces Originating Border Control ESInet Originating ESRP Terminating Border Control ESInet Terminating ESRP Wireless/IP Client Emergency Call Routing & Location Validation Databases Legacy Network Gateway Private Web Services Supplemental Services Databases NG9-1-1 (i3) PSAP PSTN client Legacy Circuit- Switched Networks Wireless/CS Client NOTE: Elements labeled in italic bold blue are in scope for this document. All others are shown for completeness only.

38

39 NG9-1-1 Status

40 AGENDA I. Introduction by Tracy MacDonald, COMPTEL II. Overview of dash Carrier Services III. Market snapshot: US migration to IP Telephony IV. State of Emergency Services Current 911 Call Flows and Challenges psali / ALI Management NG9-1-1 how do we get there? FCC mandates what you need to know V. Why dash Carrier Services is THE Industry Leader

41 FCC VoIP E911 Requirements The FCC s rules require interconnected VoIP providers to: Transmit all 911 calls, as well as ANI and the caller s Registered Location for each call, to the PSAP or other designated answering point or local emergency authority that t serves the caller s Registered Location Obtain from each customer, prior to the initiation of service, the physical location at which the service will first be utilized; and Provide subscribers one or more methods of updating their Registered Location, including at least one option that requires only the CPE used to access the service. Registered Location information must be available to the appropriate PSAP or other designated answering point or local emergency authority from or through the appropriate automatic location information (ALI) database

42 Definitions Interconnected VoIP: Enables real-time, two-way voice communications; Requires a broadband connection from the user s location; Requires Internet protocol-compatible CPE; and Permits users generally to receive calls that originate on the PSTN and to terminate calls to the PSTN Registered Location: The most recent information obtained by an interconnected VoIP service provider that identifies the physical location of an end user

43 NET 911 Act Provides wireless and Interconnected VoIP carriers the same liability protection that states have historically provided wireline common carriers Underlying policy is that carriers would not provide 911 service if they could be held liable for injury resulting for provision of the service Requires entities controlling the capabilities necessary to provide E911 service, including LECs, PSAPs, and other to make those capabilities available to VoIP on the same basis and under the same terms and conditions as they are made available to other

44 Next Generation E911 NPRM Among other things, the FCC is seeking comments on a number of issues relating to NG9-1-1, including: How NG9-1-1 deployments may affect location accuracy and ALI requirements; How the FCC may need to revise its location accuracy and ALI requirements to account for the deployment of NG9-1-1 systems; The expected impact of NG9-1-1 deployments on the existing wireless location accuracy and ALI requirements; and The current state of NG deployments and what is in the planning stage; What technological or operational changes might service providers, applications developers, and device manufacturers implement that would complement NG9-1-1 capabilities; Ways to improve location accuracy for interconnected VoIP; Whether it should apply similar requirements on nomadic VoIP; and Whether VoIP providers should be required to automatically provide geographic location information for their customers and what technologies exist to do so.

45 AGENDA I. Introduction by Tracy MacDonald, COMPTEL II. Overview of dash Carrier Services III. Market snapshot: US migration to IP Telephony IV. State of Emergency Services Current 911 Call Flows and Challenges psali / ALI Management NG9-1-1 how do we get there? FCC mandates what you need to know V. Why dash Carrier Services is THE Industry Leader

46 dashemergency

47 V. WHY dash Carrier Services dash911: full service emergency solution for CLECs, ILECs, MSOs, ISPs, and ITSPs for end-to-end call control and support, real-time address validation, automated provisioning, and patent-pending geospatial routing. Dynamic Address Validation No MSAG requirement, 98% address success on initial submission 92% enhanced PSAP coverage best in the industry! Flexible interconnect SIP, private line, or PSTN Web portal for subscriber registration, moves, adds, and changes Batch registrations for large conversions Full compliance with all regulatory agency requirements Unmatched support 24x7 support by E911 experts psali support and provisioning

48 V. WHY Dash Carrier Services, cont. dashali: a fully managed and dynamic LEC ALI database management tool for carriers providing emergency services throughout North America. dashali supports legacy ILEC and CLEC infrastructures enabling improved record management and provides a upgrade path to nomadic (VoIP) functionality. Dynamic front end address validation tool replaces antiquated and inefficient MSAG only tools with intelligent alternative address matching, civic to MSAG conversion and an average 98% first pass validation success rate. Easy integration bulk upload and project management Flexible record management including Web Portal, API and FTP for easy subscriber registration, moves, adds, and changes Batch registrations for any sized conversions Complete LEC ALI record management and psali management capability Full compliance with all regulatory agency requirements Unmatched customer support 24x7 support by E911 experts

49 ALI Record Flow

50 V. WHY Dash Carrier Services, cont. dashesp: dashesp is a comprehensive managed service for 911 authorities bridging the gap from legacy 911 to NG dashesp managed service accepts emergency calls from carriers and delivers them to Public Safety Answering Points (PSAPs). PSAPs can use the equipment they have in place today without modification or they can deploy systems that are compliant with the NG9-1-1 standards. Complete routing solution from the point of delivery by an originating network provider to delivery at the PSAP Fully adheres to the NENA NG9-1-1 standards and Support for current carrier interfaces including CAMA & SS7, current PSAP interfaces including CAMA Full project management for deployment Fully secure implementation with tight access control to all system components Phased implementation bringing the current system to be fully compliant with the NG9-1-1

51 dash Platform Differences 1. Purpose-built from ground up to Next Generation vision, I2-compliant, I3-ready 2. Dynamic Geospatial Routing Routing decisions made at time of call based on real-time X,Y coordinate of caller and PSAP boundary; automated and dynamic 3. Dynamic Address Validation Efficient and intelligent with a 98% or better validation success rate on average 4. 93% Enhanced coverage of US, Canada, and Puerto Rico via fullyredundant nationwide network 5. Dash uses the most accurate and proven PSAP boundary files to support accurate nationwide call routing 6. Emergency call center (ECC) for NRFs and I1 calls

52 Emergency Services: Features to Consider Support of all emerging technologies Start-up and Maintenance Costs - TCO Automation and accuracy Address validation success and efficiency i Ease of integration Speed to deployment (time to revenue) Customization capability Coverage and Connectivity options Responsive Customer Support

53 Conclusion All providers should not ignore FCC guidelines or the impending NG9-1-1 capabilities NG9-1-1 may not be an immediate action item but plays a role in long term decision i making for network build-out. Originating Carriers Need to Begin Evaluating How They Will Interface with i3 Compliant NG9-1-1 PSAPs Long Road Ahead But This Year Significant Increase in the Progress to NG9-1-1

54 Contact: Kevin Breault Vice President of Sales & Business Development Direct COMPTEL WEBINAR PROGRAM POWERED BY: