A fault information notification method and related apparatus

Abstract

The application discloses a fault information notification method and related device, and relates to the field of power operation and maintenance, which can acquire fault notification brief information in response to an initial fault signal. Then, the fault notification brief information is subjected to integrity check to determine whether the fault notification brief information meets a fault sending condition. When the fault sending condition is met, the fault notification brief information is sent after a first waiting duration is reached. When it is determined that the fault sending condition is not met, new fault notification brief information is continuously acquired and subjected to integrity check. If the new fault notification brief information still does not meet the fault sending condition after a second waiting duration is reached, target fault notification brief information is sent. The target fault notification brief information is fault notification brief information with the largest completeness degree acquired within the second waiting duration, and the second waiting duration is longer than the first waiting duration. The timeliness, accuracy and reliability of fault information pushing are effectively improved.

Description

Technical Field

[0001] This application relates to the field of power operation and maintenance technology, and in particular to a fault information notification method and related device. Background Technology

[0002] In the existing operation and maintenance of power systems, when equipment failures or abnormal events occur, the monitoring platform generates corresponding fault reports and pushes them to the relevant maintenance personnel via SMS or other means. However, some monitoring systems immediately send notifications after detecting an initial alarm, but at this time, the protection action may not have been completed, resulting in the notification containing missing key information (such as fault type, phase, and current value), affecting the accuracy of the judgment. Other systems, to ensure the completeness of the notification information, set a long waiting time, causing notification delays and hindering on-site response. Therefore, how to ensure the quality of notifications while maintaining timeliness has become an urgent problem to be solved. Summary of the Invention

[0003] In view of the above problems, this application provides a fault information notification method and related apparatus to improve the accuracy and reliability of fault prompts. The specific solution is as follows:

[0004] The first aspect of this application provides a fault information notification method, including:

[0005] In response to an initial fault signal, obtain fault notification briefing information;

[0006] The integrity of the fault notification briefing information is verified to determine whether the fault notification briefing information meets the fault sending conditions.

[0007] When it is determined that the fault sending conditions are met, the fault notification briefing information is sent after the first waiting time has elapsed.

[0008] If the fault sending conditions are not met, new fault notification briefing information is continuously acquired and its integrity is verified. If the new fault notification briefing information still does not meet the fault sending conditions after the second waiting period has elapsed, a target fault notification briefing information is sent. The target fault notification briefing information is the fault notification briefing information with the highest integrity obtained within the second waiting period, and the second waiting period is longer than the first waiting period.

[0009] In one possible implementation, the fault information notification method further includes:

[0010] Determine the time difference between the time of the fault occurrence and the current system time, and terminate the transmission of the fault notification briefing information when the time difference exceeds a preset duration.

[0011] In one possible implementation, the fault information notification method further includes:

[0012] If no confirmation message is received within the third waiting period after the target fault notification briefing is sent, a preset level notification mechanism will be activated to issue a reminder.

[0013] In one possible implementation, the step of performing an integrity check on the fault notification briefing information to determine whether the fault notification briefing information meets the fault sending conditions includes:

[0014] The keywords in the fault notification briefing information are identified and statistically analyzed to obtain the identification and statistical results.

[0015] Based on the identification statistics and judgment rules, determine whether the fault notification briefing information meets the fault sending conditions.

[0016] In one possible implementation, the process of generating the fault notification briefing information includes:

[0017] The alarm signals within the acquisition period are concatenated according to keywords and combined with the mileage code to generate the fault notification summary information.

[0018] In one possible implementation, the identification and statistical analysis of keywords in the fault notification briefing information to obtain identification and statistical results includes:

[0019] The key fields of current, action, and fault filter in the fault notification briefing information are statistically analyzed to obtain the identification statistics results.

[0020] The step of determining whether the fault notification summary information meets the fault sending conditions based on the identification statistics and judgment rules includes:

[0021] If the current statistics are not greater than the sum of the action statistics and the fault filter statistics, then the fault notification briefing information is determined to meet the fault sending conditions.

[0022] A second aspect of this application provides a fault information notification device, comprising:

[0023] The briefing information acquisition module is used to acquire fault notification briefing information in response to the initial fault signal;

[0024] The briefing information verification module is used to perform integrity verification on the fault notification briefing information and determine whether the fault notification briefing information meets the fault sending conditions.

[0025] The first sending execution module is configured to send the fault notification briefing information after a first waiting period has elapsed when the briefing information verification module determines that the fault sending conditions are met; and,

[0026] The second sending execution module is used to continuously acquire new fault notification briefing information and perform integrity verification when the briefing information verification module determines that the fault sending conditions are not met. If the new fault notification briefing information still does not meet the fault sending conditions after the second waiting time has elapsed, the target fault notification briefing information is sent. The target fault notification briefing information is the fault notification briefing information with the highest degree of completeness acquired within the second waiting time, and the second waiting time is longer than the first waiting time.

[0027] A third aspect of this application provides a computer program product including computer-readable instructions that, when executed on an electronic device, cause the electronic device to implement the fault information notification method of the first aspect or any implementation thereof.

[0028] A fourth aspect of this application provides an electronic device, including at least one processor and a memory connected to the processor, wherein:

[0029] The memory is used to store computer programs;

[0030] The processor is used to execute the computer program so that the electronic device can implement the fault information notification method of the first aspect or any implementation thereof.

[0031] The fifth aspect of this application provides a computer storage medium carrying one or more computer programs, which, when executed by an electronic device, enable the electronic device to implement the fault information notification method described in the first aspect or any implementation thereof.

[0032] By employing the above technical solution, the fault information notification method provided in this application can obtain fault notification summary information in response to an initial fault signal. Then, the integrity of the fault notification summary information is checked to determine whether it meets the fault transmission conditions. When the fault transmission conditions are met, the fault notification summary information is sent after a first waiting period. If the fault transmission conditions are not met, new fault notification summary information is continuously obtained and its integrity is checked. If, after a second waiting period, the new fault notification summary information still does not meet the fault transmission conditions, a target fault notification summary information is sent. The target fault notification summary information is the fault notification summary information with the highest completeness obtained within the second waiting period, which is longer than the first waiting period. This achieves timely transmission of the summary when the fault summary is relatively complete. When the summary does not meet the integrity requirements, the optimal summary can be sent after a certain extended period. This effectively reduces the phenomenon of inaccurate information due to premature transmission and the impact of delayed transmission on processing efficiency, improving the timeliness, accuracy, and reliability of fault information push. Attached Figure Description

[0033] The above and other features, advantages, and aspects of the embodiments of this disclosure will become more apparent from the accompanying drawings and the following detailed description. Throughout the drawings, the same or similar reference numerals denote the same or similar elements. It should be understood that the drawings are schematic, and the originals and elements are not necessarily drawn to scale.

[0034] Figure 1 This application provides an architecture diagram of a fault information notification system;

[0035] Figure 2 A flowchart of a fault information notification method provided in this application;

[0036] Figure 3 Another flowchart of a fault information notification method provided in this application;

[0037] Figure 4 A structural diagram of a fault information notification device provided in this application;

[0038] Figure 5 This is a structural diagram of an electronic device provided in this application. Detailed Implementation

[0039] The embodiments of this application are described below with reference to the accompanying drawings. The terminology used in the implementation section of this application is for explaining specific embodiments only and is not intended to limit the scope of this application.

[0040] The embodiments of this application will now be described with reference to the accompanying drawings. Those skilled in the art will recognize that, with technological advancements and the emergence of new scenarios, the technical solutions provided in the embodiments of this application are equally applicable to similar technical problems.

[0041] The terms "first," "second," etc., used in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such terms are interchangeable where appropriate; this is merely a way of distinguishing objects with the same attributes in the embodiments of this application. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion, so that a process, method, system, product, or apparatus that comprises a series of elements is not necessarily limited to those elements, but may include other elements not explicitly listed or inherent to those processes, methods, products, or apparatuses.

[0042] See Figure 1 , Figure 1 A schematic diagram of a fault information notification system architecture is shown. The system may include a terminal device 100 and a server 200.

[0043] The terminal device 100 can be equipped with an alarm monitoring application to collect alarm-related parameters and send them to the server 200. The server 200 can obtain the processing results based on the received parameters and send the corresponding alarm information.

[0044] The terminal device 100 in this application embodiment can be a relay protection device, etc., and this application embodiment does not impose any restrictions on it.

[0045] Terminal device 100 may include components such as a radio frequency unit, memory, input unit, display unit, camera (optional), processor, external interface, and power supply. Those skilled in the art will understand that the above-mentioned components are merely examples and do not constitute a limitation on the terminal or multifunctional device; it may include more or fewer components, or a combination of certain components, or different components.

[0046] This radio frequency unit (optional) can be used to send and receive information, as well as to receive and send signals during the interaction process.

[0047] In this embodiment of the application, the radio frequency unit can send data to the server 200.

[0048] It should be understood that this radio frequency unit is optional and can be replaced with other communication interfaces, such as a network port.

[0049] The terminal device 100 also includes a power source (such as a battery) for supplying power to the various components.

[0050] The terminal device 100 also includes an external interface, which can be a standard Micro USB interface or a multi-pin connector, which can be used to connect the terminal device 100 to other devices for communication, or to connect a charger to charge the terminal device 100.

[0051] Server 200 includes a bus, a processor, a communication interface, and memory. The processor, memory, and communication interface communicate with each other via the bus.

[0052] The memory can be used to store software code related to the fault information notification method, the processor can execute the steps of the chip's fault information notification method, and can also schedule other units to implement the corresponding functions.

[0053] In existing power system operation and maintenance, when equipment failures or abnormal events occur, a fault report is typically generated through a monitoring platform and pushed to maintenance personnel via SMS. However, the current alarm sending method still has the following problems:

[0054] Sending incomplete information: Some systems send a notification immediately after detecting an initial alarm, but at this time the protection action has not been completed and the waveform data has not been uploaded, resulting in the SMS content missing key information (such as fault type, phase, current value, etc.), affecting the accuracy of the judgment.

[0055] Excessive waiting leads to delays: To ensure information integrity, some systems set long waiting times, causing notification delays and missing opportunities for on-site response.

[0056] Lack of quality assessment mechanism: It cannot automatically determine whether the current fault report meets the conditions for sending, relying on manual intervention or fixed delay, and has a low level of intelligence.

[0057] Historical data mis-sending: When the system restarts or re-collects data, historical fault information that has exceeded the time limit may be re-sent, causing redundant alarms.

[0058] To address the aforementioned problems, this application provides a fault information notification method. The fault information notification method of this application embodiment will be described in detail below with reference to the accompanying drawings.

[0059] Reference Figure 2 , Figure 2 This is a flowchart illustrating a fault information notification method provided in an embodiment of this application, such as... Figure 2 As shown in the figure, a fault information notification method provided in this application embodiment may include steps S201 to S204, which are described in detail below.

[0060] S201. In response to the initial fault signal, obtain fault notification briefing information.

[0061] Specifically, it can receive alarm signals from monitoring mechanisms such as relay protection devices and SCADA (Supervisory Control and Data Acquisition) systems. These alarm signals typically contain information such as fault type, identifier, and category. By parsing these alarm signals, extracting key information, and combining this information, corresponding fault notification briefings can be obtained.

[0062] S202. Perform integrity verification on the fault notification briefing information to determine whether the fault notification briefing information meets the fault sending conditions.

[0063] Based on the fault notification briefing information, the system continuously collects relevant data sources (including protection action records, fault waveforms, and log files) and updates the fault notification briefing information to be sent. It then performs a completeness check on the detailed report content to determine whether it meets the requirements for briefing completeness.

[0064] S203. When it is determined that the fault transmission conditions are met, a fault notification briefing message is sent after the first waiting time has elapsed.

[0065] Specifically, provided that the integrity requirements are met, the fault occurrence time can be used as a benchmark. After the first waiting period after the fault occurs (e.g., 5 minutes after the fault occurs), the fault notification briefing information can be sent. This will prevent mistransmission of information in the intermediate process and avoid users not receiving the complete fault notification briefing information, which could affect the progress of subsequent work.

[0066] S204. If it is determined that the fault transmission conditions are not met, new fault notification briefing information is continuously acquired and its integrity is verified. If the new fault notification briefing information still does not meet the fault transmission conditions after the second waiting period has elapsed, the target fault notification briefing information is sent. The target fault notification briefing information is the fault notification briefing information with the highest degree of integrity acquired within the second waiting period. The second waiting period is longer than the first waiting period.

[0067] Specifically, conversely, if the received fault notification summary does not meet the completeness requirements, the waiting time can be extended to continue acquiring relevant alarm information and performing continuous completeness verification. Simultaneously, to prevent indefinite waiting and ensure notification delivery for the user to handle subsequent faults, the most complete fault notification summary will be sent to the user after the second waiting period (e.g., 10 minutes).

[0068] This fault information notification method performs integrity checks on pre-received fault notification briefs. Based on the integrity check results, it employs a dual waiting time constraint mechanism to prevent the complete fault notification briefs from being sent prematurely, thus preventing mis-propagation of information during the intermediate process. If the fault notification briefs still do not meet the integrity requirements within the waiting time, the optimal version of the fault notification briefs is forcibly sent to prevent indefinite waiting and ensure that the notification is delivered. This effectively reduces the phenomenon of inaccurate information due to premature delivery and the impact of inefficient handling due to delayed delivery, improving the timeliness, accuracy, and reliability of fault information push.

[0069] In another embodiment, the fault information notification method further includes:

[0070] Determine the time difference between the time of the fault occurrence and the current system time, and terminate the sending of fault notification briefing information when the time difference exceeds a preset duration.

[0071] Specifically, to avoid the repeated push of outdated fault information affecting the accuracy of fault judgment results and causing interference, the corresponding time difference can be determined by comparing the time of the fault occurrence with the current system time. When the time difference exceeds the validity period (e.g., 8 hours), the fault notification briefing information will no longer be sent.

[0072] In another embodiment, to improve the effectiveness of alarm information notification and provide more effective reminders to users, the fault information notification method further includes:

[0073] If no confirmation message is received within the third waiting period after the target fault notification briefing is sent, a preset level notification mechanism will be activated to issue a reminder.

[0074] Specifically, by recording the delivery status of SMS messages and user responses, if no confirmation is received within a specified time, an escalation notification mechanism is activated (such as calling the on-duty supervisor).

[0075] In some embodiments, the above-mentioned integrity verification of the fault notification briefing information to determine whether the fault notification briefing information meets the fault sending conditions includes:

[0076] Keywords in the fault notification briefing information are identified and statistically analyzed to obtain the identification and statistical results.

[0077] Based on the identification statistics and judgment rules, determine whether the fault notification briefing information meets the fault sending conditions.

[0078] Specifically, identification statistics can be obtained by statistically analyzing key fields such as current, action, and fault filter in the fault notification briefing information;

[0079] If the current statistics are not greater than the sum of the action statistics and the fault filter statistics, then the fault notification briefing information meets the fault sending conditions.

[0080] For example, by analyzing the report text of detailed fault notification information and counting the number of times each key field appears, if the number of times "current" appears is greater than or equal to the number of times "action" appears plus the number of times "fault recorder" appears, it is determined that the information is "complete"; otherwise, it is marked as "to be supplemented".

[0081] In other specific implementations, the process of generating fault notification briefing information includes:

[0082] The alarm signals within the acquisition period are concatenated according to keywords and combined with the processed mileage code to generate a fault notification summary.

[0083] For example, fault notification information can be obtained by taking fields such as "fault start time", "plant name", "faulted equipment", "fault phase", "fault nature", "protection name", "protection action", "fault current", and "distance measurement" from the initial fault record and piecing them together to form a brief report.

[0084] As a specific implementation of the above fault information notification method, refer to Figure 3 As shown, the fault information notification method may include the following processing steps:

[0085] Receive initial fault signal and trigger briefing transmission:

[0086] When the system receives the first alarm signal from the relay protection device or SCADA system, it generates and sends a "briefing text message" within 30 seconds. The briefing content is generated by taking the "fault start time", "plant name", "fault equipment", "fault phase", "fault nature", "protection name", "protection action", "fault current", "distance measurement" and other fields from the initial fault record and splicing them together to form a briefing.

[0087] Initiate data collection and integrity verification:

[0088] The system continuously collects relevant data sources (including protection action records, fault waveforms, and log files) and updates the detailed reports to be sent, while verifying the completeness of the detailed report content.

[0089] - Preset set of key fields: {current, action, fault recorder};

[0090] - Analyze the detailed report text content and count the number of times each key field appears. When the number of times "current" appears is greater than or equal to the number of times "action" appears plus the number of times "fault recorder" appears, it is judged as "information complete"; otherwise, it is marked as "to be supplemented".

[0091] Implement a dual time control strategy:

[0092] Activate the minimum delay + maximum timeout dual constraint mechanism:

[0093] - Minimum delay time: Detailed reports must not be sent earlier than 5 minutes after the fault occurs to prevent mistransmission of information during the intermediate process;

[0094] - Maximum timeout: If the integrity condition is not met within 10 minutes since the failure occurred, the current best version will be forcibly sent;

[0095] Simultaneously perform historical data filtering:

[0096] - Compare the time of the fault occurrence with the current system time difference;

[0097] - If the preset validity period (e.g., 8 hours) is exceeded, the push notification will be canceled to avoid interference from outdated information.

[0098] Detailed reports will be sent in stages:

[0099] Detailed SMS messages will be sent when all of the following conditions are met:

[0100] 1. Minimum delay time (≥5 min) has been reached.

[0101] 2. Data integrity meets the requirements or has exceeded the maximum timeout period (≥10 min).

[0102] 3. The fault time did not exceed the effective period (≤8h).

[0103] The detailed report includes: a complete fault description, location information, and recommended handling procedure codes.

[0104] Finally, the system records the SMS delivery status and user response; if there is no confirmation feedback within the specified time, the escalation notification mechanism is activated (such as calling the duty manager).

[0105] It is understood that those skilled in the art can adjust and select the above-mentioned judgment parameters as needed, which will not be elaborated here.

[0106] As a specific application of the above-mentioned fault information notification method, taking the transmission of alarm information from the secondary system of a 110kV substation as an example, the specific processing steps include the following:

[0107] 1. At 10:00:00, the line protection device sends an "action" signal.

[0108] 2. At 10:00:20, the system sent a briefing SMS: "[Briefing] At 10:00, there was a fault on line #2 at a certain station, and a ground fault in phase A. Please pay attention."

[0109] 3. Begin collecting data such as waveform files and action sequences.

[0110] From 4:00 to 10:03:00, only partial data was obtained. The detailed report information was updated as follows: "[Detailed Report] 10:00 Fault on line #2 of a certain station, A-phase ground fault, PCS-931A differential protection tripped, fault current 14.47A; WXH-803A differential protection tripped, please pay attention." Integrity check: "Current" count 1 < ("Action" + "Fault Recorder") count 2, which does not meet the integrity requirement.

[0111] 5. The system enters a waiting state, but a timer is set to monitor the time.

[0112] 6. At 10:10:00 (10 minutes later), the integrity check fails, triggering "forced transmission after timeout".

[0113] 7. At the same time, the system checks that the fault occurred 6 minutes before the current time, which is less than 8 hours ago, and allows transmission.

[0114] 8. Send detailed report: "[Detailed report] At 10:00, a fault occurred on line #2 of a certain station, with a ground fault in phase A. The PCS-931A differential protection tripped, with a fault current of 14.47A; the WXH-803A differential protection also tripped. Please pay attention."

[0115] As can be seen from the above embodiments, the fault information notification method can effectively solve the problems in the prior art where notification is too early, leading to inaccurate information, or too late, affecting the efficiency of handling, thereby improving the timeliness, accuracy, and reliability of fault information push.

[0116] The above describes a fault information notification method provided by the embodiments of this application. The following describes the apparatus for performing the above fault information notification method.

[0117] Please see Figure 4 , Figure 4 This is a schematic diagram of a fault information notification device provided in an embodiment of this application. Figure 4 As shown, the fault information notification device includes:

[0118] The briefing information acquisition module 401 is used to acquire fault notification briefing information in response to the initial fault signal;

[0119] The briefing information verification module 402 is used to perform integrity verification on the fault notification briefing information and determine whether the fault notification briefing information meets the fault sending conditions.

[0120] The first sending execution module 403 is configured to send a fault notification briefing message after the first waiting period has elapsed, when the briefing information verification module 402 determines that the fault sending conditions are met; and,

[0121] The second sending execution module 404 is used to continuously acquire new fault notification briefing information and perform integrity verification when the briefing information verification module 402 determines that the fault sending conditions are not met. If the new fault notification briefing information still does not meet the fault sending conditions after the second waiting time has elapsed, the target fault notification briefing information is sent. The target fault notification briefing information is the fault notification briefing information with the highest degree of integrity acquired within the second waiting time. The second waiting time is longer than the first waiting time.

[0122] In one possible implementation, it also includes: a timeliness control module for determining the time difference between the time of the fault occurrence and the current system time, and terminating the transmission of the fault notification briefing information when the time difference exceeds a preset duration.

[0123] In one possible implementation, it also includes an alarm information escalation module, which is used to activate a preset level notification mechanism to remind the user if no notification confirmation information is received within the third waiting period after the target fault notification briefing information is sent.

[0124] In one possible implementation, the briefing information verification module 402 performs integrity verification on the fault notification briefing information to determine whether the fault notification briefing information meets the fault sending conditions, including:

[0125] Keyword identification and statistics were performed on fault notification briefing information to obtain identification and statistical results;

[0126] Based on the identification statistics and judgment rules, determine whether the fault notification briefing information meets the fault sending conditions.

[0127] In one possible implementation, the process of generating fault notification briefing information in the briefing information acquisition module 401 includes:

[0128] The alarm signals within the acquisition period are concatenated according to keywords and combined with the processed mileage code to generate a fault notification summary.

[0129] In one possible implementation, the briefing information verification module 402 identifies and statistically analyzes keywords in the fault notification briefing information to obtain the identification and statistical results, including:

[0130] The key fields of current, action, and fault filter in the fault notification briefing information are statistically analyzed to obtain the identification statistics;

[0131] Based on the identification statistics and judgment rules, determine whether the fault notification briefing information meets the fault sending conditions, including:

[0132] If the current statistics are not greater than the sum of the action statistics and the fault filter statistics, then the fault notification briefing information meets the fault sending conditions.

[0133] This application also provides an electronic device in its embodiments. (See reference...) Figure 5 The diagram illustrates a structural schematic suitable for implementing the electronic device in the embodiments of this application. The electronic device in the embodiments of this application may include, but is not limited to, fixed terminals such as laptops, desktop computers, etc. Figure 5 The electronic device shown is merely an example and should not impose any limitation on the functionality and scope of use of the embodiments of this application.

[0134] like Figure 5 As shown, the electronic device may include a processing unit (e.g., a central processing unit, a graphics processing unit, etc.) 501, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 502 or a program loaded from a storage device 508 into a random access memory (RAM) 503. When the electronic device is powered on, the RAM 503 also stores various programs and data required for the operation of the electronic device. The processing unit 501, ROM 502, and RAM 503 are interconnected via a bus 504. An input / output (I / O) interface 505 is also connected to the bus 504.

[0135] Typically, the following devices can be connected to I / O interface 505: input devices 506 including, for example, touchscreens, touchpads, keyboards, mice, cameras, microphones, accelerometers, gyroscopes, etc.; output devices 507 including, for example, liquid crystal displays (LCDs), speakers, vibrators, etc.; storage devices 508 including, for example, memory cards, hard drives, etc.; and communication devices 509. Communication device 509 allows electronic devices to communicate wirelessly or wiredly with other devices to exchange data. Although Figure 5 Electronic devices with various devices are shown, but it should be understood that it is not required to implement or have all of the devices shown. More or fewer devices may be implemented or have alternatively.

[0136] This application also provides a computer program product including computer-readable instructions, which, when executed on an electronic device, cause the electronic device to implement any of the fault information notification methods provided in this application.

[0137] This application also provides a computer-readable storage medium that carries one or more computer programs. When the one or more computer programs are executed by an electronic device, the electronic device can implement any of the fault information notification methods provided in this application.

[0138] It should also be noted that the device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate, and 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 network units. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs. In addition, in the device embodiment drawings provided in this application, the connection relationship between modules indicates that they have a communication connection, which can be implemented as one or more communication buses or signal lines.

[0139] Through the above description of the embodiments, those skilled in the art can clearly understand that this application can be implemented by means of software plus necessary general-purpose hardware, or it can be implemented by special-purpose hardware including application-specific integrated circuits, special-purpose CPUs, special-purpose memory, special-purpose components, etc. Generally, any function performed by a computer program can be easily implemented by corresponding hardware, and the specific hardware structure used to implement the same function can also be diverse, such as analog circuits, digital circuits, or special-purpose circuits. However, for this application, software program implementation is more often the preferred 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 readable storage medium, such as a computer floppy disk, USB flash drive, mobile hard disk, ROM, RAM, magnetic disk, or optical disk, etc., and includes several instructions to cause a computer device (which may be a personal computer, training equipment, or network device, etc.) to execute the methods described in the various embodiments of this application.

[0140] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented in software, it can be implemented, in whole or in part, as a computer program product.

[0141] The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions may be transmitted from one website, computer, training device, or data center to another website, computer, training device, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium may be any available medium that a computer can store or a data storage device such as a training device or data center that integrates one or more available media. The available media may be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., DVDs), or semiconductor media (e.g., solid-state drives (SSDs)).

Claims

1. A fault information notification method, characterized in that, include: In response to an initial fault signal, fault notification brief information is acquired; wherein, the process of generating the fault notification brief information includes: concatenating alarm signals within the acquisition period according to keywords and combining them with mileage codes to generate the fault notification brief information, wherein the fault notification brief information includes fault start time, plant name, fault equipment, fault phase, fault nature, protection name, protection action, fault current and distance measurement. The current, action, and fault filter in the fault notification briefing information are statistically analyzed to obtain identification statistics, which represent the number of times each key field appears. Based on the identification statistics and judgment rules, it is determined whether the fault notification briefing information meets the fault sending conditions. If the current statistics are not greater than the sum of the action statistics and the fault filter statistics, then it is determined that the fault notification briefing information meets the fault sending conditions. When it is determined that the fault sending conditions are met, the fault notification briefing information is sent after the first waiting time has elapsed. If the fault sending conditions are not met, new fault notification briefing information is continuously acquired and its integrity is verified. If the new fault notification briefing information still does not meet the fault sending conditions after the second waiting period has elapsed, a target fault notification briefing information is sent. The target fault notification briefing information is the fault notification briefing information with the highest integrity obtained within the second waiting period, and the second waiting period is longer than the first waiting period.

2. The fault information notification method according to claim 1, characterized in that, Also includes: Determine the time difference between the time of the fault occurrence and the current system time, and terminate the transmission of the fault notification briefing information when the time difference exceeds a preset duration.

3. The fault information notification method according to claim 1, characterized in that, Also includes: If no confirmation message is received within the third waiting period after the target fault notification briefing is sent, a preset level notification mechanism will be activated to issue a reminder.

4. A fault information notification device, characterized in that, include: The briefing information acquisition module is used to acquire fault notification briefing information in response to the initial fault signal; The briefing information verification module is used to perform integrity verification on the fault notification briefing information and determine whether the fault notification briefing information meets the fault sending conditions. The first sending execution module is used to send the fault notification briefing information after the first waiting time has elapsed when the briefing information verification module determines that the fault sending conditions are met. as well as, The second sending execution module is used to continuously acquire new fault notification briefing information and perform integrity verification when the briefing information verification module determines that the fault sending conditions are not met. If the new fault notification briefing information still does not meet the fault sending conditions after the second waiting time has elapsed, the target fault notification briefing information is sent. The target fault notification briefing information is the fault notification briefing information with the highest degree of completeness acquired within the second waiting time. The second waiting time is longer than the first waiting time. The briefing information verification module is used to perform integrity verification on the fault notification briefing information and determine whether the fault notification briefing information meets the fault sending conditions. This process includes: performing key field statistics on the current, action, and fault filter in the fault notification briefing information to obtain identification statistics results, where the identification statistics results represent the frequency of each key field occurrence; and determining whether the fault notification briefing information meets the fault sending conditions based on the identification statistics results and judgment rules. If the current statistics are not greater than the sum of the action statistics and the fault filter statistics, then the fault notification briefing information is determined to meet the fault sending conditions. The process of generating fault notification briefing information in the briefing information acquisition module 401 includes: concatenating alarm signals within the acquisition time according to keywords and combining them with mileage codes to generate fault notification briefing information. The fault notification briefing information includes fault start time, plant name, fault equipment, fault phase, fault nature, protection name, protection action, fault current, and distance measurement.

5. A computer program product, characterized in that, It includes computer-readable instructions that, when executed on an electronic device, cause the electronic device to implement the fault information notification method as described in any one of claims 1 to 3.

6. An electronic device, characterized in that, It includes at least one processor and a memory connected to the processor, wherein: The memory is used to store computer programs; The processor is used to execute the computer program to enable the electronic device to implement the fault information notification method as described in any one of claims 1 to 3.

7. A computer storage medium, characterized in that, The storage medium carries one or more computer programs that, when executed by an electronic device, enable the electronic device to implement the fault information notification method as described in any one of claims 1 to 3.

Images