Aggregated Resource Notification Messages for RSVP LSPs
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The resource reservation protocol (RSVP) generates numerous error messages when a non-ingress node detects resource issues across multiple label-switched paths (LSPs), leading to resource storms that consume computing resources and negatively impact network performance by increasing latency, reducing throughput, and decreasing bandwidth.
Innovation Solution
A method where a non-ingress node identifies resource issues and generates individual resource notification messages for each ingress node associated with LSPs, rather than sending separate RSVP error messages for each LSP, reducing the number of messages and conserving resources.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If separate RSVP error messages are sent for each LSP when a resource issue is detected, then complete resource notification is achieved, but the number of messages increases causing resource storms and degrading network performance
Solution Approach 1:
The patent combines multiple individual RSVP error messages into a single aggregated resource notification message. When a non-ingress node detects a resource issue affecting multiple LSPs, it consolidates notifications for all affected LSPs into one message, thereby reducing message overhead while maintaining complete resource notification.
Solution Approach 2:
The aggregated resource notification message serves multiple functions simultaneously: it notifies about resource issues across multiple LSPs, identifies all affected notification-requester stacks, and enables comprehensive resource management in a single communication event, rather than requiring separate messages for each LSP.
2Loss of information
If numerous RSVP error messages are generated for multiple LSPs, then all resource issues are notified, but computing resources are consumed and latency increases
Solution Approach 1:
The patent merges multiple resource notification messages into a single aggregated message that contains information about all affected LSPs and notification-requester stacks. This consolidation reduces the total number of messages transmitted across the network, thereby reducing latency and computing resource consumption while preserving complete resource issue information.
3Measurement precision
If individual error messages are sent for each LSP, then precise resource notification is achieved, but message volume increases reducing throughput
Solution Approach 1:
The patent combines multiple precise resource notifications into a single aggregated message that maintains detailed information about each affected LSP and its associated notification-requester stacks. The aggregation reduces message volume and improves throughput while preserving the precision of resource notification through structured data organization.
Solution Approach 2:
The aggregated resource notification message employs a nested data structure where multiple notification-requester stacks are organized hierarchically within a single message framework. Each stack is properly identified and structured, allowing precise resource notification while consolidating multiple pieces of information into a compact nested format that reduces overall message volume.
Data Source
Figure 1A
Figure 1B
Figure 1C
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.