Method for power saving in mobile devices by optimizing wakelocks

• US 9,351,254 B2
• Filed: 01/22/2015
• Issued: 05/24/2016
• Est. Priority Date: 01/22/2014
• Status: Active Grant

• Current Assignee: Seven Networks LLC (SoftBank Group Corp.)
• Original Assignee: Seven Networks LLC (SoftBank Group Corp.)
• Inventors: Li, Wei, Backholm, Ari, Hu, Allan
• Primary Examiner(s): Sorowar, Golam
• Application Number:
  US14/602,808
• Publication Number:
  US 20150208352A1
• Time in Patent Office: 488 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 mobile device comprising:

a display screen;

a memory, and a processor, the mobile device configured to;

acquire a system wakelock in response to an application wakelock acquisition request;

detect an activity state of the mobile device based on a status of the display screen;

enter a power optimization state based on the detected activity state;

release the system wakelock based upon entering the power optimization state when the application that made the acquisition request is not critical to user experience, wherein the application is non-critical when the application is not identified on a whitelist;

acquire the system wakelock in response to a subsequent wakelock acquisition request from another application on the mobile device when the another application making the subsequent wakelock acquisition request is identified on the whitelist.

2. The mobile device of claim 1, wherein the activity state is based on whether keystrokes are detected on the mobile device.

3. The mobile device of claim 1, wherein the activity state is based on whether motion is sensed by the mobile device.

4. The mobile device of claim 1, wherein the activity state is based on whether the display screen of the mobile device is powered on.

5. The mobile device of claim 1, wherein the power optimization state is further in response to whether the mobile device is connected to a power source.

6. The mobile device of claim 1, wherein the activity state is based on each of whether keystrokes are detected on the mobile device, motion is sensed by the mobile device, and the screen of the mobile device being powered on.

7. The mobile device of claim 1, wherein the mobile device exits the power optimization state when any of the following occur:

keystrokes are detected on the mobile device;

motion is sensed by the mobile device;

the display screen of the mobile device is powered on.

8. The mobile device of claim 7, wherein the mobile device is configured to acquire the system wakelock in response to an application wakelock acquisition request when the mobile device has exited the power optimization state without reference to whether the application making the application wakelock acquisition request is on the whitelist.

9. The mobile device of claim 1, wherein the system wakelock is not acquired in response to wakelock acquisition requests from applications not identified on the whitelist when the mobile device is in the power optimization state.

10. A mobile device comprising:

a display screen;

a memory, and a processor, the mobile device configured to;

acquire a system wakelock in response to an application wakelock acquisition request;

detect an activity state of the mobile device based on whether the display screen is on and whether motion is detected by the mobile device;

enter a power optimization state based on the detected activity state;

release the system wakelock based upon entering the power optimization state when the application that made the acquisition request is not critical to user experience, wherein the application is non-critical when the application is not identified on a whitelist;

acquire the system wakelock in response to a subsequent wakelock acquisition request from an another application on the mobile device when the another application making the subsequent wakelock acquisition request is identified on the whitelist.

11. The mobile device of claim 10, wherein the activity state is further based on whether keystrokes are detected on the mobile device.

12. The mobile device of claim 10, wherein the power optimization state is further in response to whether the mobile device is connected to a power source.

13. The mobile device of claim 10, wherein the mobile device exits the power optimization state when any of the following occur:

keystrokes are detected on the mobile device;

motion is sensed by the mobile device;

the display screen of the mobile device is powered on.

14. The mobile device of claim 10, wherein the mobile device is configured to acquire the system wakelock in response to an application wakelock acquisition request when the mobile device has exited the power optimization state without reference to whether the application making the application wakelock acquisition request is on the whitelist.

15. The mobile device of claim 10, wherein the system wakelock is not acquired in response to wakelock acquisition requests from applications not identified on the whitelist when the mobile device is in the power optimization state.

16. A method comprising:

acquiring a system wakelock in response to an application wakelock acquisition request;

detecting an activity state of a mobile device based on a status of a display screen of the mobile device;

entering a power optimization state based on the detected activity state;

releasing the system wakelock based upon entering the power optimization state when the application that made the acquisition request is not critical to user experience, wherein the application is non-critical when the application is not identified on a whitelist;

acquiring the system wakelock in response to a subsequent wakelock acquisition request from another application on the mobile device when the another application making the subsequent wakelock acquisition request is identified on the whitelist.

17. The method of claim 16, wherein the activity state is further based on whether keystrokes are detected on the mobile device.

18. The method of claim 16, wherein the power optimization state is further in response to whether the mobile device is connected to a power source.

19. The method of claim 16, further including exiting the power optimization state when any of the following occur:

keystrokes are detected on the mobile device;

motion is sensed by the mobile device;

the display screen of the mobile device is powered on.

20. The method of claim 16, further including acquiring the system wakelock in response to an application wakelock acquisition request when the mobile device has exited the power optimization state without reference to whether the application making the application wakelock acquisition request is on the whitelist.

21. The method of claim 16, wherein the system wakelock is not acquired in response to wakelock acquisition requests from applications not identified on the whitelist when the mobile device is in the power optimization state.

22. A method comprising:

acquiring a system wakelock in response to an application wakelock acquisition request;

detecting an activity state of a mobile device based on whether a display screen is on and whether motion is detected by the mobile device;

entering a power optimization state based on the detected activity state;

releasing the system wakelock based upon entering the power optimization state when the application that made the acquisition request is not critical to user experience, wherein the application is non-critical when the application is not identified on a whitelist.

23. The method of claim 22, wherein the activity state is further based on whether keystrokes are detected on the mobile device.

24. The method of claim 22, wherein the power optimization state is further in response to whether the mobile device is connected to a power source.

25. The method of claim 22, further including exiting the power optimization state when any of the following occur:

keystrokes are detected on the mobile device;

motion is sensed by the mobile device;

the display screen of the mobile device is powered on.

26. The method of claim 22, further including acquiring the system wakelock in response to an application wakelock acquisition request when the mobile device has exited the power optimization state without reference to whether the application making the application wakelock acquisition request is on the whitelist.

27. The method of claim 22, wherein the system wakelock is not acquired in response to wakelock acquisition requests from applications not identified on the whitelist when the mobile device is in the power optimization state.

28. A mobile device comprising:

a display screen;

a memory, and a processor, the mobile device configured to;

acquire a system wakelock in response to an application wakelock acquisition request;

detect an activity state of a mobile device based on whether a display screen is on and whether motion is detected by the mobile device;

enter a power optimization state based on the detected activity state;

release the system wakelock based upon entering the power optimization state when the application that made the acquisition request is not critical to user experience, wherein the application is non-critical when the application is not identified on a whitelist.

29. The mobile device of claim 28, wherein the activity state is further based on whether keystrokes are detected on the mobile device.

30. The mobile device of claim 28, wherein the power optimization state is further in response to whether the mobile device is connected to a power source.

31. The mobile device of claim 28, wherein the mobile device is further configured to exit the power optimization state when any of the following occur:

keystrokes are detected on the mobile device;

motion is sensed by the mobile device;

the display screen of the mobile device is powered on.

32. The mobile device of claim 28, wherein the mobile device is further configured to acquire the system wakelock in response to an application wakelock acquisition request when the mobile device has exited the power optimization state without reference to whether the application making the application wakelock acquisition request is on the whitelist.

33. The mobile device of claim 28, wherein the system wakelock is not acquired in response to wakelock acquisition requests from applications not identified on the whitelist when the mobile device is in the power optimization state.