Method, system, and program element for optimizing an abandoned call notification

Patent metadata

Field	Value
Publication number	US-12278928-B2
Application number	US-202217970316-A
Country	US
Kind code	B2
Filing date	Oct 20, 2022
Priority date	Jan 13, 2022
Publication date	Apr 15, 2025
Grant date	Apr 15, 2025

Abstract

A method for optimizing an abandoned call notification can be configured to address the misrouting of an emergency call which eventually gets abandoned by the caller, through managing the indication of an abandoned call between various network elements, e.g. Emergency Service Internet Protocol network (ESInet) elements. The abandoned call notification can appear in the correct Public Safety Answering Point (PSAP) without any manual action involved in some embodiments. In addition, embodiments can also address calls which are routed in different jurisdictions due to failures in the original intended routing targets.

First claim

What is claimed is:

1. A method for optimizing an abandoned call notification, comprising:
an Emergency Service Routing Proxy (ESRP) element in an Emergency Service Internet Protocol network (ESInet) receiving a call from a caller device of caller;
verifying, by the ESRP element, that the call is considered abandoned;
performing, by the ESRP element, a rebid to obtain a fresh update of the caller location;
performing, by the ESRP element, an Emergency Call Routing Function (ECRF) query to obtain routing information of an original routing target Public Safety Answering Point (PSAP) element for the call;
sending, by an ESRP destination of the original routing target PSAP, to the ESRP element a Session Initiation Protocol (SIP) Notify message that carries the state of the original routing target PSAP;
verifying, by the ESRP element, whether the state of the original routing target PSAP is functional;
sending, by the ESRP destination, to the ESRP element a SIP Subscribe request message for abandoned call details; and
sending, by the ESRP element, to the ESRP destination a SIP Notify message which carries the abandoned call details.

2. The method of claim 1 , comprising:
forwarding, by the ESRP destination, to the original routing target PSAP the SIP Notify message, and
storing, by the original routing target PSAP on its memory-queue the abandoned call indication along with the call details.

3. The method of claim 1 , comprising:
verifying, by the ESRP element, whether at least one History-Info header exists in a SIP message of the call.

4. The method of claim 1 , wherein the call is considered abandoned if any CANCEL request is received.

5. The method of claim 1 , wherein the call is not considered an abandoned call when processing of the corresponding signaling messages of the emergency call are all exchanged in a time period t and a CANCEL request is not received.

6. The method of claim 1 , comprising:
reading out in sequence, by the ESRP element, all History-Info headers of the call and extracting the corresponding ESRP destination in the case no location update is obtain in the previous step; and
sending, by the ESRP element, a SIP Subscribe request to the extracted ESRP destination by the ESRP element to the ESRP destination obtained in the previous step to obtain the state of the original routing target PSAP element if call-History-info exists.

7. The method of claim 6 , comprising:
in response to a state of the original routing target PSAP being not functional, the ESRP element performs further reading out in sequence, by the ESRP element, all History-Info headers of the call and extracting the corresponding ESRP destination.

8. The method of claim 1 , the method comprising:
in response to caller location being updated after performance of the rebid to obtain the fresh update of the caller location, performing, by the ESRP element, an ECRF query to identify the responsible target PSAP element, and finding, by the ESRP element and/or the ESRP destination, a routing path to the target PSAP element based on the History-Information of the call.

9. The method according to claim 1 , comprising:
in response to caller location being updated after performance of the rebid to obtain the fresh update of the caller location, performing, by the ESRP element, an ECRF query to identify the responsible target PSAP element, and attempting to find a routing path to the target PSAP element based on the History-Information of the call; and
in response to the routing path not being found, extracting, by the ESRP element, another ESRP destination from the History-Info header and subsequently attempting to find the routing path to the target PSAP element based on the History-Information of the call for that other ESRP destination.

10. The method according to claim 9 , comprising:
in response to the routing path not being found:
sending, by the ESRP element, to the ESRP destination obtained a SIP Subscribe request message to obtain the state of the original routing target PSAP element;
performing, by the ESRP destination, an ECRF query to identify the original routing target PSAP element;
ending, by the ESRP destination, to the ESRP element a SIP Notify message that carries the state of the original routing target PSAP, and
verifying, by the ESRP element, whether the state of the original routing target PSAP is functional, in case the state is not functional, then the method returns to the attempting to find a routing path to the target PSAP element based on the History-Information of the call;
sending, by the ESRP destination, to the ESRP element a SIP Subscribe request message for the abandoned call details in response to the state being functional;
sending, by the ESRP element, to the ESRP destination a SIP Notify message which carries the abandoned call details;
forwarding, by the ESRP destination, to the original routing target PSAP the SIP Notify message; and
storing, by the original routing target PSAP, on its memory-queue the abandoned call indication, along with the call details.

11. The method according to claim 10 , wherein in case the state of the original routing target PSAP is not functional, the method returns to the extracting, by the ESRP element, of another ESRP destination from the History-Info header.

12. The of claim 1 , wherein the method ends in response to a determination that no History-Info header exists, the call is not considered abandoned, or the method is considered complete.

13. A system for optimizing an abandoned call notification comprising:
an Emergency Service Routing Proxy (ESRP) element positionable in an Emergency Service Internet Protocol network (ESInet), the ESRP element configured to:
receive a call from a caller device of caller;
verify that the call is considered abandoned;
perform a rebid to obtain a fresh update of the caller location;
perform an Emergency Call Routing Function (ECRF) query to obtain routing information of an original routing target Public Safety Answering Point (PSAP) element for the call;
receive from an ESRP destination of the original routing target PSAP a Session Initiation Protocol (SIP) Notify message that carries the state of the original routing target PSAP;
verify whether the state of the original routing target PSAP is functional;
receive a SIP Subscribe request message for abandoned call details from the ESRP destination; and
send to the ESRP destination a SIP Notify message which carries the abandoned call details.

14. A non-transitory computer readable medium having a program element stored thereon, the program element defining a method for optimizing an abandoned call notification, wherein the method is performed when a processor of a computer device runs the program element, the method comprising:
receiving a call from a caller device of caller;
verifying that the call is considered abandoned;
performing a rebid to obtain a fresh update of the caller location;
performing an Emergency Call Routing Function (ECRF) query to obtain routing information of an original routing target Public Safety Answering Point (PSAP) element for the call;
receiving from an ESRP destination of the original routing target PSAP a Session Initiation Protocol (SIP) Notify message that carries the state of the original routing target PSAP;
verifying whether the state of the original routing target PSAP is functional;
receiving a SIP Subscribe request message for abandoned call details from the ESRP destination; and
sending to the ESRP destination a SIP Notify message which carries the abandoned call details.

Assignees

• Unify Patente Gmbh & Co Kg
• Unify Beteiligungsverwaltung Gmbh & Co Kg

Inventors

• Anagnostou Sofia
• Milner Grant
• Pagonis Athanasios
• Tsiatsikas Zisis

Classifications

• H04M3/42357

  where the information is provided to a monitoring entity such as a potential calling party or a call processing server · CPC title

• H04L65/1045

  Proxies, e.g. for session initiation protocol [SIP] · CPC title

• H04M3/5116 Primary

  for emergency applications · CPC title

• H04L65/1069 Primary

  Session establishment or de-establishment · CPC title