Domain Controller Auto-Configures Multi-Vendor Network Functions
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Configuring network elements in multi-vendor and multi-domain topologies is complex due to proprietary data models, varying configurable features, and different interface protocols, making it challenging to achieve optimized performance across devices from different vendors and domains.
Innovation Solution
A domain controller uses machine learning to predict and apply optimal runtime configurations for virtual, physical, and cloud-native network functions, building a database of their characteristics to adapt to changing network demands and ensure compatibility across vendors.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If manual configuration methods are used for network elements in multi-vendor and multi-domain topologies, then configuration control and precision can be maintained, but the complexity of configuration and time consumption increase significantly
Solution Approach 1:
The system enables network elements to automatically discover and configure themselves by exchanging capability information and configuration parameters through standardized interfaces. Network elements autonomously determine compatibility and establish optimal configurations without manual intervention, making the system self-configure and self-manage across multi-vendor and multi-domain environments.
Solution Approach 2:
The patent implements a universal configuration framework that handles multiple vendor-specific protocols and data models through a standardized interface layer. This universal system can manage diverse network elements from different vendors and domains using common configuration procedures, eliminating the need for vendor-specific manual configuration processes.
2Reliability
If vendor-specific proprietary data models and interface protocols are used, then device compatibility and functionality can be maintained, but the difficulty of configuration and integration across vendors increases
Solution Approach 1:
The system introduces a standardized interface layer that acts as an intermediary between vendor-specific proprietary data models and the universal configuration framework. This intermediary layer translates and harmonizes different vendor protocols and data models, enabling seamless integration and configuration across multi-vendor environments while preserving vendor-specific functionality and reliability.
Solution Approach 2:
The patent dynamically adjusts configuration parameters based on vendor-specific capabilities and requirements. The system automatically modifies configuration parameters to accommodate different vendor data models and protocols while maintaining consistent configuration procedures, thereby reducing configuration difficulty without sacrificing device compatibility.
3Stability of the object's composition
If static configuration approaches are used, then configuration stability can be maintained, but the ability to adapt to changing network demands and traffic patterns decreases
Solution Approach 1:
The system transitions from static configuration to dynamic, adaptive configuration where network elements continuously exchange capability information and adjust their configurations based on real-time network conditions and traffic patterns. This dynamic approach maintains stability through standardized procedures while enabling adaptability to changing demands through automated reconfiguration.
Solution Approach 2:
The patent implements feedback mechanisms where network elements monitor network conditions, traffic patterns, and performance metrics, then automatically adjust their configurations in response. This feedback loop enables the system to maintain stable operation while adapting to changing network demands, ensuring both configuration stability and adaptability simultaneously.
Data Source
AI summary
Devices, computer-readable media, and methods for automatically configuring network elements in multi-vendor and multi-domain topologies. In one example, a method includes determining a need of a communications network, where a topology of the communications network includes a plurality of network functions from at least two different vendors, predicting a subset of the plurality of network functions and respective configuration parameter values for network functions in the subset, that are expected to support the need of the communications network, and modifying the configurations of the network functions in the subset to reflect the respective configuration parameter values.