Common use of INTERCONNECTING I3 NETWORKS Clause in Contracts

INTERCONNECTING I3 NETWORKS. While technically capable, the Arizona Managed NG9-1-1 solution does not specify nor have cost allowances for interconnection with other i3 Networks. When a PSAP identifies the need for interconnection to other i3 Networks, cost and methods will be determined at that time. However, the below provides the process that would be used to complete the interconnection and how services might work. West/CENTURYLINK assumes that the entire state of Arizona will first be moved to an IP-based Selective Routing solution. Once implemented, the IP Selective Router solution will support IP enabled (non-i3) PSAPs, legacy PSAPs and i3 PSAPs throughout the state, simultaneously. Since all TN subscriber location information is stored in a common database, which simultaneously supports LIS HELD queries, CIDB Additional Data queries, and legacy ALI queries, the capabilities of the PSAP will determine which interface will be utilized to retrieve location data. If all PSAPs involved in a bridge/transfer have transitioned to i3, they would utilize the Emergency Incident Data Document (EIDD) to exchange location data and any other supplemental data or alternatively URIs to the dereferencing systems that would provide the data or data updates to the PSAP. The West/CENTURYLINK ESInet supports interconnectivity with both neighboring i3 and legacy networks. As a transition solution, West/CENTURYLINK will provide a Legacy Selective Router Gateway (LSRG) between the ESInet and the legacy Tandem routers. This makes possible the following services: Allow i3 PSAPs on the ESInet to receive 9-1-1 calls from the Legacy Selective routers until TSP’s have migrated their circuits over to the ESInet. Allow call transfers with additional information, such as ALI, and depending on CPE, case notes and TTY, between PSAPs still on the legacy tandems and an i3 PSAP on the ESInet. Allow call transfers between i3 PSAPs on the ESInet and PSAPs on the legacy tandems. Call transfers between i3 PSAPs will support additional information, such as PIDF-LO, and depending on CPE, case notes and TTY. West/CENTURYLINK will also support ingress and egress i3 SIP to support both i3-compliant TSP traffic and interconnectivity with other i3 networks, e.g. in-state regional networks or neighboring state networks. Calls received from i3-compliant TSPs and transferred in from neighboring i3 networks will be delivered according to the PSAP-defined routing policy. West’s ESRP will also support configuration for transfers to neighboring ESInets via egress i3 SIP. For Text-to-9-1-1 transfer services, West’s TCC now supports a variety of “in-band” commands that can be sent by the PSAP to invoke certain feature-specific actions on TCC such as the transfer function to other PSAPs that are using West for Integrated, Web, or TTY. The transfer functionality also allows the PSAPs involved in a transfer to chat privately when conferencing in the PSAP that the conversation will be transferred to. Upon transfer to another PSAP the entire dialog that had previously taken place will be transferred to the accepting PSAP. Upon transfer the last location known will be forwarded in the initial message to the accepting PSAP. Note that at the time of this response, there are no industry standardized requirements that have been developed for the transfer of text sessions between PSAPs served by different TCC providers. West has implemented their own solution in order to support transfer capabilities between PSAPs served by the West TCC until such time that standards are developed or an agreement between TCC providers has been reached to support these capabilities.

INTERCONNECTING I3 NETWORKS. While technically capable, the Arizona Managed NG9-1-1 solution does not specify nor have cost allowances for interconnection with other i3 Networks. When a PSAP identifies the need for interconnection to other i3 Networks, cost and methods will be determined at that time. However, the below provides the process that would be used to complete the interconnection and how services might work. West/CENTURYLINK assumes that the entire state of Arizona will first be moved to an IP-based Selective Routing solution. Once implemented, the IP Selective Router solution will support IP enabled (non-i3) PSAPs, legacy PSAPs and i3 PSAPs throughout the state, simultaneously. Since all TN subscriber location information is stored in a common database, which simultaneously supports LIS HELD queries, CIDB Additional Data queries, and legacy ALI queries, the capabilities of the PSAP will determine which interface will be utilized to retrieve location data. If all PSAPs involved in a bridge/transfer have transitioned to i3, they would utilize the Emergency Incident Data Document (EIDD) to exchange location data and any other supplemental data or alternatively URIs to the dereferencing systems that would provide the data or data updates to the PSAP. The West/CENTURYLINK ESInet supports interconnectivity with both neighboring i3 and legacy networks. As a transition solution, West/CENTURYLINK will provide a Legacy Selective Router Gateway (LSRG) between the ESInet and the legacy Tandem routers. This makes possible the following services: Allow i3 PSAPs on the ESInet to receive 9-1-1 calls from the Legacy Selective routers until TSP’s have migrated their circuits over to the ESInet. Allow call transfers with additional information, such as ALI, and depending on CPE, case notes and TTY, between PSAPs still on the legacy tandems and an i3 PSAP on the ESInet. Allow call transfers between i3 PSAPs on the ESInet and PSAPs on the legacy tandems. Call transfers between i3 PSAPs will support additional information, such as PIDF-LO, and depending on CPE, case notes and TTY. West/CENTURYLINK will also support ingress and egress i3 SIP to support both i3-compliant TSP traffic and interconnectivity with other i3 networks, e.g. in-state regional networks or neighboring state networks. Calls received from i3-compliant TSPs and transferred in from neighboring i3 networks will be delivered according to the PSAP-defined routing policy. West’s ESRP will also support configuration for transfers to neighboring ESInets via egress i3 SIP. For Text-to-9-1-1 transfer services, WestXxxx’s TCC now supports a variety of “in-band” commands that can be sent by the PSAP to invoke certain feature-specific actions on TCC such as the transfer function to other PSAPs that are using West for Integrated, Web, or TTY. The transfer functionality also allows the PSAPs involved in a transfer to chat privately when conferencing in the PSAP that the conversation will be transferred to. Upon transfer to another PSAP the entire dialog that had previously taken place will be transferred to the accepting PSAP. Upon transfer the last location known will be forwarded in the initial message to the accepting PSAP. Note that at the time of this response, there are no industry standardized requirements that have been developed for the transfer of text sessions between PSAPs served by different TCC providers. West has implemented their own solution in order to support transfer capabilities between PSAPs served by the West TCC until such time that standards are developed or an agreement between TCC providers has been reached to support these capabilities.