Remote Node Event Delay Policy for RPD Storm Mitigation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Event storms occur in network architectures due to simultaneous reporting of events from multiple remote nodes to a principal controller, leading to network traffic delays, data loss, and performance degradation.
Innovation Solution
Implementing an event delay policy at remote nodes to stagger the reporting of events to the principal controller, using a delay factor that varies among nodes to prevent simultaneous reporting.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If remote nodes report events simultaneously to the principal controller, then complete event information is captured, but the principal controller experiences event storms causing network traffic delays and performance degradation
Solution Approach 1:
The patent implements a delay mechanism that introduces periodic time intervals between event reporting actions. Remote nodes apply exponential backoff delays with randomization, transforming simultaneous event reports into staggered periodic reports. This resolves the contradiction by maintaining event reporting completeness while preventing controller overload through time-based distribution of reporting actions.
Solution Approach 2:
The patent applies preliminary action by having remote nodes calculate and apply delay factors before actually reporting events to the principal controller. The exponential backoff algorithm with randomization is computed in advance, allowing nodes to proactively prevent event storms before they occur, thus maintaining both reporting completeness and controller productivity.
2Productivity
If remote nodes delay event reporting to prevent event storms, then principal controller performance is maintained, but event reporting time is increased
Solution Approach 1:
The patent applies partial action by implementing selective delay mechanisms. Not all events are delayed equally - the exponential backoff with randomization applies partial delays based on event type, node state, and network conditions. This resolves the contradiction by maintaining controller productivity while minimizing unnecessary time loss through selective rather than universal event delay.
Solution Approach 2:
The patent changes the time parameter dynamically through exponential backoff with randomization. Instead of fixed delays, the delay factor is adjusted based on event characteristics and network state, transforming the time parameter from static to dynamic. This resolves the contradiction by optimizing the balance between controller load management and event reporting timeliness through parameter adaptation.
Data Source
AI summary
An access network can include a plurality of remote nodes connected to a principal controller. The principal controller can experience an event storm when one or more of the plurality of remote nodes report an access network event at the same or substantially the same time. One or more remote nodes can mitigate such an event storm at the principal core by delaying by an event reporting delay the reporting of the access network event to the principal core. The event reporting delay can be based on an event delay policy associated with a given remote node. The even reporting delay can be different for each remote node or a group of remote nodes so that the principal core does not receive reports from the plurality of remote nodes so as to cause an event storm which can negatively impact the access network, one or more network devices, or both.