SCD file consistency verification method based on SV and GOOSE messages

Abstract

The invention discloses an SCD (Substation Configuration Description) file consistency verification method based on SV (Sampled Value) and GOOSE (Generic Object Oriented Substation Event) messages, which comprises the following steps of: respectively acquiring actual process layer network parameters of the SV messages and various GOOSE messages in Ethernet frame data of an SCD model file and a process layer network, actual model information of corresponding control blocks and actual data set information associated with the corresponding control blocks; according to the method, the SCD file is directly compared with the in-station SV and GOOSE messages, the consistency with the in-station actual situation can be guaranteed, the method is compatible with various protection devices before and after nine-unification, the model consistency can be verified by analyzing the real-time communication messages of process layer equipment, and the method has the advantages that the method is simple and convenient to operate and high in practicability. And the accuracy and the reliability of a checking result are fundamentally ensured.

Description

Technical Field

[0001] The present invention belongs to the technical field of smart substations, and in particular relates to an SCD file consistency verification method based on SV and GOOSE messages, which is applicable to SCD management and control of smart substations. Background Art

[0002] The SCD file of a smart substation is the core configuration file that reflects the system configuration information of the smart substation. It describes the models and communication parameter information of all devices within the station. The correctness of the configuration file and any changes directly affect the correctness of the secondary equipment functions. Managing the standardization and correctness of the SCD file is a key factor in the safe and stable operation of the substation. As the scale of the power grid continues to expand, the renovation, expansion, and operation and maintenance work of substations continues to increase. SCD model files are also prone to frequent changes. At the same time, because SCD model files are too professional and different business configuration information is mixed together, relying on manual means to control not only consumes a lot of manpower, but also still makes it difficult to ensure the correctness of the SCD file. The end result is that the SCD file is inconsistent with the model information of the actual devices within the station, which brings risks and challenges to the safe and stable operation of the substation. There is an urgent need for an automatic verification method to ensure the correctness of the SCD file.

[0003] At present, SCD file control has become one of the research hotspots in the field of smart substations and is also the focus of attention of all parties concerned. The current main method for consistency comparison of process-layer device models is to manually use the manufacturer's configuration tool to export the device's CID (Configured IED Description, configured intelligent electronic device description file) and CCD (Configured Communication Data, configured communication data file) files to compare model file differences with SCD files. This consumes a lot of manpower, and for a large number of non-unified process-layer devices, CID and CCD files cannot be obtained. There are a large number of stock stations that cannot carry out online consistency verification, making it difficult to control the correctness of SCD files and unable to meet the current SCD control needs. Summary of the Invention

[0004] The object of the present invention is to address the above-mentioned problems existing in the prior art and to provide an SCD file consistency verification method based on SV and GOOSE messages.

[0005] The above-mentioned purpose of the present invention is achieved by the following technical means:

[0006] The SCD file consistency verification method based on SV and GOOSE messages includes the following steps:

[0007] Step 1: Parse the SCD model file and extract the process layer network parameters of all SV messages and all GOOSE messages defined in the SCD model file, the model information of the corresponding SV control block, and the data set information associated with the corresponding SV control block;

[0008] Step 2: Access the process layer network, parse the Ethernet frame data of the process layer network, obtain the actual process layer network parameters of various SV messages and various GOOSE messages in the Ethernet frame data, the actual model information of the corresponding control block, and the actual data set information associated with the corresponding control block, and perform consistency verification with the process layer network parameters, model information, and data set information of each SV message and each GOOSE message defined in the SCD model file, and output the consistency verification result.

[0009] Step 1 extracts the process layer network parameters of all SV messages defined in the SCD model file, the model information of the corresponding SV control block, and the data set information of the corresponding SV control block, specifically including the following steps:

[0010] Step 1.1.1. Parse the process layer network parameters of type SMV under the SubNetwork node in the SCD model file to obtain the process layer device name, SV control block name, message identifier, and destination MAC address of all SV messages defined in the SCD model file;

[0011] Step 1.1.2, according to the process layer device name of each SV message, parse the model information of the SV control block defined under the SampledValueControl node of the corresponding process layer device in the SCD model file, and obtain the SV control block reference, sampling rate, and data set name associated with the SV control block;

[0012] Step 1.1.3: Parse the dataset information corresponding to the SV control block defined under the DataSet node of the corresponding process layer device in the SCD model file according to the dataset name associated with the SV control block, and obtain the dataset reference, FCDA number, DA number referenced by each FCDA entry, and data type defined by each DA of the dataset corresponding to the SV control block.

[0013] Step 1 extracts the process layer network parameters of all GOOSE messages defined in the SCD model file, the model information of the corresponding GOOSE control block, and the data set information of the corresponding GOOSE control block, which specifically includes the following steps:

[0014] Step 1.2.1. Parse the SCD model file, parse the process layer network parameters of type IECGOOSE under the SubNetwork node in the SCD model file, and obtain the process layer device name, GOOSE control block name, message identifier, heartbeat time, bit change time, and destination MAC address of all GOOSE messages defined in the SCD model file;

[0015] Step 1.2.2, according to the process layer device name of each GOOSE message, parse the model information of the GOOSE control block defined under the GSEControl node of the corresponding process layer device in the SCD model file, and obtain the GOOSE control block reference, sampling rate, and data set name associated with the GOOSE control block;

[0016] Step 1.2.3: Parse the dataset information of the GOOSE control block defined under the DataSet node that matches the dataset name of the GOOSE control block in the SCD model file according to the dataset name associated with the GOOSE control block, and obtain the dataset reference, FCDA number, DA number referenced by each FCDA entry, and data type defined by each DA of the dataset corresponding to the GOOSE control block.

[0017] Step 2 as described above specifically includes the following steps:

[0018] Step 2.1, parse the actual message identifiers and actual destination MAC addresses of various SV messages and various GOOSE messages in the Ethernet frame data, and compare them with the message identifiers and destination MAC addresses of the corresponding SV messages and corresponding GOOSE messages defined in the SCD model file for consistency;

[0019] Step 2.2: parse the actual SV control block references and the actual data set names associated with the SV control blocks of various SV messages in the Ethernet frame data, and compare them with the SV control block references and data set names of the corresponding SV control blocks defined in the SCD model file for consistency;

[0020] Step 2.3: parse the actual data set information associated with the SV control block in each type of SV message in the Ethernet frame data, and compare the consistency with the data set information associated with the corresponding SV control block defined in the SCD model file;

[0021] Step 2.4: Calculate the actual sampling rate of each type of SV message in the Ethernet frame data, and compare it with the sampling rate of the SV control block corresponding to each type of SV message defined in the SCD model file for consistency;

[0022] Step 2.5, parsing the actual GOOSE control block references of the GOOSE control blocks of various GOOSE messages in the Ethernet frame data and the actual data set names associated with the GOOSE control blocks, and performing consistency comparison with the GOOSE control block references and data set names of the corresponding GOOSE control blocks defined in the SCD model file;

[0023] Step 2.6, parsing the actual data set information associated with the GOOSE control block in various GOOSE messages in the Ethernet frame data, and performing consistency comparison with the data set information associated with the corresponding GOOSE control block defined in the SCD model file;

[0024] Step 2.7, calculate the actual heartbeat time and actual position change time of each type of GOOSE message, and compare them with the heartbeat time and position change time of each type of GOOSE message defined in the SCD model file;

[0025] Step 2.8: If steps 2.1 to 2.7 do not output a comparison result indicating consistency check failure, the consistency check passes.

[0026] As mentioned above, step 2.1 specifically includes the following steps:

[0027] Step 2.1.1. Parse the message types of various messages in the Ethernet frame data. If the hexadecimal byte code of the message type is 0x8100, it is an SV message; if the hexadecimal byte code of the message type is 0x88b8, it is a GOOSE message;

[0028] Step 2.1.2: Obtain the actual SV control block name, actual message ID, and actual destination MAC address of each type of SV message in the Ethernet frame data, and compare them with the message ID and destination MAC address of the SV message of the corresponding SV control block defined in the SCD model file for consistency;

[0029] Step 2.1.3, obtain the actual GOOSE control block name, actual message identifier, and actual destination MAC address of each type of GOOSE message in the Ethernet frame data, and compare them with the message identifier and destination MAC address of the GOOSE message of the corresponding GOOSE control block defined in the SCD model file for consistency;

[0030] Step 2.1.4: If the comparison in step 2.1.2 or step 2.1.3 is inconsistent, stop the consistency comparison, output the comparison result of consistency check failure, and prompt an error message; if it is consistent, go to step 2.2.

[0031] As described above, step 2.3 specifically includes the following steps:

[0032] Step 2.3.1. Obtain the actual dataset reference, the actual number of FCDA entries, the actual number of DAs referenced by each actual FCDA entry, and the actual data type defined by each actual DA in the actual dataset information associated with the SV control block in each type of SV message in the Ethernet frame data, and perform consistency comparison with the dataset reference, the actual number of FCDA entries, the actual number of DAs referenced by each actual FCDA entry, and the actual data type defined by each DA in the dataset information associated with the corresponding SV control block defined in the SCD model file.

[0033] Step 2.3.2: If the two are inconsistent, stop the consistency comparison, output the consistency check failure comparison result, and prompt an error message; if they are consistent, go to step 2.4.

[0034] Step 2.4 as described above specifically includes the following steps:

[0035] Step 2.4.1. Store all SV messages received within the set time, classify and count all SV messages according to the actual message identifiers of each type of SV message, obtain the number of SV messages received by each type of actual message identifier within the set time and the maximum sampling point statistical field in the received SV messages;

[0036] Step 2.4.2: Compare the maximum sampling point statistics field of each type of SV message with the sampling rate of the SV control block corresponding to each type of SV message defined in the SCD model file. If the two are inconsistent, it means that there is an error in the data set information of the SV control block in the SCD model file. The consistency comparison is stopped, and the consistency check failure result is output with an error message. If the two are consistent, proceed to step 2.4.3.

[0037] Step 2.4.3. Divide the number of SV messages received by each type of actual message identifier within the set time by the set time to calculate the actual sampling rate of each type of SV message, and compare the actual sampling rate of each type of SV message with the sampling rate of the SV control block corresponding to each type of SV message defined in the SCD model file for consistency. If the two are inconsistent, it means that there is an error in the data set information of the SV control block in the SCD model file. Stop the consistency comparison, output the comparison result of consistency check failure, and prompt an error message; if the two are consistent, go to step 2.5.

[0038] Step 2.6 as described above specifically includes the following steps:

[0039] Step 2.6.1. Obtain the actual dataset reference, the actual number of FCDA entries, the actual number of DAs referenced by each actual FCDA entry, and the actual data type defined by each actual DA in the actual dataset information associated with the GOOSE control block in various GOOSE messages in the Ethernet frame data, and perform consistency comparison with the dataset reference, the actual number of FCDA entries, the actual number of DAs referenced by each actual FCDA entry, and the actual data type defined by each DA in the dataset information associated with the corresponding GOOSE control block defined in the SCD model file;

[0040] Step 2.6.2: If the two are inconsistent, stop the consistency comparison, output the consistency check failure comparison result, and prompt an error message; if the two are consistent, go to step 2.7.

[0041] Step 2.7 as described above specifically includes the following steps:

[0042] Step 2.7.1, store all GOOSE messages received within the set time, classify all received GOOSE messages according to the actual message identifier, obtain the message status sequence number and sequence number of each GOOSE message received by each type of actual message identifier, and calculate the time interval between two frames of GOOSE messages with increasing sequence numbers when the message status sequence number of each type of GOOSE message does not change as T1, where T1 is the actual heartbeat time calculated;

[0043] Step 2.7.2, calculate the time interval between two frames of GOOSE messages with increasing sequence numbers when the message status sequence number of each type of GOOSE message changes as T2, where T2 is the calculated actual change time;

[0044] Step 2.7.3, the calculated actual heartbeat time T1 of each type of GOOSE message is compared with the heartbeat time corresponding to the corresponding GOOSE message defined in the SCD model file for consistency. If the two are inconsistent, it means that there is an error in the heartbeat time defined in the SCD model file, and the consistency comparison is stopped. The comparison result of consistency check failure is output and an error message is prompted;

[0045] Step 2.7.4: Compare the calculated actual displacement time T2 of each type of GOOSE message with the displacement time corresponding to the corresponding GOOSE message defined in the SCD model file for consistency. If the two are inconsistent, it means that there is an error in the displacement time defined in the SCD model file. Stop the consistency comparison, output the comparison result of consistency check failure, and prompt an error message.

[0046] A computer device includes a memory and a processor, wherein the memory stores a computer program, and when the processor executes the computer program, it implements any one of the steps of the SCD model consistency verification method described above.

[0047] Compared with the prior art, the present invention has the following beneficial effects:

[0048] The consistency check of the present invention covers the process layer network parameters of SV messages and GOOSE messages, the model information of the corresponding SV control block, and the data set information of the corresponding SV control block. The SCD file is directly compared with the SV and GOOSE messages in the station, which can ensure consistency with the actual situation in the station, and solve the problems that the process layer intelligent terminals, merging units and other equipment cannot call CID and CCD model files online, cannot carry out online consistency verification, and are difficult to control the correctness of SCD files. The solution of the present invention is not only compatible with various protection devices before and after the nine unifications, but also can verify the model consistency by parsing the real-time communication messages of the process layer equipment, fundamentally ensuring the accuracy and reliability of the verification results. BRIEF DESCRIPTION OF THE DRAWINGS

[0049] Figure 1 is a flow chart of the method of the present invention. DETAILED DESCRIPTION

[0050] In order to facilitate those skilled in the art to understand and implement the present invention, the present invention is further described in detail below with reference to the embodiments. The embodiments described herein are only used to illustrate and explain the present invention and are not intended to limit the present invention.

[0051] Example 1:

[0052] The SCD file consistency verification method based on SV and GOOSE messages includes the following steps:

[0053] Step 1: Parse the SCD model file (i.e., the SCD file is a standardized file used to describe the configuration and communication settings of the smart substation) and extract the process layer network parameters and device model information of all SV messages and all GOOSE messages defined in the SCD model file. The device model information includes the model information of the control block and the data set information associated with the control block. The specific steps include:

[0054] Step 1.1: Parse the SCD model file to extract the process layer network parameters of all SV messages defined in the SCD model file, the model information of the corresponding SV control block, and the data set information of the corresponding SV control block. Specifically, the following steps are included:

[0055] Step 1.1.1. Parse the SCD model file and the process layer network parameters of the type (type) sampled value (SMV) under the SubNetwork (communication subnet) node in the SCD model file. Obtain the process layer device name (iedName), the SV control block name (cbName) of the process layer device, the message identifier (APPID), and the destination MAC address (i.e., multicast address) of all SV messages defined in the SCD model file.

[0056] The SubNetwork node is used to define an independent communication network segment (communication subnet) within the substation. The subnet type is identified by the type attribute: when the type is SMV, it transmits sampled value messages (i.e., SV messages); when the type is IECGOOSE, it transmits trip signals or status values ​​(i.e., GOOSE messages);

[0057] Step 1.1.2. Parse the SV control block model information defined under the SampledValueControl node (used to define the model information of the SV control block) of the corresponding process layer device in the SCD model file based on the process layer device name of each SV message, and obtain the SV control block reference (smvID, which uniquely identifies an SV control block and is used to manage the generation, transmission, and parameter configuration of SV messages), sampling rate (smpRate), and data set name (datSet, which is used to specify the name of the data set associated with the control block) of the SV control block.

[0058] Step 1.1.3: Based on the dataset name datSet associated with the SV control block, parse the dataset information corresponding to the SV control block defined under the dataset (DataSet) node of the corresponding process-layer device in the SCD model file that matches the dataset name datSet of the SV control block. Obtain the dataset reference (datsetRef) and the number of FCDAs (Functional Constraint Data Attributes) of the dataset corresponding to the SV control block. Then, traverse each FCDA entry, extract the DA (Data Attribute, used to define the specific data type, such as integer, floating-point, Boolean) list under each FCDA entry, and obtain the number of DAs referenced by the FCDA entries in the DA list and the data type defined by each DA.

[0059] Step 1.2: Parse the SCD model file to extract the process layer network parameters of all GOOSE messages defined in the SCD model file, the model information of the corresponding GOOSE control block, and the data set information of the corresponding GOOSE control block, specifically including the following steps:

[0060] Step 1.2.1. Parse the SCD model file and the network parameter information of type IECGOOSE under the SubNetwork node in the SCD model file. Obtain the process layer device name (iedName), GOOSE control block name (cbName), message identifier (APPID), heartbeat time (MaxTime, the message sending interval when GOOSE data has not changed), change time (MinTime, the message sending interval when GOOSE data has changed), and destination MAC address of all GOOSE messages defined in the SCD model file.

[0061] Step 1.2.2, according to the process layer device name iedName of each GOOSE message, parse the model information of the GOOSE control block defined under the GOOSE control block (GSEControl) node of the corresponding process layer device in the SCD model file, and obtain the GOOSE control block reference (smvID, which uniquely identifies a GOOSE control block and is used to manage the generation, transmission and parameter configuration of GOOSE messages), sampling rate (smpRate), and data set name (datSet) associated with the GOOSE control block;

[0062] Step 1.2.3, according to the dataset name datSet associated with the GOOSE control block, parse the dataset information of the GOOSE control block defined under the dataset (DataSet) node of the corresponding process layer device in the SCD model file that matches the dataset name datSet of the GOOSE control block, obtain the dataset reference (datsetRef) and the number of FCDAs of the dataset corresponding to the GOOSE control block, traverse each FCDA entry, extract the DA list under each FCDA entry, and obtain the number of DAs referenced by the FCDA entries in the DA list and the data type defined by each DA;

[0063] Step 2, access the process layer network, parse the Ethernet frame data of the process layer network, obtain the actual process layer network parameters of various SV messages and various GOOSE messages, the actual model information of the corresponding SV control block, and the actual dataset information associated with the corresponding SV control block in the Ethernet frame data of the process layer network, and perform consistency check on the actual process layer network parameters of various SV messages and various GOOSE messages, the actual model information of the corresponding SV control block, and the actual dataset information associated with the corresponding SV control block in the Ethernet frame data of the process layer network and the process layer network parameters, model information, and dataset information of each SV message and each GOOSE message defined in the SCD model file, and output the consistency check result, which specifically includes the following steps:

[0064] Step 2.1, parse the actual message identifier and actual destination MAC address of various SV messages and various GOOSE messages in the Ethernet frame data of the process layer network, and perform consistency comparison on the actual message identifier and actual destination MAC address of various SV messages and various GOOSE messages and the message identifier and destination MAC address of the corresponding SV message and the corresponding GOOSE message defined in the SCD model file, specifically including the following steps:

[0065] Step 2.1.1, parse the message type of various messages in the Ethernet frame data of the process layer network, if the 16-bit byte code of the message type is 0x8100, it is an SV message; if the 16-bit byte code of the message type is 0x88b8, it is a GOOSE message;

[0066] Step 2.1.2, obtain the actual SV control block name, actual message identifier, and actual destination MAC address of various SV messages in the Ethernet frame data of the process layer network, and perform consistency comparison on the actual message identifier and actual destination MAC address of various SV messages in the Ethernet frame data and the message identifier and destination MAC address of the SV message of the corresponding SV control block defined in the SCD model file according to the actual SV control block name of various SV messages;

[0067] Step 2.1.3, obtain the actual GOOSE control block name, actual message identifier, and actual destination MAC address of various GOOSE messages in the Ethernet frame data of the process layer network, and perform consistency comparison on the actual message identifier and actual destination MAC address of various GOOSE messages in the Ethernet frame data and the message identifier and destination MAC address of the GOOSE message of the corresponding GOOSE control block defined in the SCD model file according to the actual GOOSE control block name of each GOOSE message;

[0068] Step 2.1.4: If the comparison in step 2.1.2 or step 2.1.3 is inconsistent, it means that there is an error in the process layer network parameters defined in the SCD model file. Stop the consistency comparison, output the comparison result of consistency check failure, and prompt an error message; if it is consistent, go to step 2.2.

[0069] Step 2.2, parsing the actual SV control block references of the SV control blocks of various SV messages in the Ethernet frame data of the process layer network and the actual data set names associated with the SV control blocks, and performing consistency comparison on the actual model information of the SV control blocks of various SV messages in the Ethernet frame data with the SV control block references and data set names in the model information of the corresponding SV control blocks defined in the SCD model file. If the two are inconsistent, it indicates that there is an error in the model information of the SV control block defined in the SCD model file, and the consistency comparison is stopped, and the comparison result of consistency check failure is output, and an error message is prompted;

[0070] Step 2.3: Parse the actual data set information associated with the SV control block in each type of SV message in the Ethernet frame data of the process layer network, and compare the actual data set information associated with the SV control block in each type of SV message in the Ethernet frame data with the data set information associated with the corresponding SV control block defined in the SCD model file for consistency, specifically including the following steps:

[0071] Step 2.3.1, obtaining the actual data set reference, the actual number of FCDA entries, the actual number of DAs referenced by each actual FCDA entry, and the actual data type defined by each actual DA in the actual data set information associated with the SV control block in each SV message in the Ethernet frame data of the process layer network;

[0072] Compare the actual data set references, actual number of FCDA entries, actual number of DAs referenced by each actual number of FCDA entries, and actual data types defined by each actual DA in each type of SV message with the data set references, actual number of FCDA entries, actual number of DAs referenced by each actual number of FCDA entries, and actual data types defined by each actual DA in the data set information associated with the corresponding SV control block defined in the SCD model file.

[0073] Step 2.3.2: If the two are inconsistent, there is an error in the data set information of the SV control block in the SCD model file. Stop the consistency comparison, output the consistency check failure comparison result, and prompt an error message; if they are consistent, go to step 2.4.

[0074] Step 2.4: Calculate the actual sampling rate of each SV message in the Ethernet frame data of the process layer network, and compare the actual sampling rate of each SV message with the sampling rate of the SV control block corresponding to each SV message defined in the SCD model file. Specifically, the following steps are included:

[0075] Step 2.4.1. Store all SV messages received within a set time (e.g., five minutes), classify and count all SV messages according to the actual message identifiers of each type of SV message, and obtain the number of SV messages received by each type of actual message identifier within the set time (svCnt) and the maximum sampling point statistics field (smpCnt) in the received SV messages;

[0076] Step 2.4.2: Compare the maximum sampling point statistics field smpCnt of each type of SV message with the sampling rate of the SV control block corresponding to each type of SV message defined in the SCD model file. If the two are inconsistent, it means that there is an error in the data set information of the SV control block in the SCD model file. The consistency comparison is stopped, and the comparison result of consistency check failure is output, and an error message is prompted. If the two are consistent, proceed to step 2.4.3.

[0077] The maximum sampling point statistics field smpCnt is the maximum sampling sequence number, which is equal to the sampling rate in value.

[0078] Step 2.4.3: Divide the number of SV messages received by each type of actual message identifier within the set time by the set time to calculate the actual sampling rate of each type of SV message. Compare the actual sampling rate of each type of SV message with the sampling rate of the SV control block corresponding to each type of SV message defined in the SCD model file for consistency. If the two are inconsistent, it means that there is an error in the data set information of the SV control block in the SCD model file. Stop the consistency comparison, output the comparison result of consistency check failure, and prompt an error message; if the two are consistent, proceed to step 2.5;

[0079] Step 2.4.3 can avoid the abnormal situation in which the sampling sequence number in step 2.4.2 does not start from 1, resulting in misjudgment;

[0080] Step 2.5, parse the actual GOOSE control block references of the GOOSE control blocks of various GOOSE messages in the Ethernet frame data of the process layer network and the actual data set names associated with the GOOSE control blocks, and compare the actual GOOSE control block references of the GOOSE control blocks of various GOOSE messages in the Ethernet frame data and the actual data set names associated with the GOOSE control blocks with the GOOSE control block reference smvID and data set name in the model information of the corresponding GOOSE control block defined in the SCD model file for consistency. If the two are consistent, go to step 2.6; if the two are inconsistent, it means that there is an error in the model information of the GOOSE control block defined in the SCD file, stop the consistency comparison, output the comparison result of consistency check failure, and prompt an error message.

[0081] Step 2.6: Parse the actual data set information associated with the GOOSE control block in various GOOSE messages in the Ethernet frame data of the process layer network, and compare the actual data set information associated with the GOOSE control block in various GOOSE messages in the Ethernet frame data with the data set information associated with the corresponding GOOSE control block defined in the SCD model file for consistency, specifically including the following steps:

[0082] Step 2.6.1, obtaining the actual data set reference, the actual number of FCDA entries, the actual number of DAs referenced by each actual FCDA entry, and the actual data type defined by each actual DA in the actual data set information associated with the GOOSE control block in various GOOSE messages in the Ethernet frame data of the process layer network;

[0083] The actual data set references, actual number of FCDA entries, actual number of DAs referenced by each actual number of FCDA entries, and actual data types defined by each actual DA of each type of GOOSE message are compared for consistency with the data set references, actual number of FCDA entries, actual number of DAs referenced by each actual number of FCDA entries, and data types defined by each actual DA under the data set associated with the corresponding GOOSE control block defined in the SCD model file;

[0084] Step 2.6.2: If the two are inconsistent, it indicates that there is an error in the data set information of the SV control block in the SCD model file. The consistency comparison is stopped, and the consistency check failure result is output with an error message. If the two are consistent, proceed to step 8.

[0085] Step 2.7, when no displacement data is generated, GOOSE data is sent in the form of heartbeat data, at this time the packet is sent according to the heartbeat time MaxTime, when displacement data is generated, the data is sent according to the displacement time MinTime, the actual heartbeat time and the actual displacement time of each type of GOOSE packet are calculated, and the actual heartbeat time and the actual displacement time of each type of GOOSE packet are respectively compared with the heartbeat time and the displacement time of the corresponding GOOSE packet defined in the SCD model file, which specifically includes the following steps:

[0086] Step 2.7.1, store all GOOSE packets received within the set time (such as five minutes), classify all received GOOSE packets according to the actual packet identifier, obtain the packet state sequence number (stNum) and the order sequence number (sqNum) of each GOOSE packet received by each type of actual packet identifier, and calculate the time interval T1 between two frames of GOOSE packets when the order sequence number sqNum is incremented without changing the packet state sequence number stNum, T1 is the actual heartbeat time calculated;

[0087] Step 2.7.2, calculate the time interval T2 between two frames of GOOSE packets when the order sequence number sqNum is incremented when the packet state sequence number stNum is changed, T2 is the actual displacement time calculated;

[0088] Step 2.7.3, compare the actual heartbeat time T1 of each type of GOOSE packet calculated with the corresponding heartbeat time MaxTime of each type of GOOSE packet defined in the SCD model file, if the two are inconsistent, it means that the heartbeat time MaxTime information defined in the SCD model file is incorrect, stop the consistency comparison, and output the comparison result of the consistency check failure, and prompt the error information;

[0089] Step 2.7.4, compare the actual displacement time T2 of each type of GOOSE packet calculated with the corresponding displacement time MinTime of each type of GOOSE packet defined in the SCD model file, if the two are inconsistent, it means that the displacement time defined in the SCD model file is incorrect, stop the consistency comparison, and output the comparison result of the consistency check failure, and prompt the error information;

[0090] Step 2.8, if steps 2~8 do not output the comparison result of the consistency check failure, it means that the process layer network parameters of the SCD model file, the model information of the corresponding GOOSE control block, and the data set information of the corresponding GOOSE control block are consistent with the actual, and the consistency check is passed.

[0091] In one embodiment, a computer device is further provided, including a memory and a processor. The memory stores a computer program, and the processor implements the steps in the above method embodiments when executing the computer program.

[0092] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the steps in the above-mentioned method embodiments are implemented.

[0093] In one embodiment, a computer program product is provided, including a computer program, which implements the steps in the above method embodiments when executed by a processor.

[0094] It should be noted that the embodiments described herein are merely illustrative of the spirit of the present invention. Persons skilled in the art may make various modifications, additions, or substitutions to the described embodiments without departing from the spirit of the present invention or exceeding the scope of the appended claims.

Claims

1. The SCD file consistency verification method based on SV and GOOSE messages is characterized in that: The following steps are involved: Step 1: Parse the SCD model file and extract the process layer network parameters of all SV messages and all GOOSE messages defined in the SCD model file, the model information of the corresponding SV control block, and the data set information associated with the corresponding SV control block; Step 2: Access the process layer network, parse the Ethernet frame data of the process layer network, obtain the actual process layer network parameters of various SV messages and various GOOSE messages in the Ethernet frame data, the actual model information of the corresponding control block, and the actual data set information associated with the corresponding control block, and perform consistency verification with the process layer network parameters, model information, and data set information of each SV message and each GOOSE message defined in the SCD model file, and output the consistency verification result.

2. The SCD file consistency verification method based on SV and GOOSE messages according to claim 1, characterized in that, Step 1 extracts the process layer network parameters of all SV messages defined in the SCD model file, the model information of the corresponding SV control block, and the data set information of the corresponding SV control block, specifically including the following steps: Step 1.1.

1. Parse the process layer network parameters of type SMV under the SubNetwork node in the SCD model file to obtain the process layer device name, SV control block name, message identifier, and destination MAC address of all SV messages defined in the SCD model file; Step 1.1.2, according to the process layer device name of each SV message, parse the model information of the SV control block defined under the SampledValueControl node of the corresponding process layer device in the SCD model file, and obtain the SV control block reference, sampling rate, and data set name associated with the SV control block; Step 1.1.3: Parse the dataset information corresponding to the SV control block defined under the DataSet node of the corresponding process layer device in the SCD model file according to the dataset name associated with the SV control block, and obtain the dataset reference, FCDA number, DA number referenced by each FCDA entry, and data type defined by each DA of the dataset corresponding to the SV control block.

3. The SCD file consistency verification method based on SV and GOOSE messages according to claim 1, characterized in that, Step 1 extracts the process layer network parameters of all GOOSE messages defined in the SCD model file, the model information of the corresponding GOOSE control block, and the data set information of the corresponding GOOSE control block, which specifically includes the following steps: Step 1.2.

1. Parse the SCD model file, parse the process layer network parameters of type IECGOOSE under the SubNetwork node in the SCD model file, and obtain the process layer device name, GOOSE control block name, message identifier, heartbeat time, bit change time, and destination MAC address of all GOOSE messages defined in the SCD model file; Step 1.2.2, according to the process layer device name of each GOOSE message, parse the model information of the GOOSE control block defined under the GSEControl node of the corresponding process layer device in the SCD model file, and obtain the GOOSE control block reference, sampling rate, and data set name associated with the GOOSE control block; Step 1.2.3: Parse the dataset information of the GOOSE control block defined under the DataSet node that matches the dataset name of the GOOSE control block in the corresponding process layer device in the SCD model file according to the dataset name associated with the GOOSE control block, and obtain the dataset reference, FCDA number, DA number referenced by each FCDA entry, and data type defined by each DA of the dataset corresponding to the GOOSE control block.

4. The SCD file consistency verification method based on SV and GOOSE messages according to claim 1, characterized in that: The step 2 specifically includes the following steps: Step 2.1, parse the actual message identifiers and actual destination MAC addresses of various SV messages and various GOOSE messages in the Ethernet frame data, and compare them with the message identifiers and destination MAC addresses of the corresponding SV messages and corresponding GOOSE messages defined in the SCD model file for consistency; Step 2.2: parse the actual SV control block references and the actual data set names associated with the SV control blocks of various SV messages in the Ethernet frame data, and compare them with the SV control block references and data set names of the corresponding SV control blocks defined in the SCD model file for consistency; Step 2.3: parse the actual data set information associated with the SV control block in each type of SV message in the Ethernet frame data, and compare the consistency with the data set information associated with the corresponding SV control block defined in the SCD model file; Step 2.4: Calculate the actual sampling rate of each type of SV message in the Ethernet frame data, and compare it with the sampling rate of the SV control block corresponding to each type of SV message defined in the SCD model file for consistency; Step 2.5, parsing the actual GOOSE control block references of the GOOSE control blocks of various GOOSE messages in the Ethernet frame data and the actual data set names associated with the GOOSE control blocks, and performing consistency comparison with the GOOSE control block references and data set names of the corresponding GOOSE control blocks defined in the SCD model file; Step 2.6, parsing the actual data set information associated with the GOOSE control block in various GOOSE messages in the Ethernet frame data, and performing consistency comparison with the data set information associated with the corresponding GOOSE control block defined in the SCD model file; Step 2.7, calculate the actual heartbeat time and actual position change time of each type of GOOSE message, and compare them with the heartbeat time and position change time of each type of GOOSE message defined in the SCD model file; Step 2.8: If steps 2.1 to 2.7 do not output a comparison result indicating consistency check failure, the consistency check passes.

5. The SCD file consistency verification method based on SV and GOOSE messages according to claim 4, characterized in that: The step 2.1 specifically includes the following steps: Step 2.1.

1. Parse the message types of various messages in the Ethernet frame data. If the hexadecimal byte code of the message type is 0x8100, it is an SV message; if the hexadecimal byte code of the message type is 0x88b8, it is a GOOSE message; Step 2.1.2: Obtain the actual SV control block name, actual message ID, and actual destination MAC address of each type of SV message in the Ethernet frame data, and compare them with the message ID and destination MAC address of the SV message of the corresponding SV control block defined in the SCD model file for consistency; Step 2.1.3, obtain the actual GOOSE control block name, actual message identifier, and actual destination MAC address of each type of GOOSE message in the Ethernet frame data, and compare them with the message identifier and destination MAC address of the GOOSE message of the corresponding GOOSE control block defined in the SCD model file for consistency; Step 2.1.4: If the comparison in step 2.1.2 or step 2.1.3 is inconsistent, stop the consistency comparison, output the comparison result of consistency check failure, and prompt an error message; if it is consistent, go to step 2.

2.

6. The SCD file consistency verification method based on SV and GOOSE messages according to claim 4, characterized in that: The step 2.3 specifically includes the following steps: Step 2.3.

1. Obtain the actual dataset reference, the actual number of FCDA entries, the actual number of DAs referenced by each actual FCDA entry, and the actual data type defined by each actual DA in the actual dataset information associated with the SV control block in each type of SV message in the Ethernet frame data, and perform consistency comparison with the dataset reference, the actual number of FCDA entries, the actual number of DAs referenced by each actual FCDA entry, and the actual data type defined by each DA in the dataset information associated with the corresponding SV control block defined in the SCD model file. Step 2.3.2: If the two are inconsistent, stop the consistency comparison, output the consistency check failure comparison result, and prompt an error message; if they are consistent, go to step 2.

4.

7. The SCD file consistency verification method based on SV and GOOSE messages according to claim 4, characterized in that: The step 2.4 specifically includes the following steps: Step 2.4.

1. Store all SV messages received within the set time, classify and count all SV messages according to the actual message identifiers of each type of SV message, obtain the number of SV messages received by each type of actual message identifier within the set time and the maximum sampling point statistical field in the received SV messages; Step 2.4.2: Compare the maximum sampling point statistics field of each type of SV message with the sampling rate of the SV control block corresponding to each type of SV message defined in the SCD model file. If the two are inconsistent, it means that there is an error in the data set information of the SV control block in the SCD model file. The consistency comparison is stopped, and the consistency check failure result is output with an error message. If the two are consistent, proceed to step 2.4.

3. Step 2.4.

3. Divide the number of SV messages received by each type of actual message identifier within the set time by the set time to calculate the actual sampling rate of each type of SV message, and compare the actual sampling rate of each type of SV message with the sampling rate of the SV control block corresponding to each type of SV message defined in the SCD model file for consistency. If the two are inconsistent, it means that there is an error in the data set information of the SV control block in the SCD model file. Stop the consistency comparison, output the comparison result of consistency check failure, and prompt an error message; if the two are consistent, go to step 2.

5.

8. The SCD file consistency verification method based on SV and GOOSE messages according to claim 4, characterized in that: The step 2.6 specifically includes the following steps: Step 2.6.

1. Obtain the actual dataset reference, the actual number of FCDA entries, the actual number of DAs referenced by each actual FCDA entry, and the actual data type defined by each actual DA in the actual dataset information associated with the GOOSE control block in various GOOSE messages in the Ethernet frame data, and perform consistency comparison with the dataset reference, the actual number of FCDA entries, the actual number of DAs referenced by each actual FCDA entry, and the actual data type defined by each DA in the dataset information associated with the corresponding GOOSE control block defined in the SCD model file; Step 2.6.2: If the two are inconsistent, stop the consistency comparison, output the consistency check failure comparison result, and prompt an error message; if the two are consistent, go to step 2.

7.

9. The SCD file consistency verification method based on SV and GOOSE messages according to claim 4, characterized in that: The step 2.7 specifically includes the following steps: Step 2.7.1, store all GOOSE messages received within the set time, classify all received GOOSE messages according to the actual message identifier, obtain the message status sequence number and sequence number of each GOOSE message received by each type of actual message identifier, and calculate the time interval between two frames of GOOSE messages with increasing sequence numbers when the message status sequence number of each type of GOOSE message does not change as T1, where T1 is the actual heartbeat time calculated; Step 2.7.2, calculate the time interval between two frames of GOOSE messages with increasing sequence numbers when the message status sequence number of each type of GOOSE message changes as T2, where T2 is the calculated actual change time; Step 2.7.3, the calculated actual heartbeat time T1 of each type of GOOSE message is compared with the heartbeat time corresponding to the corresponding GOOSE message defined in the SCD model file for consistency. If the two are inconsistent, it means that there is an error in the heartbeat time defined in the SCD model file, and the consistency comparison is stopped. The comparison result of consistency check failure is output and an error message is prompted; Step 2.7.4: Compare the calculated actual displacement time T2 of each type of GOOSE message with the displacement time corresponding to the corresponding GOOSE message defined in the SCD model file for consistency. If the two are inconsistent, it means that there is an error in the displacement time defined in the SCD model file. Stop the consistency comparison, output the comparison result of consistency check failure, and prompt an error message.

10. A computer device comprising a memory and a processor, wherein the memory stores a computer program, wherein: When the processor executes the computer program, the steps of the SCD model consistency verification method according to any one of claims 1 to 9 are implemented.

Images