PN 3-0172 – Scope/Issues Discussion TR41.4-04-11-017-LM-PN-3-0172-ScopeIssuesDiscussion
11
An SAIC Company PN 3-0172 – Scope/Issues Discussion TR41.4-04-11-017-LM-PN-3-0172-ScopeIssuesDiscussion Telcordia Contacts: Nadine Abbott (732) 699-6901 [email protected] An SAIC Company Provided as input to TIA TR41.4 preliminary to work on PN 3-0172 November 9, 2004 San Antonio, TX
description
An SAIC Company. PN 3-0172 – Scope/Issues Discussion TR41.4-04-11-017-LM-PN-3-0172-ScopeIssuesDiscussion. Provided as input to TIA TR41.4 preliminary to work on PN 3-0172 November 9, 2004 San Antonio, TX. Telcordia Contacts: Nadine Abbott (732) 699-6901 [email protected]. - PowerPoint PPT Presentation
Transcript of PN 3-0172 – Scope/Issues Discussion TR41.4-04-11-017-LM-PN-3-0172-ScopeIssuesDiscussion
An SAIC Company
PN 3-0172 – Scope/Issues DiscussionTR41.4-04-11-017-LM-PN-3-0172-ScopeIssuesDiscussion
Telcordia Contacts:Nadine Abbott(732) [email protected]
An SAIC Company
Provided as input to TIA TR41.4 preliminary to work on PN 3-0172
November 9, 2004 San Antonio, TX
NENA VMWG report – nba2
Overview of PN-3-0172 Structure
Summary of LIS affecting architectures/scenarios included in TSB-146– Must support civic location (street address) validation– Determining Location
SNMP MIB Network Based (Add?) LLDP assisted DHCP Tracker
– Download location to endpoint DHCP download (Add?) Direct interaction between IP endpoint and LIS (via Call Agent?)
– Support for non-call associated sending of location information (existing PS-ALI interfaces)?
– Support for Call Agent insertion of ELIN or location object in emergency call associated signaling?
NENA VMWG report – nba3
Overview of PN-3-0172 Structure
Interfaces– Ethernet LAN Switch Interfaces– LIS to Ethernet LAN Routers– LIS to DHCP Server– LIS to Call Management/Registration Function– LIS to IP Endpoint Device– Location Validation Interface– Location Creation/Update Interface (PS/ALI)
Possible to reduce the number of scenarios to be supported by LIS Interface standard?
NENA VMWG report – nba4
Civic Location Object Validation
LIS
Enterprise Network Management Workstation
E9-1-1 Location Validation Data Base
civic address
valid / error
NENA VMWG report – nba5
ELIN Location Record Creation/Update
LIS
Enterprise Network Management Workstation
E9-1-1 DBMS
Creation/Update:ELIN & civic address
valid / error
NENA VMWG report – nba6
SNMP Network (Ethernet Switch/Bridge) Based Determination of Location
LIS
Enterprise Network Management Workstation Wiremap: LAN switch/Port ID-
Jack-ERL-Address
Router
LAN Switch
MAC Address & LAN Switch/Port ID
IP Address & MAC Address
Call Management function
IP Device ID/TN’s current IP Address
ELIN/Gateway? Or Location Object?
NENA VMWG report – nba7
Network-Based Method for Location Determination using LLDB?
LIS
Call Management function
Enterprise Network Management Workstation
Wiremap: LAN switch/Port ID-Jack-ERL-Address
IP Device
(IP Device ID?), Chassis ID / Port ID
Location Object and/orELIN & Gateway ID?
NENA VMWG report – nba8
DHCP Tracker Based Location Determination & Download to Endpoint
LIS
DHCP Server
IP Address & Circuit ID
Enterprise Network Management Work Station
Wiremap: Circuit ID-Jack-ERL-Address
Location Object
NENA VMWG report – nba9
Non-Call Associated Upload of Civic Location(SNMP Network Based)
LIS
Call Management function
IP Device ID/TN & current IP Address
Enterprise Network Management Workstation
User data: IP Device ID - Primary TN
E9-1-1 DBMS
Update Primary TN & civic address
IP Device
IP DeviceID,IP Address & MAC Address
Router
LAN Switch
MAC Address & LAN Switch/Port ID
IP Address & MAC Address
NENA VMWG report – nba10
Non-Call Associated Upload of Civic Location (LLDP Assisted)
LIS
Call Management function
IP Device ID/TN & current IP Address
Enterprise Network Management Workstation
Wiremap: LAN switch/Port ID-Jack-ERL-Address
User data: IP Device ID - Primary TN
E9-1-1 DBMS
Update Primary TN & addressIP
Device
(IP Device ID?), Chassis ID / Port ID
Location Object and/orELIN & Gateway ID?
NENA VMWG report – nba11
Support for NENA i2 Solution Migration Plans
Should– Support Sending Location Object with Call– Support location object validation interface
(Optional?) – Support for location key query interface?
