IP Library Granted Patent US 12,022,282
Granted Patent B2
US 12,022,282 · App. 17/561,616 · Granted Jun 25, 2024

Anonymous authentication and remote wireless token access

Inventor: Andrew Robert Rolfe (Deerfield, IL)
Assignee: Prove Identity, Inc.
H04W12/06G06Q20/3226G06Q20/3829G06Q40/02H04L9/3215H04L9/3228H04L9/3231H04L9/3234H04L9/3236H04L9/3242H04L63/0428H04L63/0442H04L63/0861H04L63/0876H04L63/0884H04W12/02H04W12/033H04L63/061H04L2209/24H04L2209/80H04L2209/805H04W4/80H04W12/04
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,022,282
App. No.
17/561,616
Granted
Jun 25, 2024
Kind
B2
Abstract

Provided is a method for operating an authentication server for authenticating a user who is communicating with an enterprise via a network. The method include receiving, via the network, a first authenticator including first information from a low energy wireless device received via a user device wirelessly, and storing the first authenticator. When the authentication service later receives, from the enterprise, a request to authenticate the user, the authentication server transmits an authentication request to the user device via the network requesting that the user read information from the low energy wireless device using the user device. The information received from the low energy wireless device in response to the authentication request is then used authenticate the user by comparing the information received from the low energy wireless device due to the authentication request with the stored first authenticator.

Claims (68)

1. A method of authenticating a user communicating with an enterprise, comprising:

receiving, from the enterprise, a request to authenticate the user, the request comprising a relationship identifier;

identifying a user device identifier and one or more stored user credentials based, at least in part, on the relationship identifier, wherein:

the one or more stored user credentials include one or more user authenticator parameters to authenticate the user, and

the one or more user authenticator parameters comprise one or more biometric authenticators, one or more possession authenticators, and/or one or more knowledge based authenticators;

transmitting an authentication request to a user device based, at least in part, on the user device identifier; and

responsive to receiving a response from the user device to the authentication request, authenticating the user based, at least in part, on the one or more user authenticator parameters, wherein:

the one or more user authenticator parameters are stored via an authenticator,

a true identity of the user is stored via the enterprise, and

neither the enterprise nor the authenticator has access to both the one or more user authenticator parameters and the true identity.

2. The method of claim 1 , further comprising:

obtaining a one-time code, via a user interface of the user device; and

associating, via the relationship identifier, the user device with the enterprise.

3. The method of claim 2 , further comprising:

transmitting the relationship identifier to the user device via a secure connection.

4. The method of claim 1 , further comprising:

the authenticator anonymously aggregating the one or more stored user credentials prior to receiving the request to authenticate the user.

5. The method of claim 4 , wherein aggregating the one or more stored user credentials comprises:

obtaining a biometric credential.

6. The method of claim 5 , wherein obtaining the biometric credential comprises operating an application on a mobile communications device used by the user to communicate with the enterprise.

7. The method of claim 1 , further comprising:

establishing the relationship identifier between the user and the authenticator; and

associating the relationship identifier between the user and the authenticator via a set of enrolled credentials.

8. An apparatus to authenticate a user communicating with an enterprise, comprising:

one or more processors, coupled to at least one memory device, to:

receive, from the enterprise, a request to authenticate the user, the request comprising a relationship identifier;

identify a user device identifier and one or more stored user credentials based, at least in part, on the relationship identifier, wherein:

the one or more stored user credentials to include one or more user authenticator parameters to authenticate the user, and

the one or more user authenticator parameters comprise one or more biometric authenticators, one or more possession authenticators, and/or one or more knowledge based authenticators;

transmit an authentication request to a user device based, at least in part, on the user device identifier; and

responsive to receipt of a response from the user device to the authentication request, authenticate the user based, at least in part, on the one or more user authenticator parameters, wherein:

the one or more user authenticator parameters are stored via an authenticator,

a true identity of the user is stored via the enterprise, and

neither the enterprise nor the authenticator has access to both the one or more user authenticator parameters and the true identity.

9. The apparatus of claim 8 , wherein the one or more processors, coupled to the at least one memory device, are additionally to:

obtain a one-time code, via a user interface of the user device; and

associate, via the relationship identifier, the user device with the enterprise.

10. The apparatus of claim 9 , wherein the one or more processors, coupled to the at least one memory device, are additionally to:

transmit the relationship identifier to the user device via a secure connection.

11. The apparatus of claim 8 , wherein the one or more processors, coupled to the at least one memory device, are additionally to:

anonymously aggregate the one or more stored user credentials prior to receiving the request to authenticate the user, wherein the aggregating the one or more stored user credentials operates to obtain a biometric credential.

12. The apparatus of claim 11 , wherein the one or more processors, coupled to the at least one memory device, are additionally to:

obtain the biometric credential via an application on a mobile communications device used by the user to communicate with the enterprise.

13. The apparatus of claim 8 , wherein the one or more processors, coupled to the at least one memory device, are additionally to:

establish the relationship identifier between the user and the authenticator; and

associate the relationship identifier between the user and the authenticator via a set of enrolled credentials.

14. An article comprising:

a non-transitory computer-readable media having instructions encoded thereon which, when executed by a processor coupled to at least one memory device direct the processor to:

receive, from an enterprise, a request to authenticate a user, the request comprising a relationship identifier;

identify a user device identifier and one or more stored user credentials based, at least in part, on the relationship identifier, wherein:

the one or more stored user credentials to include one or more user authenticator parameters to authenticate the user, and

the one or more user authenticator parameters to comprise one or more biometric authenticators, one or more possession authenticators, and/or one or more knowledge based authenticators;

transmit an authentication request to a user device based, at least in part, on the user device identifier; and

responsive to receipt of a response from the user device to the authentication request, authenticate the user based, at least in part, on the one or more user authenticator parameters, wherein:

the one or more user authenticator parameters are stored via an authenticator,

a true identity of the user is stored via the enterprise, and

neither the enterprise nor the authenticator has access to both the one or more user authenticator parameters and the true identity.

15. The article of claim 14 , wherein the encoded instructions are additionally to direct the processor to:

obtain a one-time code, via a user interface of the user device; and

associate, via the relationship identifier, the user device with the enterprise.

16. The article of claim 15 , wherein the encoded instructions are additionally to direct the processor to:

transmit the relationship identifier to the user device via a secure connection.

17. The article of claim 14 , wherein the encoded instructions are additionally to direct the processor to:

anonymously aggregate the one or more stored user credentials prior to receiving the request to authenticate the user.

18. The article of claim 14 , wherein the encoded instructions are additionally to direct the processor to:

obtain a biometric credential via operating an application on a mobile communications device used by the user to communicate with the enterprise.

19. The article of claim 14 , wherein the encoded instructions are additionally to direct the processor to:

establish the relationship identifier between the user and the authenticator; and to associate the relationship identifier between the user and the authenticator via a set of enrolled credentials.

Assignments (5)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 23, 2022
From: ROLFE, ANDREW ROBERT
To: EARLY WARNING SYSTEMS, LLC
Reel/Frame 061192/0545 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 23, 2022
From: ROLFE, ANDREW ROBERT
To: AUTHENTIFY, INC.
Reel/Frame 061192/0572 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 23, 2022
From: AUTHENTIFY, LLC
To: EARLY WARNING SERVICES, LLC
Reel/Frame 061192/0624 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 23, 2022
From: EARLY WARNING SERVICES, LLC
To: PAYFONE, INC.
Reel/Frame 061192/0683 →
CHANGE OF NAME Recorded Sep 23, 2022
From: PAYFONE, INC.
To: PROVE IDENTITY, INC.
Reel/Frame 061535/0300 →
Continuity (4)
Continuation 16521374 · Jul 24, 2019
Continuation 15443900 · Feb 27, 2017
Continuation 14687327 · Apr 15, 2015
Related Publication 20220201477A1 · Jun 23, 2022
Cited By (2)
US 12,437,109 US 12,455,949