BGP Logical Topology Generation in SDN Controllers
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current technologies fail to effectively collect and manage Border Gateway Protocol (BGP) logical topology between forwarders in centralized network control systems, making it difficult for controllers to manage forwarders running the BGP protocol.
Innovation Solution
A method and device that allow a controller to obtain and generate BGP logical topology between forwarders by collecting node information and BGP session information, determining session types (IBGP or EBGP), and establishing corresponding BGP sessions using OpenFlow or Diameter protocols, enabling the formation of a BGP logical topology.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If a controller is introduced to centrally manage BGP sessions between forwarders, then network management capability is improved, but the complexity of implementing topology collection and session establishment increases
Solution Approach 1:
The controller acts as an intermediary that receives BGP session establishment requests from forwarders, autonomously determines session types (IBGP/EBGP), and manages session establishment. This mediator approach simplifies forwarder operations while centralizing management complexity in the controller, resolving the contradiction between improved management capability and implementation complexity.
Solution Approach 2:
The system implements feedback mechanisms where forwarders report their BGP node information and session status to the controller, and the controller provides guidance for session establishment. This feedback loop enables automated topology collection and session management, improving ease of operation while managing complexity through structured information exchange.
2Loss of information
If the controller collects detailed BGP node information and session information from all forwarders, then topology awareness is improved, but information collection overhead and processing complexity increase
Solution Approach 1:
The controller extracts only the essential BGP node information (Router ID, autonomous system number) and session information needed for topology construction from forwarders. This selective extraction approach achieves sufficient topology awareness without collecting excessive data, reducing information collection overhead and processing complexity while maintaining necessary topology awareness.
3Measurement precision
If the controller autonomously determines BGP session types (IBGP or EBGP) and establishes sessions, then session management accuracy is improved, but control logic complexity increases
Solution Approach 1:
The controller determines session types by comparing autonomous system numbers as a key parameter: if the autonomous system numbers match, it establishes an IBGP session; if they differ, it establishes an EBGP session. This parameter-based decision logic achieves accurate session type determination with relatively simple control logic, avoiding complex routing policy analysis while maintaining precision.
Data Source
AI summary
A BGP logical topology generation method includes obtaining, by a controller, node information of a first forwarder and BGP session information of the first forwarder, and obtaining node information of a second forwarder and BGP session information of the second forwarder; and generating, by the controller, a BGP logical topology between the first forwarder and the second forwarder according to the node information and the BGP session information of the first forwarder, and the node information and the BGP session information of the second forwarder that are obtained.