File System Update Simulation for Limited Storage

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Computing devices with small storage devices face challenges in updating applications and file systems due to limited space, leading to potential failures and inefficient file storage and execution, especially with wasted space from null data and fragmentation.

Innovation Solution

A method that simulates updates to ensure success, addresses storage on a per-sector basis with internal chunk management, and executes files directly from storage using virtual address translation, allowing for efficient use of space and immediate execution.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If update data is written to unused space before deleting old data, then update can be performed, but insufficient space prevents this approach on small storage devices

Engineering Contradiction:
Improveupdate success rateVSAvoidavailable storage space
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The patent deletes old data before writing update data to ensure space availability. This preliminary deletion action resolves the space constraint by freeing up storage capacity before the update operation, allowing the update to proceed without requiring additional unused space that may not be available on small storage devices.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent implements a backup mechanism that creates a backup image of the storage device before performing updates. This beforehand cushioning provides a safety net that allows the system to restore the previous state if the update fails, thereby ensuring update reliability even when space constraints prevent traditional update approaches.

Inventive Principle:
Principle #11Beforehand cushioning (Prior cushioning)

2Quantity of substance

If old data is deleted before update, then space is freed for update data, but update failure leaves no way to restore the computing device

Engineering Contradiction:
Improveavailable storage spaceVSAvoidsystem recoverability
Core Design Contradiction:
Quantity of substanceVSReliability

Solution Approach 1:

The patent creates a backup image of the entire storage device before deleting old data or performing updates. This beforehand cushioning ensures that if the update fails, the system can restore the previous state from the backup, maintaining system recoverability while still allowing space to be freed for the update operation.

Inventive Principle:
Principle #11Beforehand cushioning (Prior cushioning)

3Ease of manufacture

If files are stored on a per-cluster basis, then file storage is simplified, but significant space is wasted on small storage devices

Engineering Contradiction:
Improvefile storage simplicityVSAvoidwasted storage space
Core Design Contradiction:
Ease of manufactureVSLoss of substance

Solution Approach 1:

The patent divides the storage device into smaller units called chunks, which are smaller than traditional clusters. This segmentation allows files to be allocated more efficiently, reducing the wasted space that occurs when small files occupy entire large clusters. The chunk-based allocation maintains simplicity while significantly reducing space waste on small storage devices.

Inventive Principle:
Principle #1Segmentation

4Stability of the object's composition

If null data is stored in files, then file structure is maintained, but storage space is wasted

Engineering Contradiction:
Improvefile structure integrityVSAvoidstorage space utilization
Core Design Contradiction:
Stability of the object's compositionVSLoss of substance

Solution Approach 1:

The patent extracts and removes null data from files, keeping only the substantive data. This extraction maintains file structure integrity by preserving the logical organization of files while eliminating wasted space occupied by null data. The system can reconstruct null portions when needed, but the actual storage space is not consumed by these empty regions.

Inventive Principle:
Principle #2Taking out (Extraction)

5Ease of operation

If files are loaded into RAM before execution, then execution is smooth, but loading time delays immediate execution

Engineering Contradiction:
Improveexecution smoothnessVSAvoidfile loading time
Core Design Contradiction:
Ease of operationVSLoss of time

Solution Approach 1:

The patent enables the storage device to serve multiple functions: it acts as both long-term storage and as executable memory. By making the storage device directly addressable and capable of executing files in place, the system eliminates the need to load files into RAM before execution. This multi-functionality allows immediate execution while maintaining smooth operation through virtual address translation.

Inventive Principle:
Principle #6Universality (Multi-functionality)

6Volume of moving object

If storage device is made smaller to fit portable device, then device portability is improved, but file system operations become more difficult

Engineering Contradiction:
Improvestorage device sizeVSAvoidfile system operation complexity
Core Design Contradiction:
Volume of moving objectVSDevice complexity

Solution Approach 1:

The patent segments the storage device into small chunks that can be efficiently managed even on very small storage devices. This segmentation, combined with chunk-based allocation, simplifies file system operations by providing a uniform, fine-grained allocation unit that works effectively regardless of the total storage size, thereby reducing operational complexity on portable devices with limited storage capacity.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent creates a universal file system framework that handles both small and large storage devices using the same chunk-based allocation mechanism. This universality simplifies file system operations by providing a consistent interface and allocation strategy that works efficiently on portable devices with small storage, eliminating the need for complex size-specific handling logic.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentUS7698699B2Computing device with relatively limited storage space and operating/file system thereof
Publication Date: 2010.04.13 MICROSOFT TECHNOLOGY LICENSING LLC
  • US7698699B2 patent drawing
  • US7698699B2 patent drawing
  • US7698699B2 patent drawing

AI summary

A method is provided for updating an application residing on a storage device of a computing device. The update is simulated by performing all necessary actions except for actually committing data relating to the update to the storage device, and it is determined whether the simulated update succeeded. If so, the update is performed by performing the same necessary actions and also actually committing the data relating to the update to the storage device.