TFTP Accelerated File Retry Option
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Standard Trivial File Transfer Protocol (TFTP) requires restarting file transfers from the beginning if they fail, which is inefficient and time-consuming, especially in avionics systems where large files are involved and reliability is critical.
Innovation Solution
The implementation of an accelerated file retry option in TFTP allows file transfers to resume from the last successfully transferred block, using the TFTP Option Extension mechanism, enabling backward-compatible negotiation of file transfer options to retry incomplete transfers without requiring additional software.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If standard TFTP restarts file transfers from the beginning when transfers fail, then the protocol maintains simplicity and compatibility, but transfer time increases significantly and reliability decreases for large files
Solution Approach 1:
The patent applies preliminary action by negotiating transfer options (such as block size and timeout values) before the actual file transfer begins. This allows the system to optimize transfer parameters in advance, ensuring that if a transfer fails, the retry can use pre-negotiated optimal settings rather than restarting with default parameters, thereby reducing overall transfer time and improving reliability.
Solution Approach 2:
The patent implements dynamics by allowing TFTP to transition from static, fixed-parameter transfers to dynamic, adaptable transfers. Through option negotiation, the protocol can adjust block sizes, timeout intervals, and other parameters based on network conditions and file characteristics, enabling more efficient retries and reducing time loss when transfers fail.
2Adaptability or versatility
If TFTP uses fixed transfer parameters, then the protocol remains simple and widely compatible, but it cannot adapt to different network conditions and file sizes
Solution Approach 1:
The patent applies universality by designing an option negotiation mechanism that allows TFTP to maintain its core simple functionality while adding adaptive capabilities. The same basic TFTP protocol structure handles both traditional fixed-parameter transfers and new flexible transfers with negotiated options, making the protocol universally applicable across different network conditions and file sizes without requiring multiple separate protocols.
Solution Approach 2:
The patent implements parameter changes by introducing option negotiation that allows dynamic adjustment of transfer parameters such as block size, timeout intervals, and buffer sizes. These parameters can be modified based on network conditions and file characteristics, enabling the protocol to adapt to different scenarios while maintaining backward compatibility with systems that use default parameters.
3Productivity
If TFTP transfers large files in small fixed blocks, then the protocol remains simple to implement, but the number of packets increases and transfer efficiency decreases
Solution Approach 1:
The patent applies parameter changes by allowing the block size parameter to be negotiated between client and server before transfer begins. Instead of using fixed small blocks, the system can agree on larger block sizes appropriate for the specific file and network conditions, thereby reducing the total number of packets required and improving transfer efficiency without significantly increasing implementation complexity.
Data Source
AI summary
A method of transferring data using a Trivial File Transport Protocol (TFTP) includes sending first request packet from client to server, first request packet requesting that first file be transferred; transferring first file according to first request packet if first acknowledgement packet is received at client from server indicating that server can accommodate request of first request packet; sending second request packet from client to the server if transfer of first file does not complete successfully, the second request packet including TFTP option indicating that transfer of first file be retried beginning at first block after final block that was successfully transferred in response to first request packet; and retrying transfer of first file according to second request packet if second acknowledgement packet is received at client from server indicating that server can accommodate request of second request packet.