IP Library › Granted Patent US 11,811,754
Granted Patent B2
US 11,811,754 · App. 17/339,072 · Granted Nov 7, 2023

Authenticating devices via tokens and verification computing devices

Inventors: John Parkinson (Burlington, VT); Jason Park (Chicago, IL); David Harris (Wheaton, IL)
Assignee: Allstate Insurance Company
H04L63/0853G06F16/27G06F21/44H04L9/0869H04L9/3234
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 11,811,754
App. No.
17/339,072
Granted
Nov 7, 2023
Kind
B2
Abstract

Aspects of the disclosure relate to a system and method for securely authenticating a device via token(s) and/or verification computing device(s). A verification computing device may generate a pseudorandom number or sequence. Based on the pseudorandom number or sequence, the verification computing device may select a first plurality of parameters associated with a user of a device to be authenticated. The verification computing device may transmit, to the device, the pseudorandom number or sequence, and the device may select a second plurality of parameters. The device may generate a token based on the second plurality of parameters. The device may send the token to another device, and the other device may send the token to the verification computing device. The verification computing device may authenticate the device based on the token.

Claims (49)

1. A method comprising:

receiving, by a first device associated with a user and from a verification computing device, a pseudorandom sequence;

based on the pseudorandom sequence, selecting, by the first device and from a database, a plurality of parameters associated with the user;

generating, by the first device and based on the plurality of parameters, a token;

transmitting, by the first device and to a second device, the token for authenticating the first device.

2. The method of claim 1 , further comprising, after transmitting the token:

receiving, by the first device and from the verification computing device, information indicating the first device is authenticated.

3. The method of claim 1 , further comprising, after transmitting the token:

receiving, from the verification computing device, information indicating the first device is authenticated.

4. The method of claim 3 , further comprising, after transmitting the token:

transmitting, by the first device and to the second device, the information indicating the first device is authenticated.

5. The method of claim 1 , further comprising:

synchronizing parameters associated with the user stored in the database with parameters associated with the user stored in a second database associated with the verification computing device.

6. The method of claim 1 , further comprising:

updating the database with one or more of the token, metadata generated during generation of the token, or transaction information between the first device and the second device.

7. The method of claim 1 , wherein selecting the plurality of parameters comprises selecting, by a proxy associated with the first device, the plurality of parameters, and wherein generating the token comprises generating, by the proxy associated with the first device, the token.

8. One or more non-transitory computer readable media storing instructions which, when executed by one or more processors of a first device associated with a user, cause the one or more processors to:

receive, from a verification computing device, a pseudorandom sequence;

based on the pseudorandom sequence, select, from a database, a plurality of parameters associated with the user;

generate, based on the plurality of parameters, a token;

transmit, to a second device, the token for authenticating the first device.

9. The one or more non-transitory computer readable media of claim 8 , storing instructions which, when executed by one or more processors, cause the one or more processors to, after transmitting the token:

receive, from the verification computing device, information indicating the first device is authenticated.

10. The one or more non-transitory computer readable media of claim 9 , storing instructions which, when executed by one or more processors, cause the one or more processors to, after transmitting the token:

receive, from the verification computing device, information indicating the first device is authenticated.

11. The one or more non-transitory computer readable media of claim 10 , storing instructions which, when executed by one or more processors, cause the one or more processors to, after transmitting the token:

transmit, to the second device, the information indicating the first device is authenticated.

12. The one or more non-transitory computer readable media of claim 8 , storing instructions which, when executed by one or more processors, cause the one or more processors to:

synchronize parameters associated with the user stored in the database with parameters associated with the user stored in a second database associated with the verification computing device.

13. The one or more non-transitory computer readable media of claim 8 , storing instructions which, when executed by one or more processors, cause the one or more processors to:

update the database with one or more of the token, metadata generated during generation of the token, or transaction information between the first device and the second device.

14. The one or more non-transitory computer readable media of claim 8 , wherein selecting the plurality of parameters comprises selecting, by a proxy associated with the first device, the plurality of parameters, and wherein generating the token comprises generating, by the proxy associated with the first device, the token.

15. A device comprising:

one or more processors;

memory storing instructions which, when executed by the one or more processors, cause the device to:

receive, from a verification computing device, a pseudorandom sequence;

based on the pseudorandom sequence, select, from a database, a plurality of parameters associated with a user;

generate, based on the plurality of parameters, a token;

transmit, to a second device, the token for authenticating the device.

16. The device of claim 15 , the memory storing instructions which, when executed by the one or more processors, cause the device to, after transmitting the token:

receive, from the verification computing device, information indicating the device is authenticated.

17. The device of claim 15 , the memory storing instructions which, when executed by the one or more processors, cause the device to, after transmitting the token:

receive, from the verification computing device, information indicating the device is authenticated; and

transmit, to the second device, the information indicating the device is authenticated.

18. The device of claim 15 , the memory storing instructions which, when executed by the one or more processors, cause the device to:

synchronize parameters associated with the user stored in the database with parameters associated with the user stored in a second database associated with the verification computing device.

19. The device of claim 15 , the memory storing instructions which, when executed by the one or more processors, cause the device to:

update the database with one or more of the token, metadata generated during generation of the token, or transaction information between the device and the second device.

20. The device of claim 15 , wherein selecting the plurality of parameters comprises selecting, by a proxy associated with the device, the plurality of parameters, and wherein generating the token comprises generating, by the proxy associated with the device, the token.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 4, 2021
From: PARKINSON, JOHN; PARK, JASON; HARRIS, DAVID
To: ALLSTATE INSURANCE COMPANY
Reel/Frame 056442/0483 →
Continuity (2)
Continuation 16134247 · Sep 18, 2018
Related Publication 20210359992A1 · Nov 18, 2021