Transcript TR41.4-04-08-019-L-NENA

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
An SAIC Company
Telcordia Contacts:
Nadine Abbott
(732) 699-6901
[email protected]
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 Coordinatebased 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)
2
NENA VMWG report – nba
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-requirements01.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.
3
NENA VMWG report – nba
Overview of Current Work in NENA
Migration 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
4
NENA VMWG report – nba
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.
5
NENA VMWG report – nba
Routing Query & Direct Routing by Call Server
Emergency Services
Provider Network
VoIP domain
Call
server
7. INVITE
(ESRN, ESQK, [CRN])
V4
ESGW
V1
8. Call Setup
(Cd=911,
Cg=ESQK)
E9-1-1
Selective
Router
PSAP
9. ESQK
2. Call-Init
LO or LK
16b. Call
15. Release
SRDB 14. Disconnect
3. Query (LO or
Release
LK, CallBack,
16a. Call
User
10. ESQK
Provider info)
Release
V2
Agent
6. Response (ESRN,
13. CBN,
ESQK, CRN)
11. ESPOSREQ(ESQK)
1. LO or LK
LO, other
VPC
ALI
V0
12. esposreq
DB
(CBN,
LO,
other)
4. Request (LK)
5. Response (LO)
V3
MSAG
ESZ
LIS
DHCP
RDB
3a. NSLU
a. Circuit ID
(LIS-ID)
b.LO or LK
DNS
6
NENA VMWG report – nba
Overview of Current Work in NENA
VoIP 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
7
NENA VMWG report – nba
Regional MSAG Validation Database/Service
Architecture
Emergency Services
VoIP domain
Provider Network
LIS
DNS
DBMS
Internet
VDB
VDB
LIS
•
•
•
Periodic
updates
MSAG
MSAG
MSAG
DBMS
DHCP
Standalone
StandSAG
alone
SAG
MSAG
MSAG
MSAG
VDB
Standalone
SAG
A. Validation query (LO)
B. Validation response (valid
or error [with diagnostic])
8
NENA VMWG report – nba
Regional MSAG Validation Database/Service +
DNS Query Architecture
VoIP domain
Emergency Services
Provider Network
DNS
LIS
DNS
Internet
Endpoint
/ User
Agent
Standalone
StandSAG
alone
SAG
MSAG
MSAG
MSAG
VDB
DBMS
C. NLSU (LO)
D. NLSU response (valid or
error [pass/fail])
LIS
DHCP
DNS VDB
DNS
VDB
•
•
•
Periodic
updates
MSAG
MSAG
MSAG
Standalone
SAG
DBMS
A. Validation query (LO)
B. Validation response (valid
or error [with diagnostic])
9
NENA VMWG report – nba
Location Determination - 2 Basic Approaches
1. 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.
2. 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)
10
NENA VMWG report – nba
Location Downloaded to Endpoint & Stored
Emergency Services
Provider Network
VoIP domain
Call
server
Routing
Proxy
E9-1-1
S/R
PSAP
ESGW
SRDB
User
Agent
1. DHCPReq
4. DCHPAck
[LO ]
V0
VPC
ALI
DB
LIS
2. tbd
DHCP 3. tbd [LO ]
DNS
11
NENA VMWG report – nba
VPC Queries LIS for Location Information
Emergency Services
Provider Network
VoIP domain
Call
server
Routing
Proxy
V5
E9-1-1
S/R
6. Invite
5. Call-Init
{LK)
PSAP
ESGW
V2
7. Query ([LK other…)
SRDB
V1
User
Agent
1. DHCPReq
4. DCHPAck
V0
[LocationKey:
{Client ID,
LIS-ID,
SLIS}]
8. Request (LK)
9. Response (LO)
VPC
V3
ALI
DB
LIS
2. tbd
3. tbd [Client ID,
DHCP
LIS-ID , SLIS]
DNS
12
NENA VMWG report – nba
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
13
NENA VMWG report – nba