1 / 13

Telcordia View of NENA Progress on VoIP Migration Plan

An SAIC Company. TR41.4-04-08-019L. Telcordia View of NENA Progress on VoIP Migration Plan. Provided as input to TIA TR41.4 preliminary to work on PN 3-0172 August 10, 2004 Washington, DC. Telcordia Contacts: Nadine Abbott (732) 699-6901 nabbott@telcordia.com.

nikkos
Download Presentation

Telcordia View of NENA Progress on VoIP Migration Plan

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. An SAIC Company TR41.4-04-08-019L Telcordia View of NENA Progress on VoIP Migration Plan Provided as input to TIA TR41.4 preliminary to work on PN 3-0172 August 10, 2004 Washington, DC Telcordia Contacts:Nadine Abbott (732) 699-6901 nabbott@telcordia.com

  2. Overview of Current Work in NENA & IETF Long-Term Definition • Long-Term Definition WG • Phase “i3” solution – includes support of VoIP PSAPs (end-to-end IP) • Most of work being done in IETF & socialized in NENA • IETF 60 Meeting – San Diego, August 2-6, 2004 • IETF 9-1-1 Related Documents • Location • RFC 3825, Dynamic Host Configuration Protocol Option for Coordinate-based Location Configuration Information, J. Polk, J. Schnitzlein, M. Linsner, July 2004 • Specifies geo Location Object and method for download to UA via DHCP • Internet draft, DHCP Option for Civil Addresses, H. Schulzrinne, February 8, 2004, draft-ietf-geopriv-dhcp-civil-01 • Status: WG last call • Specifies civil Location Object and method for download to UA via DHCP • Internet draft, A Presence-based GEOPRIV Location Object Format, J. Peterson, May 2004, draft-ietf-geopriv-pidf-lo-02 • Status: IETF last call • Means to convey user-specified privacy policy and Location Object (civil and geo)

  3. Overview of Current Work in NENA & IETF Long-Term Definition • IETF documents • Architecture and Routing • Emergency Services for Internet Telephony Systems, H. Schulzrinne, B. Rosen, July 18, 2004, draft-schulzrinne-sipping-emergency-arch-01 • Status: Internet draft proposed by authors • Proposes a SIP-based emergency services architecture. • Internet-draft, Emergency Call Information in the Domain Name System, B. Rosen, July 16, 2004, draft-rosen-dns-sos-01.txt • Status: Internet draft proposed by author • Proposes a DNS-based mechanism to look up emergency calling URIs and related emergency information from a known civic location in a specific form • Requirements for Session Initiation Protocol Location Conveyance, J. Polk, B. Rosen, July 19, 2004, draft-ietf-sipping-location-requirements-01.txt • Status: Internet draft proposed by SIPPING WG • Proposes framework and requirements for using SIP [RFC 3261] to convey user location information from a SIP UA to another SIP entity. Considers end-to-end cases and cases of location-based routing by intermediaries.

  4. Overview of Current Work in NENAMigration Plan • VoIP Migratory WG (team leader Mark Lewis, Nortel Networks) • Phase “i1” solution -- existing VoIP interconnection—routing to correct PSAP, but no location information—acknowledgement of existing implementations. • Phase “i2” solution – VoIP interconnection with existing E9-1-1 network and data base infrastructure • NENA standard being drafted to describe interconnection architecture, new functions, and interfaces. • Final draft planned for end of year 2004. • Overview of i2 Solution • SIP to be used for interconnection with E9-1-1 services • Based on wireless interconnection model • Both civil address and geo-location Location Objects (LOs) to be supported • Several new IP domain elements defined to assist in location-based routing, and interworking with 9-1-1 data bases for delivery of location information to the PSAP

  5. New IP Elements for Call Routing in I2 • Emergency Services Gateway (ESGW) – • ESGW provides interconnection point between the VoIP domain and existing Emergency Services Provider Network. • The ESGW provides protocol interworking between Session Initiated Protocol (SIP) and call setup signaling to the E9-1-1 tandem (Multi-Frequency [MF] or Signaling System #7 [SS7]). • VoIP Positioning Center (VPC) – • Receives and stores information about an emergency call, including callback number information and location information. • May query LIS with LocationKey (LK) to obtain Location Object (LO) • Based on LO, VPC determines Emergency Services Routing Number (ESRN), and allocates an Emergency Services Query Key (ESQK) associated with the VPC, the call instance and the Emergency Service Zone (ESZ) from which the call originated. Also Contingency Routing Number (CRN) for alternate routing. • Responds to subsequent queries for location information for that call instance from the PSAP via its serving ALI database, using the allocated ESQK.

  6. DNS VPC ESZ RDB DHCP LIS SRDB MSAG ALI DB Routing Query & Direct Routing by Call Server Emergency Services Provider Network VoIP domain Call server E9-1-1 Selective Router 7. INVITE (ESRN, ESQK, [CRN]) 8. Call Setup (Cd=911, Cg=ESQK) PSAP V4 ESGW 9. ESQK V1 2. Call-Init LO or LK 16b. Call Release 15. Release 14. Disconnect 3. Query (LO or LK, CallBack, Provider info) 16a. Call Release User Agent 10. ESQK V2 6. Response (ESRN, ESQK, CRN) 13. CBN, LO, other 11. ESPOSREQ(ESQK) 1. LO or LK V0 12. esposreq (CBN, LO, other) 4. Request (LK)5. Response (LO) V3 3a. NSLU(LIS-ID) • Circuit ID • LO or LK

  7. Overview of Current Work in NENAVoIP Location WG • VoIP Location WG (Nadine Abbott, team leader) • Input to VMWG and LTD WG in these areas: • Determination of 9-1-1 related data elements in addition to basic location • MSAG Validation of civil address LOs • Location Determination recommendations for residential IP markets

  8. DNS Internet VDB VDB VDB DHCP LIS LIS MSAG MSAG MSAG MSAG MSAG MSAG Stand- alone SAG Stand- alone SAG Stand- alone SAG Regional MSAG Validation Database/Service Architecture Emergency Services Provider Network VoIP domain DBMS • • • Periodic updates DBMS A. Validation query (LO) B. Validation response (valid or error [with diagnostic])

  9. DNS DNS DNS DNS Internet VDB VDB VDB DHCP LIS LIS MSAG MSAG MSAG MSAG MSAG MSAG Stand- alone SAG Stand- alone SAG Stand- alone SAG Regional MSAG Validation Database/Service + DNS Query Architecture VoIP domain Emergency Services Provider Network Endpoint/ User Agent DBMS • • • C. NLSU (LO) Periodic updates D. NLSU response (valid or error [pass/fail]) DBMS A. Validation query (LO) B. Validation response (valid or error [with diagnostic])

  10. Location Determination - 2 Basic Approaches • Direct Download Method • Location Object (LO) downloaded to endpoint IP Device [or entered by user in same] and stored in the endpoint IP Device. • This is the method supported by IETF. • Query Method • LocationKey (LK) downloaded to in IP Device. Identifiers: • Client ID (to identify instance of LO) • Location Information Server (LIS) ID • LIS signature • Various entities can query for the LO, e.g., • IP Device can query LIS directly (being discussed in TR41.4) • IP Device can pass identifiers to Call Server, which queries LIS for LO on behalf of IP Device • IP Device passes identifiers to Call Server, which passes IP Device and LIS-ID to VPC. VPC queries LIS for LO. • Download and query protocols to be defined. • Must include information to guarantee privacy of location. (e.g., certificates to authenticate the querying party)

  11. DNS VPC DHCP LIS SRDB ALI DB Location Downloaded to Endpoint & Stored Emergency Services Provider Network VoIP domain Routing Proxy Call server E9-1-1 S/R PSAP ESGW User Agent 1. DHCPReq 4. DCHPAck [LO ] V0 2. tbd 3. tbd [LO ]

  12. DNS VPC DHCP LIS SRDB ALI DB VPC Queries LIS for Location Information Emergency Services Provider Network VoIP domain Routing Proxy Call server V5 E9-1-1 S/R PSAP 6. Invite ESGW 5. Call-Init {LK) V2 7. Query ([LK other…) V1 User Agent 1. DHCPReq 4. DCHPAck [LocationKey: {Client ID, LIS-ID, SLIS}] 8. Request (LK)9. Response (LO) V0 V3 2. tbd 3. tbd [Client ID, LIS-ID , SLIS]

  13. Impact on TR41.4 Project 3-0172 • A number of areas impinge on Location Information Server (LIS) Interfaces to be defined in TR41.4 Project 4-0172 • NENA looking to this project for definition of LIS to DHCP interface • NENA will be defining • LIS to VPC interface • LIS to Call Server and other local elements beyond scope of NENA

More Related