Chunked File Transfer Resuming Interruptions
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In online backup systems, large files transferred from clients to servers often require retransmission if the communication connection is interrupted, leading to inefficiencies and high computing resource usage, as many servers do not support byte-range features for resuming failed data transfers.
Innovation Solution
A method where files are transferred in distinct, uniquely named chunks, allowing for seamless continuation of transfers across multiple communication sessions if interruptions occur, using a common file name with varying suffixes or prefixes to identify each chunk, enabling the client to resume transfers without retransmitting the entire file.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the entire file is retransmitted after communication interruption, then data integrity is ensured, but transmission time and computing resources are wasted
Solution Approach 1:
The patent divides the large file into multiple smaller chunks, each with a unique name. When communication is interrupted, only the missing chunks need to be retransmitted rather than the entire file. This segmentation allows for efficient resumption of failed transfers by identifying and retransmitting only the specific chunks that were not successfully received.
2Reliability
If the entire file is retransmitted after communication interruption, then data completeness is ensured, but computing resources are consumed
Solution Approach 1:
By segmenting the file into named chunks, the system can identify which specific chunks are missing after an interruption. This allows the client to retransmit only the missing chunks rather than reprocessing and retransmitting the entire file, significantly reducing computing resource consumption while ensuring data completeness.
3Ease of operation
If simple hosted web services are used as backup servers, then ease of operation is improved, but efficiency of large file transfer is reduced
Solution Approach 1:
The patent enables simple hosted web services to efficiently handle large file transfers by dividing files into manageable chunks. Each chunk can be independently transferred using standard HTTP protocols, allowing basic web servers to support resumption of failed transfers without requiring complex server-side implementations or byte-range feature support.
Data Source
AI summary
A client designates and transfers a file to a server in distinct chunks. The number of data chunks equals the number of communication sessions that are required to complete the transfer of the designated file to the server, that number being dependent on the number of times the communication session between the client and the server is interrupted. If the designated file includes several concatenated client files, each chunk of the designated file may include one or more such client files. Each chunk of the designated file may include some part of a client file and one or more whole client files. The byte-wise size or length of a chunk depends on the duration of the related communication session: the longer a communication session, the larger the related chunk. By transferring the designated file to the server as distinctly recognizable chunks, the need to retransmit large files to the server is avoided.