Micro-ABNO SDN Controller for Cloud-Network Scalability
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current SDN controller architectures are inefficient in handling high loads of connectivity service requests, as they are not designed for cloud deployment and lack scalable mechanisms, leading to non-efficient network usage and increased complexity.
Innovation Solution
A microservices-based SDN controller, micro-ABNO, which is highly resilient, self-healing, and dynamically auto-scalable, allowing for immediate deployment of new instances to manage increased loads, and is easily integrated into cloud-native solutions, utilizing gRPC and protocol buffers for intercommunication and a non-relational database for scalability.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If a monolithic SDN controller architecture is used, then the system structure is simple, but the system cannot handle high loads of connectivity service requests and lacks scalability
Solution Approach 1:
The patent applies segmentation by dividing the monolithic SDN controller into multiple independent microservices (e.g., path computation microservice, connectivity management microservice, topology management microservice). Each microservice handles specific functions independently, enabling the system to process high loads of connectivity service requests through parallel execution while maintaining manageable complexity through modular design.
2Adaptability or versatility
If the SDN controller is designed for cloud deployment with auto-scaling, then the system can dynamically handle load increases, but the deployment complexity increases
Solution Approach 1:
The patent implements dynamics by designing the SDN controller as a cloud-native microservices architecture where individual microservices can be independently deployed, scaled, and updated. The system dynamically adapts to load changes by spawning additional instances of specific microservices based on demand, while containerization technologies simplify the deployment process and reduce operational complexity.
3Reliability
If microservices architecture is implemented, then the system achieves high resilience and self-healing, but the intercommunication complexity increases
Solution Approach 1:
The patent employs an intermediary approach by introducing a service mesh or API gateway layer that manages inter-microservice communication. This intermediary handles service discovery, load balancing, authentication, and fault tolerance, thereby achieving high resilience and self-healing capabilities while abstracting away the communication complexity from individual microservices.
4Productivity
If a non-relational database is used for cloud-native integration, then the system achieves better scalability, but the data query complexity increases
Solution Approach 1:
The patent applies parameter changes by selecting appropriate non-relational database types (e.g., document stores, key-value stores, graph databases) based on specific data access patterns and query requirements. The system optimizes database schemas and query structures to match the operational characteristics of each microservice, achieving scalability while managing query complexity through domain-specific optimizations.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
Different aspects of the invention comprise a cloud-native architecture for SDN Controllers based on ABNO architecture and gRPC interfaces with autoscaling mechanisms for high request loads and auto-healing support. The cloud-native micro-ABNO architecture has several key benefits that benefits network automation. The micro-ABNO of the invention provides a higher degree of flexibility, stability and scalability than current monolithic SDN controllers. The application of cloud-native network control and management will provide network operators with a higher degree of network automation.