Bandwidth Ex Parte Addendum M a y 1 0 , 2 0 1 8 Addendum to - PowerPoint PPT Presentation

Bandwidth Ex Parte Addendum M a y 1 0 , 2 0 1 8

Addendum to Bandwidth FCC Meeting on May 2, 2018 In response to staff requests, Bandwidth is providing additional call-flow examples of VOIP 9-1-1 calls into the ECS Proceeding Record. • Please Note: 1) To make the diagrams easier to follow, redundancy has been removed; and 2) these examples are illustrative only. A specific item that Bandwidth was asked to expand upon was the Industry Standards that pertain to various interface points in the end-to-end 9-1-1 calling system. • Sample standards have been identified on the final slide • Referenced standards are representative and not intended to be all-inclusive of all potentially applicable standards or best- practices. 2

“Fixed IVOIP” i2 9-1-1 Service (Enhanced) 1. Provisioning of customer name, telephone number and civic address to BW 2. 9-1-1 call placed from customer’s end-point SERVICE PROVIDER EMERGENCY SERVICES 3. Call delivered to Bandwidth’s redundant Core INFRASTRUCTURE POP’s (redundancy not shown) Communications Bandwidth& 6 4 8 partner(s) 4. Call routers, called a VOIP Position Center Platform 2 networks ESQK and (VPC) at both sites can process the call ESQK and voice 3 5 Selective voice ESGW 911 call VOIP 5. Bandwidth routes the call to the appropriate Customer’s VOIP Router (S/R) Public Safety Position End Point Call 3 redundant Emergency Service Gateway 9 Answering Center Server 7 (VPC) Point (ESGW) with an ESQK that is specific to the (PSAP) ALI “BID” 10 PSAP Location Automatic ESQK 6. The ESGW converts VOIP to TDM and sends Informatio Location n Server the call to the Selective Router (SR) Identification CBN + Address (LIS) CBN + Address (ALI DB) (MSAG Format) 7. SR “dips” the LEC ALI database to obtain the 1 (MSAG format) 11 trunk to route the call to the PSAP Provisioning takes place: TN, 8. The PSAP receives the ESQK, also known as civic address, customer name a “pseudo-ANI or pANI) 9. The PSAP sends the ESQK to the LEC 911 database for the ALI “bid” 10. The LEC ALI database has the ESQK set to “steer” to the Bandwidth LIS to fetch MSAG address and Call Back Number (CBN) 11. MSAG address and CBN (which is the customer’s TN) displayed at PSAP Purple solid line indicates VOIP voice Green solid line indicates TDM voice Orange dotted line indicates address data exchange 3

“Nomadic IVOIP” 9-1-1 Call Flow with “i3 Location Object” The call proceeds as SIP PIDF-Lo through the network, however when connecting to Legacy PSAPs, the ESQK mechanism is still used to route the call SERVICE PROVIDER EMERGENCY SERVICES Core INFRASTRUCTURE Communications Bandwidth& 6 4 8 partner(s) Platform 2 networks ESQK and ESQK and voice 3 5 Selective voice ESGW 911 call VOIP Customer’s VOIP Router (S/R) Public Safety Position End Point Call 3 9 Answering Center Server 7 (VPC) Point (PSAP) 10 ALI “BID” Location Automatic ESQK Informatio Location n Server Identification CBN + Address (LIS) CBN + Address (ALI DB) (MSAG Format) 1 Provisioning for all (MSAG format) 11 valid TNs VOIP Call Server selects separated from all the “Location Object” to valid civic include in the SIP INVITE addresses as PDIF-Lo. Any pre- (Location objects) provisioned “Lo” can be used at call time. While the S/R, ALI and PSAP infrastructure Purple solid line indicates VOIP voice remain “legacy”, the Bandwidth solution Green solid line indicates TDM voice processes the request for address Orange dotted line indicates address data exchange information and Call Back Number using the same i2 process. 4

“Nomadic IVOIP” 9-1-1 with PIDF-Lo to NG9-1-1 The SIP INVITE with PIDF-Lo proceeds through Bandwidth’s network and enters the NG9-1-1 Emergency Services Intranet at designated SBCs (redundancy not shown) SERVICE PROVIDER EMERGENCY INFRASTRUCTURE Bandwidth $ I3 NG9-1-1 Core Services 8 partner(s) 6 networks 4 2 5 Emergency SIP PIDF-Lo Public Safety Services 3 S Answering Routing 911 call VOIP B Customer’s VOIP Point SIP PIDF-Lo Proxy Position C SIP PIDF-Lo End Point Call (PSAP) (ESRP) Center Server (VPC) 7 Location Emergency Informatio Call Routing n Server Function (LIS) 1 (ECRF/LVF) Provisioning for all valid TNs separated from all valid civic addresses (Location objects) 6. The call proceeds through the NG9-1-1 network and is received by the Emergency Service routing Proxy (ESRP). VOIP Call Server selects The ESRP uses the Location Object to query the the “Location Object” to Emergency Call Routing Function for a route to the include in the SIP INVITE destination PSAP. as PDIF-Lo. Any pre- 7. The 9-1-1 call proceeds to the PSAP with full SIP PIDF-Lo provisioned “Lo” can be data including the original TN in the Calling Party Number used at call time. (no ESQK is needed). 8. The PSAP receives the originating TN, the address (Lo) and customer name directly from the SIP messaging. There is 5 no needed dip to an ALI or other ancillary database.

Next Generation “i3:” specification is: SOME EXAMPLE STANDARDS INVOLVED IN 9-1-1 NENA-STA-010.2-2016 (originally 08-003) VOIP call going to “i3” service begins with EMERGENCY INFRASTRUCTURE Bandwidth $ SIP INVITE and Location Object using I3 NG9-1-1 Core Services partner(s) RFC-5139 networks S Emergency SIP PIDF-Lo Redundant #1 B Public Safety Services SIP PIDF-Lo Location C Answering Routing Informatio Point Proxy n Server (PSAP) (ESRP) SERVICE PROVIDER (LIS) VOIP Emergency S Position Call Routing B Center (VPC) Function C (ECRF/LVF) Customer’s 911 call VOIP End Point Call (phone) Server EMERGENCY SERVICES NENA-03-005 January INFRASTRUCTURE Redundant #2 2004 (Original Issue) VOIP Generic Requirements for Position 3 Center an Enhanced 9-1-1 (VPC) ESQK and ESQK and voice “Normal” VOIP call begun Selective ESGW voice Selective Routing Switch Bandwidth $ Router with SIP INVITE (S/R) Public Safety Location Provisioning partner(s) Answering Information networks Point Server Provisioning portals and API’s (PSAP) (LIS) ALI “BID” between a general Service Provider Automatic ESQK and a general VPC provider are Location Identificatio proprietary. CBN + Address n (ALI DB) NENA Standard Data (MSAG Format) CBN + Address (MSAG format) Formats for 9-1-1 Data VOIP call going to “i2” service begins with Exchange & GIS Mapping standard SIP INVITE, no location object. NENA-02-010 Enhanced Wireless 9-1-1 Phase II PN-3-3890-RV2-AD1 formerly called TIA J- NENA Interim VoIP Architecture for Enhanced 9-1-1 STD-036 Services (i2) NENA 08-001, NENA Standard Data Formats for 9 ‑ 1 ‑ 1 Data 6 Exchange & GIS Mapping 015.10-201X (originally 02-010 v9)

7