Multicast Node Message Synchronization via Counter Consensus
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In multicast network protocols, nodes that reboot or experience temporary unavailability face challenges in synchronizing anti-replay and duplicate message sequence counters, leading to potential replay attacks and communication disruptions, especially when the key distribution center is unavailable or during simultaneous multi-node boot-ups.
Innovation Solution
A counter consensus protocol is introduced, allowing a booting-up node to synchronize its session keys and node message sequence numbers with the rest of the network by sending an initial multicast message and randomly generating a time value, enabling nodes to share their NMSN tables and update each other's counters without relying on an external key distribution center, thus mitigating replay attacks and communication disruptions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If standard key distribution mechanisms are used for node boot-up, then session key distribution is achieved, but communication disruption occurs and replay attacks become possible due to unsynchronized sequence counters
Solution Approach 1:
The patent applies preliminary action by having booting nodes proactively send a boot notification message to the group before their sequence counters are synchronized. This allows other nodes to update their records of the booting node's sequence number in advance, preventing replay attacks where attackers might otherwise send stale messages with older sequence numbers that would otherwise be accepted.
2Reliability
If frequent re-keying is implemented to prevent replay attacks, then security is improved, but network churn increases and communication disruption occurs
Solution Approach 1:
The patent implements feedback by having nodes monitor and track sequence numbers of incoming messages from each group member. When a node detects that a message's sequence number is not higher than the recorded sequence number for that sender, it discards the message as a potential replay. This continuous feedback mechanism allows nodes to maintain security without requiring frequent re-keying, as the sequence number tracking provides ongoing verification of message freshness.
3Ease of operation
If sequence counters are reset on node boot-up, then synchronization is simplified, but the window for replay attacks increases
Solution Approach 1:
The patent applies preliminary action by having booting nodes send a boot notification message to the group before their sequence counters are synchronized. This allows other nodes to update their records of the booting node's sequence number in advance, preventing replay attacks where attackers might otherwise send stale messages with older sequence numbers that would otherwise be accepted.
4Device complexity
If external key distribution centers are used, then key management is centralized, but single points of failure are created and processing overhead increases at non-booting nodes
Solution Approach 1:
The patent extracts the key distribution function from a centralized external key distribution center and implements it directly within the group communication protocol itself. Nodes obtain session keys through group key establishment procedures embedded in the multicast protocol, eliminating the need for separate key management infrastructure and removing single points of failure associated with external key distribution centers.
Data Source
AI summary
Systems for communicating over a network and between two or more network connected devices. In particular, the disclosure reveals systems which include a first node having a first node message sequence counter, a second node having a second node message sequence counter, and wherein the second node is configured to synchronize the first node message sequence counter based on the second node message sequence counter.