Network Route Publishing via Topology Traversal and Metadata
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing method for L3VPN route publishing in distributed architectures is complex, difficult to troubleshoot, and incompatible with SDN centralized controllers, especially in complex topologies, requiring a route reflector technique and lengthy deployment cycles.
Innovation Solution
A method and device that traverse a pre-constructed network topology starting from a local route introductory node with a maximum hop count to generate and publish network-side routes, utilizing metadata and a publishing engine to adapt to different scenarios without software upgrades, by configuring listener and reflector nodes and service level metadata.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If distributed architecture-based MP-BGP is used for L3VPN route publishing, then route publishing capability is achieved, but configuration complexity increases and troubleshooting becomes difficult
Solution Approach 1:
The patent introduces a route reflector as an intermediary component that mediates route publishing between PE nodes. Instead of direct peer-to-peer route publishing which requires complex RT configuration, the route reflector centralizes the route publishing process, simplifying configuration while maintaining full route publishing capability across the L3VPN network.
Solution Approach 2:
The patent segments the route publishing function by separating route reflection capabilities from standard BGP operations. By dividing the system into route reflector nodes and regular PE nodes with distinct functional roles, the complexity of RT configuration is isolated to specific nodes, making the overall system easier to configure and troubleshoot.
2Adaptability or versatility
If route reflector technique is used to support complex topologies, then route publishing flexibility improves, but system complexity increases
Solution Approach 1:
The patent makes the route reflector technique universally applicable to all L3VPN topologies by designing it as an optional enhancement that can be deployed regardless of network complexity. The same route reflector mechanism handles both simple and complex topologies uniformly, providing flexibility without requiring different solutions for different scenarios.
Solution Approach 2:
The patent applies preliminary action by pre-configuring route reflector nodes with their reflection capabilities before actual route publishing begins. This allows the system to handle complex topologies from the outset without requiring dynamic complexity management during operation, simplifying the overall system architecture.
3Ease of operation
If RT technique is used to control route publishing between neighbors, then route publishing control is achieved, but configuration difficulty increases
Solution Approach 1:
The patent extracts the complex RT configuration requirements from the general route publishing process and concentrates them specifically in the route reflector nodes. This allows regular PE nodes to use simpler configuration while the route reflector handles the sophisticated route control logic, making the overall system easier to configure.
Solution Approach 2:
The route reflector acts as an intermediary that simplifies route publishing control. Instead of requiring complex RT configuration between all pairs of PE nodes, the route reflector mediates route publishing with simpler configuration rules, reducing configuration difficulty while maintaining precise control over which routes are published to which neighbors.
4Stability of the object's composition
If protocol model is solidified in distributed MP-BGP, then stability is improved, but scheme updating and deployment cycle lengthens
Solution Approach 1:
The patent introduces dynamics by making the route reflector configuration modular and adaptable. While the core BGP protocol remains stable, the route reflector component can be updated and configured flexibly to accommodate new requirements without changing the fundamental protocol model, enabling faster scheme updates and deployment.
Data Source
Figure 1~3
Figure 4~5
AI summary
Disclosed are a method and device for publishing a static network route, the method including: traversing (S101) a pre-constructed network topology starting from a local route introductory node in the network and according to a maximum hop count so as to obtain a traversing result list containing traversed listener nodes and reflector nodes; and according to the traversing result list, generating (S102) a network-side route and publishing the generated network-side route to corresponding nodes in the network.