Distributed File Management Difference Data Registration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In distributed file management systems, the integration of blockchain requires managing both updated and pre-updated files, leading to increased file sizes due to the need for new registrations, which complicates the system's efficiency.

Innovation Solution

An update device and method that create difference data between original and updated files, along with a route object linking the original file and difference data, are used to register only the difference data and route object in the system, reducing the average file size by allowing efficient retrieval of updated files through recursive processing.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the updated file is newly registered in the distributed file management system, then the file update is completed, but the average file size per file managed in the system becomes large

Engineering Contradiction:
Improvefile update completionVSAvoidaverage file size
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The patent segments the updated file into two components: the original file (retained in the system) and the difference data (newly registered). This segmentation allows the system to store only the changes rather than the entire updated file, thereby reducing the average file size while maintaining complete file version history for reliability.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent extracts the essential change information from the updated file and registers only this difference data in the distributed file management system. The original file is referenced through the route object, allowing the system to take out only the necessary new information while preserving access to the complete file through the link to the original file.

Inventive Principle:
Principle #2Taking out (Extraction)

2Reliability

If the blockchain is cooperated with the distributed file management system, then the robustness against falsification is improved, but the file sizes to be managed in the entire system become large

Engineering Contradiction:
Improverobustness against falsificationVSAvoidfile size
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The patent segments file management into two parts: the immutable blockchain record (containing only difference data and route objects for robustness) and the full file storage (original files retained in the distributed file management system). This segmentation allows blockchain to provide robustness for metadata and version history while avoiding the need to store entire large files on the blockchain.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces a route object as an intermediary between the blockchain and the actual file data. The route object contains links to both the original file and the difference data, serving as a mediator that allows the blockchain to reference files without storing their full contents, thus maintaining robustness while reducing storage requirements.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Quantity of substance

If the difference data and route object are registered instead of the updated file, then the average file size is reduced, but the system complexity increases

Engineering Contradiction:
Improveaverage file sizeVSAvoidsystem complexity
Core Design Contradiction:
Quantity of substanceVSDevice complexity

Solution Approach 1:

The patent makes the route object a multi-functional element that serves multiple purposes: it acts as a reference link to the original file, stores information about the difference data, and provides the structure for version history management. This universality reduces the need for separate data structures and simplifies the overall system despite the introduction of difference data registration.

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

Solution Approach 2:

The patent implements a nested structure where the route object contains links to both the original file and the difference data, creating a compact representation of the file version history. This nesting allows the system to manage multiple file versions efficiently without requiring separate management structures for each version, thereby reducing operational complexity.

Inventive Principle:
Principle #7Nested doll (Nesting)

Data Source

PatentUS12050559B2Data update device, data update method, data update program, and data structure
Publication Date: 2024.07.30 NIPPON TELEGRAPH & TELEPHONE CORP
  • US12050559B2 patent drawing
  • US12050559B2 patent drawing
  • US12050559B2 patent drawing

AI summary

When an updated file that is an updated version of an original file is registered in a distributed file management system 100, a difference creation unit 222 creates a difference file between the original file and the updated file, a route object creation unit 223 creates a route object that includes an ID of the original file and an ID of the difference file, and a distributed file management client 11 causes the difference file and the route object to be registered in the distributed file management system 100.