Voice over Internet Protocol (VoIP) Positioning Center (VPC) Generic Requirements
Document Number GR-3118
Issue Number 04
Issue Date Sep 2008
ABSTRACT: Issue 4 of GR-3118, Voice over Internet Protocol (VoIP) Positioning Center (VPC) Generic Requirements, replaces Issue 3.
The National Emergency Number Association (NENA) is in the process of defining solutions that will enable Voice over Internet
Protocol (VoIP) customer-originated emergency calls to be routed via a client company Emergency Services Network to the appropriate
Public Safety Answering Point (PSAP), based on the location from which the call was originated. The VoIP Migratory Working Group (VMWG)
of NENA defined a near-term solution for addressing emergency call originations by VoIP customers, referred to as the i2 Solution. The
NENA i2.5 Working Group (WG) has been working to update the i2 Solution to address gaps in the i2 Solution definition, and to reflect
industry requests for changes and enhancements to the i2 Solution. As with any E9-1-1 Service solution, the i2 Solution, and any
subsequent updates to it, must support the basic E9-1-1 Service capabilities that are available to wireline and wireless customers
today. For example, the VoIP network must be able to recognize when a customer has initiated a request for emergency service (i.e., the
network must be able to identify an emergency call origination based on information received in incoming signaling). The VoIP network
must then determine how to access selective routing functionality to ensure that the call will be routed to the appropriate PSAP for
the location from which the call was originated. The VoIP network must provide the PSAP with the necessary callback and customer
location information related to the calling party to facilitate the dispatch of the appropriate emergency service personnel to the
The Voice over Internet Protocol (VoIP) Positioning Center (VPC) is a critical element of the i2 Solution defined by the National
Emergency Number Association (NENA) for supporting 9-1-1 call originations from VoIP customers. This GR defines the required functions
and interfaces that must be supported by the VPC to facilitate the routing of emergency calls and to ensure the delivery of location
information related to VoIP emergency call originations. This document provides generic requirements for the functions and interfaces
that must be supported by a VPC as a key element of the NENA i2 Solution.
Issue 4 of GR-3118 contains the following:
This GR also includes one or more Issue Lists Reports (ILRs) that detail open or closed technical issues in the main document. The
ILR(s) are automatically sent free of charge to the GR document purchaser.
- Functional and data element definitions were updated to align with draft NENA 08-001, Issue 2.
- Sections 188.8.131.52, 5.3.2 and 5.5.24 were updated to remove requirements and update text related to the v3 interface due to plans to
deprecate the v3 interface definition in Issue 2 of NENA 08-001 in anticipation of NENA adopting an industry-accepted mechanism to
support v3 interface functionality.
- Sections 184.108.40.206, 5.2.3, 5.2.4, 5.3.3, 220.127.116.11 and 18.104.22.168 were updated to describe the inclusion of geo-coded location
information in routing information provided by the ERDB in scenarios where geo-based default routing has been applied.
- Sections 22.214.171.124, and 5.2.3 were updated to clarify the information returned by the ERDB in a routing response and subsequently
stored by the VPC.
- Various subsections of Section 5.3 were updated to align the message definitions associated with the v2, v8, and v-E2
interfaces with NENA specifications.
When using GR-3118, you may want to refer to GR-2956, GR-3112, GR-3119, GR-815, and GR-3158, as well as various
NENA and standards documents.
Components of this product are:
Table of Contents:
View Table of Contents