IP Library Granted Patent US 10,523,814
Granted Patent B1
US 10,523,814 · App. 15/683,171 · Granted Dec 31, 2019

Robocall management system

Inventors: Mark Moore (Dunwoody, GA); Karl H. Koster (Sandy Springs, GA)
Assignee: NOBLE SYSTEMS CORPORATION
H04M3/436H04M3/42042H04M3/42059H04M3/493H04M2203/2027H04M2203/301
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 10,523,814
App. No.
15/683,171
Granted
Dec 31, 2019
Kind
B1
Abstract

A robocall management system (RMS) comprises a service switching point switch, a service control point, and a robocall confirmation system, that all cooperate in processing incoming calls to a subscriber. If the call is not a robocall, the call will be delivered to the subscriber as normal. If the call is, or may be, a robocall, then call will be diverted to the robocall confirmation system, which will determine whether the caller is a live person or a computer playing an announcement. If the caller is a live person, then the call is offered to the subscriber. If the caller is a robocaller, then the robocall announcement is recorded by the robocall confirmation system and made available to the subscriber should they choose to listen to it. Various algorithms may be employed along with external data to ascertain a likelihood of whether the call is a robocall.

Claims (49)

1. A method for processing a call comprising a voice call from a caller directed to a called party, comprising:

receiving the call at a service switching point (“SSP”) switch configured to launch a query to a service control point (“SCP”) in response to receiving the call;

launching the query from the SSP switch to the SCP, the query conveying a calling party number and a called party number derived from the call;

using the calling party number by the SCP to determine that the SSP switch should not offer the call to the called party;

responding to the query from the SSP switch by the SCP indicating the SSP switch should redirect the call to a robocall confirmation system (“RCS”), wherein the RCS is configured to ascertain if a live person is connected to the redirected call;

receiving at the RCS the redirected call;

answering by the RCS the redirected call;

providing by the RCS an audio prompt to the caller;

analyzing audio by the RCS provided by the caller after the audio prompt to determine whether the caller is a live person;

determining the caller is the live person; and

transferring the redirected call by the RCS to the called party using the SSP.

2. The method of claim 1 , wherein the transferred redirected call is offered to the called party indicating the calling party number of the call.

3. The method of claim 1 , wherein the audio prompt requests a response from the caller.

4. The method of claim 3 , wherein the response comprises speech from the caller.

5. The method of claim 1 wherein the redirected call from the SSP to the RCS uses the called party number of the call as the calling party number of the redirected call.

6. The method of claim 1 wherein the SCP determines the calling party number is not stored in a whitelist associated with the called party.

7. The method of claim 6 , where the SCP further determines the calling party number is not on a blacklist associated with the called party.

8. A system for processing a call comprising a voice call from a caller directed to a called party, comprising:

a service switching point (“SSP”) switch configured to receive the call and launch a query in response to receiving the call, wherein the query conveys a calling party number and a called party number derived from the call;

a service control point (“SCP”) configured to receive the query from the SSP and determine whether the SSP switch should offer the call to the called party, and in response to determining the SSP switch should not offer the call to the called party, provide a response to the SSP indicating the SSP switch should redirect the call, thereby causing a redirected call; and

a robocall confirmation system (“RCS”) configured to:

receive the redirected call from the SSP switch,

provide an audio prompt to the caller,

analyze audio from the caller received after the audio prompt,

determine, based on the audio from the caller received after the audio prompt, the caller is a live person, and

upon determining the caller is a live person, transfer the redirected call to the called party via the SSP switch.

9. The system of claim 8 , wherein the transferred redirected call is offered to the called party indicating the calling party number of the call.

10. The system of claim 8 , wherein the RCS is configured to provide the audio prompt requesting a response from the caller.

11. The system of claim 10 , wherein the RCS is configured to analyze audio from the caller received after the audio prompt comprising a dual tone multiple frequency (“DTMF”) response.

12. The system of claim 8 , wherein the SSP switch is configured to use the called party number of the call as the calling party number of the redirected call when redirecting the call to the RCS.

13. The system of claim 8 , wherein the SCP is further configured to determine the calling party number is not stored in a whitelist associated with the called party.

14. The system of claim 8 , where the SCP is further configured to determine the calling party number is not on a blacklist associated with the called party.

15. A method for processing a call directed to a called party, comprising:

receiving the call at a service switching point (“SSP”) switch configured to launch a query to a service control point (“SCP”) in response to receiving the call;

launching the query from the SSP switch to the SCP, the query conveying a calling party number and a called party number derived from the call;

using the calling party number by the SCP to determine that the SSP switch should not offer the call to the called party;

responding to the query from the SSP switch by the SCP by providing a response indicating the SSP switch should redirect the call to a robocall confirmation system (“RCS”), wherein the RCS is configured to ascertain if a live person is connected to the call;

receiving the redirected call at the RCS;

answering the redirected call by the RCS;

providing an audio prompt to the caller by the RCS;

analyzing audio by the RCS provided by the caller after the audio prompt to determine whether the caller is a live person;

determining the caller is not the live person;

in response to determining the caller is not the live person, recording the audio provided by the caller wherein the message is associated with the calling party number, and

informing the SCP by the RCS that the caller is not the live person.

16. The method of claim 15 , wherein the SCP in response to being informed by the RCS that the caller is not the live person includes the calling party number on a blacklist for the called party.

17. The method of claim 16 , where the step of using the calling party number by the SCP to determine that the SSP switch should not offer the call to the called party comprises using the calling party number by the SCP to check whether the calling party number is indicated in a whitelist, and determining the calling party number is not indicated in the whitelist.

18. The method of claim 16 , where the step of using the calling party number by the SCP to determine that the SSP switch should not offer the call to the called party comprises using the calling party number by the SCP to check whether the calling party number is indicated in a blacklist, and determining the calling party number is indicated in the blacklist.

19. The method of claim 15 , where the response indicating the SSP switch should redirect the call to the RCS indicates a telephone number associated with the RCS where all calls received at the RCS using the telephone number are provided with the audio prompt.

20. The method of claim 16 , wherein the blacklist is associated with the called party and other subscribers using the SSP switch.

Assignments (13)
RELEASE OF SECURITY INTEREST Recorded Oct 27, 2025
From: JEFFERIES FINANCE LLC, AS COLLATERAL AGENT
To: ALVARIA CAYMAN (WEM); ALVARIA CAYMAN (CXIP)
Reel/Frame 073360/0209 →
ASSIGNMENT Recorded Oct 27, 2025
From: ALVARIA CAYMAN (WEM); ALVARIA CAYMAN (CXIP); NOBLE SYSTEMS, LLC
To: ALVARIA, INC.
Reel/Frame 073360/0481 →
SECURITY INTEREST Recorded Oct 27, 2025
From: ALVARIA, INC.
To: JEFFERIES FINANCE LLC, AS COLLATERAL AGENT
Reel/Frame 073360/0564 →
PATENT SECURITY AGREEMENT Recorded Mar 20, 2024
From: ALVARIA CAYMAN (WEM); ALVARIA CAYMAN (CXIP)
To: JEFFERIES FINANCE LLC
Reel/Frame 066850/0334 →
RELEASE OF SECURITY INTEREST Recorded Mar 20, 2024
From: JEFFRIES FINANCE LLC
To: ALVARIA, INC.; NOBLE SYSTEMS, LLC
Reel/Frame 066850/0428 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 20, 2024
From: NOBLE SYSTEMS, LLC
To: ALVARIA CAYMAN (CX)
Reel/Frame 066850/0556 →
RELEASE OF SECURITY INTEREST Recorded Mar 20, 2024
From: JEFFRIES FINANCE LLC
To: ALVARIA, INC.; NOBLE SYSTEMS, LLC
Reel/Frame 066850/0384 →
CERTIFICATE OF CONVERSION Recorded Mar 12, 2024
From: NOBLE SYSTEMS CORPORATION, A GEORGIA CORPORATION
To: NOBLE SYSTEMS, LLC, A DELAWARE LIMITED LIABILITY COMPANY
Reel/Frame 066794/0435 →
RELEASE OF SECURITY INTEREST Recorded May 10, 2021
From: WELLS FARGO CAPITAL FINANCE, LLC
To: NOBLE SYSTEMS CORPORATION
Reel/Frame 056193/0363 →
SECOND LIEN PATENT SECURITY AGREEMENT Recorded May 6, 2021
From: NOBLE SYSTEMS CORPORATION; ASPECT SOFTWARE, INC.
To: JEFFERIES FINANCE LLC
Reel/Frame 057674/0664 →
FIRST LIEN PATENT SECURITY AGREEMENT Recorded May 6, 2021
From: NOBLE SYSTEMS CORPORATION; ASPECT SOFTWARE, INC.
To: JEFFERIES FINANCE LLC
Reel/Frame 057261/0093 →
SECURITY INTEREST Recorded Apr 23, 2020
From: NOBLE SYSTEMS CORPORATION
To: WELLS FARGO CAPITAL FINANCE, LLC
Reel/Frame 052495/0287 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 30, 2017
From: MOORE, MARK; KOSTER, KARL H
To: NOBLE SYSTEMS CORPORATION
Reel/Frame 043445/0782 →
Continuity (1)
Provisional Application 62377810 · Aug 22, 2016
Cited By (3)
US 12,206,820 US 12,356,293 US 12,542,853