Micro-service Network Operation Support System Architecture
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional cloud-based WI-FI network operation support systems face challenges in scalability and availability due to their dependency on virtual servers and NMS deployment software, making it difficult to extend and maintain the system effectively.
Innovation Solution
A network operation support system is designed using a micro-service architecture, where each micro-service operates independently in a container, with a main graph database for unified data management, and communication among services through a message queue, enabling real-time monitoring, analysis, and fault diagnosis.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If the system is deployed on virtual servers using IaaS mode and depends on cloud deployment software, then the system can be implemented in cloud environment, but the functional layout depends on NMS server and the system is difficult to be extended
Solution Approach 1:
The system is divided into multiple independent microservices (configuration management service, device management service, monitoring service, analysis service, etc.), each running in separate containers. This segmentation eliminates the dependency on a single NMS server and allows independent extension of specific functions without affecting the entire system.
Solution Approach 2:
The microservices architecture with standardized interfaces and message queues creates a universal platform that can perform multiple functions through different service combinations. The system can extend functionality by adding new microservices without being constrained by the original NMS server's functional layout.
2Ease of operation
If the system follows conventional client-server structure and is deployed at server level, then the system can operate with NMS deployment software, but the system itself has no layout and depends on deployment software
Solution Approach 1:
Each microservice is self-contained with its own configuration, data storage, and business logic. The services autonomously manage their operations through event-driven communication via message queues, eliminating the need for external deployment software to coordinate system operations. The system becomes self-sufficient and easier to operate independently.
3Reliability
If the system is deployed at virtual machine level, then the system can run in cloud environment, but the functional layout depends on NMS server resulting in unfavorable availability
Solution Approach 1:
By segmenting the monolithic NMS server into multiple independent microservices running in containers, the system achieves both high availability (through service independence and fault isolation) and functional layout flexibility (through configurable service orchestration via message queues and event streams).
Solution Approach 2:
The system employs dynamic service registration, discovery, and orchestration mechanisms that allow functional layouts to be adjusted in real-time based on operational requirements. Services can be dynamically added, removed, or reconfigured without system downtime, enhancing both availability and flexibility simultaneously.
Data Source
AI summary
Provided are a network operation support system and a network device management method, belonging to the technical field of communications. The system uses a micro-service architecture realized based on a container, and the system itself has a good expansibility and availability, and supports automation and layout in a cloud environment. In addition, the system also uses a main database to synchronously store operating data of various micro-services for unified maintenance of the data, thereby improving the analysis efficiency of the system.