Smart cache warming

• US 9,485,640 B2
• Filed: 03/28/2011
• Issued: 11/01/2016
• Est. Priority Date: 03/28/2011
• Status: Active Grant

• Current Assignee: Google LLC (Alphabet Inc.)
• Original Assignee: Google Inc. (Alphabet Inc.)
• Inventors: Bowers, Andrew, Tom, Kevin
• Primary Examiner(s): Rojas, Midys
• Assistant Examiner(s): Matin, Tasnima
• Application Number:
  US13/073,473
• Publication Number:
  US 20150208219A1
• Time in Patent Office: 2,045 Days
• Field of Search: None
• US Class Current: 1/1
• CPC Class Codes: G06F 12/0862 with prefetch
• CPC Class Codes: G06F 2212/1021 Hit rate improvement
• CPC Class Codes: G06F 2212/1024 Latency reduction
• CPC Class Codes: G06F 2212/171 Portable consumer electronics, e.g. mobile phone
• CPC Class Codes: G06F 2212/602 Details relating to cache prefetching
• CPC Class Codes: G06F 2212/6024 History based prefetching
• CPC Class Codes: G06F 2212/6026 Prefetching based on access pattern detection, e.g. stride based prefetch
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/535 Tracking the activity of the user network monitoring arrangements H04L43/00; recording of computer activity G06F11/34
• CPC Class Codes: H04L 67/5681 Pre-fetching or pre-delivering data based on network characteristics
• CPC Class Codes: H04W 4/029 Location-based management or tracking services
• CPC Class Codes: H04W 4/18 Information format or content conversion, e.g. adaptation by the network of the transmitted or received information for the purpose of wireless delivery to users or terminals

Abstract

According to one general aspect, a method of preemptively caching data within a mobile device may include detecting that a triggering event has occurred. The method may also include, in response to the triggering event, automatically performing an action associated with the triggering event, wherein the action includes retrieving anticipated data from a remote device. The method may include caching at least part of the anticipated data within a memory of the mobile device. The method may include receiving a request, from a user, for requested data, wherein the requested data includes at least a portion of the anticipated data. The method may include fulfilling at least part of the request for the requested data by retrieving the anticipated data portion of the requested data from the memory of the mobile device.

Claims

1. A method of preemptively caching data within a mobile device, the method comprising:

monitoring a user'"'"'s behavior in regards to a mobile device;

determining one or more user habits based upon the monitored user'"'"'s behavior;

either creating or modifying at least one triggering event associated with a respective determined user habit;

either creating or modifying an action based upon the respective determined user habit by creating and storing a triggering event and action pair such that the action is associated with a respective triggering event;

detecting that a triggering event has occurred, wherein the triggering event includes a predicted reduction in the mobile device'"'"'s system resources and the predicted reduction in system resources includes a prediction of transitioning the mobile device from AC power to battery power;

in response to the triggering event, automatically performing the action associated with the triggering event using the stored triggering event and action pair, wherein the action includes retrieving anticipated data from a remote device before the predicted reduction in the mobile device'"'"'s system resources occurs;

caching at least part of the anticipated data within a memory of the mobile device;

receiving a request, from a user, for requested data, wherein the requested data includes at least a portion of the anticipated data; and

fulfilling at least part of the request for the requested data by retrieving the anticipated data portion of the requested data from the memory of the mobile device.

2. The method of claim 1, wherein the triggering event includes a time of day;

and

wherein the action associated with the triggering event includes;

retrieving data from a plurality of news-related Internet sites, and

determining an at least a first portion of the retrieved data to cache as anticipated data and a second portion of the retrieved data to not cache as anticipated data.

3. The method of claim 1, wherein caching at least part of the anticipated data comprises:

transmitting the cached anticipated data to a remote server, wherein the remote server is configured to synchronize the anticipated data across a plurality of devices.

4. The method of claim 1, wherein the triggering event includes an upcoming calendar appointment, wherein the upcoming calendar appointment is associated with a location;

and

wherein the action associated with the triggering event includes;

retrieving traveling directions from a first location to the location associated with the upcoming calendar appointment.

5. The method of claim 1, wherein the triggering event includes an upcoming calendar appointment, wherein the upcoming calendar appointment is associated with one or more files;

and

wherein the action associated with the triggering event includes;

retrieving the one or more of the files associated with the upcoming calendar appointment.

6. The method of claim 1, wherein the triggering event includes a change in location of the mobile device;

and

wherein the action includes retrieving anticipated data based upon the new location of the mobile device.

7. The method of claim 1, wherein the triggering event includes a first time of day;

and

wherein creating or modifying the triggering event associated with the respective determined user habit includes;

modifying a trigger event to include a second time of day such that the action associated with trigger event consumes less system resources than if it occurred at the first time of day.

8. The method of claim 1, wherein the action includes one of:

trans-coding a video, synchronizing multimedia playlists, and performing a network action.

9. A mobile computing device comprising:

a user habit monitor configured to;

monitor a user'"'"'s behavior in regards to a mobile computing device;

determine one or more user habits based upon the monitored user'"'"'s behavior;

either create or modify at least one triggering event associated with a respective determined user habit;

either create or modify an action based upon the respective determined user habit by creating and storing a triggering event and action pair such that the action is associated with a respective triggering event;

an anticipated data pre-loader configured to;

detect that a triggering event has occurred, wherein the triggering event includes a prediction of a reduction in the system resources of the mobile computing device and the predicted reduction in system resources includes a prediction of transitioning the mobile device from AC power to battery power, and

in response to the triggering event, automatically perform the action associated with the triggering event using the stored triggering event and action pair, wherein the action includes retrieving anticipated data from a remote device before the predicted reduction in system resources occurs;

a memory configured to;

cache at least part of the anticipated data; and

a processor configured to execute machine readable instructions which when executed cause the mobile computing device to;

receive a request, from a user, for requested data, wherein the requested data includes at least a portion of the anticipated data, and

fulfill at least part of the request for the requested data by retrieving the anticipated data portion of the requested data from the memory.

10. The mobile computing device of claim 9, wherein the triggering event includes a time of day;

and

wherein the action associated with the triggering event causes the mobile computing device to;

retrieve data from a plurality of news-related Internet sites, and

determine at least a first portion of the retrieved data to cache as anticipated data and a second portion of the retrieved data to not cache as anticipated data.

11. The mobile computing device of claim 9, wherein the anticipated data pre-loader is configured to:

transmit the anticipated data to a remote server, wherein the remote server is configured to synchronize the anticipated data across a plurality of devices.

12. The mobile computing device of claim 9, wherein the triggering event includes an upcoming calendar appointment, wherein the upcoming calendar appointment is associated with a location;

and

wherein the action associated with the triggering event causes the mobile computing device to;

retrieve traveling directions from a first location to the location associated with the upcoming calendar appointment.

13. The mobile computing device of claim 9, wherein the triggering event includes an upcoming calendar appointment, wherein the upcoming calendar appointment is associated with one or more files;

and

wherein the action associated with the triggering event causes the mobile computing device to;

retrieve the one or more of the files associated with the upcoming calendar appointment.

14. The mobile computing device of claim 9, wherein the triggering event includes a change in location of the mobile computing device;

and

wherein the action causes the mobile computing device to;

retrieve anticipated data based upon the new location of the mobile computing device.

15. The mobile computing device of claim 9, wherein the user habit determiner configured to:

modify a trigger event that occurs at a first time of day to occur at a second time of day such that the action associated with trigger event consumes less system resources if it occurs at the second time of day than if it occurs at the first time of day.

16. A computer program product for preemptively retrieving information, the computer program product being tangibly embodied on a non-transitory computer-readable storage medium and including executable code that, when executed, is configured to cause a mobile computing device to:

monitor a user'"'"'s behavior in regards to a mobile computing device;

determine one or more user habits based upon the monitored user'"'"'s behavior;

edit at least one triggering event associated with a respective determined user habit;

edit an action based upon the respective determined user habit by editing a stored triggering event and action pair, wherein the action is associated with a respective triggering event;

detect that a triggering event has occurred, wherein the triggering event includes a prediction of a reduction in the system resources of the mobile computing device and the predicted reduction in system resources includes a prediction of transitioning the mobile device from AC power to battery power;

in response to the triggering event, automatically perform the action associated with the triggering event using the stored triggering event and action pair, wherein the action includes retrieving anticipated data from a remote device before the predicted reduction in system resources occurs;

cache at least part of the anticipated data within a memory of the mobile computing device;

receive a request, from a user, for requested data, wherein the requested data includes at least a portion of the anticipated data; and

fulfill at least part of the request for the requested data by retrieving the anticipated data portion of the requested data from the memory of the mobile computing device.