One-Way Data Link Database Update Verification
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
One-way data links, used for high security networks, do not provide feedback for detecting transmission errors in database updates, leading to incomplete updates in remote databases due to lack of acknowledgment from the receiving server.
Innovation Solution
A system that includes a monitor application to generate and forward database update information with sequence information, a send server to compress and forward updates, and a receive server to verify sequence order and update the remote database, discarding out-of-order updates to ensure accurate and complete data transfer across a one-way data link.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a one-way data link is used to ensure high security and unidirectional data transfer, then network security and prevention of unauthorized data disclosure are improved, but the ability to detect and correct transmission errors in database updates deteriorates due to lack of feedback from the receiving server
Solution Approach 1:
The patent applies preliminary action by embedding sequence numbers in database update messages before transmission. This allows the receiving server to verify the completeness and order of updates without needing to send feedback requests. The sequence numbers are prepared in advance as part of the update message structure, enabling error detection and correction purely through one-way communication.
Solution Approach 2:
The patent introduces an intermediary mechanism in the form of sequence numbers that mediate between the transmitting and receiving servers. These sequence numbers act as a passive mediator that carries verification information through the one-way link, allowing the receiving server to independently verify transmission integrity without establishing a feedback channel.
2Manufacturing precision
If sequence verification is implemented at the receive server to ensure complete database updates, then data integrity is improved, but system complexity increases due to additional verification and error handling mechanisms
Solution Approach 1:
The patent applies local quality by implementing verification only where needed - at the receiving server for database update messages. The complexity is localized to the receive server's update processing logic rather than being distributed throughout the entire system. Each update message is independently verified using its sequence number, allowing targeted verification without system-wide complexity.
Solution Approach 2:
The patent uses parameter changes by incorporating sequence numbers as additional parameters in the database update messages. This simple parameter addition enables comprehensive verification and error detection without requiring complex protocols or mechanisms. The sequence number parameter transforms the verification process from complex to straightforward comparison operations.
3Productivity
If all database update information is compressed into a single file before transmission, then transmission efficiency is improved, but the ability to identify and correct individual transmission errors deteriorates
Solution Approach 1:
The patent applies segmentation by dividing the compressed file transmission into multiple individual update messages, each with its own sequence number. Instead of transmitting one large compressed file that cannot be selectively verified, the system segments the data into discrete messages that can be independently tracked and verified. This allows the receiving server to identify exactly which messages were lost or corrupted while maintaining compression efficiency.
Data Source
AI summary
A system for assuredly copying information from a reference database to a remote database. A send server is coupled to a first network. A receive server is coupled to a second network. A one-way data link provides unidirectional transfer of information from the send server to the receive server. A monitor application iteratively forwards update files including sequence information to the send server. An update application receives each update file and updates the remote database based therein. The update files are also sequentially stored in the send server in groups and each group is sent to the receive server and stored in memory. If an update file is not received in proper sequential order, the receive server stops sending update files in the current group and instead reads the missing update file and subsequent update files in the current group from memory and forwards such files to the update application.