GR 3119 CORE : ISSUE 4

Change History
Generic Requirements Notice Of Disclaimer
List of Figures
List of Tables
Preface
The Telcordia Technologies GR Process
About GR-3119-CORE
Participants in the Development of GR-3119-CORE, Issue 1
Relative Maturity Level
GR-3119-CORE Plans
To Submit Comments
1 Introduction
  1.1 Purpose and Scope
  1.2 Target Audience
  1.3 Assumptions
  1.4 Terminology
  1.5 Requirements Terminology
  1.6 Requirement Labeling Conventions
      1.6.1 Numbering of Requirement and Related Objects
      1.6.2 Requirement, Conditional Requirement, and Objective
            Identification
  1.7 Document Organization
  1.8 Related Telcordia Documents
2 High-Level Description
  2.1 Background - Architectural Overview
      2.1.1 NENA i2 Solution Overview
            2.1.1.1 i2 Solution Architecture Overview
            2.1.1.2 Description of i2 Solution Functional Elements
            2.1.1.3 VoIP i2 Solution Data Elements
      2.1.2 i3 Solution Considerations
  2.2 ERDB Functional Overview (NA)
      2.2.1 ERDB Data Creation/Management
      2.2.2 Emergency Call Routing Query Support
      2.2.3 ERDB Interfaces
      2.2.4 Data Sources and Processes
      2.2.5 Secure Communications
  2.3 E9-1-1 System Service Provider Perspective
  2.4 External Perspectives
      2.4.1 Public Safety Perspective
      2.4.2 VPC Operator Perspective
3 Functional Requirements
  3.1 ERDB Data Organization
      3.1.1 Data Element Definitions
            3.1.1.1 Geographical Information System (GIS) Related
                    Data Features and Attributes
            3.1.1.2 Future Expansion
      3.1.2 Civic Location-Based Routing Information
      3.1.3 Coordinate-Based Routing Information
      3.1.4 ERDB Coverage Area
  3.2 Routing Data Creation/Modification
      3.2.1 Receiving and Processing ESZ Definitions/MSAG Data
            3.2.1.1 Supporting Routing Based on Civic Location
                    (Street Address)
            3.2.1.2 Supporting Routing Based on Geo Location
                    Information
      3.2.2 Receiving and Processing of Associated Routing Data
  3.3 Processing Routing Queries
      3.3.1 Receiving Routing Query from VPC
      3.3.2 Processing Contents of Query
            3.3.2.1 VPC Identifier
            3.3.2.2 Civic Location Information
                    3.3.2.2.1 Determining Emergency Service Routing
                              Number/Name
                    3.3.2.2.2 Determining the Emergency Service Number
                    3.3.2.2.3 Determining the Contingency Routing
                              Number
            3.3.2.3 Geo Location Information
                    3.3.2.3.1 Determining Emergency Service Routing
                              Number/Name
                    3.3.2.3.2 Determining the Emergency Service Number
                    3.3.2.3.3 Contingency Routing Number
      3.3.3 Sending Routing Response to VPC
      3.3.4 Abnormal Events/Errors
4 Signaling Interface Requirements
  4.1 V8 Interface Signaling Requirements - VPC to ERDB
      4.1.1 V8 Interface Messaging Requirements
            4.1.1.1 ERDBRequest Message
      4.1.2 ERDBResponse Message
  4.2 MSAG Update Interface/Process
  4.3 Additional Routing Data Interface/Process
  4.4 Geographical Information System (GIS) Interface
5 Operations, Administration and Maintenance
  5.1 Data Administration
      5.1.1 Provisioning
            5.1.1.1 Configuration Options
            5.1.1.2 Provisioned Data
            5.1.1.3 Access to Routing Database Information
      5.1.2 Data Updates and Audits
  5.2 Maintenance and Testing
      5.2.1 Maintenance
            5.2.1.1 Trouble Detection
            5.2.1.2 Trouble Notification
            5.2.1.3 Trouble Verification
            5.2.1.4 Maintenance Measurements
            5.2.1.5 Testing
6 Performance and Security
  6.1 Performance and Reliability
      6.1.1 Availability
      6.1.2 Query Response Times
  6.2 Capacity
      6.2.1 Processing Capacity
      6.2.2 Data Storage Capacity
  6.3 ERDB Security Considerations
      6.3.1 General Security Requirements
            6.3.1.1 Identification
            6.3.1.2 Security Audit (Log)
            6.3.1.3 Data and System Integrity
      6.3.2 Interface Security
            6.3.2.1 V8 Interface to VPC
Appendix A: References
            A.1 Telcordia GRs
            A.2 National Emergency Number Association Documents
            A.3 Government Publications
            A.4 Industry Standards and Documents
Note
To Contact Telcordia Customer Service or to Order Documents
To Order Documents Online From the Telcordia Information SuperStore
To Order Documents From Within Telcordia (Employees Only)
For New Information on Telcordia Licensed Products
Appendix B: Acronyms
Requirement-Object Index
Figures
Tables

Presents specifications for a new Emergency Service Zone Routing Data Base (ERDB) element used to support location-based routing of VoIP emergency calls to an appropriate interconnection point with the emergency services infrastructure in the NENA i2 Solution. It may be of use to operators and suppliers of ERDB elements in developing and deploying the ERDB, and also to the Public Safety community.