Transceiver System End-to-End Reliability Protocol
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Communication between processing nodes in multi-processor systems faces gaps in communication error coverage, particularly in signal switching fabrics, leading to unrecoverable errors and potential system failures due to packet reordering and duplication.
Innovation Solution
The implementation of a communication protocol that provides end-to-end reliability through 'late on-the-fly connection setup' and 'singleton delineation', deferring connection setup until packets arrive at the destination, using transaction IDs to associate packets, and serializing load-store sequences to avoid replay buffers, ensuring ordered delivery and error recovery.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If packet retransmission is performed due to transmission errors, then communication reliability is improved, but packet order changes and duplicate packets are created
Solution Approach 1:
The patent applies preliminary action by establishing connection state and transaction ID tracking before packet transmission begins. The source and destination nodes pre-configure the connection setup, creating a framework that will automatically maintain packet ordering and prevent duplicates during retransmission operations without requiring reactive corrections later.
Solution Approach 2:
The patent implements feedback mechanisms through acknowledgment packets and connection state tracking. When packets are retransmitted, the system uses feedback from received acknowledgments and connection state information to verify packet delivery, detect duplicates, and restore correct ordering, thereby maintaining reliability while correcting the ordering issues caused by retransmission.
2Reliability
If connection setup is performed before packet transmission, then communication reliability is improved, but connection setup time increases
Solution Approach 1:
The patent applies preliminary action by establishing connection state and transaction ID tracking before packet transmission begins. The source and destination nodes pre-configure the connection setup, creating a framework that will automatically maintain packet ordering and prevent duplicates during retransmission operations without requiring reactive corrections later.
Solution Approach 2:
The patent implements dynamic connection setup that adapts to the actual transmission needs. Rather than always performing full connection setup beforehand, the system dynamically adjusts the level of setup performed based on whether packets are already in flight or need to be sent, allowing connection establishment to occur progressively as needed rather than all at once before transmission.
3Stability of the object's composition
If replay buffers are used to maintain ordered delivery, then packet ordering is preserved, but device complexity increases
Solution Approach 1:
The patent extracts the ordering maintenance function from heavy replay buffer mechanisms and implements it through lighter-weight connection state tracking and transaction ID comparison. By taking out the complex buffer management and replacing it with simpler state tracking at the protocol level, the system preserves packet ordering while significantly reducing device complexity and memory requirements.
Solution Approach 2:
The patent introduces transaction IDs as an intermediary mechanism that mediates between packet transmission and ordering requirements. Instead of using complex replay buffers to track and reorder packets, the transaction ID serves as a simple intermediary marker that allows both source and destination to verify ordering and detect duplicates through straightforward comparison operations.
Data Source
AI summary
Packet flows between a transmitter and a receiver in an unreliable and unordered switched packet network may be established as a result of receiving a second packet comprising a second memory operation on a memory address. The transmission of memory load command packets followed by memory store command packets in the packet flow may be serialized, and a synchronization operation may be executed between the transmitter and the receiver when a packet count at the receiver satisfies a number of data packets in the packet flow.