Runtime-Merged Image Fragments for Secure, Low-Downtime OS 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 clean state restoration, while single static images fail to provide customization and security.

Innovation Solution

Implementing a system where image fragments are pre-processed and signed in a build lab, merged at runtime into a read-only volume, allowing for efficient, secure, and customizable updates by separating mutable and immutable states without requiring disk expansion.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If traditional operating system update methods are used, then updates can be installed, but the process is complex, error-prone, and does not provide clean state restoration

Engineering Contradiction:

Improveupdate reliabilityVSAvoidupdate process complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The operating system image is divided into multiple fragments that can be independently processed, signed, and merged. Each fragment represents a specific portion of the OS image that can be updated separately, reducing the complexity of handling large update processes and enabling more reliable partial updates without affecting the entire system.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

Image fragments are pre-processed and signed in a build lab before being deployed to the runtime environment. This preliminary action ensures that fragments are validated and secured before installation, reducing errors during update and ensuring clean state restoration without complex runtime processing.

Inventive Principle:

Principle #10Preliminary action

2Adaptability or versatility

If static OS images are used, then the system is simple, but customization and security are limited

Engineering Contradiction:

ImproveOS customizationVSAvoidimage management complexity

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system transitions from static OS images to dynamic composition of multiple fragments at runtime. Fragments can be selectively merged based on customization requirements, allowing the OS to adapt to different configurations and security requirements without requiring multiple static images, thus achieving versatility without proportionally increasing complexity.

Inventive Principle:

Principle #15Dynamics

Solution Approach 2:

Multiple image fragments are merged at runtime to create the final OS image composition. This merging mechanism allows customization by selecting and combining different fragments as needed, providing flexibility without requiring maintenance of multiple complete static images, thereby reducing overall management complexity.

Inventive Principle:

Principle #5Merging (Combining)

3Productivity

If complex processing is performed during update, then updates can be applied, but I/O speed decreases and downtime increases

Engineering Contradiction:

Improveupdate speedVSAvoidsystem downtime

Core Design Contradiction:

ProductivityVSLoss of time

Solution Approach 1:

Image fragments are pre-processed, validated, and signed in the build lab before deployment. This eliminates complex processing during runtime updates, allowing fragments to be directly merged and applied without extensive validation or processing, thereby significantly reducing update time and system downtime while maintaining high productivity.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The update process skips intermediate processing steps by using pre-processed fragments that require only merging and validation at runtime. This rushing through of the update process eliminates lengthy processing operations, enabling faster installation and reducing the time the system is unavailable, thus improving both productivity and minimizing time loss.

Inventive Principle:

Principle #21Skipping (Rushing through)

4Adaptability or versatility

If fragments are merged at runtime, then customization is enabled, but processing overhead increases

Engineering Contradiction:

Improveimage customizationVSAvoidprocessing energy

Core Design Contradiction:

Adaptability or versatilityVSUse of energy by moving object

Solution Approach 1:

Fragments are pre-processed and prepared in the build lab, including all necessary metadata and validation. This preliminary preparation reduces the processing overhead at runtime, as the system only needs to merge pre-validation fragments rather than performing comprehensive processing, thereby enabling customization with minimal energy consumption during runtime operations.

Inventive Principle:

Principle #10Preliminary action

Data Source

PatentUS12386608B2Boot and update from runtime merged image fragments

Publication Date: 2025.08.12 MICROSOFT TECHNOLOGY LICENSING LLC

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.