RSVP Resource Notification Messages to Reduce LSP Error Storms
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The resource reservation protocol (RSVP) generates numerous error messages (RSVP error message storm) when non-ingress nodes detect resource issues, consuming computing resources and affecting network performance by increasing latency, reducing throughput, and decreasing bandwidth.
Innovation Solution
Non-ingress nodes generate and send individual resource notification messages to ingress nodes, identifying resource issues and modifying or terminating LSPs, reducing the need for multiple RSVP error messages.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If non-ingress nodes generate RSVP error messages for each LSP when resource issues are detected, then resource allocation accuracy is improved, but network performance deteriorates due to message storms increasing latency and consuming computing resources
Solution Approach 1:
The patent merges multiple individual RSVP error messages into a single consolidated resource notification message that contains information about multiple LSPs. Instead of generating separate error messages for each LSP when resource issues are detected, the system creates one unified notification that lists all affected LSPs, thereby reducing message proliferation while maintaining accurate resource allocation information.
Solution Approach 2:
The resource notification message serves multiple functions simultaneously: it notifies about resource issues, identifies affected LSPs through the notification-requester stack, and enables ingress nodes to make informed decisions about resource reallocation. This multi-functional approach eliminates the need for separate error messages for each LSP.
2Loss of information
If non-ingress nodes send individual error messages for each LSP, then information completeness is improved, but network bandwidth is reduced due to messaging storms
Solution Approach 1:
The patent combines multiple LSP-specific error messages into a single resource notification message that includes a notification-requester stack containing information about multiple LSPs. This merging approach maintains information completeness by including all necessary LSP identifiers and resource issue details in one consolidated message, thereby reducing network bandwidth consumption.
3Measurement precision
If numerous RSVP error messages are generated and sent, then error detection accuracy is improved, but computing resources are consumed and latency increases
Solution Approach 1:
The patent merges multiple error detection operations into a single resource notification message generation process. Instead of processing and sending separate error messages for each LSP, the system identifies resource issues once and generates a single notification that contains error information for all affected LSPs, thereby reducing processing time and latency while maintaining accurate error detection.
Solution Approach 2:
The system performs preliminary identification of resource issues and consolidation of error information before sending notifications. By preparing the notification message in advance with all necessary LSP information already organized in the notification-requester stack, the system reduces processing time and latency when actually sending the notification.
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.