IP Library Granted Patent US 12,278,928
Granted Patent B2
US 12,278,928 · App. 17/970,316 · Granted Apr 15, 2025

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

Inventors: Sofia Anagnostou (Nea Erythrea, GR); Grant Milner (Erie, CO); Athanasios Pagonis (Vrilissia, GR); Zisis Tsiatsikas (Salonika, GR)
Assignee: Unify Beteiligungsverwaltung GmbH & Co. KG
H04M3/5116H04M3/42357
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,278,928
App. No.
17/970,316
Granted
Apr 15, 2025
Kind
B2
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.

Claims (57)

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.

Assignments (9)
RELEASE OF SECURITY INTEREST Recorded Jun 24, 2025
From: WILMINGTON SAVINGS FUND SOCIETY, FSB
To: MITEL (DELAWARE), INC.; MITEL COMMUNICATIONS, INC.; MITEL NETWORKS, INC.; MITEL NETWORKS CORPORATION
Reel/Frame 071712/0821 →
NOTICE OF SUCCCESSION OF AGENCY - PL Recorded Jan 14, 2025
From: UBS AG, STAMFORD BRANCH, AS LEGAL SUCCESSOR TO CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH
To: WILMINGTON SAVINGS FUND SOCIETY, FSB
Reel/Frame 069895/0755 →
NOTICE OF SUCCCESSION OF AGENCY - 3L Recorded Jan 14, 2025
From: UBS AG, STAMFORD BRANCH, AS LEGAL SUCCESSOR TO CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH
To: WILMINGTON SAVINGS FUND SOCIETY, FSB
Reel/Frame 070006/0268 →
NOTICE OF SUCCCESSION OF AGENCY - 2L Recorded Jan 14, 2025
From: UBS AG, STAMFORD BRANCH, AS LEGAL SUCCESSOR TO CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH
To: WILMINGTON SAVINGS FUND SOCIETY, FSB
Reel/Frame 069896/0001 →
CHANGE OF NAME Recorded Oct 24, 2024
From: UNIFY PATENTE GMBH & CO. KG
To: UNIFY BETEILIGUNGSVERWALTUNG GMBH & CO. KG
Reel/Frame 069242/0312 →
SECURITY INTEREST Recorded Jan 5, 2024
From: UNIFY PATENTE GMBH & CO. KG
To: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH, AS COLLATERAL AGENT
Reel/Frame 066197/0333 →
SECURITY INTEREST Recorded Jan 5, 2024
From: UNIFY PATENTE GMBH & CO. KG
To: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH, AS COLLATERAL AGENT
Reel/Frame 066197/0299 →
SECURITY INTEREST Recorded Jan 5, 2024
From: UNIFY PATENTE GMBH & CO. KG
To: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH, AS COLLATERAL AGENT
Reel/Frame 066197/0073 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 31, 2022
From: ANAGNOSTOU, SOFIA; MILNER, GRANT; PAGONIS, ATHANASIOS; TSIATSIKAS, ZISIS
To: UNIFY PATENTE GMBH & CO. KG
Reel/Frame 061590/0854 →
Priority Claims (1)
EP 22151430 · Jan 13, 2022 · regional
Continuity (1)
Related Publication 20230224405A1 · Jul 13, 2023
References Cited (16)
US 8908835B1 · Robbins · 2014 [cited by examiner]
US 11159676B1 · Ginter · 2021 [cited by examiner]
US 20080090546A1 · Dickinson · 2008 [cited by examiner]
US 20080101553A1 · Goldman · 2008 [cited by examiner]
US 20120196558A1 · Reich · 2012 [cited by examiner]
US 20150092610A1 · Russell · 2015 [cited by examiner]
US 20160173689A1 · Klaban · 2016 [cited by examiner]
US 20160373578A1 · Klaban · 2016 [cited by examiner]
US 20180013889A1 · Klaban · 2018 [cited by examiner]
US 20180352094A1 · Ginter · 2018 [cited by examiner]
US 20190149661A1 · Klaban · 2019 [cited by examiner]
US 20220201547A1 · Gupta · 2022 [cited by examiner]
WO WO2019027537A1 · 2019 [cited by examiner]
The Extended European Search Report for European Application No. 22151430.3 dated Jun. 9, 2022. [cited by applicant]
“NENA Detailed Functional and Interface Standards for the NEA i3 Solution” Prepared by: National Emergency Number Association (NENA) Interconnection and Securing Committee, i3 Architecture Working Group; Sep. 10, 2016. [cited by applicant]
“Emergency Communications (EMTEL); Core elements for network independent access to emergency services” Draft ETSI TS 103479 vV0.0.14 (Nov. 2019); copyright 2019. [cited by applicant]