Automatic LSP Stitching via RSVP-TE Signaling Extensions
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing signaling mechanisms for packet-based networks do not support explicit label switched path (LSP) stitching across multiple domains, requiring manual configuration and lacking automation.
Innovation Solution
The implementation of explicit signaling mechanisms within the Resource Reservation Protocol (RSVP-TE) to automatically stitch LSP segments across domains, enabling continuous label swapping and end-to-end LSP creation by determining support for stitching procedures between ingress and egress routers.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Extent of automation
If manual configuration is used for LSP stitching, then LSP stitching can be performed, but the ease of operation deteriorates and productivity decreases
Solution Approach 1:
The system enables automatic LSP stitching where the network devices themselves perform the stitching operation without human intervention. The ingress router automatically determines stitching capability, establishes correspondence between LSP and LSP segment, and configures the necessary label swapping operations, making the system self-sufficient in performing the stitching function.
Solution Approach 2:
The invention performs preliminary capability assessment by having the ingress router determine whether the LSP segment supports stitching before attempting the actual stitching operation. This preliminary action prevents failed operations and ensures that the stitching process only proceeds when conditions are favorable, improving overall automation reliability.
2Extent of automation
If existing signaling mechanisms are used, then protocol compatibility is maintained, but the extent of automation deteriorates due to lack of explicit stitching support
Solution Approach 1:
The invention segments the LSP creation process into distinct phases: capability determination, correspondence establishment, and actual stitching execution. By introducing specific signaling messages for each phase, the system maintains compatibility with existing RSVP-TE protocols while adding explicit stitching control capabilities that enable automation.
Solution Approach 2:
The invention introduces intermediary signaling messages between the ingress router and egress router to facilitate automatic stitching. These intermediary communications carry capability information and correspondence data, acting as a mediator that enables automated decision-making while maintaining compatibility with existing protocol frameworks.
3Productivity
If automatic stitching is implemented, then productivity improves, but device complexity increases due to additional signaling requirements
Solution Approach 1:
The invention designs the signaling mechanisms to serve multiple functions: capability advertisement, stitching request, correspondence establishment, and confirmation. By making the signaling messages multi-functional, the system reduces the total number of separate messages needed, thereby limiting the increase in device complexity while maintaining high productivity.
Solution Approach 2:
The invention merges the capability determination and stitching initiation into a single signaling exchange between ingress and egress routers. Rather than requiring separate messages for capability check and stitching request, the system combines these functions, reducing signaling overhead and limiting complexity growth while enabling fast automatic stitching.
Data Source
AI summary
Explicit signaling mechanisms facilitate automatic stitching for both packet and non-packet label switched paths (LSPs). Extensions to resource reservation protocol signaling are utilized to include explicit signaling mechanisms that setup and maintain LSPs. An inter-domain LSP may be created by automatically stitching independent LSP segments within separate domains. Stitching the intra-domain LSP segments creates an end-to-end LSP in the data plane with continuous label swapping across the different domains. An intra-domain LSP may be created by automatically stitching independent LSP segment within a single domain. A network device, such as a router, at an ingress of an LSP segment utilizes the signaling extensions to notify a network device at an egress of the LSP segment to prepare for a stitching procedure. In return, the egress network device utilizes the signaling extensions to inform the ingress network device whether the LSP segment is ready for the stitching procedure.