Remote operation and maintenance method and system based on normal form compatibility

Abstract

The invention discloses a remote operation and maintenance method and system based on normal form compatibility, and relates to the technical field of power system automatic operation and maintenance, and the method comprises the steps: constructing a tree mapping structure, presetting an operation template, defining a normal form command and a placeholder replacement rule, and generating a main version normal form template to support cross-model template inheritance adaptation; loading an operation template through a graphical interface, executing standardized acquisition and change operation by utilizing semantic recognition and placeholder replacement rules, calling a rollback command, and constructing a structured JSON strategy model; acquiring a device strategy based on the structured JSON strategy model, generating a target device configuration instruction, and executing an automatic rollback mechanism to complete strategy migration and strategy mutual guidance; according to the method, a remote operation and maintenance system with cross-model compatibility, controllable parameters and recoverable process is constructed through normal form template inheritance, structured strategy modeling and an automatic rollback mechanism.

Description

Technical Field

[0001] The present invention relates to the technical field of automated operation and maintenance of power systems, and in particular to a remote operation and maintenance method and system based on paradigm compatibility. Background Art

[0002] With the continuous development of modern society, electricity, as the lifeblood of national economic development, has become increasingly important for its safe and stable operation. The power monitoring system, the "brain" of the power system, is responsible for real-time monitoring and management of power production, transmission, and distribution. In recent years, with the rapid development of information technology, power monitoring systems have gradually shifted from traditional analog monitoring systems to digital and intelligent ones. However, this has brought with it increasingly prominent issues regarding safe operation and maintenance.

[0003] The complexity and scale of power monitoring systems are constantly increasing. Modern power systems are vast and complex, involving multiple links such as power generation, transmission, transformation, and distribution, all of which are interconnected and constrained. This complexity requires power monitoring systems to be highly reliable and real-time to ensure safe operation.

[0004] However, as the system scale and functionality increase, the difficulty of securely operating and maintaining monitoring systems also increases. Power monitoring systems are composed of a large number of hardware devices and software systems, which require regular maintenance and upgrades. Due to the wide variety and widespread distribution of these devices, traditional manual maintenance methods are inefficient and unable to meet the operational and maintenance needs of modern power systems. The skill requirements for power monitoring system operators are gradually increasing. Currently, many power companies have incomplete training systems for their operators, resulting in varying skill levels and difficulty adapting to the operational and maintenance demands of modern power monitoring systems. Summary of the Invention

[0005] In view of the above-mentioned problems, the present invention is proposed.

[0006] Therefore, the technical problem solved by the present invention is: the existing remote operation and maintenance methods have the following problems: inconsistent device command specifications, templates cannot be reused, manual debugging is heavy, operation configuration is uncontrollable, the policy migration process lacks structured support, and there is a failure rollback mechanism, which leads to low operation and maintenance efficiency and poor cross-model compatibility. The problem also involves how to achieve standardization, automation and structured migration of remote operation and maintenance operations among multiple models of equipment by building a unified paradigm operation template system, a graphical command generation mechanism and a structured policy modeling method.

[0007] In order to solve the above technical problems, the present invention provides the following technical solutions: a remote operation and maintenance method based on normalization compatibility, including building a tree mapping structure, presetting operation templates, defining normalized commands and placeholder replacement rules, generating a master version normalized template to support cross-model template inheritance adaptation; loading operation templates through a graphical interface, using semantic recognition and placeholder replacement rules to perform standardized collection and change operations, calling rollback commands, and building a structured JSON policy model; collecting device policies based on the structured JSON policy model, generating target device configuration instructions, and executing an automatic rollback mechanism to complete policy migration and policy mutual guidance; the master version normalized template includes, based on The normalized operation template inheritance mechanism based on the tree mapping relationship performs cross-model structured inheritance and differential configuration by setting the main version node in the device hierarchy structure; the placeholder replacement rules include defining the parameter position in the operation template as a replaceable identifier, and combining the parameter identification component to automatically identify, bind and fill the input parameters with a template parameter parsing mechanism; the structured JSON policy model includes a multi-field policy data modeling mechanism built based on the execution results of the policy collection class template, which formats and parses the command return results and extracts fields through the parsing template to generate a JSON data format that conforms to the predefined structure to describe the policy attributes and policy array collection.

[0008] As a preferred solution of the remote operation and maintenance method based on normalized compatibility described in the present invention, the main version normalized template includes a main version node in a tree mapping structure of device type, manufacturer, and model. The sub-model device inherits the normalized command and operation template through the main version node, configures the differentiated operation template when there are command differences, and the remaining part automatically reuses the main template configuration.

[0009] As a preferred solution of the remote operation and maintenance method based on paradigm compatibility described in the present invention, the graphical interface includes a parameter identification component for loading and binding operation templates, entering parameters, and performing placeholder replacement; the parameter identification component supports semantic recognition, parameter classification matching and manual verification.

[0010] As a preferred solution of the remote operation and maintenance method based on paradigm compatibility described in the present invention, wherein: the operation template includes a policy acquisition type operation template and a policy change type operation template formed by combining atomic-level operation commands in a fixed order; the policy acquisition type operation template is used for inspection task configuration and supports scheduled execution; the policy change type operation template is used to bind each policy change type operation command to a corresponding rollback command, and automatically trigger the rollback process when the change operation fails.

[0011] As a preferred solution of the remote operation and maintenance method based on normalization compatibility described in the present invention, wherein: the structured JSON policy model includes a policy data structure generated based on the execution result of the policy acquisition class template combined with the JS parsing function of the parsing template; the parsing template includes character set parsing, context interception positioning and key field extraction of the returned operation command, obtaining policy attributes, filling the policy attributes into a JSON structure that conforms to the predefined data pattern, and performing a unified description of policy attributes across models; the JSON structure includes policy attributes and a policy array set.

[0012] As an optimal solution of the remote operation and maintenance method based on normalization compatibility described in the present invention, the structured JSON policy model also includes: the structured JSON policy model is stored in a structured database, the database is indexed and classified by device type, manufacturer, and model, and supports version management and structural unification of policy collection attributes; the structured database provides policy data retrieval, field comparison and policy differentiation echo for policy migration and rollback mechanism calls.

[0013] As a preferred solution of the remote operation and maintenance method based on normalization compatibility described in the present invention, the policy migration and policy mutual guidance include reading a structured JSON policy model based on a policy change operation template, generating target device configuration instructions through field mapping and placeholder replacement, calling a bound rollback command for rollback when the configuration instruction execution fails, automatically opening an operation and maintenance channel when performing policy migration and policy mutual guidance, and automatically closing the channel after the policy operation is completed; the operation and maintenance channel includes an identity authentication mechanism, command auditing and access time control.

[0014] Another object of the present invention is to provide a remote operation and maintenance system based on normalized compatibility, which can set the main version normalized template by constructing a tree mapping structure of device type, manufacturer, and model, and realize the inheritance and reuse of operation templates among different models of devices, thereby solving the problems of inconsistent command formats of multi-manufacturer devices, repeated configuration of operation templates, and complex debugging in current remote operation and maintenance technology.

[0015] As an optimal solution of the remote operation and maintenance system based on paradigm compatibility described in the present invention, it includes: a paradigm template management module, a graphical operation and maintenance execution module, and a policy migration control module; the paradigm template management module is used to construct a tree mapping structure of device type, manufacturer, and model, preset policy collection class and policy change class operation templates, define paradigm commands and placeholder replacement rules, generate main version paradigm templates and support cross-model device template inheritance and differential configuration; the graphical operation and maintenance execution module is used to load operation templates through a graphical interface, combine semantic recognition and placeholder replacement rules to generate collection and change commands, call rollback commands, combine parsing templates and JS functions to build a structured JSON policy model, and uniformly represent device policy attributes and policy array fields; the policy migration control module performs field mapping and parameter filling based on the structured JSON policy model, generates target device configuration instructions and executes policy migration and policy mutual guidance, and controls the start and stop of the operation and maintenance channel through an automated mechanism.

[0016] A computer device includes a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement a remote operation and maintenance method based on paradigm compatibility.

[0017] A computer-readable storage medium stores a computer program, which, when executed by a processor, implements the steps of a remote operation and maintenance method based on paradigm compatibility.

[0018] Beneficial effects of the present invention: The remote operation and maintenance method based on paradigm compatibility provided by the present invention realizes cross-model inheritance of templates through the main version paradigm template, effectively reduces repeated debugging and configuration operations, improves equipment operation and maintenance efficiency, and reduces the technical requirements for operation and maintenance personnel; constructs operation and maintenance commands through a graphical interface and placeholder replacement rules, realizes standardized generation of equipment inspections and policy changes, and saves a lot of operation and maintenance workload; completes policy backup and mutual guidance through a structured JSON policy model combined with field mapping, improves policy migration efficiency, and greatly improves efficiency for rapid switching and recovery of faulty equipment and migration of policies when old and new equipment are replaced; the present invention has achieved better results in multi-model equipment adaptation, remote command generation automation, and policy configuration reuse. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the following briefly introduces the drawings required for use in the description of the embodiments. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0020] Figure 1This is an overall flow chart of a remote operation and maintenance method based on paradigm compatibility provided in Example 1 of the present invention.

[0021] Figure 2 An operation template execution logic diagram of a remote operation and maintenance method based on normalization compatibility provided in Example 1 of the present invention.

[0022] Figure 3 A flow chart of policy migration and mutual guidance of a remote operation and maintenance method based on paradigm compatibility is provided in Example 1 of the present invention. DETAILED DESCRIPTION

[0023] To make the above-mentioned objects, features, and advantages of the present invention more clearly understood, the following detailed description of the specific embodiments of the present invention is given in conjunction with the accompanying drawings. It is obvious that the described embodiments are only part of the embodiments of the present invention, not all of them. Based on the embodiments of the present invention, all other embodiments obtained by ordinary persons in this field without creative work should fall within the scope of protection of the present invention.

[0024] Example 1, reference Figure 1-Figure 3 , as an embodiment of the present invention, provides a remote operation and maintenance method based on normalization compatibility, including:

[0025] S1: Build a tree mapping structure, preset operation templates, define normalized commands and placeholder replacement rules, and generate a master version normalized template to support cross-model template inheritance adaptation.

[0026] Furthermore, the main version paradigm template includes a main version node in a tree mapping structure of device type, manufacturer, and model. Sub-model devices inherit the normalized command and operation templates through the main version node. When there are command differences, differentiated operation templates are configured, and the remaining parts automatically reuse the main template configuration.

[0027] It should be noted that a tree mapping structure of device type-manufacturer-model is constructed, such as switch-H3C-S5120. An operation template list is configured under the corresponding device model node. Each type of operation template consists of multiple operation commands in sequence. Change operation commands are introduced into predefined placeholders as replaceable identifiers for parameter positions, such as "undo rule#ruleid", which are used to replace them by input parameters in the graphical interface. For devices that support command operations, the commands can be paradigm commands; for devices that only support API interfaces, the API interface suffix and input parameters are defined. After all operation templates are configured and debugged, the paradigm operation templates of devices of the same manufacturer and different models are automatically inherited and generated through the XGBoost gradient boosting decision tree algorithm. It supports setting one model of device as the main version node, and the sub-models under the device can automatically inherit the operation definition and template content of the main version node. The paradigm policy template recommendation with the smallest loss function value is calculated and selected, which is expressed as:

[0028]

[0029] Among them, L(φ) represents the total evaluation value of the normalized operation template, which is an overall indicator to measure whether the current template is "accurately configured and reasonably structured" in equipment operation and maintenance. represents the error of the i-th operation command, that is, the difference between the “actual result returned by the device” and the “template prediction result”, i represents the operation command index, n represents the total number of executed operation commands, k represents the normalized operation template index, K represents the number of normalized operation templates, Ω(f k ) represents the structural complexity of the k-th operation template, f k Expressed as:

[0030]

[0031] Among them, Template k (x) indicates that the input parameters are filled into the predefined placeholder position in the template. x represents the parameters input by the operation and maintenance personnel or preset by the system. Indicates mapping, {cmd1,cmd2,···,cmd m} represents a set of standardized configuration commands that conform to the device model command specification. The generation of L(φ) enables the system to automatically select or generate a template solution with "small error and simple structure" when facing multiple manufacturers and multiple models of devices. It is used for remote device policy collection and change operations. If there are differentiated command requirements for sub-models, differentiated operation templates can be configured independently. Undefined parts default to the main version configuration.

[0032] It should also be noted that by introducing the device tree structure and main version template, the structured inheritance and minimally differentiated configuration of normalized command and operation templates are achieved, breaking through the problem of repeated template configuration caused by differences in device models in the existing technology, and realizing the organizational unification and configuration reuse of templates among multiple models of equipment, reducing the complexity of operation and maintenance adaptation, improving the efficiency of template debugging, and providing a stable command execution framework foundation for subsequent policy execution and policy migration.

[0033] S2: Load the operation template through the graphical interface, use semantic recognition and placeholder replacement rules to perform standardized collection and change operations, call the rollback command, and build a structured JSON policy model.

[0034] Furthermore, the graphical interface includes a parameter recognition component for loading binding operation templates, entering parameters, and performing placeholder replacement; the parameter recognition component supports semantic recognition, parameter classification matching, and manual verification.

[0035] It should be noted that semantic recognition includes parsing the parameter content entered by the operation and maintenance personnel, and matching them according to the semantic features and the placeholder types defined in the operation template; parameter classification matching includes comparing the execution results with the system predefined parameter types (IP address, numerical value, string); manual verification includes, after the automatic recognition is completed, allowing the operation and maintenance personnel to manually confirm or modify the binding results, thereby improving the replacement accuracy and operation safety.

[0036] It should be noted that the operation templates include policy collection type operation templates and policy change type operation templates formed by combining atomic-level operation commands in a fixed order; the policy collection type operation templates are used for inspection task configuration and support scheduled execution; the policy change type operation templates are used to bind each policy change type operation command to a corresponding rollback command, and automatically trigger the rollback process when the change operation fails.

[0037] It should also be noted that policy collection operation templates include but are not limited to interface collection, link aggregation collection, VLAN collection, port mirroring collection, port security collection, static routing collection, dynamic routing collection, ACL collection, MAC collection, link discovery collection, SNMP collection, policy hit count collection, and device parameter range collection; switch policy change templates include but are not limited to ACL addition, ACL deletion, ACL remark information modification, rule addition, and rule modification.

[0038] It should also be noted that after loading the operation template through the graphical interface and the operation and maintenance personnel select the successfully debugged policy collection or policy change operation template, the system automatically calls the parameter identification component to parse the input operation and maintenance parameters. The placeholder replacement mechanism is activated after the binding is completed, and the actual parameter value entered by the user replaces the corresponding placeholder in the template, such as replacing #ruleid with the specific rule number to generate a standardized collection command or change command. For the policy change operation template, each atomic operation command is bound to a corresponding rollback command. In the event of a change failure or abnormal interruption, the system automatically calls the rollback command to restore the status. After the command is executed, the system passes the execution result of the policy collection template to the parsing template for processing, and calls the JS parsing function to perform character parsing, context interception positioning and key field extraction operations on the returned character set. The extracted policy attributes are filled into a JSON structure that conforms to the predefined data model to construct a structured JSON policy model.

[0039] It should also be noted that through the graphical interface combined with semantic recognition and placeholder replacement mechanism, automatic binding of operation and maintenance parameters and operation templates is achieved, avoiding manual command writing, improving the standardization of input and the accuracy of execution; introducing parameter classification matching and manual verification mechanism to ensure that parameters are consistent with template requirements, enhancing the controllability of the operation and maintenance process; binding rollback commands to policy change operation templates, building an automatically recoverable operation process, breaking through the irreversible technical limitations of traditional commands, and realizing structured, standardized and reversible control of operation and maintenance execution.

[0040] S3: Collect device policies based on the structured JSON policy model, generate target device configuration instructions, and execute the automatic rollback mechanism to complete policy migration and policy interaction.

[0041] Furthermore, the structured JSON policy model includes a policy data structure generated based on the execution result of the policy collection class template combined with the JS parsing function of the parsing template; the parsing template includes character set parsing, context interception positioning and key field extraction of the returned operation command, obtaining policy attributes, filling the policy attributes into a JSON structure that conforms to the predefined data model, and uniformly describing the policy attributes across models; the JSON structure includes policy attributes and a policy array collection.

[0042] It should be noted that the structured JSON policy model also includes that the structured JSON policy model is stored in a structured database, which is indexed and classified by device type, manufacturer, and model, and supports version management and structural unification of policy collection attributes; the structured database provides policy data retrieval, field comparison, and policy differentiation echo for policy migration and rollback mechanism calls.

[0043] It should also be noted that policy migration and policy mutual guidance include reading a structured JSON policy model based on a policy change operation template, generating target device configuration instructions through field mapping and placeholder replacement, calling the bound rollback command to roll back to the backup when the configuration instruction execution fails, automatically opening the operation and maintenance channel when performing policy migration and policy mutual guidance, and automatically closing the channel after the policy operation is completed; the operation and maintenance channel includes an identity authentication mechanism, command auditing, and access time control.

[0044] It should also be noted that, based on the structured JSON policy model, when backing up policies, users can proactively trigger or configure the execution cycle according to patrol tasks. The system then loads the debugged policy collection operation template based on the device type and manufacturer, issues the corresponding operation command to the device, and obtains the return result. The system then calls the predefined JS parsing function in the parsing template to process the command return character set, extracts the context based on device model differences, and populates these policy attributes into a JSON structure that conforms to the predefined data schema, forming a collection of policy attributes and policy arrays. This is ultimately stored in a structured database and indexed by device type, manufacturer, and model, supporting policy data retrieval, field comparison, and differentiated display. During policy migration, the system reads the structured JSON policy model based on the policy change operation template, combines field mapping with a placeholder replacement mechanism, generates configuration instructions for the target device, and automatically loops through array-type policy fields to complete policy writes in batches. If any configuration instruction fails to execute, the corresponding rollback command is automatically invoked to restore the pre-change state. The entire migration process is executed through the operation and maintenance channel, supporting identity authentication mechanisms, command auditing, and access time control, ensuring that policy migration forms a controllable and reversible closed loop in terms of data structure, operation process, and security control.

[0045] It should also be noted that by building a structured JSON policy model, standardized expression and cross-model compatibility of device policies are achieved, which improves the versatility and reusability of policy data; combined with a structured database for index classification and version management, it provides reliable data support for policy migration; through field mapping and placeholder replacement mechanism, target device configuration instructions are automatically generated, and rollback commands are called in case of failure to ensure the recoverability of policy changes; an operation and maintenance channel mechanism is introduced, combined with identity authentication, command auditing and time control, to achieve a secure closed loop of the policy migration process.

[0046] Example 2 is an embodiment of the present invention, which provides a remote operation and maintenance system based on normalization compatibility, including a normalization template management module, a graphical operation and maintenance execution module, and a policy migration control module.

[0047] Among them, the paradigm template management module includes a tree mapping structure construction module, an operation template configuration module, a paradigm command and placeholder definition module, and a main version template inheritance module.

[0048] It should be noted that the tree mapping structure construction module is used to construct a tree mapping structure of device types, manufacturers, and models, and is used to organize the hierarchical relationship between the main version node and the sub-model device as the basis for template inheritance; the operation template configuration module is used to preset policy collection and policy change operation templates. The template is composed of multiple atomic-level operation commands combined in a fixed order, and supports inspection and policy change task configuration; the normalized command and placeholder definition module is used to define the normalized command structure, and set placeholders such as "#ruleid" for parameter abstraction, which is compatible with command differences of different models of devices; the main version template inheritance module is used to support setting the model as the main version node, and the sub-model device inherits the normalized command and operation template, and configures differentiated templates for commands with differences. The remaining parts are automatically reused to reduce template redundancy.

[0049] It should also be noted that the tree mapping structure construction module is used to establish the main version node structure of the device type, manufacturer, and model. Subsequently, the operation template configuration module configures the policy collection type and policy change type operation templates in the main version node. The normalized command and placeholder definition module completes the command structure standardization and parameter abstraction. Finally, the main version template inheritance module passes the main template content to the sub-model device in a hierarchical structure and supports differentiated template coverage.

[0050] The graphical operation and maintenance execution module includes a template loading and selection module, a parameter identification and placeholder replacement module, a rollback command binding module, and a structured JSON strategy model construction module.

[0051] It should be noted that the template loading and selection module is used to provide a graphical interface for loading and debugging successfully policy collection or policy change operation templates, supporting operation and maintenance personnel to visually select operation templates; the parameter identification and placeholder replacement module is used for semantic identification, parameter classification matching and manual verification, automatically binding and replacing the operation and maintenance input parameters with the placeholders in the operation template to generate standard commands; the rollback command binding module is used to configure the corresponding rollback command for each policy change operation command, supporting automatic triggering of the rollback process when the change fails, and enhancing the controllability of the operation; the structured JSON policy model construction module is used to call the JS parsing function in the parsing template to process the returned results after executing the collection command, extract the policy attributes and fill them into the predefined JSON structure.

[0052] It should also be noted that the template loading and selection module first loads and binds the successfully debugged operation template in the graphical interface, and then the parameter identification and placeholder replacement module performs semantic identification, parameter classification matching and manual verification in sequence, and binds the operation and maintenance parameters to the placeholders in the template. Then the rollback command binding module associates each change operation command with the corresponding rollback command, and finally the structured JSON policy model construction module parses the command return result and generates structured policy data.

[0053] The policy migration control module includes a policy backup and modeling module, a policy change instruction generation module, a policy rollback control module, and an operation and maintenance channel management module.

[0054] It should be noted that the policy backup and modeling module is used to obtain device policy information through policy collection operation templates, use parsing templates to generate structured JSON policy models, and store them in a structured database; the policy change instruction generation module is used to combine policy change operation templates, fill structured policy data into the template through field mapping and placeholder replacement mechanism, and generate target device configuration instructions; the policy rollback control module is used to automatically call the bound rollback command when the policy writing fails, perform state recovery operations, and ensure the reliability and reversibility of the policy migration process; the operation and maintenance channel management module is used to automatically open a controlled operation and maintenance channel during policy migration or mutual guidance, and automatically close it after the operation and maintenance is completed. The channel supports identity authentication, command auditing and access time control.

[0055] It should also be noted that the policy backup and modeling module first generates a structured JSON policy model through the policy collection operation template and stores it in a structured database. Then the policy change instruction generation module reads the structured JSON policy model and combines the policy change operation template to generate the target device configuration instructions through field mapping and placeholder replacement. If the execution fails, the policy rollback control module automatically triggers the bound rollback command to restore the status. The entire migration process is controlled by the operation and maintenance channel management module to control the opening and closing of the channel before and after the policy execution and to ensure access rights and command auditing.

Claims

1. A remote operation and maintenance method based on paradigm compatibility, characterized in that: include: Build a tree mapping structure, preset operation templates, define normalized commands and placeholder replacement rules, generate a master version normalized template, and support cross-model template inheritance adaptation; Load operation templates through a graphical interface, use semantic recognition and placeholder replacement rules to perform standardized collection and change operations, call rollback commands, and build a structured JSON policy model; Collect device policies based on a structured JSON policy model, generate target device configuration instructions, and implement an automatic rollback mechanism to complete policy migration and policy interaction; The master version paradigm template includes a normalized operation template inheritance mechanism based on a tree mapping relationship. By setting the master version node in the device hierarchy, cross-model structured inheritance and differential configuration are performed. The placeholder replacement rules include defining the parameter positions in the operation template as replaceable identifiers and combining the parameter identification component with a template parameter parsing mechanism to automatically identify, bind, and fill in the input parameters; The structured JSON policy model includes a multi-field policy data modeling mechanism built based on the execution results of the policy collection class template. It formats and parses the command return results and extracts fields through the parsing template to generate a JSON data format that conforms to the predefined structure to describe the policy attributes and policy array collection.

2. The remote operation and maintenance method based on paradigm compatibility according to claim 1, characterized in that: The main version paradigm template includes: The main version node in the tree mapping structure of device type, manufacturer, and model. Sub-model devices inherit the normalized command and operation templates through the main version node. When there are command differences, differentiated operation templates are configured. The remaining parts automatically reuse the main template configuration.

3. The remote operation and maintenance method based on normalization compatibility according to claim 2, characterized in that: The graphical interface includes: Parameter identification component that loads binding operation templates, enters parameters, and performs placeholder replacement; The parameter recognition component supports semantic recognition, parameter classification matching and manual verification.

4. The remote operation and maintenance method based on paradigm compatibility according to claim 3, characterized in that: The operation template includes: Strategy collection operation templates and strategy change operation templates are formed by combining atomic operation commands in a fixed order; The policy collection operation template is used for inspection task configuration and supports scheduled execution; The policy change operation template is used to bind each policy change operation command to a corresponding rollback command, and automatically trigger a rollback process when the change operation fails.

5. The remote operation and maintenance method based on paradigm compatibility according to claim 4, characterized in that: The structured JSON policy model includes: The strategy data structure is generated based on the execution result of the strategy collection class template and the JS parsing function of the parsing template; The parsing template includes character set parsing, context interception positioning and key field extraction of the returned operation command, obtaining policy attributes, filling the policy attributes into a JSON structure that conforms to the predefined data model, and performing a unified description of policy attributes across models; The JSON structure includes policy attributes and policy array collections.

6. The remote operation and maintenance method based on paradigm compatibility according to claim 5, characterized in that: The structured JSON policy model also includes, The structured JSON policy model is stored in a structured database, which is indexed and classified by device type, manufacturer, and model, supporting version management and structural unification of policy collection attributes; The structured database provides policy data access, field comparison and policy differentiation echo for policy migration and rollback mechanism calls.

7. The remote operation and maintenance method based on normalization compatibility according to claim 6, characterized in that: The strategy migration and strategy mutual guidance include: Reads structured JSON policy models based on policy change operation templates, generates target device configuration instructions through field mapping and placeholder replacement, and calls the bound rollback command to roll back when the configuration instruction execution fails. Automatically opens the operation and maintenance channel during policy migration and policy mutual guidance, and automatically closes the channel after the policy operation is completed. The operation and maintenance channel includes identity authentication mechanism, command auditing and access time control.

8. A remote operation and maintenance system based on normalization compatibility, using the remote operation and maintenance method based on normalization compatibility according to any one of claims 1 to 7, characterized in that: Includes paradigm template management module, graphical operation and maintenance execution module, and policy migration control module; The paradigm template management module is used to build a tree-like mapping structure of device types, manufacturers, and models, preset policy collection and policy change operation templates, define paradigm commands and placeholder replacement rules, generate master version paradigm templates, and support cross-model device template inheritance and differential configuration; The graphical operation and maintenance execution module is used to load the operation template through the graphical interface, generate the collection and change commands by combining semantic recognition and placeholder replacement rules, call the rollback command, and build a structured JSON policy model by combining the parsing template and JS function to uniformly represent the device policy attributes and policy array fields; The policy migration control module performs field mapping and parameter filling based on the structured JSON policy model, generates target device configuration instructions, executes policy migration and policy interaction, and controls the start and stop of the operation and maintenance channel through an automated mechanism.

9. A computer device comprising a memory and a processor, wherein the memory stores a computer program, wherein: When the processor executes the computer program, the steps of the remote operation and maintenance method based on normalization compatibility according to any one of claims 1 to 7 are implemented.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the remote operation and maintenance method based on normalization compatibility according to any one of claims 1 to 7 are implemented.

Images