Smart cache warming

• US 10,171,615 B1
• Filed: 10/31/2016
• Issued: 01/01/2019
• Est. Priority Date: 03/28/2011
• Status: Active Grant

• Current Assignee: Google LLC (Alphabet Inc.)
• Original Assignee: Google LLC (Alphabet Inc.)
• Inventors: Bowers, Andrew, Tom, Kevin
• Primary Examiner(s): Giardino, Jr., Mark A
• Assistant Examiner(s): Matin, Tasnima
• Application Number:
  US15/339,226
• Time in Patent Office: 792 Days
• 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:

detecting a triggering event, wherein the triggering event includes a communication from a communication application, wherein the communication is related to upcoming travel;

in response to detecting the triggering event, automatically performing an action paired with the triggering event, wherein the action includes retrieving anticipated data from a remote device and the anticipated data includes travel-related information directly related to the upcoming travel including one or more travel guides;

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

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

fulfilling at least part of the request for the requested data by retrieving at least the portion of the anticipated data directly from the memory of the mobile device such that at least part of the request for the requested data is fulfilled when the remote device is unavailable to fulfill the request.

2. The method as in claim 1, wherein the anticipated data further includes traveling directions directly related to the upcoming travel.

3. The method as in claim 1, wherein the anticipated data further includes maps directly related to the upcoming travel.

4. The method as in claim 1, wherein the anticipated data further includes travel directions from a first location to a second location.

5. The method as in claim 1, wherein the anticipated data further includes a travel itinerary.

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

monitoring a user'"'"'s behavior based on interactions with a mobile device;

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

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

generating and pairing 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 a triggering event, wherein the triggering event includes a predicted reduction in system resources of the mobile device and the predicted reduction in system resources includes a prediction of transitioning the mobile device to battery power;

in response to the triggering event, automatically performing the action paired 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 system resources occurs;

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

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

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

7. The method as in claim 6, wherein:

the triggering event includes a time of day; and

the action paired with the triggering event includes;

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

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

8. The method as in claim 6, wherein caching at least the portion of the anticipated data comprises transmitting at least the portion of the anticipated data that is cached to a remote server, wherein the remote server is configured to synchronize at least the portion of the anticipated data across a plurality of devices.

9. The method as in claim 6, wherein:

the triggering event includes an upcoming calendar appointment, wherein the upcoming calendar appointment is associated with a location; and

the action paired with the triggering event includes retrieving traveling directions from a first location to the location associated with the upcoming calendar appointment.

10. The method as in claim 6, wherein:

the triggering event includes an upcoming calendar appointment, wherein the upcoming calendar appointment is associated with one or more files; and

the action paired with the triggering event includes retrieving at least one of the one or more of the files associated with the upcoming calendar appointment.

11. The method as in claim 6, wherein:

the triggering event includes a change in location of the mobile device; and

the action includes retrieving at least the portion of the anticipated data based upon a new location of the mobile device.

12. The method as in claim 6, wherein:

the triggering event includes a first time of day; and

generating the triggering event associated with the respective determined user habit includes modifying the triggering event to include a second time of day such that the action paired with triggering event consumes less system resources than if the action occurred at the first time of day.

13. The method as in claim 6, wherein the action includes one of trans-coding a video, synchronizing multimedia playlists, and performing a network action.

14. A mobile computing device comprising:

a user habit monitor configured to;

monitor a user'"'"'s behavior based on interactions with a mobile computing device,

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

generate at least one triggering event associated with a respective determined user habit, and

generate and pair 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 a triggering event, wherein the triggering event includes a predicted reduction in system resources of the mobile computing device and the predicted reduction in system resources includes a prediction of transitioning the mobile computing device to battery power, and

in response to the triggering event, automatically perform the action paired 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 a portion 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 the portion of the anticipated data, and

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

15. The mobile computing device of claim 14, wherein:

the triggering event includes a time of day; and

the action paired 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 the portion of the anticipated data and a second portion of the retrieved data to not cache as the portion of the anticipated data.

16. The mobile computing device of claim 14, wherein:

the anticipated data pre-loader is configured to transmit at least the portion of the anticipated data that is cached to a remote server, and

the remote server is configured to synchronize at least the portion of the anticipated data across a plurality of devices.

17. The mobile computing device of claim 14, wherein:

the triggering event includes an upcoming calendar appointment, wherein the upcoming calendar appointment is associated with a location; and

the action paired 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.

18. The mobile computing device of claim 14, wherein:

the triggering event includes an upcoming calendar appointment, wherein the upcoming calendar appointment is associated with one or more files; and

the action paired with the triggering event causes the mobile computing device to retrieve at least one of the one or more of the files associated with the upcoming calendar appointment.

19. The mobile computing device of claim 14, wherein:

the triggering event includes a change in location of the mobile computing device; and

the action causes the mobile computing device to retrieve at least the portion of the anticipated data based upon the new location of the mobile computing device.

20. The mobile computing device of claim 14, wherein:

the triggering event includes a first time of day; and

the user habit determiner is configured to modify the triggering event to include a second time of day such that the action paired with the triggering event consumes less system resources than if the action occurred at the first time of day.

21. The mobile computing device of claim 14, wherein the action includes one of trans-coding a video, synchronizing multimedia playlists, and performing a network action.

22. 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 based on interactions with a mobile computing device;

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

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

generate and pair 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;

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

in response to the triggering event, automatically perform the action paired 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 a portion 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 the portion of the anticipated data; and

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

23. The computer program product of claim 22, wherein:

the triggering event includes a time of day; and

the action paired with the triggering event includes;

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

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

24. The computer program product of claim 22, wherein the executable code that, when executed, causes the mobile computing device to cache at least the portion of the anticipated data comprises executable code that, when executed, causes the mobile computing device to transmit at least the portion of the anticipated data that is cached to a remote server, wherein the remote server is configured to synchronize at least the portion of the anticipated data across a plurality of devices.

25. The computer program product of claim 22, wherein:

the triggering event includes an upcoming calendar appointment, wherein the upcoming calendar appointment is associated with a location; and

the action paired with the triggering event includes retrieving traveling directions from a first location to the location associated with the upcoming calendar appointment.

26. The computer program product of claim 22, wherein:

the triggering event includes an upcoming calendar appointment, wherein the upcoming calendar appointment is associated with one or more files; and

the action paired with the triggering event includes retrieving at least one of the one or more of the files associated with the upcoming calendar appointment.

27. The computer program product of claim 22, wherein:

the triggering event includes a change in location of the mobile device; and

the action includes retrieving at least the portion of the anticipated data based upon a new location of the mobile device.

28. The computer program product of claim 22, wherein:

the triggering event includes a first time of day; and

the executable code that, when executed, causes the mobile computing device to generate the triggering event associated with the respective determined user habit comprises executable code that, when executed, causes the mobile computing device to modify the triggering event to include a second time of day such that the action paired with triggering event consumes less system resources than if the action occurred at the first time of day.

29. The computer program product of claim 22, wherein the action includes one of trans-coding a video, synchronizing multimedia playlists, and performing a network action.