Method and system for monitoring and configuring state of relay protection device

Abstract

The invention discloses a relay protection device state monitoring and configuration method and system. The system comprises a hardware monitoring module, a relay protection device and a software upper computer platform. The hardware monitoring module directly communicates with the relay protection device through a high-speed data bus; the upper computer platform development comprises an integrated automatic test function and a monitoring board console. According to the system, communication state monitoring is achieved by analyzing standard messages such as MMS, GOOSE and SV in real time, and remote parameter configuration and function testing are supported. According to the invention, the integrated functions of online monitoring, intelligent diagnosis and remote configuration of the relay protection device are creatively realized, and the maintenance efficiency of the secondary equipment of the power system is remarkably improved.

Description

Technical Field

[0001] This invention belongs to the field of power system relay protection technology, specifically relating to a method and system for monitoring and configuring the status of a relay protection device. Background Technology

[0002] With the deepening of smart grid construction, the number of relay protection devices based on the IEC61850 standard in digital smart substations is growing exponentially. The number of relay protection devices required in smart substations is significantly greater than in traditional substations, leading to a greater workload for commissioning and maintenance. In actual operation and maintenance, many device failures originate from abnormal communication using the IEC61850 protocol.

[0003] In existing technologies, the following methods are mainly used for communication monitoring and configuration of relay protection devices:

[0004] Communication fault monitoring: It is necessary to collect MMS, GOOSE, SV and other messages one by one through the physical connection of the upper computer to the various functional modules of the device, and then analyze them through offline analysis tools or manual analysis.

[0005] Device configuration modification: The complete program configuration file (such as CID file) needs to be re-downloaded via the device panel on-site or through the backplane Ethernet port.

[0006] The existing technology has the following inherent defects:

[0007] (1) Lack of real-time monitoring capability: A continuous physical connection must be maintained between the host computer and the faulty device, making it difficult to capture sudden communication failures. For example, heartbeat timeout failures in GOOSE messages often exhibit transient characteristics;

[0008] (2) Difficulty in reproducing faults: Some communication faults (such as packet loss of SV sampling values) have random occurrence characteristics. When maintenance personnel arrive at the site, the fault may have disappeared, and there is a lack of effective means to trace historical data.

[0009] (3) Inefficient test environment construction: When conducting special network tests (including but not limited to: network storm test, bandwidth congestion test, abnormal packet injection test), it is necessary to repeatedly download the modified configuration file, resulting in a long single configuration cycle;

[0010] (4) Insufficient configuration flexibility: Key underlying parameters (such as GOOSE storm suppression threshold parameters, broadcast message storm suppression threshold parameters, SPI communication verification configuration, SV sampling rate parameters (SvControlBlock) etc.) are limited by the device firmware architecture and cannot be modified through conventional configuration files. Summary of the Invention

[0011] This invention provides a method and system for monitoring and configuring the status of relay protection devices, which solves the technical problems of poor real-time communication monitoring, difficulty in fault reproduction, and insufficient configuration flexibility of relay protection devices in the prior art.

[0012] To achieve the above objectives, the present invention is implemented through the following technical solutions.

[0013] A system for monitoring and configuring the status of a relay protection device includes: a hardware monitoring module, a relay protection device, and a software host computer platform.

[0014] The hardware monitoring module adopts an embedded architecture of FPGA+CPU, which also includes a network interface, a storage unit, and a high-speed bus interface. The hardware monitoring module connects to the internal high-speed bus of the relay protection device via the high-speed bus interface and communicates with the host computer platform via the network interface. The FPGA is used for high-speed message processing, analysis, classification, and configuration message generation; the CPU is used for running control logic, data processing, and command parsing; and the storage unit is used for caching abnormal messages and preset test messages.

[0015] The software host computer platform includes a monitoring module console program and an automated testing program. The monitoring module console program is used for system control and status monitoring, while the automated testing program is used for message analysis and test report generation.

[0016] A system for monitoring and configuring the status of a relay protection device includes: a hardware monitoring module, a relay protection device, and a software host computer platform.

[0017] The hardware monitoring module includes an FPGA and a CPU, which communicate with each other via Gigabit Ethernet. The hardware detection module is connected to the internal high-speed bus of the relay protection device through a high-speed bus interface and communicates with the host computer platform through a network interface. The FPGA is used to realize high-speed message processing, analysis, classification and configuration message generation. The CPU is used to run control logic, data processing and command parsing. The storage unit is used to cache abnormal messages and preset test messages.

[0018] The software host computer platform is equipped with a monitoring module console module and an automated testing module; the monitoring module console module is used for system control and status monitoring, and the automated testing module is used for performing message analysis and generating test reports.

[0019] A method for monitoring and configuring the status of a relay protection device includes:

[0020] Step 1: Connect the hardware monitoring module to the high-speed bus inside the relay protection device, and establish network communication between the hardware monitoring module and the host computer platform.

[0021] Step 2: Select the target function through the host computer platform and send the corresponding command to the hardware monitoring module. The command includes target module information and function type. Function types include message anomaly analysis function, device configuration modification function, device status query function, and special communication environment testing function.

[0022] Step 3: After receiving and parsing the command, the hardware monitoring module captures the target message on the high-speed bus or generates the corresponding request message and sends it to the high-speed bus by modifying the receiving address number.

[0023] Step 4: The hardware monitoring module parses the messages locally and stores the abnormal messages and context data, or uploads the messages to the host computer platform for analysis and generation of a test report.

[0024] The hardware monitoring module generates a configuration message and sends it to the target module. It receives the configuration result response message from the target module and feeds it back to the host computer platform. It generates a query message and sends it to the target module. It receives the status and configuration information returned by the target module and uploads it to the host computer platform for visualization. It generates a preset test message and sends it to the high-speed bus, simultaneously enabling message capture and analysis. The response result determines whether the test passes; if it fails, a message anomaly analysis process is triggered.

[0025] During testing, the hardware monitoring module can simulate various interference and abnormal communication scenarios, including high load, sudden packet loss, message corruption, and protocol compliance, and monitor the device's response behavior in real time. The high load test creates a high-load environment to test the device's instantaneous processing capability. The message corruption test verifies the error detection and processing mechanism of the protocol stack by controllably tampering with the checksum or specific key fields in the message. The protocol compliance test constructs unexpected messages, abnormal sequences, and messages of extreme length to test the device's ability to process malformed messages.

[0026] The aforementioned method for monitoring and configuring the status of relay protection devices, wherein the hardware monitoring module in step one adopts an embedded architecture of FPGA+CPU, including a network interface, a storage unit and a high-speed bus interface, wherein the FPGA is used for high-speed message processing and analysis, and the CPU is used for running control logic, parsing host computer commands and task scheduling.

[0027] In the aforementioned method for monitoring and configuring the status of relay protection devices, when the modified receiving address number in step three is 0xFFFF, the capture of all messages on the high-speed bus is achieved; when the receiving address number is a value between 0x0001 and 0x00FF, the capture of directional messages of the target module with the corresponding address number is achieved.

[0028] The aforementioned method for monitoring and configuring the status of relay protection devices includes, in step four, the objects of message anomaly analysis, which include MMS, GOOSE, and SV messages as specified in the IEC 61850 standard. The anomaly determination of GOOSE messages is based on the variation patterns of STNUM and SQNUM, while the anomaly determination of SV messages is based on the continuity of SMPCNT and the rationality of the sampled values.

[0029] The aforementioned method for monitoring and configuring the status of relay protection devices, wherein the GOOSE message anomaly determination is based on the changing patterns of STNUM and SQNUM; the patterns include:

[0030] STNUM and SQNUM remained unchanged for two consecutive frames.

[0031] STNUM is the same, but SQNUM jumps more than 1.

[0032] STNUM increments, but SQNUM is not reset to 0x00.

[0033] Meanwhile, a three-level verification mechanism is used when detecting message anomalies: APPID verification, timestamp verification, and data value verification.

[0034] In the aforementioned method for monitoring and configuring the status of relay protection devices, the abnormal message context data stored in step four consists of 25 frames of associated messages before and after the abnormal frame. The storage adopts a block-based circular buffer design, with 50 frames as a storage unit.

[0035] The aforementioned method for monitoring and configuring the status of relay protection devices includes the following configuration items supported by the device configuration modification function in step four: enabling / disabling the GOOSE message storm suppression function, enabling / disabling the SPI communication CRC check function, enabling / disabling the broadcast storm suppression function, and adjusting the corresponding threshold parameters.

[0036] The aforementioned method for monitoring and configuring the status of relay protection devices includes a special communication environment test function in step four, which includes network storm test, bandwidth preemption test, and abnormal message injection test. The network storm test injects high-priority GOOSE messages at 1ms intervals, and the bandwidth preemption test continuously sends 1500-byte long frame messages.

[0037] In the aforementioned method for monitoring and configuring the status of relay protection devices, the information obtained by the device status query function in step four includes the message sending counter value and the message receiving counter value of the target module. By comparing the counter values, the source module of the message packet loss anomaly can be determined.

[0038] The beneficial effects of this invention: This invention provides a method and system for monitoring and configuring the status of relay protection devices, enabling message anomaly analysis, configuration modification, status query, and communication testing. This invention solves the technical problems of poor real-time performance, difficulty in fault reproduction, and insufficient configuration flexibility in the prior art by operating the monitoring module through a host computer console to perform various tasks. The monitoring module of this invention supports the following functions: 1. Message anomaly analysis: Locally parses internal and external messages of the device and stores erroneous messages, or uploads them to the host computer to generate test reports; 2. Configuration modification: Sends configuration messages to the target module via a high-speed bus and provides feedback on the results; 3. Status query: Obtains module status and configuration information in real time and displays it through a visual interface; 4. Communication testing: Sends preset messages to the high-speed bus to test the reliability of internal communication and automatically triggers the message anomaly analysis process. Attached Figure Description

[0039] Figure 1 This is a schematic diagram of the overall framework of the relay protection device status monitoring and configuration system of the present invention in Embodiment 1;

[0040] Figure 2 This is a schematic diagram of the relay protection device status monitoring and configuration method of the present invention in Example 2;

[0041] Figure 3 This is a schematic diagram of the monitoring plate structure in Example 3;

[0042] Figure 4 This is a schematic diagram of the message detection program in the host computer platform in Example 3;

[0043] Figure 5 This is a schematic diagram of the process for analyzing and storing error messages inside the monitoring board in Example 3. Detailed Implementation

[0044] The technical solution of the present invention will be further described below with reference to the accompanying drawings.

[0045] Example 1:

[0046] like Figure 1 As shown, this embodiment provides a system for monitoring and configuring the status of a relay protection device, including: a hardware monitoring module, a relay protection device, and a software host computer platform.

[0047] The hardware monitoring module adopts an embedded architecture of FPGA+CPU, which also includes a network interface, a storage unit, and a high-speed bus interface. The hardware monitoring module connects to the internal high-speed bus of the relay protection device via the high-speed bus interface and communicates with the host computer platform via the network interface. The FPGA is used for high-speed message processing, analysis, classification, and configuration message generation; the CPU is used for running control logic, data processing, and command parsing; and the storage unit is used for caching abnormal messages and preset test messages.

[0048] The software host computer platform includes a monitoring module console program and an automated testing program. The monitoring module console program is used for system control and status monitoring, while the automated testing program is used for message analysis and test report generation.

[0049] Example 2:

[0050] like Figure 2 As shown, this embodiment provides a method for monitoring and configuring the status of a relay protection device, including: Step 1: Connecting the hardware monitoring module to the high-speed bus inside the relay protection device, and simultaneously establishing a hardware monitoring...

[0051] Network communication between the test module and the host computer platform.

[0052] Step 2: Select the target function through the host computer platform and send the corresponding command to the hardware monitoring module. The command includes target module information and function type. Function types include message anomaly analysis function, device configuration modification function, device status query function, and special communication environment testing function.

[0053] Step 3: After receiving and parsing the command, the hardware monitoring module captures the target message on the high-speed bus or generates the corresponding request message and sends it to the high-speed bus by modifying the receiving address number.

[0054] Step 4: The hardware monitoring module parses the messages locally and stores the abnormal messages and context data, or uploads the messages to the host computer platform for analysis and generation of a test report.

[0055] The hardware monitoring module generates a configuration message and sends it to the target module. It receives the configuration result response message returned by the target module and feeds it back to the host computer platform. It generates a query message and sends it to the target module. It receives the status and configuration information returned by the target module and uploads it to the host computer platform for visualization. It generates a preset test message and sends it to the high-speed bus. Simultaneously, it starts the message capture and analysis function. It determines whether the test passes based on the response result. If it fails, it triggers the message anomaly analysis process.

[0056] During testing, the hardware monitoring module can simulate various interference and abnormal communication scenarios, including high load, sudden packet loss, message corruption, and protocol compliance, and monitor the device's response behavior in real time. The high load test creates a high-load environment to test the device's instantaneous processing capability. The message corruption test verifies the error detection and processing mechanism of the protocol stack by controllably tampering with the checksum or specific key fields in the message. The protocol compliance test constructs unexpected messages, abnormal sequences, and messages of extreme length to test the device's ability to process malformed messages.

[0057] The aforementioned method for monitoring and configuring the status of relay protection devices, wherein the hardware monitoring module in step one adopts an embedded architecture of FPGA+CPU, including a network interface, a storage unit and a high-speed bus interface, wherein the FPGA is used for high-speed message processing and analysis, and the CPU is used for running control logic, parsing host computer commands and task scheduling.

[0058] In the aforementioned method for monitoring and configuring the status of relay protection devices, when the modified receiving address number in step three is 0xFFFF, the capture of all messages on the high-speed bus is achieved; when the receiving address number is a value between 0x0001 and 0x00FF, the capture of directional messages of the target module with the corresponding address number is achieved.

[0059] The aforementioned method for monitoring and configuring the status of relay protection devices includes, in step four, the objects of message anomaly analysis, which include MMS, GOOSE, and SV messages as specified in the IEC 61850 standard. The anomaly determination of GOOSE messages is based on the variation patterns of STNUM and SQNUM, while the anomaly determination of SV messages is based on the continuity of SMPCNT and the rationality of the sampled values.

[0060] The aforementioned method for monitoring and configuring the status of relay protection devices, wherein the GOOSE message anomaly determination is based on the changing patterns of STNUM and SQNUM; the patterns include:

[0061] STNUM and SQNUM remained unchanged for two consecutive frames.

[0062] STNUM is the same, but SQNUM jumps more than 1.

[0063] STNUM increments, but SQNUM is not reset to 0x00.

[0064] Meanwhile, a three-level verification mechanism is used when detecting message anomalies: APPID verification, timestamp verification, and data value verification.

[0065] In the aforementioned method for monitoring and configuring the status of relay protection devices, the abnormal message context data stored in step four consists of 25 frames of associated messages before and after the abnormal frame. The storage adopts a block-based circular buffer design, with 50 frames as a storage unit.

[0066] The aforementioned method for monitoring and configuring the status of relay protection devices includes the following configuration items supported by the device configuration modification function in step four: enabling / disabling the GOOSE message storm suppression function, enabling / disabling the SPI communication CRC check function, enabling / disabling the broadcast storm suppression function, and adjusting the corresponding threshold parameters.

[0067] The aforementioned method for monitoring and configuring the status of relay protection devices includes a special communication environment test function in step four, which includes network storm test, bandwidth preemption test, and abnormal message injection test. The network storm test injects high-priority GOOSE messages at 1ms intervals, and the bandwidth preemption test continuously sends 1500-byte long frame messages.

[0068] In the aforementioned method for monitoring and configuring the status of relay protection devices, the information obtained by the device status query function in step four includes the message sending counter value and the message receiving counter value of the target module. By comparing the counter values, the source module of the message packet loss anomaly can be determined.

[0069] Example 3:

[0070] like Figure 3 As shown in the diagram, the monitoring board's hardware structure includes a CPU, an FPGA, two network ports, a storage unit, and a high-speed bus interface. The FPGA chip is used to build Ethernet, SDIO, and SPI communication channels, as well as the analysis logic for messages on the high-speed bus. The CPU chip is used to receive and parse commands from the host computer, configure registers, and perform task control and scheduling. Network port 1 can be used to receive GOOSE, SV, and MMS Ethernet messages. Network port 2 can be used to forward messages acquired on the high-speed bus while receiving messages from network port 1, or to acquire message data from the storage unit. The storage unit is used to store problem messages and preset test messages. The high-speed bus interface is used to send and receive messages on the high-speed bus. The CPU and FPGA communicate via Gigabit Ethernet and SPI protocols, while the FPGA and storage unit communicate using the SDIO communication protocol. External communication with the monitoring board (Ethernet, high-speed bus) is processed by the FPGA, and the data is packaged and exchanged with the CPU.

[0071] like Figure 4 As shown, a message detection program in a host computer platform includes:

[0072] Step A. The host computer receives the message from the high-speed bus transmitted through the monitoring board.

[0073] Step B. The program in the host computer classifies the packets according to the destination MAC address, source MAC address, packet type identifier, and target module address.

[0074] Step C. The detection program determines whether the message is a GOOSE message, an SMV message, or a configuration message. If it is not one of these three types of messages, the message will not be analyzed.

[0075] Step D. For GOOSE messages, classify them according to the destination MAC address and message control block, and the key data STNUM, SQNUM, APPID, and the current valid data record queue.

[0076] Step E. Determine if there are any anomalies in the messages based on the key information in the queue.

[0077] Step F. For SMV packets, classify them according to the destination MAC address and svID, and the key data smpCnt, and the current valid data record queue.

[0078] Step G. Determine if there are any anomalies in the messages based on the key information in the queue.

[0079] Step H. For configuration messages, obtain the configuration and status information of the target node module, and display the specific faults according to the protocol.

[0080] Step I. The message detection program generates a final detection report, including the type of abnormal message, the location of the abnormal message, the source of the abnormal message (target module address), the configuration and status information of the target module, and the specific faults present.

[0081] A method for detecting message anomalies in a relay protection device status monitoring and configuration system includes: for GOOSE messages, 1) status sequence detection, wherein under normal conditions, when the device status changes, STNUM should increment by 1 (e.g., from 0x01 to 0x02), and SQNUM must be reset to 0x00; during steady-state communication, STNUM remains unchanged (e.g., remains at 0x02) and SQNUM should increment continuously (e.g., 0x01, 0x02, 0x03...); 2) the anomaly judgment criteria are: a) STNUM and SQNUM do not change (e.g., two consecutive frames are STNUM=0x02 / SQNUM=0x01), b) STNUM is the same but SQNUM jumps by more than 1 (e.g., from SQNUM=0x01 to 0x03), c) STNUM increases but SQNUM is not reset (e.g., STNUM changes from 0x02 to 0x03 but SQNUM remains at 0x01). Simultaneously, a three-level verification mechanism is adopted: the first level is APPID verification (preset allowable range 0x0001-0x0FFF), the second level is timestamp verification, and the third level is data value verification. For SV messages, the continuity of SMPCNT and the rationality of the sampled values ​​are detected. Dynamic adjustment of monitoring is supported by modifying the destination module address value (e.g., 0xFFFF indicates full capture, 0x0001-0x00FF indicates targeted capture). In a typical application scenario, when an anomaly is detected where STNUM changes from 0x02 to 0x03 but SQNUM remains 0x01, the system will: 1) record the error state, 2) save the abnormal frame and the context data of the preceding and following 25 frames (a total of 50 frames), thereby realizing intelligent monitoring and fault judgment of the communication status of the relay protection device.

[0082] like Figure 5 As shown, the method for analyzing and storing error messages inside the monitoring board includes:

[0083] During storage, messages are grouped into units of 50 frames, with external storage capable of holding at least 30 units. Each message frame is stored in external storage unit by unit. The monitoring board retrieves specified messages from the high-speed bus according to commands from the host computer. Messages are forwarded to the host computer via the network port after passing through two levels of buffering. For internal message analysis and storage on the monitoring board, messages are written to external storage after two levels of buffering. Two counters are used: one records the total number of messages written to external storage, and the other records the number of units containing erroneous messages. Simultaneously, messages undergo two levels of buffering for analysis. The analysis process is further divided into message classification, GOOSE message detection, and SV message detection. A counter records the total number of analyzed messages. When a problem message indicator is generated, it indicates that the message frame has a problem, and the corresponding register is set. This allows the location of the erroneous message in external storage to be determined. If the problematic message is the first frame of this unit, the message content of the previous storage unit is retained; if the problematic message is the last frame of this unit, the message content of the next storage unit is retained; if the problematic message is a message within this unit, the storage unit containing the problematic message will overwrite the previous storage unit without a problematic message. When the storage area is full, the LRU algorithm is used to update and ensure that the latest 30 abnormal units are saved. Data is read via the SDIO protocol and transmitted to the host computer via Gigabit Ethernet, containing a complete message header, data field, and checksum information.

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

Claims

1. A system for monitoring and configuring the status of a relay protection device, characterized in that, include: Hardware monitoring modules, relay protection devices, and software host computer platforms; The hardware monitoring module includes an FPGA and a CPU, and the FPGA and CPU communicate via gigabit Ethernet. The hardware detection module is connected to the internal high-speed bus of the relay protection device through a high-speed bus interface and communicates with the host computer platform through a network interface; the FPGA is used to realize high-speed message processing, analysis, classification and configuration message generation; the CPU is used to run control logic, data processing and command parsing; and the storage unit is used to cache abnormal messages and preset test messages. The software host computer platform is equipped with a monitoring module console module and an automated testing module; the monitoring module console module is used for system control and status monitoring, and the automated testing module is used for performing message analysis and generating test reports.

2. A method for monitoring and configuring the status of a relay protection device, characterized in that, include: Step 1: Connect the hardware monitoring module to the high-speed bus inside the relay protection device, and at the same time establish network communication between the hardware monitoring module and the host computer platform; Step 2: Select the target function through the host computer platform and send the corresponding command to the hardware monitoring module. The command includes target module information and function type. Function types include message anomaly analysis function, device configuration modification function, device status query function, and special communication environment testing function. Step 3: After receiving and parsing the command, the hardware monitoring module captures the target message on the high-speed bus by parsing the received address number or generates the corresponding request message and sends it to the high-speed bus. Step 4: The hardware monitoring module parses the messages locally and stores the abnormal messages and context data, or uploads the messages to the host computer platform for analysis and generation of a test report; The hardware monitoring module generates a configuration message and sends it to the target module. It receives the configuration result response message returned by the target module and feeds it back to the host computer platform. It generates a query message and sends it to the target module. It receives the status and configuration information returned by the target module and uploads it to the host computer platform for visualization. It generates a preset test message and sends it to the high-speed bus. It simultaneously starts the message capture and analysis function. It determines whether the test passes based on the response result. If it fails, it triggers the message anomaly analysis process. During testing, the hardware monitoring module can simulate various interference and abnormal communication scenarios, including high load, sudden packet loss, message corruption, and protocol compliance, and monitor the device's response behavior in real time. The high load test creates a high-load environment to test the device's instantaneous processing capability. The message corruption test verifies the error detection and processing mechanism of the protocol stack by controllably modifying the checksum or specific key fields in the message. The protocol compliance test constructs unexpected messages, abnormal sequences, and messages of extreme length to test the device's ability to process malformed messages.

3. The method for monitoring and configuring the status of a relay protection device according to claim 2, characterized in that, The hardware monitoring module in step one adopts an embedded architecture of FPGA+CPU, including a network interface, a storage unit and a high-speed bus interface. The FPGA is used for high-speed message processing and analysis, and the CPU is used for running control logic, parsing host computer commands and task scheduling.

4. The method for monitoring and configuring the status of a relay protection device according to claim 2, characterized in that, In step three, when the modified receive address number is 0xFFFF, all messages on the high-speed bus are captured; when the receive address number is a value between 0x0001 and 0x00FF, the targeted message capture of the target module with the corresponding address number is achieved.

5. The method for monitoring and configuring the status of a relay protection device according to claim 2, characterized in that, The objects of message anomaly analysis in step four include MMS, GOOSE, and SV messages as specified in the IEC 61850 standard. The anomaly determination of GOOSE messages is based on the variation patterns of STNUM and SQNUM, while the anomaly determination of SV messages is based on the continuity of SMPCNT and the rationality of the sampled values.

6. The method for monitoring and configuring the status of a relay protection device according to claim 5, characterized in that, The GOOSE message anomaly determination is based on the changing patterns of STNUM and SQNUM; these patterns include: STNUM and SQNUM remained unchanged for two consecutive frames; The STNUM values ​​are the same, but the SQNUM jumps by more than 1; STNUM increments but SQNUM is not reset to 0x00; Meanwhile, a three-level verification mechanism is used when detecting message anomalies: APPID verification, timestamp verification, and data value verification.

7. The method for monitoring and configuring the status of a relay protection device according to claim 2, characterized in that, The abnormal message context data stored in step four consists of 25 frames of associated messages before and after the abnormal frame. The storage adopts a block-based circular buffer design, with 50 frames as a storage unit.

8. The method for monitoring and configuring the status of a relay protection device according to claim 2, characterized in that, The device configuration modification function in step four supports the following configuration items: enabling / disabling the GOOSE message storm suppression function, enabling / disabling the SPI communication CRC check function, enabling / disabling the broadcast storm suppression function, and adjusting the corresponding threshold parameters.

9. The method for monitoring and configuring the status of a relay protection device according to claim 2, characterized in that, The special communication environment testing functions in step four include network storm testing, bandwidth preemption testing, and abnormal message injection testing; the network storm testing injects high-priority GOOSE messages at 1ms intervals, and the bandwidth preemption testing continuously sends 1500-byte long frame messages.

10. The method for monitoring and configuring the status of a relay protection device according to claim 2, characterized in that, The information obtained by the device status query function in step four includes the message sending counter value and the message receiving counter value of the target module. By comparing the counter values, the source module of the message packet loss anomaly can be determined.

Images