A mobile SCD configuration management method

Abstract

The application discloses a mobile SCD configuration management and control method, which comprises the following steps: a configuration management and control step of a relay protection device: importing an SCD file, adding mms service IP and ftp service IP, verifying consistency between a connection management and control object and a selected configuration management and control object, downloading a configuration file and reading back to confirm consistency, and comparing 61850 models; and a configuration management and control step of an intelligent terminal or a merging unit device. The application realizes management and control of a configuration file downloading process, realizes a unified standardized process, and guarantees correctness of the configuration file downloading.

Description

Technical Field

[0001] This invention relates to the field of secondary operation and maintenance technology for intelligent substations, specifically to a mobile SCD configuration and control method. Background Technology

[0002] The safe operation of smart substations is inseparable from relay protection devices. In daily maintenance, users only care about whether the relay protection's operating status meets requirements, and the configuration and download process largely relies on manufacturer oversight. If the manufacturer makes a configuration error or the configuration fails, users can only discover it through other means of acceptance, increasing manpower and material costs. Furthermore, the backup configuration files provided by the manufacturer cannot guarantee consistency with the SCD file received by the customer, nor can they guarantee consistency with the actual downloaded configuration file, making it impossible for the customer to monitor the entire process. Moreover, different manufacturers' protection systems require different manufacturers' tools to complete the download process; a single program cannot complete the download of all protection systems in the entire substation. Additionally, the tools from various manufacturers do not provide a verification step for configuration and download, making it difficult for the manufacturer's software to detect errors. Therefore, a standardized download process for relay protection devices is needed. This process should meet configuration and download requirements, ensure that users are not dependent on the manufacturer, complete the entire substation configuration and download process through a single procedure, and allow for full monitoring of the download process to ensure that the final backup configuration file is consistent with the actual downloaded configuration file. Summary of the Invention

[0003] The purpose of this invention is to address the aforementioned problems in the existing technology by providing a mobile SCD configuration management method that can be universally applied to download services from all manufacturers while ensuring the correctness of the download.

[0004] The above-mentioned objectives of the present invention are achieved through the following technical means:

[0005] A mobile SCD configuration management method includes the following steps:

[0006] Step 1: Import the SCD file into the mobile control unit, select the control object as the relay protection device, and add the MMS service IP and FTP service IP.

[0007] Step 2: The mobile management unit connects to the MMS network port and FTP network port of the managed object via a network cable, and verifies the consistency between the current managed object and the selected and configured managed object through ping and FTP services.

[0008] Step 3: The mobile management unit reads the configuration file in the root directory of the managed object through the FTP service, backs up the configuration file, and then downloads the configuration file that needs to be downloaded to the current managed object through the FTP service.

[0009] Step 4: The mobile management unit reads back the downloaded configuration file via FTP service and uses a text comparison method to confirm the consistency between the read-back configuration file and the downloaded configuration file.

[0010] Step 5: Restart the managed object. The mobile management unit reads the 61850 model of the managed object through the MMS service and compares it with the corresponding 61850 model of the managed object in the SCD file. If they match, the configuration and download task is completed; if they do not match, the user is prompted that the configuration and download task has failed.

[0011] A mobile SCD configuration management method further includes the following steps:

[0012] Step 6: The mobile management unit imports the SCD file, selects the smart terminal or merging unit device as the managed object, parses the SCD file to obtain the APPID of the SV / GOOSE messages sent by the managed object in the SCD process layer network, and adds IPs in the same network segment that support FTP service to the mobile management unit.

[0013] Step 7: The mobile management unit connects to the FTP port of the managed object via a network cable, and connects to the SV / GOOSE message sending interface of the managed object via a fiber optic cable. It compares the APPID of the received SV / GOOSE message sent by the managed object with the APPID of the SV / GOOSE message parsed in Step 6. It then verifies the consistency between the managed object and the selected configured managed object through the FTP service.

[0014] Step 8: The mobile management unit reads the configuration file in the root directory of the managed object via FTP service, backs up the configuration file, and then downloads the required configuration file to the current managed object via FTP service.

[0015] Step 9: The mobile management unit reads back the downloaded configuration file via FTP service and uses a text comparison method to confirm the consistency between the read-back configuration file and the downloaded configuration file.

[0016] Step 10: Restart the managed object. The mobile management unit compares the SV / GOOSE message model of the managed object obtained through the SV / GOOSE message receiving service with the SV / GOOSE message model obtained by parsing the SCD file.

[0017] As described above, step 2 includes the following steps:

[0018] Step 2.1: The mobile management unit verifies the consistency between the currently connected management object and the selected management object by checking whether it can connect to the selected management object's MMS service IP via the ping service.

[0019] Step 2.2: The mobile management unit verifies the consistency between the current connected management object and the selected and configured management object by checking whether it can log in to the current connected management object through the FTP service.

[0020] As described above, step 5, comparing the 61850 model of the controlled object obtained through the MMS service protocol with the 61850 model obtained by parsing the SCD file, includes the following steps:

[0021] Step 5.1: Compare whether the number of datasets in the two 61850 models above is consistent. If they are inconsistent, prompt the user that the configuration download task failed and revert to the current managed object through the backup configuration file in step 3 or re-download the configuration file to the managed object. If they are consistent, proceed to step 5.2.

[0022] Step 5.2: Compare whether the dataset names in the two 61850 models are completely consistent. If they are inconsistent, prompt the user that the configuration download task failed and revert to the current managed object using the backup configuration file in Step 3 or re-download the configuration file to the managed object. If they are consistent, proceed to Step 5.3.

[0023] Step 5.3: Compare the number of channels under the same dataset name in the two 61850 models above. If they are not the same, prompt the user that the configuration download task failed. Then, revert to the current managed object using the configuration file backed up in Step 3 or re-download the configuration file to the managed object. If they are the same, proceed to Step 5.4.

[0024] Step 5.4: Compare whether the channel parameters under the same dataset name in the two 61850 models are completely consistent. If they are inconsistent, prompt the user that the configuration download task has failed. Revert to the current managed object using the configuration file backed up in Step 3 or re-download the configuration file to the managed object. If they are consistent, the configuration download task is completed.

[0025] As described above, step 7 includes the following steps:

[0026] Step 7.1: The mobile management unit receives the SV / GOOSE message sent by the managed object, parses the APPID of the received SV / GOOSE message, and confirms whether the APPID of the received SV / GOOSE message is consistent with the APPID of the SV / GOOSE message obtained in Step 6. If they are consistent, proceed to the next step; if they are inconsistent, prompt the user that the current managed object is inconsistent with the selected and configured managed object.

[0027] Step 7.2: The mobile management unit logs into the currently connected managed object via FTP service. If the login is successful, proceed to the next step; if the login fails, prompt the user to confirm the FTP login name and password.

[0028] As described above, step 10, comparing the SV / GOOSE message model of the managed object obtained through the SV / GOOSE message reception service with the SV / GOOSE message model obtained by parsing the SCD file, includes the following steps:

[0029] Step 10.1: Compare the SV / GOOSE header of the managed object obtained by calling through the SV / GOOSE message receiving protocol with the SV / GOOSE header of the managed object obtained by parsing the SCD file. The SV / GOOSE header contains the IP and MAC address. If they do not match, prompt the user that the configuration download task failed. Then, revert to the current managed object using the configuration file backed up in step 8 or re-download the configuration file to the managed object. If they match, proceed to step 10.2.

[0030] Step 10.2: Compare the number of SV / GOOSE data channels of the managed object obtained by calling through the SV / GOOSE message receiving protocol with the number of SV / GOOSE data channels of the managed object obtained by parsing the SCD file. If they are not consistent, prompt the user that the configuration download task failed and revert to the current managed object through the configuration file backed up in step 8 or re-download the configuration file to the managed object. If they are consistent, proceed to step 10.3.

[0031] Step 10.3: Compare the SV / GOOSE channel type of the managed object obtained by calling through the SV / GOOSE message receiving protocol with the SV / GOOSE channel type of the managed object obtained by parsing the SCD file. If they are inconsistent, prompt the user that the configuration download task has failed. Then, revert to the current managed object by backing up the configuration file in step 8 or re-download the configuration file to the managed object. If they are consistent, the configuration download task is completed.

[0032] Compared with the prior art, the present invention has the following advantages:

[0033] 1. It enables control over the configuration file download process, allowing monitoring of all operational steps by the user, and providing traceable evidence for subsequent download errors that could lead to accidents.

[0034] 2. Provides a unified and standardized process. In the past, personnel from different manufacturers used their own proprietary processes, which led to an uncontrollable process. Now, as long as everyone follows the process provided by this method, a unified and standardized process can be achieved.

[0035] 3. Strict process control: In the past, when manufacturers' personnel downloaded configuration files to devices, the complex wiring conditions on site could lead to situations where configuration file A was downloaded to device B, causing the device to malfunction. However, according to this method, there are verification processes before and after the configuration file is downloaded, thus ensuring the correctness of the configuration file download. Detailed Implementation

[0036] To facilitate understanding and implementation of the present invention by those skilled in the art, the present invention will be further described in detail below with reference to embodiments. It should be understood that the embodiments described herein are for illustration and explanation only and are not intended to limit the present invention.

[0037] A mobile SCD configuration and control method, comprising a station control layer device configuration and control method, including the following steps:

[0038] Configuration control of relay protection devices:

[0039] Step 1: Import the SCD file into the mobile control unit, select the control object as the relay protection device, and add the MMS service IP and FTP service IP.

[0040] Step 1.1: Add the MMS service IP to the mobile management unit. Resolve the IP address of the managed object in the SCD station control layer network, and add the managed object's IP address from the same network segment in the SCD station control layer network as the MMS service IP to the mobile management unit.

[0041] Step 1.2: Add an FTP service IP to the mobile management unit. Add an IP address from the same network segment that supports FTP service to the mobile management unit as the FTP service IP.

[0042] Step 2: The mobile control unit connects to the MMS network port and FTP network port of the controlled object via a network cable to verify the consistency between the current controlled object and the selected and configured controlled object.

[0043] Step 2.1: Connect to the configured MMS service IP of the managed object via the ping service to confirm that the currently connected managed object is consistent with the configured MMS service IP. If the connection is successful, proceed to the next step; if the connection fails, lock the current step and prompt the user that the current managed object is inconsistent with the configured managed object.

[0044] Step 2.2: The mobile management unit logs into the currently connected managed object via FTP service. If the login is successful, proceed to the next step; if the login fails, prompt the user to confirm the FTP login name and password.

[0045] Step 3: The mobile management unit reads the configuration file in the root directory of the managed object via FTP service and backs up the configuration file. Then, it downloads the required configuration files to the current managed object via FTP service, such as the corresponding CID / CCD files.

[0046] Among them, the configuration files that the currently managed objects need to download need to be exported from the imported SCD file.

[0047] Step 4: The mobile management unit reads back the downloaded configuration file via FTP service and uses a text comparison method to confirm that the read-back configuration file matches the downloaded configuration file. If they match, proceed to the next step; if they do not match, lock the current step and notify the user that the download operation failed.

[0048] Step 5: Restart the managed object. The mobile management unit reads the 61850 model of the managed object through the MMS service protocol. That is, it summons and obtains various datasets (e.g., dsWarning) and dataset channels (e.g., LD0 / GGIO4.Alm1) of the managed object through the MMS service protocol. It parses the SCD file to obtain the 61850 model corresponding to the managed object. In other words, by parsing the SCD file, it obtains various datasets (e.g., dsWarning) and dataset channels (e.g., LD0 / GGIO4.Alm1) of the managed object in the SCD. It then compares the 61850 model (including datasets and dataset channels) of the managed object obtained through the MMS service protocol with the 61850 model (including datasets and dataset channels) obtained by parsing the SCD file. The specific comparison principles are as follows:

[0049] Step 5.1: Compare the number of datasets in the two 61850 models above. If they are inconsistent, prompt the user that the configuration download task failed. The user can either revert to the current managed object using the backup configuration file from Step 3, or re-download the configuration file to the managed object. If they are consistent, proceed to Step 5.2.

[0050] Step 5.2: Compare whether the dataset names in the two 61850 models are completely identical. If they are not identical, prompt the user that the configuration download task failed. The user can either revert to the current managed object using the backup configuration file from Step 3, or re-download the configuration file to the managed object. If they are identical, proceed to Step 5.3.

[0051] Step 5.3: Compare the number of channels under the same dataset name in the two 61850 models above. If they are inconsistent, prompt the user that the configuration download task failed. The user can either revert to the current managed object using the configuration file backed up in Step 3, or re-download the configuration file to the managed object. If they are consistent, proceed to Step 5.4.

[0052] Step 5.4: Compare whether the channel parameters under the same dataset name in the two 61850 models are completely consistent. If they are inconsistent, prompt the user that the configuration download task has failed. The user can either revert to the current managed object using the configuration file backed up in Step 3, or re-download the configuration file to the managed object. If they are consistent, it means that the datasets and channels in the two 61850 models are completely consistent, and the configuration download task is complete.

[0053] Step 6: The mobile management unit imports the SCD file, selects the smart terminal or merging unit device as the managed object, parses the SCD file, and obtains the APPID of the SV / GOOSE messages sent by the managed object in the SCD process layer network. The mobile management unit adds IP addresses in the same network segment that support the managed object's FTP service.

[0054] Step 7: The mobile management unit connects to the FTP port of the managed object via a network cable, and connects to the SV / GOOSE message sending interface of the managed object via a fiber optic cable to verify that the current managed object is consistent with the selected and configured managed object.

[0055] Step 7.1: The mobile management unit receives the SV / GOOSE message sent by the managed object, parses the APPID of the received SV / GOOSE message, and confirms whether the APPID of the received SV / GOOSE message is consistent with the APPID of the SV / GOOSE message obtained in Step 6. If they are consistent, proceed to the next step; if they are inconsistent, prompt the user that the current managed object is inconsistent with the selected and configured managed object.

[0056] Step 7.2: The mobile management unit logs into the currently connected managed object via FTP service. If the login is successful, proceed to the next step; if the login fails, prompt the user to confirm the FTP login name and password.

[0057] Step 8: The mobile management unit reads the configuration file in the root directory of the managed object via FTP service and backs up the configuration file. Then, it downloads the required configuration file to the current managed object via FTP service.

[0058] Among them, the configuration files that the currently managed objects need to download need to be exported from the imported SCD file.

[0059] Step 9: The mobile management unit reads back the downloaded configuration file via FTP service and uses a text comparison method to confirm that the read-back configuration file matches the downloaded configuration file. If they match, proceed to the next step; if they do not match, lock the current step and prompt the user that the download operation failed.

[0060] Step 10: Restart the managed object. The mobile management unit reads the SV / GOOSE model of the managed object through the SV / GOOSE message receiving protocol, that is, by invoking the SV / GOOSE service protocol to obtain the SV / GOOSE message header, the number of SV / GOOSE channels, and the SV / GOOSE channel type of the managed object. The mobile management unit parses the SCD file to obtain the SV / GOOSE model corresponding to the managed object. That is, by parsing the SCD file, it obtains the SV / GOOSE message header, the number of SV / GOOSE channels, and the SV / GOOSE channel type of the managed object in the SCD file. It then compares the SV / GOOSE model of the managed object obtained through the SV / GOOSE message receiving protocol (including the SV / GOOSE message header, the number of SV / GOOSE channels, and the SV / GOOSE channel type) with the SV / GOOSE model obtained by parsing the SCD file (including the SV / GOOSE message header, the number of SV / GOOSE channels, and the SV / GOOSE channel type). The specific comparison principles are as follows:

[0061] Step 10.1: Compare the SV / GOOSE header of the managed object obtained by calling through the SV / GOOSE message receiving protocol with the SV / GOOSE header of the managed object obtained by parsing the SCD file (the SV / GOOSE header contains IP and MAC addresses). If they are inconsistent, prompt the user that the configuration download task failed and revert to the current managed object using the configuration file backed up in step 8 or re-download the configuration file to the managed object. If they are consistent, proceed to step 10.2.

[0062] Step 10.2: Compare the number of SV / GOOSE data channels of the managed object obtained by calling through the SV / GOOSE message receiving protocol with the number of SV / GOOSE data channels of the managed object obtained by parsing the SCD file. If they are not consistent, prompt the user that the configuration download task failed and revert to the current managed object through the configuration file backed up in step 8 or re-download the configuration file to the managed object. If they are consistent, proceed to step 10.3.

[0063] Step 10.3: Compare the SV / GOOSE channel type of the managed object obtained by calling through the SV / GOOSE message receiving protocol with the SV / GOOSE channel type of the managed object obtained by parsing the SCD file. If they are inconsistent, prompt the user that the configuration download task has failed. Then, revert to the current managed object by backing up the configuration file in step 8 or re-download the configuration file to the managed object. If they are consistent, the configuration download task is completed.

[0064] A mobile SCD configuration management method supports exporting configuration management reports, recording configuration management process results, and indicating whether the configuration management task is completed and the result is qualified; or whether the configuration management task fails and the result is unqualified.

[0065] The specific embodiments described herein are merely illustrative of the spirit of the invention. Those skilled in the art to which this invention pertains may make various modifications or additions to the described specific embodiments or use similar methods to substitute them, without departing from the spirit of the invention or exceeding the scope defined by the appended claims.

Claims

1. A mobile SCD configuration and management method, characterized in that, Includes the following steps: Step 1: Import the SCD file into the mobile control unit, select the control object as the relay protection device, and add the MMS service IP and FTP service IP. Step 2: The mobile management unit connects to the MMS network port and FTP network port of the managed object via a network cable, and verifies the consistency between the current managed object and the selected and configured managed object through ping and FTP services. Step 3: The mobile management unit reads the configuration file in the root directory of the managed object through the FTP service, backs up the configuration file, and then downloads the configuration file that needs to be downloaded to the current managed object through the FTP service. Step 4: The mobile management unit reads back the downloaded configuration file via FTP service and uses a text comparison method to confirm the consistency between the read-back configuration file and the downloaded configuration file. Step 5: Restart the managed object. The mobile management unit reads the 61850 model of the managed object through the MMS service and compares it with the corresponding 61850 model of the managed object in the SCD file. If they match, the configuration download task is completed. If the configuration is inconsistent, the user will be prompted that the download task failed. Step 6: The mobile management unit imports the SCD file, selects the smart terminal or merging unit device as the managed object, parses the SCD file to obtain the APPID of the SV / GOOSE messages sent by the managed object in the SCD process layer network, and adds IPs in the same network segment that support FTP service to the mobile management unit. Step 7: The mobile management unit connects to the FTP port of the managed object via a network cable, and connects to the SV / GOOSE message sending interface of the managed object via a fiber optic cable. It compares the APPID of the received SV / GOOSE message sent by the managed object with the APPID of the SV / GOOSE message parsed in Step 6. It then verifies the consistency between the managed object and the selected configured managed object through the FTP service. Step 8: The mobile management unit reads the configuration file in the root directory of the managed object via FTP service, backs up the configuration file, and then downloads the required configuration file to the current managed object via FTP service. Step 9: The mobile management unit reads back the downloaded configuration file via FTP service and uses a text comparison method to confirm the consistency between the read-back configuration file and the downloaded configuration file. Step 10: Restart the managed object. The mobile management unit compares the SV / GOOSE message model of the managed object obtained through the SV / GOOSE message receiving service with the SV / GOOSE message model obtained by parsing the SCD file. Step 2 includes the following steps: Step 2.1: The mobile management unit verifies the consistency between the currently connected management object and the selected management object by checking whether it can connect to the selected management object's MMS service IP via the ping service. Step 2.2: The mobile management unit verifies the consistency between the currently connected management object and the selected configured management object by checking whether it can log in to the currently connected management object via FTP service. Step 5, comparing the 61850 model of the controlled object obtained through the MMS service protocol with the 61850 model obtained by parsing the SCD file, includes the following steps: Step 5.1: Compare whether the number of datasets in the two 61850 models above is consistent. If they are inconsistent, prompt the user that the configuration download task failed and revert to the current managed object through the backup configuration file in step 3 or re-download the configuration file to the managed object. If they are consistent, proceed to step 5.

2. Step 5.2: Compare whether the dataset names in the two 61850 models are completely consistent. If they are inconsistent, prompt the user that the configuration download task failed and revert to the current managed object using the backup configuration file in Step 3 or re-download the configuration file to the managed object. If they are consistent, proceed to Step 5.

3. Step 5.3: Compare the number of channels under the same dataset name in the two 61850 models above. If they are not the same, prompt the user that the configuration download task failed. Then, revert to the current managed object using the configuration file backed up in Step 3 or re-download the configuration file to the managed object. If they are the same, proceed to Step 5.

4. Step 5.4: Compare whether the channel parameters under the same dataset name in the two 61850 models are completely consistent. If they are inconsistent, prompt the user that the configuration download task has failed. Revert to the current managed object using the backup configuration file from Step 3, or re-download the configuration file to the managed object. If they are consistent, the configuration download task is complete. Step 7 includes the following steps: Step 7.1: The mobile management unit receives the SV / GOOSE message sent by the managed object, parses the APPID of the received SV / GOOSE message, and confirms whether the APPID of the received SV / GOOSE message is consistent with the APPID of the SV / GOOSE message obtained in step 6. If they are consistent, proceed to the next step; if they are inconsistent, prompt the user that the current managed object is inconsistent with the selected and configured managed object. Step 7.2: The mobile management unit logs into the currently connected managed object via FTP service. If the login is successful, proceed to the next step; if the login fails, prompt the user to confirm the FTP login name and password. Step 10, comparing the SV / GOOSE message model of the managed object obtained through the SV / GOOSE message reception service with the SV / GOOSE message model obtained by parsing the SCD file, includes the following steps: Step 10.1: Compare the SV / GOOSE header of the managed object obtained by calling through the SV / GOOSE message receiving protocol with the SV / GOOSE header of the managed object obtained by parsing the SCD file. The SV / GOOSE header contains the IP and MAC address. If they do not match, prompt the user that the configuration download task failed. Then, revert to the current managed object using the configuration file backed up in step 8 or re-download the configuration file to the managed object. If they match, proceed to step 10.

2. Step 10.2: Compare the number of SV / GOOSE data channels of the managed object obtained by calling through the SV / GOOSE message receiving protocol with the number of SV / GOOSE data channels of the managed object obtained by parsing the SCD file. If they are not consistent, prompt the user that the configuration download task failed and revert to the current managed object through the configuration file backed up in step 8 or re-download the configuration file to the managed object. If they are consistent, proceed to step 10.

3. Step 10.3: Compare the SV / GOOSE channel type of the managed object obtained by calling through the SV / GOOSE message receiving protocol with the SV / GOOSE channel type of the managed object obtained by parsing the SCD file. If they are inconsistent, prompt the user that the configuration download task has failed. Then, revert to the current managed object by backing up the configuration file in step 8 or re-download the configuration file to the managed object. If they are consistent, the configuration download task is completed.