Microsoft Technology Licensing, LLC

Richard K Neves

Arun Upadhyaya Kishan

Hari R Pulapaka

David Bradley Probert, Jr

Alain Franck Gefflaut

James A Schwartz, Jr

Benjamin Salim Srour

Michael H Krause

Zinaida A Pozen

James Anthony Schwartz, Jr

James A Schwartz Jr

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.

Decoupling background work and foreground work

Only a particular number of applications on a computing device are active at any given time, with applications that are not active being suspended. A policy is applied to determine when an application is to be suspended. However, an operating system component can have a particular application be exempted from being suspended (e.g., due to an operation being performed by the application). Additionally, an operating system component can have an application that has been suspended resumed (e.g., due to a desire of another application to communicate with the suspended application).

Resuming applications and/or exempting applications from suspension

Systems, methods, and apparatus for separately managing foreground work and background work. In some embodiments, an operating system may identify at least one foreground component and at least one background component of a same application or different applications, and may manage the execution of the components differently. For example, the operating system may receive a request that at least one background component of an application be executed in response to at least one event. In response to detecting an occurrence of the at least one event, the operating system may determine whether at least one first condition set by the application is satisfied and whether at least one second condition set by the operating system is satisfied, and may execute the at least one background component when it is determined that the at least one first and second conditions are satisfied following the occurrence of the at least one event.

Event aggregation for background work execution

Exempting applications from suspension

Growing community of inventors

Kirkland, WA, United States of America

Richard K Neves