Virtual File System Layer Compression for Storage Capacity

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Portable electronic devices face performance issues due to insufficient storage capacity, necessitating efficient file reading and writing methods that do not compromise device performance.

Innovation Solution

An electronic device with a software layer structure including a first virtual file system layer, a compressed file system layer, and a second virtual file system layer, which compresses and decompresses files as needed to manage storage efficiently without reducing device performance.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Quantity of substance

If files are compressed to increase storage capacity, then storage space is improved, but device performance may deteriorate due to compression and decompression operations

Engineering Contradiction:
Improvestorage capacityVSAvoiddevice performance
Core Design Contradiction:
Quantity of substanceVSProductivity

Solution Approach 1:

The patent divides the file system into multiple virtual layers (first virtual file system layer, compressed file system layer, second virtual file system layer) that operate independently. Each layer handles specific tasks: the first layer manages file access requests, the compressed layer performs compression/decompression, and the second layer manages stored data. This segmentation allows storage compression to occur without blocking overall device performance, as operations are distributed across layers rather than serialized.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces virtual file system layers as intermediary components between the application and the physical storage. These virtual layers act as mediators that buffer and manage compression operations, preventing direct performance impact on the device. The virtual file system layers handle compression asynchronously and manage data flow between the application and compressed storage, isolating performance-critical operations from the main execution path.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Device complexity

If a simple file system structure is used, then device complexity is reduced, but storage efficiency deteriorates due to insufficient compression capability

Engineering Contradiction:
Improvefile system structureVSAvoidstorage efficiency
Core Design Contradiction:
Device complexityVSQuantity of substance

Solution Approach 1:

The patent implements a nested multi-layer file system structure where virtual file system layers are embedded within each other. The first virtual file system layer sits above the compressed file system layer, which in turn sits above the second virtual file system layer that interfaces with physical storage. This nesting allows complex compression functionality to be integrated within the file system hierarchy without exposing complexity to the application layer, maintaining simplicity for users while achieving storage efficiency through compression.

Inventive Principle:
Principle #7Nested doll (Nesting)

Data Source

PatentUS10209915B2Electronic device and file read and write method thereof
Publication Date: 2019.02.19 SAMSUNG ELECTRONICS CO LTD
  • US10209915B2 patent drawing
  • US10209915B2 patent drawing
  • US10209915B2 patent drawing

AI summary

An electronic device is provided. The electronic device includes at least one first memory being nonvolatile and a processor configured to read a file from the first memory or to write a file on the first memory. The first memory stores instructions, the instructions, when executed, causing the processor to provide a software layer structure including a first virtual file system layer configured to interface with an application program layer, a compressed file system layer configured to compress at least a part of data of the written file or to decompress at least a part of data of the read file, a second virtual file system layer configured to manage the written or read file, and a first file system layer configured to read at least a part of the file from the first memory or to write at least a part of the file on the first memory.