A rule-driven power control system configuration parameter version management method

Abstract

The application discloses a rule-driven power control system configuration parameter version management method in the technical field of power automation and industrial software, which comprises the following steps: constructing a first version snapshot based on a first structured parameter document and a first configuration file set; grouping and aligning the structured parameter documents in the first version snapshot and pre-constructed historical version snapshots according to node feature keys to generate object-level difference results and attribute-level difference results; performing file-level comparison on the configuration file sets in the first version snapshot and the pre-constructed historical version snapshots to generate file-level difference results; and summarizing the object-level difference results, the attribute-level difference results and the file-level difference results to output unified difference results corresponding to the first version snapshot and the historical version snapshots. The application can alleviate the technical problems of the prior art, such as scattered parameter sources, version solidification relying on manual operation, and difficulty in unified comparison of object structure changes and file changes, thereby affecting the management efficiency.

Description

Technical Field

[0001] This invention relates to the field of power automation and industrial software technology, and in particular to a rule-driven method for version management of configuration parameters of power control systems. Background Technology

[0002] Configuration parameters for power control systems are typically distributed across database objects, device-side configuration files, and some encrypted files. Existing management schemes for power control system configuration parameters generally suffer from the following drawbacks: parameter sources are scattered, version fixing relies on manual operation, traceability is difficult, changes in object structure and file are difficult to compare uniformly, and changes in sequence can easily lead to false alarms; ultimately affecting management efficiency.

[0003] Therefore, there is an urgent need for a rule-driven method for managing the version of configuration parameters of power control systems to solve the above-mentioned technical problems. Summary of the Invention

[0004] The purpose of this invention is to overcome the shortcomings of the prior art and provide a rule-driven power control system configuration parameter version management method, which can alleviate the technical problems of the prior art, such as the dispersed parameter sources, the reliance on manual operation for version fixing, and the difficulty in uniformly comparing changes in object structure and file, thus affecting management efficiency.

[0005] To achieve the above objectives, the present invention is implemented using the following technical solution: In a first aspect, the present invention provides a rule-driven method for version management of configuration parameters in a power control system, applied to a power control system, the power control system including a database and a version management host signal-connected to the database, comprising: Read and parse the predefined rule file to obtain the database object collection rules and configuration file collection rules; According to the database object acquisition rules, the attributes of the target object are extracted from the database in real time to generate a first structured parameter document; According to the configuration file collection rules, configuration files are collected from the version management host in real time to generate the first configuration file set; A first version snapshot is built based on the first structured parameter document and the first configuration file set; The structured parameter documents in the first version snapshot and the pre-built historical version snapshot are grouped and aligned according to the node feature key to generate object-level difference results and attribute-level difference results; The configuration file sets in the first version snapshot and the pre-built historical version snapshot are compared at the file level to generate file-level difference results. The object-level difference results, attribute-level difference results, and file-level difference results are summarized, and a unified difference result corresponding to the first version snapshot and the historical version snapshot is output.

[0006] Furthermore, the database object collection rules include: The objects to be collected are determined according to the preset object collection range. The hierarchical structure of the objects to be collected is traversed according to the preset hierarchical traversal strategy to determine the target objects. The target objects are filtered according to the preset attribute extraction and filtering strategy to extract the attribute information of the target objects. The structured parameter document organizes the target object and its attribute information in the form of hierarchical nodes. Each hierarchical node includes at least one of the following: node identifier, node name, and node type.

[0007] Furthermore, the configuration file collection rules include at least one of the following: deployment host identifier, file directory, file name pattern, file type, and access method.

[0008] Furthermore, the step of grouping and aligning by node feature keys to generate object-level difference results and attribute-level difference results includes: Extract the node feature keys of each level node in the first structured parameter document and the historical structured parameter documents, perform peer matching based on the node feature keys within the same parent node range, and generate object-level difference results; For nodes that match successfully, perform an item-by-item comparison of attribute items to determine at least one type of difference among attribute addition, attribute deletion, and attribute value change, and generate attribute-level difference results. The node feature key includes at least one of a unique identifier, a business code, and a preset combination feature attribute.

[0009] Furthermore, the configuration file sets in the first version snapshot and the pre-built historical version snapshot are compared at the file level to generate file-level difference results, including... The configuration file sets in the first version snapshot and the historical version snapshot are compared in terms of file existence status and file content to detect at least one type of difference among file addition, file deletion and file content change, and file-level difference results are generated based on the detection results.

[0010] Furthermore, the unified difference result includes at least one of the following: version identifier, object identifier, difference type, difference location, and difference content, used to characterize the parameter differences and configuration file differences between different version snapshots.

[0011] Furthermore, it also includes: After outputting the unified difference results, the first version snapshot built in real time is stored as a historical version snapshot.

[0012] Secondly, the present invention provides a rule-driven power control system configuration parameter version management device, comprising: The rule management module is used to read and parse predefined rule files to obtain database object collection rules and configuration file collection rules; The database parameter acquisition module is used to extract the attributes of the target object from the database in real time according to the database object acquisition rules, and generate a first structured parameter document; The remote file acquisition module is used to acquire configuration files from the version management host in real time via a remote connection according to the configuration file acquisition rules, and generate the first configuration file set. The snapshot building module is used to build a first version snapshot based on the first structured parameter document and the first configuration file set; The structured parameter document difference analysis module is used to group and align the structured parameter documents in the first version snapshot and the pre-built historical version snapshot according to the node feature key, and generate object-level difference results and attribute-level difference results. The configuration file set difference analysis module is used to perform file-level comparison of the configuration file sets in the first version snapshot and the pre-built historical version snapshot, and generate file-level difference results. The results output module is used to summarize the object-level difference results, attribute-level difference results, and file-level difference results, and output a unified difference result corresponding to the first version snapshot and the historical version snapshot.

[0013] Furthermore, it also includes a display module for displaying the unified difference results, to display the structured parameter difference results and the configuration file difference results respectively.

[0014] Thirdly, the present invention provides an electronic device including a processor and a memory, wherein the memory stores a program running on the processor, and the program, when executed, implements the method described in any of the preceding claims.

[0015] Compared with the prior art, the beneficial effects achieved by the present invention are as follows: This invention first proposes a rule-driven method for version management of configuration parameters in power control systems. This method uses rule files to drive the acquisition of database object parameters and remote configuration files, and constructs a version snapshot by combining structured parameter documents and configuration file sets acquired at the same time. Furthermore, it performs structured parameter difference analysis and file-level difference analysis on different version snapshots, ultimately outputting a unified difference result. This enables the archiving, difference identification, and historical tracing of the power control system configuration status, further improving management efficiency. Attached Figure Description

[0016] Figure 1This is a flowchart of a rule-driven power control system configuration parameter version management method provided in an embodiment of the present invention; Figure 2 This is a block diagram of a rule-driven power control system configuration parameter version management device provided in an embodiment of the present invention. Detailed Implementation

[0017] The technical solution of the present invention will be described in detail below with reference to the accompanying drawings and specific embodiments. It should be understood that the embodiments and specific features in the embodiments are detailed descriptions of the technical solution of the present application, rather than limitations thereof. In the absence of conflict, the embodiments and technical features in the embodiments can be combined with each other.

[0018] In this invention, the term "and / or" is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent three cases: A alone, A and B together, or B alone. Additionally, in this invention, the character " / " generally indicates that the preceding and following related objects have an "or" relationship. Example 1

[0019] Figure 1 This is a flowchart of the rule-driven power control system configuration parameter version management method according to Embodiment 1 of the present invention. This flowchart only illustrates the logical sequence of the method described in this embodiment. Provided there are no conflicts, different methods may be used in other possible embodiments of the present invention. Figure 1 Complete the steps shown or described in the order indicated.

[0020] The method of this embodiment can be applied to a power control system, which includes a database and a version management host connected to the database. Specifically, it includes the following steps: Step 1: Read and parse the predefined rule file, preferably / etc / remoteParamCompare.xml, to obtain the database object collection rules and configuration file collection rules; The database object collection rules include: The objects to be collected are determined according to the preset object collection range. The hierarchical structure of the objects to be collected is traversed according to the preset hierarchical traversal strategy to determine the target objects. The target objects are filtered according to the preset attribute extraction and filtering strategy to extract the attribute information of the target objects. Among them, database object acquisition rules can be used to limit the types of objects to be read, the range of object identifiers, the parent-child hierarchy, and the range of attribute fields. For example, it can be specified that only device objects, measuring point objects, or control objects within a certain substation range should be read, and the attribute items to be extracted for each type of object can be limited.

[0021] The configuration file collection rules include at least one of the following: deployment host identifier, file directory, file name pattern, file type, and access method; The configuration file collection rules can be used to limit the connection method, file directory, file name pattern, or file path set of the target device. For example, it can be specified to obtain parameter configuration files, template files, or runtime configuration files from a preset directory of a certain device.

[0022] By parsing the pre-defined rule files, the system can adapt to the configuration collection needs of different scenarios by adjusting the rule content without modifying the core program logic.

[0023] Specifically, the rule file adopts an XML structure, with its root node being ReadConfigs, and contains at least the following rule fields: global attribute reading whitelist globalAttrReadList, global attribute filtering blacklist globalAttrNotReadList, database object collection node ReadConfig, and file collection node ReadFile.

[0024] The ReadConfig is used to define database object collection rules. Each ReadConfig includes at least an object identifier id, a rule description desc, a child traversal strategy childMode, an attribute reading strategy attrMode, and an attribute name list attrNameList. Among them, childMode is used to limit the object tree traversal method, including full traversal, partial traversal, or no traversal, and attrMode is used to limit the attribute extraction method, including full reading, no reading, or partial reading by list.

[0025] The ReadConfig can be configured with multiple ChildConfigs sub-rules. Each ChildConfig includes at least an object type otype, an attribute reading strategy attrMode, and an attribute name list attrNameList. These are used to perform differentiated collection control on different child object types to achieve fine-grained parameter extraction for "the same parent object but different child object types".

[0026] The ReadFile is used to define rules for remote configuration file collection, including at least the file path field; the rule management module parses all ReadFile@path into a set of paths to be collected, which are then used by the subsequent remote file collection module to obtain the target device configuration file item by item according to the path.

[0027] Step 2: According to the database object collection rules, extract the attributes of the target object from the database in real time, and generate a first structured parameter document based on the attributes of the target object. The first structured parameter document organizes the target object and its attribute information in the form of hierarchical nodes. Each hierarchical node includes at least one of node identifier, node name and node type. For example, for a device object in a power control system, the system can extract the basic information of the device object, the information of its sub-objects, and the parameter attributes corresponding to each object, and generate a structured parameter document with a parent-child hierarchical relationship.

[0028] In the above way, object parameters that were originally stored in a scattered manner in the database can be converted into a structured expression suitable for version archiving and hierarchical comparison.

[0029] The structured parameter document is preferably expressed in XML format, with the object's unique identifier id and the business-readable attribute Name supporting subsequent comparison and location.

[0030] Specifically, ReadConfig@id is first parsed as the starting identifier of the target object to locate the corresponding object node from the database; for example, id="47244642609", id="335007449089", id="390842023937" can be configured in the rule file, which correspond to different business object domains.

[0031] For each ReadConfig, the collection module determines the object tree traversal strategy based on childMode: when childMode is full traversal, it recursively collects all child layers; when it is partial traversal, it only traverses the object type branches declared by ChildConfigs; when it is no traversal, it only collects the current object layer.

[0032] During the object attribute extraction phase, attribute reading is performed based on attrMode: a)ReadAll: Reads all available properties of an object; b) ReadNone: Does not read the properties of the current layer, only retains the object structure; c)ReadPartial: Reads only the properties declared in attrNameList.

[0033] For ChildConfigs under ReadConfig, the child object type is matched by otype, and the attrMode / attrNameList in the applied child rule is overridden for the matched node; unmatched types can be executed according to the default strategy of the parent rule. This enables differentiated collection of different types of nodes within the same object tree.

[0034] During the attribute filtering phase, the collection module jointly applies the global strategy in the root node ReadConfigs: it prioritizes retaining the key attributes specified by globalAttrReadList and filters the non-key or easily disturbed attributes specified by globalAttrNotReadList (such as sort number and maintenance status fields), thereby improving cross-version comparability and difference stability.

[0035] After data collection is complete, the module writes the object hierarchy, object identification attributes (including at least id), business display attributes (including at least Name), and business attributes allowed by the rules into the first structured parameter document; the root node of the document can be identified as a database parameter domain node (such as DB), and its child nodes maintain consistency with the database object topology.

[0036] Step 3: According to the configuration file collection rules, collect configuration files from the version management host in real time via remote connection, and summarize one or more configuration files collected in this time to form the first configuration file set; The remote connection method can be implemented using network connection, remote access interface or device communication interface according to the actual application environment, as long as it can read the configuration file in the target device. SSH login to the target device is preferred.

[0037] Configuration file sets may include text configuration files, structured description files, operating parameter files, or other files used to describe the configuration status of the power control system.

[0038] Through the above processing, the system can simultaneously obtain database object parameters and configuration files within the same acquisition cycle, providing a complete data foundation for subsequent snapshot construction.

[0039] Step 4: Build the first version snapshot based on the first structured parameter document and the first configuration file set. A unique version identifier can be assigned to the first version snapshot, and the first structured parameter document and the first configuration file set can be uniformly stored and managed according to the version identifier. In this way, when it is necessary to view historical versions or perform version comparisons later, the system can directly locate the structured parameter document and configuration file set under the corresponding version snapshot based on the version identifier.

[0040] It should be noted that this invention does not require a one-to-one correspondence between structured parameter documents and configuration files. The focus of this invention is to manage them as components of the same version snapshot in a unified manner, thereby ensuring that the parameter state and file state at the same moment are preserved as a whole.

[0041] It should be noted that any version snapshot can be used as an independent configuration archive unit for subsequent version comparison and historical tracing.

[0042] Step 5: Group and align the structured parameter documents in the first version snapshot and the pre-built historical version snapshot according to the node feature key, generating object-level difference results and attribute-level difference results, including: Extract the node feature keys of each level node in the first structured parameter document and the historical structured parameter documents, perform peer matching based on the node feature keys within the same parent node range, and generate object-level difference results; For nodes that fail to match, the node is determined to be either newly added or deleted. For nodes that match successfully, the attribute items are compared one by one to determine at least one type of difference, namely, attribute addition, attribute deletion, and attribute value change, and attribute-level difference results are generated. The node feature key includes at least one of a unique identifier, a business code, and a preset combination feature attribute.

[0043] Step Six: Perform a file-level comparison of the configuration file sets in the first version snapshot and the pre-built historical version snapshots to generate file-level difference results, including: The configuration file sets in the first version snapshot and the historical version snapshot are compared in terms of file existence status and file content to detect at least one type of difference among file addition, file deletion and file content change, and file-level difference results are generated based on the detection results.

[0044] Specifically, for configuration file sets, the system performs file-level comparisons across the configuration file sets corresponding to the two versions. Preferably, the existence status of files is compared first to identify file additions and deletions; for files with the same name that exist in both versions, it is then determined whether the file content has changed.

[0045] In one implementation, it can be determined whether a file with the same name has changed by summarizing the file content or by direct content comparison. For example, content feature values ​​can be calculated for files with the same name for quick screening, or text content comparison can be performed on the changed files to obtain the specific location and content of the change. Based on the comparison results, the system generates file-level difference results.

[0046] Regarding historical version snapshots, the same rule file can be read again, or other pre-defined rule files can be read. Then, database object parameters are collected according to the corresponding rules to generate a historical structured parameter document; configuration files are also collected to generate a historical configuration file set, and finally, historical version snapshots are constructed. Similarly, a unique version identifier can be assigned to each historical version snapshot.

[0047] Step 7: Summarize the object-level difference results, attribute-level difference results, and file-level difference results, and output a unified difference result corresponding to the first version snapshot and historical version snapshots for version management and traceability.

[0048] The unified difference result includes at least one of the following: version identifier, object identifier, difference type, difference location, and difference content, used to characterize the parameter differences and configuration file differences between different version snapshots.

[0049] In practical applications, the unified difference results can be used for: Determine if the system configuration has changed; To query the changes made to a specific version compared to previous versions; Record and audit configuration changes; It provides a basis for operation and maintenance troubleshooting, system debugging, and version rollback.

[0050] The rule-driven power control system configuration parameter version management method provided in this embodiment also includes: After outputting the unified difference results, the first version snapshot built in real time is stored as a historical version snapshot. Example 2

[0051] Embodiment 2 of the present invention provides a rule-driven power control system configuration parameter version management device, such as... Figure 2 As shown, it includes: The rule management module is used to read and parse predefined rule files to obtain database object collection rules and configuration file collection rules; The database parameter acquisition module is used to extract the attributes of the target object from the database in real time according to the database object acquisition rules, and generate a first structured parameter document; The remote file acquisition module is used to acquire configuration files from the version management host in real time via a remote connection according to the configuration file acquisition rules, and generate the first configuration file set. The snapshot building module is used to build a first version snapshot based on the first structured parameter document and the first configuration file set; The difference analysis module includes a structured parameter document difference analysis module and a configuration file set difference analysis module; Among them, the structured parameter document difference analysis module is used to group and align the structured parameter documents in the first version snapshot and the pre-built historical version snapshot according to the node feature key, and generate object-level difference results and attribute-level difference results; The configuration file set difference analysis module is used to perform file-level comparison of the configuration file sets in the first version snapshot and the pre-built historical version snapshot, and generate file-level difference results. The results output module is used to summarize the object-level difference results, attribute-level difference results, and file-level difference results, and output a unified difference result corresponding to the first version snapshot and the historical version snapshot.

[0052] It also includes a display module for showing the unified difference results, which displays the structured parameter difference results and the configuration file difference results respectively.

[0053] The rule-driven power control system configuration parameter version management device provided in Embodiment 2 of the present invention can execute the rule-driven power control system configuration parameter version management method provided in Embodiment 1 of the present invention, and has the corresponding functional modules and beneficial effects of the execution method. Example 3:

[0054] Embodiment 3 of the present invention also provides an electronic device, including a processor and a memory, wherein the memory stores a program that runs on the processor, and the program, when executed, implements the method described in any of the above embodiments.

[0055] The electronic device provided in Embodiment 3 of the present invention can execute the rule-driven power control system configuration parameter version management method provided in Embodiment 1 of the present invention, and has the corresponding functional modules and beneficial effects of the execution method.

[0056] Those skilled in the art will understand that embodiments of this application can be provided as methods, apparatus, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0057] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (devices), and computer program products according to embodiments of this application. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0058] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0059] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0060] The above description is only a preferred embodiment of the present invention. It should be noted that for those skilled in the art, several improvements and modifications can be made without departing from the technical principles of the present invention, and these improvements and modifications should also be considered within the scope of protection of the present invention.

Claims

1. A rule-driven method for version management of configuration parameters in a power control system, characterized in that, Applied to a power control system, the power control system includes a database and a version management host signal-connected to the database, including: Read and parse the predefined rule file to obtain the database object collection rules and configuration file collection rules; According to the database object acquisition rules, the attributes of the target object are extracted from the database in real time to generate a first structured parameter document; According to the configuration file collection rules, configuration files are collected from the version management host in real time to generate the first configuration file set; A first version snapshot is built based on the first structured parameter document and the first configuration file set; The structured parameter documents in the first version snapshot and the pre-built historical version snapshot are grouped and aligned according to the node feature key to generate object-level difference results and attribute-level difference results; The configuration file sets in the first version snapshot and the pre-built historical version snapshot are compared at the file level to generate file-level difference results. The object-level difference results, attribute-level difference results, and file-level difference results are summarized, and a unified difference result corresponding to the first version snapshot and the historical version snapshot is output.

2. The rule-driven power control system configuration parameter version management method according to claim 1, characterized in that, The database object collection rules include: The objects to be collected are determined according to the preset object collection range. The hierarchical structure of the objects to be collected is traversed according to the preset hierarchical traversal strategy to determine the target objects. The target objects are filtered according to the preset attribute extraction and filtering strategy to extract the attribute information of the target objects. The structured parameter document organizes the target object and its attribute information in the form of hierarchical nodes. Each hierarchical node includes at least one of the following: node identifier, node name, and node type.

3. The rule-driven power control system configuration parameter version management method according to claim 1, characterized in that, The configuration file collection rules include at least one of the following: deployment host identifier, file directory, file name pattern, file type, and access method.

4. The rule-driven power control system configuration parameter version management method according to claim 1, characterized in that, The step of grouping and aligning by node feature keys to generate object-level and attribute-level difference results includes: Extract the node feature keys of each level node in the first structured parameter document and the historical structured parameter documents, perform peer matching based on the node feature keys within the same parent node range, and generate object-level difference results; For nodes that match successfully, perform an item-by-item comparison of attribute items to determine at least one type of difference among attribute addition, attribute deletion, and attribute value change, and generate attribute-level difference results. The node feature key includes at least one of a unique identifier, a business code, and a preset combination feature attribute.

5. The rule-driven power control system configuration parameter version management method according to claim 1, characterized in that, The configuration file sets in the first version snapshot and the pre-built historical version snapshot are compared at the file level to generate file-level difference results, including... The configuration file sets in the first version snapshot and the historical version snapshot are compared in terms of file existence status and file content to detect at least one type of difference among file addition, file deletion and file content change, and file-level difference results are generated based on the detection results.

6. The rule-driven power control system configuration parameter version management method according to claim 1, characterized in that, The unified difference result includes at least one of the following: version identifier, object identifier, difference type, difference location, and difference content, used to characterize the parameter differences and configuration file differences between different version snapshots.

7. The rule-driven power control system configuration parameter version management method according to claim 1, characterized in that, Also includes: After outputting the unified difference results, the first version snapshot built in real time is stored as a historical version snapshot.

8. A rule-driven power control system configuration parameter version management device, characterized in that, include: The rule management module is used to read and parse predefined rule files to obtain database object collection rules and configuration file collection rules; The database parameter acquisition module is used to extract the attributes of the target object from the database in real time according to the database object acquisition rules, and generate a first structured parameter document; The remote file acquisition module is used to acquire configuration files from the version management host in real time according to the configuration file acquisition rules, and generate the first configuration file set; The snapshot building module is used to build a first version snapshot based on the first structured parameter document and the first configuration file set; The structured parameter document difference analysis module is used to group and align the structured parameter documents in the first version snapshot and the pre-built historical version snapshot according to the node feature key, and generate object-level difference results and attribute-level difference results. The configuration file set difference analysis module is used to perform file-level comparison of the configuration file sets in the first version snapshot and the pre-built historical version snapshot, and generate file-level difference results. The results output module is used to summarize the object-level difference results, attribute-level difference results, and file-level difference results, and output a unified difference result corresponding to the first version snapshot and the historical version snapshot.

9. The rule-driven power control system configuration parameter version management device according to claim 8, characterized in that, Also includes: The display module is used to show the unified difference results, specifically the structured parameter difference results and the configuration file difference results.

10. An electronic device comprising a processor and a memory, the memory storing a program running on the processor, the program, when executed, implementing the method of any one of claims 1 to 7.

Images