Boot negotiation among multiple boot-capable devices

• US 7,818,559 B2
• Filed: 02/28/2007
• Issued: 10/19/2010
• Est. Priority Date: 02/28/2007
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Hasbun, Robert, Sadovsky, Vladimir, Teegan, Hugh A., Alexander, Robin A.
• Primary Examiner(s): Lee; Thomas
• Assistant Examiner(s): KINSEY, BRANDON MICHAEL
• Application Number:
  US11/680,040
• Publication Number:
  US 20080209199A1
• Time in Patent Office: 1,329 Days
• Field of Search: 713/1, 713/2, 713/100, 709/201, 709/208, 709/227
• US Class Current: 713/2
• CPC Class Codes: G06F 9/4401 Bootstrapping security arrangements therefor G06F21/57
• CPC Class Codes: G06F 9/4406 Loading of operating system
• CPC Class Codes: G06F 9/45533 Hypervisors; Virtual machine monitors

Abstract

A first device discovers the capabilities of a second device. The first device determines which of the first device and the second device is to execute a controlling boot image based at least in part on the capabilities of the first device and the second device. A first boot image is executed by the first device when the first device is determined to execute the controlling boot image, the second device to be a resource for the first boot image. The first device sends a second boot image stored on the first device to the second device when the second device is determined to execute the controlling boot image, wherein the first device to be a resource for the second boot image.

Claims

1. A method, comprising:

discovering, by a first device, the capabilities of a second device;

determining, by the first device, which of the first device and the second device is to execute a controlling boot image based at least in part on the capabilities of the first device and the second device;

executing a first boot image by the first device when the first device is determined to execute the controlling boot image, the second device to be a resource for the first boot image; and

sending, by the first device, a second boot image stored on the first device to the second device for execution when the second device is determined to execute the controlling boot image, wherein the first device to be a resource for the second boot image.

2. The method of claim 1, comprising:

determining, by the first device, whether the second boot image is compatible with the second device.

3. The method of claim 1, comprising:

determining, by the first device, whether executing the second boot image on the second device is in compliance with a boot policy stored on the first device.

4. The method of claim 3, comprising:

updating the boot policy, by the first device, by contacting a central site before determining whether executing the second boot image on the second device is in compliance with the boot policy stored on the first device.

5. The method of claim 1, comprising:

updating, by the first device, the second boot image before sending the second boot image to the second device.

6. The method of claim 1, comprising:

entering a sleep state by an operating system executing on the first device after sending the second boot image to the second device; and

waking up from the sleep state when a connection between the first device and the second device is severed.

7. The method of claim 1, comprising:

establishing a connection between the first device and the second device, wherein the first device is in operating system runtime and the second device is in preboot.

8. The method of claim 1 wherein discovering the capabilities of the second device comprises receiving, at the first device, capabilities reporting data from the second device in response to a capabilities query from the first device.

9. The method of claim 1, comprising:

authenticating the second device by the first device.

10. The method of claim 1, wherein determining which of the first device and the second device is to execute a controlling boot image comprises receiving, at the first device, confirmation of the determination from a user.

11. A method, comprising:

making a connection between a mobile device and a dock, wherein the mobile device is executing a first boot image and the dock is in preboot;

determining which of the mobile device and the dock to execute a controlling boot image based at least in part on capabilities of the mobile device and the dock;

when the dock is to execute the controlling boot image, sending a second boot image from the mobile device to the dock and executing the second boot image on the dock, wherein the second boot image includes the controlling boot image; and

when the mobile device is to execute the controlling boot image, executing the first boot image on the mobile device, wherein the first boot image includes the controlling boot image.

12. The method of claim 11 wherein determining which of the mobile device and the dock to execute a controlling boot image comprises determining if the dock is compatible with one or more boot images stored on the mobile device.

13. The method of claim 11 wherein the second boot image is executed in a virtual machine environment of the dock.

14. The method of claim 11, comprising:

updating the second boot image by the mobile device prior to sending the second boot image to the dock for execution on the dock.

15. The method of claim 11 wherein when the dock is to execute the controlling boot image, comprising:

entering a sleep state by the first boot image executing on the mobile device.

16. The method of claim 11, comprising:

receiving, at the mobile device, capabilities reporting data from the dock in response to a capabilities query from the mobile device.

17. A system, comprising:

a first computing device connected to a second computing device, wherein the first computing device having stored computer readable instructions that when executed by the first computing device perform operations comprising;

discovering capabilities of the second computing device;

determining which of the first computing device and the second computing device is to execute a controlling boot image based at least in part on capabilities of the first computing device and the capabilities of the second computing device;

executing a first boot image by the first computing device when the first computing device is determined to execute the controlling boot image, the second computing device to be a resource for the first boot image; and

sending the second boot image stored on the first computing device to the second computing device for execution when the second computing device is determined to execute the controlling boot image, wherein the first computing device to be a resource for the second boot image.

18. The system of claim 17 wherein determining which of the first computing device and the second computing device is to execute a controlling boot image comprises determining if the second computing device is compatible with one or more boot images stored on the first computing device.

19. The system of claim 17 wherein determining which of the first computing device and the second computing device is to execute a controlling boot image comprises applying policy stored on the first computing device.

20. The system of claim 17 wherein determining which of the first computing device and the second computing device is to execute a controlling boot image comprises receiving confirmation of the determination from a user.