Enhancing Conversational Speech Quality of VoIP in a Wired/Wireless Environment
E911 Services and the VoIP Environment - · PDF fileE911 Services and the VoIP Environment...
Transcript of E911 Services and the VoIP Environment - · PDF fileE911 Services and the VoIP Environment...
Technology Forum at TELECOM ‘05
E911 Services and the E911 Services and the VoIPVoIPEnvironmentEnvironment
Wednesday, October 261:30 – 3:00 p.m.Veronese 2502
Vonage E911 Deployment
The Vonage History
*BusinessWeek Online, Jane Black, September 5, 2003
Vonage looks forward to a successful year and long partnership with the 9-1-1 community to work together to resolve issues related to the current IP solution, and on the joint development of the next generations of 9-1-1 services.
2001 – 2003• Research and Development• Market Testing• Product Launch
2004• National Retail Launch• Global Expansion Commences with Canada
and the U.K.• Rhode Island E9-1-1 Deployment• Advocacy for Complete 9-1-1 Access
2005• Aggressive 9-1-1 Deployment and
Implementation• Continuing Global Expansion• Wi-Fi Phone Launch• Videophone Launch
Above and Beyond the FCC E9-1-1 Order
• Immediate Response: Aggressive Technical, Operational and Policy Leadership
• Vonage E9-1-1 Enforcer: Web based customer application that requires E9-1-1 service system sign-up. All Vonage subscribers MUST register E9-1-1 location.
• Vonage “Safety-Net” 9-1-1 Call Center: In the event a customer cannot connect directly to 9-1-1 through the native 9-1-1 network, 10-digit emergency routing, or has an address that is not valid, calls will be sent to a national call center for re-routing to proper emergency authority. APCO 33 trained call takers.
• Recognition that 9-1-1 is a Partnership: Working with ILEC’s, Regulatory Leaders, Public Safety Professionals and all parties involved in 9-1-1.
• Vonage E9-1-1 Deployment: New York City and Rhode Island. Actively Testing other Markets:Deployed E9-1-1 in New York City following six months of negotiations and active project management.
• Vonage PSAP and 9-1-1 Outreach:20/20 Outreach, NENA, APCO and More, www.vonage.com/PSAPcenter
Vonage E9-1-1 Approach
• Vonage is pursuing multiple E9-1-1 paths and approaches to ensure success:
1. Implementation of Multiple ESGW (Gateways)
2. PSAP Outreach and Deployment
3. National Interconnection and Network
4. Wireless like Methods for Transmitting Calls (pANI, Shell Records, ESN)
Vonage E9-1-1 Approach9-1-1 is a Shared Responsibility, Partnership and Functionality
1. Vonage Network
2. Over 500 plus Selective Routers
3. Provisioning of 9-1-1 System Service Provider Elements and Support (ILEC)
1. Shell Records (Format for PSAP to “receive” information)
2. ALI Record Steering for VoIP
3. Emergency Service Query Keys (unlock selective routers)
4. VoIP ESN (Emergency Service Routing Numbers)
5. Support Data and 9-1-1 Information, (Master Street Address Guides)
4. PSAPs Must be able to Receive Calls
1. Order Shell Records and Provide Data
2. Vonage, ILEC and VPC Testing
3. Go Live Notification
Vonage E9-1-1 Architecture
E9-1-1 Implementation and Deployment• PSAP outreach and “Deployment Kits”
• Verify and collect PSAP specific information
• Integration scheduling with PSAP• Operational Procedures, Testing and Updates
• Aggressive deployment timeline (120 days)• Implement voice path access to selective router / 911 tandem
• Implement data path access to ALI
• Establish real time update of regional ALI
• Timely provisioning of ESRN and ESQK numbers
• Shell record creation by 9-1-1 System Service Providers
• ALI updates by System Service Providers and Vendors
• Voice trunk flow and ALI data delivery inter-opt testing
• Delivery of “Go-Live” notifications
• Vonage “Standard Operating Procedures (SOPs)” for ongoing communications and problem resolution
• Vonage NOC, 24x7x365 Access and Safety Net Call Center
• Misrouted Call Procedure
Vonage and VoIP E9-1-1 Needs and Concerns
• Access to Selective Router / 9-1-1 Tandem for voice trunk termination
• Identification and Resolution of PSAP exceptions
• Ability to acquire and provision ESQK pools, p-ANI and other 9-1-1 elements
• MSAG data access for address validation
• Misrouting of Calls and Call Center Needs
• Real time update access to ALI database through wireless-like methods• ALI Steering
• PAM Interface (wireless methods)
• Other industry recognized standards
• State Updates and Leadership• Non-Discriminatory Access
• Support and reinforce leadership (WiCAPs 1999 & ENHANCE 911 Act of 2004)
• Statutes, laws and liability parity
• E9-1-1 advancements (statewide networks, mapping and addressing)
• Shared consumer awareness and education
Vonage’s E9-1-1 Concerns:
• ILEC Roles 9-1-1 System Service Provider
• ESQK, p-ANI Access
• Shell Records
• Uniformed record to pull information off the router, similar to wireless;
• Uniformed formast (PSAP customer)
• Vonage is requesting set of ESQK’s (p-ANI) for VoIP
• Limitations given current system, characters, etc.
• Concerns
• Timely and Non-Discriminatory Access
• MSAG Validation
• VoIP ESN?
• Wireless model;
• Integration with CAD systems and other PSAP methods may vary
Vonage E9-1-1 Deployment
• 9-1-1 Outreach, Deployment and Implementation
• Sharing of relevant 9-1-1 data
• Selective Router (SR) access points
• PSAP jurisdictional boundaries
• Vonage Deployment Kit Follow Up
• Communicating the VoIP Solution
• Sharing rollout plans
• Targeting Vonage Footprint
• Testing capabilities
• Vonage will provide ANI and ALI
• ANI will be populated by Vonage
• ALI is provided through customer provisioning process
• Vonage’s goal and long term priorities include MSAG validation
Keys to Success: Vonage E9-1-1 Deployment
• Communication, Cooperation and Coordination
• Vonage is a 9-1-1 partner
• Ensuring and requesting that IP providers have equal and immediate access to the native 9-1-1 system through Selective Routers and other native 9-1-1 methods
• Sharing any special addressing requirements (p-ANI) that we need to be aware of for MSAG validation
• Assigning appropriate 9-1-1 staff contacts and project managers for IP implementation (technical, operations and policy)
• Operations issues are on-going partnership and require all levels of leadership (national, state and local)
www.vonage.com/PSAPcenter
Click to edit Master title style
Click to edit Master subtitle style
Intrado © 2005
VoIP Implementation:A View from Above
Monica A. MaricsMonica A. Marics
October 2005October 2005
Intrado © 2005
VoIP E9-1-1
Successful implementation is a partnership
VoIP ServiceProvider
9-1-1ServiceProvider
VoIP9-1-1
Provider
Caller&
CPEPSAP
Intrado © 2005
VoIP E9-1-1
From 50,000 feet– Where is the caller?– Which PSAP should receive the call?– How to get the call to the PSAP?– What information to deliver with the call?
Intrado © 2005
Intrado © 2005
Where is the Caller?
20,000 foot view– Caller provides location to VoIP Service Provider
(VSP) during provisioning process, or– Location provided concurrent with 9-1-1 call
request
5,000 foot view– Location Information Server (LIS)– CPE solutions – GPS, RF, etc.– Network solutions – Jacks, Access Points, etc.
Intrado © 2005
Intrado © 2005
Which PSAP should receive the call?
20,000 foot view– PSAP Boundaries– Wireline versus Wireless PSAPs
5,000 foot view– ESN Boundaries for Police, Fire, Ambulance– Boundary maintenance and local government
contacts– Business rules per PSAP
Intrado © 2005
Intrado © 2005
How to get the call to the PSAP?
20,000 foot view– Routing instructions for call (ESRN, ESQK)– Selective Router serving PSAP– Physical access to the Selective Router– Provisioning of Selective Router
Intrado © 2005
Intrado © 2005
How to get the call to the PSAP?
5,000 foot view– ESRNs
• Assignment of ESRNs by VoIP Service Provider (VSP) or VoIP Positioning Center (VPC)
• Assignment at PSAP or ESN boundary– Selective Router connectivity
• Direct connection to Selective Router• Connectivity via 3rd party agreement• Gateway access to Selective Router network
– Provisioning at Selective Router• Shell records• Trunk groups• Default routing• ESNs
Intrado © 2005
Intrado © 2005
What information to deliver with the call?
20,000 foot view– Call Back Number (CBN)– Automatic Location Identification (ALI)
5,000 foot view– Address type, Civic or MSAG– Address origin, User or CPE or Network– Address accuracy, point or WiFi range– X,Y coordinates
Intrado © 2005
Intrado © 2005
Coming in for a Landing
VoIP 9-1-1 is complicated– More than Wireline or Wireless (1+1=3)– “The Devil is in the Details!”
Solutions exist– Consistent with existing FCC Order requirements– Native 9-1-1 network call delivery– MSAG address and call back number to PSAP– Limit impact to public safety process and
proceduresIntrado © 2005
Intrado © 2005
Intrado Solution
Intrado © 2005
Intrado © 2005
Thank You
Questions?
Contact Information– Monica A. Marics
V.P. Product ManagementIntrado [email protected]
Intrado © 2005
Satisfying 911 in a VoIP World
© Siemens 25
Core Components of 911 Emergency Calling
1. Identify Emergency Call – different markets around the world have different identifiers for Emergency calls
2. Basic 911- Route the Emergency Call to the appropriate Public Safety Answering Point (PSAP) for current caller location
Straight forward for Fixed line locations
Much more complicated for Mobile and Nomadic users
ATIS / NENA requirements
Apply correct QoS to insure call pathways exist
3. E911- Deliver caller location with full support of Regulatory requirements (e.g. – Operator Ringback with B-party call control in selected markets)
© Siemens 26
Different business and network models for supplying 911 to stationary subscribers
• Carriers have choices regarding support of 911 requirements
• Own the responsibility Emergency Call routing
CAS/SS7 trunking off the Media Gateway to Tandem switch to PSAP.
• Outsource the PSTN interwork responsibility by using 911 business partners (e.g. CLEC’s)
Use SIP Peering or ISUP connectivity to partner who then routes and terminates emergency call to the PSTN
© Siemens 27
QoS IP
Network
E911 – Carrier Owns the Responsibility
SCPLNPLegacy AIN
800SS7 STP
IP Trunk Gateway
H.248,MGCPTGCP
Softswitch
AccessGateway
H.248
IMT orMF
SS7
SIP users
SIP
SIPMGCPNCS
DSLAMCMTS
IADMTA
Consumer / Small Business
ALI = Automatic Location IdentifierPSAP = Public Safety Answering Point, via an EO and E911 Tandem
ALI
Routes and Trunk seizure can be prioritized if the TGRP ES COS is activated
Subscriber Call requests can be
processed as priority if ESP is
activated
Access Tandem
PSAP
© Siemens 28
QoS IP
Network
E911 – Carrier Outsources the Responsibility
SIP
Softswitch
AccessGateway
H.248
PSAP
SIP users
SIP
SIPMGCPNCS
DSLAMCMTS
IADMTA
Consumer / Small Business
Subscriber Call requests can be
processed as priority if ESP is
activated
911 Business Partner
Access Tandem
© Siemens 29
Summary
• VoIP B-911 & E-911 for VoIP fixed Line deployed worldwide today
• Mobile & Nomadic E911 planned according to ATIS / NENA I2 & I3 requirements
• Location determinationMobile UTDOA ( Uplink Time Difference Of Arrival ), WA-GPS
Nomadic GPS , DHCP : geo + civic
Rollout & Business ModelBuild own network Outsourced Charging models
© Siemens 30
Satisfying 911 in VoIP World
“Thank You For Your Attendance”
Visit us at Siemens Booth # 211 for further info.
Contact : Peter Hage , Solution Management [email protected]: (978)-923-3354
VoIP E9-1-1
The 9-1-1 Service Provider’s Perspective
Maureen NapolitanoVerizon
Director National E9-1-1October 25,2005
TELECOM ‘05
How Will E9-1-1 be cared for?
FCC issued mandate on E9-1-1By 11/28/05, VoIP providers must deliver ANI / ALI to PSAPs connected to an E9-1-1 selective routerOrder issued in 7/05 . . . Aggressive timeline to Provision . . . 4 Months!!Did not specify that address has to be MSAG valid . . Instructed VoIPproviders to deliver ‘registered location’ as supplied by the customerUnlike wireless, PSAPs do NOT request service . . Must be ready to accept!
VSPs have contracted with 3rd party database providers and CLECs to deliver E9-1-1 service
3rd party providers will provide ALI information and determine routing instructions
Provide VPC functionalityExisting CLEC trunks may be used to transport call to our E9-1-1 selective routers or direct trunking to the 9-1-1 Selective Routers2,000 PSAPs connected to about 150 E9-1-1 selective routers in VZ footprint!
How Will E9-1-1 be cared for?
Cable companies (and other CLECs) are delivering VoIP and traditional landline calls over same trunks because most of their customers are ‘static’ users
No distinction made on type of call
Assign pANIs upon request from 3rd party providerWill use ‘211’ compared to ‘511’ for wireless
Create VoIP MSAG shell record to allow 3rd party to load pANIsESN is critical element in establishing this recordPSAPs must make decision on what trunks to accept calls (landline or wireless or new)Outreach campaign underwayBuild ‘steering table’ to direct ALI query to 3rd party
Activate PSAP steering
Resolve testing/implementation issues with appropriate parties
Educate 3rd party providers/VoIP providers on need for PSAP process to transmit ‘ALI discrepancies’ and ‘No Record Found’ conditions
VZ Activities to Meet Deadline
Current DeploymentsNYC since 7/7/05
Working Collaboratively with Intrado, HBF + TCS
Testing In Progress Many VZ StatesMD, PA, VA, MA
State Oversight and GuidanceTexasCalifornia
VoIP Deployment-In Progress
“ Well we have till 11/28 !!!!”
Address ValidationPostal vs. MSAGCustomer Understanding of Where They AreWhose Problem IS It Anyway ???
Nomadic Knowledge
Interactive Presentation of Alias, Descriptive Addressing
Availability of Responding Agency InformationPolice, Fire+EMS
Post Implementation Root Cause
Challenges Ahead
ESIF is the primary venue for the telecommunications industry, public safety and other stakeholders to generate and refine both technical and operational interconnection issues to ensure that life-saving E9-1-1 service is available for everyone in all situations.
ESIF enables many different telecommunications entities to fully cooperate and interconnect with each other to determine the best practices and solutions necessary to effectively and promptly deploy E9-1-1 services.
ATIS/ESIF Emergency Services Interconnection Forum
ESIF Industry Participation
Andrew CorporationAssociation of Public Safety Commissions
Officials (APCO)AT&T CommunicationsAT&T WirelessBellSouthBexar Metro 9-1-1 DistrictCingular Wireless HBF GroupIntradoiXP CorporationLucent TechnologiesMarconi CommunicationsMid-America Regional Council (MARC)National Emergency Number Association
(NENA)NeuStarNextel CommunicationsNortel NetworksOnStar Division (GM)Polaris Wireless
QualCommRural Cellular AssociationSBCOpenWaveSprint PCSState of Vermont Enhanced 9-1-1 BoardState of WashingtonT-Mobile USATarrant County 9-1-1 DistrictTeleCommunication SystemsTechnoCom CorporationTechnology Staffing Resources (TSRI)TelcordiaTruePositionVerizonVerizon WirelessVirginia Information Technologies Agency
ESIF Successes
PSAP Readiness-Issue 12Developed to supply PSAPs with a method to verify readiness and provide carriers with complete information to speed the Wireless PHASE 1 + 2 implementation process.
Wireless 9-1-1 Emergency Information Request Fax-Issue 23Created in order to establish an acceptable generic national procedure for wireless carriers (network and resale providers) to provide current/prior customer information to PSAPs in emergency situations and/or cases of fraudulent use of 9-1-1.
ESIF Successes
Wireless Phase II test Methodology-Issue 22The FCC has established accuracy requirements for network and handset based location solutions for Enhanced 9-1-1 emergency call services (found in the Commission’s Third Report and Order, adopted September 15, 1999).
ESIF identified the need for industry-accepted requirements for testing the accuracy performance of Wireless E-9-1-1 Phase II systems. This document provides a common frame of reference that individual stakeholders can use to validate the accuracy methodology of 9-1-1 location technologies.
ESIF Work In Progress
Emergency Services Messaging Interface Task ForceProtocol and network architecture between the PSAP and Emergency Services Network has not substantially changed since its introduction approximately 30 years ago.
Barrier to advancing emergency services and evolving the role ofthe 9-1-1 PSAP call taker.
Define a new messaging and interaction protocol between PSAPsand Emergency Services Networks that goes significantly beyond the paradigms that exist to provide those services today (To be crafted as an American National Standard).
ESIF Work In Progress
IP Coordination AD HOC Sub CommitteeEstablish a close working relationship with the NENA VoIP/PacketTechnical CommitteeDevelop a process to review the work being developed in the NENA VoIP/Packet Technical CommitteeSubmit consensus documents and contributions to the NENA VoIP/Packet Technical Committee, and/or other NENA Technical Committees.Assist the NENA VoIP/Packet Technical Committee in adapting the results into a formal standards requirement document (SRD) for submission through ESIF for end-to-end, ANSI standards development and implementation.
Conclusion
9-1-1 is THE most important number a Citizen can Dial
ATIS and its ESIF share the FCC’s focus on the need for cooperative measures to deploy and
evolve E9-1-1 services and systems.