IP Library Granted Patent US 8,098,798
Granted Patent B2
US 8,098,798 · App. 11/590,464 · Granted Jan 17, 2012

Logging call data for failed emergency calls

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 8,098,798
App. No.
11/590,464
Granted
Jan 17, 2012
Kind
B2
Abstract

A method of logging call data for failed emergency calls includes: receiving from a calling party an emergency call that is to be routed to a Public Safety Answering Point (PSAP) ( 40 ) over a telecommunications network ( 20 ); determining if the received emergency call is connected to the PSAP ( 40 ); and, if the received emergency call fails to be connected to the PSAP ( 40 ), then capturing selected call data regarding the failed emergency call and recording the captured call data.

Claims (43)

1. A method of logging call data for failed emergency calls, said method comprising:

(a) receiving from a calling party an emergency call that is to be routed to a Public Safety Answering Point (PSAP) over a telecommunications network;

(b) determining if the received emergency call is connected to the PSAP;

(c) if the received emergency call fails to be connected to the PSAP, then capturing selected call data regarding the failed emergency call;

(d) forwarding and recording the captured call data in a failed emergency call log accessible to an authorized official at the PSAP such that the authorized official can review the captured call data to determine if further treatment of the failed emergency call is appropriate;

(e) sending a notification to the authorized official that the captured call data for the failed emergency call was recorded in the failed emergency call log; and

(f) sending a periodic reminder to the authorized official that the captured call data for the failed emergency call is recorded in the failed emergency call log until the failed emergency call is resolved;

wherein the captured call data includes an indication of a reason the emergency call failed to be connected to the PSAP.

2. The method of claim 1 wherein the call data is maintained in the failed emergency call log so as to be searchable by the authorized official upon accessing the same in accordance with criteria selected thereby.

3. The method of claim 1 wherein the call data is maintained in the failed emergency call log so as to be filterable by the authorized official upon accessing the same in accordance with criteria selected thereby.

4. The method of claim 1 wherein the call data is maintained in the failed emergency call log so as to be sortable by the authorized official upon accessing the same in accordance with criteria selected thereby.

5. The method of claim 1 wherein, if the calling party hangs up before the emergency call is answered by the PSAP, the reason the emergency call failed in the captured call data includes a code indicating the calling party hung up before the emergency call was answered.

6. The method of claim 1 wherein, if the PSAP could not answer the emergency call because it was busy, the reason the emergency call failed in the captured call data includes a code indicating the PSAP was busy.

7. The method of claim 1 wherein, if the telecommunications network could not route the call to the PSAP, the reason the emergency call failed in the captured call data includes a code indicating the emergency call could not be routed.

8. The method of claim 1 , further comprising:

(e) sending a notification to the authorized official that the captured call data for the failed emergency call was forwarded to the failed emergency call log.

9. A system for logging call data for failed emergency calls, said system comprising:

receiving means for receiving from a calling party an emergency call that is to be routed to a Public Safety Answering Point (PSAP) over a telecommunications network;

determining means for determining if the emergency call received by the receiving means is connected to the PSAP;

capturing means for capturing selected call data regarding the emergency call received by the receiving means if the received emergency call fails to be connected to the PSAP;

recording means for forwarding and recording call data captured by the capturing means in a failed emergency call log accessible to an authorized official at the PSAP such that the authorized official can review the captured call data to determine if further treatment of the failed emergency call is appropriate;

notifying means for sending a notification to the authorized official that the captured call data for the failed emergency call was recorded in the failed emergency call log; and

means for sending a periodic reminder to the authorized official that the captured call data for the failed emergency call is recorded in the failed emergency call log until the failed emergency call is resolved;

wherein the captured call data includes an indication of a reason the emergency call failed to be connected to the PSAP.

10. The system of claim 9 wherein the call data is maintained in the failed emergency call log so as to be searchable by the authorized official upon accessing the same in accordance with criteria selected thereby.

11. The system of claim 9 wherein the call data is maintained in the failed emergency call log so as to be filterable by the authorized official upon accessing the same in accordance with criteria selected thereby.

12. The system of claim 9 wherein the call data is maintained in the failed emergency call log so as to be sortable by the authorized official upon accessing the same in accordance with criteria selected thereby.

13. The system of claim 9 wherein, if the calling party hangs up before the emergency call is answered by the PSAP, the reason the emergency call failed in the captured call data includes a code indicating the calling party hung up before the emergency call was answered.

14. The system of claim 9 wherein, if the PSAP could not answer the emergency call because it was busy, the reason the emergency call failed in the captured call data includes a code indicating the PSAP was busy.

15. The system of claim 9 wherein, if the telecommunications network could not route the call to the PSAP, the reason the emergency call failed in the captured call data includes a code indicating the emergency call could not be routed.

16. The system of claim 9 , further comprising:

means for sending a notification to the authorized official that the captured call data for the failed emergency call was forwarded to the failed emergency call log.

17. A telecommunications network comprising:

a Public Safety Answering Point (PSAP) to which emergency calls are routed;

an originating node that provides a calling party access to the telecommunications network, said originating node, upon receiving an emergency call from the calling party, attempting to connect the emergency call to the PSAP over the telecommunications network, determining if the received emergency call is connected to the PSAP, and, if the received emergency call fails to be connected to the PSAP, capturing selected call data regarding the failed emergency call; and,

a failed emergency call log accessible to an authorized official at the PSAP to which the captured call data is forwarded by the originating node, wherein the captured call data is recorded such that the authorized official can review the captured call data to determine if further treatment of the failed emergency call is appropriate;

wherein the captured call data recorded in the failed emergency call log includes an indication of a reason the emergency call failed to be connected to the PSAP;

wherein a notification is sent to the PSAP to notify the authorized official that the captured call data for the failed emergency call was recorded in the failed emergency call log;

wherein a periodic reminder is sent to the PSAP to remind the authorized official that the captured call data for the failed emergency call is recorded in the failed emergency call log until failed emergency call is resolved.

18. The telecommunications network of claim 17 wherein a notification is sent to the PSAP to notify the authorized official that the captured call data for the failed emergency call was forwarded to the failed emergency call log.

19. The telecommunications network of claim 17 wherein, if the calling party hangs up before the emergency call is answered by the PSAP, the reason the emergency call failed in the captured call data includes a code indicating the calling party hung up before the emergency call was answered.

20. The telecommunications network of claim 17 wherein, if the PSAP could not answer the emergency call because it was busy, the reason the emergency call failed in the captured call data includes a code indicating the PSAP was busy.

21. The telecommunications network of claim 17 wherein, if the telecommunications network could not route the call to the PSAP, the reason the emergency call failed in the captured call data includes a code indicating the emergency call could not be routed.

Assignments (12)
RELEASE OF SECURITY INTEREST Recorded Jun 3, 2021
From: TERRIER SSC, LLC
To: WSOU INVESTMENTS, LLC
Reel/Frame 056526/0093 →
SECURITY INTEREST Recorded Jun 1, 2021
From: WSOU INVESTMENTS, LLC
To: OT WSOU TERRIER HOLDINGS, LLC
Reel/Frame 056990/0081 →
RELEASE OF SECURITY INTEREST Recorded May 21, 2019
From: OCO OPPORTUNITIES MASTER FUND, L.P. (F/K/A OMEGA CREDIT OPPORTUNITIES MASTER FUND LP
To: WSOU INVESTMENTS, LLC
Reel/Frame 049246/0405 →
SECURITY INTEREST Recorded May 20, 2019
From: WSOU INVESTMENTS, LLC
To: BP FUNDING TRUST, SERIES SPL-VI
Reel/Frame 049235/0068 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 25, 2017
From: ALCATEL LUCENT
To: WSOU INVESTMENTS, LLC
Reel/Frame 044000/0053 →
SECURITY INTEREST Recorded Sep 21, 2017
From: WSOU INVESTMENTS, LLC
To: OMEGA CREDIT OPPORTUNITIES MASTER FUND, LP
Reel/Frame 043966/0574 →
RELEASE OF SECURITY INTEREST Recorded Sep 30, 2014
From: CREDIT SUISSE AG
To: ALCATEL LUCENT
Reel/Frame 033868/0001 →
SECURITY AGREEMENT Recorded Jan 30, 2013
From: ALCATEL LUCENT
To: CREDIT SUISSE AG
Reel/Frame 029821/0001 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Nov 22, 2011
From: ALCATEL-LUCENT USA INC.
To: ALCATEL LUCENT
Reel/Frame 027269/0694 →
MERGER Recorded Nov 16, 2011
From: LUCENT TECHNOLOGIES INC.
To: ALCATEL-LUCENT USA INC.
Reel/Frame 027233/0104 →
CORRECTIVE ASSIGNMENT TO CORRECT THE SPELLING OF INVENTOR GOLDMAN'S NAME PREVIOUSLY RECORDED ON REEL 018918 FRAME 0036. ASSIGNOR(S) HEREBY CONFIRMS THE ASSIGNMENT. Recorded Sep 23, 2011
From: GOLDMAN, STUART O.; KROCK, RICHARD E.; MALONE, III, BERNARD L.; RAUSCHER, KARL F.; RUNYON, JAMES P.
To: LUCENT TECHNOLOGIES INC.
Reel/Frame 026962/0354 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 12, 2007
From: GOLDMAN, STUART A.; KROCK, RICHARD E.; MALONE, BERNARD L., III; RAUSCHER, KARL F.; RUNYON, JAMES P.
To: LUCENT TECHNOLOGIES INC.
Reel/Frame 018918/0036 →