Identifiers across application instances

• US 10,409,657 B2
• Filed: 01/13/2017
• Issued: 09/10/2019
• Est. Priority Date: 01/15/2016
• Status: Active Grant

• Current Assignee: Google LLC (Alphabet Inc.)
• Original Assignee: Google LLC (Alphabet Inc.)
• Inventors: Kirkpatrick, Ficus, Ganapathy, Subramaniam
• Primary Examiner(s): Keehn, Richard G
• Application Number:
  US15/406,527
• Publication Number:
  US 20170208137A1
• Time in Patent Office: 970 Days
• CPC Class Codes: G06F 8/61 Installation
• CPC Class Codes: G06F 8/65 Updates security arrangements therefor G06F21/57
• CPC Class Codes: G06F 9/445 Program loading or initiating bootstrapping G06F9/4401; security arrangements for program loading or initiating G06F21/57
• CPC Class Codes: G06F 9/44505 Configuring for program initiating, e.g. using registry, configuration files
• CPC Class Codes: G06F 9/44521 Dynamic linking or loading; Link editing at or after load time, e.g. Java class loading
• CPC Class Codes: G06F 9/546 Message passing systems or structures, e.g. queues
• CPC Class Codes: H04L 41/02 Standardisation; Integration
• CPC Class Codes: H04L 67/142 Managing session states for stateless protocols; Signalling session states; State transitions; Keeping-state mechanisms
• CPC Class Codes: H04L 67/146 Markers for unambiguous identification of a particular session, e.g. session cookie or URL-encoding
• CPC Class Codes: H04L 67/148 Migration or transfer of sessions
• CPC Class Codes: H04L 67/34 involving the movement of software or configuration parameters network booting or remote initial program loading [RIPL] G06F9/4416

Abstract

In some examples, a method includes receiving, by a supervisor component executing at a computing device, a request to execute an application, determining a current user of the computing device, and determining a reset state of the application. The method may also include generating, based on the current user of the computing device, the reset state, and an application identifier for the application, a unique identifier that does not include personally identifiable information for the current user, sending, to an application service provider, the unique identifier and one or more requests for information, and, responsive to sending the one or more request for information, receiving, from the application service provider, state information associated with the current user and for the application.

Claims

1. A method comprising:

receiving, by a supervisor component executing at a computing device, a request to execute an application;

responsive to determining that an application container for maintaining installable sub-packages of the application is allocated in memory of the computing device;

determining, by a container runtime of the application container, a current user of the computing device;

determining, by the container runtime, a reset state of the application; and

generating, by the container runtime and based on the current user of the computing device, the reset state, and an application identifier for the application, a unique identifier that does not include personally identifiable information for the current user;

sending, by the computing device and to an application service provider, the unique identifier and one or more requests for information; and

responsive to sending the one or more request for information, receiving, by the computing device and from the application service provider, state information associated with the current user and for the application.

2. The method of claim 1, wherein the request to execute the application is a first request to execute the application, and wherein the application container is a first application container, the method further comprising:

deallocating, by the supervisor component, the first application container for maintaining the installable sub-packages of the application;

after deallocating the first application container, receiving, by the computing device, a second request to execute the application;

responsive to receiving the second request to execute the application;

allocating, by the supervisor component, a second application container for maintaining the installable sub-packages of the application;

installing, by the second application container, one or more of the installable sub-packages of the application required to perform functionality of the application specified in the second request to execute the application;

determining, by a container runtime of the second application container, an updated current user of the application, wherein the updated current user is the same as the current user;

determining, by the container runtime, an updated reset state of the application, wherein the reset state is the same as the updated reset state;

generating, by a container runtime of the application container and based on the updated current user and the updated reset state, an updated unique identifier that does not include personally identifiable information for the updated current user, wherein the updated unique identifier is the same as the unique identifier;

sending, by the computing device and to the application service provider, the updated unique identifier; and

receiving, by the computing device and from the application service provider, the state information associated with the current user and for the application.

3. The method of claim 1, wherein the unique identifier is a first unique identifier, and wherein the computing device is a first computing device, the method further comprising:

receiving, by a second computing device, a request to execute a different instance of the application;

determining, by the second computing device, a current user of the second computing device;

determining, by the second computing device, a reset state of the application on the second device;

generating, by the second computing device and based on the current user of the second computing device and the reset state of the application on the second device, a second unique identifier that does not include personally identifiable information for the current user, wherein the first unique identifier and the second unique identifier are the same when the reset state and the updated reset state are the same, and wherein the first unique identifier and the second unique identifier are different when the reset state is different from the updated reset state;

sending, by the second computing device and to the application service provider, the second unique identifier; and

if the first unique identifier and the second unique identifier are the same, receiving, by the second computing device and from the application service provider, information about the one or more application requests.

4. The method of claim 1, wherein the unique identifier is a first unique identifier, the method further comprising:

receiving, by the computing device, a request to reset a state of the application;

updating, by the computing device, the reset state of the application;

generating, by the computing device and based on the current user of the computing device and the updated reset state of the application, a second unique identifier that does not include personally identifiable information for the current user, wherein the first unique identifier and the second unique identifier are different; and

sending, by the computing device and to an application service provider, the second unique identifier such that, after resetting the state of the application, the current user appears to be a different user to the application service provider.

5. The method of claim 4, wherein the computing device is a first computing device, and wherein a second computing device is associated with the current user, the method further comprising:

sending, from the first computing device and to the second computing device, the request to reset the state of the application; and

responsive to receiving the request to reset the state of the application, updating, by the second computing device, the reset state of the application at the second computing device to be the same as the reset state of the application at the first computing device.

6. The method of claim 1, wherein generating the unique identifier comprises hashing a tuple including a user identifier, an application identifier, and a reset state.

7. The method of claim 1, wherein the state information includes one or more of information about a current state of the application, historical application usage information of the current user for the application, and user preference information of the user for the application.

8. A computing device comprising:

one or more storage devices that store a supervisor component; and

one or more processors that execute the supervisor component to;

receive a request to execute an application; and

determine whether an application container for maintaining installable sub-packages of the application is allocated in the one or more storage devices,

wherein the one or more processors execute the application container to, responsive to determining that an application container for maintaining installable sub-packages of the application is allocated in the one or more storage devices;

determine a current user of the computing device;

determine a reset state of the application;

generate, based on the current user of the computing device, the reset state, and an application identifier for the application, a unique identifier that does not include personally identifiable information for the current user;

send, to an application service provider, the unique identifier and one or more requests for information; and

responsive to sending the one or more request for information, receive, from the application service provider, state information associated with the current user and for the application.

9. The computing device of claim 8, wherein:

the request to execute the application is a first request to execute the application,

the application container is a first application container,

the one or more processors execute the supervisor component to;

deallocate the first application container for maintaining the installable sub-packages of the application;

after deallocating the first application container, receive a second request to execute the application; and

responsive to receiving the second request to execute the application, allocate a second application container for maintaining the installable sub-packages of the application; and

the one or more processors execute the second application container to;

install one or more of the installable sub-packages of the application required to perform functionality of the application specified in the second request to execute the application;

determine an updated current user of the application, wherein the updated current user is the same as the current user;

determine an updated reset state of the application, wherein the reset state is the same as the updated reset state;

generate, based on the updated current user and the updated reset state, an updated unique identifier that does not include personally identifiable information for the updated current user, wherein the updated unique identifier is the same as the unique identifier;

send, to the application service provider, the updated unique identifier; and

receive, from the application service provider, the state information associated with the current user and for the application.

10. The computing device of claim 8, wherein the unique identifier is a first unique identifier, and wherein the one or more processors execute the application container to:

receive a request to reset a state of the application;

update the reset state of the application;

generate, based on the current user of the computing device and the updated reset state of the application, a second unique identifier that does not include personally identifiable information for the current user, wherein the first unique identifier and the second unique identifier are different; and

send, to an application service provider, the second unique identifier such that, after resetting the state of the application, the current user appears to be a different user to the application service provider.

11. The computing device of claim 10, wherein the one or more processors execute the application container to:

send, from the computing device and to a different computing device associated with the current user of the computing device, the request to reset the state of the application, wherein the different computing device, in response to receiving the request to rest the state of the application, updates a reset state of the application at the different device to be the same as the reset state of the application at the computing device.

12. The computing device of claim 8, wherein the one or more processors execute the application container to generate the unique identifier by at least executing the application container to apply a hash function to a tuple including a user identifier, an application identifier, and a reset state.

13. The computing device of claim 8, wherein the state information includes one or more of information about a current state of the application, historical application usage information of the current user for the application, and user preference information of the user for the application.

14. A method comprising:

receiving, by a computing system and from an application executing at a first computing device, an identifier that does not include personally identifying information for a user of the first computing device;

receiving, by the computing system and from the application executing at the first computer, one or more requests for information, the one or more requests including a request for user preference information;

updating, by the computing system and based on information about the one or more requests and the identifier, one or more historical request information associated with the identifier, the historical request information including state information of the application and user preference information associated with the identifier;

receiving, by the computing system and from an application executing at a second computing device, the identifier, wherein the application executing on the first computing device and the application executing on the second computing device are different instances of a single application;

determining, by the computing system and based on the identifier, user preference information included in the historical request information associated with the identifier;

sending, by the computing system and to the second computing device, at least portion of the user preference information included in the historical request information associated with the identifier;

receiving, by the computing system and from the application executing at the first computing device, one or more additional requests for the information, the one or more additional requests include a different identifier that does not include personally identifiable information for the user of the first computing device;

determining, by the computing system and based on the different identifier, different user preference information included in historical request information associated with the different identifier; and

sending, by the computing system and to the second computing device, at least a portion of the different user preference information.

15. The method of claim 14, further comprising:

determining, by the computing system and based on the one or more requests for the information and the identifier, the information; and

sending, by the computing system and to the first computing device, at least a portion of the information.

16. The method of claim 14, wherein the historical request information further includes one or more of information about a current state of the application, and application usage information.

17. The method of claim 14, wherein the identifier is generated by at least hashing a tuple including a user identifier, an application identifier, and a reset state.

18. The method of claim 14, wherein the first computing device and the second computing device are the same computing device, and wherein the different instance of the application executing at the second computing device is an instance of the application executing on the same computing device after reinstallation of the application.