Automatic fault elimination and recovery method for fire extinguishing device of data center

Abstract

The invention belongs to the technical field of fire safety, and particularly relates to an automatic fault elimination and recovery method for a fire extinguishing device of a data center. According to the method, analysis can be carried out according to the historical use state of the fire extinguishing device so as to obtain the regional anomaly trend of the fire extinguishing device, and in the process of calculating the anomaly trend, the appearing anomaly data can be screened out, so that the fault type is judged according to the anomaly data, and the accuracy of the anomaly trend judgment result is improved; and the safety time period of the fire extinguishing device corresponding to the normal state can be calculated based on the trend, then the maintenance period is adjusted according to the safety time period, and meanwhile, automatic recovery is performed according to the fault type, so that the fire extinguishing device can be maintained before the state is abnormal, and it is ensured that the fire extinguishing device is in a good emergency state all the time.

Description

Technical Field

[0002] This invention relates to the field of fire risk prevention and control in high-rise buildings, and in particular to an automatic troubleshooting and recovery method for fire extinguishing devices in data centers. Background Technology

[0004] With the continuous development of various types of buildings, their scale, height, and standards are increasing. Newly constructed buildings are characterized by high population density, advanced equipment, multiple functions, and luxurious decoration. Therefore, automatic fire alarm and automatic fire extinguishing systems have become an indispensable component of high-rise buildings. In daily life, the probability of fire is relatively low, so fire extinguishing devices are generally idle. To ensure the effectiveness of these devices, regular maintenance is essential. Furthermore, with the rapid development of information technology, remote monitoring of fire extinguishing devices is now possible.

[0005] Existing remote monitoring systems for fire extinguishing devices mostly only issue alerts after a malfunction occurs, prompting maintenance personnel to repair the device. Otherwise, they only inspect the device according to the scheduled maintenance cycle. Generally, malfunctions in fire extinguishing devices do not occur suddenly but rather through a slow process, such as a decrease in water storage, aging of the sprinkler heads, or changes in sprinkler pressure. These are all critical factors directly related to the fire extinguishing effect, and they may experience unexpected losses during the maintenance cycle. Summary of the Invention

[0007] The purpose of this invention is to provide an automatic troubleshooting and recovery system and method for fire extinguishing devices in data centers, which can adjust the maintenance cycle according to the status of the fire extinguishing devices, so that maintenance work can be carried out before the fire extinguishing devices become abnormal.

[0008] The specific technical solution adopted by this invention is as follows: An automatic troubleshooting and recovery system and method for fire suppression system malfunctions in a data center, comprising: The usage status of the fire extinguishing device is obtained, wherein the usage status includes historical usage status and current usage status; Obtain all historical usage statuses and aggregate them into a dataset to be evaluated; Obtain the time period of the dataset to be evaluated and label it as the period of effect to be evaluated; Multiple evaluation periods are constructed within the period to be evaluated, and the historical usage status under each evaluation period is obtained and input into the data center evaluation model to obtain the balanced usage status under each evaluation period. Input all the aforementioned balanced usage states into the data center trend prediction model to obtain the historical usage state change trend values; Obtain the current usage status and combine it with the change trend value to obtain the estimated usage status; Obtain the security status threshold and compare it with the estimated usage status; If the safety status threshold is less than or equal to the estimated usage status, it indicates that the fire extinguishing device will be abnormal in the next evaluation cycle, and the fault type is generated by the model based on the preset data center fault determination. If the safety status threshold is greater than the estimated usage status, it indicates that the fire extinguishing device is in normal condition in the next evaluation cycle. The safety status threshold is obtained and combined with the current usage status and the change trend value to calculate the safe period during which the fire extinguishing device can maintain a normal state. Obtain the maintenance cycle, and mark the first and last nodes of the maintenance cycle as the previous maintenance node and the next maintenance node, respectively. Obtain the end point of the safe period and compare it with the subsequent maintenance point; If the end point of the safe period is before the post-maintenance point, the fire extinguishing device will be automatically restored according to the fault type, and the post-maintenance point of the maintenance cycle will be adjusted to be before the end point of the safe period. If the end point of the safety period is after the subsequent maintenance point, then there is no need to adjust the maintenance cycle.

[0009] In a preferred embodiment, the step of constructing multiple evaluation cycles within the period of effect to be evaluated includes: Obtain the historical usage status within the period to be evaluated and mark it as information to be evaluated; Obtain all abnormal usage states and the time nodes corresponding to the abnormal usage states from the information to be evaluated, and mark them as abnormal nodes; The monitoring time periods between adjacent abnormal nodes are obtained and marked as the evaluation period.

[0010] In a preferred embodiment, the step of obtaining all abnormal usage states from the information to be evaluated includes: Obtain the standard usage status and compare it with the information to be evaluated; If the information to be evaluated is below the standard usage state, then the information to be evaluated will be marked as an abnormal usage state. If the information to be evaluated is higher than or equal to the standard usage state, then the information to be evaluated is marked as the normal usage state, and the normal usage state is added to the evaluation cycle.

[0011] In a preferred embodiment, the step of obtaining the historical usage status for each evaluation period and inputting it into the data center evaluation model to obtain the balanced usage status for each evaluation period includes: Obtain the evaluation period corresponding to each evaluation cycle; Obtain the rated threshold and compare it with the evaluation period; If the evaluation period is less than the rated threshold, it is marked as an abnormal period and the corresponding evaluation period is deleted. If the evaluation period is greater than or equal to the rated threshold, it is marked as a qualified period and its corresponding evaluation period is retained. The evaluation function is obtained from the data center evaluation model, and the historical usage status within each qualified time period is input into the evaluation function, and the output result is labeled as a balanced usage status.

[0012] In a preferred embodiment, the step of inputting all the balanced usage states into the data center trend prediction model to obtain the historical usage state change trend value includes: Obtain the balanced usage status for each evaluation period; Obtain the standard function from the data center trend prediction model; The balanced usage state is input into a standard function, which outputs the trend value of the historical usage state.

[0013] In a preferred embodiment, before obtaining the current usage status and combining it with the trend value to obtain the estimated usage status, the trend value is verified. The specific process is as follows: Obtain the historical usage states adjacent to the current usage state and mark them as previous usage states; Obtain the verification function, and input the previous usage state and the change trend value into the verification function to obtain the verified usage state; Obtain the difference between the verified usage state and the current usage state, and mark it as a deviation from the usage state; Obtain the allowable deviation amount and compare it with the deviation usage state to determine the feasibility of the change trend value; If the allowable deviation is greater than or equal to the deviation from the usage state, then the trend value is determined to be executable; If the allowable deviation is less than the deviation from the usage state, the trend value is determined to be unexecutable, and the trend value is recalculated.

[0014] In a preferred embodiment, the step of obtaining a safety state threshold and combining it with the current usage state and a trend value to calculate the safe period during which the fire extinguishing device maintains a normal state includes: Obtain the security status threshold, current usage status, and trend values; Obtain the target function; The safe period is obtained by inputting the safety status threshold, current usage status, and trend value into the objective function.

[0015] In a preferred embodiment, the step of adjusting the later maintenance node of the maintenance cycle to before the end node of the safe period includes: Obtain the end node of the safe period and offset the end node to obtain the safe node; Obtain the difference between the safety node and the subsequent maintenance node, and mark it as the amount to be adjusted; The subsequent maintenance nodes are adjusted according to the amount to be adjusted, and a new maintenance cycle is generated.

[0016] This invention also provides an automatic troubleshooting and recovery system for fire suppression system malfunctions in data centers, applicable to the aforementioned automatic troubleshooting and recovery method for fire suppression system malfunctions in data centers, comprising: The first acquisition module is used to acquire the usage status of the fire extinguishing device, wherein the usage status includes historical usage status and current usage status; The aggregation module is used to obtain all historical usage statuses and aggregate them into a dataset to be evaluated; The second acquisition module is used to acquire the time period of the dataset to be evaluated and mark it as the time period to be evaluated. An evaluation module is used to construct multiple evaluation periods within the period to be evaluated, obtain the historical usage status under each evaluation period, and input it into the data center evaluation model to obtain the balanced usage status under each evaluation period. The trend analysis module is used to input all the balanced usage states into the data center trend prediction model to obtain the historical usage state change trend value. The prediction module is used to obtain the current usage status and combine it with the change trend value to obtain the estimated usage status. The first determination module is used to obtain a security status threshold and compare it with the estimated usage status. If the safety status threshold is less than or equal to the estimated usage status, it indicates that the fire extinguishing device will be abnormal in the next evaluation cycle, and the fault type is generated by the model based on the preset data center fault determination. If the safety status threshold is greater than the estimated usage status, it indicates that the fire extinguishing device is in normal condition in the next evaluation cycle. The calculation module is used to obtain a safety state threshold and combine it with the current usage state and the change trend value to obtain the safe period during which the fire extinguishing device maintains a normal state. The third acquisition module is used to acquire the maintenance cycle and mark the first and last nodes of the maintenance cycle as the previous maintenance node and the next maintenance node, respectively. The second determination module is used to obtain the end node of the safe period and compare it with the subsequent maintenance node; If the end point of the safe period is before the post-maintenance point, the fire extinguishing device will be automatically restored according to the fault type, and the post-maintenance point of the maintenance cycle will be adjusted to be before the end point of the safe period. If the end point of the safety period is after the subsequent maintenance point, then there is no need to adjust the maintenance cycle.

[0017] And, an automatic troubleshooting and recovery terminal for fire suppression system malfunctions in a data center, comprising: At least one processor; and a memory communicatively connected to the at least one processor; The memory stores a computer program that can be executed by the at least one processor, which enables the at least one processor to perform the above-described automatic troubleshooting and recovery method for fire suppression devices in data centers.

[0018] The technical effects achieved by this invention are as follows: This invention can analyze the historical usage status of fire extinguishing devices to determine the trend of regional anomalies. In the process of calculating the anomaly trend, it can also filter out the abnormal data that has already appeared, thereby judging the fault type based on the abnormal data and increasing the accuracy of the anomaly trend judgment result. Based on this trend, it can calculate the safe period of the fire extinguishing device in the corresponding normal state, and then adjust the maintenance cycle according to the safe period. At the same time, it can automatically restore the system according to the fault type, so that the fire extinguishing device can be maintained before the abnormal state occurs, ensuring that the fire extinguishing device is always in a good emergency state. Attached Figure Description

[0020] To more clearly illustrate the technical solutions in the embodiments of this application, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0021] Figure 1 This is a flowchart of the method provided by the present invention; Figure 2 This is a system module diagram provided by the present invention. Detailed Implementation

[0023] In the following description, specific details such as particular system architectures and techniques are set forth for illustrative purposes and not for limitation, in order to provide a thorough understanding of the embodiments of this application. However, those skilled in the art will understand that this application may also be implemented in other embodiments without these specific details. In other instances, detailed descriptions of well-known systems, apparatuses, circuits, and methods have been omitted so as not to obscure the description of this application with unnecessary detail.

[0024] It should be understood that, when used in this application specification and the appended claims, the term "comprising" indicates the presence of the described features, integrals, steps, operations, elements and / or components, but does not exclude the presence or addition of one or more other features, integrals, steps, operations, elements, components and / or a collection thereof.

[0025] It should also be understood that the term “and / or” as used in this application specification and the appended claims means any combination of one or more of the associated listed items and all possible combinations, and includes such combinations.

[0026] As used in this application specification and the appended claims, the term "if" may be interpreted, depending on the context, as "when," "once," "in response to determination," or "in response to detection." Similarly, the phrase "if determined" or "if detected [the described condition or event]" may be interpreted, depending on the context, as meaning "once determined," "in response to determination," "once detected [the described condition or event]," or "in response to detection [the described condition or event]."

[0027] Furthermore, in the description of this application and the appended claims, the terms "first," "second," "third," etc., are used only to distinguish descriptions and should not be construed as indicating or implying relative importance.

[0028] References to "one embodiment" or "some embodiments" as described in this specification mean that one or more embodiments of this application include a specific feature, structure, or characteristic described in connection with that embodiment. Therefore, the phrases "in one embodiment," "in some embodiments," "in other embodiments," "in still other embodiments," etc., appearing in different parts of this specification do not necessarily refer to the same embodiment, but rather mean "one or more, but not all, embodiments," unless otherwise specifically emphasized. The terms "comprising," "including," "having," and variations thereof mean "including but not limited to," unless otherwise specifically emphasized.

[0029] It should be understood that the sequence number of each step in this embodiment does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of this application embodiment.

[0030] Please see Figure 1 and Figure 2 As shown, the present invention provides an automatic troubleshooting and recovery method for fire suppression system malfunctions in data centers, including: S1. Obtain the usage status of the fire extinguishing device, including historical usage status and current usage status; S2. Obtain all historical usage statuses and summarize them into a dataset to be evaluated; S3. Obtain the time period of the dataset to be evaluated and label it as the time period to be evaluated; S4. Construct multiple evaluation periods within the period to be evaluated, obtain the historical usage status of each evaluation period, and input it into the data center evaluation model to obtain the balanced usage status of each evaluation period. S5. Input all balanced usage statuses into the data center trend prediction model to obtain the historical usage status change trend values; S6. Obtain the current usage status and combine it with the trend value to obtain the estimated usage status; S7. Obtain the security status threshold and compare it with the estimated usage status; If the safety status threshold is less than or equal to the estimated usage status, it indicates that the fire extinguishing device will be abnormal in the next assessment cycle. The model will generate the fault type based on the preset data center fault determination model, and the fire extinguishing device will be automatically restored according to the fault type. If the safety status threshold is greater than the estimated usage status, it indicates that the fire extinguishing device is in normal condition in the next evaluation cycle. S8. Obtain the safety status threshold and combine it with the current usage status and the trend value to calculate the safe period during which the fire extinguishing device can maintain a normal state. S9. Obtain the maintenance cycle and mark the first and last nodes of the maintenance cycle as the previous maintenance node and the next maintenance node, respectively. S10. Obtain the end node of the safe period and compare it with the subsequent maintenance node; If the end point of the safe period is before the post-maintenance point, the fault type is generated based on the preset data center fault determination model, and the fire extinguishing device is automatically restored according to the fault type. The post-maintenance point of the maintenance cycle is then adjusted to be before the end point of the safe period. If the end point of the safe period is after the subsequent maintenance point, then there is no need to adjust the maintenance cycle.

[0031] As described in steps S1-S10 above, fire extinguishing devices are crucial for extinguishing fires in fire protection systems. They are typically installed in easily accessible and visible areas inside buildings, allowing occupants to use them for self-rescue in the event of a fire, thus ensuring their safety. However, fires are relatively rare, leading to fire extinguishing devices remaining idle for extended periods. For safety reasons, regular maintenance is essential to ensure the devices are readily available and capable of extinguishing fires. Even when idle, fire extinguishing devices still experience wear and tear. For example, in high-pressure water mist fire extinguishing devices, the amount of water stored directly affects the extinguishing effect. Similarly, the pressure of the high-pressure nozzle determines the water mist diffusion, also directly impacting the extinguishing effect. Traditional monitoring methods often require manual, step-by-step checks. However, with the rapid development of information technology, the status of fire extinguishing devices can be remotely monitored using various sensors. In this embodiment, through… The analysis is based on the historical usage status of the fire extinguishing device. To reduce computational load, the historical usage status analysis is divided into multiple evaluation periods. Trend analysis and evaluation are performed on the historical usage status in normal condition within each evaluation period. Information on abnormal conditions is not included in the trend analysis and evaluation. This ensures that the final historical usage status trend value is accurate, and correspondingly reduces the error of the estimated usage status calculated based on it. If the estimated usage status exceeds the safe state threshold, a fault type is immediately generated based on the preset data center fault determination model, and the fire extinguishing device is automatically restored according to the fault type. Maintenance personnel can then perform targeted maintenance on the fire extinguishing device based on the alarm area. This embodiment also calculates the safe period for the fire extinguishing device under normal conditions and adjusts the corresponding maintenance cycle based on the end point of the safe period. This ensures that maintenance work can be carried out on the fire extinguishing device before abnormal conditions occur, guaranteeing that the fire extinguishing device can respond to emergencies even when idle.

[0032] In a preferred embodiment, the step of constructing multiple evaluation cycles within the period of action to be evaluated includes: S401. Obtain the historical usage status within the period to be evaluated and mark it as information to be evaluated; S402. Obtain all abnormal usage states and the time nodes corresponding to the abnormal usage states from the information to be evaluated, and mark them as abnormal nodes. S403. Obtain the monitoring time period between adjacent abnormal nodes and mark it as the evaluation period.

[0033] As described in steps S401-S403 above, the evaluation period is constructed based on the time period of the dataset to be evaluated. Of course, after the fire extinguishing device is replaced, the dataset to be evaluated and the evaluation period need to be reconstructed. The evaluation period is constructed based on the node where the abnormal usage state occurs as the dividing point. Once an abnormality occurs, the abnormal point will be repaired to restore the state of the fire extinguishing device. However, the historical usage state under the abnormal state is discarded accordingly.

[0034] In a preferred embodiment, the step of obtaining all abnormal usage states from the information to be evaluated includes: S4021. Obtain the standard usage status and compare it with the information to be evaluated; S4022. If the information to be evaluated is below the standard usage status, then the information to be evaluated shall be marked as an abnormal usage status. S4023. If the information to be evaluated is higher than or equal to the standard usage status, the information to be evaluated shall be marked as the normal usage status, and the normal usage status shall be added to the evaluation cycle.

[0035] As described in steps S4021-S4023 above, when determining abnormal usage status, a standard usage status is first preset based on the threshold between the normal and abnormal status of the fire extinguishing device. Since the specifications of fire extinguishing devices are different, their corresponding standard usage statuses are also inconsistent, so no detailed restrictions are imposed here. In the information to be evaluated, there will inevitably be some information to be evaluated that is lower than the standard usage status. At this time, it can be confirmed that it is an abnormal usage status. Obviously, it is not advisable to include it in the evaluation period. Here, this embodiment removes it and marks the corresponding time node as an abnormal node. Then, the time period between adjacent abnormal nodes is used to construct the evaluation period, and the normal usage status within the evaluation period is statistically analyzed to provide corresponding data support for subsequent trend evaluation and calculation of safe periods.

[0036] In a preferred embodiment, the step of acquiring the historical usage status for each evaluation period and inputting it into the data center evaluation model to obtain the balanced usage status for each evaluation period includes: S404. Obtain the assessment period corresponding to each assessment cycle; S405. Obtain the rated threshold and compare it with the evaluation period; If the evaluation period is shorter than the rated threshold, it will be marked as an abnormal period and the corresponding evaluation period will be deleted. If the evaluation period is greater than or equal to the rated threshold, it is marked as a qualified period and its corresponding evaluation period is retained. S406. Obtain the evaluation function from the data center evaluation model, input the historical usage status within each qualified time period into the evaluation function, and label the output result as a balanced usage status.

[0037] As described in steps S404-S406 above, after the abnormal node corresponding to the abnormal usage state is determined, considering the frequency of its abnormal state occurrence, if the occurrence frequency is too fast, it indicates that the maintenance effect of the fire extinguishing device after the abnormality occurs is not good. Based on this, this embodiment also sets a rated threshold for defining the frequency of abnormal states of the fire extinguishing device. Only when the evaluation period is greater than the rated threshold is the corresponding normal usage state added to the evaluation function. The evaluation function provided in this embodiment is: , where / > represents the balanced usage state, / > represents the number of historical usage states, and / > represents the historical usage states in the interval 1 to / >. Based on this, the balanced usage state under each qualified time period can be calculated one by one.

[0038] In a preferred embodiment, the step of inputting all balanced usage states into the data center trend prediction model to obtain historical usage trend values ​​includes: S501. Obtain the balanced usage status for each evaluation period; S502. Obtain the standard function from the data center trend prediction model; S503. Input the balanced usage status into the standard function and output the historical usage status change trend value.

[0039] As described in steps S501-S503 above, after the balanced usage status is determined, the trend value of the historical usage status is calculated. The standard function of the trend value is: , where represents the trend value of the historical usage status, represents the number of balanced usage statuses, and represents the balanced usage status within the interval 1 to . Based on this, the trend value of the historical usage status can be calculated, and then it can be used to predict the estimated usage status under the next node. Based on the prediction results, it can be determined whether the fire extinguishing device will malfunction under the next node, thus playing an early warning role.

[0040] In a preferred embodiment, the current usage status is obtained and combined with the trend value to calculate the estimated usage status. Before that, the trend value is verified. The specific process is as follows: Stp1: Retrieve the historical usage state adjacent to the current usage state and mark it as the previous usage state; Stp2, obtain the verification function, and input the previous usage status and the change trend value into the verification function to obtain the verification usage status; Stp3: Obtain the difference between the current usage status and the verification usage status, and mark it as a deviation from the usage status; Stp4: Obtain the allowable deviation and compare it with the deviation from the usage state to determine the feasibility of the changing trend value; If the allowable deviation is greater than or equal to the deviation from the usage state, the trend value is determined to be executable; If the allowable deviation is less than the deviation from the operating state, the trend value is determined to be unexecutable, and the trend value is recalculated.

[0041] As described in steps Stp1-Stp4 above, after calculating the historical usage trend value, the feasibility of the trend value needs to be further verified. The verification function is: , where / > represents the verified usage state, and / > represents the previous usage state. Then, the difference between the current usage state and the previous usage state is calculated to obtain the deviation from the usage state. As long as the deviation from the usage state does not exceed the allowable deviation, the trend value can be determined to be feasible. Otherwise, the trend value needs to be recalculated. During the recalculation process, the input of the balanced usage state is reduced one by one from front to back until the trend value is determined to be feasible. Then, the trend value can be used to estimate the state of the next node of the fire extinguishing device.

[0042] In a preferred embodiment, the step of obtaining a safety state threshold and combining it with the current usage state and trend value to calculate the safe period during which the fire extinguishing device maintains a normal state includes: S801, Obtain the security status threshold, current usage status, and trend value; S802, Obtain the objective function; S803. Input the safety status threshold, current usage status, and trend value into the objective function to obtain the safe time period.

[0043] As described in steps S801-S803 above, after determining that the fire extinguishing device can operate normally under the next node, the safe period for the fire extinguishing device to operate normally is calculated by combining the preset safety status threshold. This is then compared with the maintenance cycle to determine whether the fire extinguishing device will experience any abnormalities before the next maintenance operation. The objective function used for calculating the safe period is: , where represents the safe period, represents the safety status threshold, and represents the current usage state. After calculating and obtaining the safe period, the subsequent maintenance node of the maintenance cycle and the end node of the safe period are determined. It should be noted that if there are any number of subsequent maintenance nodes before the end node of the safe period, no adjustment to the fire extinguishing device is required. However, if there are no subsequent maintenance nodes before the end node of the safe period, and the subsequent maintenance node is located after the end node of the safe period, then a fault type needs to be generated based on the preset data center fault determination model. The fire extinguishing device is then automatically restored according to the fault type, and the end node of the maintenance cycle needs to be adjusted to be before the end node of the safe period to prevent the fire extinguishing device from experiencing abnormalities before the maintenance operation.

[0044] In a preferred embodiment, the step of adjusting the later maintenance node of the maintenance cycle to before the end node of the safe period includes: S1001. Obtain the end node of the safe period and offset the end node to obtain the safe node; S1002. Obtain the difference between the safety node and the post-maintenance node, and mark it as the amount to be adjusted; S1003. Adjust the subsequent maintenance nodes according to the amount to be adjusted, and generate a new maintenance cycle.

[0045] As described in steps S1001-S1003 above, when adjusting the post-maintenance node, the end node of the safe period is first offset. This offset can be set according to specific needs, and then a clear safe node can be obtained. No specific restrictions are imposed here. Then, the difference between the safe node and the post-maintenance node is determined according to the safe node, and it is adjusted as the amount to be adjusted. In this way, the fire extinguishing device can be repaired in time during subsequent maintenance operations, ensuring that it can play an emergency fire extinguishing role.

[0046] This invention also provides an automatic troubleshooting and recovery system for fire suppression system malfunctions in data centers, applicable to the aforementioned automatic troubleshooting and recovery method for fire suppression system malfunctions in data centers, comprising: The first acquisition module is used to acquire the usage status of the fire extinguishing device, wherein the usage status includes historical usage status and current usage status; The summary module is used to obtain all historical usage statuses and summarize them into a dataset to be evaluated. The second acquisition module is used to acquire the time period of the dataset to be evaluated and mark it as the time period to be evaluated. The evaluation module is used to construct multiple evaluation periods within the period to be evaluated, obtain the historical usage status of each evaluation period, and input it into the data center evaluation model to obtain the balanced usage status of each evaluation period. The trend analysis module is used to input all balanced usage statuses into the data center trend prediction model to obtain historical usage trend values. The prediction module is used to obtain the current usage status and combine it with the trend value to obtain the estimated usage status. The first determination module is used to obtain the security status threshold and compare it with the estimated usage status. If the safety status threshold is less than or equal to the estimated usage status, it indicates that the fire extinguishing device will be abnormal in the next assessment cycle. The model will generate the fault type based on the preset data center fault determination model, and the fire extinguishing device will be automatically restored according to the fault type. If the safety status threshold is greater than the estimated usage status, it indicates that the fire extinguishing device is in normal condition in the next evaluation cycle. The calculation module is used to obtain the safety status threshold and combine it with the current usage status and the trend value to obtain the safe period of time during which the fire extinguishing device can maintain a normal state. The third acquisition module is used to acquire the maintenance cycle and to mark the first and last nodes of the maintenance cycle as the previous maintenance node and the next maintenance node, respectively. The second determination module is used to obtain the end node of the safe period and compare it with the subsequent maintenance node; If the end point of the safe period is before the post-maintenance point, the fault type is generated based on the preset data center fault determination model, and the fire extinguishing device is automatically restored according to the fault type. The post-maintenance point of the maintenance cycle is then adjusted to be before the end point of the safe period. If the end point of the safe period is after the subsequent maintenance point, then there is no need to adjust the maintenance cycle.

[0047] In the above process, when remotely monitoring the fire extinguishing device, the first acquisition module first obtains the current and historical usage status of the device. Then, the aggregation module aggregates the historical usage status into an evaluation dataset. The second acquisition module determines the evaluation period of the dataset. The evaluation module then constructs multiple evaluation cycles within the evaluation period and uses a data center evaluation model to calculate the balanced usage status for each evaluation cycle. The balanced usage status is then input into the trend analysis module to calculate and obtain the historical usage status trend value. Finally, the prediction module combines the trend value with the current usage status to predict the estimated usage status of the next node. Thus, the first judgment module can determine whether the device is operating normally. Based on this, the calculation module calculates the safe period for the fire extinguishing device to maintain a normal state. The third acquisition module obtains the maintenance cycle, and the output of the second judgment module determines whether to adjust the subsequent maintenance node and the specific adjustment method, thereby ensuring that the fire extinguishing device can play an emergency role under any circumstances.

[0048] And, an automatic troubleshooting and recovery terminal for fire suppression system malfunctions in a data center, comprising: At least one processor; and memory that is communicatively connected to at least one processor; The memory stores a computer program that can be executed by at least one processor, which enables the at least one processor to perform the aforementioned automatic troubleshooting and recovery method for fire suppression devices in the data center.

Claims

1. A method for automatic troubleshooting and recovery of fire extinguishing device based on data center, characterized in that: The method comprises the following steps: acquiring a use state of the fire extinguishing device, wherein the use state comprises a historical use state and a current use state; acquiring all historical use states and summarizing them into an evaluation data set; acquiring a time period of the evaluation data set and calibrating it as an evaluation action time period; constructing a plurality of evaluation periods within the evaluation action time period and acquiring historical use states under each of the evaluation periods respectively and inputting them into a data center evaluation model to obtain balanced use states under each of the evaluation periods; inputting all the balanced use states into a data center trend estimation model to obtain a change trend value of the historical use states; acquiring a current use state and combining it with the change trend value to obtain an estimated use state; acquiring a safety state threshold and comparing it with the estimated use state; if the safety state threshold is less than or equal to the estimated use state, it indicates that the fire extinguishing device will be abnormal in the next evaluation period, and a fault type is generated according to a preset data center fault determination model; if the safety state threshold is greater than the estimated use state, it indicates that the fire extinguishing device is in a normal state in the next evaluation period; acquiring a safety state threshold and combining it with the current use state and the change trend value to obtain a safety time period in which the fire extinguishing device continuously remains in a normal state; acquiring a maintenance period and calibrating the first and last nodes of the maintenance period as a front maintenance node and a rear maintenance node respectively; comparing an end node of the safety time period with the rear maintenance node; if the end node of the safety time period is before the rear maintenance node, the fire extinguishing device is automatically recovered according to the fault type, and the rear maintenance node of the maintenance period is adjusted to be before the end node of the safety time period; if the end node of the safety time period is after the rear maintenance node, the maintenance period does not need to be adjusted.

2. The method for automatic troubleshooting and recovery of a data center based fire suppression device failure of claim 1, wherein: The step of constructing a plurality of evaluation periods within the evaluation action time period comprises: acquiring historical use states within the evaluation action time period and calibrating them as evaluation information; acquiring all abnormal use states from the evaluation information and time nodes corresponding to the abnormal use states and calibrating them as abnormal nodes; acquiring a monitoring time period between adjacent abnormal nodes and calibrating it as an evaluation period.

3. The method for automatic troubleshooting and recovery of a data center based fire suppression device failure of claim 2, wherein: The step of acquiring all abnormal use states from the evaluation information comprises: comparing a standard use state with the evaluation information; if the evaluation information is lower than the standard use state, the evaluation information is calibrated as an abnormal use state; if the evaluation information is higher than or equal to the standard use state, the evaluation information is calibrated as a normal use state and the normal use state is added to the evaluation period.

4. The method for automatic troubleshooting and recovery of a data center based fire suppression device failure of claim 1, wherein: The step of acquiring historical use states under each of the evaluation periods respectively and inputting them into a data center evaluation model to obtain balanced use states under each of the evaluation periods comprises: acquiring an evaluation time period corresponding to each of the evaluation periods; acquiring a rated threshold and comparing it with the evaluation time period; If the evaluation period is less than the rated threshold, it is marked as an abnormal period, and its corresponding evaluation period is deleted; If the evaluation period is greater than or equal to the rated threshold, it is marked as a qualified period, and its corresponding evaluation period is retained; An evaluation function is obtained from the data center evaluation model, and the historical usage state in each of the qualified periods is input into the evaluation function, and the output result is marked as a balanced usage state.

5. The method for automatic troubleshooting and recovery of a data center based fire suppression device failure of claim 1, wherein: The step of inputting all the balanced usage states into the data center trend estimation model to obtain the change trend value of the historical usage state comprises: Obtaining the balanced usage state under each evaluation period; Obtaining a standard function from the data center trend estimation model; Input the balanced usage state into the standard function to output the change trend value of the historical usage state.

6. The method for automatic troubleshooting and recovery of a data center based fire suppression device failure of claim 1, wherein: Before the change trend value is combined with the current usage state to obtain the estimated usage state, the change trend value is verified, and the specific process is as follows: Obtaining a historical usage state adjacent to the current usage state and marking it as a previous usage state; Obtaining a verification function and inputting the previous usage state and change trend value into the verification function to obtain a verification usage state; Obtaining the difference between the verification usage state and the current usage state and marking it as a deviation usage state; Obtaining an allowable deviation amount and comparing it with the deviation usage state to determine the executability of the change trend value; If the allowable deviation amount is greater than or equal to the deviation usage state, it is determined that the change trend value is executable; If the allowable deviation amount is less than the deviation usage state, it is determined that the change trend value is not executable, and the change trend value is recalculated.

7. The method for automatic troubleshooting and recovery of a data center based fire suppression device failure of claim 1, wherein: The step of obtaining a safety state threshold and combining it with the current usage state and the change trend value to obtain a safety period during which the fire extinguishing device continuously maintains a normal state comprises: Obtaining a safety state threshold, a current usage state, and a change trend value; Obtaining a target function; Input the safety state threshold, the current usage state, and the change trend value into the target function to obtain a safety period.

8. The method for automatic troubleshooting and recovery of a data center based fire suppression device failure of claim 1, wherein: The step of adjusting the maintenance period after the maintenance node to a node before the end of the safety period comprises: Obtaining the end node of the safety period and offsetting the end node to obtain a safety node; Obtaining the difference between the safety node and the maintenance node after the maintenance and marking it as an adjustment amount; Adjusting the maintenance node after the maintenance according to the adjustment amount and generating a new maintenance period.

9. A data center fire extinguishing device failure automatic elimination and recovery system applied to the data center fire extinguishing device failure automatic elimination and recovery method in any one of claims 1 to 8, characterized in that: Comprise: A first obtaining module, the first obtaining module is used for obtaining the usage state of fire extinguishing device, wherein the usage state comprises historical usage state and current usage state; A summary module, the summary module is used for obtaining all historical usage states and summarizing them into a to-be-evaluated data set; A second obtaining module, the second obtaining module is used for obtaining the period of the to-be-evaluated data set and marking it as a to-be-evaluated action period; An evaluation module is configured to construct a plurality of evaluation periods within the to-be-evaluated action period, and obtain a historical usage state in each evaluation period and input into a data center evaluation model to obtain a balanced usage state in each evaluation period. A trend analysis module is configured to input all the balanced usage states into a data center trend estimation model to obtain a change trend value of the historical usage state. A prediction module is configured to obtain a current usage state and combine the current usage state with the change trend value to obtain an estimated usage state. A first determination module is configured to obtain a safety state threshold and compare the safety state threshold with the estimated usage state. A calculation module is configured to obtain a safety state threshold and combine the safety state threshold with the current usage state and the change trend value to obtain a safety period in which the fire extinguishing device continuously maintains a normal state. A third obtaining module is configured to obtain a maintenance period and mark a first node and a last node of the maintenance period as a front maintenance node and a rear maintenance node, respectively. A second determination module is configured to obtain an end node of the safety period and compare the end node with the rear maintenance node.

10. A fire extinguishing apparatus failure automatic exclusion and recovery terminal of a data center, characterized by: The method comprises: at least one processor; and a memory connected in communication with the at least one processor; wherein the memory stores a computer program executable by the at least one processor, and the computer program is executed by the at least one processor to enable the at least one processor to execute the data center-based fire extinguishing device failure automatic elimination and recovery method in any one of claims 1 to 8.

Images