Automated verification methods and devices for GOOSE messages

By using an automated verification method, importing configuration files, and comparing GOOSE message mapping relationships, the problem of low GOOSE message verification efficiency in the transformation of non-standard digital substations is solved, achieving efficient and accurate message conversion and equipment security.

CN119402563BActive Publication Date: 2025-11-14GUANGDONG POWER GRID CO LTD +1
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
CN202411478887.5
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2024-10-22
Publication Date
2025-11-14
Estimated Expiration
2044-10-22

AI Technical Summary

Technical Problem

In existing technologies, the verification efficiency of GOOSE messages is low, the workload is large, and errors are prone to occur during the transformation of non-standard digital substations into intelligent substations, which affects the safety of other operating equipment.

Method used

An automated verification method is adopted. By importing the configuration file of the device to be verified, the mapping relationship between GOOSE incoming messages and GOOSE outgoing messages is determined. The target message is sent for format conversion, and the results are compared to determine consistency and issue an alarm signal.

Benefits of technology

It improves the efficiency and accuracy of GOOSE message verification, reduces manual intervention, and ensures the safe operation of other devices.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119402563B_ABST
    Figure CN119402563B_ABST
Patent Text Reader

Abstract

This invention discloses an automated verification method and apparatus for GOOSE messages. The method includes: importing a configuration file of the device to be verified; determining the mapping relationship between GOOSE incoming and outgoing messages of the device to be verified based on the configuration file; sending a target GOOSE incoming message to the device to be verified, so that the device to be verified performs format conversion on the target GOOSE incoming message; receiving the target GOOSE outgoing message sent by the device to be verified; and issuing an alarm signal if the target GOOSE incoming and outgoing messages do not satisfy the mapping relationship. This invention solves the technical problems of related technologies that use manual verification methods to perform consistency verification on received and sent GOOSE messages, resulting in a large workload, susceptibility to errors, and low efficiency.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This invention relates to the field of intelligent substation technology, and more specifically, to an automated verification method and device for GOOSE messages. Background Technology

[0002] Non-standard digital substations, namely early digital substations, used fiber optic SV sampling and fiber optic GOOSE tripping. Because digital technology was not mature at the time, there were no relevant standards to refer to during the substation design process. Therefore, there are some technical differences in GOOSE / SV messages compared with the current standardized smart substations.

[0003] For digital equipment in non-standard digital substations, the GOOSE message sending format differs from the current standardized GOOSE message sending format. In scenarios where non-standard digital substations are upgraded to intelligent substations with cable sampling and optical cable tripping, or intelligent substations with optical cable sampling and optical cable tripping, there are situations where cross-bay equipment is simultaneously connected to single-bay equipment before and after the upgrade. To ensure that the cross-bay equipment operates throughout the upgrade process, bidirectional conversion between non-standard and standardized GOOSE messages is required.

[0004] The GOOSE message interface conversion device can achieve bidirectional conversion between non-standard and standardized GOOSE messages. However, during the intelligent transformation of substations, all equipment in the bays except the one being upgraded remains operational. To ensure the safe operation of other equipment is not affected, a secure interface verification scheme for the interface conversion device needs to be considered after the upgraded bay is connected to the interface conversion device. The current verification scheme uses manual verification: the verification instrument sends GOOSE messages to the interface conversion device, and the user manually captures packets to receive the messages sent by the interface conversion device, checking whether the received GOOSE messages correspond correctly to the sent GOOSE messages. This verification scheme is inefficient, labor-intensive, and prone to errors. Furthermore, since all equipment in the bays except the one being upgraded remains operational, it could potentially affect other operating equipment.

[0005] In the process of digital transformation of substations, when verifying the correctness of GOOSE input and output message conversion of interface conversion devices, manual verification is labor-intensive, inefficient, error-prone, and dangerous.

[0006] There is currently no effective solution to the problem that the manual verification method used in the aforementioned related technologies to perform consistency verification on received and sent GOOSE messages results in a large workload, is prone to errors, and has low efficiency. Summary of the Invention

[0007] This invention provides an automated verification method and apparatus for GOOSE messages, which at least solves the technical problems in related technologies where manual verification of received and sent GOOSE messages results in a large workload, is prone to errors, and is inefficient.

[0008] According to one aspect of the present invention, an automated verification method for GOOSE messages is provided, comprising: importing a configuration file of a device to be verified, wherein the device to be verified refers to a device that needs to convert the format of GOOSE messages during the intelligent transformation of a substation, the GOOSE message refers to a specific type of message used in the substation for transmitting critical event information, and the configuration file contains configuration information of the device to be verified; determining a mapping relationship between GOOSE incoming messages and GOOSE outgoing messages of the device to be verified based on the configuration file, wherein the GOOSE incoming messages refer to the GOOSE messages sent to the device to be verified, and the GOOSE outgoing messages refer to the GOOSE messages received from the device to be verified; and converting the target GOOSE incoming messages... The message is sent to the device to be verified, so that the device to be verified can perform format conversion on the target GOOSE input message. The target GOOSE input message is used to verify the accuracy of the format conversion performed by the device to be verified. After converting the target GOOSE input message, the device to be verified outputs a target GOOSE output message corresponding to the target GOOSE input message. The device receives the target GOOSE output message sent by the device to be verified. The correspondence between the target GOOSE input message and the target GOOSE output message is compared with the mapping relationship to obtain a comparison result. If the comparison result indicates that the target GOOSE input message and the target GOOSE output message do not satisfy the mapping relationship, an alarm signal is issued.

[0009] Optionally, importing the configuration file of the device to be verified includes: importing the process layer configuration file of the device to be verified, wherein the process layer configuration file is used to determine the GOOSE incoming message information of the GOOSE incoming messages subscribed to by the device to be verified, the reference paths of the GOOSE incoming messages and the GOOSE outgoing messages; and importing the internal configuration file of the device to be verified, wherein the internal configuration file is used to determine the mapping relationship between the GOOSE incoming messages and the GOOSE outgoing messages.

[0010] Optionally, the mapping relationship includes: a first mapping relationship and a second mapping relationship. Determining the mapping relationship between GOOSE incoming messages and GOOSE outgoing messages of the device to be verified based on the configuration file includes: determining the first mapping relationship between new GOOSE incoming messages and old GOOSE outgoing messages based on the configuration file, wherein the new GOOSE incoming message refers to a GOOSE incoming message with the same message format as a specific message format, and the old GOOSE outgoing message refers to a GOOSE outgoing message with a different message format than the specific message format, and the specific message format refers to a message format conforming to a specific standard; and determining the second mapping relationship between old GOOSE incoming messages and new GOOSE outgoing messages based on the configuration file, wherein the old GOOSE incoming message refers to a GOOSE incoming message with a different message format than the specific message format, and the new GOOSE outgoing message refers to a GOOSE outgoing message with the same message format as the specific message format.

[0011] Optionally, the target GOOSE incoming message includes: a target new GOOSE incoming message and a target old GOOSE incoming message; the target GOOSE outgoing message includes: a target new GOOSE outgoing message and a target old GOOSE outgoing message; and the target GOOSE incoming message is sent to the device to be verified, so that the device to be verified performs format conversion on the target GOOSE incoming message, including: sending the target new GOOSE incoming message to the device to be verified, so that the device to be verified performs format conversion on the target new GOOSE incoming message. The format conversion process involves the device under test converting the target new GOOSE inbound message into a format and then outputting a target old GOOSE outbound message corresponding to the target new GOOSE inbound message. The target old GOOSE inbound message is then sent to the device under test, enabling the device under test to convert the format of the target new GOOSE inbound message. The device under test, after converting the format of the target old GOOSE inbound message, outputs a target new GOOSE outbound message corresponding to the target old GOOSE inbound message.

[0012] Optionally, the correspondence between the target GOOSE incoming message and the target GOOSE outgoing message is compared with the mapping relationship to obtain a comparison result, including at least one of the following: obtaining the number of message frames received within a predetermined time period after sending the target GOOSE incoming message to the device to be verified; comparing the number of message frames with a predetermined number to obtain a first comparison result; obtaining the first device instantiation name of the target GOOSE incoming message and the second device instantiation name of the target GOOSE outgoing message, wherein the first device instantiation name, the target GOOSE outgoing message, and the target GOOSE outgoing message are used to obtain a first device instantiation result. The second device instantiation name refers to the unique identifier of the target GOOSE incoming message and the target GOOSE outgoing message in the substation; the first device instantiation name is compared with the second device instantiation name to obtain a second comparison result; the first reference path of the target GOOSE incoming message and the second reference path of the target GOOSE outgoing message are obtained, wherein the first reference path and the second reference path are reference paths obtained according to the configuration file; the first reference path and the second reference path are compared to obtain a third comparison result.

[0013] Optionally, obtaining the second reference path of the target GOOSE outgoing message includes: upon receiving the target GOOSE outgoing message sent by the device to be verified, determining that a data member in the target GOOSE outgoing message whose state has changed is a target data member, wherein the state change occurs when arbitrarily selecting one of the data members from the dataset corresponding to the target GOOSE incoming message for state update during the process of sending the target GOOSE incoming message to the device to be verified; obtaining the target reference path of the target data member; and determining that the target reference path is the second reference path of the target GOOSE outgoing message.

[0014] Optionally, if the comparison result indicates that the target GOOSE incoming message and the target GOOSE outgoing message do not satisfy the mapping relationship, an alarm signal is issued, including at least one of the following: if the first comparison result indicates that the number of message frames received by the device under verification within the predetermined time period after sending the target GOOSE incoming message is less than the predetermined number, the alarm signal is issued; if the second comparison result indicates that the first device instantiation name of the target GOOSE incoming message is different from the second device instantiation name of the target GOOSE outgoing message, the alarm signal is issued; if the third comparison result indicates that the first reference path of the target GOOSE incoming message and the second reference path of the target GOOSE outgoing message are different, the alarm signal is issued.

[0015] According to another aspect of the present invention, an automated verification device for GOOSE messages is also provided, comprising: an import unit, configured to import a configuration file of a device to be verified, wherein the device to be verified refers to a device that needs to convert the format of GOOSE messages during the intelligent transformation of a substation, the GOOSE message refers to a specific type of message used in the substation for transmitting critical event information, and the configuration file contains configuration information of the device to be verified; a determination unit, configured to determine, based on the configuration file, a mapping relationship between GOOSE incoming messages and GOOSE outgoing messages of the device to be verified, wherein the GOOSE incoming messages refer to the GOOSE messages sent to the device to be verified, and the GOOSE outgoing messages refer to the GOOSE messages received from the device to be verified; and a sending unit, configured to send a target GOOSE incoming message... The message is sent to the device to be verified, so that the device to be verified can perform format conversion on the target GOOSE input message. The target GOOSE input message is used to verify the accuracy of the format conversion performed by the device to be verified. After converting the target GOOSE input message, the device to be verified outputs a target GOOSE output message corresponding to the target GOOSE input message. A receiving unit is used to receive the target GOOSE output message sent by the device to be verified. A comparison unit is used to compare the correspondence between the target GOOSE input message and the target GOOSE output message with the mapping relationship to obtain a comparison result. An early warning unit is used to issue an alarm signal if the comparison result indicates that the target GOOSE input message and the target GOOSE output message do not satisfy the mapping relationship.

[0016] Optionally, the import unit includes: a first import module, configured to import the process layer configuration file of the device to be verified, wherein the process layer configuration file is used to determine the GOOSE inbound message information of the GOOSE inbound messages subscribed to by the device to be verified, the reference paths of the GOOSE inbound messages and the GOOSE outbound messages; and a second import module, configured to import the internal configuration file of the device to be verified, wherein the internal configuration file is used to determine the mapping relationship between the GOOSE inbound messages and the GOOSE outbound messages.

[0017] Optionally, the mapping relationship includes: a first mapping relationship and a second mapping relationship. The determining unit includes: a first determining module, configured to determine the first mapping relationship between a new GOOSE inbound message and an old GOOSE outbound message based on the configuration file, wherein the new GOOSE inbound message refers to a GOOSE inbound message with the same message format as a specific message format, and the old GOOSE outbound message refers to a GOOSE outbound message with a different message format than the specific message format, and the specific message format refers to a message format conforming to a specific standard; and a second determining module, configured to determine the second mapping relationship between the old GOOSE inbound message and the new GOOSE outbound message based on the configuration file, wherein the old GOOSE inbound message refers to a GOOSE inbound message with a different message format than the specific message format, and the new GOOSE outbound message refers to a GOOSE outbound message with the same message format as the specific message format.

[0018] Optionally, the target GOOSE incoming message includes: a target new GOOSE incoming message and a target old GOOSE incoming message; the target GOOSE outgoing message includes: a target new GOOSE outgoing message and a target old GOOSE outgoing message; the sending unit includes: a first sending module, configured to send the target new GOOSE incoming message to the device to be verified, so that the device to be verified performs format conversion on the target new GOOSE incoming message, wherein the device to be verified performs format conversion on the target new GOOSE incoming message. After format conversion of the GOOSE incoming message, the target old GOOSE outgoing message corresponding to the target new GOOSE incoming message is output; the second sending module is used to send the target old GOOSE incoming message to the device to be verified, so that the device to be verified performs format conversion on the target new GOOSE incoming message, wherein the device to be verified outputs the target new GOOSE outgoing message corresponding to the target old GOOSE incoming message after format conversion.

[0019] Optionally, the comparison unit includes at least one of the following: a first acquisition module, configured to acquire the number of message frames received within a predetermined time period after sending the target GOOSE inbound message to the device to be verified; a second acquisition module, configured to compare the number of message frames with a predetermined number to obtain a first comparison result; a third acquisition module, configured to acquire the first device instantiation name of the target GOOSE inbound message and the second device instantiation name of the target GOOSE outbound message, wherein the first device instantiation name and the second device instantiation name respectively refer to the unique identifiers of the target GOOSE inbound message and the target GOOSE outbound message in the substation; a fourth acquisition module, configured to compare the first device instantiation name and the second device instantiation name to obtain a second comparison result; a fifth acquisition module, configured to acquire the first reference path of the target GOOSE inbound message and the second reference path of the target GOOSE outbound message, wherein the first reference path and the second reference path are reference paths obtained according to the configuration file; and a sixth acquisition module, configured to compare the first reference path and the second reference path to obtain a third comparison result.

[0020] Optionally, the fifth acquisition module includes: a first determining submodule, configured to, upon receiving the target GOOSE output message sent by the device to be verified, determine a data member in the target GOOSE output message whose state has changed as a target data member, wherein the state change occurs when arbitrarily selecting one of the data members from the dataset corresponding to the target GOOSE input message for state update during the process of sending the target GOOSE input message to the device to be verified; an acquisition submodule, configured to acquire the target reference path of the target data member; and a second determining submodule, configured to determine that the target reference path is the second reference path of the target GOOSE output message.

[0021] Optionally, the early warning unit includes at least one of the following: a first early warning module, configured to issue an alarm signal when the first comparison result indicates that the number of message frames received by the device to be verified within the predetermined time period after sending the target GOOSE inbound message is less than the predetermined number; a second early warning module, configured to issue the alarm signal when the second comparison result indicates that the first device instantiation name of the target GOOSE inbound message is different from the second device instantiation name of the target GOOSE outbound message; and a third early warning module, configured to issue the alarm signal when the third comparison result indicates that the first reference path of the target GOOSE inbound message is different from the second reference path of the target GOOSE outbound message.

[0022] According to another aspect of the present invention, an automated verification system for GOOSE messages is also provided, wherein the automated verification system for GOOSE messages uses any of the above-described automated verification methods for GOOSE messages.

[0023] According to another aspect of the present invention, a computer-readable storage medium is also provided, the computer-readable storage medium including a stored program, wherein the program executes any of the above-described automated verification methods for GOOSE messages.

[0024] According to another aspect of the present invention, a processor is also provided, the processor being configured to run a program, wherein the program, when running, executes any of the above-described automated verification methods for GOOSE messages.

[0025] According to another aspect of the present invention, a computer program product is also provided, including computer instructions, which, when executed by a processor, perform any of the above-described automated verification methods for GOOSE messages.

[0026] In this embodiment of the invention, a configuration file of the device to be verified is imported. The device to be verified refers to a device that requires format conversion of GOOSE messages during the intelligent transformation of a substation. A GOOSE message is a specific type of message used in a substation to transmit critical event information. The configuration file contains the configuration information of the device to be verified. Based on the configuration file, a mapping relationship between GOOSE incoming messages and GOOSE outgoing messages of the device to be verified is determined. An incoming GOOSE message refers to a GOOSE message sent to the device to be verified, and an outgoing GOOSE message refers to a GOOSE message received from the device to be verified. A target incoming GOOSE message is then sent to the device to be verified. The device under test performs format conversion on the target GOOSE input message. The target GOOSE input message is used to verify the accuracy of the format conversion performed by the device under test. After format conversion, the device under test outputs a target GOOSE output message corresponding to the target GOOSE input message. The device under test also receives the target GOOSE output message sent by the device under test. The correspondence and mapping relationship between the target GOOSE input message and the target GOOSE output message are compared to obtain a comparison result. If the comparison result indicates that the target GOOSE input message and the target GOOSE output message do not satisfy the mapping relationship, an alarm signal is issued. The above technical solution achieves the goal of verifying whether the GOOSE inbound and outbound messages satisfy the mapping relationship by first importing the configuration file of the device to be verified into the verification device, then sending GOOSE inbound messages to the device to be verified and receiving GOOSE outbound messages obtained by format conversion from the device to be verified. This realizes the technical effect of using the verification device to perform consistency verification of the GOOSE messages received and sent by the device to be verified, improving verification efficiency and accuracy. It also solves the technical problem of large workload, easy error and low efficiency caused by using manual verification to perform consistency verification of received and sent GOOSE messages in related technologies. Attached Figure Description

[0027] The accompanying drawings, which are included to provide a further understanding of the invention and form part of this application, illustrate exemplary embodiments of the invention and, together with their description, serve to explain the invention and do not constitute an undue limitation thereof. In the drawings:

[0028] Figure 1 This is a hardware structure block diagram of a mobile terminal for an automated verification method for GOOSE messages according to an embodiment of the present invention.

[0029] Figure 2 This is a flowchart of an automated verification method for GOOSE messages according to an embodiment of the present invention;

[0030] Figure 3 This is a flowchart of an optional automated verification method for GOOSE messages according to an embodiment of the present invention;

[0031] Figure 4 This is a schematic diagram of the automated verification process of GOOSE messages according to an embodiment of the present invention;

[0032] Figure 5 This is a schematic diagram of an automated verification device for GOOSE messages according to an embodiment of the present invention. Detailed Implementation

[0033] To enable those skilled in the art to better understand the present invention, the technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings of the embodiments of the present invention. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort should fall within the scope of protection of the present invention.

[0034] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this invention are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of the invention described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover a non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0035] As described in the background section, related technologies employ manual verification to check the consistency of received and sent GOOSE messages, which results in a large workload, is prone to errors, and has low efficiency. To address these shortcomings, embodiments of the present invention provide an automated method and apparatus for verifying GOOSE messages.

[0036] The technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention.

[0037] The methods and embodiments provided in this invention can be executed on a mobile terminal, a computer terminal, or a similar computing device. Taking running on a mobile terminal as an example, Figure 1This is a hardware structure block diagram of a mobile terminal for an automated verification method of GOOSE messages according to an embodiment of the present invention. Figure 1 As shown, a mobile terminal may include one or more ( Figure 1 Only one is shown in the diagram. A processor 102 (which may include, but is not limited to, a microprocessor MCU or a programmable logic device FPGA, etc.) and a memory 104 for storing data are also shown. The mobile terminal may further include a transmission device 106 for communication functions and an input / output device 108. Those skilled in the art will understand that... Figure 1 The structure shown is for illustrative purposes only and does not limit the structure of the mobile terminal described above. For example, the mobile terminal may also include components that are more... Figure 1 The more or fewer components shown, or having the same Figure 1 The different configurations shown.

[0038] The memory 104 can be used to store computer programs, such as application software programs and modules, like the computer program corresponding to the automated verification method for GOOSE messages in this embodiment of the invention. The processor 102 executes various functional applications and data processing by running the computer program stored in the memory 104, thereby implementing the above-described method. The memory 104 may include high-speed random access memory and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory 104 may further include memory remotely located relative to the processor 102, and these remote memories can be connected to the mobile terminal via a network. Examples of the aforementioned networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof. The transmission device 106 is used to receive or send data via a network. Specific examples of the aforementioned networks may include wireless networks provided by the mobile terminal's communication provider. In one example, the transmission device 106 includes a Network Interface Controller (NIC), which can be connected to other network devices via a base station to communicate with the Internet. In one example, the transmission device 106 may be a radio frequency (RF) module, which is used to communicate with the Internet wirelessly.

[0039] According to an embodiment of the present invention, an embodiment of an automated verification method for GOOSE messages is provided. It should be noted that the steps shown in the flowchart in the accompanying drawings can be executed in a computer system such as a set of computer-executable instructions. Furthermore, although a logical order is shown in the flowchart, in some cases, the steps shown or described may be executed in a different order than that shown here.

[0040] Figure 2 This is a flowchart of an automated verification method for GOOSE messages according to an embodiment of the present invention, such as... Figure 2 As shown, the method includes the following steps:

[0041] Step S202: Import the configuration file of the device to be verified. The device to be verified refers to the device that needs to convert the format of GOOSE messages during the intelligent transformation of the substation. GOOSE messages refer to a specific type of message used in the substation to transmit information about critical events. The configuration file contains the configuration information of the device to be verified.

[0042] In this embodiment, a verification device with automated analysis and verification capabilities can be used to verify a device with verification capabilities, such as an interface conversion device, to verify whether the received GOOSE messages correspond correctly to the sent GOOSE messages. First, the verification device can import the configuration file of the device to be verified to lay the data foundation for the subsequent verification process.

[0043] According to the above embodiments of the present invention, in step S202, importing the configuration file of the device to be verified includes: importing the process layer configuration file of the device to be verified, wherein the process layer configuration file is used to determine the GOOSE incoming message information, the reference path of the GOOSE incoming message and the GOOSE outgoing message of the GOOSE incoming message subscribed to by the device to be verified; and importing the internal configuration file of the device to be verified, wherein the internal configuration file is used to determine the mapping relationship between the GOOSE incoming message and the GOOSE outgoing message.

[0044] Specifically, the verification device can import the process layer configuration file of the device to be verified, so as to obtain the reference paths of the new and old message format GOOSE incoming messages subscribed to by the device to be verified, as well as the new and old message format GOOSE outgoing messages sent by the device to be verified, based on the process layer configuration file; the verification device can also import the internal configuration file of the device to be verified, so as to obtain the correspondence between the old message format GOOSE incoming messages subscribed to by the device to be verified and the new message format GOOSE outgoing messages sent by the device to be verified, as well as the correspondence between the new message format GOOSE incoming messages subscribed to by the device to be verified and the old message format GOOSE outgoing messages sent by the device to be verified, based on the internal configuration file.

[0045] It should be noted that the aforementioned new message format GOOSE incoming message refers to the new GOOSE incoming message in the embodiments of the present invention, the aforementioned old message format GOOSE incoming message refers to the old GOOSE incoming message in the embodiments of the present invention, the aforementioned new message format GOOSE outgoing message refers to the new GOOSE outgoing message in the embodiments of the present invention, and the aforementioned old message format GOOSE outgoing message refers to the old GOOSE outgoing message in the embodiments of the present invention.

[0046] Step S204: Determine the mapping relationship between GOOSE incoming messages and GOOSE outgoing messages of the device to be verified based on the configuration file. Here, GOOSE incoming messages refer to GOOSE messages sent to the device to be verified, and GOOSE outgoing messages refer to GOOSE messages received from the device to be verified.

[0047] Optionally, the above mapping relationship includes: a first mapping relationship and a second mapping relationship. The first mapping relationship refers to the mapping relationship between new GOOSE incoming messages and old GOOSE outgoing messages, and the second mapping relationship refers to the mapping relationship between old GOOSE incoming messages and new GOOSE outgoing messages.

[0048] In this embodiment, the verification device can determine the correspondence between the GOOSE incoming messages and GOOSE outgoing messages subscribed to by the device to be verified based on the imported configuration file.

[0049] It should be noted that GOOSE incoming messages refer to GOOSE messages sent by the verification device to the device under verification, i.e., GOOSE messages received by the device under verification, while GOOSE outgoing messages refer to GOOSE messages received by the verification device from the device under verification, i.e., GOOSE messages sent by the device under verification.

[0050] According to the above embodiments of the present invention, in step S204, determining the mapping relationship between GOOSE input messages and GOOSE output messages of the device to be verified based on the configuration file includes: determining a first mapping relationship between new GOOSE input messages and old GOOSE output messages based on the configuration file, wherein a new GOOSE input message refers to a GOOSE input message with the same message format as a specific message format, and an old GOOSE output message refers to a GOOSE output message with a different message format than the specific message format, where the specific message format refers to a message format conforming to a specific standard; and determining a second mapping relationship between old GOOSE input messages and new GOOSE output messages based on the configuration file, wherein an old GOOSE input message refers to a GOOSE input message with a different message format than the specific message format, and a new GOOSE output message refers to a GOOSE output message with the same message format as the specific message format.

[0051] Optionally, the specific standard mentioned above refers to the IEC 61805 standard.

[0052] Specifically, based on the internal configuration file of the device to be verified imported into the verification device, the correspondence between the old message format GOOSE incoming messages subscribed to by the device to be verified and the new message format GOOSE outgoing messages sent can be obtained, that is, the first mapping relationship between the new GOOSE incoming messages and the old GOOSE outgoing messages; and the correspondence between the new message format GOOSE incoming messages subscribed to by the device to be verified and the old message format GOOSE outgoing messages sent, that is, the second mapping relationship between the old GOOSE incoming messages and the new GOOSE outgoing messages.

[0053] Step S206: The target GOOSE input message is sent to the device to be verified so that the device to be verified can perform format conversion on the target GOOSE input message. The target GOOSE input message is used to verify the accuracy of the format conversion performed by the device to be verified. After performing format conversion on the target GOOSE input message, the device to be verified outputs the target GOOSE output message corresponding to the target GOOSE input message.

[0054] Optionally, the target GOOSE incoming messages mentioned above include: target new GOOSE incoming messages and target old GOOSE incoming messages.

[0055] Optionally, the target GOOSE output message mentioned above includes: target new GOOSE output message and target old GOOSE output message.

[0056] In this embodiment, the verification device can sequentially send the target GOOSE input message to the device to be verified. After receiving the target GOOSE input message, the device to be verified will convert its format to obtain the target GOOSE output message corresponding to the target GOOSE input message.

[0057] It should be noted that the target GOOSE inbound message and target GOOSE outbound message here refer to the messages used to verify the accuracy of the format conversion of the device to be verified. In essence, they are the GOOSE inbound messages subscribed to by the device to be verified and the GOOSE outbound messages obtained by the device to be verified after converting the GOOSE inbound messages. The distinction is made here only to indicate the verification process.

[0058] The following is combined Figure 3 and Figure 4 The embodiments of the present invention will be described in detail below. Figure 3 This is a flowchart of an optional automated verification method for GOOSE messages according to an embodiment of the present invention. Figure 4 This is a schematic diagram of the automated verification process of GOOSE messages according to an embodiment of the present invention.

[0059] According to the above embodiments of the present invention, in step S206, sending the target GOOSE input message to the device to be verified, so that the device to be verified performs format conversion on the target GOOSE input message, includes: sending the target new GOOSE input message to the device to be verified, so that the device to be verified performs format conversion on the target new GOOSE input message, wherein, after performing format conversion on the target new GOOSE input message, the device to be verified outputs the target old GOOSE output message corresponding to the target new GOOSE input message; and sending the target old GOOSE input message to the device to be verified, so that the device to be verified performs format conversion on the target new GOOSE input message, wherein, after performing format conversion on the target old GOOSE input message, the device to be verified outputs the target new GOOSE output message corresponding to the target old GOOSE input message.

[0060] Specifically, as above Figure 3 As shown and above Figure 4 As shown, the verification device can sequentially send the target old GOOSE input message to the device under verification. Upon receiving the target old GOOSE input message, the device under verification will convert its format to obtain the target new GOOSE output message corresponding to the target old GOOSE input message. Alternatively, the verification device can sequentially send the target new GOOSE input message to the device under verification. Upon receiving the target new GOOSE input message, the device under verification will convert its format to obtain the target old GOOSE output message corresponding to the target new GOOSE input message. This two-way verification allows for a more comprehensive verification of the accuracy of the device under verification.

[0061] It should be noted that, Figure 3 The non-standard GOOSE message shown refers to the old message format GOOSE message in the embodiments of this invention; the standard message refers to the new message format GOOSE message in the embodiments of this invention; the standard GOOSE message here refers to the GOOSE message that conforms to the IEC 61805 standard, and the non-standard GOOSE message here refers to the GOOSE message that does not fully conform to the IEC 61805 standard.

[0062] Step S208: Receive the target GOOSE output message sent by the device to be verified.

[0063] As above Figure 3As shown, the verification device can receive the target GOOSE input message from the device to be verified, convert the format to obtain the target GOOSE output message corresponding to the target GOOSE input message, and can also parse the received target GOOSE output message to obtain the IEDNAME (Intelligent Electronic Device NAME) and reference path of the target GOOSE output message, so as to facilitate the subsequent verification of the consistency of the device to be verified.

[0064] Step S210: Compare the correspondence and mapping relationship between the target GOOSE incoming messages and the target GOOSE outgoing messages to obtain the comparison result.

[0065] In this embodiment, the consistency of the target GOOSE incoming message and the target GOOSE outgoing message can be verified from multiple perspectives, and the mapping relationship obtained in the above steps can be compared to obtain the comparison result.

[0066] According to the above embodiments of the present invention, in step S210, the correspondence and mapping relationship between the target GOOSE incoming message and the target GOOSE outgoing message are compared to obtain a comparison result, including at least one of the following: obtaining the number of message frames received within a predetermined time period after sending the target GOOSE incoming message to the device to be verified; comparing the number of message frames with the predetermined number to obtain a first comparison result; obtaining the first device instantiation name of the target GOOSE incoming message and the second device instantiation name of the target GOOSE outgoing message, wherein the first device instantiation name and the second device instantiation name refer to the unique identifiers of the target GOOSE incoming message and the target GOOSE outgoing message in the substation, respectively; comparing the first device instantiation name and the second device instantiation name to obtain a second comparison result; obtaining the first reference path of the target GOOSE incoming message and the second reference path of the target GOOSE outgoing message, wherein the first reference path and the second reference path are reference paths obtained according to the configuration file; comparing the first reference path and the second reference path to obtain a third comparison result.

[0067] Specifically, as above Figure 3As shown, the number of message frames received by the verification device within a predetermined time period after sending the target GOOSE inbound message to the device to be verified can be obtained, and then compared with the predetermined number to obtain the first comparison result; the received target GOOSE outbound message can be parsed to obtain the IEDNAME (i.e., device instantiation name) and reference path of the target GOOSE outbound message, and then compared with the IEDNAME (i.e., device instantiation name) and reference path of the target GOOSE inbound message sent by the verification device to obtain the second comparison result and the third comparison result; of course, the mapping relationship between the target GOOSE inbound message sent by the verification device and the target GOOSE outbound message can be determined by comparing whether the APPID (Application Identifier, an identifier field used to uniquely identify a specific GOOSE communication instance) of the target GOOSE inbound message and the target GOOSE outbound message are the same, and whether there are changes in GOOSE messages on other links.

[0068] In the above embodiments of the present invention, obtaining the second reference path of the target GOOSE outgoing message includes: upon receiving the target GOOSE outgoing message sent by the device to be verified, determining that the data member in the target GOOSE outgoing message whose state has changed is the target data member, wherein the state change occurs when arbitrarily selecting a data member from the dataset corresponding to the target GOOSE incoming message for state update during the process of sending the target GOOSE incoming message to the device to be verified; obtaining the target reference path of the target data member; and determining the target reference path as the second reference path of the target GOOSE outgoing message.

[0069] Specifically, during the process of the verification device sending the target GOOSE inbound message to the device to be verified, a data member is arbitrarily selected from the dataset corresponding to the target GOOSE inbound message for status update, so that its status changes. In this way, when the verification device receives the target GOOSE outbound message from the device to be verified later, it can compare the reference path of the data member whose status has changed with the reference path of the target GOOSE inbound message sent by the verification device to the device to be verified, so as to obtain the corresponding comparison result.

[0070] Step S212: If the comparison result indicates that the target GOOSE incoming message and the target GOOSE outgoing message do not satisfy the mapping relationship, an alarm signal is issued.

[0071] In this embodiment, the comparison results obtained from the above steps can be used to determine whether the target GOOSE incoming message and the target GOOSE outgoing message satisfy the mapping relationship.

[0072] According to the above embodiments of the present invention, in step S212, when the comparison result indicates that the target GOOSE incoming message and the target GOOSE outgoing message do not satisfy the mapping relationship, an alarm signal is issued, including at least one of the following: when the first comparison result indicates that the number of message frames received by the device to be verified within a predetermined period after sending the target GOOSE incoming message is less than a predetermined number, an alarm signal is issued; when the second comparison result indicates that the first device instantiation name of the target GOOSE incoming message is different from the second device instantiation name of the target GOOSE outgoing message, an alarm signal is issued; when the third comparison result indicates that the first reference path of the target GOOSE incoming message and the second reference path of the target GOOSE outgoing message are different, an alarm signal is issued.

[0073] Specifically, as above Figure 3 As shown, if the number of message frames received by the verification device within a predetermined time period after sending the target GOOSE inbound message to the device under verification is not less than a predetermined number, it is considered that the consistency and accuracy of the format conversion performed by the device under verification are high. If the number of message frames received by the device under verification within a predetermined time period after sending the target GOOSE inbound message is less than the predetermined number, it is considered that its consistency and accuracy are poor, and an alarm signal can be issued to warn of this. For example, if the verification device receives N (N≥4) GOOSE outbound messages within 30ms after sending one GOOSE inbound message, it can be considered that the consistency and accuracy of the format conversion performed by the device under verification are high; otherwise, it is considered that its consistency and accuracy are poor, and an alarm signal can be issued to warn of this. If the APPID of the target GOOSE inbound message and the target GOOSE outbound message are the same, it is considered that the consistency and accuracy of the format conversion performed by the device under verification are high; otherwise, it is considered that its consistency and accuracy are poor, and an alarm signal can be issued to warn of this. If the I of the target GOOSE inbound message and the target GOOSE outbound message are the same, it is considered that the consistency and accuracy of the format conversion performed by the device under verification are high; otherwise, it is considered that its consistency and accuracy are poor, and an alarm signal can be issued to warn of this. If both the EDNAME and the reference path are the same, the device under verification is considered to have high consistency and accuracy in format conversion. Conversely, if they are different, the consistency and accuracy are considered to be poor, and an alarm signal can be issued to warn the user. In addition, if the GOOSE messages of other links change, the consistency and accuracy of the device under verification are considered to be poor, and an alarm signal should be issued to warn the user. Conversely, if they are different, the consistency and accuracy are considered to be high.

[0074] As described above, according to the technical solution provided by the above embodiments of the present invention, a configuration file of the device to be verified can be imported. The device to be verified refers to a device that needs to convert the format of GOOSE messages during the intelligent transformation of a substation. A GOOSE message refers to a specific type of message used in a substation to transmit information about critical events. The configuration file contains the configuration information of the device to be verified. Based on the configuration file, the mapping relationship between the GOOSE incoming messages and GOOSE outgoing messages of the device to be verified is determined. The GOOSE incoming message refers to the GOOSE message sent to the device to be verified, and the GOOSE outgoing message refers to the message received from the device to be verified. The process involves: receiving a GOOSE message; sending a target GOOSE input message to the device under test, enabling the device to perform format conversion on the target GOOSE input message, whereby the target GOOSE input message is used to verify the accuracy of the format conversion performed by the device under test; the device under test outputting a target GOOSE output message corresponding to the target GOOSE input message after format conversion; receiving the target GOOSE output message sent by the device under test; and comparing the correspondence and mapping relationship between the target GOOSE input message and the target GOOSE output message to obtain the comparison result. If the comparison result indicates that the target GOOSE incoming message and the target GOOSE outgoing message do not satisfy the mapping relationship, an alarm signal is issued. This achieves the purpose of message verification by first importing the configuration file of the device under test into the verification device to obtain the mapping relationship of GOOSE incoming and outgoing messages in the device under test, then using the verification device to send GOOSE incoming messages to the device under test and receiving the GOOSE outgoing messages obtained by format conversion from the device under test, in order to verify whether the GOOSE incoming and outgoing messages satisfy the mapping relationship. This realizes the use of the verification device to verify the GOOSE messages received and sent by the device under test. The technical effect of performing consistency verification is to improve verification efficiency and accuracy. It achieves the goal of verifying whether the GOOSE input and output messages in the device under test are satisfied by first importing the configuration file of the device under test into the verification device, then sending GOOSE input messages to the device under test using the verification device, and receiving GOOSE output messages obtained by format conversion from the device under test. This realizes the technical effect of using the verification device to perform consistency verification on the GOOSE messages received and sent by the device under test, thus improving verification efficiency and accuracy.

[0075] Therefore, the technical solution provided by the above embodiments of the present invention solves the technical problem in the related art that the manual verification method is used to perform consistency verification on received and sent GOOSE messages, which results in a large workload, is prone to errors, and has low efficiency.

[0076] It should be noted that, for the sake of simplicity, the foregoing method embodiments are all described as a series of actions. However, those skilled in the art should understand that this application is not limited to the described order of actions, as some steps may be performed in other orders or simultaneously according to this application. Furthermore, those skilled in the art should also understand that the embodiments described in the specification are preferred embodiments, and the actions and modules involved are not necessarily essential to this application.

[0077] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods according to the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) and includes several instructions to cause a terminal device (which may be a mobile phone, computer, server, or network device, etc.) to execute the methods described in the various embodiments of this application.

[0078] According to embodiments of the present invention, an automated verification apparatus for GOOSE messages is also provided for implementing the above-described automated verification method for GOOSE messages. Figure 5 This is a schematic diagram of an automated verification device for GOOSE messages according to an embodiment of the present invention, as shown below. Figure 5 As shown, the device includes: an import unit 501, a determination unit 503, a sending unit 505, a receiving unit 507, a comparison unit 509, and an early warning unit 511. The automated verification device for this GOOSE message will be described in detail below.

[0079] Import unit 501 is used to import the configuration file of the device to be verified. The device to be verified refers to the device that needs to convert the format of GOOSE messages during the intelligent transformation of the substation. GOOSE messages refer to a specific type of message used in the substation to transmit key event information. The configuration file contains the configuration information of the device to be verified.

[0080] The determining unit 503 is used to determine the mapping relationship between the GOOSE incoming messages and the GOOSE outgoing messages of the device to be verified based on the configuration file. The GOOSE incoming messages refer to the GOOSE messages sent to the device to be verified, and the GOOSE outgoing messages refer to the GOOSE messages received from the device to be verified.

[0081] The sending unit 505 is used to send the target GOOSE input message to the device to be verified, so that the device to be verified can perform format conversion on the target GOOSE input message. The target GOOSE input message is used to verify the accuracy of the format conversion performed by the device to be verified. After performing format conversion on the target GOOSE input message, the device to be verified outputs the target GOOSE output message corresponding to the target GOOSE input message.

[0082] The receiving unit 507 is used to receive the target GOOSE output message sent by the device to be verified.

[0083] The comparison unit 509 is used to compare the correspondence and mapping relationship between the target GOOSE incoming message and the target GOOSE outgoing message to obtain the comparison result.

[0084] The early warning unit 511 is used to issue an alarm signal when the comparison result indicates that the target GOOSE incoming message and the target GOOSE outgoing message do not satisfy the mapping relationship.

[0085] It should be noted that the above-mentioned import unit 501, determination unit 503, sending unit 505, receiving unit 507, comparison unit 509 and warning unit 511 correspond to steps S202 to S212 in the above embodiments. The six units and the corresponding steps implement the same instances and application scenarios, but are not limited to the content disclosed in the above embodiments.

[0086] As can be seen from the above, in the scheme described in the above embodiments of the present invention, the configuration file of the device to be verified can be imported using the import unit. The device to be verified refers to a device that needs to convert the format of GOOSE messages during the intelligent transformation of a substation. A GOOSE message refers to a specific type of message used in the substation to transmit information about critical events. The configuration file contains the configuration information of the device to be verified. Then, the determining unit determines the mapping relationship between the GOOSE input messages and GOOSE output messages of the device to be verified based on the configuration file. The GOOSE input message refers to the GOOSE message sent to the device to be verified, and the GOOSE output message refers to the GOOSE message received from the device to be verified. Next, the sending unit sends the target GOOSE input message to the device to be verified, so that the device to be verified performs format conversion on the target GOOSE input message. The target GOOSE input message is used to verify the accuracy of the format conversion performed by the device to be verified. After performing format conversion on the target GOOSE input message, the device to be verified outputs a message that matches the target GOOSE input message. The system first receives the target GOOSE output message corresponding to the OOSE input message; then, the receiving unit receives the target GOOSE output message sent by the device under test; next, the comparison unit compares the correspondence and mapping relationship between the target GOOSE input message and the target GOOSE output message to obtain the comparison result; finally, the early warning unit issues an alarm signal if the comparison result indicates that the target GOOSE input message and the target GOOSE output message do not satisfy the mapping relationship. This achieves the purpose of message verification by first importing the configuration file of the device under test into the verification device to obtain the mapping relationship of the GOOSE input and output messages in the device under test, then using the verification device to send GOOSE input messages to the device under test and receiving the GOOSE output messages obtained by the device under test after format conversion, to verify whether the GOOSE input message and the GOOSE output message satisfy the mapping relationship. This achieves the technical effect of using the verification device to perform consistency verification of the GOOSE messages received and sent by the device under test, improving verification efficiency and accuracy.

[0087] Therefore, the technical solution provided by the above embodiments of the present invention solves the technical problem in the related art that the manual verification method is used to perform consistency verification on received and sent GOOSE messages, which results in a large workload, is prone to errors, and has low efficiency.

[0088] Optionally, the import unit includes: a first import module, used to import the process layer configuration file of the device to be verified, wherein the process layer configuration file is used to determine the GOOSE incoming message information, the reference paths of the GOOSE incoming messages and the GOOSE outgoing messages subscribed to by the device to be verified; and a second import module, used to import the internal configuration file of the device to be verified, wherein the internal configuration file is used to determine the mapping relationship between the GOOSE incoming messages and the GOOSE outgoing messages.

[0089] Optionally, the mapping relationship includes: a first mapping relationship and a second mapping relationship. The determining unit includes: a first determining module, used to determine the first mapping relationship between new GOOSE incoming messages and old GOOSE outgoing messages based on a configuration file, wherein a new GOOSE incoming message refers to a GOOSE incoming message with the same message format as a specific message format, and an old GOOSE outgoing message refers to a GOOSE outgoing message with a different message format than the specific message format, and the specific message format refers to a message format conforming to a specific standard; and a second determining module, used to determine the second mapping relationship between old GOOSE incoming messages and new GOOSE outgoing messages based on a configuration file, wherein an old GOOSE incoming message refers to a GOOSE incoming message with a different message format than the specific message format, and a new GOOSE outgoing message refers to a GOOSE outgoing message with the same message format as the specific message format.

[0090] Optionally, the target GOOSE incoming message includes a target new GOOSE incoming message and a target old GOOSE incoming message, and the target GOOSE outgoing message includes a target new GOOSE outgoing message and a target old GOOSE outgoing message. The sending unit includes: a first sending module, used to send the target new GOOSE incoming message to the device to be verified, so that the device to be verified can perform format conversion on the target new GOOSE incoming message, wherein the device to be verified outputs the target old GOOSE outgoing message corresponding to the target new GOOSE incoming message after performing format conversion on the target new GOOSE incoming message; and a second sending module, used to send the target old GOOSE incoming message to the device to be verified, so that the device to be verified can perform format conversion on the target new GOOSE incoming message, wherein the device to be verified outputs the target new GOOSE outgoing message corresponding to the target old GOOSE incoming message after performing format conversion on the target old GOOSE incoming message.

[0091] Optionally, the comparison unit includes at least one of the following: a first acquisition module, used to acquire the number of message frames received within a predetermined time period after sending a target GOOSE inbound message to the device to be verified; a second acquisition module, used to compare the number of message frames with a predetermined number to obtain a first comparison result; a third acquisition module, used to acquire the first device instantiation name of the target GOOSE inbound message and the second device instantiation name of the target GOOSE outbound message, wherein the first device instantiation name and the second device instantiation name refer to the unique identifiers of the target GOOSE inbound message and the target GOOSE outbound message in the substation, respectively; a fourth acquisition module, used to compare the first device instantiation name and the second device instantiation name to obtain a second comparison result; a fifth acquisition module, used to acquire the first reference path of the target GOOSE inbound message and the second reference path of the target GOOSE outbound message, wherein the first reference path and the second reference path are reference paths obtained according to the configuration file; and a sixth acquisition module, used to compare the first reference path and the second reference path to obtain a third comparison result.

[0092] Optionally, the fifth acquisition module includes: a first determining submodule, used to determine, upon receiving a target GOOSE output message sent by the device to be verified, a data member in the target GOOSE output message whose state has changed as a target data member, wherein the state change occurs when arbitrarily selecting a data member from the dataset corresponding to the target GOOSE input message for state update during the process of sending the target GOOSE input message to the device to be verified; an acquisition submodule, used to acquire the target reference path of the target data member; and a second determining submodule, used to determine that the target reference path is the second reference path of the target GOOSE output message.

[0093] Optionally, the early warning unit includes at least one of the following: a first early warning module, configured to issue an alarm signal when the first comparison result indicates that the number of message frames received by the device to be verified within a predetermined period after sending the target GOOSE inbound message is less than a predetermined number; a second early warning module, configured to issue an alarm signal when the second comparison result indicates that the first device instantiation name of the target GOOSE inbound message is different from the second device instantiation name of the target GOOSE outbound message; and a third early warning module, configured to issue an alarm signal when the third comparison result indicates that the first reference path of the target GOOSE inbound message is different from the second reference path of the target GOOSE outbound message.

[0094] According to another aspect of the present invention, an automated verification system for GOOSE messages is also provided, which uses any of the above-described automated verification methods for GOOSE messages.

[0095] According to another aspect of the present invention, a computer-readable storage medium is also provided, the computer-readable storage medium including a stored program, wherein the program executes the automated verification method for GOOSE messages described above.

[0096] Optionally, in this embodiment, the computer-readable storage medium may be located in any computer terminal in a group of computer terminals in a computer network, or in any communication device in a group of communication devices.

[0097] Optionally, in this embodiment, the computer-readable storage medium is configured to store program code for performing the following steps: importing the configuration file of the device to be verified, wherein the device to be verified refers to the device that needs to convert the format of GOOSE messages during the intelligent transformation of the substation, and the GOOSE message refers to a specific type of message used in the substation to transmit key event information, and the configuration file contains the configuration information of the device to be verified; determining the mapping relationship between the GOOSE incoming messages and GOOSE outgoing messages of the device to be verified based on the configuration file, wherein the GOOSE incoming messages refer to the GOOSE messages sent to the device to be verified, and the GOOSE outgoing messages refer to the GOOSE messages received from the device to be verified; and setting the target GOOSE... The SE input message is sent to the device under test, enabling the device to perform format conversion on the target GOOSE input message. The target GOOSE input message is used to verify the accuracy of the format conversion performed by the device under test. After converting the target GOOSE input message, the device under test outputs a target GOOSE output message corresponding to the target GOOSE input message. The device also receives the target GOOSE output message sent by the device under test; compares the correspondence and mapping relationship between the target GOOSE input message and the target GOOSE output message to obtain a comparison result; and issues an alarm signal if the comparison result indicates that the target GOOSE input message and the target GOOSE output message do not satisfy the mapping relationship.

[0098] Optionally, in this embodiment, the computer-readable storage medium is configured to store program code for performing the following steps: importing the process layer configuration file of the device to be verified, wherein the process layer configuration file is used to determine the GOOSE incoming message information, the reference paths of the GOOSE incoming messages and the GOOSE outgoing messages subscribed to by the device to be verified; and importing the internal configuration file of the device to be verified, wherein the internal configuration file is used to determine the mapping relationship between the GOOSE incoming messages and the GOOSE outgoing messages.

[0099] Optionally, in this embodiment, the computer-readable storage medium is configured to store program code for performing the following steps: determining a first mapping relationship between new GOOSE incoming messages and old GOOSE outgoing messages based on a configuration file, wherein a new GOOSE incoming message refers to a GOOSE incoming message with the same message format as a specific message format, and an old GOOSE outgoing message refers to a GOOSE outgoing message with a different message format than the specific message format, and the specific message format refers to a message format conforming to a specific standard; determining a second mapping relationship between old GOOSE incoming messages and new GOOSE outgoing messages based on a configuration file, wherein an old GOOSE incoming message refers to a GOOSE incoming message with a different message format than the specific message format, and a new GOOSE outgoing message refers to a GOOSE outgoing message with the same message format as the specific message format.

[0100] Optionally, in this embodiment, the computer-readable storage medium is configured to store program code for performing the following steps: sending a target new GOOSE input message to the device to be verified, so that the device to be verified performs format conversion on the target new GOOSE input message, wherein the device to be verified outputs a target old GOOSE output message corresponding to the target new GOOSE input message after performing format conversion on the target new GOOSE input message; sending a target old GOOSE input message to the device to be verified, so that the device to be verified performs format conversion on the target new GOOSE input message, wherein the device to be verified outputs a target new GOOSE output message corresponding to the target old GOOSE input message after performing format conversion on the target old GOOSE input message.

[0101] Optionally, in this embodiment, the computer-readable storage medium is configured to store program code for performing the following steps: obtaining the number of message frames received within a predetermined time period after sending a target GOOSE inbound message to the device to be verified; comparing the number of message frames with a predetermined number to obtain a first comparison result; obtaining the first device instantiation name of the target GOOSE inbound message and the second device instantiation name of the target GOOSE outbound message, wherein the first device instantiation name and the second device instantiation name refer to the unique identifiers of the target GOOSE inbound message and the target GOOSE outbound message in the substation, respectively; comparing the first device instantiation name and the second device instantiation name to obtain a second comparison result; obtaining the first reference path of the target GOOSE inbound message and the second reference path of the target GOOSE outbound message, wherein the first reference path and the second reference path are reference paths obtained according to the configuration file; comparing the first reference path and the second reference path to obtain a third comparison result.

[0102] Optionally, in this embodiment, the computer-readable storage medium is configured to store program code for performing the following steps: upon receiving a target GOOSE outgoing message sent by the device to be verified, determining that a data member in the target GOOSE outgoing message whose state has changed is a target data member, wherein the state change occurs when arbitrarily selecting a data member from the dataset corresponding to the target GOOSE incoming message for state update during the process of sending the target GOOSE incoming message to the device to be verified; obtaining the target reference path of the target data member; and determining the target reference path as the second reference path of the target GOOSE outgoing message.

[0103] Optionally, in this embodiment, the computer-readable storage medium is configured to store program code for performing the following steps: issuing an alarm signal if the first comparison result indicates that the number of message frames received by the device to be verified within a predetermined period after sending the target GOOSE inbound message is less than a predetermined number; issuing an alarm signal if the second comparison result indicates that the first device instantiation name of the target GOOSE inbound message is different from the second device instantiation name of the target GOOSE outbound message; and issuing an alarm signal if the third comparison result indicates that the first reference path of the target GOOSE inbound message is different from the second reference path of the target GOOSE outbound message.

[0104] According to another aspect of the present invention, a processor is also provided, which is used to run a program, wherein the program executes any of the above-described automated verification methods for GOOSE messages.

[0105] According to another aspect of the present invention, a computer program product is also provided, including computer instructions, which, when executed by a processor, perform an automated verification method for GOOSE messages as described above.

[0106] The sequence numbers of the above embodiments of the present invention are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.

[0107] In the above embodiments of the present invention, the descriptions of each embodiment have different focuses. For parts not described in detail in a certain embodiment, please refer to the relevant descriptions of other embodiments.

[0108] In the several embodiments provided in this application, it should be understood that the disclosed technical content can be implemented in other ways. The device embodiments described above are merely illustrative; for example, the division of units can be a logical functional division, and in actual implementation, there may be other division methods. For instance, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the displayed or discussed mutual coupling, direct coupling, or communication connection may be through some interfaces; the indirect coupling or communication connection between units or modules may be electrical or other forms.

[0109] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0110] Furthermore, the functional units in the various embodiments of the present invention can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0111] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, read-only memory (ROM), random access memory (RAM), portable hard drives, magnetic disks, or optical disks.

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

Claims

1. An automated verification method for GOOSE messages, characterized in that, include: Import the configuration file of the device to be verified. The device to be verified refers to the device that needs to convert the format of GOOSE messages during the intelligent transformation of the substation. The GOOSE message refers to a specific type of message used in the substation to transmit key event information. The configuration file contains the configuration information of the device to be verified. Based on the configuration file, the mapping relationship between the GOOSE incoming messages and GOOSE outgoing messages of the device to be verified is determined. The GOOSE incoming messages refer to the GOOSE messages sent to the device to be verified, and the GOOSE outgoing messages refer to the GOOSE messages received from the device to be verified. The GOOSE incoming messages include new GOOSE incoming messages and old GOOSE incoming messages. The GOOSE outgoing messages also include new GOOSE outgoing messages and old GOOSE outgoing messages. The new GOOSE incoming messages refer to GOOSE incoming messages with the same message format as a specific message format, and the old GOOSE outgoing messages refer to... GOOSE outgoing message refers to a GOOSE outgoing message whose message format differs from the specific message format. The specific message format refers to a message format that conforms to a specific standard. The old GOOSE incoming message refers to a GOOSE incoming message whose message format differs from the specific message format. The new GOOSE outgoing message refers to a GOOSE outgoing message whose message format is the same as the specific message format. The format conversion involves converting the new GOOSE incoming message into the corresponding old GOOSE outgoing message, or converting the old GOOSE incoming message into the corresponding new GOOSE outgoing message. The target GOOSE inbound message is sent to the device to be verified, so that the device to be verified performs format conversion on the target GOOSE inbound message. The target GOOSE inbound message is used to verify the accuracy of the format conversion performed by the device to be verified. After performing format conversion on the target GOOSE inbound message, the device to be verified outputs a target GOOSE outbound message corresponding to the target GOOSE inbound message. Receive the target GOOSE output message sent by the device to be verified; The correspondence between the target GOOSE incoming messages and the target GOOSE outgoing messages is compared with the mapping relationship to obtain the comparison result; If the comparison result indicates that the target GOOSE incoming message and the target GOOSE outgoing message do not satisfy the mapping relationship, an alarm signal is issued. The correspondence between the target GOOSE incoming message and the target GOOSE outgoing message is compared with the mapping relationship to obtain a comparison result, including at least one of the following: obtaining the number of message frames received within a predetermined time period after sending the target GOOSE incoming message to the device to be verified; comparing the number of message frames with the predetermined number to obtain a first comparison result; obtaining the first device instantiation name of the target GOOSE incoming message and the second device instantiation name of the target GOOSE outgoing message, wherein the first device instantiation name and the second device instantiation name refer to the unique identifiers of the target GOOSE incoming message and the target GOOSE outgoing message in the substation, respectively; comparing the first device instantiation name and the second device instantiation name to obtain a second comparison result; obtaining the first reference path of the target GOOSE incoming message and the second reference path of the target GOOSE outgoing message, wherein the first reference path and the second reference path are reference paths obtained according to the configuration file; comparing the first reference path and the second reference path to obtain a third comparison result. If the comparison result indicates that the target GOOSE incoming message and the target GOOSE outgoing message do not satisfy the mapping relationship, an alarm signal is issued, including at least one of the following: If the first comparison result indicates that the number of message frames received by the device under test within the predetermined time period after sending the target GOOSE incoming message is less than the predetermined number, the alarm signal is issued; if the second comparison result indicates that the first device instantiation name of the target GOOSE incoming message is different from the second device instantiation name of the target GOOSE outgoing message, the alarm signal is issued; if the third comparison result indicates that the first reference path of the target GOOSE incoming message and the second reference path of the target GOOSE outgoing message are different, the alarm signal is issued.

2. The automated verification method for GOOSE messages according to claim 1, characterized in that, Import the configuration file of the device to be verified, including: Import the process layer configuration file of the device to be verified, wherein the process layer configuration file is used to determine the GOOSE inbound message information of the GOOSE inbound messages subscribed to by the device to be verified, the reference path of the GOOSE inbound messages and the GOOSE outbound messages; Import the internal configuration file of the device to be verified, wherein the internal configuration file is used to determine the mapping relationship between the GOOSE incoming messages and the GOOSE outgoing messages.

3. The automated verification method for GOOSE messages according to claim 1, characterized in that, The mapping relationship includes: a first mapping relationship and a second mapping relationship. Based on the configuration file, the mapping relationship between the GOOSE incoming messages and GOOSE outgoing messages of the device to be verified is determined, including: The first mapping relationship between new GOOSE inbound messages and old GOOSE outbound messages is determined based on the configuration file. The second mapping relationship between old GOOSE inbound messages and new GOOSE outbound messages is determined based on the configuration file.

4. The automated verification method for GOOSE messages according to claim 1, characterized in that, The target GOOSE incoming message includes: a target new GOOSE incoming message and a target old GOOSE incoming message; the target GOOSE outgoing message includes: a target new GOOSE outgoing message and a target old GOOSE outgoing message; the target GOOSE incoming message is sent to the device to be verified, so that the device to be verified performs format conversion on the target GOOSE incoming message, including: The target new GOOSE input message is sent to the device to be verified, so that the device to be verified performs format conversion on the target new GOOSE input message. After performing format conversion on the target new GOOSE input message, the device to be verified outputs the target old GOOSE output message corresponding to the target new GOOSE input message. The target old GOOSE input message is sent to the device to be verified, so that the device to be verified performs format conversion on the target new GOOSE input message. After performing format conversion on the target old GOOSE input message, the device to be verified outputs a target new GOOSE output message corresponding to the target old GOOSE input message.

5. The automated verification method for GOOSE messages according to claim 1, characterized in that, Obtaining the second reference path of the target GOOSE outgoing message includes: Upon receiving the target GOOSE output message sent by the device to be verified, the data member in the target GOOSE output message whose state has changed is determined to be the target data member. The state change occurs when, during the process of sending the target GOOSE input message to the device to be verified, one of the data members is randomly selected from the dataset corresponding to the target GOOSE input message for state update. Obtain the target reference path of the target data member; The target reference path is determined to be the second reference path of the target GOOSE outgoing message.

6. An automated verification device for GOOSE messages, characterized in that, include: The import unit is used to import the configuration file of the device to be verified. The device to be verified refers to the device that needs to convert the format of GOOSE messages during the intelligent transformation of the substation. The GOOSE message refers to a specific type of message used in the substation to transmit key event information. The configuration file contains the configuration information of the device to be verified. The determining unit is configured to determine, based on the configuration file, the mapping relationship between GOOSE incoming messages and GOOSE outgoing messages of the device to be verified. The GOOSE incoming messages refer to GOOSE messages sent to the device to be verified, and the GOOSE outgoing messages refer to GOOSE messages received from the device to be verified. The GOOSE incoming messages include both new and old GOOSE incoming messages, and the GOOSE outgoing messages include both new and old GOOSE outgoing messages. The new GOOSE incoming messages refer to GOOSE incoming messages with the same message format as a specific message format. The old GOOSE outgoing message refers to a GOOSE outgoing message whose message format differs from the specific message format. The specific message format refers to a message format that conforms to a specific standard. The old GOOSE incoming message refers to a GOOSE incoming message whose message format differs from the specific message format. The new GOOSE outgoing message refers to a GOOSE outgoing message whose message format is the same as the specific message format. The format conversion involves converting the new GOOSE incoming message into the corresponding old GOOSE outgoing message, or converting the old GOOSE incoming message into the corresponding new GOOSE outgoing message. A sending unit is configured to send a target GOOSE input message to the device to be verified, so that the device to be verified performs format conversion on the target GOOSE input message. The target GOOSE input message is used to verify the accuracy of the format conversion performed by the device to be verified. After performing format conversion on the target GOOSE input message, the device to be verified outputs a target GOOSE output message corresponding to the target GOOSE input message. The receiving unit is used to receive the target GOOSE output message sent by the device to be verified; The comparison unit is used to compare the correspondence between the target GOOSE incoming message and the target GOOSE outgoing message with the mapping relationship to obtain the comparison result; The early warning unit is configured to issue an alarm signal when the comparison result indicates that the target GOOSE incoming message and the target GOOSE outgoing message do not satisfy the mapping relationship. The comparison unit includes at least one of the following: a first acquisition module, configured to acquire the number of message frames received within a predetermined time period after sending the target GOOSE inbound message to the device to be verified; a second acquisition module, configured to compare the number of message frames with a predetermined number to obtain a first comparison result; a third acquisition module, configured to acquire the first device instantiation name of the target GOOSE inbound message and the second device instantiation name of the target GOOSE outbound message, wherein the first device instantiation name and the second device instantiation name respectively refer to the unique identifiers of the target GOOSE inbound message and the target GOOSE outbound message in the substation; a fourth acquisition module, configured to compare the first device instantiation name and the second device instantiation name to obtain a second comparison result; a fifth acquisition module, configured to acquire the first reference path of the target GOOSE inbound message and the second reference path of the target GOOSE outbound message, wherein the first reference path and the second reference path are reference paths obtained according to the configuration file; and a sixth acquisition module, configured to compare the first reference path and the second reference path to obtain a third comparison result. The early warning unit includes at least one of the following: a first early warning module, configured to issue an alarm signal when the first comparison result indicates that the number of message frames received by the device under verification within the predetermined time period after sending the target GOOSE inbound message is less than the predetermined number; a second early warning module, configured to issue the alarm signal when the second comparison result indicates that the first device instantiation name of the target GOOSE inbound message is different from the second device instantiation name of the target GOOSE outbound message; and a third early warning module, configured to issue the alarm signal when the third comparison result indicates that the first reference path of the target GOOSE inbound message is different from the second reference path of the target GOOSE outbound message.

7. A computer-readable storage medium, characterized in that, The computer-readable storage medium includes a stored program, wherein the program executes the automated verification method for GOOSE messages as described in any one of claims 1 to 5.

8. A computer program product comprising computer instructions, characterized in that, When the computer instructions are executed by the processor, they perform the automated verification method for GOOSE messages as described in any one of claims 1 to 5.

Citation Information

Patent Citations

  • Intelligent substation consistency verification method and device and medium thereof

    CN115600697A

  • Device and method for checking real-time consistency of intelligent substation

    CN116055351A