Epoch-Based Messaging Reliability Without Sender IDs
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing messaging protocols rely on sender identifiers for reliability, which increases overhead and cannot support implementations without sender identifiers to minimize overhead and maximize bandwidth efficiency.
Innovation Solution
An epoch-based mechanism that uses transmit and receive checksums to validate message integrity and reliability within a collective group of nodes, eliminating the need for sender identifiers in message headers by processing checksums after a defined time period to ensure correct message reception and retransmitting if errors are detected.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If sender identifiers are included in message headers for reliability mechanisms, then message integrity and reliability are improved, but message overhead increases and bandwidth efficiency decreases
Solution Approach 1:
The patent segments the reliability verification process into two distinct phases: a transmit phase where messages are sent without sender identifiers, and a check phase where checksums are verified. This segmentation allows the system to achieve reliability without continuously including sender identifiers in every message, thereby reducing overhead while maintaining integrity.
Solution Approach 2:
The patent performs preliminary checksum calculation during the transmit phase, before the check phase begins. By pre-calculating and storing checksums with epoch identifiers (而非 sender identifiers), the system prepares verification data in advance, enabling reliable message validation without the overhead of including sender identifiers in message headers.
2Reliability
If error correction codes are used to reduce retransmissions, then message reliability is improved, but latency increases and bandwidth is consumed
Solution Approach 1:
The patent uses lightweight checksums (such as CRC or simple hash functions) instead of complex error correction codes. These checksums are computationally inexpensive to calculate and verify, providing sufficient reliability for detecting corrupted messages without the heavy computational overhead and latency associated with full error correction mechanisms.
Solution Approach 2:
The patent implements a feedback mechanism where receivers verify checksums and send back verification results. This allows the system to detect and request retransmission of corrupted messages only when necessary, rather than using continuous error correction codes on all messages, thereby reducing overall latency and bandwidth consumption.
3Reliability
If traditional reliability mechanisms with sender identifiers are used, then message validation is achieved, but bandwidth efficiency decreases due to increased overhead
Solution Approach 1:
The patent extracts the sender identifier from the message header and replaces it with an epoch identifier in the checksum data. This extraction removes the overhead of including sender identifiers in every message while maintaining the ability to validate messages through checksum verification in the check phase, thereby improving bandwidth efficiency without sacrificing validation capability.
Solution Approach 2:
The epoch identifier serves multiple functions: it groups messages into transmission batches, enables checksum verification, and provides a basis for retransmission control. This multi-functional approach replaces the traditional sender identifier, achieving message validation with reduced overhead and improved bandwidth efficiency.
Data Source
AI summary
Messaging protocols used by components in a messaging system to exchange messages conventionally use a reliability mechanism to ensure that each message sent by a sender is received, without compromise, by the intended receiver. Typically, this reliability mechanism involves use of a returned acknowledgement message to the message sender, with automatic retransmission of the message by the sender when the acknowledgement message is not received (e.g. within a defined timeframe). However, existing acknowledgement-based reliability mechanisms require that a sender identifier be included in the message header, which increases the overhead of the message. The present disclosure provides an epoch-based reliability mechanism that allows the sender identifier to be omitted from the message header to minimize overhead and maximize the efficient use of the available bandwidth.