Hierarchical Network Controller Topology for Inter-Domain Path Computation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current telecommunications networks face challenges in managing data connections across multiple domains while maintaining secrecy of internal topology and optimizing network efficiency, especially in transitioning from traditional networks to Software Defined Networks (SDN).
Innovation Solution
A hierarchical or distributed controller architecture is implemented, where parent and child controllers manage inter-domain links and access points without revealing internal topology, using global identifiers for paths and tunnels, and abstracting path segments to enable end-to-end path computation and tunnel creation across multiple domains.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If internal topology information is shared across domains for path computation, then path computation accuracy is improved, but network security and topology confidentiality deteriorate
Solution Approach 1:
The network is divided into multiple domains, each controlled by a separate controller that maintains local topology information independently. Controllers exchange only aggregated domain-level information rather than complete internal topology, enabling path computation across domains while preserving individual domain topology confidentiality.
Solution Approach 2:
A parent controller acts as an intermediary between child controllers in the hierarchical architecture. The parent controller receives path computation requests, coordinates with child controllers to obtain necessary routing information without exposing internal topologies, and computes the end-to-end path while maintaining topology secrecy.
2Device complexity
If a centralized controller manages all domains, then path computation simplicity is improved, but system scalability and reliability deteriorate
Solution Approach 1:
The centralized control function is segmented into a hierarchical structure with parent controllers and child controllers. Each child controller manages specific network domains independently, while parent controllers coordinate between domains. This segmentation enables the system to scale by adding more child controllers without overloading a single centralized controller.
Solution Approach 2:
The control architecture transitions from a single-dimensional centralized model to a multi-dimensional hierarchical model with multiple levels (parent controllers and child controllers). This dimensional change allows the system to maintain coordination simplicity at the parent level while enabling independent domain management at the child level, thus improving both scalability and reliability.
3Object-affected harmful factors
If domain-specific controllers manage individual domains, then network security is improved, but inter-domain path computation complexity increases
Solution Approach 1:
The network control is segmented into domain-specific child controllers that maintain local topology information securely. Each child controller independently manages its domain while participating in coordinated inter-domain path computation through standardized interfaces with parent controllers, reducing the complexity burden on individual controllers.
Solution Approach 2:
Parent controllers serve as intermediaries that simplify inter-domain path computation by receiving requests, coordinating with relevant child controllers, and computing end-to-end paths. This intermediary approach shields domain-specific controllers from complex inter-domain computation tasks while maintaining topology confidentiality within each domain.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A network element (NE) is configured to act as a parent controller. The NE receives connection and access point messages from a plurality of child controllers each child controller controlling one or more network domains. The connection and access point messages indicate inter-domain links and access points for the network domains. The NE receives requests to compute a path from a source to a destination traversing one or more of the network domains. The NE computes the path from the source to the destination via the network domains, and transmits a create tunnel segment message to the child controllers controlling network domains along the path. The create tunnel messages instruct the child controllers to create one or more tunnel segments to forward communications from the source to the destination along the path.