Dynamic Adjustment of Mobile Device Based on Voter Feedback

• US 20150351033A1
• Filed: 02/13/2015
• Published: 12/03/2015
• Est. Priority Date: 05/30/2014
• Status: Active Grant

• Current Assignee: Apple Inc.
• Original Assignee: Apple Inc.
• Inventors: Stanley-Marbell, Phillip, Kapoor, Gaurav, Vaishampayan, Umesh S.
• Granted Patent: US 9,813,990 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: H04W 52/0235 where the received signal is a power saving command
• 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 associated with the mobile device and/or a peer device. The occurrence of one or more events can trigger adjustments to system settings. 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 communicating with a peer device, the mobile device can be configured to check energy and data budgets and environmental conditions of the mobile device and/or a peer device to ensure a high quality user experience.

Claims

1. A method comprising:

receiving, by a first process from one or more plugin processes executing on a computing device, a request to register the plugin processes as one or more voting processes;

receiving, by the first process, events generated by one or more client processes, each event including data associated with one of a plurality of attributes;

storing the event data in an event data store on the mobile device;

receiving, by the first process, a request from a client process to initiate an event associated with a particular attribute;

sending to each registered voting process information that identifies the particular attribute;

in response to sending to each registered voting process the information that identifies the particular attribute, receiving a vote from at least one of the registered voting processes; and

determining, by the first process, to allow the event associated with the particular attribute based on the vote.

2. The method of claim 1, wherein the one or more voting processes are dynamically plugged into the first process at runtime.

3. The method of claim 1, wherein determining, by the first process, to allow the event associated with the particular attribute based on feedback from one or more voting processes comprises:

sending each voting process information that identifies the particular attribute; and

receiving a yes vote from each of the voting processes when each voting process determines that an event associated with the particular attribute should be allowed to occur.

4. The method of claim 1, further comprising determining, by the first process, to prevent a second event associated with a second attribute when the first process receives a no vote from at least one of the one or more voting processes.

5. The method of claim 1, further comprising:

receiving a request from at least one of the voting processes for a forecast associated with the particular attribute;

generating the requested forecast; and

returning the requested forecast to the at least one voting process.

6. The method of claim 1, further comprising determining, by the first process, to allow a third event associated with a particular attribute value based on feedback from one or more voting processes.

7. The method of claim 1, wherein determining, by the first process, to allow a third event associated with a particular attribute value based on feedback from one or more voting processes comprises:

sending each voting process information that identifies the particular attribute value; and

receiving a yes vote from each of the voting processes when each voting process determines that an event associated with the particular attribute value should be allowed to occur.

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

receiving, by a first process from one or more plugin processes executing on a computing device, a request to register the plugin processes as one or more voting processes;

receiving, by the first process, events generated by one or more client processes, each event including data associated with one of a plurality of attributes;

storing the event data in an event data store on the mobile device;

receiving, by the first process, a request from a client process to initiate an event associated with a particular attribute;

sending to each registered voting process information that identifies the particular attribute;

in response to sending to each registered voting process the information that identifies the particular attribute, receiving a vote from at least one of the registered voting processes; and

determining, by the first process, to allow the event associated with the particular attribute based on the vote.

9. The non-transitory computer-readable medium of claim 8, wherein the one or more voting processes are dynamically plugged into the first process at runtime.

10. The non-transitory computer-readable medium of claim 8, wherein the instructions that cause determining, by the first process, to allow the event associated with the particular attribute based on feedback from one or more voting processes include instructions that cause:

sending each voting process information that identifies the particular attribute; and

receiving a yes vote from each of the voting processes when each voting process determines that an event associated with the particular attribute should be allowed to occur.

11. The non-transitory computer-readable medium of claim 8, wherein the instructions cause determining, by the first process, to prevent a second event associated with a second attribute when the first process receives a no vote from at least one of the one or more voting processes.

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

receiving a request from at least one of the voting processes for a forecast associated with the particular attribute;

generating the requested forecast; and

returning the requested forecast to the at least one voting process.

13. The non-transitory computer-readable medium of claim 8, wherein the instructions cause determining, by the first process, to allow a third event associated with a particular attribute value based on feedback from one or more voting processes.

14. The non-transitory computer-readable medium of claim 8, wherein the instructions that cause determining, by the first process, to allow a third event associated with a particular attribute value based on feedback from one or more voting processes include instructions that cause:

sending each voting process information that identifies the particular attribute value; and

receiving a yes vote from each of the voting processes when each voting process determines that an event associated with the particular attribute value should be allowed to occur.

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;

receiving, by a first process from one or more plugin processes executing on a computing device, a request to register the plugin processes as one or more voting processes;

receiving, by the first process, events generated by one or more client processes, each event including data associated with one of a plurality of attributes;

storing the event data in an event data store on the mobile device;

receiving, by the first process, a request from a client process to initiate an event associated with a particular attribute;

sending to each registered voting process information that identifies the particular attribute;

in response to sending to each registered voting process the information that identifies the particular attribute, receiving a vote from at least one of the registered voting processes; and

determining, by the first process, to allow the event associated with the particular attribute based on the vote.

16. The system of claim 15, wherein the one or more voting processes are dynamically plugged into the first process at runtime.

17. The system of claim 15, wherein the instructions that cause determining, by the first process, to allow the event associated with the particular attribute based on feedback from one or more voting processes include instructions that cause:

sending each voting process information that identifies the particular attribute; and

receiving a yes vote from each of the voting processes when each voting process determines that an event associated with the particular attribute should be allowed to occur.

18. The system of claim 15, wherein the instructions cause determining, by the first process, to prevent a second event associated with a second attribute when the first process receives a no vote from at least one of the one or more voting processes.

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

receiving a request from at least one of the voting processes for a forecast associated with the particular attribute;

generating the requested forecast; and

returning the requested forecast to the at least one voting process.

20. The system of claim 15, wherein the instructions cause determining, by the first process, to allow a third event associated with a particular attribute value based on feedback from one or more voting processes.

21. The system of claim 15, wherein the instructions that cause determining, by the first process, to allow a third event associated with a particular attribute value based on feedback from one or more voting processes include instructions that cause:

sending each voting process information that identifies the particular attribute value; and

receiving a yes vote from each of the voting processes when each voting process determines that an event associated with the particular attribute value should be allowed to occur.