A network management system interfacing method, apparatus, device, medium and product

Abstract

The application provides a network management system interfacing method, device, equipment, medium and product, comprising obtaining a unified interfacing standard rule and a northbound interface document of a network management system to be interfaced; analyzing the northbound interface document by using a large language model to obtain northbound interface metadata corresponding to the network management system to be interfaced; generating a corresponding network management interfacing plug-in based on the unified interfacing standard rule and the northbound interface metadata of the network management system to be interfaced, loading the network management interfacing plug-in to a network orchestrator; and providing a unified network management interface through the network orchestrator. The large language model is used to learn the northbound interface document of the network management system of different manufacturers, the network management interfacing plug-in is automatically generated according to the unified interfacing standard rule and the northbound interface metadata, the code coupling between the network orchestrator and each network management system is eliminated, the network management system is more flexible when being connected or disconnected, and the development workload and complexity are reduced.

Description

Technical Field

[0001] This application relates to the field of network management technology, specifically to a method, apparatus, equipment, medium, and product for interfacing with a network management system. Background Technology

[0002] With the rapid development of network technology, networks are becoming increasingly large-scale and complex. A typical network often contains network devices from different manufacturers and of different models. In the context of software-defined networking (SDN) technology, the management and maintenance of network devices are usually handled by network administrators through network management systems provided by various vendors. However, since each vendor provides a corresponding network management system based on its own device model and version, network administrators often need to switch between multiple systems when dealing with all network devices, making the process extremely cumbersome.

[0003] To simplify network management and maintenance, a common practice is to develop network orchestrators to interface with various network management systems. However, different network management systems provide interfaces in different ways, and the request data, return data, and data models of these interfaces vary. This results in complex code, a large development workload, and a high risk of errors during the integration process. Furthermore, the core business code of the network orchestrator is highly coupled with the interface code of each network management system. Whenever a new network management system is launched or decommissioned, a large amount of code needs to be modified, resulting in a serious lack of system flexibility and scalability. Summary of the Invention

[0004] The purpose of this application is to provide a method, apparatus, device, medium, and product for interfacing with a network management system, in order to solve the problems of complex and labor-intensive development work and insufficient flexibility when interfacing network orchestrators with network management systems.

[0005] To achieve the above objectives, this application provides a method for interfacing with a network management system, comprising:

[0006] Obtain unified interface standard rules and the northbound interface documents of the network management system to be interfaced; the unified interface standard rules are used to divide the northbound interface of the network management system into multiple standardized interface categories, and to define the corresponding standardized request parameter format and standardized return parameter format for each standardized interface category.

[0007] The northbound interface documentation is analyzed using a large language model to obtain the northbound interface metadata of the network management system to be connected to. The northbound interface metadata includes the interface function information, interface calling method, original request parameters, and original return parameters of multiple northbound interfaces in the network management system to be connected to.

[0008] Based on the unified interface standard rules and the northbound interface metadata of the network management system to be interfaced, a corresponding network management interface plugin is generated.

[0009] Load the network management integration plugin corresponding to each network management system to be integrated into the network orchestrator;

[0010] The network orchestrator provides a unified network management interface; the network orchestrator is used to receive a first network management request sent by an external system to a first network management system through the unified network management interface, and to transmit the first network management request to a first network management interface plug-in corresponding to the first network management system; the first network management interface plug-in converts the first request parameters in the first network management request that meet the standardized request parameter format into first original request parameters, calls the interface of the first network management system based on the first original request parameters and the interface calling method of the first network management system to obtain first original return parameters, converts the first original return parameters into first return parameters that meet the standardized return parameter format; and returns the first return parameters to the external system via the unified network management interface.

[0011] Optionally, the northbound interface document is analyzed using a large language model to obtain the northbound interface metadata of the network management system to be interfaced with, including:

[0012] The northbound interface document is preprocessed to obtain the preprocessed northbound interface document;

[0013] The preprocessed northbound interface documents are analyzed using the large language model to obtain structured northbound interface metadata.

[0014] Optionally, based on the unified interface standard rules and the northbound interface metadata of the network management system to be interfaced, a corresponding network management interface plugin is generated, including:

[0015] For any northbound interface of the network management system to be connected, a first mapping relationship is established between the interface function information of the northbound interface and the corresponding standardized interface category, a second mapping relationship is established between the original request parameters of the northbound interface and the standardized request parameters, and a third mapping relationship is established between the original return parameters of the northbound interface and the standardized return parameters. Based on the first mapping relationship, the second mapping relationship, the third mapping relationship and the interface calling method of the northbound interface, parameter adaptation code corresponding to the northbound interface is automatically generated through codeless programming technology. The parameter adaptation code corresponding to each northbound interface of the network management system to be connected is integrated and encapsulated into the network management interface plugin.

[0016] Optionally, the network management interface plugin corresponding to each network management system is loaded into the network orchestrator, including:

[0017] Create an independent class loader for each of the aforementioned network management interface plugins and load the class loader into the network orchestrator;

[0018] The class loader adopts a parent delegation mechanism, loading the core inner class of the network management interface plugin through the parent class loader, and loading other inner classes of the network management interface plugin other than the core inner class through the child class loader.

[0019] Optionally, the step of converting the first request parameter in the first network management request that meets the standardized request parameter format into the first original request parameter through the first network management interface plugin includes: determining the first standardized interface category corresponding to the first request parameter, and converting the first request parameter into the first original request parameter in the first standardized request parameter format corresponding to the first standardized interface category.

[0020] The step of converting the first original return parameter into a first return parameter that satisfies the standardized return parameter format includes: converting the first original return parameter into a first return parameter that satisfies the first standardized request parameter format.

[0021] Optionally, the standardized interface categories in the unified interface standard rules include: physical network interface category, virtual network interface category, operation and maintenance management interface category, and system management interface category.

[0022] Optionally, the method further includes:

[0023] Scan the network management interface plugin directory and verify the digital signatures of all network management interface plugins under the directory; the plugin directory is used to maintain all the network management interface plugins.

[0024] Continuously monitor the event information triggered by the network management interface plugin directory, including plugin addition events and plugin update events;

[0025] When a new plugin event or an updated plugin event is detected, a separate class loader is created for the newly added or updated second network management interface plugin.

[0026] The second network management interface plugin is initialized, and a plugin instance of the second network management interface plugin is created. The plugin instance is then registered in the network orchestrator through the class loader.

[0027] Optionally, the event information may also include plugin deletion events and plugin replacement events;

[0028] When a plugin deletion event or plugin replacement event is detected, the system resources occupied by the deleted or replaced third-party network management interface plugin during its operation are released, the class loader of the third-party network management interface plugin is closed, and the plugin instance of the third-party network management interface plugin is removed from the network orchestrator.

[0029] This application also provides a network management system interface device, including:

[0030] The acquisition module is used to acquire unified interface standard rules and the northbound interface documents of the network management system to be connected; the unified interface standard rules are used to divide the northbound interface of the network management system into multiple standardized interface categories, and to define the corresponding standardized request parameter format and standardized return parameter format for each standardized interface category.

[0031] The analysis module is used to analyze the northbound interface document using a large language model to obtain the northbound interface metadata of the network management system to be connected to; the northbound interface metadata includes the interface function information, interface calling method, original request parameters and original return parameters of multiple northbound interfaces in the network management system to be connected to.

[0032] The code-free service module is used to generate corresponding network management interface plugins based on the unified interface standard rules and the northbound interface metadata of the network management system to be interfaced.

[0033] The loading module is used to load the network management integration plugin corresponding to each network management system to be integrated into the network orchestrator.

[0034] A network orchestrator microkernel service module is used to provide a unified network management interface through the network orchestrator. The network orchestrator is used to receive a first network management request sent by an external system to a first network management system through the unified network management interface, and to transmit the first network management request to a first network management interface plug-in corresponding to the first network management system. The first network management interface plug-in converts the first request parameters in the first network management request that meet the standardized request parameter format into first raw request parameters. Based on the first raw request parameters and the interface calling method of the first network management system, the plug-in calls the interface of the first network management system to obtain the first raw return parameters, and converts the first raw return parameters into first return parameters that meet the standardized return parameter format. The module is also used to return the first return parameters to the external system via the unified network management interface.

[0035] This application also provides an electronic device, including a memory, a processor, and a computer program stored in the memory and running on the processor, wherein the processor executes the computer program to implement the above-described network management system docking method.

[0036] This application also provides a computer-readable storage medium for storing a computer program, which, when executed by a processor, implements the steps in the above-described network management system docking method.

[0037] This application also provides a computer program product, including computer instructions that, when executed by a processor, implement the steps in the above-described network management system docking method.

[0038] Compared with existing technologies, the network management system integration method, apparatus, device, medium, and product provided in this application can learn the northbound interface documents of network management systems from different vendors through a large language model, extract relevant northbound interface metadata, and automatically generate network management integration plugins based on unified integration standard rules and northbound interface metadata. By loading the plugins, the network orchestrator can manage multiple network management systems, decoupling the code between the network orchestrator and each network management system. This allows for the addition or removal of the corresponding network management integration plugin when adding or removing a network management system, without needing to modify the internal code of the network orchestrator. This makes the operation more flexible and convenient when adding or removing systems, and reduces the workload and complexity of development. Attached Figure Description

[0039] Various other advantages and benefits will become apparent to those skilled in the art upon reading the following detailed description of preferred embodiments. The accompanying drawings are for illustrative purposes only and are not intended to limit the scope of this application. Furthermore, the same reference numerals denote the same parts throughout the drawings. In the drawings:

[0040] Figure 1 A flowchart illustrating a network management system integration method provided in one embodiment of this application;

[0041] Figure 2 This is a schematic diagram of the structure of a network management system docking device provided in one embodiment of this application. Detailed Implementation

[0042] Exemplary embodiments of the present application will now be described in more detail with reference to the accompanying drawings. While exemplary embodiments of the present application are shown in the drawings, it should be understood that the present application may be implemented in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this application will be thorough and complete, and will fully convey the scope of the present application to those skilled in the art.

[0043] See Figure 1 , Figure 1 This is a flowchart illustrating a network management system integration method provided in one embodiment. To achieve the above objectives, this application provides a network management system integration method, comprising:

[0044] Step 101: Obtain the unified interface standard rules and the northbound interface document of the network management system to be interfaced; the unified interface standard rules are used to divide the northbound interface of the network management system into multiple standardized interface categories, and to define the corresponding standardized request parameter format and standardized return parameter format for each standardized interface category.

[0045] A network management system is a software system used to centrally manage, configure, monitor, and maintain various network devices in a communication network. In modern communication network architectures, as network scale continues to expand and equipment types become increasingly diversified, operators or enterprises typically need to deploy multiple network management systems to cover network devices of different types and from different manufacturers.

[0046] Northbound interfaces are application programming interfaces (APIs) that a network management system (NMS) exposes to external systems. These APIs allow external systems to acquire data or issue commands. NMS vendors typically provide accompanying documentation explaining each NMS interface. Unified interface standard rules are pre-defined based on actual interface requirements. These rules categorize the NMS's northbound interfaces into multiple standardized interface types and define corresponding standardized request and return parameter formats for each type.

[0047] Step 102: Analyze the northbound interface document using a large language model to obtain the northbound interface metadata of the network management system to be connected; the northbound interface metadata includes the interface function information, interface calling method, original request parameters, and original return parameters of multiple northbound interfaces in the network management system to be connected.

[0048] In one embodiment of the present invention, step 102 includes:

[0049] The northbound interface document is preprocessed to obtain the preprocessed northbound interface document;

[0050] The preprocessed northbound interface documents are analyzed using the large language model to obtain structured northbound interface metadata.

[0051] Specifically, after obtaining the original northbound interface document of the network management system to be connected, since the original northbound interface document often contains a large amount of non-critical declaration text, directly inputting the original document would not only consume a lot of computing resources, but may also introduce noise that interferes with the model's understanding. Therefore, before submitting it for model analysis, the interface description part needs to be extracted and the text preprocessed to obtain the preprocessed northbound interface document. For example, optical character recognition and natural language processing technologies can be used to remove irrelevant characters such as headers, footers, watermarks, and special symbols from the northbound interface document. Then, the document is logically divided into multiple independent text blocks, each of which focuses on describing one or a group of specific interfaces, ensuring that the corpus input to the model is focused and complete. After completing the document preprocessing, this embodiment inputs the preprocessed northbound interface document into a preset large language model for intelligent analysis and information extraction to obtain the structured northbound interface metadata corresponding to the network management system to be connected. The northbound interface metadata includes the interface function information, interface calling methods, original request parameters, and original return parameters of multiple northbound interfaces in the network management system to be connected.

[0052] Step 103: Based on the unified interface standard rules and the northbound interface metadata of the network management system to be interfaced, generate the corresponding network management interface plugin.

[0053] In one embodiment of this application, step 103 involves generating a corresponding network management interface plugin based on the unified interface standard rules and the northbound interface metadata of the network management system to be interfaced with, including:

[0054] For any northbound interface of the network management system to be connected, a first mapping relationship is established between the interface function information of the northbound interface and the corresponding standardized interface category, a second mapping relationship is established between the original request parameters of the northbound interface and the standardized request parameters, and a third mapping relationship is established between the original return parameters of the northbound interface and the standardized return parameters. Based on the first mapping relationship, the second mapping relationship, the third mapping relationship and the interface calling method of the northbound interface, parameter adaptation code corresponding to the northbound interface is automatically generated through codeless programming technology. The parameter adaptation code corresponding to each northbound interface of the network management system to be connected is integrated and encapsulated into the network management interface plugin.

[0055] Specifically, to reduce the development workload when connecting to the network management system, this embodiment develops a codeless service module using Java. For any northbound interface of the network management system to be connected, the codeless service module can establish a mapping relationship between the northbound interface and the corresponding standardized interface category in the unified connection standard rules based on the northbound interface metadata extracted from the large language model. This mapping relationship consists of the first, second, and third mapping relationships. Based on the above mapping relationships and the interface calling method corresponding to the northbound interface, the module automatically generates complete and runnable parameter adaptation code. Subsequently, the parameter adaptation code corresponding to all northbound interfaces of the network management system to be connected is integrated and encapsulated into a network management connection plugin for the network management system. The network management connection plugin is preferably encapsulated in JAR format. Through this plugin, the first request parameter that meets the standardized request parameters can be converted into the original request parameters. The network management system's interface can be called according to the original request parameters and the interface calling method to obtain the original return parameters. The original return parameters can also be converted into the first return parameters that meet the standardized return parameters for subsequent loading and management by the network orchestrator.

[0056] Step 104: Load the network management integration plugin corresponding to each network management system to be integrated into the network orchestrator.

[0057] In one embodiment of the present invention, step 104 includes:

[0058] Create an independent class loader for each of the aforementioned network management interface plugins and load the class loader into the network orchestrator;

[0059] The class loader adopts a parent delegation mechanism, loading the core inner class of the network management interface plugin through the parent class loader, and loading other inner classes of the network management interface plugin other than the core inner class through the child class loader.

[0060] Specifically, after generating the network management integration plugins to be integrated with the network management system through the codeless service module, to prevent potential conflicts of classes with the same name in different plugins, this embodiment creates an independent class loader for each network management integration plugin. The class loader is obtained by inheriting the java.lang.ClassLoader class and is specifically responsible for loading the corresponding network management integration plugin into the network orchestrator microkernel service module of the network orchestrator. In this way, even if there are classes with the same fully qualified name in different network management integration plugins, they will be regarded as different classes, realizing the isolation between network management integration plugins and ensuring that the crash or memory leak of one plugin will not affect other plugins. The network orchestrator provides a unified network management interface to the outside world. When the network orchestrator receives a request from an external system, it returns the information of each network management system to the external system in JSON format.

[0061] In one embodiment of the present invention, the class loader adopts a parent delegation mechanism, with its parent class loader being the system class loader. During loading, the parent class loader is given priority in loading the core inner classes in the network management interface plugin, while the child class loader is given priority in loading other inner classes in the network management interface plugin besides the core inner classes, thus avoiding conflicts in the core inner classes.

[0062] Step 105: Provide a unified network management interface through the network orchestrator; the network orchestrator is used to receive a first network management request sent by an external system to a first network management system through the unified network management interface, and transmit the first network management request to the first network management interface plug-in corresponding to the first network management system; convert the first request parameter in the first network management request that meets the standardized request parameter format into a first original request parameter through the first network management interface plug-in, call the interface of the first network management system based on the first original request parameter and the interface calling method of the first network management system to obtain a first original return parameter, convert the first original return parameter into a first return parameter that meets the standardized return parameter format; and return the first return parameter to the external system through the unified network management interface.

[0063] Specifically, the network orchestrator, as the unified management and scheduling hub of all network management systems, provides a unified network management interface to the outside world. When an external system (such as an upper-layer business operation platform) needs to access the first network management system, it does not need to be aware of the differences between different underlying network management systems. It only needs to send a first network management request to the unified network management interface entry configured in the network orchestrator to access the first network management system. The network orchestrator then transmits the first network management request to the first network management interface plug-in corresponding to the first network management system. The first network management interface plug-in converts the first request parameters in the first network management request that meet the standardized request parameter format into first raw request parameters. Based on the first raw request parameters and the interface calling method of the first network management system, the first network management system's interface is called to obtain the first raw return parameters. Then, the first raw return parameters are converted into first return parameters that meet the standardized return parameter format. Finally, the network orchestrator returns the first return parameters to the external system through the unified network management interface.

[0064] In one embodiment of the present invention, step 105, which involves converting the first request parameter in the first network management request that satisfies the standardized request parameter format into the first original request parameter through the first network management interface plug-in, includes: determining the first standardized interface category corresponding to the first request parameter, and converting the first request parameter into the first original request parameter in the first standardized request parameter format corresponding to the first standardized interface category.

[0065] The step of converting the first original return parameter into a first return parameter that satisfies the standardized return parameter format includes: converting the first original return parameter into a first return parameter that satisfies the first standardized request parameter format.

[0066] In one embodiment of the present invention, the standardized interface categories in the unified interface standard rules include: physical network interface category, virtual network interface category, operation and maintenance management interface category, and system management interface category.

[0067] In one embodiment of the present invention, the unified interface standard rules divide the interface into multiple standardized interface categories according to its function, and configure corresponding standardized request parameters and standardized return parameters for each standardized interface category. For example, the standardized interface categories can be divided into physical network interface categories, virtual network interface categories, operation and maintenance management interface categories, and system management interface categories, and the request parameters and return parameters of each interface category are defined in a standardized and normalized manner.

[0068] In one embodiment of the present invention, the physical network interface category includes a network device management interface and a link management interface. The standardized request parameters of the network device management interface are device ID, device name, and device IP, and the standardized return parameters are device ID, device name, device IP, device status, device model, and device manufacturer. The standardized request parameters of the link management interface are link ID and link name, and the standardized return parameters are link ID, link name, link status, bandwidth, starting device ID, ending device ID, starting port, and ending port.

[0069] In one embodiment of the present invention, the virtual network interface category includes a tunnel management interface and a service management interface. The standardized request parameters of the tunnel management interface are tunnel ID and tunnel name, and the standardized return parameters are tunnel ID, tunnel name, tunnel type, status, bound service, and latency. The standardized request parameter of the service management interface is service name, and the standardized return parameters are service name, creation time, service type, and service status.

[0070] In one embodiment of the present invention, the operation and maintenance management interface category includes an alarm management interface and a traffic monitoring interface. The standardized request parameters of the alarm management interface are alarm level, start time, end time, and alarm type, and the standardized return parameters are alarm object, alarm type, alarm time, alarm level, and alarm reason. The standardized request parameters of the traffic monitoring interface are link ID, start time, and end time, and the standardized return parameters are link ID, link name, time, inflow traffic rate, and outflow traffic rate.

[0071] In one embodiment of the present invention, the system management interface category includes an operation log management interface and an access management interface. The standardized request parameters of the operation log management interface are start time, end time, and operation user, and the standardized return parameters are operation time, operation user, type, action, and event. The standardized request parameters of the access management interface are system name, access protocol, IP, port, suffix, access username, and password, and the standardized return parameters are system name and access token.

[0072] In one embodiment of this application, the method further includes:

[0073] Scan the network management interface plugin directory and verify the digital signatures of all network management interface plugins under the directory; the plugin directory is used to maintain all the network management interface plugins.

[0074] Continuously monitor the event information triggered by the network management interface plugin directory, including plugin addition events and plugin update events;

[0075] When a new plugin event or an updated plugin event is detected, a separate class loader is created for the newly added or updated second network management interface plugin.

[0076] The second network management interface plugin is initialized, and a plugin instance of the second network management interface plugin is created. The plugin instance is then registered in the network orchestrator through the class loader.

[0077] Specifically, this embodiment develops a network orchestrator microkernel service module using Java. This microkernel service module has configuration scanning and plugin loading functions. Upon startup, it automatically scans the network management interface plugin directory, which maintains all network management interface plugins. Simultaneously, it verifies the digital signatures of all network management interface plugins in the directory. Specifically, it uses the SHA-256 algorithm to verify the digital signature of each plugin, ensuring the integrity and legitimacy of the plugin's origin and preventing malicious plugin injection. A plugin listener, implemented based on Java's WatchService interface, continuously monitors event information triggered by the network management interface plugin directory through its hot-sensing function. The event information includes new plugin events and updated plugin events. When monitoring events in the network management interface plugin directory, event filtering can be performed. The filtering principle is to only respond to files in the corresponding format of the network management interface plugin, ignoring temporary files. For example, if the network management interface plugin is in JAR format, only event information for files with the ".jar" extension will be responded to. Simultaneously, the network management interface plugin is pre-verified. The purpose of pre-verification is to compare with the local cache, accelerating the configuration scanning process.

[0078] When a new plugin event or an updated plugin event is detected in the plugin directory, a separate class loader is created for the newly added or updated second network management interface plugin, and the second network management interface plugin is loaded through this class loader. Subsequently, through Java's SPI service discovery mechanism, the fully qualified name of the interface implementation class recorded in the configuration file of the second network management interface plugin (e.g., the <fully qualified name of the specification interface> file located in the META-INF / services / directory) is read. This fully qualified name must be consistent with the fully qualified name of the plugin's generic interface defined in the network orchestrator microkernel service module. The plugin is automatically identified and loaded based on this fully qualified name. A class implementing the plugin's generic interface is used to achieve automatic loading without hard-coding dependencies. After successful loading, the startup method of the second network management interface plugin is called for initialization, generating a plugin instance of the second network management interface plugin, and registering the plugin instance to the plugin manager of the network orchestrator microkernel service module for subsequent calls. Through the above steps, this embodiment can dynamically integrate the functional modules of the second network management interface plugin into the network orchestrator microkernel service without restarting the network orchestrator microkernel service, and ensure the isolation and compatibility between the second network management interface plugin and the network orchestrator microkernel service module and other network management interface plugins.

[0079] In one embodiment of this application, the event information further includes plugin deletion events and plugin replacement events;

[0080] When a plugin deletion event or plugin replacement event is detected, the system resources occupied by the deleted or replaced third-party network management interface plugin during its operation are released, the class loader of the third-party network management interface plugin is closed, and the plugin instance of the third-party network management interface plugin is removed from the network orchestrator.

[0081] Specifically, the microkernel service module also has a plugin uninstallation function. When the plugin listener detects plugin deletion and replacement events in the network management interface plugin directory, it uses the file name of the network management interface plugin as a unique identifier to accurately locate the third-party network management interface plugin that needs to be uninstalled. It then calls the stop method of the third-party network management interface plugin, triggers resource cleanup logic, releases the system resources occupied by the deleted or replaced third-party network management interface plugin during its operation, ensures the safe exit of the third-party network management interface plugin, closes the class loader corresponding to the third-party network management interface plugin, and severs the association between the class loader and the Java Virtual Machine class reference. Finally, it removes the corresponding plugin instance from the cache of the network orchestrator's plugin manager, severing the association between the network orchestrator microkernel service module and the third-party network management interface plugin to avoid memory leaks.

[0082] This application also provides a network management system interface device, such as... Figure 2 As shown, it includes:

[0083] The acquisition module 201 is used to acquire the unified interface standard rules and the northbound interface documents of the network management system to be connected; the unified interface standard rules are used to divide the northbound interface of the network management system into multiple standardized interface categories, and to define the corresponding standardized request parameter format and standardized return parameter format for each standardized interface category.

[0084] Analysis module 202 is used to analyze the northbound interface document using a large language model to obtain the northbound interface metadata of the network management system to be connected; the northbound interface metadata includes the interface function information, interface calling method, original request parameters and original return parameters of multiple northbound interfaces in the network management system to be connected;

[0085] The code-free service module 203 is used to generate a corresponding network management interface plugin based on the unified interface standard rules and the northbound interface metadata of the network management system to be interfaced.

[0086] Loading module 204 is used to load the network management integration plugin corresponding to each network management system to be integrated into the network orchestrator.

[0087] The network orchestrator microkernel service module 205 is used to provide a unified network management interface through the network orchestrator. The network orchestrator is used to receive a first network management request sent by an external system to a first network management system through the unified network management interface, and to transmit the first network management request to a first network management interface plug-in corresponding to the first network management system. The first network management interface plug-in converts the first request parameters in the first network management request that meet the standardized request parameter format into first original request parameters, calls the interface of the first network management system based on the first original request parameters and the interface calling method of the first network management system to obtain first original return parameters, converts the first original return parameters into first return parameters that meet the standardized return parameter format, and returns the first return parameters to the external system through the unified network management interface.

[0088] This application also provides an electronic device, including a memory, a processor, and a computer program stored in the memory and running on the processor, wherein the processor executes the computer program to implement the above-described network management system docking method.

[0089] This application also provides a computer-readable storage medium for storing a computer program, which, when executed by a processor, implements the steps in the above-described network management system docking method.

[0090] This application also provides a computer program product, including computer instructions that, when executed by a processor, implement the steps in the above-described network management system docking method.

[0091] The embodiments of this application have been described above with reference to the accompanying drawings. However, this application is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other forms under the guidance of this application without departing from the spirit and scope of the claims, and all of these forms are within the protection scope of this application.

Claims

1. A method for connecting to a network management system, characterized in that, include: Obtain the unified interface standard rules and the northbound interface documents of the network management system to be interfaced; The unified interface standard rules are used to divide the northbound interface of the network management system into multiple standardized interface categories, and to define the corresponding standardized request parameter format and standardized return parameter format for each standardized interface category. The northbound interface documentation is analyzed using a large language model to obtain the northbound interface metadata of the network management system to be connected to. The northbound interface metadata includes the interface function information, interface calling method, original request parameters, and original return parameters of multiple northbound interfaces in the network management system to be connected to. Based on the unified interface standard rules and the northbound interface metadata of the network management system to be interfaced, a corresponding network management interface plugin is generated. Load the network management integration plugin corresponding to each network management system to be integrated into the network orchestrator; The network orchestrator provides a unified network management interface; The network orchestrator is used to receive a first network management request sent by an external system to a first network management system through a unified network management interface, and to transmit the first network management request to the first network management interface plug-in corresponding to the first network management system; the first network management interface plug-in converts the first request parameters in the first network management request that meet the standardized request parameter format into first original request parameters, and calls the interface of the first network management system based on the first original request parameters and the interface calling method of the first network management system to obtain the first original return parameters, and converts the first original return parameters into first return parameters that meet the standardized return parameter format; And for returning the first return parameter to the external system via the unified network management interface.

2. The network management system docking method according to claim 1, characterized in that, The northbound interface document is analyzed using a large language model to obtain the northbound interface metadata of the network management system to be interfaced with, including: The northbound interface document is preprocessed to obtain the preprocessed northbound interface document; The preprocessed northbound interface documents are analyzed using the large language model to obtain structured northbound interface metadata.

3. The network management system docking method according to claim 1, characterized in that, Based on the unified interface standard rules and the northbound interface metadata of the network management system to be interfaced, a corresponding network management interface plugin is generated, including: For any northbound interface of the network management system to be connected, a first mapping relationship is established between the interface function information of the northbound interface and the corresponding standardized interface category, a second mapping relationship is established between the original request parameters of the northbound interface and the standardized request parameters, and a third mapping relationship is established between the original return parameters of the northbound interface and the standardized return parameters. Based on the first mapping relationship, the second mapping relationship, the third mapping relationship and the interface calling method of the northbound interface, parameter adaptation code corresponding to the northbound interface is automatically generated through codeless programming technology. The parameter adaptation code corresponding to each northbound interface of the network management system to be connected is integrated and encapsulated into the network management interface plugin.

4. The network management system docking method according to claim 1, characterized in that, Load the network management interface plugin corresponding to each network management system into the network orchestrator, including: Create an independent class loader for each of the aforementioned network management interface plugins and load the class loader into the network orchestrator; The class loader adopts a parent delegation mechanism, loading the core inner class of the network management interface plugin through the parent class loader, and loading other inner classes of the network management interface plugin other than the core inner class through the child class loader.

5. The network management system docking method according to claim 1, characterized in that, The first network management interface plugin converts the first request parameter in the first network management request that meets the standardized request parameter format into the first original request parameter, including: determining the first standardized interface category corresponding to the first request parameter, and converting the first request parameter into the first original request parameter in the first standardized request parameter format corresponding to the first standardized interface category. The step of converting the first original return parameter into a first return parameter that satisfies the standardized return parameter format includes: converting the first original return parameter into a first return parameter that satisfies the first standardized request parameter format.

6. The network management system docking method according to claim 5, characterized in that, The standardized interface categories in the unified interface standard rules include: physical network interface category, virtual network interface category, operation and maintenance management interface category, and system management interface category.

7. The network management system docking method according to claim 4, characterized in that, The method also includes: Scan the network management interface plugin directory and verify the digital signatures of all network management interface plugins under the directory; the plugin directory is used to maintain all the network management interface plugins. Continuously monitor the event information triggered by the network management interface plugin directory, including plugin addition events and plugin update events; When a new plugin event or an updated plugin event is detected, a separate class loader is created for the newly added or updated second network management interface plugin. The second network management interface plugin is initialized, and a plugin instance of the second network management interface plugin is created. The plugin instance is then registered in the network orchestrator through the class loader.

8. The network management system docking method according to claim 7, characterized in that, The event information also includes plugin deletion events and plugin replacement events; When a plugin deletion event or plugin replacement event is detected, the system resources occupied by the deleted or replaced third-party network management interface plugin during its operation are released, the class loader of the third-party network management interface plugin is closed, and the plugin instance of the third-party network management interface plugin is removed from the network orchestrator.

9. A network management system interface device, characterized in that, include: The acquisition module is used to acquire unified interface standard rules and the northbound interface documents of the network management system to be interfaced with; The unified interface standard rules are used to divide the northbound interface of the network management system into multiple standardized interface categories, and to define the corresponding standardized request parameter format and standardized return parameter format for each standardized interface category. The analysis module is used to analyze the northbound interface document using a large language model to obtain the northbound interface metadata of the network management system to be connected to; the northbound interface metadata includes the interface function information, interface calling method, original request parameters and original return parameters of multiple northbound interfaces in the network management system to be connected to. The code-free service module is used to generate corresponding network management interface plugins based on the unified interface standard rules and the northbound interface metadata of the network management system to be interfaced. The loading module is used to load the network management integration plugin corresponding to each network management system to be integrated into the network orchestrator. A network orchestrator microkernel service module is used to provide a unified network management interface through the network orchestrator; The network orchestrator is used to receive a first network management request sent by an external system to a first network management system through a unified network management interface, and to transmit the first network management request to the first network management interface plug-in corresponding to the first network management system; the first network management interface plug-in converts the first request parameters in the first network management request that meet the standardized request parameter format into first original request parameters, and calls the interface of the first network management system based on the first original request parameters and the interface calling method of the first network management system to obtain the first original return parameters, and converts the first original return parameters into first return parameters that meet the standardized return parameter format; And for returning the first return parameter to the external system via the unified network management interface.

10. An electronic device comprising a memory, a processor, and a computer program stored in the memory and running on the processor, characterized in that, When the processor executes the computer program, it implements the network management system docking method as described in any one of claims 1 to 8.

11. A computer-readable storage medium for storing a computer program, characterized in that, When the computer program is executed by the processor, it implements the steps in the network management system docking method as described in any one of claims 1 to 8.

12. A computer program product, characterized in that, It includes computer instructions that, when executed by a processor, implement the steps in the network management system docking method as described in any one of claims 1 to 8.

Images