TECHNIQUES FOR MIGRATING LEGACY 911 SYSTEMS to NG-911 SYSTEMS

• US 20180352094A1
• Filed: 06/06/2017
• Published: 12/06/2018
• Est. Priority Date: 06/06/2017
• Status: Active Grant

• Current Assignee: Bandwidth Inc.
• Original Assignee: Bandwidth Inc.
• Inventors: Ginter, Thomas
• Granted Patent: US 10,367,947 B2
• Time in Patent Office: Days
• CPC Class Codes: H04L 65/1046 Call controllers; Call servers
• CPC Class Codes: H04M 3/5116 for emergency applications
• CPC Class Codes: H04M 7/0087 Network planning or provisioning
• CPC Class Codes: H04W 36/0011 for data sessions of end-to-end connection
• CPC Class Codes: H04W 36/0019 adapted for mobile IP [MIP]
• CPC Class Codes: H04W 76/12 Setup of transport tunnels
• CPC Class Codes: H04W 76/50 for emergency connections
• CPC Class Codes: H04W 88/023 with message or information receiving capability

Abstract

Disclosed are techniques for enabling an emergency call routing system. The system comprises a Voice-over Internet Protocol (VoIP) position center (VPC) server and a location information server (LIS). The VPC server may be configured to receive a session initiation protocol (SIP) INVITE for an emergency call intended for a destination public safety answering point (PSAP) from a telecommunication service provider (TSP) SIP call server. The VPC may also respond to the source of the SIP INVITE message with a SIP redirect response that includes routing data compatible with and capable of enabling the TSP SIP call server to route the emergency call to the destination PSAP. The LIS server may be configured to receive and store telephone number provisioning information from a TSP, the information including registered address data for the telephone number. The LIS may also receive and store PSAP capability data, the PSAP capability data indicative of the PSAP being i2 capable or i3 capable. For i2 capable PSAPs, the LIS may receive and respond to address requests for the telephone number that initiated the emergency call. For i3 capable PSAPs, the LIS may provide the VPC a PIDF-Lo formatted location object within the SIP redirect response.

Claims

1. An emergency call routing system, comprising:

a Voice-over Internet Protocol position center (VPC) server configured to;

receive a session initiation protocol (SIP) INVITE for an emergency call intended for a destination public safety answering point (PSAP) from a telecommunication service provider (TSP) SIP call server; and

respond to the source of the SIP INVITE message with a SIP Redirect response, the SIP Redirect response including routing data compatible with and capable of enabling the TSP SIP call server to route the emergency call to the destination PSAP such that neither the VPC or a selective router is in the bearer path of the emergency call;

a location information server (LIS) configured to;

receive and store telephone number provisioning information from a TSP, the information including registered address data for the telephone number; and

receive and store PSAP capability data, the PSAP capability data indicative of the PSAP operating under the i2 transitional standard for VoIP 911 or operating under the fully implemented i3 standard for VoIP 911; and

for PSAPs operating under the i2 transitional standard for VoIP 911, receive and respond to address requests for the telephone number that initiated the emergency call;

or

for PSAPs operating under the fully implemented i3 standard for VoIP 911, provide the VPC a presence information data format location object (PIDF-Lo) within the SIP Redirect response, the PIDF-Lo to be included in the SIP INVITE.

2. The emergency call routing system of claim 1 wherein the TSP comprises a VoIP network.

3. The emergency call routing system of claim 1 wherein the PSAP routing data identifies the destination PSAP as TDM legacy circuit-switched capable.

4. The emergency call routing system of claim 1 wherein the PSAP routing data identifies the destination PSAP as IP enabled non-PIDF-Lo capable.

5. The emergency call routing system of claim 1 wherein the PSAP routing data identifies the destination PSAP as IP enabled PIDF-Lo capable.

6. The emergency call routing system of claim 1 wherein the PIDF-Lo comprises data indicative of an address.

7. The emergency call routing system of claim 1 wherein the PIDF-Lo comprises data indicative of a location.

8. An emergency call routing method, comprising:

in a Voice-over Internet Protocol position center (VPC) server;

receiving a session initiation protocol (SIP) INVITE for an emergency call intended for a destination public safety answering point (PSAP) from a telecommunication service provider (TSP) SIP call server; and

responding to the source of the SIP INVITE message with a SIP Redirect response, the SIP Redirect response including routing data compatible with and capable of enabling the TSP SIP call server to route the emergency call to the destination PSAP such that neither the VPC or a selective router is in the bearer path of the emergency call;

in a location information server (LIS);

receiving and storing telephone number provisioning information from a TSP, the information including registered address data for the telephone number; and

receiving and storing PSAP capability data, the PSAP capability data indicative of the PSAP operating under the i2 transitional standard for VoIP 911 or operating under the fully implemented i3 standard for VoIP 911; and

for PSAPs operating under the i2 transitional standard for VoIP 911, receiving and responding to address requests for the telephone number that initiated the emergency call;

or

for PSAPs operating under the fully implemented i3 standard for VoIP 911, providing a presence information data format location object (PIDF-Lo) within the SIP Redirect response, the PIDF-Lo to be included in the SIP INVITE.

9. The emergency call routing method of claim 8 wherein the TSP comprises a VoIP network.

10. The emergency call routing method of claim 8 wherein the PSAP routing data identifies the destination PSAP as TDM legacy circuit-switched capable.

11. The emergency call routing method of claim 8 wherein the PSAP routing data identifies the destination PSAP as IP enabled non-PIDF-Lo capable.

12. The emergency call routing method of claim 8 wherein the PSAP routing data identifies the destination PSAP as IP enabled PIDF-Lo capable.

13. The emergency call routing method of claim 8 wherein the PIDF-Lo comprises data indicative of an address.

14. The emergency call routing method of claim 8 wherein the PIDF-Lo comprises data indicative of a location.

15. At least one machine-readable non-transitory medium comprising a set of instructions executable on a computing device operating as a Voice-over Internet Protocol (VoIP) position center (VPC) server and location information server (LIS) to cause the computing device to route emergency calls by:

receiving a session initiation protocol (SIP) INVITE for an emergency call intended for a destination public safety answering point (PSAP) from a telecommunication service provider (TSP) SIP call server;

responding to the source of the SIP INVITE message with a SIP Redirect response, the SIP Redirect response including routing data compatible with and capable of enabling the TSP SIP call server to route the emergency call to the destination PSAP such that neither the VPC or a selective router is in the bearer path of the emergency call;

receiving and storing telephone number provisioning information from a TSP, the information including registered address data for the telephone number;

receiving and storing PSAP capability data, the PSAP capability data indicative of the PSAP operating under the i2 transitional standard for VoIP 911 or operating under the fully implemented i3 standard for VoIP 911; and

for PSAPs operating under the i2 transitional standard for VoIP 911, receiving and responding to address requests for the telephone number that initiated the emergency call;

or

for PSAPs operating under the fully implemented i3 standard for VoIP 911, providing a presence information data format location object (PIDF-Lo) within the SIP Redirect response, the PIDF-Lo to be included in the SIP INVITE.

16. The at least one machine-readable non-transitory medium of claim 15, wherein the TSP comprises a VoIP network.

17. The at least one machine-readable non-transitory medium of claim 15, wherein the PSAP routing data identifies the destination PSAP as TDM legacy circuit-switched capable.

18. The at least one machine-readable non-transitory medium of claim 15, wherein the PSAP routing data identifies the destination PSAP as IP enabled non-PIDF-Lo capable.

19. The at least one machine-readable non-transitory medium of claim 15, wherein the PSAP routing data identifies the destination PSAP as IP enabled PIDF-Lo capable.

20. The at least one machine-readable non-transitory medium of claim 15, wherein the PIDF-Lo comprises data indicative of an address.

21. The at least one machine-readable non-transitory medium of claim 15, wherein the PIDF-Lo comprises data indicative of a location.