CN116708535A

CN116708535A - Network device controller, method, electronic device, storage medium and system

Info

Publication number: CN116708535A
Application number: CN202310903979.2A
Authority: CN
Inventors: 石鸿伟; 徐逸群; 陈庆强; 黄韬
Original assignee: Network Communication and Security Zijinshan Laboratory
Current assignee: Network Communication and Security Zijinshan Laboratory
Priority date: 2023-07-20
Filing date: 2023-07-20
Publication date: 2023-09-05

Abstract

The invention discloses a network device controller, a network device controller method, an electronic device, a storage medium and a network device system. The network device controller is used for managing a plurality of network devices; the controller is provided with a core service and at least two southbound services, wherein a single southbound service is used for network equipment of a nanotube setting type; the core service is used for processing the service request and generating service processing data in a standard format according to a preset model; the southbound service is used for converting business processing data into data aiming at the network equipment of the nano tube and sending the data to the network equipment of the nano tube; the southbound service maintains long connections with managed network devices based on network configuration protocols. According to the scheme, the core service and the southbound service are separated, the core service processes the service according to the preset model, the southbound service is used for butting specific network equipment, service persistence is improved based on long connection, continuity management of different types of network equipment is supported, and the southbound service has good expansibility and adaptability, and system service processing pressure is reduced.

Description

Network device controller, method, electronic device, storage medium and system

Technical Field

The embodiment of the invention relates to the technical field of Internet, in particular to a network equipment controller, a network equipment method, electronic equipment, a storage medium and a network equipment system.

Background

A software defined network (Software Defined Network, SDN) is a network architecture that is essentially a separation of control plane and data plane and open programmability. Thereby realizing flexible control of network flow and enabling the network to become more intelligent. An SDN controller is a control layer in a software defined network. For the south direction, collecting network data such as topology state, flow statistics, routing table items and the like of the south-direction network equipment, and issuing configuration to the south-direction equipment for flow control; and for north, providing an interface for data query and service configuration. In the process of increasing the network scale and network service, the SDN controller needs to establish connection with more network devices, and send configuration messages and collect configuration and performance data to the network devices. These connections cause a significant amount of server context switching, traffic interactions with the network devices, and resulting performance data put pressure on the data processing, transmission, and memory of the controller.

In some scenarios, controllers may be deployed in a distributed fashion, but existing distributed frameworks may arbitrarily distribute requests from north to one service. The result of this is that, for a specific configuration command of a network device, different services may be allocated each time, and then these services need to be connected to the network device, and the network device models are various, and devices produced by different manufacturers have a certain difference in implementing the same function, and because the models and software versions are different, there is a greater or lesser difference, and difficulty in the process of docking is present. In summary, when the SDN controller faces the problem of increasing the network size and complexity, the expansibility and adaptability are poor, frequent connection and switching affect the service continuity, and the system pressure is increased.

Disclosure of Invention

The invention provides a network equipment controller, a method, electronic equipment, a storage medium and a system, which are used for ensuring service persistence and improving the expansibility and suitability of network equipment management.

In a first aspect, an embodiment of the present invention provides a network device controller configured to manage a plurality of network devices;

the network equipment controller is provided with a core service and at least two southbound services, and a single southbound service is used for network equipment of a nanotube setting type;

the core service is used for processing the service request and generating service processing data in a standard format according to a preset model;

the southbound service is used for converting the business processing data in the standard format into data for the network equipment of the nano tube and sending the data to the network equipment of the nano tube;

the southbound service maintains a long connection with managed network devices based on network configuration protocols.

In a second aspect, an embodiment of the present invention provides a network device management method, including:

processing a service request through a core service and generating service processing data in a standard format according to a preset model;

and converting the business processing data in the standard format into data for the network equipment of the nano tube through a southbound service, and sending the data to the network equipment of the nano tube.

In a third aspect, an embodiment of the present invention provides an electronic device, including:

at least one processor; and

a memory communicatively coupled to the at least one processor; wherein, the liquid crystal display device comprises a liquid crystal display device,

the memory stores a computer program executable by the at least one processor to enable the at least one processor to perform the network device management method of claim 10.

In a fourth aspect, an embodiment of the present invention provides a computer-readable storage medium, on which a computer program is stored, which when executed by a processor implements the network device management method according to the third aspect.

In a fifth aspect, an embodiment of the present invention provides a network device management system, including: a plurality of network devices and an electronic device as described in the fourth aspect.

The embodiment of the invention provides a network equipment controller, a method, electronic equipment, a storage medium and a system, wherein the controller is used for managing controllers of a plurality of network equipment; the network equipment controller is provided with a core service and at least two southbound services, and a single southbound service is used for network equipment of a nanotube setting type; the core service is used for processing the service request and generating service processing data in a standard format according to a preset model; the southbound service is used for converting the business processing data in the standard format into data for the network equipment of the nano tube and sending the data to the network equipment of the nano tube; the southbound service maintains a long connection with managed network devices based on network configuration protocols. According to the technical scheme, the core service is separated from the southbound service, the core service processes the service according to the preset model, the southbound service is used for docking specific network equipment, the management of different types of network equipment is supported, the service continuity is ensured, and the expansibility and the suitability of the network equipment management are improved.

Drawings

The above and other features, advantages, and aspects of embodiments of the present disclosure will become more apparent by reference to the following detailed description when taken in conjunction with the accompanying drawings. The same or similar reference numbers will be used throughout the drawings to refer to the same or like elements. It should be understood that the figures are schematic and that elements and components are not necessarily drawn to scale.

Fig. 1 is a schematic structural diagram of a network device controller according to a first embodiment of the present invention;

fig. 2 is a schematic diagram of a distributed management framework of a network device according to a second embodiment of the present invention;

fig. 3 is a schematic diagram of a relationship between a network device maintained by a controller and a southbound service according to a second embodiment of the present invention;

fig. 4 is a schematic diagram of a controller service management framework according to a second embodiment of the present invention;

fig. 5 is a flowchart of a network device management method according to a second embodiment of the present invention;

fig. 6 is a schematic structural diagram of an electronic device according to a third embodiment of the present invention;

fig. 7 is a schematic structural diagram of a network device management system according to a fourth embodiment of the present invention.

Detailed Description

The invention is described in further detail below with reference to the drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of the invention and are not limiting thereof. Furthermore, embodiments of the invention and features of the embodiments may be combined with each other without conflict. It should be further noted that, for convenience of description, only some, but not all of the structures related to the present invention are shown in the drawings.

Before discussing exemplary embodiments in more detail, it should be mentioned that some exemplary embodiments are described as processes or methods depicted as flowcharts. Although a flowchart depicts steps as a sequential process, many of the steps may be implemented in parallel, concurrently, or with other steps. Furthermore, the order of the steps may be rearranged. The process may be terminated when its operations are completed, but may have additional steps not included in the figures. The processes may correspond to methods, functions, procedures, subroutines, and the like.

It should be noted that the concepts of "first," "second," and the like in the embodiments of the present invention are merely used to distinguish between different devices, modules, units, or other objects, and are not intended to limit the order or interdependence of functions performed by the devices, modules, units, or other objects.

Example 1

Fig. 1 is a schematic structural diagram of a network device management system according to a first embodiment of the present invention. The present embodiment is applicable to a case of managing network devices by using a controller, where the controller mainly refers to an SDN controller. As shown in fig. 1, the network device management system includes: a controller 10 for controlling a plurality of network devices; the controller 10 is deployed with a core service 110 and at least two southbound services 120, a single southbound service 120 for a network device 20 of the nanotube-provisioned type; the core service 110 is used for processing the service request and generating service processing data in a standard format according to a preset model; the southbound service 120 is configured to convert the standard format business process data into data for the network device 20 of the nanotube and send the data to the network device 20 of the nanotube; southbound service 120 maintains long connections with managed network devices 20 based on network configuration protocols.

In this embodiment, the functions of the controller 10 are split into a plurality of micro services, including a core service 110 for traffic analysis processing, but not touching the device, and a southbound service 120 for delivering commands delivered by the core service 110 to the network device 20 without awareness of specific traffic.

One southbound service 120 may establish a connection with a network device 20 of a set type (also referred to as a southbound device) in a network, perform operations such as configuration issue, inquiry, performance collection, and consolidated reporting, and different southbound services 120 may be used to interface with different types of network devices 20, and it may also be understood that one southbound service 120 may manage a specific network device or devices 20 of one or more types. The southbound services 120 may be divided into different types of southbound services 120 according to the type of network device 20 docked; or may be divided into different instances of the same southbound service 120 because of the multiple instance deployment of a certain type of southbound service 120. Different types of southbound services 120 expose the same interfaces to the outside, receive the same data from core services 110, and after respective processing, perform configuration with inconsistent forms but consistent functions on different network devices 20 through configuration protocols supported by the corresponding types of network devices 20. Configuration protocols include, but are not limited to, network configuration protocol (Netconf), secure network transport protocol (Ssh), resource expression layer transformation (Representational State Transfer, REST) interface protocol, and the like.

In this embodiment, the southbound service 120 may maintain long connection with the managed network device based on the network configuration protocol, so as to ensure service continuity, avoid frequent connection and switching, and save network resources in a multi-service scenario. In particular, a transmission control protocol (Transmission Control Protocol, TCP) may be employed to maintain a TCP long connection (Keepalive).

The core service 110 provides a business interface and performance data query to the north and then assigns business configurations to the corresponding south-oriented services 120. For the core service 110, only service allocation and data storage inquiry are needed, so that the performance requirement is small; the southbound service 120 is responsible for interacting with the corresponding type of network device 20, requiring more performance resources.

In this embodiment, to achieve the adaptation of different network devices 20, a set of preset models is established for the interaction between the core service 110 and the south-oriented service 120. The preset model may be understood as a unified and standard service processing model that is built in advance, and may be used to process service requests to obtain service processing data in a standard format, and may be used to describe configuration and management operations that need to be performed on any type of network device 20, so that the southbound service 120 configures and manages the network device 20. On this basis, the core service 110 is shielded from the differences between different network devices 20, and when a new network device 20 is docked, the core service 110 is not required to be changed, and only a new type of southbound service 120 is required to be added, so that the adaptation to the new network device 20 is easier. Specifically, the data sent by the core service 110 to the southbound service 120 follows a pre-set model that supports three configuration operations, new, delete, modify, and query operations. When performing configuration operation, the southbound service 120 translates configuration data of the preset model into a configuration command of the network equipment of the network to be accommodated and issues the configuration command; in the query operation, the southbound service 120 may translate the configuration or performance data returned by the managed network device back into data that conforms to the preset model, and return the data to the core service 110 for unified processing.

The core service 110 may make service calls in a manner that bypasses the distributed system interior gateway such that operational commands to a set type of network device 20 are received by the southbound service 120 that manages the device.

When the network scale is enlarged, the number of servers can be increased, and new southbound services 120 or new southbound services 120 instances can be deployed on the servers, so that the pressure of a single southbound service 120 or a single instance can be reduced, and service capacity expansion can be realized. And simultaneously, the single core service 110 can perform service overall, so that complex service conditions of the cross-controller are avoided.

The first embodiment of the invention provides a network device management system, which designs a distributed network device driving management framework of an SDN controller by utilizing a micro-service idea, separates a core service from a southbound service, processes services according to a preset model, coordinates service distribution, and the services are always in a management domain of the controller without complex services crossing the controller; the southbound service is used for interfacing with specific types of network devices, and a part of network devices in a single southbound service management system can realize the management of complex networks; and the data transmission between the core service and the south-oriented service is realized based on a preset model, a unified docking standard is used, a call chain from north to south is formed, an expandable interface is opened, the management of different types of network equipment and the expansion of the services are supported, and the expansibility and the suitability of the network equipment management are improved.

Optionally, the southbound service 120 is also configured to: the backhaul data of the managed device is converted into data satisfying the preset model and returned to the core service 110. Specifically, the southbound service 120 may receive the backhaul data from the network device 20 of the nanotube, refine the backhaul data, and transmit the backhaul data to the core service 110 in a standard format suitable for a preset model, where the core service 110 performs unified processing on the backhaul data, without performing special processing on different types of network devices 20.

Alternatively, the southbound service 120 is deployed with at least one instance, with a single instance corresponding to a specified type of network device 20. In this embodiment, the south-oriented service 120 may deploy one or more instances, and the network devices 20 in the system may be distributed to the instance nanotubes of the plurality of south-oriented services 120 on a near average, with each south-oriented service 120 only having to establish a connection with the network device 20 to which it is hosted. Illustratively, different instances of the same southbound service 120 each manage a portion of the corresponding types of network devices hosted by that southbound service 120, wherein one instance may be used to manage at least one type of network device. In the case where the type of network device 20 is explicit, the network device 20 may be hosted by an instance of the corresponding southbound service.

Alternatively, by controlling the number of south-facing services 120 and deployed instances, the upper limit of the number of controller nanotube network devices 20 may be increased.

Optionally, the southbound service 120 is also configured to receive alert information of the network device 20. Specifically, the south service 120 may interact with the network device 20 using protocols such as Netconf, secure Ssh, REST interface, and the like. For the Netconf protocol, among other things, the southbound service 120 maintains a TCP long connection with the network device 20 and the southbound service 120 receives alert information from the network device 20 (Netconf Notification).

Optionally, the load balancing rule is satisfied among multiple instances of the southbound service 120, and the multiple instances of the southbound service 120 are disaster recovery.

Specifically, network device 20 may be approximately equally allocated to multiple instances of southbound service 120 for nanotubes, with multiple instances being load-sharing and disaster-prone to each other. When an instance of a southbound service 120 fails, the network device 20 managed by the instance is released, and other instances of the southbound service 120 or other southbound services 120 can reacquire the management rights of the released network device 20, thereby achieving the purpose of disaster recovery. Load sharing and disaster recovery can be achieved through a designed distributed lock mechanism.

In this embodiment, a load balancing algorithm is run on the south service, and the load balancing algorithm is responsible for calculating and distributing which devices can be managed by the south service, so that the network devices with the same or similar quantity of the south service nanotubes are provided; meanwhile, when the instance of the southbound service sends a fault, network equipment managed by the faulty instance can be quickly taken over by other southbound services, and the service function can be quickly recovered. In addition, after fault recovery or capacity expansion, part of network equipment can be distributed to new southbound services, and the load of each southbound service can be automatically adjusted. For example, the operation may be performed on each added network device according to the number of network devices and deployed southbound service instances, and according to the calculation result, it is determined which southbound service instance a specific network device should be managed by.

Optionally, the instance is configured to establish a connection with the fixed type network device 20 after obtaining the management authority of the fixed type network device 20; one network device 20 is connected to one instance at a time. In particular, based on a distributed lock mechanism,

an instance of a southbound service 120 may not establish a connection with network device 20 until it has acquired the management rights of network device 20, and the same network device 20 may not be hosted by both instances of southbound service 120.

In addition, the connection between the south-oriented device 120 and the network device 20 can be repeatedly used without dismantling, and only one south-oriented service 120 is guaranteed to be connected with one network device 20.

Optionally, for the network device 20 to be managed, the core service 110 is further configured to add a device type layer and a device internet protocol IP layer node according to the device type and the device management address of the network device 20 to be managed based on the distributed lock, and send a node adding message to each southbound service 120; one example of a southbound service 120 is also used to nanotube network devices 20 to be managed by adding service registration layer nodes according to the node addition message.

In particular, distributed locks are a mechanism for controlling the synchronized access of shared resources between distributed systems that can utilize lock directories to define the content and associations between nodes at each level. The core service 110 may add a device type layer and a device IP layer node according to a device type and a device management address of the network device 20 to be managed (i.e. an IP port address for managing the network device), and send node addition messages to the southbound services 120, and after each southbound service acquisition node adds a message, a load balancing algorithm may be used to calculate which southbound service the network device is specifically managed by. The load balancing algorithm allocates a specific southbound service instance to a specific network device according to the network device information and the number of southbound service instances of the network device. After each southbound service receives the message, if the network device should be managed by itself, a node corresponding to the network device is added in the service registration layer to perform the management, otherwise, the message is ignored.

Optionally, the core service 110 is further configured to write the encrypted device information into the device IP layer node during the process of adding the device IP layer node; the instance of the southbound service 120 is also configured to obtain authentication information required to connect to the network device 20 by decrypting the device information, thereby authenticating with the network device 20, the authentication being successful through the instant nano tube; the instance of the southbound service 120 is further configured to write instance information into the service registration layer node when the service registration layer node is added; the core service 110 is also configured to send traffic handling data for the network device 20 based on the service registration layer node information to an instance of the southbound service 120 that manages the network device 20.

Optionally, if the service registration layer node does not receive the heartbeat information of the instance of the southbound service 120 within a set time, triggering a deletion operation of the service registration layer node; after the service registration layer node is deleted, another southbound service instance temporarily manages the corresponding network device; if the south-oriented service instance resumes available, the temporary managed network device is released and the network device is restored by the south-oriented service instance.

Specifically, the service registration layer node maintains heartbeat with the southbound service 120 instance, and if heartbeat information (also referred to as health check information) from the southbound service 120 instance is not received within a set time, the deletion operation of the service registration layer node is triggered. When a failure heartbeat interrupt occurs to an instance of a southbound service, the network device under the southbound service can be redistributed based on a load balancing algorithm, and another appropriate southbound service instance (another appropriate southbound service instance may be available, any one of southbound service instances with relatively smaller current load) can temporarily register and take over the batch of network devices, and in this process, a service registration layer node is added to the other southbound service instance to complete temporary nanotubes. When the failure removal recovery of the original southbound service instance is available, the southbound service instance for temporary takeover releases the network device for temporary takeover (corresponding service registration layer node can be deleted in the process) under the influence of the load balancing algorithm, and the southbound service instance after recovery is taken over again (service registration layer node can be added in the process). It should be noted that, based on the load balancing algorithm, the number of available southbound services and examples in the system and the corresponding load can be counted in real time, and the distribution relationship between the network device and each southbound service and example can also be monitored. On this basis, once the failure-removal restoration of the original southbound service instance is found available, the temporarily taken over network device may be preferentially taken over again by the restored southbound service instance.

Fig. 2 is a schematic diagram of a distributed management framework of a network device according to a second embodiment of the present invention. As shown in fig. 2, the dashed box represents a cluster server, and the solid internal box represents a micro service instance, where the device is mainly a network device. In the distributed cluster, core services are deployed in a multi-instance mode to perform load sharing. When the service request reaches any core service, the core service calls the southbound service corresponding to the network equipment to issue the service. The southbound service A and the southbound service B are deployed in multiple instances, and the southbound service C is deployed in a single instance. When the first server fails, the southbound service instance 1 corresponding to the A, B type device fails, and the managed network devices can be respectively taken over by the southbound service instance 2 corresponding to the A, B type device, so that the disaster resistance of the southbound service is improved.

When the type C network equipment is added into the network, starting the corresponding southbound service instance of the type C equipment, and expanding the new network equipment type. If the number of the type A network devices continues to increase, the southbound service instance of the two type A devices cannot bear pressure, and if the server III has idle resources, the instance III can be started to expand the capacity of the devices of the same type; if the third server has no idle resource, the third server can be newly added to expand the capacity of the cluster, and then the new server expands the capacity of the south service.

Fig. 3 is a schematic diagram of a relationship between a network device maintained by a controller and a southbound service according to a second embodiment of the present invention. As shown in fig. 3, the devices therein are mainly referred to as network devices. When a network device is declared to the controller to require nanotubes, the core service adds device type layer and device IP layer nodes according to the device type and management IP respectively. After the device IP layer node is created, the corresponding message is sent to all southbound service instances, one of which will nanotube the device by adding a service registration layer node. For example, a network device IP node with type a network management IP 172.171.1.1 is added, and one example of a type a network device southbound service would add a node at the service registration layer.

When the core service adds a device IP layer node for the network device, the encrypted device information is written into the device IP layer node, and the southbound service obtains authentication information required by connecting the network device by decrypting the device information. When the service registration layer node is added to the southbound service instance, the information of the service instance is written into the service registration layer node, and the core node can send the operation to the network equipment to the southbound service instance for managing the network equipment based on the information of the service registration layer node.

The node deleted message is sent to the surviving southbound service instance, and one of the remaining southbound service instances completes the process of adding the service registration layer node to complete the nanotube.

When the capacity expansion of the network equipment of the same type is carried out, a new service instance is deployed, the new network equipment is led into the core service, the new service instance with small load is subjected to the equipment nano-tube preferentially, and the capacity expansion of the network equipment of the same type in the network is completed.

When a new type of network equipment is introduced, the type of southbound service instance can be deployed, and the equipment is introduced into a controller (the order is not sequential), so that capacity expansion can be completed rapidly.

Fig. 4 is a schematic diagram of a controller service management framework according to a second embodiment of the present invention. As shown in fig. 4, the controller core service converts the received service requirement into a requirement for network resources through network planning, and then splits the service. Such as planning of resources for routes, access points, tunnels, etc. These planned resources, configurations are in turn passed to the south-oriented service for processing. When the configuration of the southbound service fails, the core service can perform configuration rollback in reverse order.

Before the core service transmits the configuration to the south service, model conversion is needed to convert the configuration into a standard preset model (also called unified model). The default model describes each resource involved in configuration and the operation corresponding to that resource and is independent of the particular network device.

In the southbound service, a preset model configuration module load receives a configuration based on a preset model and converts the configuration into a configuration command of a specific network device. The module maintains a library of configuration modules, retrieves the configuration module that handles the model according to the specific configuration involved in the configuration of the preset model, converts the preset model into the configuration of the network device 20, and sends the configuration module to the network device through the session management module to obtain device feedback.

The southbound service also provides an extension of the configuration module library through a serial peripheral interface (Serial Peripheral Interface, SPI). It is assumed that a certain network device does not support a certain service of the core service, but after a software upgrade of the network device, the network device may support a new service. At this time, the southbound service can receive the preset model configuration from the core service, but cannot perform model configuration. Through SPI interface provided by south service, third party can realize configuration module by oneself or obtain latest configuration module, inject into configuration module library of south service to support new business. In addition, through the SPI interface, the own configuration module of the southbound service can be rewritten to meet specific requirements.

If the configuration involves a scene not covered by the preset model, the southbound service provides a three-party configuration processing module, and the third party system can directly interact with the network equipment through a configuration protocol supported by the southbound service.

The session management scheme and the registration mechanism of the network device in the embodiment can be used for solving the problems of saving long connection resources and addressing a plurality of southbound services in a multi-service scenario.

The system of the embodiment is suitable for management control of the SDN controller on backbone network routing equipment. A set of preset models based on Openconfig is established. The pre-set model may be used with the main protocol or technology of the controller such as: border gateway protocol (Border Gateway Protocol, BGP), three-Layer virtual private network (Layer 3Virtual Private Network,L3VPN), two-Layer virtual private network (Layer 2Virtual Private Network,L2VPN), traffic engineering-based Segment Routing-Traffic Engineering, SR-TE), IPv6 Segment Routing (Segment Routing IPv6 Policy, SRv6 Policy), and the like are generally described. Because the preset model is based on a standard protocol, any function can be realized by the existing equipment or network equipment possibly appearing in the future, and descriptions can be found in the standard model. Furthermore, even if the network device may not temporarily support some functions in the preset model due to heterogeneous model, hardware and software, in the upgrading process, for example, after a hardware module is added or a software version is upgraded, some new functions are realized or the function configuration is modified.

The network equipment management system of the embodiment ensures that the interface provided by the core service of the controller is stable through the difference between the southbound equipment and the southbound equipment, and the interface can be used directly or butted through a manager, and the interface can be kept effective for a long time after the butting is completed; the quantity of the southbound devices is expanded through southbound service multiple instances, and the controller core service manages complete business information, so that overhead across controllers is eliminated; the core service and the southward service are docked through the preset model, the universality is strong, the southward service realizes the conversion from the preset model to southward equipment configuration, and the adaptation can be completed; in addition, the interface is provided to allow the external providing model-configuration conversion scheme to be developed secondarily, so that the expansibility is strong.

Example two

Fig. 5 is a flowchart of a network device management method according to a first embodiment of the present invention, where the embodiment is applicable to a case of managing network devices. In particular, the network device management system may be implemented by a network device management method, which may be implemented in software and/or hardware and integrated in an electronic device. An SDN controller may be deployed in the electronic device. It should be noted that technical details not described in detail in this embodiment may be found in any of the above embodiments.

Specifically, as shown in fig. 5, the method specifically includes the following steps:

s310, processing the service request through the core service and generating service processing data in a standard format according to a preset model.

S320, converting the business processing data in the standard format into data for the network equipment of the nano tube through the south-oriented service, and sending the data to the network equipment of the nano tube.

S330, long connection is kept between the network configuration protocol and the network equipment of the nano-tube.

It should be noted that, the embodiment does not limit the execution sequence of S330 and other steps, and maintains a long connection with the network device of the nanotube, and may extend through the processes of processing the service request, generating the service processing data, and converting and transmitting the data.

The method of the embodiment can separate the core service from the southbound service, the core service processes the service according to the preset model, the southbound service is used for butting specific network equipment and improving the service persistence based on long connection, supports the continuity management of different types of network equipment, has better expansibility and suitability, and reduces the service processing pressure of the system.

Optionally, the method further comprises: and converting the returned data of the nano-tube equipment into data meeting the preset model through a southbound service and returning the data to the core service.

Optionally, the southbound service is deployed with at least one instance, a single instance corresponding to a specified type of network device.

Optionally, the method further comprises: and receiving the alarm information of the network equipment through the southbound service.

Optionally, the multiple instances of the southbound service meet load balancing rules, and the multiple instances of the southbound service are disaster recovery.

Optionally, the method further comprises: after acquiring the management authority of the network equipment of the appointed type through the example of the southbound service, establishing connection with the network equipment of the appointed type; a network device is connected to one of the instances at a time.

Optionally, the method further comprises:

for network equipment to be managed, respectively adding equipment type layer and equipment Internet Protocol (IP) layer nodes according to the equipment type and equipment management address of the network equipment to be managed through a core service based on a distributed lock, and sending node adding information to each southbound service;

and carrying out nano-tube on the network equipment to be nano-tube by adding a service registration layer node through an example of a south-oriented service.

Optionally, the method further comprises:

Writing encrypted equipment information into the equipment IP layer node through core service in the process of adding the equipment IP layer node;

decrypting the device information through an instance of the southbound service to obtain authentication information required to connect to the network device;

when a service registration layer node is added through an instance of a southbound service, writing instance information into the service registration layer node;

the node information is viewed by a core service to send operations on the network device to an instance of a southbound service that manages the network device.

Optionally, the method further comprises:

if the heartbeat information of the southbound service instance is not received within the set time, triggering the deleting operation of the service registration layer node;

after the service registration layer node is deleted, another southbound service instance temporarily manages the corresponding network device;

if the south-oriented service instance resumes available, the temporary managed network device is released and the network device is restored by the south-oriented service instance.

The network device management method in this embodiment and the network device management system in any of the foregoing embodiments belong to the same inventive concept, and have the same or corresponding beneficial effects.

Example III

Fig. 6 shows a schematic diagram of an electronic device 100 that may be used to implement an embodiment of the invention. Electronic device 100 is intended to represent various forms of digital computers, such as laptops, desktops, workstations, personal digital assistants, servers, blade servers, mainframes, and other appropriate computers. The electronic device 100 may also represent various forms of mobile devices. The components shown herein, their connections and relationships, and their functions, are meant to be exemplary only, and are not meant to limit implementations of the inventions described and/or claimed herein.

As shown in fig. 6, the electronic device 100 includes at least one processor 11, and a memory, such as a Read Only Memory (ROM) 12, a Random Access Memory (RAM) 13, etc., communicatively connected to the at least one processor 11, in which the memory stores a computer program executable by the at least one processor, and the processor 11 may perform various appropriate actions and processes according to the computer program stored in the Read Only Memory (ROM) 12 or the computer program loaded from the storage unit 18 into the Random Access Memory (RAM) 13. In the RAM 13, various programs and data required for the operation of the electronic device 100 can also be stored. The processor 11, the ROM 12 and the RAM 13 are connected to each other via a bus 14. An input/output (I/O) interface 15 is also connected to bus 14.

A number of components in the electronic device 100 are connected to the I/O interface 15, including: an input unit 16 such as a keyboard, a mouse, etc.; an output unit 17 such as various types of displays, speakers, and the like; a storage unit 18 such as a magnetic disk, an optical disk, or the like; and a communication unit 19 such as a network card, modem, wireless communication transceiver, etc. The communication unit 19 allows the electronic device 100 to exchange information/data with other devices via a computer network, such as the internet, and/or various telecommunication networks, wireless networks.

The processor 11 may be a variety of general and/or special purpose processing components having processing and computing capabilities. Some examples of processor 11 include, but are not limited to, a Central Processing Unit (CPU), a Graphics Processing Unit (GPU), various specialized Artificial Intelligence (AI) computing chips, various processors running machine learning model algorithms, digital Signal Processors (DSPs), and any suitable processor, controller, microcontroller, etc. The processor 11 performs the various methods and processes described above.

In some embodiments, the network device management method may be implemented as a computer program tangibly embodied on a computer-readable storage medium. One or more steps of the methods described above may be performed when the computer program is executed by a processor. Alternatively, in other embodiments, the processor may be configured to perform the network device management method in any other suitable manner (e.g., by means of firmware).

Various implementations of the systems and techniques described here above may be implemented in digital electronic circuitry, integrated circuit systems, field Programmable Gate Arrays (FPGAs), application Specific Integrated Circuits (ASICs), application Specific Standard Products (ASSPs), systems On Chip (SOCs), load programmable logic devices (CPLDs), computer hardware, firmware, software, and/or combinations thereof. These various embodiments may include: implemented in one or more computer programs, the one or more computer programs may be executed and/or interpreted on a programmable system including at least one programmable processor, which may be a special purpose or general-purpose programmable processor, that may receive data and instructions from, and transmit data and instructions to, a storage system, at least one input device, and at least one output device.

A computer program for carrying out methods of the present invention may be written in any combination of one or more programming languages. These computer programs may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus, such that the computer programs, when executed by the processor, cause the functions/acts specified in the flowchart and/or block diagram block or blocks to be implemented. The computer program may execute entirely on the machine, partly on the machine, as a stand-alone software package, partly on the machine and partly on a remote machine or entirely on the remote machine or server.

In the context of the present invention, a computer-readable storage medium may be a tangible medium that can contain, or store a computer program for use by or in connection with an instruction execution system, apparatus, or device. The computer readable storage medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. Alternatively, the computer readable storage medium may be a machine readable signal medium. More specific examples of a machine-readable storage medium would include an electrical connection based on one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

Example IV

Fig. 7 is a schematic structural diagram of a network device management system according to a fourth embodiment of the present invention. As shown in fig. 7, the system includes: a plurality of network devices 20 and an electronic device 100 as described in any of the embodiments above. The network device controller of the electronic device 100 is deployed with a core service and at least two southbound services, a single southbound service for a network device of a nanotube-set type; the core service is used for processing the service request and generating service processing data in a standard format according to a preset model; the southbound service is used for converting the business processing data in the standard format into data for the network equipment of the nano tube and sending the data to the network equipment of the nano tube; southbound service 120 maintains long connections with managed network devices based on network configuration protocols.

The network device management system provided in the seventh embodiment may be used to implement the network device management method provided in any of the foregoing embodiments, and has corresponding functions and beneficial effects. Technical details which are not described in detail in this embodiment can be found in any of the above embodiments.

It should be appreciated that various forms of the flows shown above may be used to reorder, add, or delete steps. For example, the steps described in the present invention may be performed in parallel, sequentially, or in a different order, so long as the desired results of the technical solution of the present invention are achieved, and the present invention is not limited herein.

The above embodiments do not limit the scope of the present invention. It will be apparent to those skilled in the art that various modifications, combinations, sub-combinations and alternatives are possible, depending on design requirements and other factors. Any modifications, equivalent substitutions and improvements made within the spirit and principles of the present invention should be included in the scope of the present invention.

Claims

1. A network device controller for managing a plurality of network devices;

2. The network device controller of claim 1, wherein the southbound service is further configured to:

and converting the returned data of the nano-tube equipment into data meeting the preset model and returning the data to the core service.

3. The network device controller of claim 1, wherein the south-oriented service is deployed with at least one instance, a single instance corresponding to a specified type of network device.

4. The network device controller of claim 1, wherein the southbound service is further configured to receive alert information for the network device.

5. The network device controller of claim 3, wherein load balancing rules are satisfied between multiple instances of the southbound service, and wherein multiple instances of the southbound service are disaster recovery from each other.

6. A network device controller according to claim 3, wherein the instance is configured to establish a connection with the specified type of network device after obtaining the management rights of the specified type of network device;

a network device is connected to one of the instances at a time.

7. The network device controller according to claim 1, wherein for network devices to be managed, the core service is further configured to add device type layer and device IP layer nodes according to device types and device management addresses of the network devices to be managed, respectively, based on a distributed lock, and send a node addition message to each of the southbound services;

an example of a southbound service is also used to add a service registration layer node to nanotube the network device to be hosted according to the node addition message.

8. The network device controller of claim 7, wherein the core service is further configured to write encrypted device information into a device IP layer node during the addition of the device IP layer node;

the southbound service instance is further configured to obtain authentication information required to connect to a network device by decrypting the device information; when a service registration layer node is added, writing instance information into the service registration layer node;

The core service is further configured to send traffic processing data for the network device to the instance of the southbound service based on the service registration layer node information.

9. The network device controller of claim 8, wherein the deletion operation of the service registration layer node is triggered if the service registration layer node does not receive heartbeat information of the southbound service instance within a set time;

after the service registration layer node is deleted, another southbound service instance is used for temporarily managing the corresponding network device;

10. A network device management method is characterized in that,

converting the business processing data in the standard format into data for the network equipment of the nano tube through a southbound service, and transmitting the data to the network equipment of the nano tube;

the network configuration protocol based network maintains a long connection with the managed network device.

11. An electronic device, comprising:

at least one processor; and

12. A computer-readable storage medium, on which a computer program is stored, characterized in that the program, when being executed by a processor, implements the network device management method according to claim 10.

13. A network device management system, comprising: a plurality of network devices and an electronic device as claimed in claim 11.