IP Library › Granted Patent US 12,199,982
Granted Patent B2
US 12,199,982 · App. 18/453,087 · Granted Jan 14, 2025

Friction-less identity proofing during employee self-service registration

Inventors: Kalyan Vbh (Hyderabad, IN); Frank Villavicencio (Roseland, NJ); Pavan Katamveera (Hyderabad, IN)
Assignee: ADP, Inc.
H04L63/0884H04L63/0807H04L63/083H04L63/1433
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,199,982
App. No.
18/453,087
Granted
Jan 14, 2025
Kind
B2
Abstract

A method for proving identity when registering for a service includes presenting by the entity a user with options for registering for the service, wherein the options comprise validating an identity of the user through a trusted partner. The method includes receiving, by the entity, user data from the trusted partner responsive to the user logging into a page on the trusted partner. The method includes validating the user identity for the service responsive to a determination that a user identifier from the trusted partner matches a user identifier on record with the entity. The method includes populating entity user data for the service according to the user data received from the trusted partner responsive to successfully validation of the user identity. In embodiments, a risk analysis score is determined for the user and registration steps for registering are selected based on comparison of the registration score with a threshold.

Claims (65)

1. A system, comprising:

one or more processors, coupled with memory, to:

receive, in response to a request to register for a service provided by an entity, identifying information from a user of a client device;

generate, via application of an artificial intelligence analysis to the identifying information, a score;

update, based on changes in information comprising previous locations of the client device that performed attempts to register to the service provided by the entity, a threshold risk score used to identify low risk or high risk authentications;

determine, based on a comparison of the score with the threshold risk score, to allow or not allow the user to register for the service provided by the entity; and

provide, to the client device based on the determination to allow or not allow the user, a response to the request to register for the service.

2. The system of claim 1 , wherein the one or more processors are further configured to:

provide, for presentation via the client device, a plurality of options configured to register the user for the service; and

receive, responsive to selection of an option of the plurality of options, the identifying information from the client device.

3. The system of claim 1 , wherein the one or more processors are further configured to:

provide, for presentation via the client device, a plurality of options configured to register the user for the service, the plurality of options comprising a first option to validate via a trusted partner and a second option to validate via the identifying information; and

receive, responsive to selection of the second option of the plurality of options, the identifying information from the client device.

4. The system of claim 1 , wherein the one or more processors are further configured to:

determine the score satisfies the threshold risk score based on the comparison;

authenticate, responsive to the determination that the score satisfies the threshold risk score, the user to register for the service provided by the entity; and

allow, responsive to the authentication, the user to register for the service.

5. The system of claim 1 , wherein the one or more processors are further configured to:

determine the score is less than or equal to the threshold risk score based on the comparison; and

allow, responsive to the score being less than or equal to the threshold risk score, the user to register for the service.

6. The system of claim 1 , wherein the one or more processors are further configured to:

determine the score does not satisfy the threshold risk score based on the comparison; and

prevent, responsive to the determination, the user from registering for the service.

7. The system of claim 1 , wherein the one or more processors are further configured to:

determine the score is greater than the threshold risk score based on the comparison; and

prevent, responsive to the score being greater than the threshold risk score, the user from registering for the service.

8. The system of claim 1 , wherein the one or more processors are further configured to:

determine the score does not satisfy the threshold risk score based on the comparison; and

select a different authentication option for the user responsive to the determination the score does not satisfy the threshold risk score, wherein the different authentication option comprises at least one of an on-the-fly registration via a personal registration code or a knowledge based authentication.

9. The system of claim 1 , wherein the one or more processors are further configured to:

dynamically update the threshold risk score based on additional information received for the client device.

10. The system of claim 1 , wherein the one or more processors are further configured to:

determine one or more of the previous locations of the client device based on an IP address of the client device.

11. A method, comprising:

receiving, by one or more processors coupled with memory, in response to a request to register for a service provided by an entity, identifying information from a user of a client device;

generating, by the one or more processors via application of an artificial intelligence analysis to the identifying information, a score;

updating, by the one or more processors based on changes in information comprising previous locations of the client device that performed attempts to register to the service provided by the entity, a threshold risk score used to identify low risk or high risk authentications;

determining, by the one or more processors based on a comparison of the score with the threshold risk score, to allow or not allow the user to register for the service provided by the entity; and

providing, by the one or more processors to the client device based on the determination to allow or not allow the user, a response to the request to register for the service.

12. The method of claim 11 , comprising:

providing, by the one or more processors for presentation via the client device, a plurality of options configured to register the user for the service; and

receiving, by the one or more processors responsive to selection of an option of the plurality of options, the identifying information from the client device.

13. The method of claim 11 , comprising:

providing, by the one or more processors for presentation via the client device, a plurality of options configured to register the user for the service, the plurality of options comprising a first option to validate via a trusted partner and a second option to validate via the identifying information; and

receiving, by the one or more processors responsive to selection of the second option of the plurality of options, the identifying information from the client device.

14. The method of claim 11 , comprising:

determining, by the one or more processors, the score satisfies the threshold risk score based on the comparison;

authenticating, by the one or more processors, responsive to the determination that the score satisfies the threshold risk score, the user to register for the service provided by the entity; and

allowing, by the one or more processors responsive to the authentication, the user to register for the service.

15. The method of claim 11 , comprising:

determining, by the one or more processors, the score is less than or equal to the threshold risk score based on the comparison; and

allowing, by the one or more processors, responsive to the score being less than or equal to the threshold risk score, the user to register for the service.

16. The method of claim 11 , comprising:

determining, by the one or more processors, the score does not satisfy the threshold risk score based on the comparison; and

preventing, by the one or more processors responsive to the determination, the user from registering for the service.

17. The method of claim 11 , comprising:

determining, by the one or more processors, the score is greater than the threshold risk score based on the comparison; and

preventing, by the one or more processors, responsive to the score being greater than the threshold risk score, the user from registering for the service.

18. The method of claim 11 , comprising:

determining, by the one or more processors, the score does not satisfy the threshold risk score based on the comparison; and

selecting, by the one or more processors, a different authentication option for the user responsive to the determination the score does not satisfy the threshold risk score, wherein the different authentication option comprises at least one of an on-the-fly registration via a personal registration code or a knowledge based authentication.

19. The method of claim 11 , comprising:

dynamically updating, by the one or more processors, the threshold risk score based on additional information received for the client device.

20. The method of claim 11 , comprising:

determining, by the one or more processors, one or more of the previous locations of the client device based on an IP address of the client device.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 10, 2024
From: VBH, KALYAN; VILLAVICENCIO, FRANK; KATAMVEERA, PAVAN
To: ADP, INC.
Reel/Frame 069541/0915 →
Continuity (2)
Continuation 16376882 · Apr 5, 2019
Related Publication 20230403276A1 · Dec 14, 2023
References Cited (28)
US 8745698B1 · Ashfield et al. · 2014 [cited by applicant]
US 9348981B1 · Hearn et al. · 2016 [cited by applicant]
US 9660989B1 · Fredinburg et al. · 2017 [cited by applicant]
US 11736481B2 · Vbh · 2023 [cited by examiner]
US 20030135734A1 · Fagan et al. · 2003 [cited by applicant]
US 20060021004A1 · Moran et al. · 2006 [cited by applicant]
US 20110307381A1 · Kim et al. · 2011 [cited by applicant]
US 20130086657A1 · Srinivasan et al. · 2013 [cited by applicant]
US 20140259135A1 · Postrel · 2014 [cited by applicant]
US 20160269379A1 · Livesay et al. · 2016 [cited by applicant]
US 20180013565A1 · Fox et al. · 2018 [cited by applicant]
US 20180268056A1 · Gharabegian · 2018 [cited by applicant]
US 20180343246A1 · Benayed · 2018 [cited by applicant]
US 20190266314A1 · Trelin · 2019 [cited by applicant]
US 20190356679A1 · Sites et al. · 2019 [cited by applicant]
US 20190384794A1 · Holly et al. · 2019 [cited by applicant]
US 20200244640A1 · Itzhaki et al. · 2020 [cited by applicant]
US 20200302543A1 · Corretjer et al. · 2020 [cited by applicant]
US 20210056562A1 · Hart et al. · 2021 [cited by applicant]
CN 106982193A · 2017 [cited by applicant]
“Enable Seamless, Secure Access with Adaptive Authentication and Authorization,” Ping Identity, Aug. 2017, 13 pages. [cited by applicant]
Notice of Allowance issued in U.S. Appl. No. 16/376,882 dated Apr. 7, 2023 (8 pages). [cited by applicant]
SecureKey Concierge, Did You Know, 2017, SecureKey Technologies, 3 pages, http://1h7gwkpz6sk2qtcdf2oqmto1-,wpengine.netdna-ssl.com/wp contenl/uploads/sites/3/2017 /02/did-you-know-trifold-brochure-2017-WEB.pdf. [cited by applicant]
U.S. Office Action issued in U.S. Appl. No. 16/376,882, dated Dec. 23, 2022 (31 pages). [cited by applicant]
U.S. Office Action issued in U.S. Appl. No. 16/376,882, dated Jan. 5, 2022 (28 pages). [cited by applicant]
U.S. Office Action issued in U.S. Appl. No. 16/376,882, dated Jul. 26, 2022 (30 pages). [cited by applicant]
U.S. Office Action issued in U.S. Appl. No. 16/376,882, dated Jun. 25, 2021 (22 pages). [cited by applicant]
U.S. Office Action issued in U.S. Appl. No. 16/376,882, dated May 9, 2022 (32 pages). [cited by applicant]