Dynamic Adjustment of Mobile Device Based on User Activity

• US 20140366041A1
• Filed: 04/15/2014
• Published: 12/11/2014
• Est. Priority Date: 06/09/2013
• Status: Active Grant

• Current Assignee: Apple Inc.
• Original Assignee: Apple Inc.
• Inventors: Kapoor, Gaurav, Andrews, Jonathan J., Stanley-Marbell, Phillip, Wan, Kit-man
• Granted Patent: US 9,256,484 B2
• Time in Patent Office: Days
• US Class Current: 719/318
• CPC Class Codes: G06F 9/4825 Interrupt from clock, e.g. time of day
• CPC Class Codes: G06F 9/542 Event management; Broadcasting; Multicasting; Notifications
• CPC Class Codes: H04L 67/55 Push-based network services
• CPC Class Codes: H04M 1/72406 by software upgrading or downloading
• CPC Class Codes: H04M 1/72448 with means for adapting the functionality of the device according to specific conditions
• CPC Class Codes: H04W 4/50 Service provisioning or reconfiguring
• CPC Class Codes: H04W 52/0258 controlling an operation mode according to history or models of usage information, e.g. activity schedule or time of day
• CPC Class Codes: H04W 52/0264 by selectively disabling software applications
• CPC Class Codes: Y02D 30/70 in wireless communication networks

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:

receiving event data at a first process running on a mobile device;

receiving event registration data from a second process running on the mobile device, the event registration data identifying one or more events for triggering an invocation of the second process, where the second process is suspended or terminated after the event registration data is received;

determining, by the first process, that the one or more events have occurred based on the event data; and

invoking the second process on the mobile device.

2. The method of claim 1, wherein invoking the second process causes the second process to adjust one or more components of the mobile device.

3. The method of claim 2, wherein the one or more components include a central processing unit, graphics processing unit, baseband processor or display of the mobile device.

4. The method of claim 1, wherein the one or more events include a change in operating temperature of the mobile device, a change in a system setting, a user input, turning on or off a display, setting a clock alarm, or setting a calendar event.

5. The method of claim 1, further comprising:

receiving, at the first process, a request from the second process for event data stored by the second process;

transmitting, from the first process to the second process, the requested event data, where the second process is configured to adjust one or more components of the mobile device based on the event data.

6. The method of claim 1, wherein the one or more events include a pattern of events and wherein the first process is configured to identify patterns in the received event data and invoke the second process when the pattern of events is detected.

7. A non-transitory computer-readable medium including one or more sequences of instructions which, when executed by one or more processors, causes:

receiving event data at a first process running on a mobile device;

receiving event registration data from a second process running on the mobile device, the event registration data identifying one or more events for triggering an invocation of the second process, where the second process is suspended or terminated after the event registration data is received;

determining, by the first process, that the one or more events have occurred based on the event data; and

invoking the second process on the mobile device.

8. The non-transitory computer-readable medium of claim 7, wherein invoking the second process causes the second process to adjust one or more components of the mobile device.

9. The non-transitory computer-readable medium of claim 8, wherein the one or more components include a central processing unit, graphics processing unit, baseband processor or display of the mobile device.

10. The non-transitory computer-readable medium of claim 7, wherein the one or more events include a change in operating temperature of the mobile device, a change in a system setting, a user input, turning on or off a display, setting a clock alarm, or setting a calendar event.

11. The non-transitory computer-readable medium of claim 7, wherein the instructions cause:

receiving, at the first process, a request from the second process for event data stored by the second process;

transmitting, from the first process to the second process, the requested event data, where the second process is configured to adjust one or more components of the mobile device based on the event data.

12. The non-transitory computer-readable medium of claim 7, wherein the one or more events include a pattern of events and wherein the first process is configured to identify patterns in the received event data and invoke the second process when the pattern of events is detected.

13. A system comprising:

one or more processors; and

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

receiving event data at a first process running on a mobile device;

receiving event registration data from a second process running on the mobile device, the event registration data identifying one or more events for triggering an invocation of the second process, where the second process is suspended or terminated after the event registration data is received;

determining, by the first process, that the one or more events have occurred based on the event data; and

invoking the second process on the mobile device.

14. The system of claim 13, wherein invoking the second process causes the second process to adjust one or more components of the mobile device.

15. The system of claim 14, wherein the one or more components include a central processing unit, graphics processing unit, baseband processor or display of the mobile device.

16. The system of claim 13, wherein the one or more events include a change in operating temperature of the mobile device, a change in a system setting, a user input, turning on or off a display, setting a clock alarm, or setting a calendar event.

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

receiving, at the first process, a request from the second process for event data stored by the second process;

transmitting, from the first process to the second process, the requested event data, where the second process is configured to adjust one or more components of the mobile device based on the event data.

18. The system of claim 13, wherein the one or more events include a pattern of events and wherein the first process is configured to identify patterns in the received event data and invoke the second process when the pattern of events is detected.