Dynamic addition and removal of operating system components

• US 9,405,556 B2
• Filed: 06/28/2012
• Issued: 08/02/2016
• 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, Spradlin, Jeremiah, Lovitt, Andrew
• Primary Examiner(s): Sough, H S
• Assistant Examiner(s): SEYE, ABDOU K
• Application Number:
  US13/535,599
• Publication Number:
  US 20140007140A1
• Time in Patent Office: 1,496 Days
• Field of Search: None
• US Class Current: 1/1
• 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 system for facilitating dynamic addition and removal of operating system components on a computing device, comprising:

a processor;

a first application programming interface (API) intercept layer that is executable by the processor and capable of intercepting an API call from an application executing on the computing device, said API call being intended for a component of the operating system;

a hydrate engine capable of adding and removing said component of the operating system from the computing device; and

a rules engine, coupled to said API intercept layer and said hydrate engine, capable of;

reading information stored by said first API intercept layer, said information related to said API call from said application executing on the computing device; and

applying at least one hydrate rule, utilizing said information, that is related to a time period said component was last utilized by said application executing on the computing device, and that instructs said hydrate engine to do one of;

add said component to the operating system of the computing device; and

remove said component from the operating system of the computing device.

2. The system of claim 1, wherein said hydrate engine adds said component to the operating system of the computing device by retrieving said component from one of:

a cloud-based service;

a storage located on said computing device; and

a second computing device coupled to said computing device via a network.

3. The system of claim 1, wherein said at least one hydrate rule applied by said rules engine is further based on a mark and sweep model.

4. The system of claim 1, wherein said first API intercept layer is configured to intercept said API call at a first layer of the operating system.

5. The system of claim 4, further comprising:

a second API intercept layer capable of intercepting said API call from said application executing on the computing device;

wherein said second API intercept layer is configured to intercept said API call at a second layer of the operating system.

6. The system of claim 1, wherein said first API intercept layer is configured to intercept said API call from said application executing on the computing device after said API call accesses a shared library file of the operating system.

7. The system of claim 1, wherein the computing device is one of:

a desktop;

a laptop;

a tablet;

a notebook; and

a mobile telephone.

8. A method for facilitating dynamic addition and removal of operating system components on a computing device, the method executing on a processor of the computing device, comprising the steps:

(a) intercepting, by a first application programming interface (API) intercept layer, an API call from an application executing on the computing device, said API call being intended for a component of the operating system;

(b) reading, by a rules engine coupled to said API intercept layer, information stored by said first API intercept layer, said information related to said API call from said application executing on the computing device; and

(c) applying, by said rules engine, at least one hydrate rule that is related to a time period said component was last utilized by said application executing on the computing device and which utilizes said information to instruct a hydrate engine coupled to said rules engine to do one of;

add said component to the operating system of the computing device; and

remove said component from the operating system of the computing device.

9. The method of claim 8, wherein said hydrate engine adds said component to the operating system of the computing device by retrieving said component from one of:

a cloud-based service;

a storage located on said computing device; and

a second computing device coupled to said computing device via a network.

10. The method of claim 8, wherein said at least one hydrate rule applied by said rules engine is further based on a mark and sweep model.

11. The method of claim 8, wherein said first API intercept layer is configured to intercept said API call at a first layer of the operating system.

12. The method of claim 11, further comprising the step of:

(d) intercepting, by a second API intercept layer, said API call from said application executing on the computing device at a second layer of the operating system.

13. The method of claim 8, wherein said first API intercept layer is configured to intercept said API call from said application executing on the computing device after said API call accesses a shared library file of the operating system.

14. The method of claim 8, wherein the computing device is one of:

a desktop;

a laptop;

a tablet;

a notebook; and

a mobile telephone.

15. A computer program product device comprising a computer usable medium having an operating system and control logic stored thereon for causing a computer to facilitate dynamic addition and removal of operating system components, said control logic comprising:

first computer readable program code means for causing the computer to intercept, by a first application programming interface (API) intercept layer, an API call from an application executing on the computer, said API call being intended for a component of the operating system;

second computer readable program code means for causing the computer to read, by a rules engine coupled to said API intercept layer, information stored by said first API intercept layer, said information related to said API call from said application executing on the computer; and

third computer readable program code means for causing the computer to apply, by said rules engine, at least one hydrate rule that is related to a time period said component was last utilized by said application executing on the computing device and which utilizes said information to instruct a hydrate engine coupled to said rules engine to do one of;

add said component to the operating system of the computer; and

remove said component from the operating system of the computer.

16. The computer program product device of claim 15, wherein said hydrate engine adds said component to the operating system of the computer by retrieving said component from one of:

a cloud-based service;

a storage located on said computer; and

a computing device coupled to said computer via a network.

17. The computer program product device of claim 15, wherein said at least one hydrate rule applied by said rules engine is further based on a mark and sweep model.

18. The computer program product device of claim 15, wherein said first API intercept layer is configured to intercept said API call at a first layer of the operating system.

19. The computer program product device of claim 18, further comprising:

fourth computer readable program code means for causing the computer to intercept, by a second API intercept layer, said API call from said application executing on the computer at a second layer of the operating system.

20. The computer program product device of claim 15, wherein said first API intercept layer is configured to intercept said API call from said application executing on the computer after said API call accesses a shared library file of the operating system.