Fault processing method and system considering timeliness of transformer substation fault recording file

Abstract

The invention belongs to the technical field of data transmission and processing, and provides a fault processing method and system considering the timeliness of a fault recording file of a transformer substation, and the method comprises the steps: obtaining the recording file of the transformer substation, and judging whether the recording file exists in a preset hash table; wherein the hash table is a hash table in which a plurality of wave recording files in different formats are associated with the fault object, and the plurality of wave recording files in different formats are associated with the same fault object; judging whether a plurality of fault recording files with different preset formats exist in the recording file or not; and if all the preset types of fault recording files exist, performing a fault processing thread, otherwise, continuing to obtain the recording files. According to the method, the Hash table for associating the plurality of wave recording files in different formats with the fault object is created, and the plurality of wave recording files in different formats are associated with the same fault object, so that the purpose of determining whether the plurality of wave recording files are received by only querying the fault object is achieved, and the time efficiency of fault analysis is improved.

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 a transformer substation fault recording file. Background Art

[0002] In the high-reliability substation control layer system, after a fault occurs, the main and auxiliary integrated monitoring host platform will push the summoned recording file list to the smart alarm App, and then the smart alarm will request 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 performed; the recording files include three files: dat, cfg and hdr.

[0003] The inventor has found that, currently, when judging whether the three files, dat file, cfg file and hdr file, are received, when requesting the first file, a timer is started to periodically query whether the three files exist, and the timer is ended when they exist; however, the query method by starting the timer has poor timeliness, and it is almost impossible to analyze the 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 taking 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 a fault object. Multiple recording files in different formats are associated with a same fault object, thereby achieving the purpose of determining whether multiple recording files have been received 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: In a first aspect, the present invention provides a fault handling method considering the timeliness of a substation fault recording file, comprising: Get the recording file of the substation; Determine whether the wave recording file exists in a preset hash table, and if so, determine the fault object associated with the wave recording file in the hash table, otherwise terminate the query; wherein the hash table is a hash table in which multiple wave recording files of different formats are associated with the fault object, and multiple wave recording files of different formats are associated with a same fault object; Deleting the key-value pair of the recording 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 there are fault recording files of all preset types, the fault processing thread is executed, otherwise the recording file is continued to be obtained.

[0006] Furthermore, after a fault occurs, a file list of recording files is received; the file list is divided into one or more fault groups; 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.

[0007] Furthermore, if the fault object satisfies the naming convention 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 judged to be valid; otherwise, it is invalid.

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

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

[0010] 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.

[0011] In a second aspect, the present invention further provides a fault handling system taking into account the timeliness of substation fault recording files, comprising: The data acquisition module is configured to: obtain the wave recording file of the substation; The judgment module is configured to: judge whether the recording file exists in a preset hash table, and 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 in which multiple recording files of different formats are associated with the fault object, and multiple recording files of different formats are associated with a same fault object; A deletion module is configured to: delete the key-value pair of the recording file and the fault object in the hash table; The fault processing 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 processing thread is executed; otherwise, the recording file is continued to be obtained.

[0012] In a third aspect, the present invention further provides a computer-readable storage medium having a computer program stored thereon, 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.

[0013] In a fourth aspect, the present invention further provides an electronic device comprising a memory, a processor, and a computer program stored in the memory and capable of running on the processor, wherein 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.

[0014] 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, the steps of the fault handling method considering the timeliness of the substation fault recording file described in the first aspect are implemented.

[0015] Compared with the prior art, the present invention has the following beneficial effects: After the present invention obtains the recording file of the substation, it is determined 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 in which multiple recording files of different formats are associated with the 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 performed, otherwise the recording file is continued to be obtained. By creating a hash table in which multiple recording files of different formats are associated with the 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, the time efficiency of fault analysis is improved, and the high real-time requirements of a high-reliability substation are met. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] The drawings in the specification that constitute a part of this embodiment are used to provide a further understanding of this embodiment. The schematic embodiments of this embodiment and their descriptions are used to explain this embodiment and do not constitute improper limitations on this embodiment.

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

[0018] The present invention will be further described below in conjunction with the accompanying drawings and embodiments.

[0019] 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 meanings as those commonly understood by those skilled in the art to which the present application belongs.

[0020] Embodiment 1: The timer query method has poor timeliness and can hardly be analyzed immediately after all three files are received, which cannot meet the high real-time requirements of the intelligent alarm App for fault analysis. In some embodiments, a fault handling method considering the timeliness of the substation fault recording file is provided, including: Get the recording file of the substation; Determine whether the wave recording file exists in a preset hash table, and if so, determine the fault object associated with the wave recording file in the hash table, otherwise terminate the query; wherein the hash table is a hash table in which multiple wave recording files of different formats are associated with the fault object, and multiple wave recording files of different formats are associated with a same fault object; Deleting the key-value pair of the recording 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 there are fault recording files of all preset types, the fault processing thread is executed, otherwise the recording file is continued to be obtained.

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

[0022] After receiving the file pushed by the platform, obtain the fault object corresponding to the file in the hash table. If the obtained fault object is not empty and has not started running, then check if all three files are received and start the analysis process of the fault object. This is very time-effective and can meet the high real-time requirements of the smart alarm app for fault analysis. Figure 1 As shown, the specific implementation steps of this embodiment may include: S1. The intelligent alarm app subscribes to the fault information of related devices from the main and auxiliary integrated platform.

[0023] Optionally, the smart alarm app is an app client with functions such as data processing and transmission; the main and auxiliary integrated platform is the integrated monitoring platform for main and auxiliary equipment of smart substations and other equipment; subscription can be understood as the smart alarm app receiving information from the main and auxiliary integrated platform. The relevant devices and fault information are all related equipment and fault information in the substation. The specific equipment and information content can be determined according to monitoring needs or other needs, and will not be described in detail.

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

[0025] S3. The smart alarm App processes the received file list and divides it into one or more fault groups, and determines in turn whether the fault has been processed. If it has been processed, the data processing ends; if it has not been processed, proceed to step S4.

[0026] 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. The map records 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 occurs. Whether the fault has been processed is determined based on whether the map contains the fault time of the fault. If the map contains the time, it means that it has been processed. If the map does not contain the time, it means that it has not been processed, and the time of the fault should be added to the map.

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

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

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

[0030] S6. Associate the fault timeout signal and the processing function; the purpose of step S6 is to delete the created fault object if the smart alarm App has not received 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 has not been received for 10 minutes or more.

[0031] 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 dat files, cfg files, and hdr files in sequence.

[0032] S8. Add all requested files to a hash table, which is composed 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.

[0033] S9. The smart alarm App receives the request file sent back by the platform and parses it. It first determines whether the hash table includes 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.

[0034] 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.

[0035] This embodiment can complete the transmission of the fault recording file from the main and auxiliary integrated platform to the intelligent alarm App, and perform 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.

[0036] Embodiment 2: This embodiment provides a fault handling system that takes into account the timeliness of substation fault recording files, including: The data acquisition module is configured to: obtain the wave recording file of the substation; The judgment module is configured to: judge whether the recording file exists in a preset hash table, and 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 in which multiple recording files of different formats are associated with the fault object, and multiple recording files of different formats are associated with a same fault object; A deletion module is configured to: delete the key-value pair of the recording file and the fault object in the hash table; The fault processing 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 processing thread is executed; otherwise, the recording file is continued to be obtained.

[0037] 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.

[0038] Embodiment 3: This embodiment provides a computer-readable storage medium on which a computer program is stored. 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.

[0039] Embodiment 4: 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.

[0040] Embodiment 5: 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.

[0041] The above description is only a preferred embodiment of the present embodiment and is not intended to limit the present embodiment. For those skilled in the art, the present embodiment may have various modifications and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present embodiment shall be included in the protection scope of the present embodiment.

Claims

1. A fault handling method considering the timeliness of substation fault recording files, characterized in that: include: Get the recording file of the substation; Determine whether the wave recording file exists in a preset hash table, and if so, determine the fault object associated with the wave recording file in the hash table, otherwise terminate the query; wherein the hash table is a hash table in which multiple wave recording files of different formats are associated with the fault object, and multiple wave recording files of different formats are associated with a same fault object; Deleting the key-value pair of the recording 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 there are fault recording files of all preset types, the fault processing thread is executed, otherwise the recording file is continued to be obtained.

2. The fault handling method considering the timeliness of the substation fault recording file according to claim 1 is characterized in that: After a fault occurs, a file list of recording files is received; the file list is divided into one or more fault groups; 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.

3. The fault handling method considering the timeliness of the substation fault recording file according to claim 1 is characterized in that: If the fault object meets the naming conventions of the fault file, meets the subscribed faults, 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.

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

5. The fault handling method considering the timeliness of the substation fault recording file according to claim 1 is characterized in that: Multiple recording files include dat files, cfg files and hdr files.

6. The fault handling method considering the timeliness of the substation fault recording file according to claim 1, characterized in that: 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.

7. A fault handling system considering the timeliness of substation fault recording files, characterized in that: include: The data acquisition module is configured to: obtain the wave recording file of the substation; The judgment module is configured to: judge whether the recording file exists in a preset hash table, and 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 in which multiple recording files of different formats are associated with the fault object, and multiple recording files of different formats are associated with a same fault object; A deletion module is configured to: delete the key-value pair of the recording file and the fault object in the hash table; The fault processing 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 processing thread is executed; otherwise, the recording file is continued to be obtained.

8. 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 6 are implemented.

9. 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 6 are implemented.

10. A computer program product, characterized in that The computer program product includes a computer program, and 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 as described in any one of claims 1 to 6 are implemented.

Images