SDN Controller Orchestration Logic for Simplified Network Management
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing software defined networking (SDN) orchestration methods, particularly using the Neutron model, require users to have a deep understanding of network service capabilities, making it complex for users to orchestrate SDN networks and integrate existing network management systems.
Innovation Solution
A method and SDN controller that automate the creation and connection of logical switches and routers by sending configuration information to forwarding devices, allowing users to orchestrate SDN networks without specifying forwarding devices, simplifying operations and facilitating data transmission.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If users orchestrate SDN networks using the Neutron model, then service capabilities of the SDN network are enhanced, but user operation complexity increases due to the need for deep understanding of network service capabilities
Solution Approach 1:
The patent introduces a translation module that acts as an intermediary between the user-friendly network element model (logical routers, logical switches, ports) and the underlying Neutron service model. This translation module automatically converts high-level orchestration commands into appropriate Neutron API calls, shielding users from the complexity of direct Neutron model operations while maintaining full service capabilities.
Solution Approach 2:
Instead of requiring users to directly operate the complex Neutron model, the patent inverts the approach by providing a simplified abstract model that translates into Neutron operations. The system maps familiar network concepts (logical routers, switches, ports) to Neutron resources automatically, reversing the traditional flow where users must understand the underlying complex model to use it effectively.
2Manufacturing precision
If users directly create and configure logical networks, subnets, and ports using the Neutron model, then precise network control is achieved, but the number of操作步骤 and configuration complexity increases
Solution Approach 1:
The patent merges multiple separate configuration operations (creating logical networks, subnets, ports, and establishing associations) into a single unified orchestration process. Users define network elements using a simplified model, and the system automatically handles the sequential creation and association of all related Neutron resources, reducing the number of discrete steps while maintaining precise control over the final network configuration.
Solution Approach 2:
The system performs preliminary actions by pre-defining the relationships and dependencies between network elements in the simplified model. Before executing actual Neutron API calls, the system analyzes the high-level configuration to determine the correct sequence of operations, pre-calculate resource associations, and prepare the orchestration plan, thereby simplifying the execution phase while ensuring precise control.
3Adaptability or versatility
If existing network management systems are transplanted to SDN networks, then system reusability is improved, but integration complexity increases due to the need to understand SDN-specific service capabilities
Solution Approach 1:
The patent creates an abstract copy of traditional network management concepts that mirrors familiar network elements (routers, switches, ports) but maps them to SDN/Neutron resources. This abstract model serves as a compatibility layer that allows existing network management systems to operate on SDN networks using their familiar data structures and operation patterns, while the translation module handles the mapping to SDN-specific implementations, thereby reducing integration complexity.
Data Source
AI summary
A SDN orchestration method includes: obtaining a first request for creating a first logical switch; creating a control plane instance of the first logical switch, and sending first configuration information to instruct the first forwarding device to configure the data plane instance of the first logical switch; obtaining a second request for connecting the first logical switch to a first logical router; sending second configuration information to instruct the first forwarding device to configure a first port of the data plane instance of the first logical switch to be communicatively connected to a second port of a data plane instance of the first logical router on the second forwarding device configured with the data plane instance of the first logical router; and sending third configuration information to instruct the second forwarding device to configure the second port to be communicatively connected to the first port.