Subscriber Node Sequence Validation for Message Integrity
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing messaging systems in computing and networking devices face challenges in ensuring message sequence integrity and security, particularly in preventing unauthorized third-party interference and message loss detection.
Innovation Solution
The method involves generating and managing sequence numbers using a one-way function with a secret value known only to authorized nodes, allowing subscribers to validate message sequences and detect message drops by comparing expected and received sequence numbers, and using replay messages to synchronize and secure message delivery.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If sequence numbers are generated using a one-way function with secret value, then message security and integrity are improved, but device complexity increases due to additional validation operations
Solution Approach 1:
The subscriber node pre-generates expected sequence numbers using the one-way function and secret value before message validation. This preliminary computation enables efficient O(1) comparison validation when messages arrive, resolving the contradiction by shifting computational burden to setup phase rather than validation phase
Solution Approach 2:
The patent introduces replay messages as an intermediary mechanism that carries sequence number information between publisher and subscriber nodes. This intermediary structure enables secure message delivery validation without requiring complex real-time cryptographic verification, thus improving security while managing device complexity
2Reliability
If replay messages are used to synchronize message delivery, then message loss detection is improved, but loss of time occurs due to additional message exchanges
Solution Approach 1:
The subscriber node sends replay messages containing expected sequence numbers to the publisher node as feedback. The publisher uses this feedback to determine which messages need to be retransmitted. This feedback mechanism improves message loss detection by enabling the system to identify and recover from lost messages, while the targeted nature of replay messages minimizes unnecessary communication overhead
Solution Approach 2:
Instead of requiring complete message sequence verification for every message, the system uses partial verification through replay messages that only contain necessary sequence number information. This partial action approach provides sufficient loss detection capability without the excessive time cost of full sequence verification, resolving the contradiction between reliability and time loss
Data Source
Figure 1
Figure 2A~2B
Figure 2C~2D
AI summary
A method for message management is disclosed. The method includes: deriving, by a first subscriber node (SN), a secret value associated with a publisher node (PN); generating, by the first SN, a first expected sequence number using a one-way function and the secret value; receiving, by the first SN, a first publisher message generated by the PN and including a first sequence number; validating, by the first SN, the first publisher message by comparing the first sequence number with the first expected sequence number; processing, by the first SN, a payload of the first publisher message in response to the first sequence number and the first expected sequence number matching; and generating, by the first SN node, a second expected sequence number using the one-way function, the first sequence number, and the secret value.