WO2022242024A1 - 一种网络管理系统、方法、装置及电子设备 - Google Patents

一种网络管理系统、方法、装置及电子设备 Download PDF

Info

Publication number
WO2022242024A1
WO2022242024A1 PCT/CN2021/124558 CN2021124558W WO2022242024A1 WO 2022242024 A1 WO2022242024 A1 WO 2022242024A1 CN 2021124558 W CN2021124558 W CN 2021124558W WO 2022242024 A1 WO2022242024 A1 WO 2022242024A1
Authority
WO
WIPO (PCT)
Prior art keywords
network
microservice
target
management
data
Prior art date
Application number
PCT/CN2021/124558
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 EP21940470.4A priority Critical patent/EP4161015A4/en
Priority to US18/003,936 priority patent/US20240297828A1/en
Priority to JP2022577541A priority patent/JP7453426B2/ja
Publication of WO2022242024A1 publication Critical patent/WO2022242024A1/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/20—Network management software packages
    • 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/14—Network analysis or design
    • H04L41/145—Network analysis or design involving simulating, designing, planning or modelling of a network
    • 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/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/0866—Checking the configuration
    • H04L41/0869—Validating the configuration within one network element
    • 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/14—Network analysis or design
    • 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/22—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks comprising specially adapted graphical user interfaces [GUI]
    • 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
    • H04L41/5041—Network service management, e.g. ensuring proper service fulfilment according to agreements characterised by the time relationship between creation and deployment of a service
    • H04L41/5051—Service on demand, e.g. definition and deployment of services in real time
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
    • H04L63/0876—Network architectures or network communication protocols for network security for authentication of entities based on the identity of the terminal or configuration, e.g. MAC address, hardware or software configuration or device fingerprint

Definitions

  • the present application relates to the technical field of communications, and in particular to a network management system, method, device and electronic equipment.
  • the purpose of the embodiments of the present application is to provide a network management system, method, device and electronic equipment, so as to realize simplified network management operations.
  • the specific technical scheme is as follows:
  • a network management system includes a support unit, a data management unit, a business service unit, and a display unit;
  • the business service unit includes multiple groups of microservice subunits
  • Each of the microservice subunits is used to provide a microservice, and the microservices provided by each group of the microservice subunits are jointly used to implement a management function;
  • the support unit installs and deploys all the micro-service sub-units through the same installation and deployment logic, so as to provide a unified deployment platform for all the micro-service sub-units;
  • the support unit performs operation management on all the micro-service sub-units through the same operation management logic, so as to provide a unified operation platform for all the micro-service sub-units;
  • the data management unit stores the data of all the microservice subunits through the same data storage logic, so as to provide unified data storage services for all the microservice subunits;
  • the data management unit encapsulates the access logic of each type of data into the same access logic, and makes all the microservice subunits access each type of data through the same access logic;
  • the display unit provides a unified portal for all the micro-service sub-units by displaying the main interface and setting an interface for jumping to the functional interface of each of the micro-service sub-units in the main interface Framework services.
  • the display unit is further configured to determine the menu item corresponding to the access right of the account logged into the network management system according to the pre-stored correspondence between the access right and the menu item; And display the determined menu items in the main interface.
  • the display unit is further configured to, according to the pre-stored correspondence between access rights and interface elements, determine in the main interface the corresponding access rights of the account that logs into the network management system interface elements; reset the attributes of the determined interface elements in the main interface; and display the reset main interface, wherein the interface elements include menu items and/or widgets.
  • the support unit is also used to perform unified message modeling and encapsulation on the protocols used in all microservices provided by all microservice subunits, so as to implement The service subunit provides unified protocol channel services.
  • the support unit is further configured to obtain logs generated by all microservices provided by all microservice subunits, and perform log management on all obtained logs through the same log management logic , so as to provide a unified log service for all the microservice subunits.
  • the data management unit is further configured to configure a universally unique identification code UUID for each network device in the target network managed by the network management system, so that each group of the microservice sub
  • the management function jointly implemented by the microservices provided by the unit manages the network device according to the UUID of the network device.
  • a network management method is provided, which is applied to the network management system described in any one of the aforementioned first aspects, and the method includes:
  • the target network parameters as network parameters of a simulated network, where the simulated network is constructed based on the target network managed by the network management system;
  • simulation running state matches the target running state, configuring the target network parameters as network parameters of the target network.
  • the method also includes:
  • the simulation running state does not match the target running state, re-determine the new target network parameters, and return to the execution of configuring the target network parameters as network parameters of the simulated network, the simulated network is based on the The steps of building the target network managed by the network management system.
  • the determining target network parameters includes:
  • the inference model Inputting the target operating state into the inference model to obtain the target network parameters output by the inference model, wherein the inference model is pre-trained and used to infer the network parameters of the network according to the input target operating state Model.
  • the method also includes:
  • the inference model is updated according to the difference between the inference network parameters and the current network parameters.
  • a network management device which is applied to the network management system described in any one of the first aspects above, and the device includes:
  • a parameter determination module configured to determine target network parameters
  • a simulation module configured to configure the target network parameters as network parameters of a simulated network, where the simulated network is constructed based on the target network managed by the network management system;
  • a verification module configured to obtain the simulation running status of the simulation network
  • a judging module configured to judge whether the simulation running state matches the target running state
  • a configuration module configured to configure the target network parameters as network parameters of the target network if the simulation running state matches the target running state.
  • an electronic device including:
  • the processor is configured to implement the method steps described in any one of the above-mentioned second aspects when executing the program stored in the memory.
  • a computer-readable storage medium is provided, and a computer program is stored in the computer-readable storage medium, and when the computer program is executed by a processor, any one of the above-mentioned second aspects is implemented. Method steps.
  • the network management system, method, device, and electronic equipment provided in the embodiments of the present application can divide services for implementing various management functions into multiple groups of microservices based on the microservice architecture, and provide these microservices by microservice subunits, Therefore, a variety of different management functions can be realized in a network management system.
  • the installation and deployment logic and operation management logic of all micro-service sub-units are unified through the support unit, so as to provide a unified deployment platform and operation platform for all micro-service sub-units , so as to realize the unification of different management functions in the support layer.
  • the data management unit the data of each micro-service sub-unit is uniformly stored, and at the same time, the access logic of different types of data is unified, so that the data between different micro-service sub-units can communicate, so as to realize the unification of different management functions in the data layer .
  • the main interface is displayed through the presentation layer, and an interface for jumping to the functional interface of each microservice subunit is set in the main interface, so that users can access the functional interface of different microservice subunits through a unified portal, thereby realizing Unification of different management functions in the presentation layer.
  • a variety of different management functions can be integrated into an organic whole in the support layer, data layer, business layer, and display layer. Users can effectively implement a variety of different management functions through a unified interface, which can simplify network management. operation.
  • FIG. 1 is a schematic structural diagram of a network management system provided in an embodiment of the present application
  • FIG. 2 is a schematic structural diagram of a support unit in a network management system provided by an embodiment of the present application
  • FIG. 3 is a schematic flowchart of a service deployment method provided in an embodiment of the present application.
  • FIG. 4 is a schematic structural diagram of a data management unit in the network management system provided by the embodiment of the present application.
  • FIG. 5 is a schematic structural diagram of a display unit in the network management system provided by the embodiment of the present application.
  • FIG. 6 is a schematic flowchart of a network management method provided in an embodiment of the present application.
  • FIG. 7 is a schematic structural diagram of a network management device provided in an embodiment of the present application.
  • FIG. 8 is a schematic structural diagram of an electronic device provided by an embodiment of the present application.
  • relevant personnel can log in a program product (hereinafter referred to as network management product) for managing the network, a program product (hereinafter referred to as controller product) for controlling the network, and a program product (hereinafter referred to as controller product) for performing intelligent analysis on the network are installed.
  • network management product for managing the network
  • controller product for controlling the network
  • controller product for controlling the network
  • controller product for performing intelligent analysis on the network
  • intelligent analysis products The management platform of program products (hereinafter referred to as intelligent analysis products). According to the actual needs of users, activate one or more of the network management products, controller products, and intelligent analysis products to manage the network.
  • the relevant personnel may start the intelligent analysis product to perform analysis such as prediction and fault detection on the network, and obtain the analysis result output by the intelligent analysis product.
  • Relevant personnel judge whether it is necessary to change the network parameters of the network based on the analysis results and their own actual experience. If the relevant personnel think that the network parameters of the network need to be changed, they can start the network management product to change the network parameters of the network.
  • the network management product, the controller product, and the intelligent analysis product are independent of each other, and relevant personnel need to switch the products used according to the actual situation and/or experience, resulting in cumbersome and unsmooth operation, so the user experience is poor.
  • the embodiment of the present application provides a network management system, as shown in Figure 1, which is a schematic structural diagram of the network management system provided in the embodiment of the present application, which may include a support unit 110, a data management unit 120 , business service unit 130 and display unit 140 .
  • the business service unit 130 includes multiple groups of microservice subunits 131 .
  • Each microservice subunit 131 is used to provide a microservice, and the microservices provided by each group of microservice subunits 131 are jointly used to implement a management function.
  • the support unit 110 installs and deploys all microservice subunits 131 through the same installation and deployment logic, so as to provide a unified deployment platform for all microservice subunits;
  • the support unit 110 performs operation management on all micro-service sub-units 131 through the same operation management logic, so as to provide a unified operation platform for all micro-service sub-units;
  • the data management unit 120 stores the data of all microservice subunits 131 through the same data storage logic, so as to provide unified data storage services for all microservice subunits 131;
  • the data management unit 120 encapsulates the access logic of each type of data into the same access logic, and makes all microservice subunits 131 access each type of data through the same access logic;
  • the display unit 140 provides a unified portal framework service for all microservice subunits 131 by displaying the main interface and setting an interface for jumping to the functional interface of each microservice subunit in the main interface.
  • the services used to implement various management functions can be divided into multiple groups of microservices based on the microservice architecture, and these microservices are provided by the microservice sub-units, so that a variety of different management functions can be implemented in one network management system.
  • the installation and deployment logic and operation management logic of all micro-service sub-units are unified through the support unit, so as to provide a unified deployment platform and operation platform for all micro-service sub-units, so as to realize the unification of different management functions at the support layer.
  • the data management unit the data of each micro-service sub-unit is uniformly stored, and at the same time, the access logic of different types of data is unified, so that the data between different micro-service sub-units can communicate, so as to realize the unification of different management functions in the data layer .
  • the main interface is displayed through the presentation layer, and an interface for jumping to the functional interface of each microservice subunit is set in the main interface, so that users can access the functional interface of different microservice subunits through a unified portal, thereby realizing Unification of different management functions in the presentation layer. Therefore, a variety of different management functions can be integrated into an organic whole at the support layer, data layer, business layer, and display layer. Users can effectively implement various management functions through a unified interface, which can simplify network management. operate.
  • each microservice subunit 131 may be composed of one or more virtual machines and/or containers (such as docker containers), and the microservice provided by each microservice subunit 131 is used to implement a management function
  • the microservices in the service can be, for example, monitoring service, topology service, report service, etc.
  • Different microservice subunits 131 may be deployed on the same physical device, or may be deployed on different physical devices, which is not limited in this embodiment. Exemplarily, all the microservice subunits 131 may be deployed on the same physical device, or they may be deployed on different physical devices in the cluster, or a part of the microservice subunits 131 may be deployed on one physical device in the cluster , another part of the microservice sub-units is deployed on another physical device in the cluster.
  • the cluster may refer to a cluster formed by multiple physical devices that can be used to implement the network management system provided by the embodiment of the present invention.
  • the microservice subunits 131 included in the business service unit 130 may be different.
  • the business service unit 130 may include three groups of microservice subunits 131, wherein the microservices provided by a group of microservice subunits 131 are jointly used to realize the functions of network management products, The microservices provided by a group of microservice subunits 131 are jointly used to implement the functions of the controller product, and the microservices provided by a group of microservice subunits 131 are jointly used to implement the functions of the intelligent analysis product.
  • the business service unit 130 may only include two groups of microservice subunits 131 or four or more groups of microservice subunits 131 , which is not limited in this embodiment.
  • the support unit 110 the data management unit 120 and the display unit 140 will be described respectively below.
  • the structure of the support unit 110 can be shown in FIG. A role unification subunit 115 and a system self-monitoring unification subunit 116 .
  • the support unit 110 may only include some subunits in all the subunits shown in FIG. 2 , and may also include subunits not shown in FIG. 2 , and this embodiment does not make any Restrictions, for example, in a possible embodiment, the support unit 110 may only include the deployment platform unified subunit 111, the operating platform unified subunit 112, the protocol channel unified subunit 113, and the account role unified subunit 115, instead of the above-mentioned The log unification subunit 114 and the system self-monitoring unification subunit 116 .
  • the unified deployment platform subunit 111 is used to install and deploy all microservice subunits 131 through the same installation and deployment logic, so as to provide a unified deployment platform for all microservice subunits.
  • the same installation and deployment logic can be different according to different actual needs.
  • FIG. 3 is a schematic flow chart of the service deployment method provided by the embodiment of the present application , which can include:
  • each business service refers to a service for realizing any management function, such as a service for realizing a function of a network management product (hereinafter referred to as a network management service), a service for realizing a function of a controller product (hereinafter referred to as a control server service) and services for realizing the functions of intelligent analysis products (hereinafter referred to as intelligent analysis services).
  • a network management service a service for realizing a function of a network management product
  • a control server service a service for realizing a function of a controller product
  • intelligent analysis services services for realizing the functions of intelligent analysis products
  • the format of the installation package can be different according to different application scenarios.
  • it can be a compressed package format
  • the installation package can include: installation and deployment configuration files, such as json (a lightweight data exchange format) or YAML ( A configuration file in the format used to represent data serialization); installation and deployment scripts, such as shell (shell) or py (python, a programming language) script; container images, such as tar (a compressed format) format container image; database scripts, such as database scripts in sql (structured query language, structured query language) format.
  • installation and deployment configuration files such as json (a lightweight data exchange format) or YAML ( A configuration file in the format used to represent data serialization)
  • installation and deployment scripts such as shell (shell) or py (python, a programming language) script
  • container images such as tar (a compressed format) format container image
  • database scripts such as database scripts in sql (structured query language, structured query language) format.
  • It can be decompressed according to the uploaded installation package and analyzed and displayed according to the preset specifications, so that the user can input selection instructions according to the displayed content, and select the service to be installed and deployed according to the selection instructions entered by the user.
  • the parameter configuration of the service may be performed according to the parameter configuration instruction input by the user, or according to a preset rule, which is not limited in this embodiment.
  • the deployment platform unified subunit 111 can maintain a subnet IP address pool, and the subnet IP address pool includes a plurality of IP addresses, and the deployment platform unified subunit 111 can use the subnet IP address pool to allocate IP addresses for the services installed and deployed, thereby Network configuration for installed and deployed services.
  • Local storage resources and/or shared storage resources can be set up for services that need to be installed and deployed.
  • the local storage may refer to a storage resource local to the physical device for implementing the service and used to store data of the service
  • the shared storage resource may refer to a storage resource used to store data of multiple different services.
  • the installation and deployment configuration is used to indicate the configuration for the service to be installed and deployed, including but not limited to the parameter configuration in the aforementioned S303, the network configuration in the aforementioned S304, and the storage configuration in the aforementioned S305.
  • the deployment platform unified subunit 111 can also call scripts corresponding to the parameter settings to initialize the database and load and start each service container image according to the parameter settings in the installation and deployment configuration.
  • the installation and deployment logic of products with different management functions may be different. If users need to use products with different management functions, they need to use different installation and deployment logic to install different products respectively, that is, users need to learn multiple Different installation and deployment logics lead to higher learning costs for users.
  • users can realize various management functions without having to learn a variety of different installation and deployment logics, effectively reducing the user's learning costs.
  • the running platform unification subunit 112 is used for running and managing all microservice subunits 131 through the same operation management logic, so as to provide a unified running platform for all microservice subunits 131 .
  • the unified operating platform subunit 112 can provide a unified container operation mode, unified operation scheduling and management for all microservice subunits 131 in the business service unit 130, thereby effectively simplifying the operation management of each business service.
  • the operating platform unified subunit 112 may be composed of the following systems: an operating system, such as a Linux operating system; a microservice management and orchestration system, such as K8S (kubernets, a cluster management tool); a container system, such as a Docker container system.
  • the running platform unified subunit 112 can run in a stand-alone mode or in a cluster mode.
  • the supporting services and the microservices provided by each microservice subunit 131 are sent to the microservice management and orchestration system through the unified deployment platform, and the microservice management and orchestration system performs unified operation scheduling on the microservices provided by each microservice subunit 131.
  • the microservices provided by each microservice sub-unit 131 perform unified operation management such as start-stop, restart, etc., and uniformly run on the operating system in the form of containers.
  • the protocol channel unifying subunit 113 is used for uniform message modeling and encapsulation of the protocols used in all microservices provided by all microservice subunits 131 , so as to provide unified protocol channel services for all microservice subunits 131 .
  • the protocol channel unification subunit 113 may manage the protocol channels in a connection pool manner, including but not limited to creation, destruction, and channeling of the protocol channels.
  • the microservices provided by each microservice subunit 131 use the protocol through SDK (Software Development Kit, software development kit) or REST (a software architecture style) interface.
  • the log unification subunit 114 is used to obtain the operation logs generated by all microservices provided by all microservice subunits 131, and perform log management on all obtained logs through the same log management logic, so as to implement log management for all microservice subunits 131 Provide a unified log service.
  • the obtained logs may include but not limited to: operation logs of microservices provided by each microservice subunit 131 , operation logs of microservices provided by each microservice subunit 131 , and operation logs of the supporting service itself.
  • the microservices provided by the microservice subunits 131 publish operation logs through the message bus, and the log unification subunit 114 obtains the operation logs by monitoring the message bus.
  • the log unification subunit 114 can collect the running logs of the microservices provided by each microservice subunit 131 and the running logs of the supporting services themselves through the log plug-in. And the obtained operation logs and running logs are uniformly output to the search engine database for storage management. All types of logs support conditional retrieval, export, and automatic cleaning according to time or disk space occupied.
  • the account role unifying subunit 115 is used to provide a unified account role for the microservices provided by each microservice subunit 131, so that only one set of unified account roles is required in various network scenarios.
  • the account role unification subunit 115 can perform unified role authority management, wherein role authority management can include but not limited to operations such as creation, modification, and deletion of operator accounts, tenants, roles, permissions, and groups.
  • permissions can be composed of functional operation permissions and data permissions, and a collection of permissions constitutes a role.
  • Multiple operator accounts can be defined as a group, that is, multiple operator accounts can be defined as a group according to actual needs .
  • Permissions are assigned to operator accounts or groups through roles, and operator accounts can obtain group roles. For example, assuming that operator account 1 belongs to group A, and group A is assigned role A, the operator account 1 has all the permissions of role A.
  • the collection of data in the system constitutes a tenant, and the operator account can obtain permissions related to the data in the tenant by binding to the tenant.
  • the microservices provided by each microservice subunit 131 can obtain the permission of the currently logged-in operator account through the SDK or the REST interface, so as to use the obtained permission to perform access control on the resources required by the provided microservice.
  • the unified system self-monitoring subunit 116 provides unified self-monitoring services for the microservices provided by each microservice subunit 131 by monitoring the running platform and analyzing the running logs. Assuming that each microservice subunit 131 is deployed on different physical devices in the cluster, when installing and deploying each microservice subunit 131, the self-monitoring service can be deployed on each physical device in the cluster, and the cluster can be connected to the cluster through the interface of the operating platform. Continuously monitor the CPU, memory, disk resources, running status and real-time utilization of each physical device in the system and microservices provided by each microservice subunit 131.
  • the structure of the data management unit 120 can be shown in Figure 4, including a data model unified subunit 121, a data storage unified subunit 122, a data access unified subunit 123, and a data recovery backup unified subunit 124.
  • the data management unit 120 may also include only some subunits of all the subunits shown in FIG. 4 , and may also include subunits not shown in FIG. 4 , and this embodiment does not make any limit
  • the data model unified subunit 121 is used to configure UUID (Universally Unique Identifier) for each network device in the target network managed by the network management system, so that the microservice subunit 131 provided by each group
  • UUID Universally Unique Identifier
  • the management function jointly realized by the service manages the network device according to the UUID of the network device.
  • the data model unifying subunit 121 can establish a unified data model for objects such as switches and other objects managed in the service for implementing various management functions according to the attributes of each object.
  • the attributes of the objects are composed of public attributes and extended attributes.
  • the public attributes of the object include public attributes such as UUID, domain ID, type ID, and management IP address, and the extended attributes can be defined according to different objects.
  • the data model unifying subunit 121 will generate a unique object UUID through hash coding calculation of public attributes such as domain ID, type ID, and management IP address. This ensures that the object UUID generated by the same device is the same whenever it is used.
  • Each service can integrate data and functions in different scenarios through the UUID of the object.
  • the unified data storage subunit 122 is used to store data of all microservice subunits 131 through the same data storage logic, so as to provide unified data storage services for all microservice subunits 131 .
  • the data storage services provided by the data storage unified subunit 122 include but are not limited to: provide relational database services to store relational data, provide cache database services to store key-value type data, provide time series database services to store time series data, and provide graph database services Store graph-structured data and provide search engine database services to store and retrieve data.
  • the data access unified subunit 123 is used to encapsulate the access logic of various types of data into the same access logic, and make all the microservice subunits 131 scope the various types of data through the same access logic.
  • the same access logic can be different according to different application scenarios.
  • the unified data access subunit 123 can perform CRUD on the access of various types of data based on the RESTful (a design style and development method of network applications) protocol. (Create Retrieve Update Delete, Add, Retrieve, Update and Delete) operation interface encapsulation modeling, and packaged into SDK, to provide a unified CRUD service for each business service.
  • each microservice subunit 131 pass in the type of data service, object model, or object UUID or other attribute parameters through the SDK or REST interface of the unified data access service to perform data CURD operations on various databases. That is, the unified data access subunit 123 can encapsulate the access logic for various types of data into an SDK based on the RESTful protocol, and each microservice subunit 131 accesses various types of data by calling the interface of the SDK.
  • the unified data backup and recovery subunit 124 can provide unified backup and recovery services for the data of the microservices provided by each microservice subunit 131, which can be backed up locally or remotely, and can be backed up regularly.
  • the data storage management of the microservices provided by each microservice subunit 131 is provided by the data management unit 120, so each microservice subunit 131 does not need to pay attention to the data backup and recovery of the microservice provided by itself, but is unified by the data management unit 120.
  • the microservices provided by each microservice subunit 131 can register policies with the data management unit 120 during installation and deployment. The registered policies are used to indicate the data backup and recovery methods of the microservices.
  • the registered policies can be used for It indicates that the data backup mode of the microservice is cold backup and the recovery mode is cold loading.
  • the registered policy may also be used to indicate that the data backup mode of the microservice is hot backup and the recovery mode is hot loading.
  • the data management unit 120 performs a corresponding stop or restart operation on the microservices provided by each microservice subunit 131 through the unified operating platform according to the registered policy.
  • the policy registered by a microservice subunit 131 indicates The data backup mode of the microservice provided by the microservice subunit 131 is cold backup, then the data management unit 120 can restart the microservice subunit 131 when performing data backup for the microservice provided by the microservice subunit 131 operation to complete the cold backup of the microservice data provided by the microservice subunit 131.
  • the policy registered by a microservice subunit 131 indicates that the data recovery mode of the microservice provided by the microservice subunit 131 is hot loading, then the data management unit 120 can provide the microservice for the microservice subunit 131 When data recovery is performed, the microservice subunit 131 is stopped to complete the hot loading of the microservice data provided by the microservice subunit 131 .
  • the structure of the display unit 140 can be shown in Figure 5, including a unified portal frame subunit 141, a unified login authentication subunit 142, a northbound interface subunit 143, a dynamic menu subunit 144, and interface layout Subunit 145.
  • the display unit 140 may only include some subunits in all the subunits shown in FIG. 4 , and may also include subunits not shown in FIG. 4 , and this embodiment does not make any limit
  • the unified portal framework subunit 141 is used to display the main interface, and the interface for jumping to the functional interface of each microservice subunit 131 is set in the main interface, so as to provide a unified portal for all microservice subunits Framework services. That is, the unified portal framework subunit 141 has the function of displaying the main interface, and has the function of setting an interface for jumping to the functional interface of each microservice subunit 131 in the main interface, and unifies the portal framework through these two functions
  • the subunit 141 provides a unified portal framework service for all microservice subunits 131 .
  • the form of the interface can be different according to different application scenarios.
  • a control for jumping to the functional interface of each microservice subunit 131 can be set in the main interface, and in other possible embodiments, an input box for user input URL (Uniform Resource Locator, Uniform Resource Locator) may also be set in the main interface, and jump to the microservice corresponding to the URL according to the URL input by the user The functional interface of the subunit 131.
  • Uniform Resource Locator Uniform Resource Locator
  • the unified portal framework subunit 141 can provide a unified login entry and a page rendering display framework for the microservices provided by the microservice subunits 131 .
  • the microservices provided by each microservice subunit 131 only need to provide interfaces related to business functions.
  • the access route registered by the display layer jumps to the specific business function page.
  • the unified portal frame subunit 141 can provide the entire display frame of the page through a page template.
  • the top navigation and the left menu area of the page can also be rendered and displayed by the unified portal frame subunit 141, and the business function content can be displayed through web (network) page code fragments or iframe (a page element) ) frame embedded in the content area of the business function page.
  • the unified login authentication subunit 142 provides unified login authentication for the microservices provided by each microservice subunit 131, including login interface, access policy, password authentication, and external authentication system, such as LDAP (Lightweight Directory Access Protocol, Lightweight Directory Access agreement), etc.
  • the unified login authentication subunit can intercept the access request of the microservice provided by each microservice subunit 131 through a filter, and perform authentication and confirmation on the logged-in operator account. Jump to the login entry page to authenticate the logged-in operator account.
  • the northbound interface subunit 143 provides a unified northbound gateway for the microservices provided by each microservice subunit 131 , thereby providing a unified northbound access service for the microservices provided by each microservice subunit 131 .
  • the microservice provided by each microservice subunit 131 registers the route URL for northbound access to the northbound gateway provided by the presentation layer during installation and deployment.
  • the dynamic menu subunit 144 is configured to determine the menu items corresponding to the access rights of the accounts logged into the network management system according to the pre-stored correspondence between access rights and menu items, and display the determined menu items.
  • the dynamic menu subunit 144 may provide registration and rendering of menus for microservices provided by each microservice subunit 131 .
  • the microservices provided by each microservice subunit 131 register single-scene domain and cross-scene domain menus in the dynamic menu subunit 144 according to the menu registration model specification during installation and deployment. After the operation account is logged in and authenticated, the dynamic menu subunit The unit 144 can obtain the registered menu configuration, and render and display the menu items according to the menu configuration and access rights.
  • the interface layout subunit 145 is used to determine the interface element corresponding to the access authority of the account that logs into the network management system in the main interface according to the corresponding relationship between the pre-stored access authority and the interface element, and determine the corresponding interface element in the main interface.
  • the properties of the interface elements are reset to display the reset main interface, wherein the interface elements include menu items and/or widgets (widgets).
  • the interface layout subunit 145 may provide menu rearrangement services and page content display rearrangement services for the microservices provided by each microservice subunit 131 .
  • the menu rearrangement service and the page content display rearrangement service will be described separately below:
  • the microservices provided by each microservice subunit 131 register the preset menus in the interface layout service during installation and deployment, and the interface layout service obtains the menu items within the authority range of the operator account that has passed the current login authentication through the entry of menu rearrangement , reset one or more of the properties of these menu items, such as name, opening method, rendering priority, hidden or not, parent-child relationship, etc., save the reset properties, and load the reset menu items properties, and render according to the loaded properties and re-main interface.
  • the properties of each menu item in the re-displayed interface are theoretically the same as those after the reset.
  • each microservice subunit 131 can encapsulate business functions into one or more widgets and register them with the interface layout service during installation and deployment, and the interface layout service obtains the operation of passing the current login authentication through the page content rearrangement entry Widgets within the authority of the account, reset one or more of the widget’s title, whether to hide, size, position, style, data source connection and other attributes, save the reset attributes, and load the widget After resetting the properties of the component, render according to the loaded properties and reset the main interface.
  • the property of each widget in the redisplayed interface is theoretically the same as the property after reset.
  • FIG. 6 is one of the network management methods provided in the embodiment of the present application.
  • a flow diagram which may include:
  • network management products, controller products, and intelligent analysis products can be integrated at the service layer, so that the services of the three products can communicate with each other, forming an autonomous closed loop in terms of services, thereby automatically optimizing the network without the need for relevant personnel
  • the network parameters are manually optimized, so the network can be effectively optimized in real time.
  • the manner of determining the target network parameter may be different according to different application scenarios.
  • the target network parameter may be determined according to the received user intention or the system intention.
  • the user intent is used to represent the operating state that the user expects the target network to be in
  • the system intent is used to represent the operating state that the management system expects the target network to be in.
  • User intentions can be input by users according to actual needs, and system intentions can be generated by the system according to preset rules. It may be to identify the user intention or the system intention, so as to obtain the target network parameters corresponding to the user intention or the system intention.
  • the inference model may be to obtain the target operating state, and input the target operating state into the inference model to obtain the target network parameters output by the inference model, wherein the inference model is pre-trained for A model that infers the network parameters of the network based on the input target operating state.
  • the inference model may be an algorithm model obtained based on traditional machine learning training, or a neural network model obtained based on deep learning training, which is not limited in this embodiment.
  • the accuracy of the trained inference model is often limited.
  • the current network parameters and the current running state of the target network can be obtained, the current running state is input into the reasoning model, and the reasoning running parameters output by the reasoning model are obtained, and The inference model is updated based on the difference between the inference run parameters and the current network parameters.
  • the current network parameters and the current operation state of the target network are the network parameters and the operation state of the target network at a certain moment collected during the operation of the target network. It can be understood that the current network parameters are the real network parameters when the target network is in the current operating state. Therefore, without considering the error of the inference model, theoretically input the current operating state into the inference model, and the obtained inference network parameters should be Current network parameters.
  • the inference model actually has errors, there is a certain difference between the inference network parameters and the current network parameters, and the inference model can be updated according to the difference to further improve the accuracy of the inference model.
  • the simulation network is constructed based on the target network managed by the network management system, and is used to simulate the target network.
  • the simulated network environment where the simulated network is located should be the same or similar to the network environment where the target network is located.
  • the simulation running state is the running state of the target network obtained by simulation when the network parameters of the target network are the target network parameters, and the real running state when the network parameters of the non-target network are the target network parameters.
  • a simulated network verification environment may be built according to the target network parameters, and the simulation is performed in the simulated network verification environment to obtain the simulation running status.
  • the target operating state is the expected operating state of the target network. For example, assuming that the target network parameters are determined according to the user intention or the system intention, the target operating state may be the user intention or the system intention. Indicates the running status.
  • the match between the simulation running state and the target running state can mean that the simulation running state is the same as the target running state, or it can mean that the simulation running state is better than the target running state, or it can mean that the difference between the simulation running state and the target running state is less than the preset program threshold.
  • the load rate of the CPU in the target running state is 50%
  • the load rate of the CPU in the simulated running state is also 50%
  • State matching it can also be considered that the simulation running state matches the target running state when the CPU load rate in the simulation running state is lower than 50%, or when the difference between the CPU load rate and 50% in the simulation running state is less than 10%
  • the simulation run state is considered to match the target run state.
  • the simulation running state does not match the target running state
  • the network parameters of the target network are the target network parameters
  • the target network cannot run in the expected running state.
  • the target network parameters cannot be used as the target network parameters.
  • the simulation running status may be displayed, and the user judges whether to manually optimize the target network according to the displayed simulation running status.
  • the displayed simulation running status meets the user's expectations, it can be considered that the target network can be automatically optimized according to the target network parameters, and the user does not need to manually optimize the target network.
  • the displayed simulation running status does not meet the user's expectations, it can be considered that it is difficult to automatically optimize the target network according to the target network parameters at this time, and the user can manually optimize the target network.
  • FIG. 7 is a schematic structural diagram of a network management device provided in an embodiment of the present application, which may include:
  • a simulation module 702 configured to configure the target network parameters as network parameters of a simulated network, where the simulated network is constructed based on the target network managed by the network management system;
  • a verification module 703, configured to acquire the simulation running status of the simulation network
  • a judging module 704 configured to judge whether the simulation running state matches the target running state
  • the configuration module 705 is configured to configure the target network parameters as network parameters of the target network if the simulation running state matches the target running state.
  • the simulation module 702 is further configured to re-determine new target network parameters if the simulation running state does not match the target running state, and return to execute the
  • the network parameter configuration is a network parameter of a simulated network, and the simulated network is a step constructed based on the target network managed by the network management system.
  • the parameter determination module 701 is specifically configured to obtain the target operating state
  • the inference model Inputting the target operating state into the inference model to obtain the target network parameters output by the inference model, wherein the inference model is pre-trained and used to infer the network parameters of the network according to the input target operating state Model.
  • the device further includes a model update module, configured to acquire current network parameters and current operating status of the target network;
  • the inference model is updated according to the difference between the inference network parameters and the current network parameters.
  • the embodiment of the present application also provides an electronic device, as shown in FIG. 8 , including:
  • memory 801 for storing computer programs
  • the target network parameters as network parameters of a simulated network, where the simulated network is constructed based on the target network managed by the network management system;
  • simulation running state matches the target running state, configuring the target network parameters as network parameters of the target network.
  • the communication bus mentioned above for the electronic device may be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus or the like.
  • PCI Peripheral Component Interconnect
  • EISA Extended Industry Standard Architecture
  • the communication bus can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is used in the figure, but it does not mean that there is only one bus or one type of bus.
  • the communication interface is used for communication between the electronic device and other devices.
  • the memory may include a random access memory (Random Access Memory, RAM), and may also include a non-volatile memory (Non-Volatile Memory, NVM), such as at least one disk memory.
  • RAM Random Access Memory
  • NVM non-Volatile Memory
  • the memory may also be at least one storage device located far away from the aforementioned processor.
  • the above-mentioned processor can be a general-purpose processor, including a central processing unit (Central Processing Unit, CPU), a network processor (Network Processor, NP), etc.; it can also be a digital signal processor (Digital Signal Processor, DSP), a dedicated integrated Circuit (Application Specific Integrated Circuit, ASIC), Field-Programmable Gate Array (Field-Programmable Gate Array, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components.
  • CPU Central Processing Unit
  • NP Network Processor
  • DSP Digital Signal Processor
  • ASIC Application Specific Integrated Circuit
  • FPGA Field-Programmable Gate Array
  • a computer-readable storage medium is also provided, and a computer program is stored in the computer-readable storage medium, and when the computer program is executed by a processor, any of the above-mentioned network management methods is implemented. A step of.
  • a computer program product including instructions is also provided, which, when run on a computer, causes the computer to execute any one of the network management methods in the above embodiments.
  • all or part of them may be implemented by software, hardware, firmware or any combination thereof.
  • software When implemented using software, it may be implemented in whole or in part in the form of a computer program product.
  • the computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on the computer, the processes or functions according to the embodiments of the present application will be generated in whole or in part.
  • the computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable devices.
  • the computer instructions may be stored in or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from a website, computer, server or data center Transmission to another website site, computer, server, or data center by wired (eg, coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (eg, infrared, wireless, microwave, etc.).
  • the computer-readable storage medium may be any available medium that can be accessed by a computer, or a data storage device such as a server or a data center integrated with one or more available media.
  • the available medium may be a magnetic medium (for example, a floppy disk, a hard disk, or a magnetic tape), an optical medium (for example, DVD), or a semiconductor medium (for example, a Solid State Disk (SSD)).
  • SSD Solid State Disk

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Human Computer Interaction (AREA)
  • Power Engineering (AREA)
  • Computer Hardware Design (AREA)
  • Computer Security & Cryptography (AREA)
  • Computing Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Computer And Data Communications (AREA)

Abstract

本发明实施例提供了一种网络管理系统、方法、装置及电子设备。其中，所述网络管理系统包括支撑单元、数据管理单元、业务服务单元以及展示单元；业务服务单元包括多组微服务子单元；每个微服务子单元用于提供一种微服务，并且每组微服务子单元所提供的微服务共同用于实现一种管理功能；支撑单元，通过相同的安装部署逻辑对所有微服务子单元进行安装部署；并且，支撑单元通过相同的运行管理逻辑对所有微服务子单元进行运行管理；数据管理单元通过相同的数据存储逻辑存储所有微服务子单元的数据；并且，数据管理单元通过将各类型的数据的访问逻辑封装为同一访问逻辑；展示单元通过展示主界面。可以实现简化网络管理的操作。

Description

一种网络管理系统、方法、装置及电子设备
本申请要求于2021年5月17日提交中国专利局、申请号为202110532166.8发明名称为“一种网络管理系统、方法、装置及电子设备”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域，特别是涉及一种网络管理系统、方法、装置及电子设备。
背景技术
随着网络规模的逐渐增加，网络结构日益复杂，对网络进行管理的难度也逐渐增加。为了便于用户对网络进行有效的管理，相关技术中提供了多种具备不同管理功能的产品，如网管产品、控制器产品、智能分析产品等。用户可以根据实际需求同时运行多个具备不同管理功能的产品，共同对网络进行管理。
但是，相关技术中具备不同管理功能的产品彼此之间是相互独立的产品，用户需要根据实际情况轮番使用不同的产品进行网络管理，导致操作繁琐、用户体验较差。
发明内容
本申请实施例的目的在于提供一种网络管理系统、方法、装置及电子设备，以实现简化网络管理的操作。具体技术方案如下：
在本申请实施例的第一方面，提供了一种网络管理系统，所述网络管理系统包括支撑单元、数据管理单元、业务服务单元以及展示单元；
所述业务服务单元包括多组微服务子单元；
每个所述微服务子单元用于提供一种微服务，并且每组所述微服务子单元所提供的微服务共同用于实现一种管理功能；
所述支撑单元，通过相同的安装部署逻辑对所有所述微服务子单元进行安装部署，以实现为所有所述微服务子单元提供统一的部署平台；
并且，所述支撑单元通过相同的运行管理逻辑对所有所述微服务子单元进行运行管理，以实现为所有所述微服务子单元提供统一的运行平台；
所述数据管理单元通过相同的数据存储逻辑存储所有所述微服务子单元的数据，以实现为所有所述微服务子单元提供统一的数据存储服务；
并且，所述数据管理单元通过将各类型的数据的访问逻辑封装为同一访问逻辑，并使得所有所述微服务子单元通过所述同一访问逻辑访问各类型的数据；
所述展示单元通过展示主界面，并在所述主界面中设置用于跳转至每个所述微服务子单元的功能界面的接口，以实现为所有所述微服务子单元提供统一的门户框架服务。
在一种可能的实施例中，所述展示单元，还用于根据预先存储的访问权限与菜单项之间的对应关系，确定登录所述网络管理系统的账号的访问权限所对应的菜单项；并在所述主界面中展示所确定的菜单项。
在一种可能的实施例中，所述展示单元，还用于根据预先存储的访问权限与界面元素之间的对应关系，在主界面中确定登录所述网络管理系统的账号的访问权限所对应的界面元素；对主界面中所确定的界面元素的属性进行重新设置；展示经过重新设置后的主界面，其中，所述界面元素包括菜单项和/或微件。
在一种可能的实施例中，所述支撑单元，还用于对所有所述微服务子单元提供的所有微服务中使用的协议进行统一的消息建模和封装，以实现为所有所述微服务子单元提供统一的协议通道服务。
在一种可能的实施例中，所述支撑单元，还用于获取所有所述微服务子单元提供的所有微服务产生的日志，并通过相同的日志管理逻辑对所有获取到的日志进行日志管理，以实现为所有所述微服务子单元提供统一的日志服务。
在一种可能的实施例中，所述数据管理单元，还用于为所述网络管理系统所管理的目标网络中的各个网络设备配置通用唯一识别码UUID，以使得每组所述微服务子单元提供的微服务所共同实现的管理功能按照网络设备的所述UUID对网络设备进行纳管。
在本申请的第二方面，提供了一种网络管理方法，应用于前述第一方面任一所述的网络管理系统，所述方法包括：
确定目标网络参数；
将所述目标网络参数配置为仿真网络的网络参数，所述仿真网络为基于所述网络管理系统所管理的目标网络构建的；
获取所述仿真网络的仿真运行状态；
判断所述仿真运行状态是否与目标运行状态匹配；
如果所述仿真运行状态与所述目标运行状态匹配，则将所述目标网络参数配置为所述 目标网络的网络参数。
在一种可能的实施例中，所述方法还包括：
如果所述仿真运行状态与所述目标运行状态不匹配，重新确定新的目标网络参数，并返回执行所述将所述目标网络参数配置为仿真网络的网络参数，所述仿真网络为基于所述网络管理系统所管理的目标网络构建的步骤。
在一种可能的实施例中，所述确定目标网络参数，包括：
获取目标运行状态；
将所述目标运行状态输入至推理模型，得到所述推理模型输出的目标网络参数，其中，所述推理模型为预先经过训练的用于根据所输入的目标运行状态据推理网络的网路参数的模型。
在一种可能的实施例中，所述方法还包括：
获取所述目标网络的当前网络参数以及当前运行状态；
将所述当前运行状态输入至所述推理模型，得到所述推理模型输出的推理网络参数；
根据所述推理网络参数与所述当前网络参数之间的差异，更新所述推理模型。
在本申请实施例的第三方面，提供了一种网络管理装置，应用于前述第一方面任一所述的网络管理系统，所述装置包括：
参数确定模块，用于确定目标网络参数；
仿真模块，用于将所述目标网络参数配置为仿真网络的网络参数，所述仿真网络为基于所述网络管理系统所管理的目标网络构建的；
验证模块，用于获取所述仿真网络的仿真运行状态；
判断模块，用于判断所述仿真运行状态是否与目标运行状态匹配；
配置模块，用于如果所述仿真运行状态与所述目标运行状态匹配，则将所述目标网络参数配置为所述目标网络的网络参数。
在本申请的第四方面，提供了一种电子设备，包括：
存储器，用于存放计算机程序；
处理器，用于执行存储器上所存放的程序时，实现上述第二方面任一所述的方法步骤。
在本申请的第五方面，提供了一种计算机可读存储介质，所述计算机可读存储介质内存储有计算机程序，所述计算机程序被处理器执行时实现上述第二方面任一所述的方法步骤。
本申请实施例有益效果：
本申请实施例提供的网络管理系统、方法、装置及电子设备，可以基于微服务架构将用于实现多种管理功能的服务划分为多组微服务，并由微服务子单元提供这些微服务，从而在一种网络管理系统可以实现多种不同的管理功能，另外通过支撑单元统一所有微服务子单元的安装部署逻辑与运行管理逻辑，从而为所有微服务子单元提供统一的部署平台和运行平台，从而实现不同管理功能在支撑层的统一。并且通过数据管理单元对各微服务子单元的数据进行统一存储，同时统一不同类型的数据的访问逻辑，使得不同微服务子单元之间的数据可以互通，从而实现不同管理功能在数据层的统一。并且通过展示层展示主界面，并且在主界面中设置有用于跳转至每个微服务子单元的功能界面的接口，使得用户可以通过统一的门户访问不同微服务子单元的功能界面，从而实现不同管理功能在展示层的统一。，因此可以将多种不同的管理功能在支撑层、数据层、业务层以及展示层统一融合为一个有机整体，用户可以通过统一的界面有效的实现多种不同的管理功能，即可以简化网络管理的操作。
当然，实施本申请的任一产品或方法并不一定需要同时达到以上所述的所有优点。
附图说明
为了更清楚地说明本申请实施例或现有技术中的技术方案，下面将对实施例或现有技术描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本申请的一些实施例，对于本领域普通技术人员来讲，还可以根据这些附图获得其他的实施例。
图1为本申请实施例提供的网络管理系统的一种结构示意图；
图2为本申请实施例提供的网络管理系统中的支撑单元的一种结构示意图；
图3为本申请实施例提供的服务部署方法的一种流程示意图；
图4为本申请实施例提供的网络管理系统中的数据管理单元的一种结构示意图；
图5为本申请实施例提供的网络管理系统中的展示单元的一种结构示意图；
图6为本申请实施例提供的网络管理方法的一种流程示意图；
图7为本申请实施例提供的网络管理装置的一种结构示意图；
图8为本申请实施例提供的电子设备的一种结构示意图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例仅仅是本申请一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员基于本申请所获得的所有其他实施例，都属于本申请保护的范围。
为了更清楚的对本申请实施例提供的网络管理方法进行说明，下面将对本申请实施例提供的网络管理方法的一种可能的应用场景进行示例性的说明，可以理解的是，以下示例仅是本申请实施例提供的网络管理方法的一种可能的应用场景，在其他可能的实施例中，本申请实施例提供的网络管理方法也可以应用于其他可能的应用场景中，以下示例对此不做任何限制。
相关技术中，相关人员可以登录一个安装有用于对网络进行管理的程序产品(下文称网管产品)、用于对网络进行控制的程序产品(下文称控制器产品)以及用于对网络进行智能分析的程序产品(下文称智能分析产品)的管理平台。根据用户实际需求，启动网管产品、控制器产品以及智能分析产品中的一个或多个产品，以对网络进行管理。
示例性的，相关人员可以是启动智能分析产品对网络进行预测、故障检测等分析，并得到智能分析产品输出的分析结果。相关人员根据该分析结果结合自己的实际经验判断是否需要更改网络的网络参数，如果相关人员认为需要更改网络的网络参数，则可以启动网管产品对网络的网络参数进行更改。
但是，该方法中网管产品、控制器产品以及智能分析产品之间相互独立，需要相关人员根据实际情况和/或经验切换所使用的产品，导致操作繁琐、不流畅，因此用户体验较差。
基于此，本申请实施例提供了一种网络管理系统，可以如图1所示，图1所示为本申请实施例提供的网络管理系统的一种结构示意图，可以包括支撑单元110、数据管理单元120、业务服务单元130以及展示单元140。
其中，业务服务单元130包括多组微服务子单元131。
每个微服务子单元131用于提供一种微服务，并且每组微服务子单元131所提供的微服务共同用于实现一种管理功能。
支撑单元110，通过相同的安装部署逻辑对所有微服务子单元131进行安装部署，以实 现为所有微服务子单元提供统一的部署平台；
并且，支撑单元110通过相同的运行管理逻辑对所有微服务子单元131进行运行管理，以实现为所有微服务子单元提供统一的运行平台；
数据管理单元120通过相同的数据存储逻辑存储所有微服务子单元131的数据，以实现为所有微服务子单元131提供统一的数据存储服务；
并且，数据管理单元120通过将各类型的数据的访问逻辑封装为同一访问逻辑，并使得所有微服务子单元131通过同一访问逻辑访问各类型的数据；
展示单元140通过展示主界面，并在主界面中设置用于跳转至每个微服务子单元的功能界面的接口，以实现为所有微服务子单元131提供统一的门户框架服务。
选用该实施例，可以基于微服务架构将用于实现多种管理功能的服务划分为多组微服务，并由微服务子单元提供这些微服务，从而在一种网络管理系统可以实现多种不同的管理功能，另外通过支撑单元统一所有微服务子单元的安装部署逻辑与运行管理逻辑，从而为所有微服务子单元提供统一的部署平台和运行平台，从而实现不同管理功能在支撑层的统一。并且通过数据管理单元对各微服务子单元的数据进行统一存储，同时统一不同类型的数据的访问逻辑，使得不同微服务子单元之间的数据可以互通，从而实现不同管理功能在数据层的统一。并且通过展示层展示主界面，并且在主界面中设置有用于跳转至每个微服务子单元的功能界面的接口，使得用户可以通过统一的门户访问不同微服务子单元的功能界面，从而实现不同管理功能在展示层的统一。因此可以将多种不同的管理功能在支撑层、数据层、业务层以及展示层统一融合为一个有机整体，用户可以通过统一的界面有效的实现多种不同的管理功能，即可以简化网络管理的操作。
其中，每个微服务子单元131可以是由一个或多个虚拟机和/或者容器(如docker容器)组成的，并且每个微服务子单元131提供的微服务为用于实现一种管理功能的服务中的微服务，例如可以是监控服务、拓扑服务、报表服务等。
不同的微服务子单元131可以是部署于同一物理设备上的，也可以是部署在不同物理设备上的，本实施例对此不做任何限制。示例性的，可以是所有微服务子单元131部署在同一物理设备上，也可以是分别部署在集群中的不同物理设备上，还可以是一部分微服务子单元131部署在集群中的一个物理设备上，另一部分微服务子单元部署在集群中的另一个物理设备上。其中，集群可以是指由多个能够用于实现本发明实施例提供的网络管理系统的物理设备所构成的集群。
根据应用场景的不同，业务服务单元130中包括的微服务子单元131可以不同。示例性 的，在一种可能的实施例中，业务服务单元130中可以包括三组微服务子单元131，其中，一组微服务子单元131提供的微服务共同用于实现网管产品的功能，一组微服务子单元131提供的微服务共同用于实现控制器产品的功能，一组微服务子单元131提供的微服务共同用于实现智能分析产品的功能。
在其他可能的实施例中，业务服务单元130中也可以只包括两组微服务子单元131或者4组及4组以上的微服务子单元131，本实施例对此不做任何限制。
下面将分别对支撑单元110、数据管理单元120以及展示单元140分别进行说明。
在一种可能的实施例中，支撑单元110的结构可以如图2所示，包括部署平台统一子单元111、运行平台统一子单元112、协议通道统一子单元113、日志统一子单元114、账号角色统一子单元115以及系统自监控统一子单元116。在其他可能的实施例中，支撑单元110也可以只包括图2示出的所有子单元中的部分子单元，还可以包括图2中未示出的子单元，本实施例对此不做任何限制，例如在一种可能的实施例中，支撑单元110可以只包括部署平台统一子单元111、运行平台统一子单元112、协议通道统一子单元113、账号角色统一子单元115，而不包括上述日志统一子单元114以及系统自监控统一子单元116。
其中，部署平台统一子单元111用于通过相同的安装部署逻辑对所有微服务子单元131进行安装部署，以实现为所有微服务子单元提供统一的部署平台。相同的安装部署逻辑根据实际需求的不同可以不同，示例性的，在一种可能的实施例中，可以参见图3，图3所示为本申请实施例提供的服务部署方法的一种流程示意图，可以包括：
S301，将支撑服务以及各业务服务的安装包上传至服务器。
在本实施例中各业务服务是指用于实现任意管理功能的服务，如用于实现网管产品的功能的服务(下文称网管服务)、用于实现控制器产品的功能的服务(下文称控制器服务)以及用于实现智能分析产品的功能的服务(下文称智能分析服务)。
安装包的格式根据应用场景的不同可以不同，示例性的，可以是压缩包格式，并且安装包中可以包括：安装部署配置文件，如json(一种轻量级的数据交换格式)或YAML(一种用于表示数据序列化的格式)格式的配置文件；安装部署脚本，如shell(壳层)或py(python，一种编程语言)脚本；容器镜像，如tar(一种压缩格式)格式的容器镜像；数据库脚本，如sql(structured query language，结构化查询语言)格式的数据库脚本。
S302，选择所需安装部署的服务。
可以是根据上传的安装包进行解压缩并按照预设规范进行解析展示，以使得用户根据 所展示的内容输入选择指令，并根据用户输入的选择指令选择所需安装部署的服务。
S303，针对所需安装部署的服务进行参数配置。
可以根据用户输入的参数配置指令对服务进行参数配置，也可以是按照预设规则进行参数配置，本实施例对此不做任何限制。
S304，针对所需安装部署的服务进行网络配置。
部署平台统一子单元111可以维护有子网IP地址池，子网IP地址池中包括多个IP地址，部署平台统一子单元111可以使用子网IP地址池为安装部署的服务分配IP地址，从而为安装部署的服务进行网络配置。
S305，针对所需安装部署的服务进行存储配置。
可以为所需安装部署的服务设置本地存储资源和/或共享存储资源。其中，本地存储可以是指用于实现该服务的物理设备本地并且用于存储该服务的数据的存储资源，共享存储资源可以是指用于存储多个不同服务的数据的存储资源。
S306，在确认配置无误后将安装部署配置发送至运行平台。
其中，安装部属配置用于表示针对所需安装部署的服务进行的配置，包括但不限于前述S303中进行的参数配置、前述S304中进行的网络配置以及前述S305中的存储配置。在发送安装部署配置后，部署平台统一子单元111还可以根据安装部署配置中的参数设置，调用与参数设置对应的脚本进行数据库的初始化以及进行各服务容器镜像的加载启动。
可以理解的是，具备不同管理功能的产品的安装部署逻辑可能不同，用户如果需要使用具备不同管理功能的产品，则需要使用不同的安装部署逻辑分别安装部不同的产品，即用户需要学习多种不同的安装部署逻辑，导致用户的学习成本较高。而本申请通过统一所有微服务子单元131的安装部署逻辑，使得用户无需学习多种不同的安装部署逻辑，即可实现多种不同管理功能，有效降低用户的学习成本。
运行平台统一子单元112用于通过相同的运行管理逻辑对所有微服务子单元131进行运行管理，以实现为所有微服务子单元131提供统一的运行平台。运行平台统一子单元112可以是为业务服务单元130中所有微服务子单元131提供统一的容器运行方式、统一的运行调度和管理，从而有效简化各业务服务的运行管理。运行平台统一子单元112可以是由以下系统组成的：操作系统，如Linux操作系统；微服务管理编排系统，如K8S(kubernets，一种集群管理工具)；容器系统，如Docker容器系统。并且运行平台统一子单元112可以以单机模式运行也可以以集群的模式运行。支撑服务和各微服务子单元131提供的微服务通过统 一部署平台发送至微服务管理编排系统，并由微服务管理编排系统对各微服务子单元131提供的微服务进行统一的运行调度，对各微服务子单元131提供的微服务的启停、重启等进行统一的运行管理，并统一以容器的形式运行在操作系统之上。
协议通道统一子单元113用于对所有微服务子单元131提供的所有微服务中使用的协议进行统一的消息建模和封装，以实现为所有微服务子单元131提供统一的协议通道服务。示例性的，协议通道统一子单元113可以对协议通道以连接池的方式统一进行管理，包括但不限于协议通道的创建、销毁、通道等。各微服务子单元131提供的微服务通过SDK(Software Development Kit，软件开发工具包)或者REST(一种软件架构风格)接口对协议进行使用。
日志统一子单元114用于获取所有微服务子单元131提供的所有微服务产生的运行日志，并通过相同的日志管理逻辑对所有获取到的日志进行日志管理，以实现为所有微服务子单元131提供统一的日志服务。其中，获取到的日志可以包括但不限于：各微服务子单元131提供的微服务的操作日志、各微服务子单元131提供的微服务的运行日志以及支撑服务自身的运行日志。
在一种可能的实施例中，各微服务子单元131提供的微服务通过消息总线发布操作日志，日志统一子单元114通过监听消息总线的方式获取操作日志。日志统一子单元114可以通过日志插件收集各微服务子单元131提供的微服务的运行日志以及支撑服务自身的运行日志。并将获取到的操作日志以及运行日志统一输出至搜索引擎数据库中进行存储管理。所有类型的日志支持条件检索、导出、按时间或者占用磁盘空间大小进行自动清理。
账号角色统一子单元115用于为各微服务子单元131提供的微服务提供统一的账号角色，使得在各种网络场景下只需一套统一的账号角色。示例性的，账号角色统一子单元115可以进行统一的角色权限管理，其中，角色权限管理可以包括但不限于操作员账号、租户、角色、权限、群组的创建、修改、删除等操作。
可以理解的是，权限可以是由功能操作权限和数据权限组成，权限的集合构成角色，多个操作员账号可以定义成群组，即可以根据实际需求将多个操作员账号定义为一个群组。权限通过角色赋到操作员账号或者群组上，操作员账号可以获取群组的角色，示例性的，假设操作员账号1属于群组A，而群组A被赋予角色甲，则操作员账号1具有角色甲的所有权限。系统内数据的集合构成租户，操作员账号可以通过绑定到租户上，获取租户内数据相关的权限。
各微服务子单元131提供的微服务可以通过SDK或者REST接口获取当前登录操作员账号的权限，从而利用获取到的权限对所提供的微服务所需要的资源进行访问控制。
系统自监控统一子单元116通过对运行平台的监控以及对运行日志的分析为各微服务子单元131提供的微服务提供统一的自监控服务。假设各微服务子单元131部署在集群中的不同物理设备上，则在安装部署各微服务子单元131时可以将自监控服务部署到集群中的各个物理设备上，通过运行平台的接口对集群中的各物理设备以及各微服务子单元131提供的微服务分配的CPU、内存、磁盘资源、运行状态和实时的利用率进行持续监控。通过对各集群中的各物理设备和各微服务子单元131提供的微服务收集运行日志，并分析收集到的日志级别以及日志内容，根据分析结果，评估集群中各物理设备和各微服务子单元131提供的微服务在不同时间点运行的健康状态。
在一种可能的实施例中，数据管理单元120的结构可以如图4所示，包括数据模型统一子单元121、数据存储统一子单元122、数据访问统一子单元123以及数据恢复备份统一子单元124。在其他可能的实施例中，数据管理单元120也可以只包括图4示出的所有子单元的部分子单元，还可以包括图4中未示出的子单元，本实施例对此不做任何限制
其中，数据模型统一子单元121，用于为网络管理系统所管理的目标网络中的各个网络设备配置UUID(Universally Unique Identifier，通用唯一识别码)，以使得每组微服务子单元131提供的微服务所共同实现的管理功能按照网络设备的UUID对网络设备进行纳管。
示例性的，数据模型统一子单元121可以根据各对象的属性，为用于实现各管理功能的服务中纳管的交换机等对象建立统一的数据模型，对象的属性由公共属性和扩展属性组成，对象的公共属性包括UUID、域ID、类型ID、管理IP地址等公共属性，扩展属性可以根据对象的不同进行定义。无论是通过何种服务进行设备纳管时，数据模型统一子单元121都会通过域ID、类型ID、管理IP地址等公共属性的哈希编码计算生成唯一的对象UUID。从而保证无论何时使用时只要是同一个设备生成的对象UUID都是相同的。各服务可以通过对象的UUID将数据以及功能在不同的场景下进行融合统一。
数据存储统一子单元122用于通过相同的数据存储逻辑存储所有微服务子单元131的数据，以实现为所有微服务子单元131提供统一的数据存储服务。数据存储统一子单元122所提供的数据存储服务，包括但不限于：提供关系数据库服务存储关系型数据，提供缓存数据库服务存储键值类型数据，提供时序数据库服务存储时序类型数据，提供图数据库服务存储图结构类型的数据，提供搜索引擎数据库服务存储检索类数据。
数据访问统一子单元123用于通过将各类型的数据的访问逻辑封装为同一访问逻辑，并使得所有微服务子单元131通过该同一访问逻辑范围各类型的数据。该同一访问逻辑根据应用场景的不同可以不同，示例性的，数据访问统一子单元123可以基于RESTful(一种网络应用程序的设计风格和开发方式)协议对各类型的数据的访问统一进行了CRUD (Create Retrieve Update Delete，增加、检索、更新和删除)操作的接口封装建模，并打包成SDK，为各业务服务提供统一的CRUD服务。各微服务子单元131提供的微服务通过统一数据访问服务的SDK或者REST接口传入数据服务的类型、对象模型、或者对象的UUID或者其他属性参数对各类数据库进行数据的CURD操作。，即数据访问统一子单元123可以将对各类型的数据的访问逻辑封装为基于RESTful协议的SDK，各微服务子单元131通过调用该SDK的接口对各类型的数据进行访问。
数据备份恢复统一子单元124可以为各微服务子单元131提供的微服务的数据提供统一的备份恢复服务，可以本地备份也可以远程备份，并能够定时备份。各微服务子单元131提供的微服务的数据存储管理统一由数据管理单元120提供，因此各微服务子单元131无需关注自身提供的微服务的数据备份和恢复，而是统一由数据管理单元120根据备份和恢复的策略设置进行备份和恢复即可。各微服务子单元131提供的微服务在安装部署时可以向数据管理单元120注册策略，所注册的策略用于表示该微服务的数据备份方式和恢复方式，例如，所注册的策略可以用于表示该微服务的数据备份方式为冷备份并且恢复方式为冷加载，又例如，所注册的策略也可以用于表示该微服务的数据备份方式为热备份并且恢复方式为热加载。
数据管理单元120在备份和恢复时根据所注册的策略通过统一运行平台对各微服务子单元131提供的微服务进行对应的停止或重启操作，例如，一微服务子单元131所注册的策略表示该微服务子单元131提供的微服务的数据备份方式为冷备份，则数据管理单元120可以在为该微服务子单元131提供的微服务进行数据备份时，对该微服务子单元131进行重启操作，以完成该微服务子单元131提供的微服务的数据的冷备份。又例如，一微服务子单元131所注册的策略表示该微服务子单元131提供的微服务的数据恢复方式为热加载，则数据管理单元120可以在为该微服务子单元131提供的微服务进行数据恢复时，对该微服务子单元131进行停止操作，以完成该微服务子单元131提供的微服务的数据的热加载。
在一种可能的实施例中，展示单元140的结构可以如图5所示，包括统一门户框架子单元141、统一登录认证子单元142、北向接口子单元143、动态菜单子单元144以及界面编排子单元145。在其他可能的实施例中，展示单元140也可以只包括图4示出的所有子单元中的部分子单元，还可以包括图4中未示出的子单元，本实施例对此不做任何限制
其中，统一门户框架子单元141用于通过展示主界面，并且主界面中设置用于跳转至每个微服务子单元131的功能界面的接口，以实现为所有微服务子单元提供统一的门户框架服务。即，统一门户框架子单元141具备展示主界面的功能，并且具备在主界面中设置用于跳转至每个微服务子单元131的功能界面的接口的功能，通过该两个功能统一门户框架子单元141为所有微服务子单元131提供统一的门户框架服务。
其中接口的形式根据应用场景的不同可以不同，示例性的，在一种可能的实施例中，可以是在主界面中设置用于跳转至各个微服务子单元131的功能界面的控件，在其他可能的实施例中，也可以是在主界面中设置有用于用户输入URL(Uniform Resource Locator，统一资源定位器)的输入框，并根据用户输入的URL跳转至与该URL对应的微服务子单元131的功能界面。
示例性的，统一门户框架子单元141可以为各微服务子单元131提供的微服务提供统一的登录入口以及页面渲染展示框架。各微服务子单元131提供的微服务只需提供业务功能相关的界面，操作员账号登录认证成功后，通过解析具体业务功能页面的URL路径以及各微服务子单元131提供的微服务部署时向展示层注册的访问路由，跳转到具体的业务功能页面。统一门户框架子单元141可以通过页面模板方式提供页面的整个展示框架。
在一种可能的实施例中，页面的顶部导航和左边菜单区也可以由统一门户框架子单元141渲染并展示，业务功能内容部分通过web(网络)页面代码片段方式或者iframe(一种页面元素)框架嵌入到业务功能页面的内容区域。
统一登录认证子单元142为各微服务子单元131提供的微服务提供统一的登录认证，包括登录界面、访问策略、密码认证、对接外部的认证系统，如LDAP(Lightweight Directory Access Protocol，轻型目录访问协议)等。统一登录认证子单元可以通过过滤器拦截各微服务子单元131提供的微服务的访问请求，并对登录的操作员账号进行认证确认，如果确认已经过认证，则继续该访问请求的处理，否则跳转到登录入口页面对登录的操作员账号进行认证。
北向接口子单元143通过为各微服务子单元131提供的微服务提供统一的北向网关，从而为各微服务子单元131提供的微服务对外提供统一的北向访问服务。各微服务子单元131提供的微服务在安装部署时将北向访问的路由URL注册到展示层提供的北向网关上。
动态菜单子单元144，用于根据预先存储的访问权限与菜单项之间的对应关系，确定登录网络管理系统的账号的访问权限所对应的菜单项，并展示所确定的菜单项。
示例性的，动态菜单子单元144可以为各微服务子单元131提供的微服务提供菜单的注册以及渲染。各微服务子单元131提供的微服务在安装部署时按照菜单注册模型规范将单场景域和跨场景域的菜单注册到动态菜单子单元144中，在操作账号登录并认证通过后，动态菜单子单元144可以获取注册的菜单配置，并根据菜单配置以及访问权限对菜单项进行渲染并展示。
可以理解的是，用户可以通过界面中不同的菜单项以控制网络管理系统实现不同的功 能，而不同的用户具有不同的权限，因此一些用户可能并不具备控制网络管理系统实现特定功能的权限。因此用于实现这些特定功能的菜单项对于这些用户而言是没有必要展示的，即选用该实施例，可以根据用户权限的不同对应展示菜单项，以精简所展示的菜单项便于用户在界面中找寻所需要使用的菜单项。
界面编排子单元145，用于根据预先存储的访问权限与界面元素之间的对应关系，在主界面中确定登录网络管理系统的账号的访问权限所对应的界面元素，并对主界面中所确定的界面元素的属性进行重新设置，展示经过重新设置后的主界面，其中，界面元素包括菜单项和/或微件(widget)。
示例性的，界面编排子单元145可以为各微服务子单元131提供的微服务提供菜单再编排服务以及页面内容显示再编排服务。下面将分别对菜单再编排服务以及页面内容显示再编排服务进行说明：
各微服务子单元131提供的微服务在安装部署时将预置的菜单注册到界面编排服务中，界面编排服务通过菜单再编排的入口获取当前登录认证通过的操作员账号权限范围内的菜单项，对这些菜单项的名称、打开方式、渲染优先级、是否隐藏、父子关系等属性中的一种或多种属性进行重新设置，保存经过重新设置后的属性，加载菜单项经过重新设置后的属性，并按照加载的属性进行渲染并重新主界面。重新展示后的界面中各菜单项的属性理论上与经过重新设置后的属性相同。
各微服务子单元131提供的微服务在安装部署时可以将业务功能封装成一个或多个的微件注册至界面编排服务，界面编排服务通过页面内容再编排的入口获取当前登录认证通过的操作员账号权限范围内的微件，对微件的标题、是否隐藏、大小、位置、样式、数据源对接等属性中的一个或多个属性进行重新设置，保存经过重新设置后的属性，加载微件经过重新设置后的属性，并按照加载的属性进行渲染并重新主界面。重新展示后的界面中各微件的属性理论上与经过重新设置后的属性相同。
可以理解的是，在不同的网络结构以及不同的网络场景下，需要为网络配置不同的参数才能够使得网络正常运行。而在传统的运维方式中，需要依靠相关人员人工对网络的配置参数进行管理。但是在面对复杂的网络结构和多变的网络场景下，相关人员难以及时调整网络的配置参数，导致网络无法正常运行。
基于此，本申请实施例提供了一种网络管理方法，应用于前述任一所述的网络管理系统，方法可以参见图6，图6所示为本申请实施例提供的网络管理方法的一种流程示意图，可以包括：
S601，确定目标网络参数。
S602，将目标网络参数配置为仿真网络的网络参数。
S603，获取仿真网络的仿真运行状态。
S604，判断仿真运行状态是否与目标运行状态匹配。
S605，如果仿真运行状态与目标运行状态匹配，则将目标网络参数配置为目标网络的网络参数。
选用该实施例，可以在业务层融合网管产品、控制器产品以及智能分析产品，使得三个产品的业务互通，形成一个在业务上自治的闭环，从而自动地对网络进行优化，可以无需相关人员对网络参数进行人工的优化，因此可以有效地对网络进行实时地优化。
其中，在S601中，确定目标网络参数的方式根据应用场景的不同可以不同。示例性的，可以是在接收到用户意图或系统意图时，根据接收到的用户意图或系统意图确定目标网络参数。其中，用户意图用于表示用户预期中目标网络所应处于的运行状态，系统意图用于表示管理系统预期中目标网络所应处于的运行状态。
用户意图可以是用户根据实际需求输入的，系统意图可以是系统按照预设规则生成的。可以是对用户意图或系统意图进行识别，从而得到与用户意图或系统意图对应的目标网络参数。
示例性的，在一种可能的实施例中，可以是获取目标运行状态，并将目标运行状态输入至推理模型，得到推理模型输出的目标网络参数，其中，推理模型为预先经过训练的用于根据所输入的目标运行状态据推理网络的网路参数的模型。并且推理模型可以是基于传统的机器学习训练得到的算法模型，也可以是基于深度学习训练得到的神经网络模型，本实施例对此不做任何限制。
可以理解的是，受限制于训练得到推理模型时所使用的样本的质量以及数量，训练得到的推理模型的准确性往往有限。为进一步提高推理模型的准确性，在一种可能的实施例中，可以获取目标网络的当前网络参数以及当前运行状态，将当前运行状态输入至推理模型，得到推理模型输出的推理运行参数，并根据推理运行参数与当前网络参数之间的差异，更新推理模型。
其中，目标网络的当前网络参数以及当前运行状态为在目标网络运行过程中采集得到的目标网络在某一时刻的网络参数以及运行状态。可以理解为，当前网络参数为目标网络处于当前运行状态时真实的网络参数，因此在不考虑推理模型存在误差的情况下，理论上 将当前运行状态输入至推理模型，得到的推理网络参数应当为当前网络参数。
而由于推理模型实际上存在误差，因此推理网络参数与当前网络参数之间存在一定的差异，可以根据该差异更新推理模型，以进一步提高推理模型的准确性。
在S603中，仿真网络为基于网络管理系统所管理的目标网络构建的，用于对目标网络进行仿真模拟。仿真网络所处的仿真网络环境应当与目标网络所处的网络环境相同或相近。
在S604中，仿真运行状态为仿真得到的目标网络的网络参数为目标网络参数时目标网络的运行状态，而非目标网络的网络参数为目标网络参数时的真实运行状态。在一种可能的实施例中，可以是根据目标网络参数搭建模拟的网络验证环境，在该模拟的网络验证环境下进行仿真模拟，得到仿真运行状态。
在S605中，目标运行状态为预期中目标网络所应处于的运行状态，示例性的，假设目标网络参数是根据用户意图或系统意图确定得到的，则目标运行状态可以是用户意图或系统意图所表示的运行状态。
仿真运行状态与目标运行状态匹配可以是指仿真运行状态与目标运行状态相同，也可以是指仿真运行状态优于目标运行状态，还可以是指仿真运行状态与目标运行状态的差异程序小于预设阈值。
示例性的，假设目标运行状态中CPU的负载率为50％，则在一种可能的实施例中，可以是当仿真运行状态中CPU的负载率也为50％时认为仿真运行状态与目标运行状态匹配，也可以是当仿真运行状态中CPU的负载率低于50％时认为仿真运行状态与目标运行状态匹配，还可以是当仿真运行状态中CPU的负载率与50％相差小于10％时认为仿真运行状态与目标运行状态匹配。
在S604中，可以理解的是，当仿真运行状态与目标运行状态匹配时，可以认为当目标网络的网络参数为目标网络参数时，目标网络能够以预期中的运行状态运行，此时可以将目标网络参数作为目标网络的网络参数。
而当仿真运行状态与目标运行状态不匹配时，可以认为当目标网络的网络参数为目标网络参数时，目标网络无法以预期中的运行状态运行，此时不能够将目标网络参数作为目标网络的网络参数。
并且，在一种可能的实施例中，为便于用户对网络进行管理，可以展示仿真运行状态，用户根据所展示的仿真运行状态判断是否需要人工为目标网络进行优化。示例性的，如果所展示的仿真运行状态符合用户的预期，则可以认为可以根据目标网络参数自动对目标网 络进行优化，此时无需用户人工为目标网络进行优化。而如果所展示的仿真运行状态不符合用户的预期，则可以认为此时难以根据目标网络参数自动对目标网络进行优化，则可以由用户人工为目标网络进行优化。
当仿真运行状态与目标运行状态匹配时，将目标网络的网络参数设置为目标网络参数。当仿真运行状态与目标运行状态不匹配时，重新确定目标网络参数，并返回执行前述S602的步骤。
参见图7，图7所示为本申请实施例提供的网络管理装置的一种结构示意图，可以包括：
参数确定模块701，用于确定目标网络参数；
仿真模块702，用于将所述目标网络参数配置为仿真网络的网络参数，所述仿真网络为基于所述网络管理系统所管理的目标网络构建的；
验证模块703，用于获取所述仿真网络的仿真运行状态；
判断模块704，用于判断所述仿真运行状态是否与目标运行状态匹配；
配置模块705，用于如果所述仿真运行状态与所述目标运行状态匹配，则将所述目标网络参数配置为所述目标网络的网络参数。
在一种可能的实施例中，所述仿真模块702，还用于如果所述仿真运行状态与所述目标运行状态不匹配，重新确定新的目标网络参数，并返回执行所述将所述目标网络参数配置为仿真网络的网络参数，所述仿真网络为基于所述网络管理系统所管理的目标网络构建的步骤。
在一种可能的实施例中，参数确定模块701，具体用于获取目标运行状态；
将所述目标运行状态输入至推理模型，得到所述推理模型输出的目标网络参数，其中，所述推理模型为预先经过训练的用于根据所输入的目标运行状态据推理网络的网路参数的模型。
在一种可能的实施例中，所述装置还包括模型更新模块，用于获取所述目标网络的当前网络参数以及当前运行状态；
将所述当前运行状态输入至所述推理模型，得到所述推理模型输出的推理网络参数；
根据所述推理网络参数与所述当前网络参数之间的差异，更新所述推理模型。
本申请实施例还提供了一种电子设备，如图8所示，包括：
存储器801，用于存放计算机程序；
处理器802，用于执行存储器801上所存放的程序时，实现如下步骤：
确定目标网络参数；
将所述目标网络参数配置为仿真网络的网络参数，所述仿真网络为基于所述网络管理系统所管理的目标网络构建的；
获取所述仿真网络的仿真运行状态；
判断所述仿真运行状态是否与目标运行状态匹配；
如果所述仿真运行状态与所述目标运行状态匹配，则将所述目标网络参数配置为所述目标网络的网络参数。
上述电子设备提到的通信总线可以是外设部件互连标准(Peripheral Component Interconnect，PCI)总线或扩展工业标准结构(Extended Industry Standard Architecture，EISA)总线等。该通信总线可以分为地址总线、数据总线、控制总线等。为便于表示，图中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
通信接口用于上述电子设备与其他设备之间的通信。
存储器可以包括随机存取存储器(Random Access Memory，RAM)，也可以包括非易失性存储器(Non-Volatile Memory，NVM)，例如至少一个磁盘存储器。可选的，存储器还可以是至少一个位于远离前述处理器的存储装置。
上述的处理器可以是通用处理器，包括中央处理器(Central Processing Unit，CPU)、网络处理器(Network Processor，NP)等；还可以是数字信号处理器(Digital Signal Processor，DSP)、专用集成电路(Application Specific Integrated Circuit，ASIC)、现场可编程门阵列(Field-Programmable Gate Array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。
在本申请提供的又一实施例中，还提供了一种计算机可读存储介质，该计算机可读存储介质内存储有计算机程序，所述计算机程序被处理器执行时实现上述任一网络管理方法的步骤。
在本申请提供的又一实施例中，还提供了一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机执行上述实施例中任一网络管理方法。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。 当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机程序指令时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质，(例如，软盘、硬盘、磁带)、光介质(例如，DVD)、或者半导体介质(例如固态硬盘Solid State Disk(SSD))等。
需要说明的是，在本文中，诸如第一和第二等之类的关系术语仅仅用来将一个实体或者操作与另一个实体或操作区分开来，而不一定要求或者暗示这些实体或操作之间存在任何这种实际的关系或者顺序。而且，术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、物品或者设备不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、物品或者设备所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括所述要素的过程、方法、物品或者设备中还存在另外的相同要素。
本说明书中的各个实施例均采用相关的方式描述，各个实施例之间相同相似的部分互相参见即可，每个实施例重点说明的都是与其他实施例的不同之处。尤其，对于装置、电子设备、计算机可读存储介质以及计算机程序产品的实施例而言，由于其基本相似于方法实施例，所以描述的比较简单，相关之处参见方法实施例的部分说明即可。
以上所述仅为本申请的较佳实施例，并非用于限定本申请的保护范围。凡在本申请的精神和原则之内所作的任何修改、等同替换、改进等，均包含在本申请的保护范围内。

Claims (13)

  1. 一种网络管理系统，其特征在于，所述网络管理系统包括支撑单元、数据管理单元、业务服务单元以及展示单元；
    所述业务服务单元包括多组微服务子单元；
    每个所述微服务子单元用于提供一种微服务，并且每组所述微服务子单元所提供的微服务共同用于实现一种管理功能；
    所述支撑单元，通过相同的安装部署逻辑对所有所述微服务子单元进行安装部署，以实现为所有所述微服务子单元提供统一的部署平台；
    并且，所述支撑单元通过相同的运行管理逻辑对所有所述微服务子单元进行运行管理，以实现为所有所述微服务子单元提供统一的运行平台；
    所述数据管理单元通过相同的数据存储逻辑存储所有所述微服务子单元的数据，以实现为所有所述微服务子单元提供统一的数据存储服务；
    并且，所述数据管理单元通过将各类型的数据的访问逻辑封装为同一访问逻辑，并使得所有所述微服务子单元通过所述同一访问逻辑访问各类型的数据；
    所述展示单元通过展示主界面，并在所述主界面中设置用于跳转至每个所述微服务子单元的功能界面的接口，以实现为所有所述微服务子单元提供统一的门户框架服务。
  2. 根据权利要求1所述的系统，其特征在于，所述展示单元，还用于根据预先存储的访问权限与菜单项之间的对应关系，确定登录所述网络管理系统的账号的访问权限所对应的菜单项；并在所述主界面中展示所确定的菜单项。
  3. 根据权利要求1所述的系统，其特征在于，所述展示单元，还用于根据预先存储的访问权限与界面元素之间的对应关系，在主界面中确定登录所述网络管理系统的账号的访问权限所对应的界面元素；对主界面中所确定的界面元素的属性进行重新设置；展示经过重新设置后的主界面，其中，所述界面元素包括菜单项和/或微件。
  4. 根据权利要求1所述的系统，其特征在于，所述支撑单元，还用于对所有所述微服务子单元提供的所有微服务中使用的协议进行统一的消息建模和封装，以实现为所有所述微服务子单元提供统一的协议通道服务。
  5. 根据权利要求1所述的系统，其特征在于，所述支撑单元，还用于获取所有所述微服务子单元提供的所有微服务产生的日志，并通过相同的日志管理逻辑对所有获取到的日 志进行日志管理，以实现为所有所述微服务子单元提供统一的日志服务。
  6. 根据权利要求1所述的系统，其特征在于，所述数据管理单元，还用于为所述网络管理系统所管理的目标网络中的各个网络设备配置通用唯一识别码UUID，以使得每组所述微服务子单元提供的微服务所共同实现的管理功能按照网络设备的所述UUID对网络设备进行纳管。
  7. 一种网络管理方法，其特征在于，应用于权利要求1-6任一所述的网络管理系统，所述方法包括：
    确定目标网络参数；
    将所述目标网络参数配置为仿真网络的网络参数，所述仿真网络为基于所述网络管理系统所管理的目标网络构建的；
    获取所述仿真网络的仿真运行状态；
    判断所述仿真运行状态是否与目标运行状态匹配；
    如果所述仿真运行状态与所述目标运行状态匹配，则将所述目标网络参数配置为所述目标网络的网络参数。
  8. 根据权利要求7所述的方法，其特征在于，所述方法还包括：
    如果所述仿真运行状态与所述目标运行状态不匹配，重新确定新的目标网络参数，并返回执行所述将所述目标网络参数配置为仿真网络的网络参数的步骤，所述仿真网络为基于所述网络管理系统所管理的目标网络构建的步骤。
  9. 根据权利要求7所述的方法，其特征在于，所述确定目标网络参数，包括：
    获取目标运行状态；
    将所述目标运行状态输入至推理模型，得到所述推理模型输出的目标网络参数，其中，所述推理模型为预先经过训练的用于根据所输入的目标运行状态据推理网络的网路参数的模型。
  10. 根据权利要求9所述的方法，其特征在于，所述方法还包括：
    获取所述目标网络的当前网络参数以及当前运行状态；
    将所述当前运行状态输入至所述推理模型，得到所述推理模型输出的推理网络参数；
    根据所述推理网络参数与所述当前网络参数之间的差异，更新所述推理模型。
  11. 一种网络管理装置，其特征在于，应用于权利要求1-6任一所述的网络管理系统，所述装置包括：
    参数确定模块，用于确定目标网络参数；
    仿真模块，用于将所述目标网络参数配置为仿真网络的网络参数，所述仿真网络为基于所述网络管理系统所管理的目标网络构建的；
    验证模块，用于获取所述仿真网络的仿真运行状态；
    判断模块，用于判断所述仿真运行状态是否与目标运行状态匹配；
    配置模块，用于如果所述仿真运行状态与所述目标运行状态匹配，则将所述目标网络参数配置为所述目标网络的网络参数。
  12. 一种电子设备，其特征在于，包括：
    存储器，用于存放计算机程序；
    处理器，用于执行存储器上所存放的程序时，实现权利要求7-10任一所述的方法步骤。
  13. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质内存储有计算机程序，所述计算机程序被处理器执行时实现权利要求7-10任一所述的方法步骤。
PCT/CN2021/124558 2021-05-17 2021-10-19 一种网络管理系统、方法、装置及电子设备 WO2022242024A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
EP21940470.4A EP4161015A4 (en) 2021-05-17 2021-10-19 NETWORK MANAGEMENT SYSTEM, METHOD AND APPARATUS, AND ELECTRONIC DEVICE
US18/003,936 US20240297828A1 (en) 2021-05-17 2021-10-19 Network management system, method, and apparatus, and electronic device
JP2022577541A JP7453426B2 (ja) 2021-05-17 2021-10-19 ネットワーク管理システム、方法、装置及び電子機器

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202110532166.8 2021-05-17
CN202110532166.8A CN112994958B (zh) 2021-05-17 2021-05-17 一种网络管理系统、方法、装置及电子设备

Publications (1)

Publication Number Publication Date
WO2022242024A1 true WO2022242024A1 (zh) 2022-11-24

Family

ID=76336604

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/124558 WO2022242024A1 (zh) 2021-05-17 2021-10-19 一种网络管理系统、方法、装置及电子设备

Country Status (5)

Country Link
US (1) US20240297828A1 (zh)
EP (1) EP4161015A4 (zh)
JP (1) JP7453426B2 (zh)
CN (1) CN112994958B (zh)
WO (1) WO2022242024A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN117596157A (zh) * 2024-01-18 2024-02-23 厦门立林科技有限公司 物模型的动态构成方法

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112994958B (zh) * 2021-05-17 2021-08-13 新华三技术有限公司 一种网络管理系统、方法、装置及电子设备
CN113783929A (zh) * 2021-07-27 2021-12-10 武汉光庭信息技术股份有限公司 一种Web前端微服务架构的实现方法及其架构
CN114036113A (zh) * 2021-11-19 2022-02-11 深圳市商汤科技有限公司 设备管理方法、装置、电子设备及存储介质
CN114363221B (zh) * 2021-12-29 2024-05-03 武汉烽火信息集成技术有限公司 一种基于微服务系统的心跳检测方法、存储介质、电子设备及系统
CN116112369A (zh) * 2023-01-04 2023-05-12 中国联合网络通信集团有限公司 一种云网络运维管理系统、方法及装置

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107193546A (zh) * 2017-04-11 2017-09-22 国网天津市电力公司信息通信公司 一种微服务化业务应用系统
US20200396225A1 (en) * 2019-06-17 2020-12-17 Sap Se Microservice Deployment
US10892960B1 (en) * 2018-12-21 2021-01-12 Virtuozzo International Gmbh System and method of unifying and deploying a microservice-based application platform
CN112733359A (zh) * 2021-01-05 2021-04-30 北京三快在线科技有限公司 动力学模型验证方法、装置、介质、电子设备及无人设备
CN112787708A (zh) * 2021-01-25 2021-05-11 航天恒星科技有限公司 基于微服务的卫星地面站监控管理架构
CN112994958A (zh) * 2021-05-17 2021-06-18 新华三技术有限公司 一种网络管理系统、方法、装置及电子设备

Family Cites Families (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2000049788A (ja) 1998-05-27 2000-02-18 Matsushita Electric Ind Co Ltd フロ―制御方法ならびにそれを実行する通信要素および通信端末
JP3712196B2 (ja) 2002-02-25 2005-11-02 日本電信電話株式会社 パケット転送制御システムと方法およびそのプログラムと記録媒体ならびに通信装置
US20140046645A1 (en) * 2009-05-04 2014-02-13 Camber Defense Security And Systems Solutions, Inc. Systems and methods for network monitoring and analysis of a simulated network
JP2016066945A (ja) 2014-09-25 2016-04-28 株式会社日立製作所 管理装置、ネットワーク装置の管理方法及びプログラム
CN106533804A (zh) 2016-12-22 2017-03-22 成都西加云杉科技有限公司 一种网络运营支撑系统
CN109747682B (zh) * 2018-01-09 2019-12-10 比亚迪股份有限公司 轨道交通弱电一体化系统
US11321337B2 (en) * 2018-06-04 2022-05-03 Cisco Technology, Inc. Crowdsourcing data into a data lake
US10579370B2 (en) * 2018-08-03 2020-03-03 EMC IP Company LLC Method to disintegrate a monolith service to microservices
CN110209719B (zh) * 2019-05-20 2023-06-16 华南理工大学 一种基于微服务架构的多种数据库统一访问系统及方法
CN110809017B (zh) * 2019-08-16 2022-02-25 云南电网有限责任公司玉溪供电局 一种基于云平台和微服务构架的数据分析应用平台系统
US20210021533A1 (en) 2020-09-25 2021-01-21 Francesc Guim Bernat Intelligent data forwarding in edge networks

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107193546A (zh) * 2017-04-11 2017-09-22 国网天津市电力公司信息通信公司 一种微服务化业务应用系统
US10892960B1 (en) * 2018-12-21 2021-01-12 Virtuozzo International Gmbh System and method of unifying and deploying a microservice-based application platform
US20200396225A1 (en) * 2019-06-17 2020-12-17 Sap Se Microservice Deployment
CN112733359A (zh) * 2021-01-05 2021-04-30 北京三快在线科技有限公司 动力学模型验证方法、装置、介质、电子设备及无人设备
CN112787708A (zh) * 2021-01-25 2021-05-11 航天恒星科技有限公司 基于微服务的卫星地面站监控管理架构
CN112994958A (zh) * 2021-05-17 2021-06-18 新华三技术有限公司 一种网络管理系统、方法、装置及电子设备

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP4161015A4

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN117596157A (zh) * 2024-01-18 2024-02-23 厦门立林科技有限公司 物模型的动态构成方法
CN117596157B (zh) * 2024-01-18 2024-05-14 厦门立林科技有限公司 物模型的动态构成方法、设备和存储介质

Also Published As

Publication number Publication date
CN112994958B (zh) 2021-08-13
US20240297828A1 (en) 2024-09-05
JP7453426B2 (ja) 2024-03-19
EP4161015A4 (en) 2024-01-03
CN112994958A (zh) 2021-06-18
JP2023531196A (ja) 2023-07-21
EP4161015A1 (en) 2023-04-05

Similar Documents

Publication Publication Date Title
WO2022242024A1 (zh) 一种网络管理系统、方法、装置及电子设备
US10635433B2 (en) Cross application behavior customization
US10764290B2 (en) Governed access to RPA bots
EP3511822A1 (en) Method and system for managing access to artifacts in a cloud computing environment
US20230054057A1 (en) Login Method and System Based on Cloud Application Instance, and Related Device
US8321549B2 (en) Action execution management for service configuration items
KR102368200B1 (ko) 장치 설계를 위한 코드 모듈 선택
US20240045842A1 (en) Integrated transition control center
US8478850B2 (en) Platform component architecture (PCA)-based system, method and application designer
US20200382442A1 (en) Method and system for managing sub-tenants in a cloud computing environment
CN111556158B (zh) 物联网平台的接入方法、接入装置、接入设备及存储介质
US9516700B1 (en) Cloud-based controller for managing access points
US11882154B2 (en) Template representation of security resources
US11886939B2 (en) System, device, method and datastack for managing applications that manage operation of assets
US9455879B1 (en) Validating changes to attributes for computing resources
US11757976B2 (en) Unified application management for heterogeneous application delivery
JP2016115182A (ja) 仮想機器試験装置、仮想機器試験方法及び仮想機器試験プログラム
US11734381B2 (en) Efficient downloading of related documents
US20240272926A1 (en) Building management system with integration and containerization of gateway components on edge devices
US12003963B2 (en) Mobile provisioning of a data center asset in a data center connectivity management environment
US20240118907A1 (en) Scalable specification and self-governance for autonomous databases, cluster databases and multi-tenant databases in cloud and on-prem environment
US11818183B2 (en) System and method for workspace sharing
Martí Luque Developing and deploying NFV solutions with OpenStack, Kubernetes and Docker
JP5975910B2 (ja) データ処理装置、データ処理方法、データ処理プログラムおよび連携業務システム
CN116595057A (zh) 数据查询方法、装置、计算机设备及计算机程序产品

Legal Events

Date Code Title Description
ENP Entry into the national phase

Ref document number: 2022577541

Country of ref document: JP

Kind code of ref document: A

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

Ref document number: 21940470

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2021940470

Country of ref document: EP

Effective date: 20221230

NENP Non-entry into the national phase

Ref country code: DE