Runtime Image Fragment Merging for Secure OS Boot Updates

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing operating system update methods are inefficient, prone to errors, and lack flexibility, requiring complex processing and often result in incomplete restoration to a known clean state, while single static images fail to provide customization and security.

Innovation Solution

Implementing a system where operating system images are composed using pre-packaged image fragments that are merged at runtime, allowing for quick and dynamic combination into a read-only OS image, with complex processing done offline in a build lab, and using signed containers for security.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Manufacturing precision

If a single large image is downloaded and stored before runtime, then image quality and completeness are improved, but memory consumption and startup time increase

Engineering Contradiction:

Improveimage qualityVSAvoidmemory consumption

Core Design Contradiction:

Manufacturing precisionVSQuantity of substance

Solution Approach 1:

The image is divided into multiple fragments that are downloaded and stored separately in the manifest. Each fragment occupies a portion of the total image data, allowing selective loading and reduced memory consumption while maintaining complete image quality when all fragments are assembled at runtime.

Inventive Principle:

Principle #1Segmentation

2Manufacturing precision

If a single large image is downloaded and stored before runtime, then image quality and completeness are improved, but startup time increases

Engineering Contradiction:

Improveimage qualityVSAvoidstartup time

Core Design Contradiction:

Manufacturing precisionVSLoss of time

Solution Approach 1:

Inventive Principle:

Principle #1Segmentation

3Quantity of substance

If multiple image fragments are downloaded and merged at runtime, then memory consumption and startup time are improved, but device complexity increases

Engineering Contradiction:

Improvememory consumptionVSAvoidsystem complexity

Core Design Contradiction:

Quantity of substanceVSDevice complexity

Solution Approach 1:

The manifest is prepared in advance during the build process, containing all the information needed to locate and assemble image fragments at runtime. This preliminary organization of fragment metadata eliminates the need for complex runtime image processing logic, reducing device complexity despite the fragmented approach.

Inventive Principle:

Principle #10Preliminary action

4Quantity of substance

If multiple image fragments are downloaded and merged at runtime, then memory consumption and startup time are improved, but loss of information increases

Engineering Contradiction:

Improvememory consumptionVSAvoidimage data integrity

Core Design Contradiction:

Quantity of substanceVSLoss of information

Solution Approach 1:

The manifest contains verification information and metadata that enables runtime validation of fragment integrity and correct assembly. This feedback mechanism ensures that image data is reconstructed accurately from fragments, preventing information loss despite the fragmented storage approach.

Inventive Principle:

Principle #23Feedback

Data Source

PatentEP4433893B1Boot and update from runtime merged image fragments

Publication Date: 2026.04.29 MICROSOFT TECHNOLOGY LICENSING LLC

Figure 1A
Figure 1B
Figure 1C

AI summary

A feature is updated on a computing device. One or more composite image files are accessed that correspond to updates to be implemented in the computing device. The composite image files are signed containers. A runtime in-memory merge of the composite image files is performed. The merged composite image files are exposed as a read-only volume. The features are made available to the computing device. A system boot using the read-only volume can be initiated.