Integrating RSVP-TE and Segment Routing for QoS
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Modern networks face challenges in efficiently managing diverse traffic flows while ensuring optimal resource reservation and Quality of Service (QoS) requirements, as traditional routing protocols like RSVP-TE focus on resource reservation, whereas Segment Routing (SR) introduces opportunities for network optimization without complex signaling protocols, leading to a need for integrating both for enhanced resource allocation and QoS guarantees.
Innovation Solution
The techniques enable the coexistence of RSVP-TE and SR within a network by using bandwidth reservation measures from SR to inform RSVP-TE routing decisions, creating one-hop RSVP-TE LSPs based on SR bandwidth reservations, and integrating SR bandwidth reservation measurements into RSVP-TE for optimized resource allocation and path selection.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If RSVP-TE protocol is used for resource reservation, then QoS guarantees are improved, but device complexity and signaling overhead increase
Solution Approach 1:
The patent merges RSVP-TE and Segment Routing protocols within the same network infrastructure, allowing RSVP-TE to operate over SR paths. This combination enables QoS guarantees through RSVP-TE's resource reservation capabilities while utilizing SR's simplified forwarding plane, thereby reducing overall device complexity and signaling overhead compared to pure RSVP-TE implementations.
Solution Approach 2:
The network infrastructure is designed to support multiple protocols (RSVP-TE and Segment Routing) simultaneously, making the system multi-functional. This universality allows the network to leverage the QoS guaranteeing capability of RSVP-TE while also benefiting from SR's simplified routing mechanisms, reducing the need for separate dedicated systems.
2Device complexity
If Segment Routing is used for network optimization, then device complexity is reduced, but resource reservation capability is worsened
Solution Approach 1:
The patent combines Segment Routing's simplified forwarding plane with RSVP-TE's resource reservation signaling plane. This merging allows the network to enjoy reduced device complexity from SR while maintaining strong resource reservation capabilities through RSVP-TE, as RSVP-TE signaling messages can establish resource reservations along SR-defined paths.
Solution Approach 2:
The patent segments the routing function into two distinct parts: the Segment Routing control plane for path definition and the RSVP-TE signaling plane for resource reservation. This segmentation allows each protocol to operate in its optimal domain, with SR handling forwarding simplification and RSVP-TE handling resource guarantees, thereby resolving the contradiction between complexity reduction and reservation capability.
3Productivity
If both RSVP-TE and Segment Routing are integrated, then resource allocation is optimized, but protocol compatibility challenges increase
Solution Approach 1:
The patent introduces a mediator mechanism that translates between Segment Routing path definitions and RSVP-TE signaling messages. This intermediary layer handles the protocol compatibility challenges by converting SR's simplified path setup into RSVP-TE's detailed resource reservation messages, enabling optimized resource allocation while managing integration complexity through standardized translation procedures.
Data Source
AI summary
Techniques for enabling a resource reservation routing protocol (e.g., the Resource Reservation Protocol-Traffic Engineering (RSVP-TE) protocol) to perform routing operations based at least in part on bandwidth reservations by a non-reservation protocol (e.g., the Segment Routing (SR) protocol) are described herein. In some cases, the techniques described herein enable an example network to use both a resource reservation protocol and a non-reservation protocol. In some cases, one or more bandwidth reservation measures associated with a label-switched path (LSP) associated with a non-reservation protocol (e.g., an SR LSP) are used to create LSPs associated with a resource reservation protocol (e.g., RSVP-TE LSPs).