Distributed File Management With Modification-Triggered Synchronization

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 manual file transfer and synchronization, which existing solutions like remote desktop, distributed file systems, FTP, and email attachments exacerbate.

Innovation Solution

Implementing mobile agent objects that automatically transfer and synchronize files across computer systems in response to user modifications, using a server to manage file synchronization and ensure the latest version is accessible on all devices, while maintaining a unified file organization and access method.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If manual file transfer methods (email, FTP, Web posting) are used to share files between devices, then file accessibility across devices is achieved, but redundant file copies proliferate and the environment becomes error-prone

Engineering Contradiction:
Improvefile accessibility across devicesVSAvoidenvironment error rate
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent merges multiple file copies across different devices into a unified virtual file system. Instead of maintaining separate physical copies on each device, the system creates a single virtualized file namespace that spans multiple devices, allowing users to access files from any device without creating redundant physical copies.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The patent introduces a file synchronization service as an intermediary between devices and files. This service automatically manages file transfers, version control, and consistency across devices, eliminating the need for manual file handling and reducing errors associated with manual copy-paste operations.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If distributed file systems are used to enable file sharing, then file accessibility improves, but the host machine must remain continuously connected to the internet

Engineering Contradiction:
Improvefile sharing capabilityVSAvoidhost availability requirement
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The patent implements preliminary actions by pre-synchronizing files to local device storage before network disconnection occurs. The system proactively caches files and metadata locally, enabling users to access files offline without requiring the host machine to be continuously connected to the internet.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent implements local quality by allowing different devices to have different levels of file availability based on their local cache state. Files recently accessed or marked as important are cached locally on each device, providing fast offline access, while less frequently accessed files remain on the host or in the cloud.

Inventive Principle:
Principle #3Local quality

3Adaptability or versatility

If each device maintains its own local file system, then device independence is maintained, but file management complexity increases and unified access is lost

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

Solution Approach 1:

The patent implements universality by creating a unified virtual file system that works across all devices regardless of their underlying local file systems. The system provides a consistent file access interface and organization model that functions uniformly on desktops, laptops, tablets, and smartphones, eliminating the need for users to learn different filing conventions on each device.

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

Solution Approach 2:

The patent uses virtual copying to create a unified view of files across devices. Instead of physically copying files between devices, the system creates virtual references or pointers to files in a centralized storage location, allowing users to access the same file from multiple devices without duplicating the actual file data.

Inventive Principle:
Principle #26Copying

4Adaptability or versatility

If remote desktop software is used to access files on a host machine, then file accessibility is achieved, but the host machine must be powered on and connected at all times

Engineering Contradiction:
Improveremote file accessVSAvoidhost uptime requirement
Core Design Contradiction:
Adaptability or versatilityVSDuration of action of stationary object

Solution Approach 1:

The patent implements preliminary action by pre-caching files and synchronization metadata on local devices before the host machine goes offline. This allows users to continue accessing and working with files locally even when the host machine is powered off or disconnected from the network.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent segments the file access function into two independent components: a centralized file storage service on the host machine and a local file caching/synchronization client on user devices. This segmentation allows the host to be offline while users retain access to previously cached files, breaking the dependency between host availability and user access.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS12373387B2Architecture for management of digital files across distributed network
Publication Date: 2025.07.29 TOPIA TECH
  • US12373387B2 patent drawing
  • US12373387B2 patent drawing
  • US12373387B2 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.