Optimizing user interface data caching for future actions

• US 10,356,200 B2
• Filed: 12/28/2016
• Issued: 07/16/2019
• Est. Priority Date: 12/28/2016
• Status: Active Grant

• Current Assignee: Mariela R. Miller-Velasquez
• Original Assignee: Google LLC (Alphabet Inc.)
• Inventors: Zhang, Fan, Zhuang, Peng, Meng, Yi
• Primary Examiner(s): Zand, Davoud A
• Application Number:
  US15/392,894
• Publication Number:
  US 20180183891A1
• Time in Patent Office: 930 Days
• CPC Class Codes: G06F 12/0813 with a network or matrix configuration
• CPC Class Codes: G06F 2212/154 Networked environment
• CPC Class Codes: G06F 2212/60 Details of cache memory
• CPC Class Codes: G06F 2212/62 Details of cache specific to multiprocessor cache arrangements
• CPC Class Codes: G06F 3/0484 for the control of specific functions or operations, e.g. selecting or manipulating an object, an image or a displayed text element, setting a parameter value or selecting a range
• CPC Class Codes: H04L 67/04 specially adapted for terminals or networks with limited capabilities; specially adapted for terminal portability
• CPC Class Codes: H04L 67/125 involving control of end-device applications over a network
• CPC Class Codes: H04L 67/306 User profiles
• CPC Class Codes: H04L 67/5681 Pre-fetching or pre-delivering data based on network characteristics
• CPC Class Codes: H04W 4/60 Subscription-based services using application servers or record carriers, e.g. SIM application toolkits

Abstract

The subject matter of this specification generally relates to pre-caching data for a predicted future action. In some implementations, a client device includes a data storage device having a cache that stores data received for one or more mobile applications and a data processing apparatus that communicates with the data storage device and a display. A user interface context can be determined for a given user interface being presented for a given application. A predicted next action that a user of the client device will perform at the given user interface can be determined based on the user interface context. Prior to detecting the predicted next action, a request for next action data that will be presented in response to the user performing the predicted next action can be transmitted over a network. The next action data can be received and stored in the cache.

Claims

1. A client device, comprising:

a display that presents user interfaces for one or more mobile applications;

a data storage device having a cache that stores data received over a data communication network for the one or more mobile applications;

a data processing apparatus that communicates with the data storage device and the display, and performs operations comprising;

determining a user interface context for a given user interface being presented by the display for a given application, the user interface context for the given user interface specifying at least one of (i) a group to which data that is being presented in the given user interface belongs or (ii) a type of data that is being presented in the given user interface;

determining, based on the user interface context, a predicted next action that a user of the client device will perform at the given user interface;

transmitting, over the data communication network and prior to detecting the predicted next action, a request for next action data that will be presented in response to the user performing the predicted next action;

receiving, over the data communication network, the next action data;

storing the next action data in the cache;

determining that the next action data will be presented by a second application different from the given application;

prior to detecting the predicted next action, obtaining code for executing the second application; and

storing the code in the cache.

2. The client device of claim 1, wherein the operations further comprise:

detecting an occurrence of the predicted action at the given user interface;

obtaining the next action data from the cache; and

updating the user interface to present the next action data.

3. The client device of claim 1, wherein the user interface context specifies a rollup level of the data that is being presented in the given user interface, the rollup level specifying a hierarchical level at which the data is aggregated.

4. The client device of claim 1, wherein the predicted action next action is determined based on a number of times each action of a set of possible actions that can be performed at the given user interface has been performed by one or more users including the user when the given user interface had a context that matches the determined user interface context.

5. The client device of claim 1, wherein the operations further comprise detecting a trigger event for determining the predicted next action, wherein the predicted next action is determined in response to detecting the trigger event.

6. The client device of claim 1, wherein the operations further comprise:

obtaining a prediction model that determines the predicted next action based on the user interface context; and

converting the predictive model to mappings between predicted next actions and probabilities, each mapping being a mapping between a respective predicted next action and a probability of the respective predicted next action occurring for a given user interface context.

7. The client device of claim 6, wherein the operations further comprise selecting the predictive model from a set of predictive models based on at least one of (i) a prediction accuracy for each predictive model, (ii) a cache hit rate for each predictive model, (iii) a reduction in latency provided by each predictive model, or (iv) a number of historical user interactions performed by the user at the given user interface.

8. A system, comprising:

one or more data storage devices that store data for one or more applications;

one or more front-end servers that receive requests for next action data and provide the next action data in response to the requests; and

one or more back-end servers that communicate with the one or more front-end servers and the one or more data storage devices, the one or more back-end servers performing operations comprising;

receiving, from the one or more front-end servers, a given request for next action data that was received from a given client device, the request including user interface context data specifying at least one of (i) a group to which data that is being presented in a given user interface for a given application of the given client device belongs or (ii) a type of data that is being presented in the given user interface;

determining, based on the user interface context data, a predicted next action that a user of the given client device will perform at the given user interface;

identifying, in the one or more data storage devices, next action data for the predicted next action;

providing the identified next action data to the one or more front-end servers for transmission to the given client device, wherein the given client device stores the identified next action data in a cache of the given client device;

determining that the next action data will be presented by a second application different from the given application; and

prior to detecting the predicted next action, sending, to the given client device, code for executing the second application, wherein the given client device stores the code in the cache.

9. The system of claim 8, wherein the given client device performs operations comprising:

detecting an occurrence of the predicted action at the given user interface;

obtaining the next action data from the cache; and

updating the given user interface to present the next action data.

10. The system of claim 8, wherein the user interface context data specifies a rollup level of the data that is being presented in the given user interface, the rollup level specifying a hierarchical level at which the data is aggregated.

11. The system of claim 8, wherein the predicted action next action is determined based on a number of times each action of a set of possible actions that can be performed at the given user interface has been performed by one or more users including the user when the given user interface had a context that matches the determined user interface context.

12. The system of claim 8, wherein the operations further comprise detecting a trigger event for determining the predicted next action, wherein the predicted next action is determined in response to detecting the trigger event.

13. The system of claim 8, wherein the operations further comprise:

obtaining a prediction model that determines the predicted next action based on the user interface context; and

converting the predictive model to mappings between predicted next actions and probabilities, each mapping being a mapping between a respective predicted next action and a probability of the respective predicted next action occurring for a given user interface context.

14. The system of claim 13, wherein the operations further comprise selecting the predictive model from a set of predictive models based on at least one of (i) a prediction accuracy for each predictive model, (ii) a cache hit rate for each predictive model, (iii) a reduction in latency provided by each predictive model, or (iv) a number of historical user interactions performed by the user at the given user interface.

15. A method, comprising:

determining a user interface context for a given user interface being presented by a display of a client device for a given application, the user interface context for the given user interface specifying at least one of (i) a group to which data that is being presented in the given user interface belongs or (ii) a type of data that is being presented in the given user interface;

determining, based on the user interface context, a predicted next action that a user of the client device will perform at the given user interface;

transmitting, over the data communication network and prior to detecting the predicted next action, a request for next action data that will be presented in response to the user performing the predicted next action;

receiving, over the data communication network, the next action data; and

storing the next action data in the cache;

determining that the next action data will be presented by a second application different from the given application;

prior to detecting the predicted next action, obtaining code for executing the second application; and

storing the code in the cache.

16. The method of claim 15, further comprising:

detecting an occurrence of the predicted action at the given user interface;

obtaining the next action data from the cache; and

updating the user interface to present the next action data.

17. The method of claim 15, wherein the user interface context specifies a rollup level of the data that is being presented in the given user interface, the rollup level specifying a hierarchical level at which the data is aggregated.

18. The method of claim 15, wherein the predicted action next action is determined based on a number of times each action of a set of possible actions that can be performed at the given user interface has been performed by one or more users including the user when the given user interface had a context that matches the determined user interface context.