Common use of Functional Components of i3 Solution Clause in Contracts

Functional Components of i3 Solution. 10.6.1 Emergency Call Routing Function (ECRF) and Location Validation Function (LVF) The ECRF provides full i3 compliancy housing Customer provided street centerline and point data, multiple geospatial routing boundary layers and utilization of the LoST (RFC 5222 compliant) interface for retrieval of police, fire, emergency medical services and other applicable service types. Interface with the ECRF is via an i3-based LoST protocol interface. The Emergency Services Routing Proxy (ESRP) queries the ECRF via the LoST protocol to obtain the destination Uniform Resource Identifier (URI) for the call. Using the destination URI, the ESRP interfaces with the policy store to identify applicable routing policies. For geospatial routing policies other than Standard Routing or a Priority Override policy, the ESRP re-queries the ECRF via LoST to obtain the routing destination for alternate service types – e.g. abandonment, diversion requested or special event routing. The ECRF supports multiple Geographic Information Systems (GIS) and service type layers which are leveraged to support geospatial queries via the LoST protocol. In addition to street centerline and point data provisioned via the GIS provisioning platform and SIF systems, the ECRF supports provisioning of multiple service types including:  Standard Routing – The standard i3 routing boundary for each PSAP and the corresponding URI are pre-provisioned via the SIF and retrieved by the ESRP for use in determining the applicable routing policy.  Abandonment, Overflow, Diversion, and Special Event Routing – In addition to standard i3 routing, the ECRF allows geospatial boundaries to be provisioned for multiple routing service types to support abandonment, overflow, diversion, and special event routing policies. Each assigned a unique URN. Provisioning via the ECRF ensures that alternate policy routing is based on fully-validated GIS boundaries. Once provisioned, configuration changes made via the Policy Routing Function (PRF) User Interface can specify an alternate URN to be used for routing determination. Note that these capabilities are in addition to use of a Priority Override Polygon which would be provisioned directly to the PRF and for locations that fall within its boundary, would be used in place of an ECRF query to route calls.

Functional Components of i3 Solution. 10.6.1 Emergency Call Routing Function (ECRF) and Location Validation Function (LVF) The ECRF provides full i3 compliancy housing Customer provided street centerline and point data, multiple geospatial routing boundary layers and utilization of the LoST (RFC 5222 compliant) interface for retrieval of police, fire, emergency medical services and other applicable service types. Interface with the ECRF is via an i3-based LoST protocol interface. The Emergency Services Routing Proxy (ESRP) queries the ECRF via the LoST protocol to obtain the destination Uniform Resource Identifier (URI) for the call. Using the destination URI, the ESRP interfaces with the policy store to identify applicable routing policies. For geospatial routing policies other than Standard Routing or a Priority Override policy, the ESRP re-queries the ECRF via LoST to obtain the routing destination for alternate service types – e.g. abandonment, diversion requested or special event routing. The ECRF supports multiple Geographic Information Systems (GIS) and service type layers which are leveraged to support geospatial queries via the LoST protocol. In addition to street centerline and point data provisioned via the GIS provisioning platform and SIF systems, the ECRF supports provisioning of multiple service types including:  • Standard Routing – The standard i3 routing boundary for each PSAP and the corresponding URI are pre-provisioned via the SIF and retrieved by the ESRP for use in determining the applicable routing policy.  • Abandonment, Overflow, Diversion, and Special Event Routing – In addition to standard i3 routing, the ECRF allows geospatial boundaries to be provisioned for multiple routing service types to support abandonment, overflow, diversion, and special event routing policies. Each assigned a unique URN. Provisioning via the ECRF ensures that alternate policy routing is based on fully-validated GIS boundaries. Once provisioned, configuration changes made via the Policy Routing Function (PRF) User Interface can specify an alternate URN to be used for routing determination. Note that these capabilities are in addition to use of a Priority Override Polygon which would be provisioned directly to the PRF and for locations that fall within its boundary, would be used in place of an ECRF query to route calls.