Network Interface Device Transaction Assurance Engine
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current reliable message exchange protocols in high-speed transactions incur significant latency due to the need for acknowledgement and verification, compromising both reliability and speed in data transmission across computer networks.
Innovation Solution
The implementation of a network interface device (NID) with a transaction transmission assurance engine (TTAM) that ensures reliable message delivery without waiting for acknowledgements, using duplicate pathways and error-recovery mechanisms to maintain transaction integrity and reduce latency.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If conventional reliable message exchange protocols are used, then message delivery reliability is ensured, but transmission latency increases significantly
Solution Approach 1:
The patent extracts the reliability assurance function from the host machine and relocates it to the network interface device (NID). The NID independently executes reliable message delivery protocols, including sending acknowledgements and handling retransmissions, without requiring host machine intervention. This extraction eliminates the latency associated with host machine processing cycles while maintaining message delivery reliability.
Solution Approach 2:
The NID acts as an intermediary between the host machine and the network. It assumes responsibility for message delivery by buffering messages locally and independently managing the reliable delivery protocol execution. This intermediary role allows the host machine to send messages without waiting for protocol completion, significantly reducing transmission latency while ensuring reliability through the NID's autonomous protocol execution.
2Reliability
If the host machine processes each message delivery confirmation, then transaction reliability is maintained, but processing speed decreases
Solution Approach 1:
The NID provides self-service by independently executing the reliable message delivery protocol without requiring host machine processing for each message confirmation. It autonomously sends acknowledgements, handles retransmissions, and manages error recovery. This self-service capability maintains transaction reliability while eliminating the processing bottleneck at the host machine, thereby increasing overall transaction processing speed.
Solution Approach 2:
The patent extracts the protocol execution burden from the host machine and transfers it to the NID. The host machine only needs to initiate message sending, while the NID independently completes the entire reliable delivery process including acknowledgements and retransmissions. This extraction of processing responsibilities maintains reliability while dramatically improving transaction processing speed by removing the host machine as a bottleneck.
3Reliability
If duplicate pathway mechanisms are implemented, then error recovery capability is improved, but device complexity increases
Solution Approach 1:
The NID implements preliminary action by pre-buffering messages in local memory before transmission and pre-establishing duplicate pathway mechanisms. When errors occur, the NID can immediately retrieve buffered messages and retransmit them through alternative pathways without requiring complex real-time decision-making or host machine intervention. This preliminary preparation simplifies the overall device complexity while maintaining robust error recovery capability.
Data Source
AI summary
A network interface device (NID) interfaced with a host machine communicates with a local link of the host machine to obtain transaction-specific data relied upon by the host machine to be delivered to a destination by the NID according to a reliable message delivery protocol. The NID conducts communications over a network in response to obtaining of the transaction-specific data, with the network communications including execution of the reliable message delivery protocol independent of any operability of the host machine.


