Virtual Network Routers for Cloud Native SDN Scalability
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current software-defined networking (SDN) architectures face challenges in cloud-native adoption due to complexity in life cycle management, scale limitations in configuration modules, and the lack of command-line interface (CLI)-based interfaces, which hinder efficient management and scalability in cloud data centers.
Innovation Solution
A cloud-native SDN architecture is introduced, featuring a scale-out design with container-based microservices, a network controller for simplified installation and modular upgrades, and a unified intent model using custom resources exposed through an aggregated API layer, enabling intuitive intent-based networking and improved usability.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional SDN architecture is used, then network control functionality is provided, but system complexity and difficulty in life cycle management increase
Solution Approach 1:
The patent segments the SDN controller into multiple independent containerized microservices that can be deployed, managed, and upgraded separately. Each microservice handles specific network control functions, allowing independent lifecycle management without affecting the entire system. This resolves the contradiction by maintaining full network control functionality while eliminating the complexity of managing a monolithic SDN controller.
Solution Approach 2:
The patent implements a universal container orchestration platform that manages multiple SDN controller microservices along with other network functions using standardized interfaces and processes. This multi-functional approach allows the same infrastructure to handle diverse network control tasks, reducing overall system complexity while maintaining comprehensive network control capabilities.
2Ease of operation
If traditional configuration modules are used, then network configuration is provided, but scalability is limited
Solution Approach 1:
The patent implements dynamic configuration modules that can be independently scaled and adapted based on workload requirements. The containerized architecture allows configuration services to be dynamically added, removed, or modified without reconfiguring the entire system. This resolves the contradiction by providing ease of operation through standardized interfaces while achieving scalability through flexible, dynamic resource allocation.
Solution Approach 2:
The patent enables parameter changes in configuration modules by allowing independent scaling of container instances based on demand. Configuration capacity can be adjusted by modifying the number and resources of container instances, providing both ease of operation through consistent interfaces and scalability through flexible parameter adjustment.
3Ease of operation
If conventional SDN architecture is used, then network management is provided, but CLI-based interfaces and usability are lacking
Solution Approach 1:
The patent introduces container orchestration platforms and abstraction layers as intermediaries between users and the underlying complex SDN infrastructure. These intermediaries provide simplified CLI-based interfaces and automated management capabilities, hiding the complexity of individual microservices while maintaining full network management functionality. This resolves the contradiction by improving usability through intermediary interfaces without adding to the actual system complexity.
Data Source
AI summary
In general, techniques are described for a creating a virtual network router within a software defined network (SDN) architecture. A network controller for the SDN architecture system may include processing circuitry that is configured to execute a configuration node and a control node. The configuration node may process a request by which to create a virtual network router (VNR), where the virtual network router may cause the network controller to interconnect a first virtual network (VN) and a second VN. The VNR may represent a logical abstraction of one or more policies that cause import and/or export of routing information between the first VN and the second VN. The control node configures the first VN and the second VN according to the one or more policies to enable the import and/or the export of routing information between the first VN and the second VN via the VNR.