SR Interworking Controller for SR-MPLS to SRv6 Domain Bridging
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing technologies face challenges in seamlessly interworking between different segment routing protocol domains, such as SR-MPLS and SRv6, which hinders efficient data routing across networks with diverse routing protocols.
Innovation Solution
Implementing an SR domains Interworking controller that determines optimal paths and pushes label stacks or extension headers to routers in both SR-MPLS and SRv6 domains, enabling seamless segment routing by converting between SR-MPLS label stacks and SRv6 extension headers.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If segment routing is implemented across networks with different routing protocols (SR-MPLS and SRv6), then network interoperability and routing efficiency are improved, but the complexity of interworking between different protocol domains increases
Solution Approach 1:
An SR domains interworking controller is introduced as an intermediary component that bridges SR-MPLS and SRv6 domains. The controller receives path establishment requests, determines optimal paths through both domains, and coordinates the pushing of label stacks and extension headers to appropriate routers, thereby enabling interoperability while centralizing the complexity in a dedicated mediation component
Solution Approach 2:
The network is segmented into distinct SR-MPLS domains and SRv6 domains, each handled by specialized routers equipped with specific protocol capabilities. The interworking controller divides the path establishment task into sub-tasks: determining the overall path, identifying domain boundaries, and coordinating protocol-specific operations in each domain, thereby managing complexity through functional segmentation
2Reliability
If label stacks and extension headers are pushed to routers for path establishment, then segment routing paths are established with precise control, but signaling overhead increases
Solution Approach 1:
Label stacks and extension headers are pushed to routers in advance during path establishment before actual data transmission begins. The interworking controller proactively sets up the entire SR path through both domains by pushing the necessary label stacks to SR-MPLS routers and extension headers to SRv6 routers beforehand, ensuring reliable forwarding without real-time computation overhead
Solution Approach 2:
The path establishment process establishes a continuous SR path through both domains with pre-configured forwarding instructions. Once the label stacks and extension headers are pushed, the forwarding action continues seamlessly through the entire path without requiring additional signaling or control actions during data transmission, maintaining continuous useful action from source to destination
Data Source
AI summary
A controller determines a first path across a first segment routing (SR) domain and a second SR domain to a destination in the second SR domain, where the first SR domain uses a first SR protocol and the second SR domain uses a second SR protocol. The controller determines SR instructions that enable the interworking of the first SR domain and the second SR domain when data is routed across the first path to the destination. The controller sends, prior to the data being routed over the first path, the SR instructions to at least one of a first router in the first SR domain, a second router in the second SR domain, or a third router in the first SR domain to enable the interworking of the first and the second SR domains for segment routing the data across the first path.