Dynamic addition and removal of operating system components

• US 10,394,580 B2
• Filed: 07/19/2016
• Issued: 08/27/2019
• Est. Priority Date: 06/28/2012
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Inventors: Hall, Michael, Lovitt, Andrew, Spradlin, Jeremiah
• Primary Examiner(s): Wathen, Brian W
• Assistant Examiner(s): Seye, Abdou K
• Application Number:
  US15/214,122
• Publication Number:
  US 20160328245A1
• Time in Patent Office: 1,134 Days
• CPC Class Codes: G06F 9/44505 Configuring for program initiating, e.g. using registry, configuration files
• CPC Class Codes: G06F 9/451 Execution arrangements for user interfaces
• CPC Class Codes: G06F 9/545 where tasks reside in different layers, e.g. user- and kernel-space

Abstract

Systems, computer program products and computer program products for facilitating the dynamic addition and removal of operating system components on computing devices based on application or user interaction over time are disclosed. Such systems, computer program products and computer program products provide one or more API intercept layers, a rules engine and a hydrate engine that facilitates the ability to dynamically rehydrate or hydrate operating system components. In an embodiment, a minimal (or core) operating system image on a computing device is deployed. Then, required components may be dynamically added (i.e., “streamed” or “rehydrated”) from storage, a server or cloud service as required by an executing application program on the computing device. In another embodiment, a totally complete operating system image is deployed on a computing device. Then, unused components may be dynamically removed (i.e., “dehydrated”) from the computing device over time based on application or user interaction.

Claims

1. A method in a computing device, comprising:

receiving a call from an application executing on the computing device;

determining an operating system component intended to receive the call that does not exist in an operating system of the computing device; and

hydrating the component into the operating system of the computing device based at least in part on said determining, said hydrating comprising dynamic installation by the computing device of the component into the operating system to handle the call.

2. The method of claim 1, wherein said hydrating comprises:

hydrating the component after a predetermined number of calls related to the component is received.

3. The method of claim 1, wherein said hydrating comprises:

retrieving the component from a service over a network.

4. The method of claim 1, wherein said receiving comprises:

intercepting the call from a shared library file at an API (application programming interface) intercept layer, the shared library file called by the application executing on the computing device.

5. The method of claim 4, further comprising:

storing, by the API intercept layer, touches of components of the operating system.

6. The method of claim 4, wherein said determining comprises:

determining with a rules engine the operating system component intended to receive the call that does not exist in the operating system, the rules engine including a data structure at least of rehydration rules that uses information logged by API intercept layer to direct said hydrating.

7. The method of claim 6, wherein at least one of the rehydration rules is a rehydration rule to not rehydrate under certain conditions.

8. A method in a computing device, comprising:

determining a component of an operating system for dehydration based on a dehydrate rule;

dehydrating the component in the operating system of the computing device based at least on said determining, said dehydrating comprising dynamic removal by the computing device of the component from the operating system;

receiving a call from an application executing on the computing device;

determining the component supports the call; and

rehydrating the component in the operating system of the computing device based at least on said determining the component supports the call to enable the component to handle the call, said rehydrating comprising dynamic installation by the computing device of the component into the operating system.

9. The method of claim 8, wherein the dehydrate rule indicates that any components not touched during a certain time period be removed from the operating system, and wherein said determining comprises:

determining the component was not touched during the certain time period.

10. The method of claim 8, wherein the dehydrate rule provides a periodic sweep of unused components for removal from the operating system, and wherein said determining comprises:

determining the component as unused during the periodic sweep.

11. The method of claim 8, further comprising:

storing, by an API intercept layer, touches of components of the operating system.

12. The method of claim 11, wherein said determining comprises:

determining with a rules engine the component for dehydration based on the dehydrate rule, the rules engine including a data structure at least of dehydration rules that uses information logged by API intercept layer to direct said dehydrating.

13. A system in a computing device, comprising:

a memory configured to store control logic;

at least one processor configured to execute the control logic, the control logic including;

a rules engine configured to determine an operating system component intended to receive a call from an application executing on the device that does not exist in an operating system of the computing device; and

a hydrate engine configured to be directed by the rules engine to hydrate the component into the operating system of the computing device, said hydrating comprising dynamic installation by the hydrate engine of the component into the operating system to handle the call.

14. The system of claim 13, wherein said the rules engine is configured to direct the hydrate engine to hydrate the component after a predetermined number of calls related to the component is received.

15. The system of claim 13, wherein the hydrate engine is configured to retrieve the component from a service over a network.

16. The system of claim 13, further comprising:

an API (application programming interface) intercept layer configured to intercept the call from a shared library file called by the application executing on the computing device.

17. The system of claim 16, wherein the API intercept layer is configured to store touches of components of the operating system.

18. The system of claim 16, wherein the rules engine including a data structure at least of rehydration rules that uses information logged by API intercept layer to direct the hydrate engine.

19. A method in a computing device, comprising:

determining a component of an operating system for dehydration based on a dehydrate rule;

dehydrating the component in the operating system of the computing device based at least on said determining, said dehydrating comprising dynamic removal by the computing device of the component from the operating system;

receiving a call from an application executing on the computing device;

determining the component supports the call; and

redirecting the call to a cloud service for handling based at least on said determining the component supports the call.

20. The method in the computing device of claim 19, wherein:

the dehydrate rule indicates that any components not touched during a certain time period be removed from the operating system, and wherein said determining comprises determining the component was not touched during the certain time period;

or

the dehydrate rule provides a periodic sweep of unused components for removal from the operating system, and wherein said determining comprises determining the component as unused during the periodic sweep.