Route Processing Method for Cross-Domain Network Stitching
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The configuration of stitching nodes in networks that combine newly constructed SRv6 networks with conventional MPLS networks is cumbersome due to the need for extensive configuration to perceive VRF instances, leading to increased operational complexity and configuration pressure.
Innovation Solution
A route processing method where a first network device allocates a second identifier based on a first identifier in a received route and sends a second route carrying the second identifier to a third network device in a different network domain, facilitating normal route advertisement across domains without the need for extensive stitching node configuration.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If the stitching node uses VRF instance to transfer and re-advertise routes, then route advertisement between network domains is achieved, but the configuration complexity on the stitching node increases significantly
Solution Approach 1:
The patent introduces a route reflection mechanism where the stitching node acts as an intermediary to reflect routes between network domains. Instead of requiring complex VRF configurations, the stitching node simply reflects routes received from one domain to another domain, significantly simplifying the configuration while maintaining route advertisement capability.
Solution Approach 2:
The patent enables the stitching node to perform multiple functions through a unified route reflection mechanism. The same reflection process handles routes from different network domains (SRv6 and MPLS), making the stitching node universally applicable to various network domain combinations without requiring domain-specific complex configurations.
2Reliability
If extensive configuration is added on the stitching node to perceive VRF, then VRF routing is achieved, but the ease of operation deteriorates
Solution Approach 1:
The patent implements self-service by enabling the stitching node to automatically reflect routes without requiring manual VRF configuration. The route reflection process is autonomous and does not depend on complex VRF perceptions, making the system easier to operate while maintaining reliable routing capability.
Solution Approach 2:
The patent extracts the essential function of route reflection from the complex VRF mechanism. By separating the route reflection function from VRF configuration, the system maintains reliable routing while eliminating the need for complex VRF perceptions and configurations on the stitching node.
3Adaptability or versatility
If a large amount of configuration is added on the stitching node, then cross-network service capability is improved, but the configuration pressure increases
Solution Approach 1:
The patent uses the stitching node as a simple route reflection intermediary that does not require extensive configuration. The node simply reflects routes between network domains without needing complex cross-network service configurations, thereby reducing configuration pressure while maintaining cross-network service capability.
Solution Approach 2:
The patent segments the routing function into simple route reflection at the stitching node and independent route processing at each network domain. This segmentation allows each domain to manage its own routing independently, reducing the configuration burden on the stitching node while maintaining overall cross-network service capability.
Data Source
AI summary
A route processing method, implemented by a first device, includes: receiving a first route sent by a second network device, where the first route includes a first identifier; allocating, based on the first identifier, a second identifier corresponding to the first route; and sending a second route to a third network device based on the first route, where the second route includes the second identifier. The second network device is located in a first network domain, and the third network device is located in a second network domain.