Method and system for online management and control of version of system configuration description file of smart substation

Abstract

The application provides a kind of intelligent substation system configuration description file version online management method and system, obtain the version list stored locally, receive the request of target file version number;The obtained system configuration description file is parsed, and the data in intelligent electronic device attribute model structure is shown;Response to the editing request of system configuration description file in the process of intelligent substation joint debugging, store the new file version modified and mark, update modification index table;With cloud data synchronization, send the latest version of file and modification index table summary information;Receive the latest version number formed by the summary of the target file modification feedback from the cloud, update the local version to the latest version.The application can greatly reduce the management cost and time waste in the process of intelligent substation joint debugging, improve the reliability of system configuration description file version, so as to ensure the safe operation of intelligent substation.

Description

Technical Field

[0001] This invention belongs to the field of document version control technology, and relates to an online management method and system for configuration description document versions in intelligent substation systems. Background Technology

[0002] The statements in this section are merely background information related to the present invention and do not necessarily constitute prior art.

[0003] Compared to conventional substations, smart substations represent a significant technological revolution. Conventional substations connect various relay protection devices via cables to achieve signal transmission and functional implementation. Smart substations employ advanced, reliable, integrated, low-carbon, and environmentally friendly intelligent equipment, with full-station information digitization, networked communication platforms, and standardized information sharing as basic requirements, thereby improving the reliability and economy of the entire power grid. Simultaneously, smart substations incorporate the IEC 61850 standard to standardize engineering operations. The hard-wired interoperability relationships established by cables in conventional substations are replaced by digital configurations of interoperability relationships carried by system configuration description files (System Configuration Descriptions). These system configuration description files are typically created by the equipment supplier and then distributed to other sharing units. During the on-site commissioning of smart substations, all equipment suppliers participate in the configuration of system configuration description files and modify them. Currently, the modified files are shared using methods such as USB flash drive copying and file transfer. However, multiple modifications can easily lead to version confusion. If an incorrect version is used for joint commissioning, it will result in a significant waste of time and impact the overall project schedule.

[0004] The inventors discovered that in the above scenarios, the collaborative configuration of system configuration description files is quite difficult, especially in the early stages of commissioning of smart substations when modifications are frequent. This directly affects the construction cycle of smart substations and potential safety hazards. Summary of the Invention

[0005] To address the aforementioned problems, this invention proposes an online management method and system for the version control of configuration description files in intelligent substations. This invention can significantly reduce management costs and time waste during the commissioning of intelligent substations, improve the reliability of system configuration description file versions, and thus ensure the safe operation of intelligent substations.

[0006] According to some embodiments, the present invention adopts the following technical solution:

[0007] A method for online management and control of configuration description file versions in an intelligent substation system includes the following steps:

[0008] Retrieve the list of versions stored locally and receive a request for the version number of the target file;

[0009] The acquired system configuration description file is parsed to display the data in the attribute model structure of the intelligent electronic device;

[0010] In response to editing requests for system configuration description files during the commissioning of smart substations, the system stores and identifies the new version of the modified file and updates the modification index table.

[0011] Synchronize data with the cloud, send the latest version of files and summary information of modified index tables;

[0012] Receive the latest version number generated from the summary of modifications to the target file from the cloud feedback, and update the local version to the latest version.

[0013] As an optional implementation, the specific process of parsing the acquired system configuration description file includes parsing out the device attributes and interoperability relationships in the device model, storing them in the set model structure, and configuring the names and explanatory attributes of all smart electronic devices.

[0014] As an alternative implementation, the specific process of displaying the data in the attribute model structure of the intelligent electronic device includes displaying the data of the device model as a device list, and for a specific device in the device list, matching the interoperability relationship of that device in the interoperability relationship model structure by the name attribute, and then displaying it.

[0015] As an alternative implementation, the edit request includes the following categories: changing the attribute information of the device model, changing the interoperability relationship of the device model, and upgrading the device model version.

[0016] As an alternative implementation, the specific process of storing and identifying the modified new file version includes responding to the editing request, modifying the information according to the project requirements, storing the modified version after the modification is completed, generating a new file version, generating a unique identifier that records the version number, and storing the device model involved in this modification in the modification index table corresponding to the version.

[0017] As an alternative implementation, when synchronizing data with the cloud, the union of the modification index tables of all versions between the last update and the latest version is taken to obtain a local summary modification index table between the two versions, and the latest version file and the summary modification index table are pushed to the cloud.

[0018] As an alternative implementation, the cloud receives the latest version files and a summary modification index table sent by all clients, takes the union of the modification index tables corresponding to the version sequence to obtain the cloud summary modification index table, compares it with the locally pushed summary modification index table, merges all the latest versions, generates the latest version, and generates a modification index table corresponding to the latest version.

[0019] As a further defined implementation method, the principles of version merging include:

[0020] If the device model is recorded in the local summary modification index table but not in the cloud summary modification index table, the local modification content will be used directly and stored in the modification index table.

[0021] b. If the device model record is in the local summary modification index table and the record is in the cloud summary modification index table, then a prompt will be made, and the selection result of the modified content will be received and stored in the modification index table;

[0022] c. If the device model is not recorded in the local summary modification index table, but is recorded in the cloud summary modification index table, then it does not need to be stored in the modification index table.

[0023] If the device model is not recorded in the local summary modification index table, nor in the cloud summary modification index table, then the cloud modification content will be used directly.

[0024] As an alternative implementation method, after the merge is completed, the cloud will push the latest version number to each client, allowing each client to update its local version to the latest version and complete the entire synchronization process.

[0025] An online management and control system for the version of configuration description files of an intelligent substation system includes:

[0026] The client, with a local storage service unit, is configured to execute:

[0027] Get the local version list and receive a request for the version number of the target file;

[0028] The acquired system configuration description file is parsed to display the data in the attribute model structure of the intelligent electronic device;

[0029] In response to editing requests for system configuration description files during the commissioning of smart substations, the system stores and identifies the new version of the modified file and updates the modification index table.

[0030] Synchronize data with the cloud, send the latest version of files and summary information of modified index tables;

[0031] Receive the latest version number generated from the summary of modifications to the target file from the cloud, and update the local version to the latest version;

[0032] The cloud storage service unit is configured to aggregate the latest version files sent by each client, aggregate the modification index table, take the union of the modification index tables corresponding to the version sequence to obtain the cloud aggregated modification index table, compare it with the locally aggregated modification index table pushed in, merge all the latest versions, generate the latest version, and generate the modification index table corresponding to the latest version.

[0033] Compared with the prior art, the beneficial effects of the present invention are as follows:

[0034] This invention can significantly reduce management costs and time waste during the commissioning of smart substations, improve the reliability of system configuration description file versions, and thus ensure the safe operation of smart substations.

[0035] This invention takes into account the network conditions at smart substation work sites. In this technical solution, local storage services and cloud storage services do not need to be connected in real time; periodic data synchronization is sufficient to ensure that on-site commissioning is not limited by network conditions. At the smart substation commissioning site, different equipment suppliers can simultaneously edit and modify system configuration description files using configuration tool clients, and periodically synchronize data through cloud storage services, ensuring version correctness while reducing communication overhead. Attached Figure Description

[0036] The accompanying drawings, which form part of this invention, are used to provide a further understanding of the invention. The illustrative embodiments of the invention and their descriptions are used to explain the invention and do not constitute an improper limitation of the invention.

[0037] Figure 1 This is a diagram of the system configuration description file;

[0038] Figure 2 This is a schematic diagram of the system in this embodiment;

[0039] Figure 3 This is a schematic diagram of the version update in this embodiment;

[0040] Figure 4 This is a schematic diagram of data synchronization in this embodiment;

[0041] Figure 5 This is a schematic diagram of cloud data merging in this embodiment. Detailed Implementation

[0042] The present invention will be further described below with reference to the accompanying drawings and embodiments.

[0043] It should be noted that the following detailed description is illustrative and intended to provide further explanation of the invention. Unless otherwise specified, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this invention pertains.

[0044] It should be noted that the terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit the scope of exemplary embodiments according to the invention. As used herein, the singular form is intended to include the plural form as well, unless the context clearly indicates otherwise. Furthermore, it should be understood that when the terms "comprising" and / or "including" are used in this specification, they indicate the presence of features, steps, operations, devices, components, and / or combinations thereof.

[0045] Example 1

[0046] A system for managing the version of configuration description files for intelligent substations that enables collaborative configuration within the substation can significantly reduce management costs and time wastage during the commissioning of intelligent substations, improve the reliability of system configuration description file versions, and thus ensure the safe operation of intelligent substations.

[0047] like Figure 1 As shown, the system configuration description file consists of the device model files of all relay protection devices in the smart substation.

[0048] like Figure 2 As shown, this system consists of a configuration tool client (hereinafter referred to as the client), a local storage service unit or local storage server (hereinafter referred to as the local storage service), and a cloud service unit or server (hereinafter referred to as the cloud storage service).

[0049] The configuration tool client is responsible for editing and modifying the system configuration description file; the local storage service is responsible for storing and managing the modified versions submitted by the configuration tool, and also for synchronizing data with the cloud storage service; while the cloud storage service is responsible for storing a globally unique version shared library.

[0050] The configuration tool client and local storage service are deployed simultaneously on the local work terminal, while the cloud storage service is deployed on the internet. Considering the network conditions at the smart substation work site, the local storage service and cloud storage service do not need to be connected in real time in this technical solution; periodic data synchronization is sufficient to ensure that on-site commissioning is not limited by network conditions. At the smart substation commissioning site, different equipment suppliers can simultaneously edit and modify system configuration description files using the configuration tool client, and periodically synchronize data through the cloud storage service.

[0051] The detailed steps for configuring the client are as follows:

[0052] I. Model Analysis:

[0053] I. The configuration tool client first retrieves the version list from the local storage service, selects the version number to be edited, usually the latest version number, but you can also go back and select a historical version.

[0054] II. The configuration tool client parses the obtained system configuration description file, extracts the device attributes and interoperability relationships in the device model, and stores them in the following model structure.

[0055] Object name: ied (device property) Attribute 1: name Attribute 2: desc

[0056] Object name: relation (interoperability relationship) Attribute 1: intIed (associated with the ied model) Attribute 2: intAddr Attribute 3: iedName Attribute 4: ldInst Attribute 5: lnClass Attribute 6: lnInst Attribute 7: prefix Attribute 8: doName Attribute 9: daName

[0057] The name and desc attributes of all IED nodes in the system configuration description file are parsed and stored in the ied device attribute model structure.

[0058] The parsing of the iedName, ldInst, lnClass, lnInst, prefix, doName, daName, and intAddr of all ExtRef nodes under the IED / AccessPoint / Server / Ldevice / LN0 / Inputs path in the system configuration description file represents all the interoperability relationships received by this relay protection device from the outside, which are then associated with the corresponding devices and stored in the relation interoperability relationship model structure.

[0059] II. Model Display

[0060] III. Retrieve all data from the ied device attribute model structure and display it as a device list, as shown in the table below:

[0061] name desc PL2201A City East Line A Protection Set IL2201A Chengdong Jiaxian Smart Terminal Set A ML2201A Unit A, merged unit of Chengdong Jia Line PM2201A 22022Ⅰ-Ⅱ Mother Protection Set A … …

[0062] I2. For a specific device in the device list, by matching the `name` attribute with the `intIed` attribute in the `relation` interoperability table, the interoperability relationships of that device in the `relation` interoperability model structure can be obtained and displayed. The table below shows all the received interoperability relationships of PL2201A (Chengdong Jia Line Protection Set A).

[0063]

[0064]

[0065] III. Model Modification:

[0066] V. The configuration tool client displays the parsed relay protection devices and interoperability relationships to the user and supports user modification. During the commissioning of smart substations, the editing of system configuration description files mainly falls into three categories: changing the attribute information of device models, changing the interoperability relationships of device models, and upgrading device model versions.

[0067] in:

[0068] Changing equipment model attribute information includes: adding, modifying, and deleting equipment model attributes;

[0069] Changing equipment model interoperability relationships includes: adding, modifying, and deleting interoperability relationships;

[0070] Equipment model version upgrade: Due to the version upgrade, the entire equipment model structure is updated.

[0071] VI. Modify the information according to project requirements. After modification, execute the save operation. The local storage service will generate a new file version and a unique identifier ID to record the version number. At the same time, the local storage service will store the device models involved in this modification in the modification index table corresponding to this version.

[0072] The local storage service initiates the data synchronization process with the cloud storage service:

[0073] 1) When the configuration tool client performs a synchronization operation, the local storage service will check the network status to ensure that the data synchronization is performed under normal connection with the cloud storage service.

[0074] 2) such as Figure 5 As shown, assuming the latest version of the local storage service after the last synchronization update with the cloud storage service is 3eb8 (hereinafter referred to as the last update version), the new version number saved by the local storage service after this modification is 1251 (hereinafter referred to as the latest version).

[0075] 3) After performing the synchronization operation, the local storage service will take the union of the modification index tables of all versions between the last update and the latest version to obtain a local summary modification index table between the two versions. The local storage service will then push the latest version file and the summary modification index table to the cloud storage service.

[0076] 4) After receiving the push message, the cloud storage service searches for all version sequences after version 3eb8, takes the union of the modification index tables corresponding to the version sequences, and obtains the cloud-based aggregated modification index table. This is then compared with the locally aggregated modification index table pushed to it.

[0077] 5) Based on the comparison results, merge version 1251 pushed from the local storage service and the latest d006 version from the cloud storage service. The merged version will generate a new version number, 29a5, and a corresponding modification index table will be created. The merging principles are as follows:

[0078] a. If the device model is recorded in the local summary modification index table, but not in the cloud summary modification index table.

[0079] This indicates that the device model was modified on the local client, but not on other clients. The modified content was directly adopted from the local client and stored in the modification index table.

[0080] b. If the device model record is recorded in the local summary modification index table, it is also recorded in the cloud summary modification index table.

[0081] If the device model has been modified by multiple people, a prompt should be provided, allowing the user to decide whether to adopt the modified content, and the modification index table should be saved.

[0082] c. If the device model is not recorded in the local summary modification index table, but is recorded in the cloud summary modification index table.

[0083] This indicates that the device model has been modified by others, using modifications from the cloud (modifications made in the cloud do not need to be stored in the modification index table).

[0084] d. If the device model is not recorded in the local summary modification index table, nor in the cloud summary modification index table.

[0085] This indicates that the device model was not modified; the modifications were made directly from the cloud.

[0086] 6) After the merge is complete, the cloud storage service will push the latest version number to the local storage service, update the local version to the latest version, and complete the entire synchronization process.

[0087] Example 2

[0088] Provide a method for execution by the aforementioned system.

[0089] Those skilled in the art will understand that embodiments of the present invention can be provided as methods, systems, or computer program products. Therefore, the present invention can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present invention 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.

[0090] This invention is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. 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 flowchart illustrations and / or block diagrams. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0091] 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.

[0092] 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.

[0093] The above description is merely a preferred embodiment of the present invention and is not intended to limit the invention. Various modifications and variations can be made to the present invention by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present invention should be included within the scope of protection of the present invention.

[0094] While the specific embodiments of the present invention have been described above in conjunction with the accompanying drawings, this is not intended to limit the scope of protection of the present invention. Those skilled in the art should understand that various modifications or variations that can be made by those skilled in the art without creative effort based on the technical solutions of the present invention are still within the scope of protection of the present invention.

Claims

1. An online management method for version of system configuration description file of smart substation, characterized in that, The method comprises the following steps: Obtain the local stored version list, receive the request of target file version number; Parse the obtained system configuration description file, show the data in the intelligent electronic device attribute model structure; In response to the editing request of the system configuration description file in the intelligent substation joint debugging process, store the modified new file version and mark, and update the modification index table; Synchronize data with the cloud, send the latest version of the file and the summary information of the modification index table; The cloud receives the latest version of the file and the summary modification index table sent by all clients, takes the union of the modification index table corresponding to the version sequence, obtains the cloud summary modification index table, and compares with the local summary modification index table pushed from the cloud, merges all the latest versions, generates the latest version after merging, and generates the modification index table corresponding to the latest version; The principles of version merging include: a If the device model is recorded in the local summary modification index table but not in the cloud summary modification index table, directly adopt the local modification content and store it in the modification index table; b If the device model is recorded in the local summary modification index table and the cloud summary modification index table, prompt and receive the selection result of the modification content, and store it in the modification index table; c If the device model is not recorded in the local summary modification index table but is recorded in the cloud summary modification index table, it is not necessary to store it in the modification index table; d If the device model is not recorded in the local summary modification index table and the cloud summary modification index table, directly adopt the cloud modification content; Receive the latest version number formed by the cloud feedback to the summary of the target file modification, and update the local version to the latest version.

2. The method for online management and control of configuration description file versions in an intelligent substation system as described in claim 1, characterized in that, The specific process of parsing the obtained system configuration description file includes parsing the device attributes and interoperation relationship in the device model, and storing them in the set model structure, and configuring the names and interpretation attributes of all intelligent electronic devices.

3. The method for online management and control of configuration description file versions in an intelligent substation system as described in claim 1, characterized in that, The specific process of showing the data in the intelligent electronic device attribute model structure includes showing the data of the device model as a device list, matching the interoperation relationship of the device in the interoperation relationship model structure through the name attribute for the specific device in the device list, and showing it.

4. The method for online management and control of configuration description file versions in an intelligent substation system as described in claim 1, characterized in that, The editing request includes the following categories: changing the attribute information of the device model, changing the interoperation relationship of the device model, and upgrading the device model version.

5. The method for online management and control of configuration description file versions of an intelligent substation system as described in claim 1, characterized in that, The specific process of storing the modified new file version and marking includes responding to the editing request, modifying the information according to the engineering needs, storing after the modification is completed, generating a new file version, generating a unique identifier recording the version number, and storing the device model involved in this modification into the modification index table corresponding to the version.

6. The method for online management and control of configuration description file versions in an intelligent substation system as described in claim 1, characterized in that, When synchronizing data with the cloud, take the union of the modification index table of all versions between the last updated version and the latest version, obtain the local summary modification index table between the two versions, push the latest version of the file and the summary modification index table to the cloud.

7. The method for online management and control of configuration description file versions of an intelligent substation system as described in claim 1, characterized in that, After merging is completed, the cloud pushes the latest version number to each client for updating the local version to the latest version, and completes the whole synchronization process.

8. An online management system for smart substation system configuration description file version, characterized in that, It comprises: The client has a local storage service unit, which is configured to perform: Obtain a local version list and receive a request for a target file version number; Parse the obtained system configuration description file to display data in the intelligent electronic device attribute model structure; In response to an editing request for the system configuration description file during the intelligent substation joint debugging process, store the modified new file version and identification, and update the modification index table; Synchronize data with the cloud, send the latest version of the file and the summary information of the modification index table; The cloud receives the latest version of the file and the summary modification index table sent by all clients, takes the union of the modification index table corresponding to the version sequence, obtains the cloud summary modification index table, and compares it with the local summary modification index table pushed, merges all the latest versions, generates the latest version after merging, and generates the modification index table corresponding to the latest version; The principles of version merging include: a If the device model is recorded in the local summary modification index table but not in the cloud summary modification index table, directly use the local modification content and store it in the modification index table; b If the device model is recorded in the local summary modification index table and the cloud summary modification index table, prompt and receive the selection result of the modification content, and store it in the modification index table; c If the device model is not recorded in the local summary modification index table but is recorded in the cloud summary modification index table, it is not necessary to store it in the modification index table; d If the device model is not recorded in the local summary modification index table and is not recorded in the cloud summary modification index table, directly use the cloud modification content; Receive the latest version number formed by the cloud feedback for the summary of the target file modification, and update the local version to the latest version; The cloud storage service unit is configured to summarize the latest version of the file and the summary modification index table sent by each client, take the union of the modification index table corresponding to the version sequence, obtain the cloud summary modification index table, and compare it with the local summary modification index table pushed, merge all the latest versions, generate the latest version after merging, and generate the modification index table corresponding to the latest version.

Images