Delta Set File Management Reducing Storage Redundancy
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current file management systems face issues with redundancy, leading to decreased storage capacity, dispersed information, and complex versioning, as full files are often transmitted and stored multiple times, making it cumbersome to track and manage changes effectively.
Innovation Solution
A delta device that stores full versions of files and updates them based on delta information, using a tree structure to track changes over time and by user identity, allowing for efficient storage and transmission of modifications while controlling access and optimizing change data to reduce redundancy, and utilizing blockchain for secure transactions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If full files are transmitted and stored multiple times for each modification, then file sharing and versioning are achieved, but storage capacity decreases geometrically and transmission bandwidth is overburdened
Solution Approach 1:
The patent segments files into delta sets representing incremental changes between versions. Instead of storing complete file copies for each modification, the system stores only the differential portions (delta sets) that capture specific changes. This segmentation allows efficient storage where each delta set contains only the necessary modification data, reducing overall storage requirements while maintaining complete version history.
Solution Approach 2:
The patent extracts and stores only the essential change information from full file comparisons. By identifying and isolating the specific delta sets that represent modifications, the system removes redundant data while preserving versioning capability. This extraction process creates a compact representation of file evolution without requiring full file storage for each version.
2Loss of information
If full files are transmitted for sharing and editing, then complete information is available to users, but transmission bandwidth is overburdened
Solution Approach 1:
The patent segments file transmission into selective delta set transfers rather than complete file transmissions. Users receive only the specific delta sets they need to reconstruct desired file versions, significantly reducing transmission bandwidth requirements while maintaining information completeness through incremental application of change sets.
Solution Approach 2:
The system performs preliminary processing to identify and prepare delta sets before transmission. By pre-computing and organizing change sets in advance, the system enables efficient selective transmission of only necessary data portions, reducing real-time bandwidth consumption while ensuring complete information delivery.
3Speed
If separate local versions are stored by users, then access speed is improved, but information becomes dispersed and versioning becomes complex
Solution Approach 1:
The patent implements a universal delta set structure that serves multiple functions simultaneously: enabling fast local access through cached delta sets, maintaining centralized version control through server-managed delta repositories, and simplifying versioning through standardized change representations. This multi-functional approach resolves the trade-off between access speed and versioning complexity.
Solution Approach 2:
The system incorporates feedback mechanisms where users can query the server for available delta sets and receive notifications about new versions. This feedback loop enables users to maintain local caches efficiently while the server coordinates version management, reducing both access delays and versioning complexity through synchronized information exchange.
Data Source
AI summary
A delta set information management device (delta device) stores full versions of files and updates such files based upon delta information. The delta device can be a web server running delta software. It can store original files as either seed files or node files in a tree structure and store modifications to seed files and node files based upon the time and identity of the entity (e.g., user or computer) that requested or made such modifications.