A fault data processing method and terminal

Abstract

This invention discloses a fault data processing method and terminal, which receives fault reporting information and fault detail data from devices in real time; simultaneously, upon receiving the fault reporting information, it writes the fault time and the associated device from the fault reporting information into a search engine database; and it writes the fault detail data into a time-series database. This invention allows users to query the search engine database when they need to view fault data for quick search results, and to use the time-series database when they want to view detailed fault data. Leveraging the superior performance and compression capabilities of the time-series database, the querying and analysis of massive amounts of data becomes much faster. This not only reduces the pressure on the database when storing fault data but also facilitates rapid retrieval of fault data later.

Description

Technical Field

[0001] This invention relates to the field of fault handling technology, and in particular to a fault data processing method and terminal. Background Technology

[0002] Photovoltaic-storage charging stations need to ensure the health of all operating modules, so they collect module status data and issue alarms for unhealthy or abnormal modules. A large amount of fault data is generated before the modules return to normal. How to store the fault data and how to quickly retrieve it play a crucial role in its tracking and analysis.

[0003] During a module failure, fault data is continuously uploaded, resulting in a massive amount of data generated from a single failure. The traditional approach is to store this data in a relational database, such as MySQL, and then shard and partition the database, identifying each failure based on its upload interval. However, even with database sharding and partitioning, searching massive amounts of data becomes slow and data management becomes difficult.

[0004] In this scenario, users should ultimately receive the merged data when querying for faults. However, in reality, the query requires retrieving all data, which, due to the massive amount of data, causes a surge in pressure on the relational database. Even viewing the raw IoT data puts significant strain on the relational database, making it difficult to quickly retrieve the desired fault data. Summary of the Invention

[0005] The technical problem to be solved by the present invention is to provide a fault data processing method and terminal that can not only reduce the pressure on the database when storing fault data, but also facilitate the rapid retrieval of fault data later.

[0006] To solve the above-mentioned technical problems, the technical solution adopted by the present invention is as follows:

[0007] A fault data processing method includes the following steps:

[0008] S1. Receive fault reporting information and fault details from the equipment in real time;

[0009] S2. Upon receiving the fault reporting information, write the fault time and the associated device in the fault reporting information into the search engine database;

[0010] S3. Write the fault details data into the time series database.

[0011] To solve the above-mentioned technical problems, another technical solution adopted by the present invention is as follows:

[0012] A fault data processing terminal includes a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, it performs the following steps:

[0013] S1. Receive fault reporting information and fault details from the equipment in real time;

[0014] S2. Upon receiving the fault reporting information, write the fault time and the associated device in the fault reporting information into the search engine database;

[0015] S3. Write the fault details data into the time series database.

[0016] The beneficial effects of this invention are as follows: It provides a fault data processing method and terminal. When a device malfunctions, the fault time and the device to which it belongs in the fault report information sent by the device are written into a search engine database. The fault details data continuously generated by the device during the fault period are written into a time-series database. When a user needs to view fault data, they can query the search engine database to quickly obtain search results. When a user wants to view fault details, they can use the time-series database to query. Relying on the superior performance and compression capabilities of the time-series database, the querying and analysis of massive amounts of data becomes faster. Thus, when storing fault data, it not only reduces the pressure on the database but also facilitates the rapid retrieval of fault data later. Attached Figure Description

[0017] Figure 1 This is a flowchart illustrating a fault data processing method according to the present invention.

[0018] Figure 2 Diagram of the existing fault handling architecture;

[0019] Figure 3 This is a fault handling architecture diagram related to an embodiment of the present invention;

[0020] Figure 4 This is a schematic diagram of the structure of a fault data processing terminal according to an embodiment of the present invention.

[0021] Label Explanation:

[0022] 1. A fault data processing terminal; 2. Processor; 3. Memory; 4. Device; 5. Gateway; 6. Relational database; 7. Client; 8. Search engine library; 9. Time series database. Detailed Implementation

[0023] To explain in detail the technical content, objectives, and effects of the present invention, the following description is provided in conjunction with the embodiments and accompanying drawings.

[0024] Please refer to Figure 1 and Figure 3 A fault data processing method, comprising the following steps:

[0025] S1. Receive fault reporting information and fault detail data from device 4 in real time;

[0026] S2. Upon receiving the fault reporting information, write the fault time and the associated device in the fault reporting information into the search engine database 8;

[0027] S3. Write the fault details data into the time series database 9.

[0028] As can be seen from the above description, the beneficial effects of the present invention are as follows: It provides a fault data processing method and terminal. When the device 4 malfunctions, the fault time and the device to which it belongs in the fault report information sent by the device 4 are written into the search engine database 8, and the fault detail data continuously generated by the device 4 during the fault period are written into the time series database 9. When the user needs to view the fault data, he / she can query the search engine database 8 to quickly obtain the search results. When the user wants to view the fault details data, he / she can use the time series database 9 to query. Relying on the super performance and compression capability of the time series database 9, the query and analysis of massive amounts of data will become faster. Thus, when storing fault data, it can not only reduce the pressure on the database, but also facilitate the rapid retrieval of fault data later.

[0029] Furthermore, step S2 also includes:

[0030] The fault time and the associated device are stored in the cache and a fault notification is sent to the user terminal.

[0031] As can be seen from the above description, the fault time and the associated device are stored in the cache area to facilitate the statistics of all fault reports during this fault period. The fault notification, including the fault time and the associated device, is sent to the user terminal 7 so that the user can understand some general information about the fault in advance.

[0032] Furthermore, after step S3, the method further includes:

[0033] S4. In real time, determine whether a fault recovery notification has been received. If so, integrate all the fault times and associated devices within the cache during this fault period, as well as the fault recovery notification, to obtain information on the recovered fault devices and update the search engine database 8. Otherwise, continue with step S1.

[0034] As can be seen from the above description, receiving the first fault report means entering the fault period; receiving the fault recovery notification means exiting the fault period. All fault times and associated equipment during the fault period are integrated with the last fault recovery notification to obtain information on recovered fault equipment and update the search engine database 8, so that users can directly view the fault information of a single fault period and understand the recovery status of the fault when searching later.

[0035] Furthermore, the fault notification includes a query button that links to the search window of the search engine library 8.

[0036] As can be seen from the above description, a query button is provided at the same time as sending the fault notification, so that users can directly query the stored content of search engine library 8 to understand the fault details.

[0037] Furthermore, S3 specifically refers to:

[0038] Based on the classification of the equipment to which it belongs, the detailed fault data is written into the time-series database 9.

[0039] As can be seen from the above description, classifying and summarizing the fault details of faulty device 4 can improve search efficiency when users query data.

[0040] Please refer to Figure 4 A fault data processing terminal 1 includes a memory 3, a processor 2, and a computer program stored in the memory 3 and executable on the processor 2. When the processor 2 executes the computer program, it performs the following steps:

[0041] S1. Receive fault reporting information and fault detail data from device 4 in real time;

[0042] S2. Upon receiving the fault reporting information, write the fault time and the associated device in the fault reporting information into the search engine database 8;

[0043] S3. Write the fault details data into the time series database 9.

[0044] As can be seen from the above description, the beneficial effects of the present invention are as follows: It provides a fault data processing method and terminal. When the device 4 malfunctions, the fault time and the device to which it belongs in the fault report information sent by the device 4 are written into the search engine database 8, and the fault detail data continuously generated by the device 4 during the fault period are written into the time series database 9. When the user needs to view the fault data, he / she can query the search engine database 8 to quickly obtain the search results. When the user wants to view the fault details data, he / she can use the time series database 9 to query. Relying on the super performance and compression capability of the time series database 9, the query and analysis of massive amounts of data will become faster. Thus, when storing fault data, it can not only reduce the pressure on the database, but also facilitate the rapid retrieval of fault data later.

[0045] Furthermore, step S2 also includes:

[0046] The fault time and the associated device are stored in the cache and a fault notification is sent to the user terminal.

[0047] As can be seen from the above description, the fault time and the associated device are stored in the cache area to facilitate the statistics of all fault reports during this fault period. The fault time and the associated device are sent to the user terminal 7 to facilitate the user to understand some general information about the fault in advance.

[0048] Furthermore, after step S3, the method further includes:

[0049] S4. In real time, determine whether a fault recovery notification has been received. If so, integrate all the fault times and associated devices within the cache during this fault period, as well as the fault recovery notification, to obtain information on the recovered fault devices and update the search engine database 8. Otherwise, continue with step S1.

[0050] As can be seen from the above description, receiving the first fault report means entering the fault period; receiving the fault recovery notification means exiting the fault period. All fault times and associated equipment during the fault period are integrated with the last fault recovery notification to obtain information on recovered fault equipment and update the search engine database 8, so that users can directly view the fault information of a single fault period and understand the recovery status of the fault when searching later.

[0051] Furthermore, the fault notification includes a query button that links to the search window of the search engine library 8.

[0052] As can be seen from the above description, a query button is provided at the same time as sending the fault notification, so that users can directly query the stored content of search engine library 8 to understand the fault details.

[0053] Furthermore, S3 specifically refers to:

[0054] Based on the classification of the equipment to which it belongs, the detailed fault data is written into the time-series database 9.

[0055] As can be seen from the above description, classifying and summarizing the fault details of faulty device 4 can improve search efficiency when users query data.

[0056] The fault data processing method and terminal of the present invention are applicable to scenarios involving fault time and management of associated equipment. The following detailed embodiments illustrate these methods:

[0057] Please refer to Figures 1 to 3 Embodiment 1 of the present invention is as follows:

[0058] Taking a charging station as an example, when some modules of the charging station's equipment 4 malfunction, equipment 4 will generate fault reporting information for this fault and report it through gateway 5. At the same time, the modules will continuously generate a large amount of fault detail data before returning to normal during the fault period, and the fault detail data will also be continuously uploaded.

[0059] like Figure 1 As shown, the existing fault handling architecture stores its data in a relational database, such as MySQL, and then shards and partitions it to determine a fault based on the fault upload interval. However, even with database sharding and partitioning, searching massive amounts of data can slow down searches and make data management difficult.

[0060] Based on this, in order to better store and manage this data and improve retrieval efficiency, this embodiment provides a fault data processing method, including the following steps:

[0061] S1. Receive fault reporting information and fault detail data from device 4 in real time;

[0062] S2. Upon receiving a fault report, write the fault time and the associated device from the fault report into the search engine database 8.

[0063] In this embodiment, the fault reporting information mainly includes two pieces of information: the fault time and the device to which it belongs. To facilitate differentiation, each device can be represented by a unique ID, which clearly shows the source of the fault.

[0064] In this embodiment, upon receiving the first fault report, device 4 is considered to be in a faulty state. At this time, the fault time and associated device are stored in a cache, and a fault notification is sent to client 7. Client 7 is promptly notified of the fault in device 4, allowing for early recovery operations to restore device 4 to normal operation. The fault notification can be sent to client 7 via a distributed publish-subscribe messaging system, such as Kafka.

[0065] Furthermore, the fault notification includes a query button that links to the search window of the search engine library 8. Combined with... Figure 3 As shown, when a user clicks the query button in the pushed fault notification, the system will directly query the fault report information in search engine database 8. If the user queries before the fault is resolved, the retrieved information will be the fault report information already written in search engine database 8. If the user queries after the fault is resolved, the retrieved information will include the fault recovery notification and all fault report information during the fault period, including the fault time and the associated device. Additionally, users can view detailed fault data by clicking on the function module, which will then retrieve the corresponding detailed fault data from the time-series database 9.

[0066] S3. Write the fault details data into the time series database 9.

[0067] In this embodiment, before writing the fault details data into the time series database 9, the fault details data is processed according to the device to which it belongs. Specifically, when the fault details data is received, it is forwarded to the real-time computing program Flink for processing.

[0068] S4. In real time, determine whether a fault recovery notification has been received. If so, integrate all fault times and associated devices during this fault period in the cache and the fault recovery notification to obtain information on the recovered fault devices and update the search engine database 8. Otherwise, continue to execute step S1.

[0069] In this embodiment, when a fault recovery notification is received, it indicates that all faulty devices during the fault period have been recovered. At this time, all fault times and associated devices during the fault period, as well as the fault recovery notification, are integrated in the cache to obtain information on recovered faulty devices and update the search engine library 8. This means that all fault times and associated devices added in the search engine library 8 for a single fault period are integrated together to form a complete piece of information from the occurrence of the fault to the fault recovery process, and stored separately. This reduces the storage pressure on the search engine library 8 and makes it easier for users to query and understand this information.

[0070] Please refer to Figure 4 Embodiment two of the present invention is as follows:

[0071] A fault data processing terminal 1 includes a memory 3, a processor 2, and a computer program stored in the memory 3 and executable on the processor 2. When the processor 2 executes the computer program, it implements the steps of the above embodiment 1.

[0072] In summary, the fault data processing method and terminal provided by this invention, when a device malfunctions, writes the fault time and the device to which it belongs in the fault report information sent by the device into a search engine database, and writes the detailed fault data continuously generated by the device during the fault period into a time-series database. When a user needs to view fault data, they can query the search engine database to quickly obtain search results. When a user wants to view detailed fault data, they can use the time-series database for querying. Relying on the superior performance and compression capabilities of the time-series database, the querying and analysis of massive amounts of data becomes faster. Thus, when storing fault data, it not only reduces the pressure on the database, but also facilitates the rapid retrieval of fault data later.

[0073] The above description is merely an embodiment of the present invention and does not limit the patent scope of the present invention. Any equivalent modifications made based on the content of the present invention specification and drawings, or direct or indirect applications in related technical fields, are similarly included within the patent protection scope of the present invention.

Claims

1. A fault data processing method, characterized in that, Including the following steps: S1. Receive fault reporting information and fault details from the equipment in real time; S2. Upon receiving the fault reporting information, write the fault time and the associated device in the fault reporting information into the search engine database; S3. Write the fault details data into the time series database; Step S2 further includes: The fault time and the associated device are stored in the cache and a fault notification is sent to the user terminal. The step S3 is followed by: S4. In real time, determine whether a fault recovery notification has been received. If so, integrate all the fault times and associated devices within the cache during this fault period, as well as the fault recovery notification, to obtain information on the recovered fault devices and update the search engine database. Otherwise, continue to execute step S1. The fault notification includes a query button in the search window that links to the search engine database; After a user clicks the query button, the fault reporting information will be directly retrieved from the search engine database. If the user queries before the fault is resolved, the fault reporting information already written in the search engine database will be retrieved. If the user queries after the fault is resolved, the information on the resolved faulty device will be retrieved, including the fault recovery notification and all fault times and associated devices during the fault period. If the user needs to view detailed fault data, they can do so by clicking on the function module, and the backend will display the corresponding detailed fault data from the time-series database.

2. The fault data processing method according to claim 1, characterized in that, S3 specifically refers to: Based on the classification of the equipment to which it belongs, the detailed fault data is written into the time-series database.

3. A fault data processing terminal, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the computer program, it performs the following steps: S1. Receive fault reporting information and fault details from the equipment in real time; S2. Upon receiving the fault reporting information, write the fault time and the associated device in the fault reporting information into the search engine database; S3. Write the fault details data into the time series database; Step S2 further includes: The fault time and the associated device are stored in the cache and a fault notification is sent to the user terminal. The step S3 is followed by: S4. In real time, determine whether a fault recovery notification has been received. If so, integrate all the fault times and associated devices within the cache during this fault period, as well as the fault recovery notification, to obtain information on the recovered fault devices and update the search engine database. Otherwise, continue to execute step S1. The fault notification includes a query button in the search window that links to the search engine database; After a user clicks the query button, the fault reporting information will be directly retrieved from the search engine database. If the user queries before the fault is resolved, the fault reporting information already written in the search engine database will be retrieved. If the user queries after the fault is resolved, the information on the resolved faulty device will be retrieved, including the fault recovery notification and all fault times and associated devices during the fault period. If the user needs to view detailed fault data, they can do so by clicking on the function module, and the backend will display the corresponding detailed fault data from the time-series database.

4. A fault data processing terminal according to claim 3, characterized in that, S3 specifically refers to: Based on the classification of the equipment to which it belongs, the detailed fault data is written into the time-series database.

Images