Multi-tenant Framework Bi-directional File Sync

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional systems face challenges in accurately updating and managing large volumes of documents and files across networked folders, leading to computational strain and difficulties in maintaining document accuracy, availability, and security, especially in cloud environments where manual processes are complex and error-prone.

Innovation Solution

A novel multi-tenant framework enables bi-directional uploading, synchronization, and access of files between local and network-hosted applications and devices, using cloud storage to replicate data across endpoints, manage permissions, and provide versioning, ensuring timely and secure access to updated files across various locations and platforms.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Quantity of substance

If conventional shared or networked folders are used to host and store documents, then files can be centrally stored with associated metadata, but the server and administrative processor experience computational strain and difficulty in accurately updating and managing large volumes of documents

Engineering Contradiction:
Improvenumber of documents processedVSAvoidcomputational complexity for metadata updating
Core Design Contradiction:
Quantity of substanceVSDevice complexity

Solution Approach 1:

The system segments the document management workload by introducing distributed peer nodes that each independently manage subsets of documents. Instead of a centralized server processing all metadata updates, the computational task is divided across multiple peers, where each peer handles updates for its local document subset, thereby reducing the computational burden on any single server.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system implements self-service by enabling peer nodes to autonomously perform metadata updates and document synchronization without requiring centralized server intervention for each operation. Peers independently validate and propagate document changes across the network, eliminating the need for the server to process every metadata update manually.

Inventive Principle:
Principle #25Self-service

2Adaptability or versatility

If manual downloading and processing of documents is used in cloud environments, then files can be accessed from remote locations, but the process becomes complicated, time-consuming, and error-prone

Engineering Contradiction:
Improveaccess from remote locationsVSAvoidtime for manual download and processing
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The system performs preliminary action by pre-synchronizing documents and metadata to peer nodes before they are needed. Documents are proactively replicated across the peer network in advance, so when users need to access files from remote locations, the data is already available locally on peer nodes, eliminating the need for time-consuming manual downloads.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements feedback mechanisms where peer nodes continuously monitor and report document access patterns and synchronization status. This feedback enables the network to dynamically adjust document replication and synchronization strategies, ensuring that frequently accessed documents are readily available while minimizing unnecessary data transfer and processing time.

Inventive Principle:
Principle #23Feedback

3Reliability

If centralized folder monitoring is used to track uploads, then document availability can be maintained, but network and device resources are drained in maintaining accuracy, availability, and security

Engineering Contradiction:
Improvedocument availabilityVSAvoidnetwork and device resources
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

The system applies local quality by enabling each peer node to independently maintain document availability and security for its local subset without requiring continuous centralized monitoring. Each peer validates and protects its local documents autonomously, reducing the need for constant network communication and server resources while maintaining overall system reliability.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The system implements periodic action by scheduling intermittent synchronization and validation operations instead of continuous monitoring. Peer nodes perform document availability checks and security validations at predetermined intervals, significantly reducing network traffic and device resource consumption compared to real-time centralized monitoring while maintaining document availability.

Inventive Principle:
Principle #19Periodic action

Data Source

PatentUS11892985B2Computerized systems and methods for bi-directional file sharing and synchronization on and over a network
Publication Date: 2024.02.06 AVEVA SOFTWARE LLC
  • US11892985B2 patent drawing
  • US11892985B2 patent drawing
  • US11892985B2 patent drawing

AI summary

Disclosed are systems and methods for improving interactions with and between computers in content providing, searching and/or hosting systems supported by or configured with devices, servers and/or platforms. The disclosed systems and methods provide a novel framework that automatically and bi-directionally enables applications and devices to upload and access files from remote locations on a network, while synchronizing the stored files for access from the various applications, devices and locations. The disclosed framework enables files sharing and file synchronization between location to location, cloud to cloud, network to network, device to device, location to cloud and vice-versa, and some combination thereof. The disclosed synchronization framework is a cloud-based multi-tenant infrastructure that securely, efficiently and accurately hosts shared files for administrative, read/write and/or read only access from devices, locations and applications with access to the associated drive(s) in/on the cloud.