Power optimization for data services

• US 8,255,716 B2
• Filed: 08/27/2009
• Issued: 08/28/2012
• Est. Priority Date: 08/27/2009
• Status: Active Grant

• Current Assignee: Qualcomm, Inc.
• Original Assignee: Qualcomm, Inc.
• Inventors: Mandyam, Giridhar D.
• Primary Examiner(s): Spittle, Matthew D
• Application Number:
  US12/549,343
• Publication Number:
  US 20110055613A1
• Time in Patent Office: 1,097 Days
• Field of Search: 713300-340, 455/572, 455/574, 370/311, 370/318
• US Class Current: 713/320
• 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: Y02D 30/70 in wireless communication networks

Abstract

Systems and methods for optimizing the power of a battery in a mobile device are provided. The systems and methods include receiving a request from at least one of a plurality of applications running on the mobile device. The systems and methods further include determining user characteristics from interacting with at least one of the applications and determining a user dwell time threshold based upon the user'"'"'s interactions with an application. The systems and methods further include buffering requests if the user dwell time is less than the user dwell threshold level.

Claims

1. A method for optimizing power of a battery in a mobile device, comprising:

receiving, at a first time, a request from at least one of a plurality of applications on the mobile device;

determining if a battery charge level of the battery in the mobile device meets a power preservation threshold;

determining if a current dwell time of user interaction with at least one of the applications meets a dwell time threshold, wherein the dwell time threshold is based on user interaction characteristics from interacting with at least one of the plurality of applications; and

buffering the request for processing until a second time later than the first time, wherein the second time corresponds to an end of the dwell time threshold for the current dwell time, if the battery charge level meets the power preservation threshold and if the current dwell time does not meet the dwell time threshold.

2. The method of claim 1, further comprising collecting historical data defining the user interaction characteristics, and calculating the dwell time threshold as a function of the collected historical data.

3. The method of claim 2, wherein collecting the user interaction characteristics includes collecting data defining one or more of user interactions with one or more of the plurality of applications on the mobile device, or user interaction with content retrieved from prior requests, or web browsing habits, or type of content viewed.

4. The method of claim 1, wherein receiving the request includes receiving instructions to send data to or receive data from a network via a wireless connection.

5. The method of claim 1, wherein buffering further comprises:

forming a queue including the request.

6. The method of claim 5, wherein forming the queue further comprises listing queued requests in an order based on an application priority.

7. The method of claim 5, wherein forming the queue further comprises listing queued requests in an order based upon an amount of power consumption required by the request.

8. The method of claim 5, wherein forming the queue further comprises listing queued requests in an order based upon a time of receipt.

9. The method of claim 1, wherein buffering further comprises:

delaying processing of the request for a period of time, wherein the period of time is a difference between the dwell time threshold and the current dwell time.

10. The method of claim 1, wherein if the power preservation threshold is achieved, providing a user alert for powering down the mobile device to recover the battery charge level for the mobile device.

11. The method of claim 10, wherein the user alert further comprises:

notifying a user of a first period of time for powering down the mobile device, wherein the first period of time is based on extending the user'"'"'s interaction with at least one of the applications for a second period of time,

wherein the second period of time is based on user interaction characteristics from interacting with at least one of the plurality of applications.

12. The method of claim 1, wherein if a minimum power preservation threshold is achieved, powering down the mobile device.

13. The method of claim 12, further comprising determining that the battery charge level meets a minimum threshold, and wherein powering down the mobile device is based on the battery charge level meeting the minimum threshold.

14. At least one processor configured for optimizing power of a battery in a mobile device, the at least one processor comprising:

a first module for receiving, at a first time, a request from at least one of a plurality of applications on the mobile device;

a second module for determining if a battery charge level of the battery in the mobile device meets a power preservation threshold;

a third module for determining if a current dwell time of user interaction with at least one of the applications meets a dwell time threshold, wherein the dwell time threshold is based on user interaction characteristics from interacting with at least one of the plurality of applications; and

a fourth module for buffering the request for processing until a second time later than the first time, wherein the second time corresponds to an end of the dwell time threshold for the current dwell time, if the battery charge level meets the power preservation threshold and if the current dwell time does not meet the dwell time threshold.

15. A computer program product, comprising:

a computer-readable medium comprising;

at least one instruction operable to cause a computer to receive, at a first time, a request from at least one of a plurality of applications on the mobile device;

at least one instruction operable to cause the computer to determine if a battery charge level of a battery on the mobile device meets a power preservation threshold;

at least one instruction operable to cause the computer to determine if a current dwell time of user interaction with at least one of the applications meets a dwell time threshold, wherein the dwell time threshold is based on user interaction characteristics from interacting with at least one of the plurality of applications; and

at least one instruction operable to cause the computer to buffer the request for processing until a second time later than the first time, wherein the second time corresponds to an end of the dwell time threshold for the current dwell time, if the battery charge level meets the power preservation threshold and if the current dwell time does not meet the dwell time threshold.

16. A mobile device, comprising:

means for receiving, at a first time, a request from at least one of a plurality of applications on the mobile device;

means for determining if a battery charge level of a battery on the mobile device meets a power preservation threshold;

means for determining if a current dwell time of user interaction with at least one of the applications meets a dwell time threshold, wherein the dwell time threshold is based on user interaction characteristics from interacting with at least one of the plurality of applications; and

means for buffering the request for processing until a second time later than the first time, wherein the second time corresponds to an end of the dwell time threshold for the current dwell time, if the battery charge level meets the power preservation threshold and if the current dwell time does not meet the dwell time threshold.

17. A mobile device, comprising:

a plurality of applications, wherein at least one of the plurality of applications is configured to generate at a first time request for processing;

a battery having a battery charge level;

a memory having a power preservation threshold and a dwell time threshold, wherein the dwell time threshold is based on user interaction characteristics from interacting with at least one of the plurality of applications; and

a request manager having request processing logic, wherein the request processing logic is configured to determine if the battery charge level of the battery meets the power preservation threshold, to determine if a current dwell time of user interaction with at least one of the applications meets the dwell time threshold, and to buffer the request for processing until a second time later than the first time, wherein the second time corresponds to an end of the dwell time threshold for the current dwell time, if the battery charge level meets the power preservation threshold and if the current dwell time does not meet the dwell time threshold.

18. The mobile device of claim 17, further comprising a dwell determiner operable for collecting historical data defining the user interaction characteristics, and further operable for calculating the dwell time threshold as a function of the collected historical data.

19. The mobile device of claim 18, wherein the collected historical data comprises data defining one or more of user interactions with one or more of the plurality of applications on the mobile device, or user interaction with content retrieved from prior requests, or web browsing habits, or type of content viewed.

20. The mobile device of claim 17, wherein the request includes instructions to send data to or receive data from a network via a wireless connection.

21. The mobile device of claim 17, wherein the memory stores the buffered request in a queue.

22. The mobile device of claim 21, wherein the queue further comprises a listing of queued requests in an order based on an application priority.

23. The mobile device of claim 21, wherein the queue further comprises a listing of queued requests in an order based upon an amount of power consumption required by the request.

24. The mobile device of claim 21, wherein the queue further comprises a listing of queued requests in an order based upon a time of receipt.

25. The mobile device of claim 17, wherein the request manager is further operable to delay processing of the request for a period of time, wherein the period of time is a difference between the dwell time threshold and the current dwell time.

26. The mobile device of claim 17, wherein if the power preservation threshold is achieved, the request manager is operable to provide a user alert for powering down the mobile device to recover the battery charge level for the mobile device.

27. The mobile device of claim 26, wherein the user alert further comprises:

notifying a user of a first period of time for powering down the mobile device, wherein the first period of time is based on extending the user'"'"'s interaction with at least one of the applications for a second period of time,

wherein the second period of time is based on user interaction characteristics from interacting with at least one of the plurality of applications.

28. The mobile device of claim 17, wherein the request manager is operable to power down the mobile device if a minimum power preservation threshold is achieved.

29. The mobile device of claim 28, further comprising a charge determiner operable for determining that the battery charge level meets a minimum threshold, and wherein the request manager is operable to power down the mobile device if the battery charge level meets the minimum threshold.