Resource Notification Message Aggregation for RSVP Error Storm Reduction
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing RSVP protocol generates numerous error messages when a non-ingress node detects resource issues, leading to an RSVP error message storm that consumes significant computing resources and negatively affects network performance.
Innovation Solution
Implement a method where a non-ingress node identifies resource issue events and generates individual resource notification messages that include a notification-requester stack, allowing these messages to be sent directly to the ingress node, thereby reducing the number of messages sent and conserving computing resources.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the existing RSVP protocol sends error messages for each LSP when a resource issue is detected, then complete resource notification is achieved, but the number of messages increases significantly causing network overload
Solution Approach 1:
The patent merges multiple individual error messages into a single aggregated resource notification message. When a non-ingress node detects a resource issue, it consolidates notifications for multiple LSPs into one message containing a stack of notification-requester identifiers, thereby reducing message volume while maintaining complete resource notification coverage
Solution Approach 2:
The resource notification message is designed with universal applicability to handle multiple LSPs simultaneously. The message structure includes a stack of notification-requester stacks that can accommodate identifiers from multiple ingress nodes, enabling a single message to serve multiple notification purposes that previously required separate messages
2Loss of information
If numerous error messages are generated and processed for each LSP, then accurate resource issue notification is provided, but computing resources are significantly consumed
Solution Approach 1:
The patent combines multiple individual error message processing operations into a single aggregated notification processing event. The non-ingress node consolidates resource issue information for multiple LSPs into one message, and the ingress node processes a single aggregated message instead of multiple individual messages, significantly reducing computing resource consumption while preserving complete resource issue information
Solution Approach 2:
The patent uses a structured data representation (notification-requester stack) that can be copied and reused across multiple LSPs. Instead of creating and processing unique error messages for each LSP, the system creates a template structure that is instantiated multiple times within a single aggregated message, reducing the computational overhead of message creation and processing
Data Source
AI summary
In some implementations, a non-ingress node of one or more label-switched paths (LSPs) may identify a resource issue event. The non-ingress node may identify, based on identifying the resource issue event, one or more notification-requester stacks included in a data structure. The non-ingress node may generate one or more resource notification messages that each include a respective notification-requester stack of the one or more notification-requester stacks. The non-ingress node may send the one or more resource notification messages based on the one or more notification-requester stacks.