MIDDLEWARE POWER MANAGEMENT

• US 20130318370A1
• Filed: 12/30/2011
• Published: 11/28/2013
• Est. Priority Date: 12/30/2011
• Status: Abandoned Application

• Current Assignee: Intel Corporation
• Original Assignee: Intel Corporation
• Inventors: Gorbatov, Eugene, Diefenbaugh, Paul
• Application Number:
  US13/976,025
• Publication Number:
  US 20130318370A1
• Time in Patent Office: Days
• US Class Current: 713/300
• CPC Class Codes: G06F 1/3206 Monitoring of events, devices or parameters that trigger a change in power modality
• CPC Class Codes: G06F 1/3234 Power saving characterised by the action undertaken
• CPC Class Codes: G06F 1/329 by task scheduling
• CPC Class Codes: G06F 9/4856 resumption being on a different machine, e.g. task migration, virtual machine migration G06F9/5088 takes precedence
• CPC Class Codes: G06F 9/4893 taking into account power or heat criteria power management in computers in general G06F1/3203; thermal management in computers in general G06F1/206
• CPC Class Codes: G06F 9/5094 where the allocation takes into account power or heat criteria power management in computers in general G06F1/3203; thermal management in computers in general G06F1/206
• CPC Class Codes: Y02D 10/00 Energy efficient computing, e.g. low power processors, power management or thermal management

Abstract

A system can include multiple devices each configured to run an application at an application level and each having varying performance, power, and other capabilities. A middleware power management facility spanning each of the devices can transfer applications from one device to another responsive to a determination based on capabilities of the devices, with the goal of optimizing the individual power consumption or collective energy efficiency of the devices, within application quality of service constraints.

Claims

1. A system, comprising:

a first device configured to run an application at a first application level, the first device having a first power capability;

a second device configured to run the application at a second application level, the second device having a second power capability; and

middleware power management (MWPM) facility spanning each of the first and second devices and configured to transfer the application from the first device to the second device responsive to a determination based at least in part on the first and second power capabilities.

2. The system of claim 1, wherein the first device comprises a first operating system-driven power management (OSPM) facility, and wherein the MWPM facility resides between the first OSPM facility and the first application level on the first device.

3. The system of claim 2, wherein the second device comprises a second OSPM and wherein the MWPM facility resides between the first OSPM facility and the second application level on the second device.

4. The system of claim 1, wherein the first device comprises a first hardware-controlled power management (HWPM) facility, and wherein the MWPM facility resides between the first HWPM facility and the first application level on the first device.

5. The system of claim 2, wherein the second device comprises a second hardware-controlled power management (HWPM) facility, and wherein the MWPM facility resides between the second HWPM facility and the second application level on the second device.

6. The system of claim 1, wherein each of the first and second devices comprises one of a group consisting of:

a laptop computer, a handheld computing device, a tablet computing device, and a smartphone.

7. A method, comprising:

a first device running an application;

a second device configured to run the application;

the first device entering a proximity of a second device;

a middleware power management (MWPM) facility that spans the first and second devices determining whether the application is to be transferred from the first device to the second device, wherein the determining is based at least in part on a power capability of the second device; and

responsive to the determining, the MWPM facility transferring the application to the second device.

8. The method of claim 7, wherein the determining is further based on a power capability of the first device.

9. The method of claim 8, wherein the power capability of the second device is determined to have a quality that exceeds that of the power capability of the first device, the quality comprising at least one of a group consisting of:

amount, quality, efficiency, and reliability.

10. The method of claim 7, further comprising resetting a memory latency requirement on the first device responsive to the transferring.

11. The method of claim 7, further comprising setting a memory latency requirement on the second device responsive to the transferring.

12. The method of claim 7, further comprising the MWPM facility detecting an event that may impact the application running on the second device.

13. The method of claim 12, wherein the event comprises one of a group consisting of:

the first device leaving the proximity of the second device, an actual impairment of the power capability of the second device, and a potential impairment of the power capability of the second device.

14. The method of claim 12, further comprising the MW PM facility determining whether the application is to be transferred from the second device back to the first device responsive to the detecting.

15. The method of claim 12, further comprising the MWPM facility determining whether the application is to be transferred from the second device to a third device responsive to the detecting.

16. The method of claim 7, wherein the first device entering the proximity of the second device comprises the first device detecting a network to which the second device is connected.

17. A mobile device, comprising:

a processor for executing an application at an application level;

a memory for storing information pertaining to the application;

a power supply for providing power for the processor, the power supply having a power capability;

an operating system-driven power management (OSPM) facility for at least partially managing power for the application; and

a middleware power management (MWPM) facility between the OSPM facility and the application level and configured to transfer the application to another device.

18. The mobile device of claim 18, wherein the MWPM facility is configured to transfer the application to the other device responsive to a determination that a power capability of the other device is greater than the power capability of the power supply.

19. The mobile device of claim 18, further comprising a hardware-controlled power management (HWPM) facility for at least partially managing the power for the application.

20. The mobile device of claim 19, wherein the MWPM is further between the HWPM and the application level.