18343598. RESOURCE RESERVATION PROTOCOL RESOURCE NOTIFICATION MESSAGES simplified abstract (Juniper Networks, Inc.)

RESOURCE RESERVATION PROTOCOL RESOURCE NOTIFICATION MESSAGES

Organization Name

Juniper Networks, Inc.

Inventor(s)

Vishnu Pavan Beeram of Hyderabad (IN)

Chandrasekar Ramachandran of Bangalore (IN)

RESOURCE RESERVATION PROTOCOL RESOURCE NOTIFICATION MESSAGES - A simplified explanation of the abstract

This abstract first appeared for US patent application 18343598 titled 'RESOURCE RESERVATION PROTOCOL RESOURCE NOTIFICATION MESSAGES

Simplified Explanation: The abstract describes a system where a non-ingress node of label-switched paths can identify resource issues and send notification messages based on the identified issues.

• The system allows non-ingress nodes to detect resource problems on label-switched paths.
• Notification messages are generated by the non-ingress nodes and sent to relevant parties.
• The messages include information about the identified resource issues and notification-requester stacks.

Key Features and Innovation:

• Detection of resource issues on label-switched paths by non-ingress nodes.
• Generation and sending of notification messages based on identified resource problems.
• Inclusion of notification-requester stacks in the messages for targeted communication.

Potential Applications: This technology can be applied in networking systems to improve resource management and efficiency.

Problems Solved:

• Efficient detection of resource issues on label-switched paths.
• Targeted communication of resource problem notifications.

Benefits:

• Improved network performance.
• Timely identification and resolution of resource issues.

Commercial Applications: This technology can be utilized by network operators and service providers to enhance the reliability and performance of their networks.

Questions about the Technology: 1. How does the system differentiate between different types of resource issues? 2. What measures are in place to ensure the accuracy and reliability of the notifications sent by non-ingress nodes?

Original Abstract Submitted

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.