IP Library Granted Patent US 12,423,403
Granted Patent B1
US 12,423,403 · App. 18/173,436 · Granted Sep 23, 2025

Preventing spam communications

Inventors: Edward Manuel Alonzo, III (San Antonio, TX); Robert Lee Black (San Antonio, TX); Sydney Ann Conrad-Cook (Van Meter, IA); Madhusudhana Rao Abburi (San Antonio, TX); Janelle Denice Dziuk (Falls City, TX); Carlos J P Chavez (San Antonio, TX)
Assignee: UIPCO, LLC
G06F21/44H04M3/42034G06F2221/2133H04M2203/6072
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,423,403
App. No.
18/173,436
Granted
Sep 23, 2025
Kind
B1
Abstract

Aspects of the present disclosure are directed to systems and methods for preventing spam communications. Implementations can implement an access control list that a communicator (e.g., a user device sending a text message, making a phone call, etc.) must be on in order to complete the communication with a recipient. If they are not on the access control list, the communicator can be prevented from sending the communication to the recipient, redirected to a registration process, or the communication can be tagged with an unverified status flag. In some implementations, the access control list can include a recipient's contacts, contacts of the recipient's contacts, authenticated entities (e.g., users and/or companies), previously verified entities, etc. In some implementations, a recipient can give out a temporary extension that a communicator can enter to complete communications with the recipient for a certain amount of time or for a certain number of uses.

Claims (63)

1. A method for preventing spam communications, the method comprising:

generating a registry of trusted devices, the trusted devices being associated with authenticated entities;

intercepting a first request for telephone communication with a receiving device from a first sending device;

determining that an identifier of the first sending device is not included on the registry of trusted devices;

in response to determining that the identifier of the first sending device is not included on the registry of trusted devices, redirecting the first sending device to a registration process which includes:

interrogating an installed application dataset, specifying identifiers of applications installed on the receiving device, to determine that an application provided by an entity, associated with the identifier of the first sending device, is installed on the receiving device; and

in response to the determining that the application provided by the entity is installed on the receiving device, determining that the first sending device is associated with a first authentic entity;

in response to determining that the first sending device is associated with the first authentic entity, transmitting the first request for telephone communication to the receiving device;

intercepting a second request for telephone communication with the receiving device from a second sending device;

determining that an identifier of the second sending device is not included on the registry of trusted devices;

in response to determining that the identifier of the second sending device is not included on the registry of trusted devices, redirecting the second sending device to the registration process;

determining, via the registration process, that the second sending device is not associated with a second authentic entity; and

in response to determining that the second sending device is not associated with the second authentic entity:

facilitating presentation of an unverified status flag on the receiving device and transmitting the second request for telephone communication to the receiving device; or

blocking the second request for telephone communication with the receiving device.

2. The method of claim 1 , wherein the registry of trusted devices includes one or more identifiers associated with one or more contacts of the receiving device.

3. The method of claim 2 , wherein the registry of trusted devices includes one or more identifiers associated with one or more secondary contacts, the one or more secondary contacts being one or more contacts of the one or more contacts of the receiving device.

4. The method of claim 1 , wherein the registry of trusted devices includes one or more identifiers associated with one or more devices that previously completed the registration process.

5. The method of claim 1 , wherein further in response to determining that the first sending device is associated with the first authentic entity, the method further comprises:

adding the identifier of the first sending device to the registry of trusted devices.

6. The method of claim 1 , wherein the registration process further includes providing and verifying an audio CAPTCHA.

7. The method of claim 1 , wherein the registration process further includes receiving an extension code corresponding to a stored extension code associated with the receiving device.

8. The method of claim 7 , wherein the stored extension code is associated with a time at which the stored extension code will no longer be accepted.

9. A computer-readable storage medium storing instructions that, when executed by a computing system, cause the computing system to perform a process for preventing spam communications, the process comprising:

intercepting a first request for communication with a receiving device from a first sending device;

determining that an identifier of the first sending device is not included on a registry of trusted devices;

in response to determining that the identifier of the first sending device is not included on the registry of trusted devices, redirecting the first sending device to a registration process which includes:

interrogating an installed application dataset, specifying identifiers of applications installed on the receiving device, to determine that an application provided by an entity, associated with the identifier of the first sending device, is installed on the receiving device; and

in response to the determining that the application provided by the entity is installed on the receiving device, determining that the first sending device is associated with a first authentic entity;

in response to determining that the first sending device is associated with the first authentic entity, transmitting the first request for communication to the receiving device;

intercepting a second request for communication with the receiving device from a second sending device;

determining that an identifier of the second sending device is not included on the registry of trusted devices;

in response to determining that the identifier of the second sending device is not included on the registry of trusted devices, redirecting the second sending device to the registration process;

determining, via the registration process, that the second sending device is not associated with a second authentic entity; and

in response to determining that the second sending device is not associated with the second authentic entity:

facilitating presentation of an unverified status flag on the receiving device and transmitting the second request for communication to the receiving device; or

blocking the second request for communication with the receiving device.

10. The computer-readable storage medium of claim 9 ,

wherein the first request for communication is a first request for telephone communication, and

wherein the second request for communication is a second request for telephone communication.

11. The computer-readable storage medium of claim 9 , wherein the process further comprises:

generating the registry of trusted devices, the trusted devices being associated with authenticated entities.

12. The computer-readable storage medium of claim 9 , wherein the registry of trusted devices includes one or more identifiers associated with one or more contacts of the receiving device.

13. The computer-readable storage medium of claim 12 , wherein the registry of trusted devices includes one or more identifiers associated with one or more secondary contacts, the one or more secondary contacts being one or more contacts of the one or more contacts of the receiving device.

14. The computer-readable storage medium of claim 9 , wherein the registry of trusted devices includes one or more identifiers associated with one or more devices that previously completed the registration process.

15. The computer-readable storage medium of claim 9 , wherein further in response to determining that the first sending device is associated with the first authentic entity, the process further comprises:

adding the identifier of the first sending device to the registry of trusted devices.

16. The computer-readable storage medium of claim 9 , wherein the registration process further includes providing a verifying a CAPTCHA.

17. The computer-readable storage medium of claim 9 , wherein the registration process further includes receiving an extension code corresponding to a stored extension code associated with the receiving device.

18. The computer-readable storage medium of claim 16 , wherein the stored extension code is associated with a time at which the stored extension code will no longer be accepted.

19. A computing system for preventing spam communications, the computing system comprising:

one or more processors; and

one or more memories storing instructions that, when executed by the one or more processors, cause the computing system to perform a process comprising:

intercepting a request for communication with a receiving device from a sending device;

determining that an identifier of the sending device is not included on a registry of trusted devices;

in response to determining that the identifier of the sending device is not included on the registry of trusted devices, redirecting the sending device to a registration process which includes:

interrogating an installed application dataset, specifying identifiers of applications installed on the receiving device, to determine that an application provided by an entity, associated with the identifier of the sending device, is not installed on the receiving device; and

in response to determining that the application provided by the entity is not installed on the receiving device, determining that the sending device is not associated with an authentic entity; and

in response to determining that the sending device is not associated with the authentic entity:

facilitating presentation of an unverified status flag on the receiving device and transmitting the request for communication to the receiving device; or

blocking the request for communication with the receiving device.

20. The computing system of claim 19 ,

wherein the request for communication is a request for telephone communication.

Assignments (2)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 3, 2025
From: UIPCO, LLC
To: UNITED SERVICES AUTOMOBILE ASSOCIATION (USAA)
Reel/Frame 072145/0156 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 23, 2023
From: ALONZO, EDWARD MANUEL, III; BLACK, ROBERT LEE; CONRAD-COOK, SYDNEY ANN; ABUURI, MADHUSUDHANA RAO; DZIUK, JANELLE DENICE; CHAVEZ, CARLOS JP
To: UIPCO, LLC
Reel/Frame 062785/0320 →
References Cited (14)
US 9667577B2 · Deluca et al. · 2017 [cited by applicant]
US 10067772B1 · Ledet · 2018 [cited by applicant]
US 10594648B2 · Iyer et al. · 2020 [cited by applicant]
US 20090132662A1 · Sheridan et al. · 2009 [cited by applicant]
US 20100268682A1 · Lewis et al. · 2010 [cited by applicant]
US 20100317319A1 · Gorman · 2010 [cited by examiner]
US 20110191847A1 · Davis · 2011 [cited by examiner]
US 20180176168A1 · Tsou · 2018 [cited by applicant]
US 20190020687A1 · Noon et al. · 2019 [cited by applicant]
US 20190197479A1 · Huang et al. · 2019 [cited by applicant]
US 20210306456A1 · Kanagala · 2021 [cited by examiner]
US 20220078197A1 · Jakobsson et al. · 2022 [cited by applicant]
US 20230075625A1 · Patel · 2023 [cited by examiner]
US 20230334247A1 · Albero et al. · 2023 [cited by applicant]