Decoupling background work and foreground work

• US 9,032,413 B2
• Filed: 09/01/2011
• Issued: 05/12/2015
• Est. Priority Date: 09/01/2011
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Inventors: Schwartz, James A. Jr., Kishan, Arun U., Neves, Richard K., Probert, David B., Pulapaka, Hari, Gefflaut, Alain F.
• Primary Examiner(s): Anya, Charles E
• Application Number:
  US13/224,168
• Publication Number:
  US 20130061249A1
• Time in Patent Office: 1,349 Days
• Field of Search: 718/104
• US Class Current: 718/104
• CPC Class Codes: G06F 2209/543 Local
• CPC Class Codes: G06F 9/445 Program loading or initiating bootstrapping G06F9/4401; security arrangements for program loading or initiating G06F21/57
• CPC Class Codes: G06F 9/44521 Dynamic linking or loading; Link editing at or after load time, e.g. Java class loading
• CPC Class Codes: G06F 9/4881 Scheduling strategies for dispatcher, e.g. round robin, multi-level priority queues
• CPC Class Codes: G06F 9/542 Event management; Broadcasting; Multicasting; Notifications

Abstract

Systems, methods, and apparatus for separately loading and managing foreground work and background work of an application. In some embodiments, a method is provided for use by an operating system executing on at least one computer. The operating system may identify at least one foreground component and at least one background component of an application, and may load the at least one foreground component for execution separately from the at least one background component. For example, the operating system may execute the at least one foreground component without executing the at least one background component. In some further embodiments, the operating system may use a specification associated with the application to identify at least one piece of computer executable code implementing the at least one background component.

Claims

1. A method of controlling resource consumption by a background component that consumes resources when executed, the method comprising:

detecting an occurrence of a trigger;

identifying a brokered event associated with the trigger based upon a data structure comprising one or more entries corresponding to one or more registered triggers;

determining whether one or more conditions specified for the brokered event are satisfied;

responsive to determining that the one or more conditions are satisfied,

determining whether one or more broker limitations applicable to the brokered event are satisfied;

responsive to determining that the one or more broker limitations are satisfied, signaling the brokered event, where the background component is executed responsive to the signaling.

2. The method of claim 1, comprising:

identifying a foreground component of an application; and

identifying the background component, the background component associated with the application and different than the foreground component.

3. The method of claim 2, comprising:

loading the foreground component in response to a user action.

4. The method of claim 2, comprising:

loading the background component in a controlled execution environment, thereby isolating the background component from the foreground component.

5. The method of claim 1, at least some of the method performed by an operating system.

6. The method of claim 1, the trigger comprising at least one of an event relating to a network activity, an event relating to a user activity, a scheduled event or an event relating to a peripheral device.

7. The method of claim 1, the background component comprising a dynamic link library (DLL).

8. A computer readable storage medium comprising instructions that when executed perform acts for controlling resource consumption by a background component that consumes resources when executed, the acts comprising:

detecting an occurrence of a trigger;

identifying a brokered event associated with the trigger based upon a data structure comprising one or more entries corresponding to one or more registered triggers;

determining whether one or more conditions specified for the brokered event are satisfied;

responsive to determining that the one or more conditions are satisfied,

determining whether one or more broker limitations applicable to the brokered event are satisfied; and

responsive to determining that the one or more broker limitations are satisfied, signaling the brokered event, where the background component is executed responsive to the signaling.

9. The computer readable storage medium of claim 8, the acts comprising:

identifying a foreground component of an application; and

identifying the background component, the background component associated with the application and different than the foreground component.

10. The computer readable storage medium of claim 9, the foreground component comprising an interface for receiving a report concerning execution progress of the background component.

11. The computer readable storage medium of claim 8, the background component comprising a dynamic link library (DLL).

12. The computer readable storage medium of claim 8, the background component comprising a background task.

13. The computer readable storage medium of claim 8, the trigger comprising at least one of an event relating to a network activity or an event relating to a user activity.

14. The computer readable storage medium of claim 8, the trigger comprising at least one of a scheduled event or an event relating to a peripheral device.

15. A system, comprising:

one or more processing units; and

memory comprising instructions that when executed by at least one of the one or more processing units perform acts for controlling resource consumption by a background component that consumes resources when executed, the acts comprising;

identifying a foreground component of an application;

identifying the background component, the background component associated with the application and different than the foreground component;

detecting an occurrence of a trigger associated with the application;

identifying a brokered event associated with the trigger based upon a data structure comprising one or more entries corresponding to one or more registered triggers;

determining whether one or more conditions specified for the brokered event are satisfied;

responsive to determining that the one or more conditions are satisfied,

determining whether one or more broker limitations applicable to the brokered event are satisfied; and

responsive to determining that the one or more broker limitations are satisfied, signaling the brokered event, where the background component is executed responsive to the signaling.

16. The system of claim 15, the foreground component corresponding to a foreground task and the background component corresponding to a background task.

17. The system of claim 15, at least some of the acts performed by an operating system.

18. The system of claim 15, the trigger comprising at least one of an event relating to a network activity, an event relating to a user activity, a scheduled event or an event relating to a peripheral device.

19. The system of claim 15, the acts comprising:

providing, to the foreground component, a report concerning execution progress of the background component.

20. The system of claim 15, the acts comprising:

loading the background component in a controlled execution environment, thereby isolating the background component from the foreground component.