Bridging the Gap from Static Infrastructure to IP-based

The Carrier’s Migration Path to e911: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:COMPTEL WEBINAR PROGRAM POWERED BY:

©2010 dash carrier services | 303.228.8800 | www.dashcs.com

AGENDAAGENDA

I. Introduction by Tracy MacDonald, COMPTELII. Overview of dash Carrier ServicesIII Market snapshot: US migration to IP TelephonyIII. Market snapshot: US migration to IP TelephonyIV. State of Emergency Services

– Current 911 Call Flows and Challenges– psALI / ALI Management– 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 LeaderV. Why dash Carrier Services is THE Industry Leader


I IntroductionI. Introduction

Today’s Speakers• Kevin Breault VP for Business Development &• Kevin Breault, VP for Business Development &

Sales, dash Carrier Services

• Craig Clausen, EVP of New Paradigm Resources Group


AGENDAAGENDA





II Overview: dash Carrier ServicesII. Overview: dash Carrier Services

dash Carrier Services is the leading-edge E911 provider covering the end-to-end 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 NG9 1 1• dashESP: Managed Service for NG9-1-1

• dashVOICE - wholesale carrier solutions

• More than 300 Carrier and VSP Customers Across North America


Products OverviewProducts Overview


AGENDAAGENDA





NEW PARADIGM RESOURCES GROUP Inc (NPRG) is aNEW 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 analysiscarriers, NPRG s analysts prepare meaningful information and analysis on these companies. This information is found in the "Service Provider Profiles and Coverage" NPRG produces.


The Road to Service Provider CompetitionXO serves VoIP

to 100,000 business customer

employees

AT&T launches VoIP

service, CallVantage

i

Global Crossing carries more than one billion

VoIP MOU

Israeli-based VocalTec

Communications develops first

I t t h d

VoIP Handsets Sold Passes

Time Warner Cable launches VoIP service

through a partnership with MCI and Sprint

Sk

eBay acquires

Skype for $2.6 billion

Internet phone and phone software

MetaSwitchfounded Comcast launches

Comcast surpasses 2

million VoIP customers

S R k t h

TDM

All-Things-IP

Skype founded

Vonage founded

2002 2004 2005 2006 2007 20082003 20092000 20011990s1970s-80s

founded Comcast launches VoIP service

SunRocket reaches 200,000 VoIP

subscribers

2010 2011+

Verizon acquires MCI

LEC landline erosion begins

FCC extends

1973: BBN Technologies develops the ARPANET,

hi h

Carrier-grade Ethernet over

Copper Matures

SBC acquires AT&T

FCC extends Local number

portability (LNP) rules to mobile

phones

Nov 2007: FCC extends Local

number portability (LNP)

rules to VoIP

which provided the fist secure traffic sent

over a packet network

MetaSwitchFirst VON

Conference held announces 50th

softswitchdeployment



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



AGENDAAGENDA





IV STATE OF EMERGENCY SERVICESIV. STATE OF EMERGENCY SERVICES

CURRENT E911 INFRASTRUCTRE

– Legacy PSTN Network for Voice Delivery to PSAPsg y y• 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 Connectionp

– Address Validation based on MSAG


Acronyms Defined

• ANI (Automatic Number Identification) the calling

Acronyms Defined

• ANI (Automatic Number Identification)—the calling party number

• Selective Router—specialized telephone switch used for 9-1-1 that routes calls based on calling number (ANI) instead of 9 t at outes ca s based o ca g u be ( ) stead ocalled number; a.k.a. 9-1-1 tandem switch

• PSAP (Public Safety Answer Point)–First-tier triage call center for emergency callsg g y–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


M A

ALI (A t ti L ti Id tifi ti ) db d f

More Acronyms

• ALI (Automatic Location Identification)—a db record of telephone number to geographic location

• CAMA (Centralized Automated Message Accounting)—designed for long distance trunks to carry billing informationdesigned 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


Types of Emergency CallsTypes of Emergency Calls

• i1 911 (Basic 911) – Call delivery to Public Service Answering

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) databaseInformation (ALI) database.


Wire-line vs VoIP Call Flow

1 PSAP receives call over trunk

i2/E911 Wire-line Call Flow1. PSAP receives call over trunk.2. PSAP CPE queries static ALI database (local or remote)

with ANI3 PSAP CPE obtains address information that has been3. PSAP CPE obtains address information that has been

statically provisioned by service provider. 4. PSAP CPE displays address information to PSAP

operatoroperator.


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.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.


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 to2. 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 – systemInability for PSAP to leverage shell record mechanism system

limit• Cost structure to obtain trunking to PSAP


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.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• 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 routingtype routing.

4. MSAG Address Validation • Timely updates are difficult and leaves many gaps in routing

logic


Summary – Adoption rates

• VoIP 911 rules and functionality have been in place since 2005P t ti t b N ILEC i t d t• Penetration 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 wire-line and VoIP subscribers


AGENDAAGENDA


– Current 911 Call Flows and Challenges– psALI / ALI Management– 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


IV psALI / ALI ManagementIV. 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


U.S. State Regulation: MLTSAuthority Implementation Cite

Arkansas Broad Interpretation AR Code §12-10-317

Colorado HB 1084 (2001)—Notification Only Will Amend §29-11-100.5

Connecticut Broad Interpretation CT Gen. Statutes §28-25b

Florida Mandatory Compliance by Statute 365.175. F.S.

Illinois Mandatory Compliance by Statute and Regulation

50 ILCS 750/15.5–15.683 IAC 726–727

C li b R d iCity of Chicago Compliance by Recommendations for PBX Systems N/A

Kentucky Statute—Residential Only KRS §65.752–754

Louisiana ACT—Compliance for PBX Systems Senate Bill 878 R.S. 33:9110

M i M d t C li b St t t H Bill 1056 (LD 1444)Maine Mandatory Compliance by Statute House Bill 1056, (LD 1444)

Minnesota Mandatory Compliance by Statute Chapter 282 SF No. 653

Mississippi Mandatory Compliance by Statute §19-5-359

Texas Mandatory Compliance by Statute House Bill 802, Amends Section 772.218 of the Health and Safety Codey p y of the Health and Safety Code

Vermont Mandatory Compliance by Statute 30 VSA §07057

Virginia House Bill 1603 (adopted 2/19/2007) Amends § 56-484.14 the powers and duties code of Wireless E-911 Service Board

Washington Mandatory Compliance by Statute RCW 80 36 555–560

http://www.apcointl.org/about/pbx/documents/E911_chart.pdf

Washington Mandatory Compliance by Statute RCW 80.36.555–560

Emergency Response Location (ERL) and E L ti Id tifi ti N b (ELIN)Emergency Location Identification Number (ELIN)

• ERL: A location to which a 9-1-1 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


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• 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 9-1-1 calls


NENA GuidelinesNENA Guidelines

• NENA “MLTS Model Legislation”– http://www.nena.org/9%2D1%2D1techstandards/

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 ft2 on a single propertyp g p p y– Workspaces less than 40,000 ft2 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)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


AGENDAAGENDA


– Current 911 Call Flows and Challenges– psALI / ALI Management– 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


IV NG9 1 1 H d t th ?IV. NG9-1-1 How do we get there?

• Next Generation 9-1-1 capabilities are currently being planned and implemented.Carriers will have to comply with new database formats and• Carriers will have to comply with new database formats and call delivery

• Existing 911 call methods will have to be supported through the transitionthe transition


Wh t i NG9 1 1?What is NG9-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 otherdeliver 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 communicationscommunications


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 9‐1‐1.

• 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, li /b i l d t id d t il ll dpolicy/business rules, and system‐wide detail call records.


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.


I3/NG9 1 1 AdvantagesI3/NG9-1-1 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 routing3. 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 operatorsy p p


Why is I3/NG9 1 1 not ubiquitous?Why is I3/NG9-1-1 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/Wirelessg g

2. NG9-1-1 is More Complicated• PSAPs forced to integrate new systems, processes, and risks into their existing

infrastructure.• Early adopter issuesEarly 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


NENA’s i3 Architecture

Legacy PSAP/Emergency RespondersGovernment

Services

Access Networks Origination Networks Emergency Services IP Network (ESInet) DomainsClients

DNS

Public WebServices

LISsMultimediaServices

ESInet

IM Clients

CSPCall Server

Legacy PSAPGateway

NG9-1-1 (i3) PSAP

OriginatingESRP

OriginatingBorder Control

Location Validation

S etGlobal Internet,

Private Networks or IMS

Public AccessIP NetworksSIP/H.323

clients

ESInet

TerminatingESRP

TerminatingBorder ControlE-CSCF

(IMS)

ECRWeb

Interfaces

Wireless/IPClient

Web Interface

SupplementalServices

Databases

LegacyNetworkGateway

Private WebServices

Emergency Call Routing &Location Validation

Databases

NG9-1-1 (i3) PSAP

Legacy Circuit-Switched Networks

PSTN client

NOTE:

Wireless/CSClient

Elements labeled in italic bold blueare in scope for this document. All others are shown for completeness only.

NG9-1-1 Status

AGENDAAGENDA





FCC VoIP E911 Requirements

The FCC’s rules require interconnected VoIP providers to:

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

th it th t th ll ’ R i t d L tiauthority that 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– 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


DefinitionsDefinitions

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


NET 911 ActNET 911 Act

• Provides wireless and Interconnected VoIP carriers the same liability protection that states have historically provided wire-line 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 toRequires 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 yavailable to other


Next Generation E911 NPRM

Among other things the FCC is seeking comments on a number of issues

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; H th FCC d t i it l ti d ALI i t t t f th• 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 NG9 1 1 deployments and what is in the planning stage;• The current state of NG9-1-1 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 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.


AGENDAAGENDA





dashEMERGENCYdashEMERGENCY


V WHY dash Carrier ServicesV. WHY dash Carrier Services

d h911 f ll i l ti f CLEC ILEC MSO ISPdash911: 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


p pp p g

V WHY Dash Carrier Services contV. WHY Dash Carrier Services, cont.

dashALI: a fully managed and dynamic LEC ALI database management tool fordashALI: 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 managementEasy 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 capabilityComplete LEC ALI record management and psALI management capability• Full compliance with all regulatory agency requirements• Unmatched customer support — 24x7 support by E911 experts


ALI Record Flow

V WHY Dash Carrier Services contV. WHY Dash Carrier Services, cont.

dashESP: dashESP is a comprehensive managed service for 911 authoritiesdashESP: dashESP is a comprehensive managed service for 911 authorities bridging the gap from legacy 911 to NG9-1-1. 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 withtoday 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 08-002 and 08-003• Support for current carrier interfaces including CAMA & SS7, current PSAP

interfaces including CAMAinterfaces 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

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;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 averagebetter validation success rate on average

4. 93% Enhanced coverage of US, Canada, and Puerto Rico via fully-redundant nationwide network

5. Dash uses the most accurate and proven PSAP boundary files to p ysupport accurate nationwide call routing

6. Emergency call center (ECC) for NRFs and I1 calls


Emergency Services: Features to ConsiderEmergency Services: Features to Consider

• Support of all emerging technologies• Start-up and Maintenance Costs - TCO• Automation and accuracy

Add lid ti d ffi i• Address validation success and efficiency• Ease of integration• Speed to deployment (time to revenue)• Customization capability• Customization capability• Coverage and Connectivity options• Responsive Customer Support


C l iConclusion

All id h ld t i FCC id li th i di• 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 i l t d i i ki f t k b ild tin long term decision 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


Contact:

Kevin BreaultVice President of Sales & Business DevelopmentDirect – [email protected]

COMPTEL WEBINAR PROGRAM POWERED BY:


POWERED BY:

Documents

Bridging the Gap from Static Infrastructure to IP-based