File Distribution Server with Automatic Availability Check

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing methods for transferring large volumes of data between locations are inefficient, insecure, and prone to time lags and errors, especially over low-speed connections, as they require manual downloads from servers and lack secure protocols.

Innovation Solution

A file distribution system using a network of Rainbow servers that pushes file details and contents between servers, allowing efficient, secure, and scalable file transfer by determining which files are needed and transmitting only those, with built-in error recovery and hop-by-hop routing, optimizing message size and security.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If files are uploaded to a server for distribution, then the sender can notify the recipient that data is available, but the recipient must manually log on and start each download, leading to large time lags

Engineering Contradiction:
Improvemanual download processVSAvoidtime lag between upload and receipt
Core Design Contradiction:
Ease of operationVSLoss of time

Solution Approach 1:

The system performs preliminary actions by having the recipient's server proactively check for needed files before they are actually needed. The receiving server queries the sending server about file availability and automatically initiates downloads in advance, eliminating the manual logon and download initiation steps that cause time lags.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The file distribution system operates autonomously without requiring manual user intervention. The receiving server automatically determines which files are needed, queries the sending server, and initiates downloads without human involvement, making the system self-service and eliminating the manual operation steps that create delays.

Inventive Principle:
Principle #25Self-service

2Reliability

If the recipient manually downloads files from a server, then files can be transferred, but if the download fails, the recipient must start the download again, wasting time and resources

Engineering Contradiction:
Improvedownload failure recoveryVSAvoidtime to restart failed downloads
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system implements feedback mechanisms where the receiving server monitors download progress and status. If a download fails or is interrupted, the system receives feedback about the failure and automatically restarts the download process, using the feedback information to recover from errors without manual intervention and minimizing time loss.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The system prepares for potential download failures in advance by implementing automatic retry mechanisms and error handling protocols. Before a failure can impact the user, the system has cushioning measures in place to automatically recover from errors, preventing the need for manual restart and reducing the impact of failures on overall transfer time.

Inventive Principle:
Principle #11Beforehand cushioning (Prior cushioning)

3Quantity of substance

If large volumes of data are transferred over low-speed connections, then data can be moved between locations, but the time delay increases significantly, causing further problems

Engineering Contradiction:
Improvevolume of data transferredVSAvoiddownload time delay
Core Design Contradiction:
Quantity of substanceVSLoss of time

Solution Approach 1:

The system performs preliminary file identification and availability checking before the actual data transfer begins. By determining which files are needed and verifying their availability in advance, the system prepares the transfer process so that when data movement begins over low-speed connections, no additional time is spent on negotiation or discovery, maximizing the efficiency of the limited bandwidth.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system segments the file transfer process into distinct phases: file identification, availability verification, and data transfer. This segmentation allows the system to optimize each phase separately, particularly the data transfer phase over low-speed connections, by ensuring that only necessary files are transferred and that the transfer process is efficiently managed without unnecessary overhead.

Inventive Principle:
Principle #1Segmentation

4Productivity

If ftp server is used for file distribution, then files can be transferred, but the password is passed over the network in clear text, creating security concerns

Engineering Contradiction:
Improvefile transfer capabilityVSAvoidsecurity vulnerability
Core Design Contradiction:
ProductivityVSObject-affected harmful factors

Solution Approach 1:

The system introduces an intermediary layer between the file transfer capability and the authentication process. Instead of using direct FTP protocols that expose passwords in clear text, the system uses an intermediate mechanism that handles authentication securely, separating the file transfer function from the vulnerable authentication process and eliminating the security vulnerability while preserving productivity.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentEP1868351B1File distribution system
Publication Date: 2011.11.23 MICROSOFT CORP
  • EP1868351B1 patent drawingFigure 1
  • EP1868351B1 patent drawingFigure 2
  • EP1868351B1 patent drawingFigure 3

AI summary

A file distribution server, system and method of file distribution are described. Files are distributed between servers (201,202) and before files are sent from a first server (201) to a second server (202), details about the files (205) are sent to the second server. The second server determines whether the files are already held (207) at the second server and then requests only those files which are not already held (208). In response to receiving the request, the requested files (210) are sent by the first server (201) to the second server (202).