Self-describing software image update components

• US 7,549,148 B2
• Filed: 05/01/2004
• Issued: 06/16/2009
• Est. Priority Date: 12/16/2003
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Cross, Brian D., Glaum, Jeffrey D., McNeill, Lorna Rebecca, Shell, Scott R., Markley, Michael E.
• Primary Examiner(s): Zhen; Wei Y.
• Assistant Examiner(s): Chow; Chih-Ching
• Application Number:
  US10/837,024
• Publication Number:
  US 20050132356A1
• Time in Patent Office: 1,872 Days
• Field of Search: 717/174
• US Class Current: 717/174
• CPC Class Codes: G06F 8/658 Incremental updates; Differential updates

Abstract

Described is a system and method in which software images including updates are provided as packages. The package is self-describing, thereby facilitating the replacement of only component parts of an image. A software build process maps operating system features (comprising files, metadata, configuration information and so forth) into the packages, and executable code is processed for relocation purposes. The final package includes a device manifest file that describes the package and conveys dependency information and information about the priority of settings (shadow data).

Claims

1. In a mobile computing system comprising a software image that includes operating system files and other associated software application files, a method for updating a portion of the files in the software image, the software image being stored in embedded system memory, the method comprising:

building a self-describing package, the package corresponding to part of an operating system image and containing files and registry settings, the package comprising a package manifest file that describes the binary structure of the image into which the package will be incorporated, the package including at least some language-independent executable code files configured for processing in any language that are separate from language-dependent data files, such that at least some of the executable code is independent of language-specific processing;

generating a build manifest file that specifies the file contents for the self-describing package;

generating a device manifest file that describes a set of information about the package including dependency and package settings priority information for the mobile computing system, the device manifest file being stored in the self-describing package and being configured to receive list and attribute information from the build manifest;

inserting one or more feature handles into the generated device manifest file, the feature handles specifying one or more software features that are to be included in the package such that those individual files, registry settings and libraries comprising the software features that are mapped with this feature are automatically included in the device manifest file, wherein individual feature mapping is omitted;

associating information in the package manifest file, the build manifest file and the device manifest file, including the inserted feature handles, with the self-describing package that describes the contents of the package such that an installation mechanism can determine how to install the package to a device; and

installing the files of the self-describing package according to the corresponding manifest files, wherein only those files identified in the self-describing package are overwritten in the software image.

2. The method of claim 1 wherein the information associated with the package comprises a device manifest file, and further comprising, adding the device manifest file to the package.

3. The method of claim 2 further comprising writing data into the device manifest file comprising dependency information that describes a dependency of at least some contents of the package on another entity.

4. The method of claim 3 wherein the other entity comprises another package, and further comprising extracting the device manifest file from the package and extracting another device manifest file from the other package.

5. The method of claim 2 further comprising writing data into the device manifest file comprising shadow information that describes precedence of settings data relative to other settings data.

6. The method of claim 1 wherein building a package comprises, determining which files are executable files and performing a relocation process on the executable files.

7. The method of claim 1 wherein associating information with the package that describes the contents of the package comprises associating dependency information that describes a dependency of at least some contents of the package on another entity.

8. The method of claim 1 wherein associating information with the package that describes the contents of the package comprises associating shadow information that describes precedence of settings data relative to other settings data.

9. The method of claim 1 wherein building a package comprises mapping a package to a definition for that package that defines existing files, reading a build manifest file that specifies the file contents for that package, and generating the package based on the package definition and the build manifest file.

10. The method of claim 9 further comprising creating the build manifest file from a binary image builder file for the operating system image and a component to package mapping file.

11. The method of claim 10 further comprising processing executable code identified in the build manifest file, to enable executable code relocation at install time to a device.

12. The method of claim 1 wherein building the package comprises reading a binary image builder file that contains a list of files to be included in the package when built.

13. The method of claim 1 wherein building the package comprises creating a build manifest file corresponding to the binary image builder file and reading the build manifest file.

14. The method of claim 1 wherein building the package comprises reading a settings file that contains a list of setting information to be included in the package when built.

15. The method of claim 1 wherein building the package comprises reading a component mapping file that maps module-related information and files to the package.

16. The method of claim 1 wherein building the package comprises reading a component relationships file that defines shadow relationships.

17. The method of claim 16 wherein the information associated with the package comprises a device manifest file, and further comprising, writing information to the device manifest file based on the shadow relationships, and adding the device manifest file to the package.

18. The method of claim 1 wherein building the package comprises reading a component relationships file that defines dependency relationships.

19. The method of claim 16 wherein the information associated with the package comprises a device manifest file, and further comprising, writing information to the device manifest file based on the dependency relationships, and adding the device manifest file to the package.

20. The method of claim 1 wherein building the package comprises reading a package definition file that defines what packages exist.

21. At least one computer-readable storage media having computer-executable instruction which when executed perform the method of claim 1.

22. In a mobile computing system comprising a software image that includes operating system files and other associated software application files, a system for updating a portion of the files in the software image, the software image being stored in embedded system memory, the system comprising:

a system memory;

a package generation process that builds a self-describing package containing files and registry settings, the package comprising a package manifest file that describes the binary structure of the image into which the package will be incorporated, the package including at least some language-independent executable code files configured for processing in any language that are separate from language-dependent data files, such that at least some of the executable code is independent of language-specific processing;

a build manifest file generation process that generates a build manifest file that specifies the file contents for the self-describing package;

a device manifest file generation process that generates a device manifest file that describes a set of information about the package including dependency and package settings priority information for the mobile computing system, the device manifest file being stored in the self-describing package and being configured to receive list and attribute information, from the build manifest;

a feature handle inserting process that inserts one or more feature handles into the generated device manifest file, the feature handles specifying one or more software features that are to be included in the package such that those individual files, registry settings and libraries comprising the software features that are mapped with this feature are automatically included in the device manifest file, wherein individual feature mapping is omitted;

a package associating process that associates information in the package manifest file, the build manifest file and the device manifest file, including the inserted feature handles, with the self-describing package to describe the contents of the package, the information including component relationship information; and

an installation process that installs the files of the self-describing package according to the corresponding manifest files, wherein only those files identified in the self-describing package are overwritten in the software image.

23. The system of claim 22 wherein the component relationship information describes a dependency on another entity.

24. The system of claim 23 wherein the other entity is another package.

25. The system of claim 22 wherein the component relationship information describes a shadow relationship with another entity.

26. The system of claim 25 wherein the other entity is another package.

27. The system of claim 22 wherein the package generation process determines which files are executable files and performs a relocation process on the executable files.

28. The system of claim 22 wherein the package generation process allows a distinction between at least some executable code and data such that at least some of the executable code is independent of any language.