IP Library Granted Patent US 11,188,626
Granted Patent B2
US 11,188,626 · App. 16/477,062 · Granted Nov 30, 2021

Multi-user login session

Inventors: Victor Carbune (Zurich, CH); Daniel Keysers (Stallikon, CH); Thomas Deselaers (Zurich, CH)
Assignee: Google LLC
G06F21/31H04L63/0815H04L63/102H04L63/104H04W12/068
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,188,626
App. No.
16/477,062
Filed
Jul 10, 2019
Granted
Nov 30, 2021
Kind
B2
Art Unit
2439
USPC
726/8
Abstract

An example method includes establishing a single-user login session associated with a first user-account such that the single-user login session has read and/or write access to first user data associated with the first user-account. The method further includes accepting, within the single-user login session, a further login associated with a second user-account to convert the single-user login session to a multi-user login session having read and/or write access to second user data associated with the second user-account in addition to having read and/or write access to the first user data. Computer readable media and computing devices related to the example method are disclosed herein as well.

Claims (79)

1. A method comprising:

establishing a single-user login session associated with a first user-account such that the single-user login session has read and/or write access to first user data associated with the first user-account;

accepting, within the single-user login session, a further login associated with a second user-account to convert the single-user login session to a multi-user login session having read and/or write access to second user data associated with the second user-account in addition to having read and/or write access to the first user data;

receiving, by a first computing device from a second computing device, a first user credential and a second user credential;

determining, by the first computing device, that the first user credential corresponds to a first user-account and that the second user credential corresponds to a second user-account;

in response to determining that the first user credential corresponds to the first user-account and that the second user credential corresponds to the second user-account, analyzing first data and second data, wherein the first data is access-protected via the first user credential and is associated with the first user-account, and wherein the second data is access-protected via the second user credential and is associated with the second user-account;

sending, to the second computing device, output data that is customized for both the first user-account and the second user-account based on the analysis of the first data and the second data;

receiving, from a third computing device associated with the second user-account, a request that information that is access-protected via the second user credential no longer be communicated between the first computing device and the second computing device; and

sending, to the second computing device, a notification that information that is access-protected via the second user credential is no longer to be communicated between the first computing device and the second computing device.

2. The method of claim 1 , wherein the single-user login session and the multi-user login session are both provided by an operating system.

3. The method of claim 1 , further comprising:

providing a graphical user interface for the multi-user login session; and

reading the second user data or writing to the second user data based on input received via the graphical user interface.

4. The method of claim 1 , further comprising executing, in the multi-user login session, a software application for which both the first user data and the second user data are applicable.

5. The method of claim 4 , further comprising displaying, via the application, both the first user data and the second user data that are applicable to the application.

6. The method of claim 4 , further comprising updating both the first user data and the second user data that are applicable to the application with data generated by execution of the application in the multi-user user session.

7. The method of claim 1 ,

wherein the first data comprises first calendar data and one or more first user preferences that are associated with the first user-account,

wherein the second data comprises second calendar data and one or more second user preferences that are associated with the second user-account,

wherein analyzing the first data and the second data comprises:

determining that the first calendar data and the second calendar data share a calendar entry; and

analyzing the one or more first user preferences and the one or more second user preferences, and

wherein the output data comprises a suggested venue for the shared calendar entry.

8. The method of claim 1 ,

wherein the first data comprises one or more first user preferences that are associated with the first user-account,

wherein the second data comprises one or more second user preferences that are associated with the second user-account,

wherein analyzing the first data and the second data comprises analyzing the one or more first user preferences and the one or more second user preferences, and

wherein the output data comprises a news feed comprising one or more media items that are each associated with the one or more first user preferences and the one or more second user preferences.

9. The method of claim 8 ,

wherein the one or more first user preferences comprise a first contact list and the one or more second user preferences comprise a second contact list, and

wherein the one or more media items are each associated with a respective user-account that is included in the first contact list and in the second contact list.

10. The method of claim 1 , further comprising:

receiving a search string from the second computing device,

wherein the first data comprises one or more first emails that are associated with the first user-account,

wherein the second data comprises one or more second emails that are associated with the second user-account,

wherein analyzing the first data and the second data comprises analyzing the one or more first emails and the one or more second emails, and

wherein the output data comprises at least one email from the one or more first emails or the one or more second emails, and wherein the at least one email contains the search string.

11. The method of claim 1 ,

wherein the first data comprises a first internet browsing history that is associated with the first user-account,

wherein the second data comprises a second internet browsing history that is associated with the second user-account,

wherein analyzing the first data and the second data comprises analyzing the first internet browsing history and the second internet browsing history, and

wherein the output data comprises a combined internet browsing history that includes at least a portion of the first internet browsing history and at least a portion of the second internet browsing history.

12. The method of claim 1 , further comprising: receiving, from the second computing device, a request to send the output data.

13. The method of claim 12 , wherein the request includes a message indicating that the output data is allowed to include the second data but not other data associated with the second user-account.

14. The method of claim 1 , further comprising:

determining that a predetermined amount of time passed since receiving the second user credential from the second computing device;

after determining that the predetermined amount of time passed, receiving, from the second computing device, a request to send additional output data that is customized for both the first user-account and the second user-account; and

based on determining that the predetermined amount of time passed and based on receiving the request, sending, to the second computing device, a request for the second computing device to reacquire a user credential that corresponds to the second user-account.

15. The method of claim 14 , further comprising:

receiving, from the second computing device, the requested user credential; and

in response to receiving the requested user credential, sending the additional output data.

16. The method of claim 1 , further comprising:

receiving, from a third computing device associated with the second user-account, location data indicating a location of the third computing device; and

in response to determining that the third computing device is within a threshold distance of the second computing device, sending, to the second computing device, an instruction to provide, via a user interface of the second computing device, output requesting the second user credential.

17. The method of claim 16 , further comprising:

determining that the first user-account has conducted a past multi-user login session on a shared device with the second user-account,

wherein sending the instruction comprises sending the instruction additionally in response to determining that the first user-account has conducted the past multi-user login session on the shared device with the second user-account.

18. The method of claim 16 , further comprising:

determining that the second user-account appears on a contact list of the first user-account,

wherein sending the instruction comprises sending the instruction additionally in response to determining that the second user-account appears on the contact list of the first user-account.

19. A method comprising:

establishing a single-user login session associated with a first user-account such that the single-user login session has read and/or write access to first user data associated with the first user-account;

accepting, within the single-user login session, a further login associated with a second user-account to convert the single-user login session to a multi-user login session having read and/or write access to second user data associated with the second user-account in addition to having read and/or write access to the first user data;

receiving, by a first computing device from a second computing device, a first user credential and a second user credential;

determining, by the first computing device, that the first user credential corresponds to a first user-account and that the second user credential corresponds to a second user-account;

in response to determining that the first user credential corresponds to the first user-account and that the second user credential corresponds to the second user-account, analyzing first data and second data, wherein the first data is access-protected via the first user credential and is associated with the first user-account, and wherein the second data is access-protected via the second user credential and is associated with the second user-account;

sending, to the second computing device, output data that is customized for both the first user-account and the second user-account based on the analysis of the first data and the second data;

determining that a predetermined amount of time passed since receiving the second user credential from the second computing device;

after determining that the predetermined amount of time passed, receiving, from the second computing device, a request to send additional output data that is customized for both the first user-account and the second user-account; and

based on determining that the predetermined amount of time passed and based on receiving the request, sending, to the second computing device, a request for the second computing device to reacquire a user credential that corresponds to the second user-account.

20. A method comprising:

establishing a single-user login session associated with a first user-account such that the single-user login session has read and/or write access to first user data associated with the first user-account;

accepting, within the single-user login session, a further login associated with a second user-account to convert the single-user login session to a multi-user login session having read and/or write access to second user data associated with the second user-account in addition to having read and/or write access to the first user data;

receiving, by a first computing device from a second computing device, a first user credential and a second user credential;

determining, by the first computing device, that the first user credential corresponds to a first user-account and that the second user credential corresponds to a second user-account;

in response to determining that the first user credential corresponds to the first user-account and that the second user credential corresponds to the second user-account, analyzing first data and second data, wherein the first data is access-protected via the first user credential and is associated with the first user-account, and wherein the second data is access-protected via the second user credential and is associated with the second user-account;

sending, to the second computing device, output data that is customized for both the first user-account and the second user-account based on the analysis of the first data and the second data;

receiving, from a third computing device associated with the second user-account, location data indicating a location of the third computing device; and

in response to determining that the third computing device is within a threshold distance of the second computing device, sending, to the second computing device, an instruction to provide, via a user interface of the second computing device, output requesting the second user credential.

Assignments (3)
CHANGE OF NAME Recorded Nov 22, 2019
From: GOOGLE INC
To: GOOGLE LLC
Reel/Frame 051097/0314 →
CORRECTIVE ASSIGNMENT TO CORRECT THE RECEIVING PARTY FROM GOOGLE LLC TO GOOGLE INC. PREVIOUSLY RECORDED ON REEL 049725 FRAME 0086. ASSIGNOR(S) HEREBY CONFIRMS THE RECEIVING PARTY IS GOOGLE INC.. Recorded Jul 25, 2019
From: CARBUNE, VICTOR; KEYSERS, DANIEL; DESELAERS, THOMAS
To: GOOGLE INC.
Reel/Frame 049870/0663 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 11, 2019
From: CARBUNE, VICTOR; KEYSERS, DANIEL; DESELAERS, THOMAS
To: GOOGLE LLC
Reel/Frame 049725/0086 →
Continuity (1)
Related Publication 20190342282A1 · Nov 7, 2019