IP Library Granted Patent US 10,505,928
Granted Patent B2
US 10,505,928 · App. 15/888,174 · Granted Dec 10, 2019

Facilitation of service login

Inventors: Richard Stephen Allinson (Morgan Hill, CA); Chris Stoner (San Jose, CA); Manoj Palki (Santa Clara, CA)
Assignee: Oath Inc.
H04L63/0853G06F21/34H04L9/3234H04L63/083H04L63/0884
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 10,505,928
App. No.
15/888,174
Granted
Dec 10, 2019
Kind
B2
Abstract

As provided herein, a first device may be registered as authorized to authenticate a user login into a service from a second device (e.g., a smart phone may be used to log the user into a webmail service on a computer without the user having to enter a password through the computer). Responsive to the user attempting to access the service through the second device, a login interface may be displayed on the first device. The user may confirm or deny that the user wants to log into the service on the second device, thus allowing the user to seamlessly log into the service on the second device (e.g., without entering a password) while mitigating unauthorized logins into the service from unknown devices. Further, the user may use the first device to delegate the authority to authenticate the user login into the service to one or more other devices.

Claims (76)

1. A system for facilitating service login, comprising:

a processor; and

memory comprising processor-executable instructions that when executed by the processor cause implementation of a service login management component configured to:

register a first device, comprising a first processor, as having authorization to authenticate a user for accessing a service from a second device comprising a second processor;

store device authorization information on the second device, the device authorization information specifying that the first device is registered as having authorization to authenticate the user;

receive an authorization delegation request, for a third device comprising a third processor, from the first device;

register the third device as having authorization to authenticate the user for accessing the service from the second device;

determine a first viability score of the first device corresponding to the user;

determine a second viability score of the third device corresponding to the user;

select, from amongst a plurality of devices comprising the first device and the third device, the first device as a destination for a request based upon a comparison of the first viability score and the second viability score;

responsive to the selecting the first device, as the destination for the request, from amongst the plurality of devices, send the request to the first device; and

responsive to receiving a login user authorization notification from the first device in response to the request sent to the first device, log the user into the service on the second device.

2. The system of claim 1 , the service login management component configured to:

maintain a count of user logins from the second device; and

responsive to the count exceeding a threshold, instruct the second device to facilitate a non-credential login with the service.

3. The system of claim 1 , the selecting based upon a determination that the first viability score is greater than the second viability score.

4. The system of claim 1 , the first device comprising a mobile phone, and the service login management component configured to:

maintain a registration of the first device within a key ring account for the user; and

responsive to receiving a phone number change request, modify the registration based upon the phone number change request.

5. The system of claim 1 , the service login management component configured to:

maintain a registration of the first device, the registration specifying a trust level for the first device; and

modify the trust level based upon at least one of successful authentication or unsuccessful authentication of the user by the first device.

6. The system of claim 5 , the service login management component configured to:

maintain a second registration of the third device, the second registration specifying a second trust level for the third device; and

responsive to the second trust level exceeding a trust level threshold, open a push channel to the third device for authenticating the user for accessing the service from the second device.

7. The system of claim 1 , the service login management component configured to perform at least one of the determining the first viability score or the determining the second viability score based upon at least one of:

a spatial proximity relative to the user, a typing characteristic of the user, a time of day, a temperature at a location of the user, user identification from imagery of the user, or voice recognition of captured audio.

8. The system of claim 1 , the service login management component configured to:

receive an access request for the service from the second device, the access request specifying a username; and

query an authorization database using the username to identify a push token,

the sending performed using the push token.

9. The system of claim 1 , the service login management component configured to:

receive an access request for the service from the second device, the access request specifying a username;

query an authorization database using the username to identify an encryption key; and

create the request using the encryption key.

10. A system for facilitating service login, comprising:

a processor; and

memory comprising instructions that when executed by the processor perform operations comprising:

registering a first device, comprising a first processor, as having authorization to authenticate a user for accessing a service from a second device comprising a second processor;

registering a third device, comprising a third processor, as having authorization to authenticate the user for accessing the service from the second device;

determining a first viability score of the first device corresponding to the user;

determining a second viability score of the third device corresponding to the user;

selecting, from amongst a plurality of devices comprising the first device and the third device, the first device as a destination for a request based upon a comparison of the first viability score and the second viability score; and

sending the request to the first device selected as the destination for the request.

11. The system of 10 , the operations comprising:

responsive to receiving a login user authorization notification from the first device in response to the request sent to the first device, logging the user into the service on the second device.

12. The system of claim 10 , the operations comprising:

maintaining a registration of the first device, the registration specifying a trust level for the first device; and

modifying the trust level based upon at least one of successful authentication or unsuccessful authentication of the user by the first device.

13. The system of claim 12 , the operations comprising:

maintaining a second registration of the third device, the second registration specifying a second trust level for the third device; and

responsive to the second trust level exceeding a trust level threshold, opening a push channel to the third device for authenticating the user for accessing the service from the second device.

14. A method for facilitating service login, comprising:

registering a first device, comprising a first processor, as having authorization to authenticate a user for accessing a service from a second device comprising a second processor;

registering a third device, comprising a third processor, as having authorization to authenticate the user for accessing the service from the second device;

determining a first viability score of the first device corresponding to the user;

determining a second viability score of the third device corresponding to the user;

selecting, from amongst a plurality of devices comprising the first device and the third device, the first device as a destination for a request based upon a comparison of the first viability score and the second viability score;

sending the request to the first device selected as the destination for the request; and

responsive to receiving a login user authorization notification from the first device in response to the request sent to the first device, logging the user into the service on the second device.

15. The method of claim 14 , comprising:

maintaining a count of user logins from the second device; and

responsive to the count exceeding a threshold, instructing the second device to facilitate non-credential logins with the service.

16. The method of claim 14 , comprising:

receiving an authorization delegation request, for the third device, from the first device.

17. The method of claim 14 , comprising:

maintaining a registration of the first device, the registration specifying a trust level for the first device; and

modifying the trust level based upon at least one of successful authentication or unsuccessful authentication of the user by the first device.

18. The method of claim 17 , comprising:

maintaining a second registration of the third device, the second registration specifying a second trust level for the third device; and

responsive to the second trust level exceeding a trust level threshold, opening a push channel to the third device for authenticating the user for accessing the service from the second device.

19. The method of claim 14 , the sending comprising:

responsive to the first viability score being greater than the second viability score, sending the request to the first device but not the third device.

20. The method of claim 14 , comprising:

receiving device authorization information for the service from the second device; and

storing the device authorization information within a login management cookie on the second device.

Assignments (5)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 28, 2024
From: YAHOO! INC.
To: YAHOO HOLDINGS, INC.
Reel/Frame 068424/0445 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 28, 2024
From: YAHOO HOLDINGS, INC.
To: OATH INC.
Reel/Frame 068426/0048 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 27, 2024
From: ALLINSON, RICHARD STEPHEN; STONER, CHRIS; PALKI, MANOJ
To: YAHOO! INC.
Reel/Frame 068415/0294 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 19, 2021
From: VERIZON MEDIA INC.
To: VERIZON PATENT AND LICENSING INC.
Reel/Frame 057453/0431 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 26, 2020
From: OATH INC.
To: VERIZON MEDIA INC.
Reel/Frame 054258/0635 →
Continuity (2)
Continuation 14671026 · Mar 27, 2015
Related Publication 20180159850A1 · Jun 7, 2018