IP Library › Granted Patent US 12,323,553
Granted Patent B2
US 12,323,553 · App. 18/436,668 · Granted Jun 3, 2025

Systems and methods for detecting call provenance from call audio

Inventors: Vijay Balasubramaniyan (Atlanta, GA); Mustaque Ahamad (Atlanta, GA); Patrick Gerald Traynor (Decatur, GA); Michael Thomas Hunter (Atlanta, GA); Aamir Poonawalla (Atlanta, GA)
Assignee: Georgia Tech Research Corporation
H04M3/2281H04L43/0829H04L65/1076H04M1/68H04W12/02H04W24/08H04M7/0078H04M2203/558H04M2203/6027H04M2203/6045H04W12/12H04W12/63H04W12/65
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,323,553
App. No.
18/436,668
Granted
Jun 3, 2025
Kind
B2
Abstract

Various embodiments of the invention are detection systems and methods for detecting call provenance based on call audio. An exemplary embodiment of the detection system can comprise a characterization unit, a labeling unit, and an identification unit. The characterization unit can extract various characteristics of networks through which a call traversed, based on call audio. The labeling unit can be trained on prior call data and can identify one or more codecs used to encode the call, based on the call audio. The identification unit can utilize the characteristics of traversed networks and the identified codecs, and based on this information, the identification unit can provide a provenance fingerprint for the call. Based on the call provenance fingerprint, the detection system can identify, verify, or provide forensic information about a call audio source.

Claims (27)

1. A computer-implemented method comprising:

obtaining, by a computer, call data for a call originated at a calling device of a caller, the call data including audio data and indicating one or more characteristics associated with the calling device;

extracting, by the computer, a feature vector using the one or more characteristics associated with the calling device from the call data, the one or more characteristics including at least one of a network or a location associated with the calling device;

generating, by the computer, a risk score associated with the call based upon comparing the feature vector for the one or more characteristics associated with the calling device extracted for the call data against a stored feature vector for one or more stored characteristics stored in one or more databases using a machine learning model trained to generate the risk score based upon training feature vectors from training call data.

2. The method according to claim 1 , further comprising authorizing, by the computer, the call data, in response to the computer determining that the one or more characteristics for the call data satisfies a matching threshold to the one or more stored characteristics.

3. The method according to claim 1 , further comprising obtaining, by the computer, the one or more stored characteristics associated with a registered user from enrollment call data of one or more enrollment calls to generate the one or more stored characteristics for the registered user.

4. The method according to claim 3 , wherein the one or more stored characteristics associated with the registered indicates at least one of: a registered telecommunications device, one or more expected locations, one or more expected networks, one or more codecs, or the registered user.

5. The method according to claim 1 , further comprising obtaining, by the computer, the one or more stored characteristics associated with a fraudster from prior call data of prior fraud call to generate the one or more stored characteristics for the fraudster in a blacklist in the one or more databases.

6. The method according to claim 5 , wherein the computer determines the risk score based upon a similarity between the one or more characteristics associated with the calling device and the one or more stored characteristics for the fraudster in the blacklist.

7. The method according to claim 1 , further comprising identifying, by the computer, a unique telecommunications device involved in the call based on the one or more characteristics.

8. The method according to claim 1 , further comprising identifying, by the computer, at least a portion of one or more networks of a transmission path of the call based on the one or more characteristics extracted from call data.

9. The method according to claim 1 , further comprising receiving, by the computer, metadata associated with the call for at least a portion of the call data of the call.

10. The method according to claim 9 , wherein the computer compares the metadata against at least a portion of the stored one or more characteristics.

11. A system comprising:

a computer comprising at least one processor configured to:

obtain call data for a call originated at a calling device of a caller, the call data including audio data and indicating one or more characteristics associated with the calling device;

extract a feature vector using the one or more characteristics associated with the calling device from the call data, the one or more characteristics including at least one of a network or a location associated with the calling device; and

generate a risk score associated with the call based upon comparing the feature vector for the one or more characteristics associated with the calling device extracted for the call data against a stored feature vector for one or more stored characteristics stored in one or more databases using a machine learning model trained to generate the risk score based upon training feature vectors from training call data.

12. The system according to claim 11 , wherein the computer is further configured to authorize the call data, in response to the computer determining that the one or more characteristics for the call data satisfies a matching threshold to the one or more stored characteristics.

13. The system according to claim 11 , wherein the computer is further configured to extract the one or more stored characteristics associated with a registered user from enrollment call data of one or more enrollment calls to generate the one or more stored characteristics for the registered user.

14. The system according to claim 13 , wherein the one or more stored characteristics associated with the registered indicates at least one of: a registered telecommunications device, one or more expected locations, one or more expected networks, one or more codecs, or the registered user.

15. The system according to claim 11 , wherein the computer is further configured to obtain the one or more stored characteristics associated with a fraudster from prior call data of prior fraud call to generate the one or more stored characteristics for the fraudster in a blacklist in the one or more databases.

16. The system according to claim 15 , wherein the computer determines the risk score based upon a similarity between the one or more characteristics associated with the calling device and the one or more stored characteristics for the fraudster in the blacklist.

17. The system according to claim 11 , wherein the computer is further configured to identify a unique telecommunications device involved in the call based on the one or more characteristics.

18. The system according to claim 11 , wherein the computer is further configured to identify at least a portion of one or more networks of a transmission path of the call based on the one or more characteristics extracted from call data.

19. The system according to claim 11 , wherein the computer is further configured to receive metadata associated with the call for at least a portion of the call data of the call.

20. The system according to claim 19 , wherein the computer compares the metadata against at least a portion of the stored one or more characteristics.

Assignments (2)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 13, 2025
From: BALASUBRAMANIYAN, VIJAY; AHAMAD, MUSTAQUE; TRAYNOR, PATRICK GERARD; HUNTER, MICHAEL THOMAS; POONAWALLA, AAMIR
To: GEORGIA TECH RESEARCH CORPORATION
Reel/Frame 070215/0222 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 4, 2024
From: BALASUBRAMANIYAN, VIJAY; AHAMAD, MUSTAQUE; TRAYNOR, PATRICK GERARD; HUNTER, MICHAEL THOMAS; POONAWALLA, AAMIR
To: GEORGIA TECH RESEARCH CORPORATION
Reel/Frame 067619/0940 →
Continuity (8)
Continuation 18541182 · Dec 15, 2023
Continuation 17338523 · Jun 3, 2021
Continuation 16730666 · Dec 30, 2019
Continuation 15347440 · Nov 9, 2016
Continuation 14715549 · May 18, 2015
Continuation 13807837
Provisional Application 61359586 · Jun 29, 2010
Related Publication 20240223697A1 · Jul 4, 2024
References Cited (68)
US 6241050B1 · Hikita et al. · 2001 [cited by applicant]
US 6256606B1 · Thyssen et al. · 2001 [cited by applicant]
US 6347088B1 · Katou et al. · 2002 [cited by applicant]
US 6928482B1 · Ben Nun et al. · 2005 [cited by applicant]
US 7123709B1 · Montgomery et al. · 2006 [cited by applicant]
US 7171355B1 · Chen · 2007 [cited by applicant]
US 7251241B1 · Jagadeesan et al. · 2007 [cited by applicant]
US 7660901B1 · O'Toole, Jr. · 2010 [cited by applicant]
US 7925304B1 · Gailloux et al. · 2011 [cited by applicant]
US 8094800B1 · Smith et al. · 2012 [cited by applicant]
US 8145562B2 · Wasserblat et al. · 2012 [cited by applicant]
US 9037113B2 · Balasubramaniyan et al. · 2015 [cited by applicant]
US 9516497B2 · Balasubramaniyan et al. · 2016 [cited by applicant]
US 9571652B1 · Zeppenfeld et al. · 2017 [cited by applicant]
US 11050876B2 · Balasubramaniyan · 2021 [cited by examiner]
US 11849065B2 · Balasubramaniyan · 2023 [cited by examiner]
US 20030054867A1 · Dowlat et al. · 2003 [cited by applicant]
US 20030112941A1 · Brown et al. · 2003 [cited by applicant]
US 20040235509A1 · Burritt et al. · 2004 [cited by applicant]
US 20040242284A1 · Sierawski et al. · 2004 [cited by applicant]
US 20050015489A1 · Whynot et al. · 2005 [cited by applicant]
US 20050185779A1 · Toms · 2005 [cited by applicant]
US 20050287954A1 · Lim et al. · 2005 [cited by applicant]
US 20060046724A1 · Ton et al. · 2006 [cited by applicant]
US 20060047516A1 · Gaichies et al. · 2006 [cited by applicant]
US 20060104218A1 · Kako · 2006 [cited by applicant]
US 20060147014A1 · Smith et al. · 2006 [cited by applicant]
US 20060238611A1 · Kenoyer et al. · 2006 [cited by applicant]
US 20070019618A1 · Shaffer et al. · 2007 [cited by applicant]
US 20070025281A1 · Mcfarland et al. · 2007 [cited by applicant]
US 20070060166A1 · Kitamura et al. · 2007 [cited by applicant]
US 20070223682A1 · Uusitalo · 2007 [cited by applicant]
US 20070272738A1 · Berkun · 2007 [cited by applicant]
US 20070282613A1 · Diethorn · 2007 [cited by applicant]
US 20080002676A1 · Wiley et al. · 2008 [cited by applicant]
US 20080291894A1 · Chang et al. · 2008 [cited by applicant]
US 20080300871A1 · Gilbert · 2008 [cited by applicant]
US 20090063159A1 · Crockett · 2009 [cited by applicant]
US 20090108854A1 · Agevik et al. · 2009 [cited by applicant]
US 20090119106A1 · Rajakumar et al. · 2009 [cited by applicant]
US 20090203365A1 · Lee et al. · 2009 [cited by applicant]
US 20090221276A1 · Vander Veen et al. · 2009 [cited by applicant]
US 20100105446A1 · Charlier et al. · 2010 [cited by applicant]
US 20100114899A1 · Aloke et al. · 2010 [cited by applicant]
US 20100317396A1 · Reynolds et al. · 2010 [cited by applicant]
US 20110028168A1 · Champlin et al. · 2011 [cited by applicant]
US 20110042410A1 · Paulen · 2011 [cited by applicant]
US 20120020351A1 · Booton · 2012 [cited by applicant]
US 20120253805A1 · Rajakumar et al. · 2012 [cited by applicant]
US 20120254243A1 · Zeppenfeld · 2012 [cited by examiner]
US 20130097303A1 · Gichana et al. · 2013 [cited by applicant]
US 20130109358A1 · Balasubramaniyan et al. · 2013 [cited by applicant]
US 20140044020A1 · Mikkelsen et al. · 2014 [cited by applicant]
US 20140295802A1 · Rybak et al. · 2014 [cited by applicant]
US 20150381801A1 · Rajakumar et al. · 2015 [cited by applicant]
US 20180152561A1 · Strong · 2018 [cited by examiner]
US 20200126569A1 · Mcdowell et al. · 2020 [cited by applicant]
Canadian Office Action and Examination Report, dated Apr. 11, 2018, in corresponding Canadian Application No. 2,804,040, 4 pages. [cited by applicant]
Examiner Requisition in Canadian Application No. dated Apr. 29, 2019. [cited by applicant]
Examiner Requisition issued in Canadian Application No. 2,804,040 dated Apr. 11, 2018. [cited by applicant]
Examiner Requisition on CA 2804040 dated Apr. 9, 2020. [cited by applicant]
Extended European Search Report issued in European Patent Application No. 11804190.4 dated Jan. 3, 2018. [cited by applicant]
Final Office Action on U.S. Appl. No. 17/338,523 dated May 12, 2023 (12 pages). [cited by applicant]
International Search Report and Written Opinion, dated Jan. 13, 2012, for related PCT Patent Application No. PCT US2011/042410. [cited by applicant]
Notice of Allowance on U.S. Appl. No. 17/338,523 DTD Aug. 9, 2023. [cited by applicant]
Patent Examination Report No. 1 issued in Patent Application No. 2011276467 dated Jul. 7, 2014. [cited by applicant]
Supplementary European Search Report, mailed Jan. 19, 2018, issued in corresponding European Application No. 11804190.4, 14 pages. [cited by applicant]
Supplementary Partial European Search Report and Written Opinion, dated Sep. 22, 2017, for related PCT Patent Application No. PCT/US2011/042410. [cited by applicant]