Fault handling method and system considering timeliness of substation fault recording files

Abstract

The present invention belongs to the technical field of data transmission and processing, and provides a fault processing method and system that considers the timeliness of transformer substation fault recording files. After obtaining the transformer substation recording file, it is determined whether the recording file exists in a preset hash table; wherein the hash table is a hash table that associates multiple recording files of different formats with a fault object, and the multiple recording files of different formats are associated with the same fault object; it is determined whether all the multiple fault recording files of different formats are preset in the recording file; if all the preset types of fault recording files exist, a fault processing thread is executed, otherwise the recording file acquisition continues. By creating a hash table that associates multiple recording files of different formats with the fault object, and the multiple recording files of different formats are associated with the same fault object, the purpose of determining whether multiple recording files have been received can be achieved by only querying the fault object, thereby improving the time efficiency of fault analysis.

Description

Technical Field

[0001] The present invention belongs to the technical field of data transmission and processing, and in particular relates to a fault processing method and system considering the timeliness of substation fault recording files. Background Art

[0002] In the high-reliability substation control system, after a fault occurs, the integrated main and auxiliary monitoring host platform pushes the summoned recording file list to the smart alarm app, and then the smart alarm requests the platform for each file in the list in turn. Only when all three files are received can the next step of fault analysis be carried out; the recording files include three files: dat, cfg, and hdr.

[0003] The inventors have found that currently, when determining whether the three files, dat file, cfg file and hdr file, have been received, when requesting the first file, a timer is started to periodically query whether all three files exist, and the timer is ended when all three files exist; however, the query method by starting the timer has poor timeliness, and it is almost impossible to analyze all three files immediately after they are received, which cannot meet the high real-time requirements of the intelligent alarm app for fault analysis. Summary of the Invention

[0004] In order to solve the above problems, the present invention proposes a fault handling method and system that takes into account the timeliness of substation fault recording files. The present invention creates a hash table that associates multiple recording files in different formats with fault objects. Multiple recording files in different formats are associated with the same fault object, so that the purpose of determining whether multiple recording files have been received can be achieved by only querying the fault object, thereby improving the time efficiency of fault analysis and meeting the high real-time requirements of high-reliability substations.

[0005] In order to achieve the above object, the present invention is implemented through the following technical solutions:

[0006] In a first aspect, the present invention provides a fault handling method that considers the timeliness of substation fault recording files, comprising:

[0007] Obtain the substation recording file;

[0008] Determine whether the recording file exists in a preset hash table; if so, determine the fault object associated with the recording file in the hash table; otherwise, terminate the query; wherein the hash table is a hash table that associates multiple recording files of different formats with fault objects, and multiple recording files of different formats are associated with the same fault object;

[0009] Deleting the key-value pair of the recording file and the fault object in the hash table;

[0010] If the associated fault object is empty or fault analysis is in progress, the query is terminated; otherwise, it is determined whether there are multiple fault recording files of all preset different formats in the recording file; if there are fault recording files of all preset types, the fault processing thread is executed; otherwise, the recording file is continued to be obtained.

[0011] Furthermore, after a fault occurs, a file list of the recording file is received; the file list is divided into one or more fault groups; and it is determined whether the fault has been processed. If so, data processing is terminated; otherwise, a fault object is created according to the file list of each fault.

[0012] Furthermore, if the fault object satisfies the naming conventions of the fault file, conforms to the subscribed fault, and the file list of each fault includes at least files of a preset format and type, then the fault object is considered valid; otherwise, it is invalid.

[0013] Furthermore, if the recording file of the substation is not received within a preset time, the created fault object is deleted.

[0014] Furthermore, the plurality of recording files are dat files, cfg files and hdr files.

[0015] Furthermore, the key-value pairs in the hash table include dat file and fault object, cfg file and fault object, and hdr file and fault object.

[0016] In a second aspect, the present invention further provides a fault handling system that takes into account the timeliness of substation fault recording files, including:

[0017] The data acquisition module is configured to: obtain the waveform recording file of the substation;

[0018] The judgment module is configured to: determine whether the recording file exists in a preset hash table; if so, determine the fault object associated with the recording file in the hash table; otherwise, terminate the query; wherein the hash table is a hash table that associates multiple recording files of different formats with fault objects, and multiple recording files of different formats are associated with the same fault object;

[0019] A deletion module is configured to: delete the key-value pair of the recording file and the fault object in the hash table;

[0020] The fault handling module is configured as follows: if the associated fault object is empty or fault analysis is in progress, the query is terminated; otherwise, it is determined whether there are multiple fault recording files of all preset different formats in the recording file; if there are fault recording files of all preset types, the fault handling thread is executed; otherwise, the recording file is continued to be obtained.

[0021] In a third aspect, the present invention further provides a computer-readable storage medium storing a computer program, which, when executed by a processor, implements the steps of the fault handling method considering the timeliness of the substation fault recording file as described in the first aspect.

[0022] In a fourth aspect, the present invention also provides an electronic device comprising a memory, a processor, and a computer program stored in the memory and capable of running on the processor. When the processor executes the program, the steps of the fault handling method considering the timeliness of the substation fault recording file as described in the first aspect are implemented.

[0023] In a fifth aspect, the present invention further provides a computer program product, which includes a computer program. When the computer program is executed by a processor, it implements the steps of the fault handling method considering the timeliness of the substation fault recording file as described in the first aspect.

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

[0025] After obtaining a recording file of a substation, the present invention determines whether the recording file exists in a preset hash table. If so, the fault object associated with the recording file in the hash table is determined, otherwise the query is terminated; wherein the hash table is a hash table that associates multiple recording files of different formats with a fault object, and multiple recording files of different formats are associated with one same fault object; if the associated fault object is empty or fault analysis is in progress, the query is terminated, otherwise it is determined whether all multiple fault recording files of different formats are preset in the recording file; if all preset types of fault recording files exist, the fault processing thread is executed, otherwise the recording file is continued to be obtained. By creating a hash table that associates multiple recording files of different formats with a fault object, and multiple recording files of different formats are associated with one same fault object, the purpose of determining whether multiple recording files are received by only querying the fault object is achieved, thereby improving the time efficiency of fault analysis and meeting the high real-time performance requirements of a highly reliable substation. BRIEF DESCRIPTION OF THE DRAWINGS

[0026] The drawings constituting a part of the specification of this embodiment are used to provide a further understanding of this embodiment. The schematic embodiments and descriptions of this embodiment are used to explain this embodiment and do not constitute an improper limitation on this embodiment.

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

[0028] The present invention will be further described below with reference to the accompanying drawings and embodiments.

[0029] It should be noted that the following detailed descriptions are exemplary and are intended to provide further explanation of the present application. Unless otherwise specified, all technical and scientific terms used herein have the same meaning as commonly understood by those skilled in the art to which the present application belongs.

[0030] Example 1:

[0031] The timer query method has poor timeliness and can hardly be analyzed immediately after all three files are received. This fails to meet the high real-time requirements of fault analysis by the smart alarm app. In some embodiments, a fault handling method that considers the timeliness of substation fault recording files is provided, including:

[0032] Obtain the substation recording file;

[0033] Determine whether the recording file exists in a preset hash table; if so, determine the fault object associated with the recording file in the hash table; otherwise, terminate the query; wherein the hash table is a hash table that associates multiple recording files of different formats with fault objects, and multiple recording files of different formats are associated with the same fault object;

[0034] Deleting the key-value pair of the recording file and the fault object in the hash table;

[0035] If the associated fault object is empty or fault analysis is in progress, the query is terminated; otherwise, it is determined whether there are multiple fault recording files of all preset different formats in the recording file; if there are fault recording files of all preset types, the fault processing thread is executed; otherwise, the recording file is continued to be obtained.

[0036] In some embodiments, after receiving a list of fault recording files including dat files, cfg files and hdr files, a fault object is created, and then a hash table associating three file names and fault objects is created. The three file names are all associated with the same fault object. Finally, the platform is requested to send these three files in turn, and the platform is waited for to push the requested files to the App.

[0037] After receiving the file pushed by the platform, the fault object corresponding to the file in the hash table is obtained. If the obtained fault object is not empty and has not started running, then if the three files are received, the analysis process of the fault object is started. This is very time-sensitive and can meet the high real-time requirements of the intelligent alarm app for fault analysis. Figure 1 As shown, the specific implementation steps of this embodiment may include:

[0038] S1. The intelligent alarm app subscribes to the fault information of related devices from the main and auxiliary integrated platform.

[0039] The Smart Alarm App is an optional app client with data processing and transmission capabilities. The integrated primary and secondary platform is an integrated monitoring platform for primary and secondary equipment in smart substations. Subscription can be understood as the Smart Alarm App receiving information from the integrated primary and secondary platform. Related device and fault information refers to information related to substation equipment and faults. Specific equipment and information content can be determined based on monitoring or other requirements, and will not be detailed here.

[0040] S2. After a fault occurs, the protection or recording device will generate a recording signal and file. After the background retrieves the recording file of the device, it pushes the file list to the smart alarm app.

[0041] S3. The smart alarm app processes the received file list and divides it into one or more fault groups. It then determines whether the fault has been processed. If it has been processed, it ends the data processing. If it has not been processed, it proceeds to step S4.

[0042] It can be understood that the smart alarm app processes the received file list and divides it into one or more fault groups. During the grouping process, a member that records the fault time is created for the fault group. A map is set in the app to record the fault groups that have been processed. The map is a key-value pair that associates the fault time with the time when the grouping was performed. Whether the fault is processed is determined based on whether the fault time of the fault is included in the map. If the time is included in the map, it means that it has been processed. If the time is not included in the map, it means that it has not been processed, and the time of the fault must be added to the map.

[0043] S4. Create a fault object according to the file list of each fault.

[0044] S5. Check whether the fault object is valid. If it is valid, proceed to step S6; otherwise, end the process.

[0045] Optionally, the criteria for whether a fault object is valid is that the naming conforms to the naming conventions of the fault file, conforms to the subscribed fault, and the file list for each fault includes at least three files; among which, optionally, the naming convention ends with -_F or _f, and the three files are the dat file, the cfg file, and the hdr file.

[0046] S6. Associate the fault timeout signal and processing function; the purpose of step S6 is to delete the created fault object if the smart alarm app does not receive the file sent by the primary and secondary integrated platform for a long time, for example, if the file sent by the primary and secondary integrated platform is not received for 10 minutes or more.

[0047] S7. The intelligent alarm app asynchronously requests fault files from the primary and secondary integrated platforms in sequence according to the file list, that is, requests the dat file, cfg file, and hdr file in sequence.

[0048] S8. Add all requested files to a hash table, which consists of file name-fault object key-value pairs. Optionally, create dat file-fault object key-value pairs, cfg file-fault object key-value pairs, and hdr file-fault object key-value pairs in sequence.

[0049] S9. The smart alarm app receives the request file sent back by the platform and parses it. It first determines whether the hash table contains the file name. If not, the process ends. If included, the fault object associated with the file in the hash table is obtained, and then the file-fault object key-value pair is deleted from the hash table. If the fault object is empty or fault analysis is in progress, the process ends, otherwise step S10.

[0050] S10. Check whether the three files of the fault object have all been summoned, that is, have all been received; if all have been received, start the fault processing thread, otherwise continue to wait for the request file sent by the platform.

[0051] This embodiment can complete the transmission of fault recording files from the main and auxiliary integrated platform to the intelligent alarm app, and conduct fault analysis in a timely manner, which can improve the time efficiency of fault analysis and meet the high real-time requirements of high-reliability substations.

[0052] Example 2:

[0053] This embodiment provides a fault handling system that considers the timeliness of substation fault recording files, including:

[0054] The data acquisition module is configured to: obtain the waveform recording file of the substation;

[0055] The judgment module is configured to: determine whether the recording file exists in a preset hash table; if so, determine the fault object associated with the recording file in the hash table; otherwise, terminate the query; wherein the hash table is a hash table that associates multiple recording files of different formats with fault objects, and multiple recording files of different formats are associated with the same fault object;

[0056] A deletion module is configured to: delete the key-value pair of the recording file and the fault object in the hash table;

[0057] The fault handling module is configured as follows: if the associated fault object is empty or fault analysis is in progress, the query is terminated; otherwise, it is determined whether there are multiple fault recording files of all preset different formats in the recording file; if there are fault recording files of all preset types, the fault handling thread is executed; otherwise, the recording file is continued to be obtained.

[0058] The working method of the system is the same as the fault handling method considering the timeliness of the substation fault recording file in Example 1, and will not be repeated here.

[0059] Example 3:

[0060] This embodiment provides a computer-readable storage medium having a computer program stored thereon. When the program is executed by a processor, the steps of the fault handling method considering the timeliness of the substation fault recording file described in Example 1 are implemented.

[0061] Example 4:

[0062] This embodiment provides an electronic device, including a memory, a processor, and a computer program stored in the memory and capable of running on the processor. When the processor executes the program, the steps of the fault handling method considering the timeliness of the substation fault recording file described in Example 1 are implemented.

[0063] Example 5:

[0064] This embodiment provides a computer program product, which includes a computer program. When the computer program is executed by a processor, the steps of the fault handling method considering the timeliness of the substation fault recording file described in Example 1 are implemented.

[0065] The above description is merely a preferred embodiment of this embodiment and is not intended to limit this embodiment. Those skilled in the art will readily appreciate that this embodiment may be modified and varied in various ways. Any modifications, equivalent substitutions, or improvements made within the spirit and principles of this embodiment shall be within the scope of protection of this embodiment.

Claims

1. A fault handling method considering the timeliness of substation fault recording files is characterized by: include: Obtain the substation recording file; Determine whether the recording file exists in a preset hash table; if so, determine the fault object associated with the recording file in the hash table; otherwise, terminate the query; wherein the hash table is a hash table that associates multiple recording files of different formats with fault objects, and multiple recording files of different formats are associated with the same fault object; Multiple recording files include dat files, cfg files and hdr files; Deleting the key-value pair of the recording file and the fault object in the hash table; The key-value pairs in the hash table include dat file and fault object, cfg file and fault object, and hdr file and fault object; First, determine whether the hash table contains the dat file, cfg file, or hdr file. If not, end the process. If included, obtain the fault object associated with the file in the hash table, and then delete the key-value pair of the file and the fault object in the hash table. If the associated fault object is empty or fault analysis is in progress, the query is terminated. Otherwise, it is determined whether there are multiple fault recording files of all preset different formats in the recording file; if all preset types of fault recording files exist, the fault processing thread is executed, otherwise, the recording file is continued to be acquired; After a fault occurs, a file list of recording files is received; the file list is divided into one or more fault groups; and it is determined whether the fault has been processed. If so, data processing is terminated; otherwise, a fault object is created according to the file list of each fault.

2. The fault handling method considering the timeliness of substation fault recording files according to claim 1, characterized in that: If the fault object meets the naming conventions of the fault file, meets the subscribed fault, and the file list of each fault includes at least files of the preset format and type, then the fault object is considered valid; otherwise, it is invalid.

3. The fault handling method considering the timeliness of substation fault recording files according to claim 1, characterized in that: If the recording file of the substation is not received within the preset time, the created fault object will be deleted.

4. A fault handling system that takes into account the timeliness of substation fault recording files is characterized by: include: The data acquisition module is configured to: obtain the waveform recording file of the substation; The judgment module is configured to: determine whether the recording file exists in a preset hash table; if so, determine the fault object associated with the recording file in the hash table; otherwise, terminate the query; wherein the hash table is a hash table that associates multiple recording files of different formats with fault objects, and multiple recording files of different formats are associated with the same fault object; Multiple recording files include dat files, cfg files and hdr files; A deletion module is configured to: delete the key-value pair of the recording file and the fault object in the hash table; The key-value pairs in the hash table include dat file and fault object, cfg file and fault object, and hdr file and fault object; The fault processing module is configured to: first determine whether the hash table includes the dat file, cfg file, or hdr file; if not, terminate the process; if included, obtain the fault object associated with the file in the hash table; and then delete the key-value pair of the file and the fault object in the hash table; If the associated fault object is empty or fault analysis is in progress, the query is terminated. Otherwise, it is determined whether there are multiple fault recording files of all preset different formats in the recording file; if all preset types of fault recording files exist, the fault processing thread is executed, otherwise, the recording file is continued to be acquired; After a fault occurs, a file list of recording files is received; the file list is divided into one or more fault groups; and it is determined whether the fault has been processed. If so, data processing is terminated; otherwise, a fault object is created according to the file list of each fault.

5. The fault handling system considering the timeliness of substation fault recording files according to claim 4 is characterized in that: If the fault object meets the naming conventions of the fault file, meets the subscribed fault, and the file list of each fault includes at least files of the preset format and type, then the fault object is considered valid; otherwise, it is invalid.

6. The fault handling system considering the timeliness of substation fault recording files according to claim 4, characterized in that: If the recording file of the substation is not received within the preset time, the created fault object will be deleted.

7. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the program is executed by a processor, the steps of the fault handling method considering the timeliness of the substation fault recording file as described in any one of claims 1 to 3 are implemented.

8. An electronic device comprising a memory, a processor, and a computer program stored in the memory and capable of running on the processor, characterized in that: When the processor executes the program, the steps of the fault handling method considering the timeliness of the substation fault recording file as described in any one of claims 1 to 3 are implemented.

9. A computer program product, characterized in that The computer program product includes a computer program. When the computer program is executed by a processor, the steps of the fault handling method considering the timeliness of the substation fault recording file are implemented as described in any one of claims 1 to 3.

Images