WO2018113556A1 - 一种网络运营支撑系统及网络设备管理方法 - Google Patents

一种网络运营支撑系统及网络设备管理方法 Download PDF

Info

Publication number
WO2018113556A1
WO2018113556A1 PCT/CN2017/115708 CN2017115708W WO2018113556A1 WO 2018113556 A1 WO2018113556 A1 WO 2018113556A1 CN 2017115708 W CN2017115708 W CN 2017115708W WO 2018113556 A1 WO2018113556 A1 WO 2018113556A1
Authority
WO
WIPO (PCT)
Prior art keywords
configuration
data
service
microservice
database
Prior art date
Application number
PCT/CN2017/115708
Other languages
English (en)
French (fr)
Inventor
李屏君
张志飞
雷永成
陈华
Original Assignee
成都西加云杉科技有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 成都西加云杉科技有限公司 filed Critical 成都西加云杉科技有限公司
Priority to US16/472,396 priority Critical patent/US10944628B2/en
Publication of WO2018113556A1 publication Critical patent/WO2018113556A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0895—Configuration of virtualised networks or elements, e.g. virtualised network function or OpenFlow elements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/02—Standardisation; Integration
    • H04L41/0246—Exchanging or transporting network management information using the Internet; Embedding network management web servers in network elements; Web-services-based protocols
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/02—Standardisation; Integration
    • H04L41/0246—Exchanging or transporting network management information using the Internet; Embedding network management web servers in network elements; Web-services-based protocols
    • H04L41/0273—Exchanging or transporting network management information using the Internet; Embedding network management web servers in network elements; Web-services-based protocols using web services for network management, e.g. simple object access protocol [SOAP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/04—Network management architectures or arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H04L41/0806—Configuration setting for initial configuration or provisioning, e.g. plug-and-play
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/40—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks using virtualisation of network functions or resources, e.g. SDN or NFV entities
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H04L43/0805—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability
    • H04L43/0817—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability by checking functioning
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/20—Arrangements for monitoring or testing data switching networks the monitoring system or the monitored elements being virtualised, abstracted or software-defined entities, e.g. SDN or NFV
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/34—Signalling channels for network management communication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/51—Discovery or management thereof, e.g. service location protocol [SLP] or web services

Definitions

  • the present application relates to the field of communications technologies, and in particular, to a network operation support system and a network device management method.
  • the traditional WI-FI network operation support system runs on the server of the network management center, and its system architecture still uses the traditional client-server structure. Because it is deployed at the server level, it relies on the NMS (Network Management System) to deploy software, and the system itself is not orchestrated.
  • NMS Network Management System
  • the preferred embodiment of the present application provides a network operation support system, where the system includes: a pre-configured micro service configured to receive configuration data input by a user layer interface, and store the configuration data in a configuration database; And configured to obtain the configuration data from the configuration database and send the configuration data to the network device; the network management micro service is configured to monitor and manage the running status and configuration data of the network device, and generate the data according to the data acquired in the monitoring management process. Analyze the report; analyze the microservice, configure the algorithm to support all the analysis requirements of the network operation support system; and the primary database, configured to synchronously store the operational data of each microservice and the data model between the operational data of different microservices, Perform unified maintenance of data.
  • the primary database is a graphical database that uses a graph structure to establish a data model between operational data of different microservices.
  • each microservice in the network operation support system is implemented based on a separate container, and each micro service is transported.
  • the row data is stored in at least one of three types of data storage modes: database storage, file storage, and write memory or cache.
  • the system further includes a communication micro-service, wherein: the network management micro-service, the configuration download micro-service, and the communication micro-service exchange information through a message queue, wherein the network management micro service performs the network device
  • the process of monitoring and managing configuration data includes:
  • the configuration download microservice Transmitting, by the network management microservice, the configuration download or upgrade request to the configuration download microservice by using the message queue; the configuration download microservice is obtained from the configuration database according to the configuration download or upgrade request After the configuration data is sent, the obtained configuration data is sent to the communication micro service; after receiving the configuration data, the communication micro service sends the configuration data to the network device.
  • the system further includes: a service operation micro service, configured to perform operation management on the service of the network operation support system, where the operation data of the service operation micro service is stored in an operation relationship database, the main database and the The operational relational database is connected to synchronously store the operational data of the service operation microservice.
  • a service operation micro service configured to perform operation management on the service of the network operation support system, where the operation data of the service operation micro service is stored in an operation relationship database, the main database and the The operational relational database is connected to synchronously store the operational data of the service operation microservice.
  • the system further includes: a data collection aggregation micro service configured to collect logs and statistics from the network device and each micro service, and save the collected information to the NoSQL database; diagnose the micro service, configure In the cooperation of the analysis microservice, the fault of the network operation support system is diagnosed in real time based on the data stored in the NoSQL database or in the main database.
  • a data collection aggregation micro service configured to collect logs and statistics from the network device and each micro service, and save the collected information to the NoSQL database
  • diagnose the micro service configure In the cooperation of the analysis microservice, the fault of the network operation support system is diagnosed in real time based on the data stored in the NoSQL database or in the main database.
  • system further includes: a fault location microservice configured to exclude the fault in real time according to the diagnosis result of the diagnostic microservice.
  • the preferred embodiment of the present application further provides a network device management method, which is applied to a network operation support system, where the network operation support system includes multiple microservices implemented based on independent containers; the method includes:
  • the configuration is sent to the network device.
  • the data of the running data of each micro service and the running data of different micro services are synchronously stored by the primary database to perform unified maintenance of the data.
  • the configuration database includes a data table configured to record configuration data that has been updated by the pre-configured micro-service; the configuration downloading micro-service obtains configuration data from the configuration database, and then sends the configuration data to the configuration database.
  • the steps of the network device include:
  • the configuration download microservice performs update detection on the data table according to a predetermined schedule
  • the configuration download micro-service obtains all the currently updated configuration data and delivers the configuration data to the network device.
  • the network operation support system further includes a communication micro service, where the network management micro service, the configuration download micro service, and the communication micro service exchange information through a message queue;
  • the steps of the network device performing monitoring and management of configuration data include:
  • the configuration downloading micro-service After the configuration downloading micro-service obtains the corresponding configuration data from the configuration database according to the configuration download or upgrade request, the configuration data is sent to the communication micro-service;
  • the communication micro-service After receiving the configuration data, the communication micro-service sends the configuration data to the network device.
  • the method further includes:
  • the method further includes:
  • the fault of the network operation support system is diagnosed in real time by the diagnostic microservice in cooperation with the analysis microservice based on the data stored in the NoSQL database or in the primary database.
  • the method further includes:
  • the fault is correctly excluded according to the diagnosis result of the diagnostic microservice by the fault location microservice.
  • the method further includes:
  • a user layer interface in the form of a graphical user interface is provided through the user interface microservice for the user to access all microservices through the graphical user interface.
  • the operation support system applied to the WI-FI network provided by the embodiment of the present application adopts a container-based micro service architecture, and the system itself has good scalability and availability, and does not need to rely on orchestration software to support automation and orchestration in the cloud environment. Easier to implement components and services, and further evolving new services in the cloud.
  • the system also uses the main database to link the running data of each micro service together to perform unified data maintenance and improve the analysis efficiency of the system.
  • FIG. 1 is a schematic diagram of a system framework of a network operation support system based on a micro service architecture according to an embodiment of the present application
  • FIG. 2 is a schematic diagram of a system framework of another network operation support system based on a micro service architecture according to an embodiment of the present application.
  • Icons 100-network operation support system; 102-pre-configured micro-service; 104-configuration download micro-service; 106-network management micro-service; 108-analysis micro-service; 110-user interface micro-service; 112-communication micro-service; - Business Operations Microservices; 116 - Data Collection Aggregation Microservices; 118 - Diagnostic Microservices; 120 - Fault Location Microservices; 101 - Master Database; 103 - Configuration Database; 105 - Network Management Relationship Database; 107 - Message Queuing; Operational relational database; 111-NoSQL database.
  • Microservices Architecture is an architectural style and design pattern developed by decomposing applications into a set of independently deployable, miniaturized, modular microservices, each running in a separate process.
  • the microservices have clear boundaries and interact with lightweight communication mechanisms to serve specific business objectives through a versioned API (Application Programming Interface) and data storage.
  • the micro service architecture is applied to the development of a network operation support system, and the original network management and operation and maintenance services are decomposed according to functional boundaries into a set of micro-services that can be independently deployed, compiled, and extended at the cloud server level.
  • Service module Compared with the network operation support system deployed at the physical server level or virtual host level in the prior art, it has better scalability and availability, supports automation and orchestration in the cloud environment, and does not need to rely on orchestration software.
  • the unified data maintenance based on the primary database solves the problem that the operation data of each micro service in the existing micro service structure is difficult to establish a data link, thereby further improving the analysis efficiency of the system, thereby further improving the analysis efficiency of the system. Enables real-time diagnosis and troubleshooting of the system.
  • the network operation support system provided by the embodiment of the present application can be applied to the WI-FI network system. Management and operation and maintenance, but not limited to this.
  • the implementation principle of the network operation support system provided by the embodiment of the present application will be described in detail below by taking the WI-FI network as an example and referring to the accompanying drawings.
  • the micro service architecture provided by the following embodiments is merely exemplary, and the basic microservices and optional microservices included in the other embodiments may be mutually transformed or further services according to actual needs. Design, functional boundary division, etc.
  • the basic microservice refers to a core (essential) microservice in the network operation support system
  • the optional microservice may refer to a microservice configured in the network operation support system to further optimize the system.
  • the embodiment provides a system architecture diagram of a network operation support system 100 including only a basic micro service and a primary database 101.
  • the basic microservices include a pre-configured microservice 102, a configuration download microservice 104, a network management microservice 106, and an analysis microservice 108.
  • each micro service of the network operation support system 100 is implemented based on a separate container (such as a Docker container), and each of the micro services can be used as a function that the network operation support system 100 can be independently deployed and operated. Module.
  • a separate container such as a Docker container
  • the pre-configured microservices 102 are configured to receive configuration data entered by the user layer interface and store the configuration data in the configuration database 103. That is, the configuration data entered by the user through the user layer interface will ultimately be delivered to the pre-configured microservices 102 for persistence by the pre-configured microservices 102.
  • the pre-configured microservices 102 can also be configured to check the validity of the configuration.
  • the configuration data can also be directly stored in the main database 101 without the need to separately configure the configuration database 103.
  • the configuration download micro-service 104 is configured to be sent to the network device after obtaining the configuration data from the configuration database 103.
  • the network device may be a wireless controller and a wireless access point communicatively coupled to the wireless controller, but is not limited thereto.
  • the wireless controller manages the wireless access point through a CAPWAP (Control and Provisioning of Wireless Access Points Protocol Specification) tunnel, and when the wireless controller receives the configuration download microservice 104 After the configuration data is delivered, the configuration data is sent to the wireless access point through the CAPWAP tunnel.
  • CAPWAP Control and Provisioning of Wireless Access Points Protocol Specification
  • the network management microservice 106 is configured to monitor and manage the running status and configuration data of the network device, and generate an analysis report according to the data acquired in the monitoring management process. It should be noted that in other embodiments, the network management microservice 106 may also have other functions, such as system management, topology management functions, and the like in an existing network management service.
  • the analysis micro-service 108 is configured to provide support for all analysis requirements of the network operation support system 100, such as providing a corresponding analysis algorithm for the network management micro-service 106 in the statistical report.
  • the primary database 101 is configured to synchronously store the operational data of each microservice and the data model between the operational data of different microservices to perform unified maintenance of the data, thereby improving the analysis efficiency of the system.
  • some functions of the network operation support system 100 are implemented or maintained by different microservices, and different microservices may use different types of databases (such as a relational database or a non-relational database) to maintain their own functions. data. Therefore, in order to realize synchronous management of data between different microservices, different storage services are uniformly stored, converted or synchronized by the primary database 101.
  • databases such as a relational database or a non-relational database
  • the primary database 101 is implemented using a graphical database.
  • the graphics database establishes a data model between operational data of different microservices through a graph structure to meet the requirements of the tree storage structure.
  • the running data of each micro service may be stored in at least one of three types of data storage modes: database storage, file storage, and write memory or cache. That is to say, in the network operation support system 100 provided in this embodiment, the storage mode of the operation data of the micro service is allowed to be different from that of the main database 101.
  • the pre-configured microservices 102 stores configuration data in a configuration database 103, which can store data suitable for structured storage (such as a device repository, etc.) in the operational data in a network management relational database.
  • 105 other running data is written to the cache or memory.
  • the configuration data delivery usually includes the following two situations:
  • the configuration data is sent to the network device after the configuration data corresponding to the request is obtained from the configuration database 103 in response to the configuration download or upgrade request initiated by the network management micro-service 106.
  • the second is that the configuration data is obtained from the configuration database 103 and then sent to the network device.
  • a data table configured to describe configuration data that has been updated by the pre-configured microservices 102 is stored in the configuration database 103.
  • the configuration download micro-service 104 performs update detection on the data table according to a predetermined schedule. Once the configuration data that has been updated is found, the configuration download micro-service 104 acquires all current updated configuration data and Send to the network device.
  • Each microservice in the network operation support system 100 provided by this embodiment exists in the form of a service component.
  • a portion of the microservices can be further divided into a plurality of deployable subservice components based on functional boundaries.
  • two or more microservices in the network operation support system 100 may also be combined into one microservice.
  • the preconfigured microservice 102 and the The configuration download microservices 104 can be combined into one configuration microservice, which can coordinate the data configuration operations of the system.
  • each microservice can be accessed through the user layer interface.
  • information interaction relationship between microservices is not shown in FIG. 1, mutual access between different microservices (such as information interaction between the network management microservice 106 and the configuration download microservice 104). ) can be implemented through remote access protocols (such as AMQP, REST, etc.).
  • remote access protocols such as AMQP, REST, etc.
  • a microservice will have information interaction with one or more other microservices.
  • the analysis microservice 108 provides algorithmic support for all analysis requirements in the system, so it may have information with each of the other microservices. Interaction relationship.
  • FIG. 2 it is a system architecture diagram of another network operation support system 100 provided by an embodiment of the present application. Different from that shown in FIG. 1, the system provided by this embodiment further includes a micro service configured to further optimize system services.
  • the system further includes a user interface microservice 110, a communication microservice 112, a service operation microservice 114, a data collection aggregation microservice 116, a diagnostic microservice 118, and a fault. Locate the microservice 120.
  • the functions of each microservice will be elaborated below.
  • the user interface microservice 110 is configured to provide a user layer interface in the form of a graphical user interface for the user to access all microservices through the graphical user interface.
  • the configuration data received by the pre-configured microservices 102 may be configuration information input by the user through the graphical user interface.
  • the communication microservices 112 are configured to deliver configuration data and monitor data delivery status.
  • the communication microservice 112 can be, but is not limited to, an ONOS or OpenDayLight module.
  • the network management microservices 106, the configuration download microservices 104, and the communication microservices 112 exchange information through a message queue 107 (such as RabbitMQ). Two possible interaction processes will be exemplified below.
  • the configuration download is performed.
  • the microservice 104 responds to the request, and after acquiring the corresponding configuration data from the configuration database 103, sends the acquired configuration data to the communication microservice 112.
  • the communication microservice 112 After receiving the configuration data, the communication microservice 112 sends the configuration data to the network device.
  • the communication microservice 112 detects that the configuration data fails to be sent to the network device through the network configuration protocol (Netconf protocol)
  • the communication microservice 112 sends the detailed information of the configuration data failure to the message queue. 107.
  • the received message failure information is sent by the message queue 107 to the configuration download microservice 104, which is recorded by the configuration download microservice 104 in the data table of the configuration database 103.
  • the role of the message queue 107 is introduced to achieve decoupling and peak clipping between microservices.
  • the one-to-many communication can be completed through the notification mechanism of the message queue 107, and the pressure on the system caused by high concurrent jitter can be alleviated.
  • the service operation microservices 114 are configured to perform operation management and provide service support for services of the network operation support system 100, such as service registration, activation, billing, ranking, and the like.
  • the operational data of the business operations microservice 114 is stored in the operational relationship database 109.
  • the primary database 101 is connected to the operational relationship database 109 to synchronously store operational data of the service operation microservice 114.
  • the data collection aggregation microservice 116 is configured to collect log and statistics information from the network device and each microservice, and save the collected information to a NoSQL database 111 (such as a Cassandra database).
  • NoSQL Database 111 can efficiently store data in a cloud environment with excellent scalability and availability.
  • the network management microservice 106 may be connected to the NoSQL database 111 to be stored according to the The stored data is analyzed to better monitor and manage network devices.
  • the diagnostic microservice 118 is configured to perform real-time diagnosis of the fault of the network operation support system 100 based on data stored in the NoSQL database 111 or in the primary database 101, in cooperation with the analysis microservice 108. Find out the cause of the failure and related information.
  • the fault location microservice 120 is configured to exclude faults in real time based on the diagnostic results of the diagnostic microservice 118.
  • the fault location microservice 120 provides a repair solution for the diagnosed fault and performs troubleshooting according to the repair scheme to restore the system to a normal working state with minimal cost.
  • the network operation support system 100 may further include a service component of a third-party application to optimize management of the network according to data fed back by the third-party application.
  • the network operations support system 100 may also include only portions of the optional microservices described above.
  • the system includes only the communication microservices 112 and the service operations microservices 114 in addition to the basic microservices described above.
  • the system includes only the data collection aggregation microservice 116, the diagnostic microservice 118, and the fault location microservice 120 in addition to the basic microservices described above.
  • the Mesos and Marathon frameworks may be adopted. This framework fully automates and integrates agile processes, and developers can be responsible for the development of microservices and their containers, as well as subsequent operational support and lifecycle management.
  • various service functions of the network operation support system 100 are modularized by implementing the functions of the network operation support system by relatively independent micro-services implemented by independent containers.
  • the modification or extension of various functions in the network operation support system 100 provided by this embodiment is performed for the corresponding micro service function module, as compared with the manner in which the function of the network operation support system is implemented by a complete NMS server in the prior art.
  • the network operation support system 100 is made to have very high scalability and availability.
  • the embodiment further provides a network device management method applied to the network operation support system 100, and the network device management method includes the following steps.
  • Step S110 Receive configuration data input by the user layer interface by pre-configuring the microservice, and store the configuration data in the configuration database.
  • Step S120 After the configuration data is obtained from the configuration database, the configuration micro-service is delivered to the network device.
  • the configuration database includes a data table configured to record configuration data that has been updated by the pre-configured microservice.
  • the configuration download microservice performs update detection on the data table according to a predetermined schedule. And when it is found that there is configuration data that has been updated, the configuration download micro service obtains All configuration data that has been updated is currently delivered to the network device.
  • Step S130 Perform monitoring and management on the running status and configuration data of the network device by using the network management micro service, and generate an analysis report according to the data acquired in the monitoring management process;
  • the network operation support system further includes a communication micro service, and the network management micro service, the configuration download micro service, and the communication micro service exchange information through the message queue.
  • the network management microservice sends the configuration download or upgrade request to the configuration download microservice via the message queue. After the configuration download micro-service obtains the corresponding configuration data from the configuration database according to the configuration download or upgrade request, the configuration data is sent to the communication micro service. After receiving the configuration data, the communication micro-service sends the configuration data to the network device.
  • Step S140 providing algorithm support for analyzing all the analysis requirements of the network operation support system by analyzing the micro service.
  • Step S150 synchronously store the running data of each micro service and the data model between the running data of different micro services through the primary database to perform unified maintenance of the data.
  • the method may further include step S160.
  • Step S160 Perform operation management on the service of the network operation support system by using the service operation micro service, where the operation data of the service operation micro service is stored in an operation relationship database, and the main database is connected with the operation relationship database to The operational data of the service operation microservice is synchronously stored.
  • the method may further include step S170.
  • Step S170 collecting log and statistical information from the network device and each micro service by using the data collection aggregation micro service, and saving the collected information to the NoSQL database;
  • the fault of the network operation support system is diagnosed in real time by the diagnostic microservice in cooperation with the analysis microservice based on the data stored in the NoSQL database or in the primary database.
  • the method may further include step S180.
  • Step S180 the fault is randomly excluded according to the diagnosis result of the diagnostic microservice by the fault location microservice.
  • the method may further include step S190.
  • Step S190 providing a user layer interface in the form of a graphical user interface through the user interface microservice for the user to access all microservices through the graphical user interface.
  • the network operation support system 100 and the network device management method deployed at the cloud server level have good scalability and availability, and support automation and orchestration in a cloud environment.
  • the network operation support system 100 based on the micro service structure can implement independent and real-time deployment of the micro service, thereby effectively improving the overall deployment efficiency of the system.
  • the technical solution of the present application which is essential to the prior art or part of the technical solution, may be embodied in the form of a software product stored in a storage medium, including a number of instructions for making A computer device (which may be a personal computer, a server, or a network device, etc.) implements all or part of the steps of the microservices described in various embodiments of the present application.
  • a computer device which may be a personal computer, a server, or a network device, etc.
  • the foregoing storage medium includes various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read only memory, a random access memory, a magnetic disk, or an optical disk.
  • the modification or extension of various functions in the network operation support system provided by this embodiment is performed for the corresponding micro service function module, as compared with the manner in which the function of the network operation support system is implemented by a complete NMS server in the prior art.
  • the network operation support system deployed at the cloud server level provided by this embodiment has good scalability and availability, and supports automation and orchestration in a cloud environment.
  • each micro service has an independent running process, the network operation support system based on the micro service structure can realize independent and real-time deployment of the micro service, thereby effectively improving the overall deployment efficiency of the system.

Abstract

本申请实施例提供一种网络运营支撑系统及网络设备管理方法，属于通信技术领域。该系统采用基于容器实现的微服务架构，系统本身具有良好的可扩展性和可用性，支持云环境中的自动化和编排。此外，该系统中还利用主数据库对各个微服务的运行数据进行同步存储，进行数据的统一维护，提高系统的分析效率。

Description

一种网络运营支撑系统及网络设备管理方法
相关申请的交叉引用
本申请要求于2016年12月22日提交中国专利局的申请号为2016112035890、名称为“一种网络运营支撑系统”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域，具体而言，涉及一种网络运营支撑系统及网络设备管理方法。
背景技术
传统的WI-FI网络运营支撑系统运行于网管中心的服务器上，其系统架构至今仍沿用传统的客户端-服务器结构。由于部署在服务器级别，所以依赖于NMS(Network Management System，网络管理系统)部署软件，而且系统本身没有编排。
近几年，随着云技术的兴起和广泛应用，由于其具备节省成本、可扩展性及可用性好、易于编排和实施等特点，使得私有云和公有云成为网络运营支撑系统更好的选择，并在云环境中进化出新的服务。但是，现有的基于云的WI-FI网络运营支撑系统都是基于虚拟服务器进行部署的，依赖于IaaS(Infrastructure as a Service，基础设施即服务)模式的云部署软件。由于部署在虚拟机级别，所以运营支撑系统的功能编排依赖于NMS服务器，而且系统本身难以扩展，可用性不佳。
发明内容
有鉴于此，本申请的目的在于提供一种网络运营支撑系统，以改善上述问题中的至少一个。
本申请较佳实施例提供一种网络运营支撑系统，该系统包括：预配置微服务，配置成接收由用户层接口输入的配置数据，并将所述配置数据存储于配置数据库；配置下载微服务，配置成从所述配置数据库中获取配置数据后下发至网络设备；网络管理微服务，配置成对网络设备进行运行状态及配置数据的监控管理，并根据在监控管理过程中获取的数据生成分析报表；分析微服务，配置成为该网络运营支撑系统的所有分析需求提供算法支持；以及主数据库，配置成同步存储各微服务的运行数据以及不同微服务的运行数据之间的数据模型，以进行数据的统一维护。
可选地，所述主数据库为采用图结构建立不同微服务的运行数据之间的数据模型的图形数据库。
可选地，该网络运营支撑系统中的每个微服务基于独立的容器实现，各个微服务的运 行数据以数据库存储、文件存储及写入内存或缓存三种数据存储模式中的至少一种模式进行存储。
可选地，该系统还包括通信微服务，其中：所述网络管理微服务、配置下载微服务及通信微服务之间通过消息队列进行信息交互，其中，所述网络管理微服务对网络设备进行配置数据的监控管理的过程包括：
所述网络管理微服务通过所述消息队列将所述配置下载或升级请求发送至所述配置下载微服务；所述配置下载微服务根据所述配置下载或升级请求从所述配置数据库中获取到相应的配置数据后，将获取到的配置数据发送至所述通信微服务；所述通信微服务接收到所述配置数据后，再将该配置数据发送至所述网络设备。
可选地，该系统还包括：业务运营微服务，配置成对所述网络运营支撑系统的业务进行运营管理，该业务运营微服务的运行数据存储于运营关系数据库中，所述主数据库与该运营关系数据库连接，以对所述业务运营微服务的运行数据进行同步存储。
可选地，该系统还包括：数据收集聚合微服务，配置成从所述网络设备及各微服务中收集日志和统计信息，并将收集到的信息保存到NoSQL数据库中；诊断微服务，配置成在所述分析微服务的配合下，基于保存到所述NoSQL数据库中或所述主数据库中的数据对该网络运营支撑系统的故障进行实时诊断。
可选地，该系统还包括：故障定位微服务，配置成根据所述诊断微服务的诊断结果对故障进行实时排除。
本申请较佳实施例还提供一种网络设备管理方法，应用于网络运营支撑系统，所述网络运营支撑系统包括多个基于独立的容器实现的微服务；所述方法包括：
通过预配置微服务接收由用户层接口输入的配置数据，并将所述配置数据存储于配置数据库；
通过配置下载微服务从所述配置数据库中获取配置数据后下发至网络设备；
通过网络管理微服务对所述网络设备进行运行状态及配置数据的监控管理，并根据在监控管理过程中获取的数据生成分析报表；
通过分析微服务为该网络运营支撑系统的所有分析需求提供算法支持；及
通过主数据库同步存储各微服务的运行数据以及不同微服务的运行数据之间的数据模型，以进行数据的统一维护。
可选地，所述配置数据库中包括有配置成记载已被所述预配置微服务更新的配置数据的数据表；所述通过配置下载微服务从所述配置数据库中获取配置数据后下发至网络设备的步骤，包括：
所述配置下载微服务按照预定的时间表对所述数据表进行更新检测；
当发现存在已被更新的配置数据时，所述配置下载微服务则获取当前所有已被更新的配置数据并下发至所述网络设备。
可选地，所述网络运营支撑系统还包括通信微服务，所述网络管理微服务、配置下载微服务及通信微服务之间通过消息队列进行信息交互；所述通过网络管理微服务对所述网络设备进行配置数据的监控管理的步骤，包括：
所述网络管理微服务通过所述消息队列将所述配置下载或升级请求发送至所述配置下载微服务；
所述配置下载微服务根据所述配置下载或升级请求从所述配置数据库中获取到相应的配置数据后，将获取到的配置数据发送至所述通信微服务；
所述通信微服务接收到所述配置数据后，再将该配置数据发送至所述网络设备。
可选地，该方法还包括：
通过业务运营微服务对所述网络运营支撑系统的业务进行运营管理，该业务运营微服务的运行数据存储于运营关系数据库中，所述主数据库与该运营关系数据库连接，以对所述业务运营微服务的运行数据进行同步存储。
可选地，该方法还包括：
通过数据收集聚合微服务从所述网络设备及各微服务中收集日志和统计信息，并将收集到的信息保存到NoSQL数据库中；
通过诊断微服务在所述分析微服务的配合下，基于保存到所述NoSQL数据库中或所述主数据库中的数据对该网络运营支撑系统的故障进行实时诊断。
可选地，该方法还包括：
通过故障定位微服务根据所述诊断微服务的诊断结果对故障进行实时排除。
可选地，该方法还包括：
通过用户界面微服务提供图形用户界面形式的用户层接口，以供用户通过该图形用户界面访问所有微服务。
本申请实施例提供的应用于WI-FI网络的运营支撑系统采用基于容器实现的微服务架构，系统本身具有良好的可扩展性和可用性，无需依赖编排软件，支持云环境中的自动化和编排，更易实现组件和服务，以及在云环境中进一步演进新的服务。此外，该系统中还采用主数据库将各个微服务的运行数据链接在一起，进行统一的数据维护，提高系统的分析效率。
附图说明
为了更清楚地说明本申请实施例的技术方案，下面将对实施例中所需要使用的附图作简单地介绍，应当理解，以下附图仅示出了本申请的某些实施例，因此不应被看作是对范 围的限定，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他相关的附图。
图1为本申请实施例提供的一种基于微服务架构的网络运营支撑系统的系统框架示意图；
图2为本申请实施例提供的另一种基于微服务架构的网络运营支撑系统的系统框架示意图。
图标：100-网络运营支撑系统；102-预配置微服务；104-配置下载微服务；106-网络管理微服务；108-分析微服务；110-用户界面微服务；112-通信微服务；114-业务运营微服务；116-数据收集聚合微服务；118-诊断微服务；120-故障定位微服务；101-主数据库；103-配置数据库；105-网管关系数据库；107-消息队列；109-运营关系数据库；111-NoSQL数据库。
具体实施方式
为使本申请实施例的目的、技术方案和优点更加清楚，下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例是本申请一部分实施例，而不是全部的实施例。通常在此处附图中描述和示出的本申请实施例的组件可以以各种不同的配置来布置和设计。
因此，以下对在附图中提供的本申请的实施例的详细描述并非旨在限制要求保护的本申请的范围，而是仅仅表示本申请的选定实施例。基于本申请中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都属于本申请保护的范围。应注意到：相似的标号和字母在下面的附图中表示类似项，因此，一旦某一项在一个附图中被定义，则在随后的附图中不需要对其进行进一步定义和解释。
微服务架构(Microservices Architecture)是一种架构风格和设计模式，其开发方式是将应用分解为一组可独立部署、小型化、模块化的微服务，每个微服务运行于独立的进程中，微服务之间边界清晰，采用轻量级通信机制进行交互，通过版本化的API(Application Programming Interface，应用程序编程接口)和数据存储来服务于特定的商业目标。
本申请实施例中，将所述微服务架构应用于网络运营支撑系统的开发中，将原网络管理及运维服务按照功能边界分解成一组可在云服务器级别进行独立部署、编译和扩展的微服务模块。与现有技术中的部署于物理服务器级别或虚拟主机级别的网络运营支撑系统相比，具有更好的可扩展性和可用性，支持云环境下的自动化和编排，无需依赖编排软件。此外，本实施例提供的系统中，基于主数据库进行的统一数据维护，解决了现有微服务结构中各微服务的运行数据难以建立数据链接的难题，更进一步提升了系统的分析效率，从而使对系统的实时诊断和故障排除成为可能。
需要强调的是，本申请实施例提供的网络运营支撑系统可以应用于WI-FI网络系统的 管理和运维，但并不限制于此。
下面将以WI-FI网络为例，并结合附图，对本申请实施例提供的所述网络运营支撑系统的实现原理进行详细的阐述。所应理解的是，下述实施例提供的微服务架构仅是示例性的，其中包含的各基础微服务及可选微服务在其他实施例中可以进行相互变换或者根据实际需求进行另外的服务设计、功能边界划分等。所述基础微服务是指网络运营支撑系统中核心(必要)的微服务，所述可选微服务可以是指网络运营支撑系统中配置成进一步优化系统的微服务。
如图1所示，作为一种实施方式，本实施例提供一种仅包含基础微服务及主数据库101的网络运营支撑系统100的系统架构图。其中，所述基础微服务包括预配置微服务102、配置下载微服务104、网络管理微服务106以及分析微服务108。本实施例中，该网络运营支撑系统100的每个微服务均是基于独立的容器(如Docker容器)实现，每个所述微服务可以作为所述网络运营支撑系统100可以独立部署运行的功能模块。下面对图1所示的各微服务的功能进行描述。
所述预配置微服务102配置成接收由用户层接口输入的配置数据，并将所述配置数据存储于配置数据库103中。也就是说，用户通过所述用户层接口输入的配置数据将最终交付至所述预配置微服务102，由该预配置微服务102进行持久化。当然，在其他实施例中，所述预配置微服务102还可以配置成检查配置的有效性。此外，所述配置数据也可以直接存储于主数据库101中，而无需另设配置数据库103。
所述配置下载微服务104配置成从所述配置数据库103中获取配置数据后下发至网络设备。所述网络设备可以是无线控制器以及与所述无线控制器通信连接的无线接入点，但并不限制于此。所述无线控制器通过CAPWAP(Control And Provisioning of Wireless Access Points Protocol Specification，无线接入点的控制和配置协议)隧道对无线接入点进行管理，当所述无线控制器接收到配置下载微服务104下发的配置数据后，再通过所述CAPWAP隧道将配置数据发送给无线接入点。
所述网络管理微服务106配置成对所述网络设备进行运行状态及配置数据的监控管理，并根据在监控管理过程中获取的数据生成分析报表。应注意的是，在其他实施例中，所述网络管理微服务106还可以具备其他功能，比如已有网管服务中的系统管理、拓扑管理功能等。
所述分析微服务108配置成为该网络运营支撑系统100的所有分析需求提供算法支持，如为所述网络管理微服务106在统计报表时提供相应的分析算法。
所述主数据库101配置成同步存储各微服务的运行数据以及不同微服务的运行数据之间的数据模型，以进行数据的统一维护，进而提升系统的分析效率。
在本实施例中，通过不同的微服务实现或者维护所述网络运营支撑系统100的部分功能，而不同的微服务可能采用不同类型的数据库(如关系型数据库或非关系型数据库)维护自身的数据。所以，为了实现不同微服务之间的数据的同步管理，通过所述主数据库101对不同微服务进行统一的存储、转换或同步。
所述主数据库101采用图形数据库实现。所述图形数据库通过图结构建立不同微服务的运行数据之间的数据模型，以满足树形存储结构的需求。
需要说明的是，各微服务的运行数据可以以数据库存储、文件存储及写入内存或缓存三种数据存储模式中的至少一种模式进行存储。也就是说，本实施例提供的网络运营支撑系统100中，允许微服务的运行数据的存储模式与主数据库101不同。例如，所述预配置微服务102将配置数据存储于配置数据库103中，所述网络管理微服务106可以将运行数据中的适于结构化存储的数据(如设备仓库等)存储于网管关系数据库105中，将其他运行数据写入缓存或内存。
关于所述配置下载微服务104，更为具体的是，其进行配置数据下发通常包括如下两种情形：
其一是，响应所述网络管理微服务106发起的配置下载或升级请求，从所述配置数据库103中获取与所述请求相应的配置数据后，下发至所述网络设备。
其二是，主动从所述配置数据库103中获取配置数据后下发至网络设备。所述配置数据库103中存储有配置成记载已被所述预配置微服务102更新的配置数据的数据表。所述配置下载微服务104按照预定的时间表对所述数据表进行更新检测，一旦发现存在已被更新的配置数据，所述配置下载微服务104则获取当前所有已被更新的配置数据并下发至所述网络设备。
本实施例提供的网络运营支撑系统100中各微服务以服务组件形式存在。在一些实施例中，部分微服务可以进一步根据功能边界划分为多个可部署的子服务组件。在另外一些实施例中，该网络运营支撑系统100中的某两个或两个以上的微服务还可以合并为一个微服务，例如，作为一种实施方式，所述预配置微服务102与所述配置下载微服务104可以合并为一个配置微服务，该配置微服务可以统筹负责系统的数据配置操作。
本实施例中，各微服务可通过所述用户层接口被访问。此外，应强调的是，虽然图1中未示出各微服务间的信息交互关系，但不同微服务之间的相互访问(比如网络管理微服务106与配置下载微服务104之间的信息交互)可以通过远程访问协议(如AMQP、REST等)实现。而且通常一个微服务会与其他一个甚至多个微服务之间存在信息交互，比如分析微服务108是为系统中的所有分析需求提供算法支持，所以其可能与其他每个微服务都存在着信息交互关系。
如图2所示，是本申请实施例提供的另一种网络运营支撑系统100的系统架构图。与图1所示的不同的是，本实施例提供的系统还包括配置成进一步优化系统服务的微服务。
具体地，除图1中所示的各基础微服务外，该系统还包括用户界面微服务110、通信微服务112、业务运营微服务114、数据收集聚合微服务116、诊断微服务118以及故障定位微服务120。下面将对各微服务的功能进行详细阐述。
所述用户界面微服务110配置成提供图形用户界面形式的用户层接口，以供用户通过该图形用户界面访问所有微服务。本实施例中，所述预配置微服务102接收到的配置数据可以是用户通过所述图形用户界面输入的配置信息。
所述通信微服务112配置成下发配置数据以及监测数据下发状态。该通信微服务112可以是但不限于，ONOS或OpenDayLight模块。本实施例中，所述网络管理微服务106、配置下载微服务104及通信微服务112之间通过消息队列107(如RabbitMQ)进行信息交互。下面将示例性的举出两种可能的交互过程。
其一，所述网络管理微服务106对网络设备进行配置数据的监控管理的过程中，通过所述消息队列107将配置下载或升级请求发送至所述配置下载微服务104后，所述配置下载微服务104响应该请求，从所述配置数据库103中获取到相应的配置数据后，将获取到的配置数据发送至所述通信微服务112。所述通信微服务112接收到所述配置数据后，再将该配置数据发送至所述网络设备。
其二，当所述通信微服务112监测到通过网络配置协议(Netconf协议)向所述网络设备发送配置数据失败时，该通信微服务112将把配置数据下发失败的详细信息发送至消息队列107，再由所述消息队列107将接收到的下发失败的信息发送至配置下载微服务104，由所述配置下载微服务104将其记录于配置数据库103的数据表中。
本实施例中，引入消息队列107的作用在于实现微服务间的解耦和削峰。既可以通过消息队列107的通知机制完成一对多的通信，又能够减轻高并发抖动时对系统造成的压力。
所述业务运营微服务114配置成对所述网络运营支撑系统100的业务进行运营管理及提供服务支持，例如服务注册、激活、计费、排名等。该业务运营微服务114的运行数据存储于运营关系数据库109中。所述主数据库101与该运营关系数据库109连接，以对所述业务运营微服务114的运行数据进行同步存储。
所述数据收集聚合微服务116配置成从所述网络设备及各微服务中收集日志和统计信息，并将收集到的信息保存到NoSQL数据库111(如Cassandra数据库)中。NoSQL数据库111可以在云环境中高效地存储数据，具有出色的可扩展性和可用性。然而，由于NoSQL数据库111的无模式特点，存储于NoSQL数据库111中的数据之间的关系通常很难被描述。本实施例中，所述网络管理微服务106可以与所述NoSQL数据库111连接，以根据其中存 储的数据进行分析，对网络设备进行更好的监控管理。
所述诊断微服务118配置成在所述分析微服务108的配合下，基于保存到所述NoSQL数据库111中或所述主数据库101中的数据对该网络运营支撑系统100的故障进行实时诊断，查找出故障原因及相关信息。
所述故障定位微服务120配置成根据所述诊断微服务118的诊断结果对故障进行实时排除。该故障定位微服务120为诊断出的故障提供修复方案，并根据所述修复方案进行故障排除，使系统以最小的成本恢复到正常工作状态。
所应说明的是，在其他实施例中，所述网络运营支撑系统100还可以包括第三方应用的服务组件，以根据第三方应用反馈的数据对网络进行优化管理。
此外，在一些实施例中，所述网络运营支撑系统100还可以仅包括上述可选微服务中的部分。比如，在一实施例中，该系统除上述基础微服务外，仅包括所述通信微服务112和业务运营微服务114。在另一实施例中，该系统除上述基础微服务外，仅包括所述数据收集聚合微服务116、诊断微服务118和故障定位微服务120。
另外，与图1类似地，图2中部分微服务之间的信息交互关系未示出，但应理解，当两个不同微服务之间需要进行访问时，可以通过消息队列107实现通信。
在本实施例提供的网络运营支撑系统100的实际开发过程中，可以采用Mesos和Marathon框架。这种框架完全自动化和集成敏捷过程，开发人员可以负责微服务及其容器的开发，以及后续运营支持和生命周期管理。
基于上述设计，在本实施例中，通过由相对独立的基于独立的容器实现的微服务实现网络运营支撑系统的功能，使所述网络运营支撑系统100的各种服务功能模块化。相比于现有技术中依赖一个完整NMS服务器实现网络运营支撑系统功能的方式，本实施例提供的网络运营支撑系统100中各种功能的修改或者扩展都是针对相应微服务功能模块进行的，使得所述网络运营支撑系统100具有非常高的扩展性和可用性。
本实施例还提供一种应用于上述网络运营支撑系统100的网络设备管理方法，所述网络设备管理方法包括以下步骤。
步骤S110，通过预配置微服务接收由用户层接口输入的配置数据，并将所述配置数据存储于配置数据库。
步骤S120，通过配置下载微服务从所述配置数据库中获取配置数据后下发至网络设备。
进一步地，在本实施例中，所述配置数据库中包括有配置成记载已被所述预配置微服务更新的配置数据的数据表。所述配置下载微服务按照预定的时间表对所述数据表进行更新检测。并在发现存在已被更新的配置数据时，所述配置下载微服务则获取 当前所有已被更新的配置数据并下发至所述网络设备。
步骤S130，通过网络管理微服务对所述网络设备进行运行状态及配置数据的监控管理，并根据在监控管理过程中获取的数据生成分析报表；
进一步地，在本实施例中，所述网络运营支撑系统还包括通信微服务，所述网络管理微服务、配置下载微服务及通信微服务之间通过消息队列进行信息交互。所述网络管理微服务通过所述消息队列将所述配置下载或升级请求发送至所述配置下载微服务。所述配置下载微服务根据所述配置下载或升级请求从所述配置数据库中获取到相应的配置数据后，将获取到的配置数据发送至所述通信微服务。所述通信微服务接收到所述配置数据后，再将该配置数据发送至所述网络设备。
步骤S140，通过分析微服务为该网络运营支撑系统的所有分析需求提供算法支持。
步骤S150，通过主数据库同步存储各微服务的运行数据以及不同微服务的运行数据之间的数据模型，以进行数据的统一维护。
进一步地，在本实施例中，该方法还可以包括步骤S160。
步骤S160，通过业务运营微服务对所述网络运营支撑系统的业务进行运营管理，该业务运营微服务的运行数据存储于运营关系数据库中，所述主数据库与该运营关系数据库连接，以对所述业务运营微服务的运行数据进行同步存储。
进一步地，在本实施例中，该方法还可以包括步骤S170。
步骤S170，通过数据收集聚合微服务从所述网络设备及各微服务中收集日志和统计信息，并将收集到的信息保存到NoSQL数据库中；
通过诊断微服务在所述分析微服务的配合下，基于保存到所述NoSQL数据库中或所述主数据库中的数据对该网络运营支撑系统的故障进行实时诊断。
进一步地，在本实施例中，该方法还可以包括步骤S180。
步骤S180，通过故障定位微服务根据所述诊断微服务的诊断结果对故障进行实时排除。
进一步地，在本实施例中，该方法还可以包括步骤S190。
步骤S190，通过用户界面微服务提供图形用户界面形式的用户层接口，以供用户通过该图形用户界面访问所有微服务。
综上所述，本申请实施例提供的部署于云服务器级别的网络运营支撑系统100及网络设备管理方法，具有良好的可扩展性和可用性，支持云环境下的自动化和编排。另外，由于各微服务具备独立的运行进程，所以基于微服务结构的网络运营支撑系统100可以实现微服务的独立和实时部署，有效提升了系统整体的部署效率。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统也可以通过其它的方式 实现。以上所描述的实施例仅仅是示意性的。
本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)实现本申请各个实施例所述微服务的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器、随机存取存储器、磁碟或者光盘等各种可以存储程序代码的介质。
需要说明的是，在本文中，诸如第一和第二等之类的关系术语仅仅用来将一个实体或者操作与另一个实体或操作区分开来，而不一定要求或者暗示这些实体或操作之间存在任何这种实际的关系或者顺序。而且，术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、物品或者设备不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、物品或者设备所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括所述要素的过程、方法、物品或者设备中还存在另外的相同要素。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准。
工业实用性
相比于现有技术中依赖一个完整NMS服务器实现网络运营支撑系统功能的方式，本实施例提供的网络运营支撑系统中各种功能的修改或者扩展都是针对相应微服务功能模块进行的，使得本实施例提供的部署于云服务器级别的网络运营支撑系统具有良好的可扩展性和可用性，支持云环境下的自动化和编排。另外，由于各微服务具备独立的运行进程，所以基于微服务结构的网络运营支撑系统可以实现微服务的独立和实时部署，有效提升了系统整体的部署效率。

Claims (17)

  1. 一种网络运营支撑系统，其特征在于，该系统包括：
    预配置微服务，配置成接收由用户层接口输入的配置数据，并将所述配置数据存储于配置数据库；
    配置下载微服务，配置成从所述配置数据库中获取配置数据后下发至网络设备；
    网络管理微服务，配置成对所述网络设备进行运行状态及配置数据的监控管理，并根据在监控管理过程中获取的数据生成分析报表；
    分析微服务，配置成为该网络运营支撑系统的所有分析需求提供算法支持；及
    主数据库，配置成同步存储各微服务的运行数据以及不同微服务的运行数据之间的数据模型，以进行数据的统一维护。
  2. 根据权利要求1所述的系统，其特征在于，所述主数据库为采用图结构建立不同微服务的运行数据之间的数据模型的图形数据库。
  3. 根据权利要求2所述的系统，其特征在于，该网络运营支撑系统中的每个微服务基于独立的容器实现，各个微服务的运行数据以数据库存储、文件存储及写入内存或缓存三种数据存储模式中的至少一种模式进行存储。
  4. 根据权利要求1所述的系统，其特征在于，所述配置数据库中包括有配置成记载已被所述预配置微服务更新的配置数据的数据表，所述配置下载微服务从所述配置数据库中获取配置数据后下发至所述网络设备的过程包括：
    所述配置下载微服务按照预定的时间表对所述数据表进行更新检测；
    当发现存在已被更新的配置数据时，所述配置下载微服务则获取当前所有已被更新的配置数据并下发至所述网络设备。
  5. 根据权利要求1所述的系统，其特征在于，该系统还包括通信微服务，其中：
    所述网络管理微服务、配置下载微服务及通信微服务之间通过消息队列进行信息交互，其中，所述网络管理微服务对网络设备进行配置数据的监控管理的过程包括：
    所述网络管理微服务通过所述消息队列将所述配置下载或升级请求发送至所述配置下载微服务；
    所述配置下载微服务根据所述配置下载或升级请求从所述配置数据库中获取到相应的配置数据后，将获取到的配置数据发送至所述通信微服务；
    所述通信微服务接收到所述配置数据后，再将该配置数据发送至所述网络设备。
  6. 根据权利要求1所述的系统，其特征在于，该系统还包括：
    业务运营微服务，配置成对所述网络运营支撑系统的业务进行运营管理，该业务 运营微服务的运行数据存储于运营关系数据库中，所述主数据库与该运营关系数据库连接，以对所述业务运营微服务的运行数据进行同步存储。
  7. 根据权利要求6所述的系统，其特征在于，该系统还包括：
    数据收集聚合微服务，配置成从所述网络设备及各微服务中收集日志和统计信息，并将收集到的信息保存到NoSQL数据库中；
    诊断微服务，配置成在所述分析微服务的配合下，基于保存到所述NoSQL数据库中或所述主数据库中的数据对该网络运营支撑系统的故障进行实时诊断。
  8. 根据权利要求7所述的系统，其特征在于，该系统还包括：
    故障定位微服务，配置成根据所述诊断微服务的诊断结果对故障进行实时排除。
  9. 根据权利要求1所述的系统，其特征在于，该系统还包括：
    用户界面微服务，配置成提供图形用户界面形式的用户层接口，以供用户通过该图形用户界面访问所有微服务。
  10. 根据权利要求1所述的系统，其特征在于，所述网络设备包括无线控制器及与所述无线控制器通信连接的无线接入点。
  11. 一种网络设备管理方法，应用于网络运营支撑系统，其特征在于，所述网络运营支撑系统包括多个基于独立的容器实现的微服务；所述方法包括：
    通过预配置微服务接收由用户层接口输入的配置数据，并将所述配置数据存储于配置数据库；
    通过配置下载微服务从所述配置数据库中获取配置数据后下发至网络设备；
    通过网络管理微服务对所述网络设备进行运行状态及配置数据的监控管理，并根据在监控管理过程中获取的数据生成分析报表；
    通过分析微服务为该网络运营支撑系统的所有分析需求提供算法支持；及
    通过主数据库同步存储各微服务的运行数据以及不同微服务的运行数据之间的数据模型，以进行数据的统一维护。
  12. 根据权利要求11所述的方法，其特征在于，所述配置数据库中包括有配置成记载已被所述预配置微服务更新的配置数据的数据表；所述通过配置下载微服务从所述配置数据库中获取配置数据后下发至网络设备的步骤，包括：
    所述配置下载微服务按照预定的时间表对所述数据表进行更新检测；
    当发现存在已被更新的配置数据时，所述配置下载微服务则获取当前所有已被更新的配置数据并下发至所述网络设备。
  13. 根据权利要求11所述的方法，其特征在于，所述网络运营支撑系统还包括通信微服务，所述网络管理微服务、配置下载微服务及通信微服务之间通过消息队列进行 信息交互；所述通过网络管理微服务对所述网络设备进行配置数据的监控管理的步骤，包括：
    所述网络管理微服务通过所述消息队列将所述配置下载或升级请求发送至所述配置下载微服务；
    所述配置下载微服务根据所述配置下载或升级请求从所述配置数据库中获取到相应的配置数据后，将获取到的配置数据发送至所述通信微服务；
    所述通信微服务接收到所述配置数据后，再将该配置数据发送至所述网络设备。
  14. 根据权利要求11所述的方法，其特征在于，该方法还包括：
    通过业务运营微服务对所述网络运营支撑系统的业务进行运营管理，该业务运营微服务的运行数据存储于运营关系数据库中，所述主数据库与该运营关系数据库连接，以对所述业务运营微服务的运行数据进行同步存储。
  15. 根据权利要求14所述的方法，其特征在于，该方法还包括：
    通过数据收集聚合微服务从所述网络设备及各微服务中收集日志和统计信息，并将收集到的信息保存到NoSQL数据库中；
    通过诊断微服务在所述分析微服务的配合下，基于保存到所述NoSQL数据库中或所述主数据库中的数据对该网络运营支撑系统的故障进行实时诊断。
  16. 根据权利要求15所述的方法，其特征在于，该方法还包括：
    通过故障定位微服务根据所述诊断微服务的诊断结果对故障进行实时排除。
  17. 根据权利要求11所述的方法，其特征在于，该方法还包括：
    通过用户界面微服务提供图形用户界面形式的用户层接口，以供用户通过该图形用户界面访问所有微服务。
PCT/CN2017/115708 2016-12-22 2017-12-12 一种网络运营支撑系统及网络设备管理方法 WO2018113556A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US16/472,396 US10944628B2 (en) 2016-12-22 2017-12-12 Network operation support system and network device management method

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201611203589.0 2016-12-22
CN201611203589.0A CN106533804A (zh) 2016-12-22 2016-12-22 一种网络运营支撑系统

Publications (1)

Publication Number Publication Date
WO2018113556A1 true WO2018113556A1 (zh) 2018-06-28

Family

ID=58337498

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/115708 WO2018113556A1 (zh) 2016-12-22 2017-12-12 一种网络运营支撑系统及网络设备管理方法

Country Status (3)

Country Link
US (1) US10944628B2 (zh)
CN (1) CN106533804A (zh)
WO (1) WO2018113556A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110096273A (zh) * 2019-05-06 2019-08-06 上海东尚信息科技股份有限公司 生产型软件框架系统及软件访问系统
CN112799803A (zh) * 2021-01-14 2021-05-14 深圳市瞬点科技有限公司 微服务架构运行维护方法、装置、设备及可读存储介质

Families Citing this family (32)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106533804A (zh) * 2016-12-22 2017-03-22 成都西加云杉科技有限公司 一种网络运营支撑系统
CN106936934A (zh) * 2017-04-27 2017-07-07 四川长虹电器股份有限公司 基于模块化服务的开放平台第三方应用接入方法
CN107317881B (zh) * 2017-08-10 2021-04-20 上海庄生机电工程设备有限公司 一种基于微服务架构的ba系统
CN107645508A (zh) * 2017-10-16 2018-01-30 深圳市买买提乐购金融服务有限公司 一种数据处理系统、方法、客户端及服务器
CN107730125B (zh) * 2017-10-20 2021-09-14 南方电网科学研究院有限责任公司 实验室管理系统
CN107734066A (zh) * 2017-11-16 2018-02-23 郑州云海信息技术有限公司 一种数据中心综合管理系统服务治理方法
CN107943958B (zh) * 2017-11-24 2021-05-25 税友软件集团股份有限公司 一种个税主数据共享方法及系统
CN108134696A (zh) * 2017-12-15 2018-06-08 云宏信息科技股份有限公司 一种微服务配置更新方法及装置
CN108153547A (zh) * 2017-12-26 2018-06-12 泰康保险集团股份有限公司 微服务的版本管理方法、装置、介质及电子设备
CN108415994B (zh) * 2018-02-13 2021-03-02 北京天元创新科技有限公司 一种网络管理系统报表生成方法、装置和设备
CN109033435A (zh) * 2018-08-14 2018-12-18 安徽云才信息技术有限公司 一种跨微服务的模糊搜索方法
CN109302314B (zh) * 2018-09-28 2022-04-29 深信服科技股份有限公司 一种被控节点模拟方法及相关装置
CN109618119A (zh) * 2018-10-31 2019-04-12 视联动力信息技术股份有限公司 业务处理方法和装置
US11082287B2 (en) 2019-03-11 2021-08-03 At&T Intellectual Property I, L.P. Data driven systems and methods to isolate network faults
CN110048883B (zh) * 2019-04-03 2022-06-07 国网福建省电力有限公司 一种基于微服务云架构实现综合网络管理的方法
CN110008045B (zh) * 2019-04-12 2021-12-10 深圳乐信软件技术有限公司 微服务的聚合方法、装置、设备及存储介质
US11032396B2 (en) * 2019-05-17 2021-06-08 Citrix Systems, Inc. Systems and methods for managing client requests to access services provided by a data center
CN110324341A (zh) * 2019-07-03 2019-10-11 浪潮软件集团有限公司 一种基于istio的微服务API网关的安全计费方法
CN110943863A (zh) * 2019-11-29 2020-03-31 怀来斯达铭数据有限公司 一种数据中心
CN111193610B (zh) * 2019-11-30 2021-11-26 北京无限自在文化传媒股份有限公司 一种基于物联网的智慧监控数据系统和方法
CN111209126A (zh) * 2020-01-03 2020-05-29 北京明略软件系统有限公司 微服务之间的数据传输方法及装置、电子设备
US11252025B2 (en) * 2020-04-16 2022-02-15 Juniper Networks, Inc. Model driven configuration management for microservices
CN111669401B (zh) * 2020-06-22 2022-05-13 南方电网数字电网研究院有限公司 网络系统的安全防护方法、装置、计算机设备和存储介质
US11824734B2 (en) * 2020-08-24 2023-11-21 HCL America Inc. System providing management of services and a method thereof
JP7480866B2 (ja) 2020-12-18 2024-05-10 日本電信電話株式会社 トラヒック制御装置、トラヒック制御方法、通信システムおよびプログラム
CN113220573A (zh) * 2021-05-12 2021-08-06 北京百度网讯科技有限公司 用于微服务架构的测试方法、装置和电子设备
CN113111374B (zh) * 2021-05-13 2022-09-23 上海交通大学 一种端边云的工业微服务系统、数据交互方法及介质
CN112994958B (zh) 2021-05-17 2021-08-13 新华三技术有限公司 一种网络管理系统、方法、装置及电子设备
US11875156B2 (en) * 2021-09-14 2024-01-16 Open Text Holdings, Inc. System and method for centralized configuration of distributed and heterogeneous applications
CN114201231B (zh) * 2021-11-29 2023-01-03 江苏金农股份有限公司 一种分布式的微服务编排系统及方法
CN114363222A (zh) * 2021-12-17 2022-04-15 中电信数智科技有限公司 一种基于Netconf协议的网络设备巡检方法和系统
CN116611749B (zh) * 2023-02-13 2023-10-20 国家电投集团数字科技有限公司 一种基于微服务架构的电力数据智能录入方法及系统

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104158910A (zh) * 2014-08-29 2014-11-19 金石易诚（北京）科技有限公司 一种云端Web应用自动化部署系统
CN105550130A (zh) * 2015-12-14 2016-05-04 中电科华云信息技术有限公司 基于容器的应用环境动态编排的方法及其应用系统
WO2016195562A1 (en) * 2015-06-03 2016-12-08 Telefonaktiebolaget Lm Ericsson (Publ) Allocating or announcing availability of a software container
CN106533804A (zh) * 2016-12-22 2017-03-22 成都西加云杉科技有限公司 一种网络运营支撑系统

Family Cites Families (20)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103973497A (zh) * 2014-05-23 2014-08-06 浪潮电子信息产业股份有限公司 一种基于高密度微服务器实现多路并发存储的方法和装置
US9749428B2 (en) * 2014-10-21 2017-08-29 Twilio, Inc. System and method for providing a network discovery service platform
US10230571B2 (en) * 2014-10-30 2019-03-12 Equinix, Inc. Microservice-based application development framework
US10291726B2 (en) * 2015-05-12 2019-05-14 Equinix, Inc. Network field unit for a cloud-based services exchange
CN105808414A (zh) * 2016-03-08 2016-07-27 联想(北京)有限公司 一种日志处理方法及日志处理电子设备
US9716617B1 (en) * 2016-06-14 2017-07-25 ShieldX Networks, Inc. Dynamic, load-based, auto-scaling network security microservices architecture
US10515212B1 (en) * 2016-06-22 2019-12-24 Amazon Technologies, Inc. Tracking sensitive data in a distributed computing environment
US10218730B2 (en) * 2016-07-29 2019-02-26 ShieldX Networks, Inc. Systems and methods of stateless processing in a fault-tolerant microservice environment
US10178045B2 (en) * 2016-09-07 2019-01-08 Sap Se Dynamic discovery and management of microservices for multi-cluster computing platforms
US10484243B2 (en) * 2016-09-16 2019-11-19 Oracle International Corporation Application management for a multi-tenant identity cloud service
DE102016124348A1 (de) * 2016-12-14 2018-06-14 Codewrights Gmbh System und Mikroservice zum Überwachen einer Anlage der Prozessautomatisierung
US10657019B1 (en) * 2017-05-30 2020-05-19 EMC IP Holding Company LLC Method and system for multi-node monitoring services
US10581873B2 (en) * 2017-07-11 2020-03-03 Cisco Technology, Inc. Securing micro-services
WO2019020514A1 (en) * 2017-07-28 2019-01-31 Siemens Aktiengesellschaft PERIPHERAL DEVICES AND RELATED NETWORKS USING MICROSERVICES
US10348858B2 (en) * 2017-09-15 2019-07-09 Oracle International Corporation Dynamic message queues for a microservice based cloud service
JP6996271B2 (ja) * 2017-12-13 2022-01-17 富士通株式会社 情報処理装置、情報処理方法、及び情報処理プログラム
US10635572B2 (en) * 2018-05-01 2020-04-28 Hitachi, Ltd. System and method for microservice validator
US11418603B2 (en) * 2018-08-02 2022-08-16 International Business Machines Corporation Dynamic backoff and retry attempts based on incoming request
US10673708B2 (en) * 2018-10-12 2020-06-02 International Business Machines Corporation Auto tuner for cloud micro services embeddings
US10713664B1 (en) * 2019-03-22 2020-07-14 International Business Machines Corporation Automated evaluation and reporting of microservice regulatory compliance

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104158910A (zh) * 2014-08-29 2014-11-19 金石易诚（北京）科技有限公司 一种云端Web应用自动化部署系统
WO2016195562A1 (en) * 2015-06-03 2016-12-08 Telefonaktiebolaget Lm Ericsson (Publ) Allocating or announcing availability of a software container
CN105550130A (zh) * 2015-12-14 2016-05-04 中电科华云信息技术有限公司 基于容器的应用环境动态编排的方法及其应用系统
CN106533804A (zh) * 2016-12-22 2017-03-22 成都西加云杉科技有限公司 一种网络运营支撑系统

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110096273A (zh) * 2019-05-06 2019-08-06 上海东尚信息科技股份有限公司 生产型软件框架系统及软件访问系统
CN112799803A (zh) * 2021-01-14 2021-05-14 深圳市瞬点科技有限公司 微服务架构运行维护方法、装置、设备及可读存储介质
CN112799803B (zh) * 2021-01-14 2023-11-17 深圳市瞬点科技有限公司 微服务架构运行维护方法、装置、设备及可读存储介质

Also Published As

Publication number Publication date
CN106533804A (zh) 2017-03-22
US20190363934A1 (en) 2019-11-28
US10944628B2 (en) 2021-03-09

Similar Documents

Publication Publication Date Title
WO2018113556A1 (zh) 一种网络运营支撑系统及网络设备管理方法
CN104679717B (zh) 集群弹性部署的方法和管理系统
US8825752B1 (en) Systems and methods for providing intelligent automated support capable of self rejuvenation with respect to storage systems
US20170244626A1 (en) Device and settings management platform
WO2017161984A1 (zh) 数据集群的部署方法、装置、系统及计算机存储介质
CN105706469B (zh) 管理机器对机器设备
US11483218B2 (en) Automating 5G slices using real-time analytics
US10198284B2 (en) Ensuring operational integrity and performance of deployed converged infrastructure information handling systems
CN105653425B (zh) 基于复杂事件处理引擎的监控系统
RU2679344C1 (ru) Способ обработки информации об аварийных сигналах, соответствующее устройство и система
WO2021203979A1 (zh) 运维处理方法、装置及计算机设备
CN103812699A (zh) 基于云计算的监控管理系统
CN105592122A (zh) 一种云平台监控方法以及云平台监控系统
US8856174B2 (en) Asset managing apparatus and asset managing method
WO2019041930A1 (zh) 巡检方法、装置、系统、计算机设备和存储介质
CN105447681A (zh) 一种理化检测控制与信息管理系统
CN113742031A (zh) 节点状态信息获取方法、装置、电子设备及可读存储介质
US20150106485A1 (en) System and Method for Facilitating Design Configuration and Management of Data Center
CN110874272A (zh) 资源配置方法及装置、计算机可读存储介质、电子设备
WO2023246347A1 (zh) 数字孪生处理方法及数字孪生系统
KR101357135B1 (ko) 로그 정보 수집 장치
CN113778486A (zh) 一种代码流水线的容器化处理方法、装置、介质及设备
US11531612B2 (en) Methods for providing an enterprise synthetic monitoring framework
CN104391762A (zh) 一机实现多机多应用的备用方法
CN104539449B (zh) 一种故障信息处理方法与相关装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 17884796

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 17884796

Country of ref document: EP

Kind code of ref document: A1