Alternatives for Providing Routing and Location Information ...
Upcoming SlideShare
Loading in...5
×
 

Alternatives for Providing Routing and Location Information ...

on

  • 644 views

 

Statistics

Views

Total Views
644
Views on SlideShare
644
Embed Views
0

Actions

Likes
0
Downloads
7
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • Assume Local LIS sends address information to Network LIS for validation against MSAG. Network LIS has access to MSAG data for address validation and to obtain ESN. Network LIS may assist in assignment/administration of Address Token. Network LIS stores Address Token representing an ERL with its associated ESN and ALI data. For valid addresses, Network LIS returns Address Token to Local LIS Address validation requests Requested by VoIP enterprise customer or VoIP Service Provider to validate their address information against the MSAG. It is assumed that the ALI information for an ERL that is provided in the validation request is “partial” (including only data provider identification, I.e., carrier, and MSAG-validatable street address information, not a TN). Supplementary “location field details” information like “2 nd floor, west wing” are provided separately. Network LIS may be configured to administer, allocate and return an “Address Token” to the Local LIS. These address validation requests may be sent individually or in a batch form. Address re-validation requests. VoIP SP or Enterprise customer’s Local LIS may request periodic “re-validation” of the address information, e.g., to accommodate infrequent changes in MSAG data. In this case, it is assumed that there is no need for a new [set of] Address Token[s] to be assigned for an ERL, although the association with an ESN MAY change in the Network LIS and/or SRDB records as a result of an MSAG change. Therefore, the flow illustrates that revalidation does not result in the return of a new Address Token to the Local LIS. Possible future enhancement for pure VoIP solutions might be to provide routing information from Network LIS function to Local LIS instead of Address Token in response.
  • After successful address validation, the Network LIS may push routing and location information to the SRDB and ALI DBs for creation of shell records that can be used later to support moves and changes or real-time updates. These may be “complete” records, or they may be “shell records” associated with an Address Token which can be used, with additional details provided during real-time processing to create temporary records for a CBN=TN. This is equivalent or supplemental to initial service order creation processes. This information must be sent from the Network LIS if the Network LIS is tasked with administering/allocating Address Tokens. The update methods described in subsequent flows describe how this information is accessed, modified, or used to create records that provide a temporary association between a particular caller (identified by a CBN) and the routing information populated in the SRDB and the ALI information populated in the ALI DB during the course of address validation or as the result of queries to the Network LIS.
  • Assume that: SRDB and ALI DB are populated with a shell record for each IP enterprise CBN that indicates the Network LIS to be queried. During address validation, the Network LIS stores the Address Token representing an ERL, along with its associated ESN and also its validated ALI (if not sent earlier to ALI DB for shell record creation). As VoIP devices are moved, the Local LIS sends updates to the Network LIS. When a location update is received from the Local LIS, the Network LIS associates the indicated CBN with the ESN and ALI of the ERL identified by the Address Token received in the update. Emergency call origination. CBN is key to routing and location information. SRDB uses CBN to query the Network LIS for routing information (ESN) associated with that CBN ALI DB uses CBN to query the Network LIS for the ALI associated with that CBN.
  • Assume that the SRDB is pre-populated with an association between ELIN/CGL and ESN and that the ALI DB is pre-populated with an association between the ELIN and ALI. It is assumed these data elements are pre-populated during the service order process or during the address validation process by the Network LIS. Assume that the Local CMF has the required signaling protocol support to signal both the CBN and the ELIN to the VoIP gateway. The VoIP Gateway will have to support a GR-3023 type interface to support the transport of both the CBN and the ELIN/CGL to the EO. The EO will have to support an interface to the E9-1-1 tandem that is capable of transporting both CBN and ELIN/GDL information. As VoIP devices are moved, the Local LIS tracks location. On Emergency call origination, Local LIS provides the Local CMF with ELIN/CGL information (optional, if Local LIS has not already provided location information directly to IP device, e.g., using DHCP query approach in IETF) Local CMF communicates both CBN and ELIN/CGL to the VoIP gateway VoIP Gateway passes this information to the EO or E9-1-1 Tandem. (If present, EO sends both CBN and ELIN/GDL to the E9-1-1 tandem using SS7, not shown) ELIN/CGL is key to routing and location information. E9-1-1 tandem uses ELIN/CGL to query SRDB PSAP uses CBN & ELIN to query ALI DB
  • CGL assumes coordinate based routing? Probably too time-consuming to calculate ESN based on civic location? As an alternative, perhaps routing information could be provided to the Local LIS (and then to IP devices and/or CMFs) during address validation?

Alternatives for Providing Routing and Location Information ... Alternatives for Providing Routing and Location Information ... Presentation Transcript

  • Alternatives for Providing Routing and Location Information to support Emergency Calling from IP Enterprises Prepared For: NENA VoIP Meeting on behalf of SBC, BellSouth, Qwest July 29, 2003 Telcordia Contacts: Nadine Abbott (732) 758-5257 nabbott @telcordia.com An SAIC Company Telcordia Technologies – Confidential Restricted Access This document contains proprietary information that shall be distributed, routed or made available only within Telcordia Technologies, SBC, and BellSouth, and Qwest except with written permission of Telcordia Technologies.
  • Purpose and Objectives
    • Provide an overview of a possible evolution for supporting location information for emergency calls originated from IP networks.
      • High-level information flows
    • Discussion to identify path forward
      • Identify and solicit comments on new interface functionality that needs to be supported.
  • Terms
    • ALI = Automatic Location Identification (including street address, detailed location, etc.)
    • CBN = Call Back Number (a dialable NANP number, or Telephone Number [TN] assigned to the IP Enterprise)
    • CGL = Calling Geodetic Location (lat/long) as defined in ANSI T1.628 for ISDN and for SS7.
    • CMF = Call Management Function (generic term used to represent various VoIP architecture functions that may be used to support call management, e.g., H.323 Gatekeepers, SIP Servers, Megaco Call Agents, etc.)
    • LIS = Location Information Server (or application/function)
    • ELIN = Emergency Location Identification Number = dialable NANP number used to identify an Emergency Response Location on a customer’s premises; usually allocated from among the customer’s DID numbers.
    • ERL = Emergency Response Location = a specific geographic area on a customer’s premises with a unique association to a PSAP ESN.
  • Terms (cont.)
    • “ Address Token” = an identifier assigned/administered by the Network LIS and associated with a particular ERL. (This term differs from ELIN in that it need not be a dialable NANP number.)
    • ESN = Emergency Service Number = an up to 5-digit identifier uniquely associated with an ESZ and a PSAP DN.
    • ESZ = Emergency Service Zone = a specific geographic area with a unique association with police, fire, and emergency medical response agencies.
    • “ Shell record” = A record that includes some, but not all of the required information for processing an emergency call. Some examples for various scenarios:
      • An ALI DB shell record for an ERL might include an Address Token identification, information about the carrier, the IP enterprise customer, and MSAG validated address information for the ERL, but not a Telephone Number. This shell record might be used to create temporary records for a CBN in real time. May be supplemented with additional location details in real time during a call, or may be used to create initial temporary records for a CBN.
      • An SRDB shell record for a TN might include a default ESN or an identifier for a Network LIS to be queried for routing information.
  • Terms & Abbreviations (cont.)
    • ALI DB – Automatic Location Identification Data Base
    • DBMS – Data Base Management System
    • LIS – Location Information Server
    • PS-ALI – Private Switch ALI
    • PSAP – Public Safety Answering Point
    • SRDB – Selective Routing Data Base
    • VoIP – Voice over IP
    • CAS – Call Associated Signaling
    • NCAS – Non-Call Associated Signaling
    • SIP – Session Initiation Protocol
  • Assumptions
    • Assume that the Local LIS will perform address validation for all of its ERLs before implementing emergency calling from VoIP devices.
    • Assume that the Local LIS will periodically request re-validation of its ERL address information, scheduled as required to reflect expected frequency of changes in MSAG data.
    • Assume that Local LIS will be able to track locations of the served VoIP devices and determine when a device has moved between ERLs (for NCAS-like solutions-see slide 13).
    • Assume that the Local LIS will able to accept and store Address Tokens received from the Network LIS, and associate them with the appropriate ERL and address information.
  • Assumptions
    • Assume that for scenarios when the Network LIS is in the critical path for real-time processing, it will be designed so as to have the same availability, reliability, and accessibility characteristics as the SRDB and ALI DBs.
    • Assume that at a minimum, for all alternatives, new connectivity and an interface between the Local LIS and the Network LIS will need to be supported.
      • For some scenarios, connectivity may be established only as needed for address validation
      • In other scenarios, interface also used to push location information into the E9-1-1 network and/or data bases.
  • Address Validation & Re-Validation LAN Originating Network E9-1-1 Tandem Network LIS VoIP device Local LIS Local VoIP CMF Address Validation Request (ALI) Address Validation Response (success; Address Token* ) Address Re-Validation Request (ALI, Address Token) Address Re-Validation Response (success) • • • • • • Notification of MSAG change Address changes MSAG DBMS ALI ESN or equiv. LIS = Location Information Server CMF = Call Management Function e.g., H.323 Gatekeeper, SIP Server, Call Agent * Consider also including routing information equivalent to ESN – what?
  • Possible Ways to Leverage IETF DHCP and Geopriv WG Solutions (1) Call Associated Soln. VoIP device Local LIS Network LIS Address Validation DHCP Server DHCP query DHCP query [ + Circuit ID ] Location query: [IP address, Circuit ID] [IP address, location object ] [location object] e.g., LAN switch VoIP Call Setup [Callback ID, Location Object ] Map Circuit ID to Location Object VoIP Network
  • Example Way to Leverage IETF DHCP and Geopriv WG Solutions (2) – with Transitional Non-Call Associated Solution VoIP device Local LIS Network LIS Address Validation DHCP Server DHCP query DHCP query [ + Circuit ID ] NENA XML near real-time updates of changes (Callback ID, Address Token) Location query: [IP address, Circuit ID] [IP address, location ] [location] e.g., LAN switch VoIP Call Setup [Callback ID] Local VoIP CMF Map Circuit ID to Location Object “ registration” [Callback ID, IP Address] [Callback ID, IP Address]
  • Optional E9-1-1 DB ALI shell record creation; after Address Validation (Re-Validation) for NCAS-Like Transitional Solutions DBMS ALI DB Create Shell Record ( Address Token , ALI) Acknowledgement For all Address Tokens: LAN Originating Network E9-1-1 Tandem Network LIS VoIP device Local LIS Local VoIP CMF
  • (Optional) E9-1-1 DB Initial CBN record creation after Address Validation (or Re-Validation) for NCAS-Like Transitional Solutions Create/Update Response [success] Create/Update Request [ CBN , Address Token, (optional) additional location details] For all Call Back Numbers/IDs (CBNs): LAN Originating Network E9-1-1 Tandem Network LIS VoIP device Local LIS Local VoIP CMF
  • NCAS-Like Transitional Solution IP device gets location Emergency call origination Network LIS SRDB ALI DB PSAP Update Request [ CBN, Address Token, (opt. additional details) ] Update Response (success) VoIP Call setup (Caller ID) Call setup (Caller ID) Call setup ( CBN ) Routing Query ( CBN ) Response (ESN) Call setup ( CBN ) Query ( CBN ) Response (ALI) Routing Query ( CBN ) Response (ESN/PSAP DN) Location Query ( CBN ) Response (CBN, Address Token, ALI details) E9-1-1 Tandem SRDB gets routing information from Network LIS in real time. Assume that shell records for Address Tokens pre-populated in ALI DBs; ALI queries Network LIS using CBN, and retrieves ALI details from Network LIS in real time. LAN VoIP device Local LIS Local VoIP CMF ALI DB SRDB Originating Network
  • CAS-like Solution; CBN & Location Info with Call IP device gets location Emer-gency call origina-tion SRDB ALI DB PSAP Call setup ( Caller ID, opt: ELIN or Location Object ) VoIP Call setup ( CBN & ELIN/ Location Object ) Routing Query ( ELIN/CGL ) Call setup (CBN & ELIN ) Query (CBN, ELIN ) Response (CBN & ALI) Response (ESN or equiv.) api ( Caller ID ) api ( ELIN/ Location Object ) VoIP Gwy GR-3023 ISDN PRI SETUP (CBN & ELIN or CGL ) NOTE: To be specified; may leverage IETF Geopriv & other WG solutions? * Queries assume that ELIN/CGLs pre-populated with ESN in SRDB & location information in ALI DB during service order or by Network LIS during address validation processes. E9-1-1 Tandem VoIP device Local LIS Local VoIP CMF NOTE: Optional query if device doesn’t know location Originating Network
  • Pure VoIP Solution IP device gets location Emer-gency call origina-tion VoIP PSAP VoIP Call setup ( Caller ID, Location Object =lat/long and/or Civic Location ) VoIP Call setup ( Caller ID & Location Object ) VoIP’ Call setup ( Caller ID & Location Object) VoIP’ Call setup ( Caller ID & Location Object ) VoIP Gwy NOTE: To be specified; should leverage IETF Geopriv & other standard WG solutions Selective Routing Function VoIP device Local LIS Local VoIP CMF DHCP NOTE: may not be needed if routing to PSAP determined at originating network? Coordinate-based routing? Impractical to decode civil location for routing. Originating Network VoIP E9-1-1 Network
  • Next Steps
    • Definition of VoIP protocols to carry lat/long and civic location (interworking issues with PSTN for CGL)
      • Leverage IETF Geopriv and DHCP work
    • Specification of Local LIS to Network LIS protocols for address validation and creation/updates (leverage NENA XML library)
    • Specification of DHCP Server to Local LIS function interface
    • Specification of Local LIS function/application
      • Telcordia plans to issue Generic Requirements later this year for some Local LIS applications