Negotiated Accelerated TFTP for Aircraft Network Transfer
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The ARINC 615A specification's use of Trivial File Transfer Protocol (TFTP) on commercial aviation systems leads to increased software load times due to bandwidth constraints on slow aircraft networks, causing aircraft downtime, as the Data/Acknowledgement handshake significantly slows down file transfers.
Innovation Solution
Implementing a negotiated accelerated TFTP method that allows for the transmission of multiple data blocks without waiting for acknowledgement, optimizing block acceleration based on hardware constraints and network conditions to maintain continuous data transmission and reduce overall file transfer time.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If TFTP Data/Acknowledgement handshake is used on aircraft network, then transfer reliability is maintained, but file transfer speed deteriorates due to bandwidth constraints
Solution Approach 1:
The patent applies preliminary action by pre-negotiating and caching the IP address of the TFTP server in the client device before actual file transfer begins. This pre-action eliminates the need for repeated DNS lookups and connection establishment during transfers, significantly reducing latency and improving transfer speed while maintaining protocol reliability. The negotiation of transfer parameters occurs in advance, allowing the system to prepare optimal transfer settings before data movement commences.
Solution Approach 2:
The patent implements dynamics by making the TFTP client adaptive to network conditions through dynamic adjustment of transfer parameters. The client negotiates with the server to determine optimal block sizes and transfer rates based on current network status, allowing the system to dynamically optimize performance for varying aircraft network conditions while preserving the reliability guarantees of the TFTP protocol.
2Adaptability or versatility
If traditional TFTP protocol is used, then compatibility with ARINC 615A specification is maintained, but software load time increases causing aircraft downtime
Solution Approach 1:
The patent applies segmentation by dividing the file transfer process into distinct phases: a negotiation phase where transfer parameters are agreed upon, and an execution phase where pre-negotiated parameters are used for rapid data transfer. This segmentation allows the system to maintain protocol compatibility during negotiation while achieving high-speed transfer during execution, effectively reducing overall software load time without sacrificing ARINC 615A compliance.
Solution Approach 2:
The patent utilizes parameter changes by dynamically adjusting TFTP transfer parameters such as block size and transfer rate based on network conditions and file characteristics. By negotiating and optimizing these parameters before transfer begins, the system achieves faster software loading times while remaining within the bounds of the TFTP protocol specification, thus maintaining compatibility with ARINC 615A.
3Reliability
If bandwidth is dedicated to flying operations, then flight safety is prioritized, but file transfer performance deteriorates due to insufficient network capacity
Solution Approach 1:
The patent implements self-service by enabling the TFTP client to autonomously negotiate transfer parameters and cache necessary information without requiring additional network resources or manual intervention. The client independently determines optimal transfer settings and manages its own connection state, reducing the burden on network infrastructure and allowing efficient transfers within the constrained bandwidth allocated for safety-critical operations.
Solution Approach 2:
The patent applies continuity of useful action by maintaining persistent connection state information in cache between transfers. Once the TFTP server IP address and transfer parameters are negotiated, this information is retained and reused for subsequent file transfers, eliminating the need to repeatedly establish connections and negotiate parameters. This continuous utilization of cached information maximizes file transfer performance within the limited bandwidth available for non-critical operations.
Data Source
AI summary
Systems and Methods for Negotiated Accelerated Block Option for Trivial File Transfer Protocol are provided. In one embodiment, a method for implementing a negotiated accelerated Trivial File Transfer Protocol (TFTP) file transfers, the method comprising: transmitting a TFTP request packet for accelerated transfer from a requesting device to a serving device; receiving a response from the serving device; determining whether to initiate an accelerated transfer by evaluating the response packet from the serving device; and when evaluating the response packet indicates that the serving device accepts acceleration, initiating an accelerated TFTP file transfer using a negotiated block acceleration value, wherein the negotiated block acceleration value is negotiated by the client device and the Accelerated TFTP Server Engine based on one or both of hardware constraint factors and transmission statistics.