Composite Image Block Storage for Space-Reusing File Replacement

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current composite image (CIM) formats for containerization technologies inefficiently use storage space when extending filesystem volumes due to variable-sized data portions, leading to waste and inefficiencies in constructing, extracting, and deleting files.

Innovation Solution

Implementing data region files with fixed-size data blocks and block-level deduplication to efficiently reuse space and reduce redundancy by using fixed-size data blocks and block-level deduplication within CIMs.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If variable-sized data portions are used in CIM formats, then flexibility in storing different file sizes is improved, but storage space efficiency deteriorates due to waste and inability to reuse space

Engineering Contradiction:
Improveflexibility in storing different file sizesVSAvoidstorage space efficiency
Core Design Contradiction:
Adaptability or versatilityVSLoss of substance

Solution Approach 1:

The patent segments data storage into fixed-size blocks within data region files. Each file is represented as a collection of fixed-size data blocks rather than variable-sized portions, enabling efficient space reuse while maintaining flexibility through block-level allocation and deallocation mechanisms

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent changes the fundamental parameter of data storage from variable-sized portions to fixed-size blocks. This parameter change enables efficient space management by allowing blocks to be reused when files are deleted or modified, eliminating the storage waste inherent in variable-sized portion systems

Inventive Principle:
Principle #35Parameter changes

2Loss of substance

If fixed-size data blocks are used in CIM formats, then storage space efficiency is improved through reuse, but device complexity increases due to block-level management requirements

Engineering Contradiction:
Improvestorage space efficiencyVSAvoidblock-level management complexity
Core Design Contradiction:
Loss of substanceVSDevice complexity

Solution Approach 1:

The patent segments data into fixed-size blocks and introduces metadata structures to track block allocation. This segmentation approach simplifies management by providing uniform block units that can be efficiently allocated, deallocated, and reused without complex variable-size management logic

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces metadata as an intermediary layer between the fixed-size data blocks and the filesystem operations. This metadata layer abstracts the block-level management complexity, providing a simplified interface for file operations while enabling efficient block reuse underneath

Inventive Principle:
Principle #24Intermediary (Mediator)

3Loss of substance

If block-level deduplication is implemented, then redundant data storage is minimized and storage efficiency is improved, but processing time increases due to deduplication operations

Engineering Contradiction:
Improveredundant data storageVSAvoidprocessing time
Core Design Contradiction:
Loss of substanceVSLoss of time

Solution Approach 1:

The patent uses copying mechanisms to implement block-level deduplication by creating references to identical data blocks rather than storing duplicate copies. When blocks are added to the CIM, the system checks for existing identical blocks and creates references to them, eliminating redundant storage while maintaining fast access through direct block references

Inventive Principle:
Principle #26Copying

Data Source

PatentUS12596677B2Storing files in blocks within composite images
Publication Date: 2026.04.07 MICROSOFT TECHNOLOGY LICENSING LLC
  • US12596677B2 patent drawing
  • US12596677B2 patent drawing
  • US12596677B2 patent drawing

AI summary

Using a block-based region file to extend a composite image (CIM). A device determines to replace a first file with a second file within a filesystem volume of the CIM. The device identifies a first file definition within CIM metadata, which defines the first data of the first file as including a first data block of a first CIM region file comprising equally-sized data blocks. The device extends the CIM to include the second file. The extension includes adding a second region file comprising equally-sized data blocks to the CIM, including writing a portion of data from the second file into a second data block of the second region file. The extension also includes writing a second file definition to the CIM metadata, which defines the second data of the second file as including the first data block and the second data block.