IP Library Granted Patent US 12,457,291
Granted Patent B2
US 12,457,291 · App. 17/317,559 · Granted Oct 28, 2025

Silent caller ID verification using callback request

Inventors: Payas Gupta (Atlanta, GA); Terry Nelms, II (Atlanta, GA)
Assignee: Pindrop Security, Inc.
H04M3/436H04M3/2281H04M3/42059H04M19/04H04M2203/6045
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,457,291
App. No.
17/317,559
Granted
Oct 28, 2025
Kind
B2
Abstract

Disclosed herein are embodiments of systems, methods, and products comprises an authentication server for caller ID verification. When a caller makes a phone call, the server receives the phone call and verifies whether the phone call is from a registered device associated with the phone number. The server queries the registered device to retrieve one or more current call states via an authentication function on the registered device. The server compares the states and/or state transitions to the observed states and/or state transitions of the phone call. If the registered device states and/or state transitions match the observed phone call states and/or state transitions, the server verifies that the phone call is from the registered device and not some imposter's device. If there is no such match, the server rejects the phone call before the call phone is connected or terminates the phone call after the phone call is connected.

Claims (46)

1 . A computer-implemented method comprising:

receiving, by a computer, from a caller device associated with a call, device state information of the caller device, the device state information received from an authentication application of the caller device in response to a request for the device state information;

identifying, by the computer, based upon the device state information of the caller device, a device state transition from a first state to a second state during the call, and based upon call state information obtained from an interactive voice response (IVR) server, a call state transition from a first call state to a second call state during the call;

receiving, by the computer, authentication information including biometric data of a caller of the call; and

determining, by the computer, whether the biometric data of the caller is authenticated and whether a first timestamp of the device state transition matches a second timestamp of the call state transition of the call obtained from the IVR server;

if the computer determines the biometric data of the caller is authenticated and the first timestamp of the device state transition matches the second timestamp of the call state transition of the call obtained from the IVR server, forwarding, by the computer, the call to a called device associated with the call; and

if the computer determines the biometric data of the caller is not authenticated or the first timestamp of the device state transition does not match the second timestamp of the call state transition of the call obtained from the IVR server, not forwarding, by the computer, the call to the called device associated with the call.

2 . The method according to claim 1 , further comprising:

receiving, by the computer, a caller identifier for a caller associated with the call;

identifying, by the computer, in a database a device identifier of the caller device by querying the database using the caller identifier; and

transmitting, by the computer, the request for the device state information to the caller device using the device identifier.

3 . The method according to claim 2 , wherein the caller identifier is at least one of a phone number, an account number, and an e-mail address.

4 . The method according to claim 2 , wherein the computer transmits the request to an authentication function of the caller device for the device state information.

5 . The method according to claim 2 , wherein the request is transmitted via at least one of an internet protocol channel and a mobile message channel.

6 . The method according to claim 1 , wherein a first device state or second device state of the caller device is at least one of inactive, idle, off-hook, outgoing call started, outgoing call ringing, outgoing call connected, outgoing call put on hold, and outgoing call terminated.

7 . The method according to claim 1 , wherein the authentication information includes an indicator of a type of authentication and authentication data used to authenticate the caller at the caller device, and

wherein the computer further authenticates the caller device using the the type of authentication including the biometric data and at least one of a personal identification number (PIN) and a password.

8 . The method according to claim 1 , further comprising:

receiving, by the computer, from the caller device, second device state information;

identifying, by the computer, based upon the second device state information of the caller device, a second device state transition from a third state to a fourth state during the call; and

further authenticating, by the computer, the caller device in response to the computer determining that the second device state transition matches a second call state transition of the call.

9 . The method according to claim 1 , wherein the computer periodically transmits to the caller device a new request for new device state information, receives the new device state information indicating a new device state transition, and further authenticates the caller device based upon the new device state transition and a new call state transition.

10 . A system comprising:

a non-transitory storage medium storing computer-executable program instructions; and

a computer coupled to the non-transitory storage medium and configured to execute the plurality of computer program instructions to:

receive from a caller device associated with a call, device state information of the caller device, the device state information received from an authentication application of the caller device in response to a request for the device state information;

identify, based upon the device state information of the caller device, a device state transition from a first state to a second state during the call, and based upon call state information obtained from an interactive voice response (IVR) server, a call state transition from a first call state to a second call state during the call;

receive authentication information including biometric data of a caller of the call; and

determine whether the biometric data of the caller is authenticated and whether a first timestamp of the device state transition matches a second timestamp of the call state transition of the call obtained from the IVR server;

if the computer determines the biometric data of the caller is authenticated and the first timestamp of the device state transition matches a second timestamp of the call state transition of the call obtained from the IVR server, forward the call to a called device associated with the call; and

if the computer determines the biometric data of the caller is not authenticated or the first timestamp of the device state transition does not match the second timestamp of the call state transition of the call obtained from the IVR server, not forward the call to the called device associated with the call.

11 . The system according to claim 10 , wherein the computer is further configured to:

receive a caller identifier for a caller associated with the call;

identify in a database a device identifier of the caller device by querying the database using the caller identifier; and

transmit the request for the device state information to the caller device using the device identifier.

12 . The system according to claim 11 , wherein the caller identifier is at least one of a phone number, an account number, and an e-mail address.

13 . The system according to claim 11 , wherein the computer transmits the request to an authentication function of the caller device for the device state information.

14 . The system according to claim 11 , wherein the request is transmitted via at least one of an internet protocol channel and a mobile message channel.

15 . The system according to claim 10 , wherein a first device state or second device state of the caller device is at least one of inactive, idle, off-hook, outgoing call started, outgoing call ringing, outgoing call connected, outgoing call put on hold, and outgoing call terminated.

16 . The system according to claim 10 , wherein the authentication information includes an indicator of a type of authentication and authentication data used to authenticate the caller at the caller device, and

wherein the computer further authenticates the caller device using the type of authentication including the biometric data and at least one a personal identification number (PIN) and a password.

17 . The system according to claim 10 , wherein the computer is further configured to:

receive from the caller device, second device state information;

identify based upon the second device state information of the caller device, a second device state transition from a third state to a fourth state during the call; and

further authenticate the caller device in response to the computer determining that the second device state transition matches a second call state transition of the call.

18 . The system according to claim 10 , wherein the computer periodically transmits to the caller device a new request for new device state information, receives the new device state information indicating a new device state transition, and further authenticates the caller device based upon the new device state transition and a new call state transition.

Assignments (4)
SECURITY INTEREST Recorded Jun 26, 2024
From: PINDROP SECURITY, INC.
To: HERCULES CAPITAL, INC., AS AGENT
Reel/Frame 067867/0860 →
RELEASE OF SECURITY INTEREST Recorded Jun 26, 2024
From: JPMORGAN CHASE BANK, N.A., AS ADMINISTRATIVE AGENT
To: PINDROP SECURITY, INC.
Reel/Frame 069477/0962 →
SECURITY INTEREST Recorded Jul 31, 2023
From: PINDROP SECURITY, INC.
To: JPMORGAN CHASE BANK, N.A.
Reel/Frame 064443/0584 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 11, 2021
From: GUPTA, PAYAS; NELMS, TERRY, II
To: PINDROP SECURITY, INC.
Reel/Frame 056205/0150 →
Continuity (3)
Continuation 16287879 · Feb 27, 2019
Provisional Application 62640826 · Mar 9, 2018
Related Publication 20210281680A1 · Sep 9, 2021
References Cited (83)
US 5949874A · Mark · 1999 [cited by applicant]
US 6021119A · Derks et al. · 2000 [cited by applicant]
US 8046230B1 · McIntosh · 2011 [cited by applicant]
US 8135119B1 · Zhao et al. · 2012 [cited by applicant]
US 8254541B2 · Cai · 2012 [cited by applicant]
US 8660255B2 · Theivendran · 2014 [cited by examiner]
US 8738442B1 · Liu et al. · 2014 [cited by applicant]
US 8856895B2 · Perrot · 2014 [cited by applicant]
US 9001985B2 · Cox et al. · 2015 [cited by applicant]
US 9060057B1 · Danis · 2015 [cited by examiner]
US 9094519B1 · Shuman et al. · 2015 [cited by applicant]
US 9277049B1 · Danis · 2016 [cited by applicant]
US 9332119B1 · Danis · 2016 [cited by applicant]
US 9338619B2 · Kang · 2016 [cited by applicant]
US 9344892B1 · Rodrigues et al. · 2016 [cited by applicant]
US 9531695B2 · Koppolu et al. · 2016 [cited by applicant]
US 9544440B2 · Deng et al. · 2017 [cited by applicant]
US 9549062B1 · Yaung et al. · 2017 [cited by applicant]
US 9762728B1 · Cox et al. · 2017 [cited by applicant]
US 9781255B1 · Gailloux et al. · 2017 [cited by applicant]
US 9800612B2 · Harvey et al. · 2017 [cited by applicant]
US 9860367B1 · Jiang et al. · 2018 [cited by applicant]
US 9942766B1 · Bonn · 2018 [cited by examiner]
US 10044647B1 · Karp et al. · 2018 [cited by applicant]
US 10142464B1 · Cairns et al. · 2018 [cited by applicant]
US 10149156B1 · Tiku et al. · 2018 [cited by applicant]
US 10389874B1 · Farnsworth et al. · 2019 [cited by applicant]
US 10397398B2 · Gupta · 2019 [cited by applicant]
US 11019203B2 · Gupta · 2021 [cited by examiner]
US 11258896B1 · Cox et al. · 2022 [cited by applicant]
US 12212709B2 · Gupta · 2025 [cited by examiner]
US 20040023644A1 · Montemer · 2004 [cited by applicant]
US 20060142012A1 · Kirchhoff et al. · 2006 [cited by applicant]
US 20070116227A1 · Vitenson · 2007 [cited by examiner]
US 20080219177A1 · Flynn et al. · 2008 [cited by applicant]
US 20080253376A1 · Charzinski · 2008 [cited by applicant]
US 20090080624A1 · Small et al. · 2009 [cited by applicant]
US 20090097630A1 · Fotta · 2009 [cited by applicant]
US 20090138712A1 · Driscoll · 2009 [cited by applicant]
US 20090274143A1 · Garg · 2009 [cited by examiner]
US 20100040216A1 · Chida · 2010 [cited by applicant]
US 20110183652A1 · Eng et al. · 2011 [cited by applicant]
US 20110211572A1 · Campion · 2011 [cited by examiner]
US 20110250874A1 · Shah · 2011 [cited by examiner]
US 20120021751A1 · Zhang · 2012 [cited by examiner]
US 20120166185A1 · Zirngibl et al. · 2012 [cited by applicant]
US 20130016819A1 · Cheethirala · 2013 [cited by examiner]
US 20130156170A1 · Springer · 2013 [cited by examiner]
US 20140241513A1 · Springer · 2014 [cited by applicant]
US 20140250512A1 · Goldstone et al. · 2014 [cited by applicant]
US 20140335822A1 · Jain · 2014 [cited by applicant]
US 20150024712A1 · Kang · 2015 [cited by applicant]
US 20150036813A1 · Ananthakrishnan et al. · 2015 [cited by applicant]
US 20150057044A1 · Altman · 2015 [cited by applicant]
US 20150347725A1 · Ben Ari et al. · 2015 [cited by applicant]
US 20150373193A1 · Cook · 2015 [cited by applicant]
US 20160050203A1 · Hefetz · 2016 [cited by applicant]
US 20170060779A1 · Falk · 2017 [cited by applicant]
US 20170163803A1 · Russell · 2017 [cited by applicant]
US 20180082689A1 · Khoury et al. · 2018 [cited by applicant]
US 20180365400A1 · Lopez-Hinojosa et al. · 2018 [cited by applicant]
US 20200008021A1 · Polychronidis · 2020 [cited by applicant]
US 20200267224A1 · Doane · 2020 [cited by applicant]
US 20200396331A1 · Gupta et al. · 2020 [cited by applicant]
US 20210136200A1 · Li et al. · 2021 [cited by applicant]
US 20220046126A1 · Grabowski et al. · 2022 [cited by applicant]
US 20230362298A1 · Kwok et al. · 2023 [cited by applicant]
US 20240098177A1 · Edwards et al. · 2024 [cited by applicant]
WO WO2018236625A1 · 2018 [cited by applicant]
Examination Report No. 1 for Australian app. 2020340368 dated Jan. 31, 2023 (4 pages). [cited by applicant]
Android Phone Application to Detect Malicious Cell Phone Spoofing, https://cse.sc.edu/files/Laurie%20Dening.pdf, Apr. 3, 2018, 8 pages. [cited by applicant]
International Preliminary Report and Patentability and Written Opinion issued in corresponding International Application No. PCT/US2019/021062 dated Jul. 10, 2019. [cited by applicant]
International Search Report and Written Opinion issued in corresponding International Application No. PCT/US2018/013965 dated May 14, 2018. [cited by applicant]
International Search Report issued in International Application No. PCT/US2020/048175 dated Dec. 31, 2020. [cited by applicant]
Jiang et al., “Integrating Internet Telephony Services”, Jun. 2002, retrieved on [Oct. 29, 2020]. Retrieved from the Internet <URL: http://cs.uccs.edu/˜cs525/sip/IEEEInternetComputing02_IPTelephony.pdf> entire document. [cited by applicant]
Mustafa et al., You Can Call But You Can't Hide: Detecting Caller ID Spoofing Attacks, https://ieeexplore.ieee.org/document/6903577/, Jun. 26, 2014, 20 pages. [cited by applicant]
International Search Report and Written Opinion issued in corresponding International Application No. PCT/US2019/021063 dated May 15, 2019, 14 pages. [cited by applicant]
International Search Report and the Written Opinion issued in corresponding International Application No. PCT/US2019/021062, dated Jul. 10, 2019, 12 pages. [cited by applicant]
Written Opinion of the International Searching Authority issued in International Application No. PCT/US2020/048175 dated Dec. 31, 2020. [cited by applicant]
International Preliminary Report on Patentability for PCT/US2020/048175 dated Mar. 10, 2022 (7 pages). [cited by applicant]
Extended European Search Report on EPO App. 20859570.2 dated Aug. 8, 2023 (8 pages). [cited by applicant]
Examiner's Requisition dated Mar. 28, 2024 on CA App. 3, 150,456 (4 pages). [cited by applicant]
U.S. Appl. No. 62/928,222 (filed Oct. 30, 2019) (Year: 2019). [cited by applicant]