Method for power saving in mobile devices by optimizing wakelocks

• US 10,244,479 B1
• Filed: 10/19/2017
• Issued: 03/26/2019
• 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: Backholm, Ari, Hu, Allan, Li, Wei
• Primary Examiner(s): Sorowar, Golam
• Application Number:
  US15/787,896
• Time in Patent Office: 523 Days
• 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 upon entering the power optimization state when the application that made the acquisition request is not critical to user experience, wherein the criticality is characterized on an application-by-application basis;

acquire, while in the power optimization state, the system wakelock in response to a subsequent wakelock acquisition request from another application on the mobile device, wherein to acquire the system wakelock is based on the characterized criticality.

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 3, 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;

a change in the status of the display screen.

5. The mobile device of claim 4, 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 a criticality of the application making the application wakelock acquisition request.

6. 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.

7. 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 a change in the status of the display screen of the mobile device.

8. The mobile device of claim 1, wherein the mobile device is configured to release the system wakelock in response to an application wakelock release request.

9. The mobile device of claim 1, wherein the status of the display screen includes whether the screen is on.

10. The mobile device of claim 1, wherein acquisition of the system wakelock in response to a wakelock acquisition request is based on the criticality such that not all wakelock requests result in acquiring the system wakelock.

11. The mobile device of claim 1, wherein, while in the power optimization state, the system wakelock remains released unless a subsequent wakelock acquisition request is by the another application, wherein a subsequent wakelock acquisition request, while in the power optimization state, by the application does not cause acquisition of the system wakelock.

12. The mobile device of claim 1, wherein the mobile device is configured to terminate an application based on a monitored behavior of the application.

13. The mobile device of claim 1, wherein the mobile device is further configured to enter the power optimization state based on user inactivity.

14. The mobile device of claim 1, wherein to acquire the system wakelock in response to an application wakelock request occurs after detecting a wakelock acquisition request.

15. The mobile device of claim 1, wherein the mobile device is further configured to allow execution of the application while adjusting whether to acquire the system wakelock based on the characterized criticality.

16. The mobile device of claim 1, wherein, while in the power optimization state, a subsequent wakelock acquisition request by the application does not cause acquisition of the system wakelock.

17. The mobile device of claim 1, wherein the power optimization state improves device resource management while in the power optimization state, wherein improving device resource management includes improving battery life.

18. A method comprising:

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

detecting an activity state of the 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 upon entering the power optimization state when the application that made the acquisition request is not critical to user experience, wherein the criticality is characterized on an application-by-application basis;

acquiring, while in the power optimization state, the system wakelock in response to a subsequent wakelock acquisition request from another application on the mobile device, wherein acquiring the system wakelock is based on the characterized criticality.

19. The method of claim 18, wherein the activity state is based on whether keystrokes are detected on the mobile device.

20. The method of claim 18, wherein the activity state is based on whether motion is sensed by the mobile device.

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

22. The method of claim 18, 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 a change in the status of the display screen of the mobile device.

23. The method of claim 18, 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;

a change in the status of the display screen.

24. The method of claim 23, wherein acquiring the system wakelock is in response to an application wakelock acquisition request when the mobile device has exited the power optimization state without reference to a criticality of the application making the application wakelock acquisition request.

25. The method of claim 18, comprising releasing the system wakelock in response to an application wakelock release request.

26. The method of claim 18, wherein the status of the display screen includes whether the screen is on.

27. The method of claim 18, wherein acquisition of the system wakelock in response to a wakelock acquisition request is based on the criticality such that not all wakelock requests result in acquiring the system wakelock.

28. The method of claim 18, wherein, while in the power optimization state, the system wakelock remains released unless a subsequent wakelock acquisition request is by the another application, wherein a subsequent wakelock acquisition request, while in the power optimization state, by the application does not cause acquisition of the system wakelock.

29. The method of claim 18, comprising terminating an application based on a monitored behavior of the application.

30. The method of claim 18, wherein entering the power optimization state is further based on user inactivity.

31. The method of claim 18, wherein acquiring the system wakelock in response to an application wakelock request occurs after detecting a wakelock acquisition request.

32. The method of claim 18, comprising allowing execution of the application while adjusting whether to acquire the system wakelock based on the characterized criticality.

33. The method of claim 18, wherein, while in the power optimization state, a subsequent wakelock acquisition request by the application does not cause acquisition of the system wakelock.

34. The method of claim 18, wherein the power optimization state improves device resource management while in the power optimization state, wherein improving device resource management includes improving battery life.

35. A mobile device comprising:

a display screen;

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

determine a criticality of applications executing on the mobile device, wherein the criticality is determined on an application-by-application basis;

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

detect an activity state of the mobile device based on a status of the display screen, wherein the status of the display screen includes whether the screen is on;

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

while in the power optimization state;

release the system wakelock upon entering the power optimization state when the application that made the acquisition request is not critical, wherein a subsequent wakelock acquisition request by the application does not cause acquisition of the system wakelock and the system wakelock remains released unless a subsequent wakelock acquisition request is by a critical application;

acquire the system wakelock in response to a subsequent wakelock acquisition request from a critical application on the mobile device.

36. The mobile device of claim 35, wherein the mobile device is configured to terminate an application based on a monitored behavior of the application.

37. The mobile device of claim 35, wherein the mobile device is further configured to enter the power optimization state based on user inactivity.

38. The mobile device of claim 35, wherein to acquire the system wakelock in response to an application wakelock request occurs after detecting a wakelock acquisition request.

39. The mobile device of claim 35, wherein the mobile device is further configured to allow execution of the application.

40. The mobile device of claim 35, 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;

a change in the status of the display screen.

41. The mobile device of claim 40, wherein the system wakelock is acquired in response to a wakelock acquisition request after the mobile device has exited the power optimization state.

42. The mobile device of claim 35, wherein the power optimization state improves device resource management while in the power optimization state, wherein improving device resource management includes improving battery life.