METHOD FOR POWER SAVING IN MOBILE DEVICES BY OPTIMIZING WAKELOCKS

• US 20150208352A1
• Filed: 01/22/2015
• Published: 07/23/2015
• Est. Priority Date: 01/22/2014
• Status: Active Grant

• Current Assignee: Seven Networks LLC (SoftBank Group Corp.)
• Original Assignee: Seven Networks Inc
• Inventors: Backholm, Ari, Li, Wei, Hu, Allan
• Granted Patent: US 9,351,254 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: H04W 52/0251 using monitoring of local events, e.g. events related to user activity
• CPC Class Codes: H04W 52/0264 by selectively disabling software applications
• CPC Class Codes: Y02D 30/70 in wireless communication networks

Abstract

A method for conserving device and/or network resources is provided herein. The method includes detecting a wakelock operating on a mobile device and determining a consumption of one of a power or radio usage attributed to the detected wakelock. The method further includes determining a criticality related to user experience for the detected wakelock and releasing the detected wakelock based on the determined consumption and criticality. Related systems and mobile devices are also disclosed.

Claims

1. A method comprising:

detecting a wakelock operating on a mobile device;

determining a consumption of one of a power or radio usage attributed to the detected wakelock;

determining a criticality related to user experience for the detected wakelock; and

releasing the detected wakelock based on the determined consumption and criticality.

2. The method of claim 1, wherein releasing the detected wakelock based on the determined consumption and criticality comprises releasing the detected wakelock if the determined criticality and determined consumption are not within predetermined ranges.

3. The method of claim 2, further including determining if a detected wakelock is native or non-native to the mobile device.

4. The method of claim 2, wherein detecting a wakelock comprises detecting a wakelock at predetermined intervals.

5. The method of claim 2, wherein determining a criticality related to user experience comprises determining that a wakelock is unnecessary for operation of the mobile device.

6. The method of claim 5, wherein determining a criticality related to user experience comprises determining a criticality on an application-by-application basis.

7. The method of claim 6, wherein, when only wakelocks below a predetermined criticality are detected, releasing any wakelocks that are native to the mobile device.

8. The method of claim 6, wherein, when wakelocks above a predetermined criticality are detected, continue detecting wakelocks operating on the mobile device.

9. The method of claim 6, comprising:

detecting wakelocks operating on the mobile device at a subsequent time, and

monitoring changes between the detected wakelocks and subsequently detected wakelocks.

10. The method of claim 9, further comprising restoring released native wakelocks if the subsequently detected wakelocks are above the predetermined criticality.

11. The method of claim 9, wherein monitoring changes comprises identifying patterns of previously detected wakelocks, wherein the patterns are stored within a cache of the mobile device.

15. The mobile device of claim 3, wherein detecting a wakelock comprises detecting a wakelock at predetermined intervals.

12. A mobile device comprising:

a native wakelock observer module configured for detecting a native wakelock operating on the mobile device;

a wakelock monitor module configured for monitoring one or more detected wakelocks operating on the mobile device; and

an application wakelock detection module configured for detecting an application induced wakelock operating on the mobile device,

wherein the wakelock monitor module releases a detected wakelock based on a determined consumption and criticality associated with the detected wakelock.

13. The mobile device of claim 12, wherein releasing the detected wakelock based on the determined consumption and criticality comprises releasing the detected wakelock if the determined criticality and determined consumption are not within predetermined ranges.

14. The mobile device of claim 13, further including determining if a detected wakelock is native or non-native to the mobile device.

16. The mobile device of claim 13, wherein determining a criticality related to user experience comprises determining that a wakelock is unnecessary for operation of the mobile device.

17. The mobile device of claim 16, wherein determining a criticality related to user experience comprises determining a criticality on an application-by-application basis.

18. The mobile device of claim 17, wherein, when only wakelocks below a predetermined criticality are detected, releasing any wakelocks that are native to the mobile device.

19. The mobile device of claim 17, wherein, when wakelocks above a predetermined criticality are detected, continue detecting wakelocks operating on the mobile device.

20. The mobile device of claim 17, wherein the mobile device is further configured to:

detect wakelocks operating on the mobile device at a subsequent time, and

monitor changes between the detected wakelocks and subsequently detected wakelocks.

21. The mobile device of claim 20, further comprising restoring released native wakelocks if the subsequently detected wakelocks are above the predetermined criticality.

22. The mobile device of claim 20, wherein monitoring changes comprises identifying patterns of previously detected wakelocks, wherein the patterns are stored within a cache of the mobile device.

23. A mobile device comprising:

computer control code that when executed by a processor on the mobile device causes the mobile device to;

detect a wakelock operating on a mobile device;

determine or receive a criticality assessment related to user experience for the detected wakelock; and

release a detected or received wakelock based on the determined criticality.