Dynamic Network File Replication via Peer Interception

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing distributed computing systems face resource challenges and network saturation when accessing and managing files across multiple networked devices, as they often require all necessary files to be hosted on a single server, leading to inefficiencies in file availability and replication.

Innovation Solution

Implementing dynamic replication of networked files through a file system that intercepts file requests, determines local availability, and replicates files from peer devices using metadata, reducing unnecessary I/O operations and improving network efficiency by distributing requests across multiple devices.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If all necessary files are hosted on a single file server, then file availability is ensured, but network saturation occurs when multiple computing devices connect to the single file server

Engineering Contradiction:
Improvefile availabilityVSAvoidnetwork efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent segments the centralized file server into multiple peer devices in a distributed network. Each peer device stores and serves files locally, dividing the single-point file hosting function across multiple nodes. This segmentation eliminates network saturation by distributing request handling while maintaining file availability through the peer-to-peer architecture where files can be accessed from multiple locations simultaneously.

Inventive Principle:
Principle #1Segmentation

2Productivity

If files are distributed across multiple network locations, then network efficiency improves, but the initial configuration time and complexity increase

Engineering Contradiction:
Improvenetwork efficiencyVSAvoidconfiguration time
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The patent implements self-service through automatic file replication and metadata synchronization. When a file is added or updated on any peer device, the system automatically replicates it to other peers and updates metadata across the network without manual intervention. This eliminates the need for manual file distribution and configuration, allowing the system to self-organize and reducing initial setup time while maintaining distributed file access efficiency.

Inventive Principle:
Principle #25Self-service

3Ease of operation

If manual file specification and maintenance is used, then file access control is precise, but the process becomes excessively broad and manual maintenance is required

Engineering Contradiction:
Improvefile access controlVSAvoidmanual maintenance complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent implements feedback through automatic metadata synchronization and file replication tracking. The system continuously monitors file changes across peer devices and automatically updates replication status and metadata. This feedback mechanism replaces manual file specification and maintenance with automated tracking, reducing operational complexity while maintaining precise file access control through the metadata system that tracks file locations and versions across the distributed network.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS10289691B2Dynamic replication of networked files
Publication Date: 2019.05.14 MICROSOFT TECHNOLOGY LICENSING LLC
  • US10289691B2 patent drawing
  • US10289691B2 patent drawing
  • US10289691B2 patent drawing

AI summary

In embodiments of dynamic replication of networked files, a process that utilizes file system objects is executed on a computing device. A file system request that is initiated by the process for a requested file system object can be intercepted, and a determination is made as to whether the requested file system object exists based on file system metadata. The file system request from the process is returned if the requested file system object is stored on the computing device. Alternatively, replication of the requested file system object is initiated from a networked peer device that has the requested file system object to replicate the file system object to the computing device. Alternatively, an indication that the requested file system object does not exist can be returned to the process.