Embed Size (px)
Citation preview
What do YOU Really Need to Know?
ESInet
i3PSAP
Next Generation 9-1-1 Call FlowNG9-1-1 Call (i3)
LIS
LVF
ECRF
ESRP
SI
GIS DBMSGIS
GISGIS
CSP
Simplified for presentation
LVF – Location Validation FunctionECRF – Emergency Call Routing Function
CSP– Communications Service Provider
LIS– Location Information ServerESRP– Emergency Services Routing Proxy
SI – Spatial Interface
ESInet
i3PSAP
Next Generation 9-1-1 - Call FlowNG9-1-1 Call (i3)
LIS
LVF
ECRF
ESRP
SI
GIS DBMSGIS
GISGIS
CSP
Simplified for presentation
08-003 v1 Detailed Functional and Interface Specifications for NENA i3 Solution – Stage 3v2 under development
REQ 002NG9-1-1 Data ManagementPublic Review
08-003 v1Detailed Functional and Interface Specifications for NENA i3 Solution
Stage 3
•Describes how NG works after transition◦ Detailed functional and external interfaces to NG9-1-1 functional elements
• Includes gateways for legacy wireline and wireless origination networks
• V2 currently addressing all committee review ◦ Revised Standard will use new NENA numbering schema STA-010
REQ-002 - NG9-1-1 Data Management
•Guidelines for communicating issues or status of various elements
• Issues related to GIS-related errors◦ Minimum report content requirements◦ Timeframe for error resolution timeframe
• Discrepancy Report◦ Gap/Overlap in Boundary Layers
• Performance Statistics◦ GIS Data Provisioning Performance Statistics Report
ESInet
i3PSAP
GIS DataNG9-1-1 Call (i3)
LIS
LVF
ECRF
ESRP
SI
GIS DBMSGIS
GISGIS
CSP
02-014 v1GIS Data Collections and Maintenance Standards
71-501 v1Synchronizing GIS Databases with MSAG and ALI
INF-014Development of Site/Structure Address Point GIS Data for 9-1-1
STA-006Standard for NG9-1-1 GIS Data Model
STA- 004.1-2014Next Generation 9-1-1 (NG9-1-1) United States Civic Location Data Exchange Format (CLDXF) Standard
02-014 v1 GIS Data Collections and Maintenance Standards• Ensure the accuracy and integrity of the GIS data collected and maintained for use in PSAPs and 9-1-1 data bases
• Maintenance issues
• Maintenance across data layers
• GPS equipment recommendations (spatial accuracy)
71-501 v1Synchronization GIS database with - MSAG and ALI
• Informational document
• Ensure attribute accuracy for 9-1-1 functions
• Recommended analysis processes
• Recommended error resolution process
• 98% synchronization between all databases for NG9-1-1 (MSAG, ALI, GIS)
INF-014Development of Site/Structure Address Point GIS Data for
9-1-1
• Workgroup completed – Published 9/30/2015
• Address point placement methodologies for 9-1-1
• Best practices
• Takes into account NG9-1-1 functionality
STA-006NG9-1-1 GIS Data
Model • All Committee review comments
• Support location information conveyed in the PIDF-LO
• Support NG9-1-1 systems, databases, call routing, call handling, and related processes
• Required layers◦ Authoritative Boundary◦ Road Centerline ◦ Emergency Service Boundary(s)◦ PSAP Boundary(s)
• Standardized data fields
STA- 004.1-2014CLDXF Standard
◦ Set of core civic location data elements that support call routing and dispatch.
◦ Profile between PIDF-LO and those same NENA core civic location data elements.
◦ Provides illustrative examples of address parsing.◦ Defines civic location data elements corresponding to the Federal Geographic Data Committee, United States Thoroughfare, Landmark, and Postal Address Data Standard, Document Number FGDC-STD-016-2011 set of data elements
◦ Sponsored by the Urban and Regional Information Systems Association (URISA) and the National Emergency Number Association (NENA).
ESInet
i3PSAP
Provisioning GIS DataNG9-1-1 Call (i3)
LIS
LVF
ECRF
ESRP
SI
GIS DBMSGIS
GISGIS
CSP
STA-005Standards for the Provisioning and Maintenance of GIS data to ECRF/LVF Public Review
SI – Spatial Interface(Formally the Spatial Information Function)
• Provisions Standardized GIS data into the ECRF and LVF
The SI could be◦ Built into a GIS system◦ A stand-alone element with propriety interfaces into GIS systems
Standards for the Provisioning and Maintenance of GIS data to ECRF/LVF STA-005
• Stable Form Notice
• Operational processes and procedures to support i3 ECRF and LVF
• GIS data requirements◦ QA/QC◦ Ownership, sharing and distribution
• Provisioning Standardized GIS data to ECRF/LVF
• Deployment considerations
ESInet
i3PSAP
Policy RoutingESRP checks Policy Routing prior to sending to PSAPNG9-1-1
Call (i3)
LIS
LVF
ECRF
ESRP
SI
GIS DBMSGIS
GISGIS
CSP
STA-003.1.1- 2014NG9-1-1 Policy Routing Rules
INF-011.1- 2014Policy Routing Rules Operations Guide
STA-003.1.1- 2014NG9-1-1 Policy Routing Rules
• Allows a variety of Policy Rules for call routing◦Backup PSAP Overflow Call Queue◦Time of Day Language Off Line Default
INF-011.1- 2014Policy Routing Rules Operations Guide
• Assist 9-1-1 Authorities in development and use of PRR
ESInet
i3PSAP
Additional DataNG9-1-1 Call (i3)
LIS
LVF
ECRF
ESRP
SI
GIS DBMSGIS
GISGIS
CSP
Simplified for presentation
71-001 v1NG9-1-1 Additional Data Standard• Device• Caller• Location
71-001 v1NG9-1-1 Additional Data Standard
• Three types of data◦Device◦Caller◦Location
• Location ◦Accessible existing data◦GIS support data
NG9-1-1 Call Flow Pageant
ACRONYMS!
20
NG9-1-1 & GIS
Border Control Function
(BCF)
Location Information
Server(LIS)
Emergency Services Routing
Proxy(ESRP)
Location Validation Function
(LVF)
PSAP
Emergency Call Routing Function
(ECRF)
Spatial Interface
(SI)
Mapping
Legacy Network Gateway
(LNG)
9-1-1 AuthorityGIS Data
PRF
ESInet
Service Uniform Resource Name
nena:service:sos
Presence Information Data Format – Location Object
<civicAddress xml:lang=”en-US” xmlns=”urn:ietf:params:xml:ns:pidf:geopriv10:civicAddr”>
<country>US</country><A1>TX</A1><A3>Austin</A3><A6>Main</A3><STS>Street</STS><HNO>911</HNO>
</civicAddress>
Location-to-Service Translation
<?xml version="1.0" encoding="UTF-8"?> <findService xmlns="urn:ietf:params:xml:ns:lost1" recursive="true" serviceBoundary="value"> <location id="627b8bf819d0bcd4d" profile="civic"> <civicAddress xmlns="urn:ietf:params:xml:ns:pidf:geopriv10:civicAddr"> <country>US</country> <A1>TX</A1> <A3>Austin</A3> <RD>Main</RD> <STS>Street</STS> <HNO>911</HNO> </civicAddress> </location> <service>urn:service:sos</service> </findService>
Act I: GIS Data Provisioning
• GIS Data is created and maintained at the local level
BCF ESRP
LVF
PSAP
ECRF
Map
Spatial Interface
(SI)
Local Government/ 9-1-1 Authority GIS
Data
SI – Spatial Interface
• Provides an interface between an authoritative copy of GIS data and Functional Elements within the ESInet
• Nearly all location related data is derived from the SI. SI supplies data for the ECRF/LVF and map views for alternate PSAPs
• Provisioned by the 9-1-1 Authority, or other government agencies
Here’s your GIS
Data
Two primary things done by the Spatial Interface:• Projection – WGS 84• Layer replication – WFS + ATOM GeoRSS feed
Act II: Location Validation
Location Information
Server(LIS)
Location Validation Function
(LVF)
Emergency Call Routing
Function (ECRF)
Spatial Interface
(SI) 9-1-1 AuthorityGIS Data
Is this a valid location in GIS? YES or NO
LIS – Location Information Server• Calling devices query the LIS• Civic addresses are validated prior to being
stored in the LIS by the LVF – validated against the GIS
• Returns a PIDF-LO (Presence Information Data Format – Location Object) – can be a civic address or a geo-coordinate
LVF – Location Validation Function• Pre-validation, validates before loading to the LIS
database• Similar to MSAG, verifies that the civic location
matches a known address in the 9-1-1 Authorities service area
• Able to validate to an address, not just address range
• Receives as input: PIDF-LO and service URN – Returns: location validation
• Queried by LoST protocol
Act III: Geospatial Call Routing
Emergency Services
Routing Proxy(ESRP)
Location Validation Function
(LVF)
PSAP
Emergency Call Routing Function
(ECRF)
Spatial Interface(SI)
Mapping
9-1-1 AuthorityGIS Data
Where do I route the call?
Route to PSAP A
ESRP – Emergency Services Routing Proxy• Call routing engine• Closest thing to a selective router in NG9-1-
1• Uses the ECRF(GIS) to choose how to
route a 9-1-1 call
ECRF – Emergency Call Routing Function• Provides GIS based Next Generation call
routing• Replaces legacy selective router databases• Allows for alternate dynamic call routing • Receives as input: PIDF-LO and service
URN– returns –route URI• Queried by LoST protocol
PRF
Discussion – Questions – Concerns
How to Cover Your Attributes
GIS Data Model Issues
GIS Data Stewardship WG
Today
•Background
•Purpose
•Goal
•Topics
GIS and NG9-1-1
•It’s not just about map display anymore
GIS in NG9-1-1 recap•Location Validation
•Geospatial Call Routing
•Confirming/validating emergency caller’s location
•Display emergency caller’s location on a map
•Provide vehicular routing
• Road Centerline - Required
• Emergency Services Boundaries- Required
•Authoritative Boundary- Required
•Address Points – Strongly Recommended
•Optional GIS Dataset for ECRF/LVF – can be useful to particular ECRF/LVF implementations to facilitate the URI mapping of invalid or incomplete civic location
•States or Equivalents – Strongly Recommended
•Counties or Equivalents – Strongly Recommended
•Municipal Boundary – Strongly Recommended
GIS Data provisioned by the Spatial
Interface
NENA GIS Documents
•~20Published GIS related Documents or documents that mention GIS
•Recently Published: Site/Structure Address Point
•4 in Workgroup Development◦ GIS Data Model◦ ECRF/LVF Provisioning of data◦ Version 2 of i3 document
CategoryDoc Number Doc Name Committee Approved Date
DATA STRUCTURES & MANAGEMENT DOCUMENTS (including NG9-1-1)
Legacy02-010 Standard Legacy Data Formats For 9-1-1 Data Exchange GIS Mapping Core Services 3/28/2011
Legacy02-014 GIS Data Collection and Maintenance Standards Core Services 6/17/2007
Legacy
71-501 Synchronizing Geographic Information System Databases with MSAG & ALI Information Document Core Services 9/8/2009
NG9-1-1 NENA-STA-004.1-2014NENA Next Generation United States Civic Location Data
Core Services 3/23/2014
Exchange Format (CLDXF)
NG9-1-1 TRANSITION PLANNING DOCUMENTS
NG9-1-1NENA-INF-008.2-2014 (originally 77-501) NG9-1-1 Transition Plan Considerations Information Document NG Transition Planning 11/20/2013
NEXT GENERATION 9-1-1 (NG9-1-1) DOCUMENTS
NG9-1-108-003 Detailed Functional and Interface Standards for the NENA i3 Solution Interconnection & Security 6/14/2011
NG9-1-108-751 NENA i3 Requirements Document Interconnection & Security 9/28/2006
NG9-1-1
08-752 Location Information to Support IP-Based Emergency Services Requirements Document Interconnection & Security 12/21/2006
NG9-1-1NENA-INF-006.1-2014 NG9-1-1 Planning Guidelines Information Document NG Project Lead Team 1/8/2014
NG9-1-1NENA-INF-009.1-2014 Requirements for a National Forest Guide Information Document Interconnection & Security 8/14/2014
PSAP OPERATIONS - CONTINGENCY PLANNING
Legacy
53-001 Communications Center/PSAP Disaster and Contingency Plans Model Recommendation & Evacuation Checklist PSAP Operations 6/7/2005
PSAP OPERATIONS - STANDARD OPERATING PROCEDURES
Legacy56-007 Pipeline Emergency Operations Standard/Model Recommendation PSAP Operations 11/11/2010
Legacy
56-503 Wide Area / Statewide Emergency Notification Systems Information Document PSAP Operations 6/6/2006
Legacy56-507 Railroad & PSAP Interaction Information Document PSAP Operations 4/28/2009
WIRELESS 9-1-1 INTEGRATION DOCUMENTS
Legacy
57-001 Wireless E9-1-1 Overflow, Default and Diverse Routing Standard & A PSAP Managers’ Guide to GIS & Wireless 9-1-1 PSAP Operations 11/18/2004
Legacy
57-002 E9-1-1 Wireless Maintenance Call Routing & Testing Validation Standard including Call Routing & Testing Validation Worksheet & Sample Non-Disclosure Agreement
PSAP Operations 6/9/2007
Legacy57-501 Wireless Phase I & II Features and Functions Information Document PSAP Operations 1/20/2003
Legacy
57-502 Wireless Phase I/II Planning and Implementation Checklist and Modules Information Document including Service Agreements PSAP Operations 5/24/2004
Legacy
60-601 Model Baseline Guidelines for Drafting Statutes or Rules Associated with Prepaid Wireless Service and 9-1-1 Emergency Service Fees Information Document
Regulatory/ Legislative 9/24/2008
Description of Problem or
Opportunity•The GIS data and functionality requirements for Next Generation 9-1-1 are qualitatively different than those needed for paper maps or for digital map displays. NENA’s current GIS standards document (NENA 02-014 – NENA GIS Data Collection and Maintenance Standards) does not provide sufficient guidance on how to create and maintain GIS data for Next Generation 9-1-1 processes and functionality. While it is likely that NENA 02-014 may be useful for Enhanced 9-1-1 environments, we propose that NENA form a workgroup to develop a new document that focuses on GIS data requirements for Next Generation 9-1-1 and the practices needed to satisfy those requirements.
Expected Outcome /Proposed Solution
•Create a workgroup to develop an informational document that provides guidance on GIS Stewardship with a clear and specific focus on GIS data that will be used by NG9-1-1 Core Services to validate and route 9-1-1 calls.
GIS Data Stewardship
•Deals with establishing requirements and assessing the data fitness for use
•Ensure that data meets process needs
•Ensures data documentation - metadata
Potential Topics to Include
•GIS Database Development
•Quality Assurance/Quality Control
•GIS Data Maintenance and Stewardship
GIS Database Development
GIS Database Development – layers to be provisioned by the Spatial Interface for geospatial call routing and location validation
•Best Management Practices for GIS layer development
•Topological relationships
•Accuracy and Precision recommendations for GIS feature development
•Source data considerations for data development
QA/QC
Quality Assurance/Quality Control
•GIS Data Development and Management
•NG9-1-1 Discrepancy and Error Reporting
GIS Data Maintenance
GIS Data Maintenance and Stewardship
•Jurisdictional boundary concerns and implications
•Completeness and timeliness of data
•Guidelines for gap/overlap detection
•Roadmap for process improvement
Correcting the Gap: The Discrepancies of NG9-1-1 Data Management
NG9-1-1 Discrepancy Report Turn-around Times
Discrepancy Report ResolutionLIS validating records against the Location Validation Function (LVF)
3 Business Days
Spatial Interface (SI) Operator to 9-1-1 Authority on provisioning Geographic Information Systems (GIS) data
3 Business Days
ECRF/LVF Operator to SI Operator on GIS data provisioning 1 Business Day
ECRF/LVF Operator to Discrepancy Report (DR) Subscribers on GIS gaps and overlaps
3 Business Days
NG9-1-1 Discrepancy Report Turn-around Times
Discrepancy Report ResolutionPSAP/Entity to 9-1-1 Authority on misroute to their PSAP/Entity
1 Business Day
PSAP/9-1-1 Authority to the GIS Provider when issues found in the map display
Based on Criticality
Forest Guide Operator to Contributing ECRF Node Operator on provisioning coverage data
3 Business Days
Discrepancy Report Required Content
•Common descriptive elements (aka its “prolog”)◦ Time Stamp of Discrepancy Submittal◦ Discrepancy Report ID◦ Discrepancy reporting agency domain name◦ Discrepancy reporting agent user ID◦ Discrepancy reporting agency contact info◦ Service or Instance in which the discrepancy exists◦ Additional notes/comments◦ Discrepancy Service or Database specifics◦ Reporting Agency’s assessment of severity (as noted in STA-010)
Discrepancy Report Required Content•Additional content about the
discrepancy◦Query that generated the discrepancy◦Full response of the query that generated the discrepancy (Message ID, Result Code, etc.)
◦What the reporting agency thinks is wrong
◦What the reporting agency thinks is the correct response, if available
Example: Service Boundary Gaps and Overlaps
ECRF/LVF Gap/Overlap Discrepancy Report
Example ContentTime Stamp of Discrepancy Submittal 2015-10-05T12:58.03.01+05:00
Discrepancy Report ID a56e556d871
Discrepancy reporting agency domain name N/A – the ECRF/LVF is an element
Discrepancy reporting agent user ID N/A – the ECRF/LVF is an element
Discrepancy reporting agency contact info vCard of contact about this reportService or Instance in which the discrepancy exists ecrf.state.pa.us
Additional notes/comments During GIS data provisioning, the ECRF detected an overlap between Zone 45 and Zone 46.
Discrepancy Service or Database specifics GIS features that overlap including a polygon representation of the overlap
Reporting Agency’s assessment of severity High
ECRF/LVF Gap/Overlap Discrepancy Report
Example ContentQuery that generated the discrepancy N/A – since it occurred during
provisioningFull response of the query that generated the discrepancy
N/A – since it occurred during provisioning
What the reporting agency thinks is wrong
An overlap of 102193.344 square meters exists between urn:nena:service:sos.psap Zone 46 (feature [email protected]) and Zone 45 (feature [email protected])
What the reporting agency thinks is the correct response Eliminate the overlap
Extra Slides that may be used in development discussions
Procedures+ Databases+ Spatial Routing+ i3 Architecture+ ESInet= NG9-1-1
What is Next Generation 9-1-1
OriginatingNetworks
LIS
VoIP
Cellular
PSTN
Enterprise
BCF
ECRF
BCF
ESRP
ESInet
This figure is simplified for illustrative purposes
i3PSAP
E9-1-1Gateway
LegacySelectiveRouter
LegacyPSAP
Gateway
LegacyPSAPsLegacy E9-1-1
Networks
SRGateway
GISLVF
Next Generation 9-1-1
GIS
GIS
GIS
GIS Data ManagementSI
Location + Service Identifier URN
PIDF-LO + URN: urn:service:sos
dial 9-1-1
ESRP
ECRF
VoiceTextVideo
Location + PSAP URI
NG9-1-1 Call flow
1) LIS location sent to ECRF: 354 W 44th St, Houston, TX
2) ECRF finds address point of: 354 W 44th St, Houston, TX
3) ECRF determines Location is within the Houston PSAP4) ECRF sends Houston PSAP URI to the ESRP
psap.houston.tx.us
3
4PIDF-LO + PSAP URI [email protected]
Spatial Interface- SICertain GIS data layers will become the core databases within NG9-1-1
These core GIS data layers will be provisioned into the LVF to provide location validation
These same GIS data layers are also provisioned to the ECRF and routing of 9-1-1
This GIS data layers must meet the highly standardized data requirements and strict data integrity and data quality demands
The Spatial Interface is the NG9-1-1 functional element responsible for validating these needs and the provisioning of the GIS data into the LVF and ECRF
Discrepancy Reporting
LIS – Record invalid against the LIS / SP incorrectly provisioning records
LVF – Validations, partial validation and invalid records by SP
ECRF – Same as LVF / Gaps and Overlaps in provisioned data / garbled queries from ESRP
ESRP – BFC handoff issue, ECRF input / return issues/ PRG issues
PRF – Malformed Policies / Illogical Policies
BCF - invalid, unusual, inconsistent, or improper incoming data
SI – 9-1-1 Authority improperly provisioning data
Discrepancy Reporting – Minimum ContentsTime Stamp of Discrepancy Submittal
Discrepancy Report ID
Discrepancy reporting agency domain name
Discrepancy reporting agent user ID
Discrepancy reporting agency contact info
Additional Information Service or Instance in which the discrepancy exists Discrepancy Service or Database specifics Additional Info Additional notes/comments Query that generated the discrepancy Full response of the query that generated the discrepancy (Message ID, Result Code, etc.) What the reporting agency thinks is wrong What the reporting agency thinks is the correct response, if available
