Block Chain Hashing for File Transmission Failure Identification
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current file transfer systems between servers rely on rudimentary row counts or checksums at the trailer to indicate the number of blocks in a file, but when a transmission issue occurs, the entire file or batch must be re-transmitted without identifying the specific faulty block, leading to inefficiencies.
Innovation Solution
Implementing a cryptographic hashing function, such as SHA256, to generate unique hashes for each block, which are tagged and used to form a block chain, allowing for precise identification of transmission errors and targeted re-transmission of faulty blocks.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Device complexity
If traditional trailer validation with row counts or checksums is used, then the validation process is simple, but the entire file must be re-transmitted when any block fails
Solution Approach 1:
The patent segments the file into individual blocks, each with its own cryptographic hash. This allows the system to identify and re-transmit only the failed block rather than the entire file, directly resolving the contradiction between simple validation and transmission efficiency.
Solution Approach 2:
The patent replaces traditional mechanical trailer validation with cryptographic hashing mechanisms. Each block is hashed individually, and these hashes are stored in a ledger, enabling precise failure identification without complex validation processes.
2Measurement precision
If block-level cryptographic hashing is implemented, then failure location can be identified precisely, but the system complexity increases
Solution Approach 1:
The patent creates a copy of the file's structural information in the form of a ledger that stores cryptographic hashes of each block. This copy allows the system to reference block locations and identify failures without storing the actual file data, reducing system complexity while maintaining precision.
Solution Approach 2:
The patent introduces a ledger as an intermediary between the file transmission system and the validation process. The ledger stores cryptographic hashes and metadata, serving as a reference that enables precise failure location identification without adding complex validation logic to the transmission process.
3Reliability
If the entire file is re-transmitted on failure, then validation is simple, but time and resources are wasted
Solution Approach 1:
The patent implements a feedback mechanism where the ledger stores cryptographic hashes of transmitted blocks. When validation fails, the system compares the received block hash with the expected hash from the ledger, identifies the specific failed block, and requests re-transmission of only that block, thereby reducing time loss while maintaining reliability.
Data Source
AI summary
Embodiments of the invention are directed to a system, method, or computer program product for file transmission validation and failure location identification. The invention provides a cryptographic hashing function to generate a unique hash for each block in a file being transmitted. The hash from the previous block is included along with the contents of the next block to create the hash for the next block. Similarly the hash from the previous blocks is used with the data of that block to generate the hash forming onto a block chain. The files can only be transmitted to a select group of servers forming a private block chain network within the entity server systems after the files are transmitted to the target location. As such, the system can recalculate the hashes and match hash blocks to identify an exact file location of a transmission failure.