Distributed File Management Architecture with Automatic Version Sync

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Modern computing systems fail to provide a seamless environment for file management across multiple devices, leading to issues such as redundant file copies, error-prone environments, unnecessary complexity, and inefficient access due to lack of integration with applications and network dependencies.

Innovation Solution

Utilizing mobile agent objects to automatically transfer and synchronize files across computer systems, ensuring consistent file versions and accessibility by encoding and decoding these objects for execution on remote hosts, and using a server to manage file synchronization and storage.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If files are manually moved between devices using protocols like email, FTP, or web posting, then file transfer capability is achieved, but redundant file copies proliferate and create confusion about the official version

Engineering Contradiction:
Improvemanual file transfer capabilityVSAvoidfile version consistency
Core Design Contradiction:
Ease of operationVSLoss of information

Solution Approach 1:

The system implements automatic feedback mechanisms where file changes on one device are detected and automatically propagated to other devices. The file management system monitors modification events and triggers synchronization operations, ensuring that all devices receive updates about the latest file versions without manual intervention.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The file synchronization system operates autonomously without requiring user intervention. When a file is modified on any device, the system automatically detects the change, determines the appropriate actions, and executes the synchronization process, making the system self-managing and eliminating manual file transfer needs.

Inventive Principle:
Principle #25Self-service

2Ease of operation

If files are manually copied between devices, then file accessibility is improved, but the environment becomes error-prone with broken references in documents

Engineering Contradiction:
Improvefile accessibilityVSAvoiddocument reference integrity
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The system performs preliminary actions by pre-synchronizing all related files before they are needed. When a document is accessed, the system ensures that all referenced files are already present on the device, preventing broken links and reference errors. This proactive approach maintains document integrity across devices.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The file management system provides universal synchronization capabilities that work across all file types and devices. A single synchronization mechanism handles documents, images, and all associated references uniformly, ensuring that the same reliable process maintains integrity regardless of file type or device platform.

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

3Adaptability or versatility

If each device maintains its own filing system, then device autonomy is preserved, but unnecessary complexity arises in managing multiple filing models and security models

Engineering Contradiction:
Improvedevice independenceVSAvoidfiling system management complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system introduces a file management intermediary layer that sits between the user and the various device filing systems. This intermediary provides a unified interface and abstraction layer, allowing users to interact with a consistent file management model while the intermediary handles the complexity of translating operations across different device-specific filing systems and security models.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The file management architecture is segmented into distinct functional layers: a user-facing abstraction layer, a synchronization management layer, and device-specific implementation layers. This segmentation allows each layer to operate independently with well-defined interfaces, reducing overall system complexity while maintaining device autonomy.

Inventive Principle:
Principle #1Segmentation

4Ease of operation

If remote desktop software is used to access files on a host machine, then file accessibility is improved, but the host machine must remain turned on and connected to the internet

Engineering Contradiction:
Improveremote file accessVSAvoidnetwork dependency
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The system pre-synchronizes files to local devices before they are needed, so that files are available offline without requiring the host machine to be online. This preliminary action eliminates the need for continuous network connectivity or remote desktop sessions, allowing users to access files locally even when disconnected from the network.

Inventive Principle:
Principle #10Preliminary action

5Ease of operation

If distributed file systems are used to share files between devices, then file sharing capability is improved, but files may be buried deep in filing structures and access is not immediately evident

Engineering Contradiction:
Improvefile sharing capabilityVSAvoidfile location discoverability
Core Design Contradiction:
Ease of operationVSDifficulty of detecting and measuring

Solution Approach 1:

The file management system provides an intermediary interface that abstracts the complex distributed filing structure from users. This intermediary presents files in a unified, device-agnostic view that shows all accessible files regardless of their physical location in the distributed system, making file discovery immediate and intuitive without requiring users to navigate deep folder structures.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS20250328491A1Architecture for management of digital files across distributed network
Publication Date: 2025.10.23 TOPIA TECH
  • US20250328491A1 patent drawing
  • US20250328491A1 patent drawing
  • US20250328491A1 patent drawing

AI summary

In certain embodiments, automatic modification-triggered transfer of a file among two or more computer systems associated with a user. In some embodiments, a copy of a first file may be received, via a first application at a first computer system, from a second application at a second computer system associated with a user. The first file copy may be automatically received from the second application responsive to the user modifying a content of the first file, where the first file copy is a version of the first file that is generated from the user modifying the content of the first file. Responsive to receiving the first file copy from the second computer system, the first file copy may be automatically transferred via the first application to a third computer system associated with the user to replace an older version of the first file stored on the third computer system.