Initiating background updates based on user activity

• US 10,223,156 B2
• Filed: 04/15/2014
• Issued: 03/05/2019
• Est. Priority Date: 06/09/2013
• Status: Active Grant

• Current Assignee: Apple Inc.
• Original Assignee: Apple Inc.
• Inventors: Chan, David Michael, Iarocci, John, Kapoor, Gaurav, Wan, Kit-man, Stanley-Marbell, Phillip, Andrews, Jonathan J., Shepherd, Matthew E., Vyas, Amit K., Ramadurai, Anand, Russell, Lee, Hughes, Brittany D., Myszewski, David B., Matuschak, Andrew M., Graessley, Joshua V., Krochmal, Marc, Vinegrad, Daniel, Peters, Stephen C.
• Primary Examiner(s): Sough, S.
• Assistant Examiner(s): Jordan, Kimberly L
• Application Number:
  US14/253,781
• Publication Number:
  US 20140366042A1
• Time in Patent Office: 1,785 Days
• CPC Class Codes: G06F 1/3206 Monitoring of events, devices or parameters that trigger a change in power modality
• CPC Class Codes: G06F 1/3212 Monitoring battery levels, e.g. power saving mode being initiated when battery voltage goes below a certain level
• CPC Class Codes: G06F 11/3058 Monitoring arrangements for monitoring environmental properties or parameters of the computing system or of the computing system component, e.g. monitoring of power, currents, temperature, humidity, position, vibrations thermal management in cooling arrangements of a computing system G06F1/206
• CPC Class Codes: G06F 11/3409 for performance assessment
• CPC Class Codes: G06F 11/3438 monitoring of user actions tracking the activity of the user H04L67/535
• CPC Class Codes: G06F 2201/86 Event-based monitoring
• CPC Class Codes: G06F 2201/88 Monitoring involving counting
• CPC Class Codes: G06F 9/4825 Interrupt from clock, e.g. time of day
• CPC Class Codes: H04L 67/568 Storing data temporarily at an intermediate stage, e.g. caching
• CPC Class Codes: H04M 1/72403 with means for local support of applications that increase the functionality
• CPC Class Codes: Y02D 10/00 Energy efficient computing, e.g. low power processors, power management or thermal management

Abstract

In some implementations, a mobile device can be configured to monitor environmental, system and user events. The occurrence of one or more events can trigger adjustments to system settings. In some implementations, the mobile device can be configured to keep frequently invoked applications up to date based on a forecast of predicted invocations by the user. In some implementations, the mobile device can receive push notifications associated with applications that indicate that new content is available for the applications to download. The mobile device can launch the applications associated with the push notifications in the background and download the new content. In some implementations, before running an application or accessing a network interface, the mobile device can be configured to check energy and data budgets and environmental conditions of the mobile device to preserve a high quality user experience.

Claims

1. A method comprising:

collecting, by a mobile device, event data corresponding to events occurring on the mobile device, the event data including application invocation data associated with user initiated application invocations on the mobile device;

determining a first current time is within a first time period;

in response to determining the first current time is within the first time period, generating, by the mobile device, an application invocation forecast for the first time period based on the application invocation data, wherein generating the application invocation forecast includes generating for each of a plurality of second time periods within the first time period a respective ranking score, the ranking score representing how many applications are predicted to be invoked by a user of the mobile device in the corresponding second time period;

selecting, by the mobile device, a number of the plurality of second time periods based on the ranking scores for each of the plurality of second time periods, where the selected time periods include less than all of the plurality of second time periods;

determining, by the mobile device, that a second current time is within a particular time period of the selected time periods;

in response to determining that the second current time is within the particular time period of the selected time periods, determining, by the mobile device, an application score for each of a plurality of applications based on the application invocation data, the application score representing a likelihood that a respective application will be invoked by the user within the particular time period;

selecting, by the mobile device, a number of the plurality of applications based on the application score, where the selected applications include less than all of the plurality of applications; and

automatically launching, by the mobile device, at least one of the selected applications as a background process on the mobile device within the particular time period.

2. The method of claim 1, further comprising:

determining a probability for each of a plurality of applications on the mobile device that the respective application will be invoked by a user during the particular time period; and

automatically launching, by the mobile device, a particular application of the selected applications as a background process in anticipation of a user invocation of the particular application when a probability for the particular application indicates that the particular application is likely to be invoked by the user.

3. The method of claim 2, further comprising:

receiving a request; and

in response to the request, determining whether to launch the particular application based on an energy budget and thermal conditions of the mobile device, the energy budget allocating a portion of a battery capacity of the mobile device for processing application launches during the particular time period.

4. The method of claim 1, wherein the first time period is one day in length, and wherein each of the plurality of second time periods has a length of fifteen minutes.

5. The method of claim 2, wherein determining the probability includes performing time series modeling on the invocation data collected by the mobile device.

6. The method of claim 2, wherein determining the probability includes analyzing recent, daily and weekly user invocation history to calculate a probability that the user will invoke an application at about the current time.

7. The method of claim 1, wherein the second current time comprises a time window that is larger than a time window of the first current time.

8. A method comprising:

receiving, at a first process on a mobile device, a background data transfer request from a second process on the mobile device;

determining whether to perform the background data transfer request based on budgeting constraints of the mobile device, wherein the budgeting constraints include an energy budget that allocates a portion of the battery capacity of the mobile device for processing background data transfer requests and thermal conditions of the mobile device;

performing a background data transfer indicated by the background data transfer request in response to a determination that the budgeting constraints of the mobile device allow the background data transfer; and

storing the background data transfer request in response to a determination that the background data transfer should not be performed based on the budgeting constraints of the mobile device.

9. The method of claim 8, wherein determining whether to perform the background data transfer request further comprises:

determining a current operating temperature using one or more temperature sensors of the mobile device; and

determining whether the current operating temperature is above a predetermined threshold.

10. The method of claim 8, wherein the second process is terminated or suspended after the background data request is received by the first process.

11. The method of claim 8, further comprising:

after storing the background data transfer request, determining that the background data transfer request can be performed based on budgeting constraints or environmental conditions of the mobile device; and

performing the background data transfer indicated by the background data transfer request in response to a determination that budgeting constraints and environmental conditions of the mobile device allow the background data transfer.

12. The method of claim 11, further comprising relaunching the second process when the background data transfer is completed.

13. The method of claim 11, further comprising:

while performing the background data transfer, suspending the background data transfer when a poor network connection is detected.

14. The method of claim 11, further comprising:

while performing the background data transfer, suspending the background data transfer when one or more budgets are exceeded.

15. A system comprising:

one or more processors; and

a computer-readable medium including one or more sequences of instructions which, when executed by the one or more processors, causes;

collecting, by a mobile device, event data corresponding to events occurring on the mobile device, the event data including application invocation data associated with user initiated application invocations on the mobile device;

determining a first current time is within a first time period;

in response to determining the current time is within the first time period, generating, by the mobile device, an application invocation forecast for the first time period based on the application invocation data, wherein generating the application invocation forecast includes generating for each of a plurality of second time periods within the first time period a respective ranking score, the ranking score representing how many applications are predicted to be invoked by a user of the mobile device in the corresponding second time period;

selecting, by the mobile device, a number of the plurality of second time periods based on the ranking scores for each of the plurality of second time periods, where the selected time periods include less than all of the plurality of second time periods;

determining, by the mobile device, that a second current time is within a particular time period of the selected time periods;

in response to determining that the second current time is within the particular time period of the selected time periods, determining, by the mobile device, an application score for each of a plurality of applications based on the application invocation data, the application score representing a likelihood that a respective application will be invoked by the user within the particular time period;

selecting, by the mobile device, a number of the plurality of applications based on the application score, where the selected applications include less than all of the plurality of applications; and

automatically launching, by the mobile device, at least one of the selected applications as a background process on the mobile device within the particular time period.

16. The system of claim 15, wherein the instructions cause:

determining a probability for each of a plurality of applications on the mobile device that the respective application will be invoked by a user during the particular time period; and

automatically launching, by the mobile device, a particular application of the selected applications as a background process in anticipation of a user invocation of the particular application when the probability for a particular application indicates that the particular application is likely to be invoked by the user.

17. The system of claim 16, wherein the instructions cause:

receiving a request; and

in response to the request;

determining a current operating temperature using one or more temperature sensors of the system;

determining whether the current operating temperature is above a predetermined threshold; and

determining whether to launch the particular application based on an energy budget and thermal conditions of the mobile device, wherein the energy budget allocates a portion of a battery capacity of the mobile device for processing application launches during the particular time period, and wherein the thermal conditions prevent launching of the particular application in response to the current operating temperature being above the predetermined threshold.

18. The system of claim 15, wherein the first time period is one day in length, and wherein each of the plurality of second time periods has a length of fifteen minutes.

19. The system of claim 16, wherein determining the probability includes performing time series modeling on the invocation data collected by the mobile device.

20. The system of claim 16, wherein determining the probability includes analyzing recent, daily and weekly user invocation history to calculate a probability that the user will invoke an application at about the current time.