Unified access method, system, device and medium for network management control system
Patent Information
- Application Number
- CN202611147257.9
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2026-07-30
- Publication Date
- 2026-10-13
AI Technical Summary
[0006]本发明提供了一种网络管理控制系统的统一接入方法、系统、设备及介质，旨在解决上述现有技术中存在的执行效率低下，多场景下容易失效；以及需要同时维护针对两套后端的独立接入逻辑，接口碎片化导致运维自动化的开发成本高的技术问题
1.本发明通过分通道CLI化转换，将网络管理控制系统的全部业务功能转化为具备明确参数定义、标准化输出格式和完整语义描述的结构化CLI命令。结合MCP（模型上下文协议）标准协议将其注册为Agent可调用的Tool接口，使AI Agent能够直接通过程序化方式精准操控网络管理控制系统，将单次操作耗时从秒级降低至毫秒级，且不受界面UI变更影响，从根本上满足了生产环境对智能运维的高可靠性要求。
Smart Images
Figure CN122909054A_ABST
Abstract
Description
Technical Field
[0001] This invention belongs to the field of network management technology, and in particular relates to a unified access method, system, device and medium for network management and control systems. Background Technology
[0002] The network management and control system is the core control and scheduling hub that ensures the stable, efficient and secure operation of network infrastructure. It provides maintenance personnel with full lifecycle management capabilities, from status monitoring and configuration distribution to fault diagnosis.
[0003] In existing technologies, network management and control systems generally adopt a graphical user interface (GUI) as the primary human-computer interaction method, forming a typical interaction paradigm with a B / S architecture web interface and a C / S architecture desktop client as dual entry points. The web interface is accessed through a browser, with underlying RESTful API services provided by a Java backend; the desktop client is provided by a C++ backend through the ICE middleware framework via RPC.
[0004] The existing technology has the following technical problems: 1. The fundamental contradiction between GUI interaction paradigm and AI Agent (artificial intelligence agent) automation: Traditional screenshot plus pixel positioning scheme is not only inefficient, but also prone to failure in scenarios such as changes in the position of interface elements, resolution adjustment, and theme switching, and cannot meet the reliability requirements of the production environment.
[0005] 2. Fragmentation of Interfaces from Multiple Heterogeneous Backends: The web frontend connects to the Java backend's RESTful API (Representational State Transfer Application Programming Interface) system, while the desktop client connects to the C++ backend's ICE RPC (Internet Communications Engine, Remote Procedure Call) interface. The two backends have completely different technology stacks, communication protocols, data formats, and authentication mechanisms. Automated operation and maintenance scripts need to maintain independent access logic for both backends simultaneously, and this interface fragmentation leads to high development costs for automated operation and maintenance. Summary of the Invention
[0006] This invention provides a unified access method, system, device, and medium for network management and control systems, aiming to solve the technical problems of low execution efficiency, easy failure in multiple scenarios, and the need to maintain independent access logic for two backends simultaneously, resulting in high development costs for automated operation and maintenance due to interface fragmentation in the prior art.
[0007] The technical solution of this invention to solve the above-mentioned technical problems is as follows: A unified access method for a network management and control system, comprising: The first conversion channel converts front-end business operations of the graphical user interface into first command-line interface commands; the second conversion channel converts client business functions based on remote procedure calls into second command-line interface commands. Register the first command-line interface command and the second command-line interface command to a unified command-line namespace to construct a unified command tree containing different command prefixes; Receive a call request, and based on the command prefix in the call request, transparently distribute the call request to the corresponding backend service through the command routing engine; The command-line interface commands in the unified command tree are registered as tool interfaces that can be called by the artificial intelligence agent through a standard protocol, so that the artificial intelligence agent can automatically control the network management and control system through the tool interface.
[0008] Furthermore, the aforementioned first conversion channel transforms the front-end business operations of the graphical user interface into first command-line interface commands, specifically including: Capture document object model interaction events and hypertext transfer protocol requests on front-end pages using the browser's automation engine; By combining the pre-configured semantic mapping configuration table, the captured Hypertext Transfer Protocol requests are subjected to interface endpoint discovery and semantic annotation, and the operation dependencies are determined based on the document object model interaction events. The labeled interface endpoints, parameters, and operational dependencies are abstracted into the first command-line interface command.
[0009] Furthermore, the aforementioned use of the browser's automation engine to capture document object model interaction events and Hypertext Transfer Protocol requests on the front-end page specifically includes: The complete request header and request body of the Hypertext Transfer Protocol request are obtained through the browser developer tools protocol session, and the document object model interaction events are obtained by listening to the state transitions of page nodes. The semantic mapping configuration table adopts YAML data serialization format and is used to specify the name, parameter list and output format of the command line interface command; The method further includes: keeping the web session active via background heartbeat and automatically synchronizing tokens before requests to achieve persistent login state.
[0010] Furthermore, the aforementioned second conversion channel transforms client-side business functions based on remote procedure calls into second command-line interface commands, specifically including: Scan the interface description language file and parse it to extract the interface metadata model; Based on the interface metadata model, business domain grouping and method semantic enhancement are performed; The improved method signature and parameters are mapped to the second command-line interface command, and corresponding command-line wrapper code is generated; wherein, the command-line wrapper code is used to parse the parameters of the second command-line interface command and execute the corresponding remote procedure call.
[0011] Furthermore, the interface description language file mentioned above is an ICE Slice file; The method semantic enhancement includes: automatically extracting method annotations, supplementing missing annotations through semantic configuration overwrite files, and marking the side effect level; The process of mapping the enhanced method signature and parameters to the second command-line interface includes: directly mapping basic data type parameters to command-line options, transferring composite data type parameters through JSON or YAML files, and supporting automatic generation of parameter templates.
[0012] Furthermore, the unified command tree described above includes a first subtree and a second subtree, wherein the first subtree carries the first command line interface command and the second subtree carries the second command line interface command; Based on the command prefix in the call request, the call request is transparently distributed to the corresponding backend service through the command routing engine, specifically including: Extract the command prefix from the call request; Identify the target subtree to which the command prefix belongs; wherein the target subtree is either the first subtree or the second subtree; When the command prefix belongs to the first preset prefix, the target subtree is determined to be the first subtree, and the Hypertext Transfer Protocol Stack or Secure Hypertext Transfer Protocol Stack is invoked to distribute the request to the Java-based backend service; When the command prefix belongs to the second preset prefix, the target subtree is determined to be the second subtree, and the ICE remote procedure call protocol stack is invoked to distribute the request to the C++-based backend service.
[0013] Furthermore, the command-line interface commands in the unified command tree are registered as tool interfaces that can be called by the AI agent through a standard protocol, enabling the AI agent to automatically control the network management and control system through the tool interfaces. Specifically, this includes: Each command-line interface command is registered as a tool interface through the model context protocol; The parameters of the command-line interface commands are mapped to the input mode of the tool interface, the output of the command-line interface commands is mapped to the return content of the tool interface, and the help information of the command-line interface commands is mapped to the description information of the tool interface. The AI agent queries alarm information by calling the first command-line interface command through the tool interface according to natural language instructions, and automatically arranges and calls the second command-line interface command to perform alarm confirmation operation based on the query results.
[0014] Secondly, to solve the above-mentioned technical problems, the present invention also provides a unified access system for network management and control systems, comprising: The heterogeneous conversion module is used to convert front-end business operations of the graphical user interface into first command-line interface commands through a first conversion channel; and to convert client business functions based on remote procedure calls into second command-line interface commands through a second conversion channel. The namespace management module is used to register the first command-line interface command and the second command-line interface command to a unified command-line namespace and construct a unified command tree containing different command prefixes. The command routing module is used to receive call requests and, based on the command prefix in the call request, transparently distribute the call request to the corresponding backend service through the command routing engine; The agent adaptation module is used to register the command-line interface commands in the unified command tree as tool interfaces that can be called by the artificial intelligence agent through a standard protocol, so that the artificial intelligence agent can automatically control the network management and control system through the tool interface.
[0015] Thirdly, in order to solve the above-mentioned technical problems, the present invention also provides an electronic device, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, it implements the unified access method of the network management and control system of the present application.
[0016] Fourthly, in order to solve the above-mentioned technical problems, the present invention also provides a computer-readable storage medium storing a computer program, which, when executed by a processor, implements the unified access method of the network management and control system of the present application.
[0017] Compared with the prior art, the present invention has the following advantages: 1. This invention transforms all business functions of the network management and control system into structured CLI commands with clearly defined parameters, standardized output formats, and complete semantic descriptions through channel-specific CLI conversion. Combined with the MCP (Model Context Protocol) standard protocol, these commands are registered as a tool interface that can be called by the agent. This allows the AI agent to directly and precisely control the network management and control system programmatically, reducing the time for a single operation from seconds to milliseconds, and remaining unaffected by changes in the user interface. This fundamentally meets the high reliability requirements of intelligent operation and maintenance in production environments.
[0018] 2. The Web-CLI channel of this invention generates CLI by observing web page behavior externally through browser automation engines such as Playwright+CDP; the Ice-CLI channel automatically parses and generates a CLI wrapper based on the existing ICE Slice IDL interface definition. Neither channel requires any modification to the existing Java / C++ backend of the network management and control system, achieving seamless and non-intrusive adaptation to existing heterogeneous systems.
[0019] 3. This invention integrates the previously fragmented RESTful API and ICE RPC interfaces into a hierarchical unified command tree by constructing a unified CLI namespace and command routing engine. Upper-layer callers only need to interface with one set of standard CLI interfaces, and the command routing engine automatically and transparently distributes commands to the corresponding underlying protocol stack and backend according to prefixes, completely shielding the heterogeneous differences at the underlying level and eliminating the redundant development costs caused by interface fragmentation.
[0020] 4. The unified namespace design of this invention has strong scalability. If new backend types need to be added in the future, only the corresponding CLI-based conversion channel needs to be added and registered in the corresponding subtree of the unified namespace to be incorporated into the unified routing system. There is no need to reconstruct the existing architecture, providing a flexible technical foundation for the continuous evolution of the network management and control system.
[0021] Other features and advantages of the invention will be set forth in the following description, and some features and advantages will be apparent upon reading the description or may be learned by practicing the invention. The objects and other advantages of the invention may be realized and obtained by means of the structures pointed out in the description, claims and drawings. Attached Figure Description
[0022] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.
[0023] Figure 1 A flowchart illustrating a unified access method for a network management and control system according to an embodiment of the present invention is shown. Figure 2 An overall architecture diagram of a unified access method for a network management and control system according to an embodiment of the present invention is shown; Figure 3 A schematic diagram of the CLI-based conversion logic for Web paths according to an embodiment of the present invention is shown; Figure 4 A flowchart illustrating the implementation of Web path CLI-based conversion according to an embodiment of the present invention is shown; Figure 5 A schematic diagram of the Ice path CLI-based conversion logic according to an embodiment of the present invention is shown; Figure 6 A flowchart illustrating the implementation of Ice path CLI-based conversion according to an embodiment of the present invention is shown; Figure 7 A schematic diagram of the structure of a unified access system for a network management and control system according to an embodiment of the present invention is shown; Figure 8 A schematic diagram of an electronic device structure according to an embodiment of the present invention is shown. Detailed Implementation
[0024] To make the objectives, technical solutions, and advantages of the embodiments of the present invention clearer, the technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.
[0025] Figure 1 A flowchart illustrating a unified access method for a network management and control system according to an embodiment of the present invention is shown, such as... Figure 1 As shown in the figure, a unified access method for a network management and control system according to an embodiment of the present invention includes: S1: Through the first conversion channel, the front-end business operations of the graphical user interface are converted into first command-line interface commands; through the second conversion channel, the client business functions based on remote procedure calls are converted into second command-line interface commands. S2: Register the first command-line interface command and the second command-line interface command to a unified command-line namespace, and construct a unified command tree containing different command prefixes; S3: Receive a call request, and based on the command prefix in the call request, transparently distribute the call request to the corresponding backend service through the command routing engine; S4: Register the command-line interface commands in the unified command tree as tool interfaces that can be called by the artificial intelligence agent through a standard protocol, so that the artificial intelligence agent can automatically control the network management and control system through the tool interface.
[0026] In this embodiment, a non-intrusive strategy is adopted to convert the business functions of two heterogeneous backends into standard CLI commands through a first conversion channel (Web-CLI conversion channel) and a second conversion channel (Ice-CLI conversion channel), respectively. For example... Figure 2 The diagram shown illustrates the architecture of a unified access method for a network management and control system, specifically comprising the following four core layers: Heterogeneous dual-channel CLI conversion layer: includes Web-CLI conversion channel and Ice-CLI conversion channel, which are responsible for converting the business functions of the Web front-end (Java back-end) and client front-end (C++ back-end) into standard CLI commands, respectively.
[0027] Unified CLI Namespace Manager: Responsible for the unified registration, discovery, help documentation generation, and version management of dual-channel command generation.
[0028] Command routing and distribution engine: responsible for automatically identifying and transparently distributing requests to the corresponding heterogeneous backends based on command prefixes at runtime.
[0029] Agent native interface layer: Registers CLI as a tool that can be directly called by AI Agent via MCP (Model Context Protocol).
[0030] Optionally, in S1, the front-end business operations of the graphical user interface are converted into first command-line interface commands through the first conversion channel, specifically including: S1.1: Use the browser's automation engine to capture document object model interaction events and hypertext transfer protocol requests of the front-end page; S1.2: Combining the pre-configured semantic mapping configuration table, perform interface endpoint discovery and semantic annotation on the captured Hypertext Transfer Protocol requests, and determine operation dependencies based on the document object model interaction events; S1.3: Abstract the labeled interface endpoints, parameters, and operation dependencies into the first command-line interface command.
[0031] Optionally, in S1.1, the browser's automation engine is used to capture Document Object Model (DOM) interaction events and Hypertext Transfer Protocol (HTTP) requests from the front-end page, specifically including: S1.1.1: Obtain the complete request header and request body of the Hypertext Transfer Protocol request through the browser developer tools protocol session, and obtain the document object model interaction events by listening to page node state transitions; S1.1.2: The semantic mapping configuration table adopts the YAML data serialization format and is used to specify the name, parameter list and output format of the command line interface command; The method further includes: keeping the web session active via background heartbeat and automatically synchronizing tokens before requests to achieve persistent login state.
[0032] like Figure 3 and Figure 4 As shown, in this embodiment, the core idea of Web path CLI-based conversion is to use Playwright as a semantic bridge between the Web interface and CLI, automatically converting Web business operations into equivalent CLI commands. The specific implementation steps are as follows: 1. Web operation recording and capture: Use Playwright to record user action sequences, capturing DOM events (including XPath, field names, and commit actions), HTTP requests (including methods, URLs, request headers, and request bodies), and page state transitions.
[0033] 2. API endpoint discovery and semantic annotation: The abstract API template normalizes dynamic parameters into placeholders, identifying required, optional, and enumerated parameters. This embodiment introduces a manually configured semantic mapping table to ensure accurate business semantics and establishes an API call dependency graph for multi-step operations, resolving the semantic drift problem caused by purely automatic inference.
[0034] 3. CLI command abstraction and definition generation.
[0035] Perform command name mapping (mapping API paths to three levels of command hierarchy), parameter mapping (mapping API parameters to CLI options), and output formatting (converting underlying JSON data into table, tree, or JSON format output).
[0036] 4. Persistence of login state.
[0037] Web sessions are kept alive via background heartbeats, and tokens are automatically synchronized before each CLI request is initiated to ensure authentication effectiveness.
[0038] In the specific project implementation (Web-CLI implementation), the core tools adopt Playwright + CDP (ChromeDevTools Protocol) + semantic mapping configuration table. Operations are recorded using Playwright codegen; HTTP requests are intercepted in real time using `page.on('request' / 'response')`; and complete request headers, request bodies, and response bodies are obtained through CDP sessions. The semantic mapping configuration table is manually maintained in YAML format, specifying the CLI command name, description, parameter list (source fields / types / required / description), and output format for each API endpoint. The final generated CLI command takes the form of: `umc-cliweb.<domain>.<module>.<action>--<parameters><value>`, containing structured parameters, help descriptions, and underlying mappings to the corresponding HTTP calls. Optionally, in S1, the client business functions based on remote procedure calls are converted into second command-line interface commands through the second conversion channel, specifically including: S1.4: Scan the interface description language file and parse it to extract the interface metadata model; S1.5: Based on the interface metadata model, perform business domain grouping and method semantic enhancement; S1.6: Map the elevated method signature and parameters to the second command-line interface command, and generate the corresponding command-line wrapper code; wherein, the command-line wrapper code is used to parse the parameters of the second command-line interface command and execute the corresponding remote procedure call.
[0039] Optionally, the interface description language file is an ICE Slice file; The method semantic enhancement includes: automatically extracting method annotations, supplementing missing annotations through semantic configuration overwrite files, and marking the side effect level; The process of mapping the enhanced method signature and parameters to the second command-line interface includes: directly mapping basic data type parameters to command-line options, transferring composite data type parameters through JSON or YAML files, and supporting automatic generation of parameter templates.
[0040] like Figure 5 and Figure 6 As shown in this embodiment, the core idea of Ice-CLI path conversion is to take the C++ backend ICESlice file as input, elevate the fine-grained RPC interface to a business-level CLI, and directly call the backend through ICE RPC. The specific implementation steps are as follows: 1. Slice parsing and interface extraction: Scan all .ice files, build an interface metadata model, and extract module / interface hierarchy, method signatures, parameters and return types, custom types, and exception information.
[0041] 2. Interface semantic enhancement and business aggregation: Group by business domain and aggregate by .ice directory hierarchy (directory name corresponds to business domain); obtain method semantics, automatically extract method comments, and supplement missing or inaccurate comments with manual semantic mapping files; perform parameter dependency analysis and establish input-output dependency chains between methods.
[0042] 3. CLI command mapping and parameter conversion design: Define the command hierarchy (module→domain, interface→module, operation→action); define bidirectional type conversion between ICE and CLI, output formatting, and mapping of exceptions to exit codes.
[0043] 4. CLI wrapper code generation: Automatically generate the main entry point, parameter conversion layer, ICE RPC call layer, and output formatting layer.
[0044] In the specific project implementation (Ice-CLI implementation), the core tools adopt the ZeroC ICE Slice compiler + method annotation extractor + semantic configuration coverage.
[0045] Comments and semantic processing: Automatically adding / ... / Comments serve as CLI command descriptions; when comments are missing or semantically unclear, the CLI command name, description, and side effect level (readonly / reversible / irreversible) are supplemented using a YAML semantic overriding file.
[0046] Parameter mapping strategy: Simple types are directly mapped to the --option value; complex objects (such as nested structs, long sequences, dictionaries) are transferred to JSON / YAML files (passed through --input-file) and automatically deserialized into ICE types by CLI; parameter templates can be automatically generated through --gen-template to reduce the threshold for manual writing.
[0047] Wrapper generation: Automatically generates CLI11 parameter parsing + ICE Communicator / Proxy creation + RPC call + output formatted code, which, after compilation, becomes a standalone executable CLI program.
[0048] Optionally, the unified command tree includes a first subtree and a second subtree, wherein the first subtree carries the first command line interface command and the second subtree carries the second command line interface command; Based on the command prefix in the call request, the call request is transparently distributed to the corresponding backend service through the command routing engine, specifically including: Extract the command prefix from the call request; Identify the target subtree to which the command prefix belongs; wherein the target subtree is either the first subtree or the second subtree; When the command prefix belongs to the first preset prefix, the target subtree is determined to be the first subtree, and the Hypertext Transfer Protocol Stack or Secure Hypertext Transfer Protocol Stack is invoked to distribute the request to the Java-based backend service; When the command prefix belongs to the second preset prefix, the target subtree is determined to be the second subtree, and the ICE remote procedure call protocol stack is invoked to distribute the request to the C++-based backend service.
[0049] In this embodiment, the commands from the two channels are merged into a single command tree, and at runtime, they are transparently routed to the heterogeneous backend based on a prefix. Specifically: 1. Hierarchical unified command tree: The unified entry format is defined as: umc-cli<domain>.<module>.<action>.
[0050] Build the web.subtree: to host the CLI (covering alarms, faults, performance, and other business logic) generated by the web path; Construct the ice.subtree: to carry the CLI (covering alarms, performance, security and other services) generated by Ice path.
[0051] A unified CLI namespace manager provides unified registration, discovery, help, and version management.
[0052] 2. Command routing engine: Automatically identify the target backend based on the namespace prefix: When matching web. When using the prefix, the HTTP / HTTPS protocol stack is invoked to call the Java backend; When matching ice. When the prefix is invoked, the ICE RPC protocol stack is called to invoke the C++ backend.
[0053] Through this mechanism, the caller only sees a unified CLI, and the heterogeneous protocol stack is completely transparent to the user and agent. Future additions of backends (such as Python / Go) only require adding a prefix and conversion channel to be integrated.
[0054] Optionally, in S4, the command-line interface commands in the unified command tree are registered as tool interfaces that can be called by the artificial intelligence agent through a standard protocol, so that the artificial intelligence agent can automatically control the network management and control system through the tool interface, specifically including: Each command-line interface command is registered as a tool interface through the model context protocol; The parameters of the command-line interface commands are mapped to the input mode of the tool interface, the output of the command-line interface commands is mapped to the return content of the tool interface, and the help information of the command-line interface commands is mapped to the description information of the tool interface. The AI agent queries alarm information by calling the first command-line interface command through the tool interface according to natural language instructions, and automatically arranges and calls the second command-line interface command to perform alarm confirmation operation based on the query results.
[0055] In this embodiment, CLI inherently possesses orchestration and composition capabilities, which can be used by AI agents to perform complex operations. This embodiment automatically registers CLI as an MCP tool, with the specific mapping rules as follows: Each CLI command is automatically registered as an MCP Tool; CLI parameters are mapped to the Tool's input_schema (in JSON Schema format). CLI output is mapped to the content returned by the Tool (text / json format); CLI help is mapped to the tool's description; Additional note: Inject use cases, dependencies between tools, and side effect levels (read-only / recoverable / irreversible) into the tool metadata so that the agent can perform security assessments during orchestration.
[0056] Based on and Figure 1 Using the same principle as the method shown, this embodiment of the invention also provides a unified access system for network management and control systems, such as... Figure 7 As shown, it includes: The heterogeneous conversion module is used to convert front-end business operations of the graphical user interface into first command-line interface commands through a first conversion channel; and to convert client business functions based on remote procedure calls into second command-line interface commands through a second conversion channel. The namespace management module is used to register the first command-line interface command and the second command-line interface command to a unified command-line namespace and construct a unified command tree containing different command prefixes. The command routing module is used to receive call requests and, based on the command prefix in the call request, transparently distribute the call request to the corresponding backend service through the command routing engine; The agent adaptation module is used to register the command-line interface commands in the unified command tree as tool interfaces that can be called by the artificial intelligence agent through a standard protocol, so that the artificial intelligence agent can automatically control the network management and control system through the tool interface.
[0057] The unified access system of the network management and control system in this embodiment of the invention can execute the unified access method of the network management and control system provided in this embodiment of the invention. The implementation principle is similar. The actions performed by each module and unit in the unified access system of the network management and control system in each embodiment of the invention correspond to the steps in the unified access method of the network management and control system in each embodiment of the invention. For detailed functional descriptions of each module of the unified access system of the network management and control system, please refer to the descriptions in the corresponding unified access method of the network management and control system shown above, which will not be repeated here.
[0058] The unified access system of the aforementioned network management and control system can be a computer program (including program code) running on a computer device. For example, the unified access system of the network management and control system is an application software. The application software can be used to execute the corresponding steps in the method provided in the embodiments of the present invention.
[0059] The modules described in the embodiments of the present invention can be implemented in software or hardware. The names of the modules are not, in some cases, limiting the scope of the module itself.
[0060] Based on the same principles as the methods shown in the embodiments of the present invention, the embodiments of the present invention also provide an electronic device, which may include, but is not limited to: a processor and a memory; the memory for storing computer programs; and the processor for executing the methods shown in any embodiment of the present invention by invoking the computer programs.
[0061] In one alternative embodiment, an electronic device is provided, such as Figure 8 As shown, Figure 8 The illustrated electronic device includes a processor and a memory. The processor and memory are connected, for example, via a bus. Optionally, the electronic device may also include a transceiver, which can be used for data interaction between the electronic device and other electronic devices, such as sending and / or receiving data. It should be noted that in practical applications, the transceiver is not limited to one unit, and the structure of this electronic device does not constitute a limitation on the embodiments of the present invention.
[0062] The memory stores application code (computer program) that executes the present invention, and its execution is controlled by a processor. The processor executes the application code stored in the memory to implement the content shown in the foregoing method embodiments.
[0063] Among these, electronic devices can also be terminal devices. Figure 8 The electronic device shown is merely an example and should not be construed as limiting the functionality and scope of use of the embodiments of the present invention.
[0064] This invention provides a computer-readable storage medium storing a computer program that, when run on a computer, enables the computer to execute the corresponding content in the aforementioned method embodiments.
[0065] According to another aspect of the present invention, a computer program product or computer program is also provided, which includes computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the methods provided in the various embodiments described above.
[0066] The aforementioned computer-readable storage medium carries one or more programs, which, when executed by the electronic device, cause the electronic device to perform the method shown in the above embodiments.
[0067] The above description is merely a preferred embodiment of the present invention and an explanation of the technical principles employed. Those skilled in the art should understand that the scope of disclosure in this invention is not limited to technical solutions formed by specific combinations of the above-described technical features, but should also cover other technical solutions formed by arbitrary combinations of the above-described technical features or their equivalents without departing from the above-described concept. For example, technical solutions formed by substituting the above features with (but not limited to) technical features with similar functions disclosed in this invention.
Claims
1. A unified access method for a network management and control system, characterized in that, The method includes: The first conversion channel converts front-end business operations of the graphical user interface into first command-line interface commands; the second conversion channel converts client business functions based on remote procedure calls into second command-line interface commands. Register the first command-line interface command and the second command-line interface command to a unified command-line namespace to construct a unified command tree containing different command prefixes; Receive a call request, and based on the command prefix in the call request, transparently distribute the call request to the corresponding backend service through the command routing engine; The command-line interface commands in the unified command tree are registered as tool interfaces that can be called by the artificial intelligence agent through a standard protocol, so that the artificial intelligence agent can automatically control the network management and control system through the tool interface.
2. The unified access method for a network management and control system according to claim 1, characterized in that, Through the first conversion channel, the front-end business operations of the graphical user interface are converted into the first command-line interface commands, specifically including: Capture document object model interaction events and hypertext transfer protocol requests on front-end pages using the browser's automation engine; By combining the pre-configured semantic mapping configuration table, the captured Hypertext Transfer Protocol requests are subjected to interface endpoint discovery and semantic annotation, and the operation dependencies are determined based on the document object model interaction events. The labeled interface endpoints, parameters, and operational dependencies are abstracted into the first command-line interface command.
3. The unified access method for a network management and control system according to claim 2, characterized in that, This involves using the browser's automation engine to capture Document Object Model (DOM) interaction events and Hypertext Transfer Protocol (HTTP) requests from the front-end page, specifically including: The complete request header and request body of the Hypertext Transfer Protocol request are obtained through the browser developer tools protocol session, and the document object model interaction events are obtained by listening to page node state transitions. The semantic mapping configuration table adopts YAML data serialization format and is used to specify the name, parameter list and output format of the command line interface command; The method further includes: keeping the web session active via background heartbeat and automatically synchronizing tokens before requests to achieve persistent login state.
4. The unified access method for a network management and control system according to claim 1, characterized in that, Through the second conversion channel, client-side business functions based on remote procedure calls are converted into second command-line interface commands, specifically including: Scan the interface description language file and parse it to extract the interface metadata model; Based on the interface metadata model, business domain grouping and method semantic enhancement are performed; The improved method signature and parameters are mapped to the second command-line interface command, and corresponding command-line wrapper code is generated; wherein, the command-line wrapper code is used to parse the parameters of the second command-line interface command and execute the corresponding remote procedure call.
5. The unified access method for a network management and control system according to claim 4, characterized in that, The interface description language file is an ICE Slice file; The method semantic enhancement includes: automatically extracting method annotations, supplementing missing annotations through semantic configuration overwrite files, and marking the side effect level; The process of mapping the enhanced method signature and parameters to the second command-line interface includes: directly mapping basic data type parameters to command-line options, transferring composite data type parameters through JSON or YAML files, and supporting automatic generation of parameter templates.
6. The unified access method for a network management and control system according to claim 1, characterized in that, The unified command tree includes a first subtree and a second subtree, where the first subtree carries the first command line interface command and the second subtree carries the second command line interface command. Based on the command prefix in the call request, the call request is transparently distributed to the corresponding backend service through the command routing engine, specifically including: Extract the command prefix from the call request; Identify the target subtree to which the command prefix belongs; wherein the target subtree is either the first subtree or the second subtree; When the command prefix belongs to the first preset prefix, the target subtree is determined to be the first subtree, and the Hypertext Transfer Protocol Stack or Secure Hypertext Transfer Protocol Stack is invoked to distribute the request to the Java-based backend service; When the command prefix belongs to the second preset prefix, the target subtree is determined to be the second subtree, and the ICE remote procedure call protocol stack is invoked to distribute the request to the C++-based backend service.
7. The unified access method for a network management and control system according to claim 1, characterized in that, Registering the command-line interface commands in the unified command tree as tool interfaces callable by the AI agent through a standard protocol enables the AI agent to automate the network management and control system via the tool interfaces. Specifically, this includes: Each command-line interface command is registered as a tool interface through the model context protocol; The parameters of the command-line interface commands are mapped to the input mode of the tool interface, the output of the command-line interface commands is mapped to the return content of the tool interface, and the help information of the command-line interface commands is mapped to the description information of the tool interface. The AI agent queries alarm information by calling the first command-line interface command through the tool interface according to natural language instructions, and automatically arranges and calls the second command-line interface command to perform alarm confirmation operation based on the query results.
8. A unified access system for a network management and control system, characterized in that, include: The heterogeneous conversion module is used to convert the front-end business operations of the graphical user interface into the first command line interface commands through the first conversion channel; The second conversion channel transforms client business functions based on remote procedure calls into second command-line interface commands. The namespace management module is used to register the first command-line interface command and the second command-line interface command to a unified command-line namespace and construct a unified command tree containing different command prefixes. The command routing module is used to receive call requests and, based on the command prefix in the call request, transparently distribute the call request to the corresponding backend service through the command routing engine; The agent adaptation module is used to register the command-line interface commands in the unified command tree as tool interfaces that can be called by the artificial intelligence agent through a standard protocol, so that the artificial intelligence agent can automatically control the network management and control system through the tool interface.
9. A unified access device for a network management and control system, comprising electronic equipment, characterized in that, It includes a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor, when executing the computer program, implements the method of any one of claims 1-7.
10. A unified access medium for a network management and control system, comprising a computer storage medium, characterized in that, The computer storage medium stores a computer program, which, when executed by a processor, implements the method of any one of claims 1-7.