Energy storage device and fault detection method

Abstract

The application relates to the technical field of energy storage, in particular to an energy storage device and a fault detection method. The method comprises the following steps: detecting whether a key configuration file in the energy storage device is tampered with; detecting whether internal services in the energy storage device are normally operated; if the key configuration file in the energy storage device is tampered with and the internal services are normally operated, performing fault reminding according to a first fault state; if the key configuration file in the energy storage device is not tampered with and the internal services are abnormally operated, performing fault reminding according to a second fault state; and if the key configuration file in the energy storage device is tampered with and the internal services are abnormally operated, performing fault reminding according to a third fault state. The application can locally remind faults of the energy storage device, so that local maintenance personnel can timely find faults existing in the energy storage device.

Description

Technical Field

[0001] This application relates to the field of energy storage technology, specifically to an energy storage device and a fault detection method. Background Technology

[0002] With the popularization of new energy sources, photovoltaic (PV) power generation is playing an increasingly important role. In PV power generation systems, energy storage devices are crucial for storing the electrical energy generated by PV. Ensuring the safe and stable operation of energy storage devices is essential for guaranteeing the normal power generation of the PV system. Therefore, detecting faults in energy storage devices and promptly identifying problems has become a technical challenge that needs to be addressed. Summary of the Invention

[0003] In view of this, this application provides an energy storage device and a fault detection method, which can provide fault alerts locally on the energy storage device, making it easier for local maintenance personnel to promptly detect faults in the energy storage device.

[0004] In a first aspect, embodiments of the present invention provide a fault detection method for an energy storage device, the method comprising: Detect whether critical configuration files in energy storage devices have been tampered with; Check whether the internal services in the energy storage device are operating normally; If the critical configuration file in the energy storage device is tampered with and the internal services are operating normally, a fault alert will be issued according to the first fault state. If the critical configuration files in the energy storage device have not been tampered with and the internal services are malfunctioning, a fault alert will be issued according to the second fault state. If the critical configuration file in the energy storage device is tampered with or the internal service malfunctions, a fault alert will be issued according to the third fault state.

[0005] In some embodiments, the method further includes: A list of key configuration files is pre-defined, which contains multiple key configuration files; The tampering of critical configuration files in the energy storage device includes: at least one critical configuration file in the list of critical configuration files being tampered with.

[0006] In some embodiments, detecting whether a critical configuration file in an energy storage device has been tampered with includes: Calculate the hash value of the key configuration file; If the hash value of the key configuration file is consistent with the preset initial value, it is determined that the key configuration file has not been tampered with; If the hash value of the critical configuration file is inconsistent with the preset initial value, it is determined that the critical configuration file has been tampered with.

[0007] In some embodiments, the method further includes: An internal service list is pre-set, which contains multiple internal services; The internal service malfunction includes at least one internal service in the internal service list that is malfunctioning.

[0008] In some embodiments, after determining that a critical configuration file in the energy storage device has been tampered with, the method further includes: Identify the security configuration items associated with the critical configuration file that has been tampered with; Check whether the security configuration item has undergone configuration changes; If the security configuration item undergoes a configuration change, a fault alert will be issued according to the fourth fault state.

[0009] In some embodiments, the method further includes: If the security configuration item has a formatting problem, the fault alert will still be issued according to the first fault state even if the critical configuration file in the energy storage device is tampered with and the internal services are running normally.

[0010] In some embodiments, providing a fault status alert includes: Different colored indicator lights are used to provide fault alerts for different fault states.

[0011] In some embodiments, the second fault state and the third fault state are indicated by color indicator lights of the same color.

[0012] In some embodiments, the key configuration files in the list of key configuration files include one or more of the following: Operating system kernel files, network configuration files, audit logs, operating system files used for remote login, PAM configuration files, database configuration files, and custom files containing critical data.

[0013] In some embodiments, providing a fault status alert further includes: The detection information of the key configuration files and / or the internal services is displayed on the display interface of the energy storage device or sent to the terminal device.

[0014] Secondly, embodiments of the present invention provide an energy storage device, comprising: At least one processor; and at least one memory communicatively connected to the processor, wherein the memory stores program instructions executable by the processor, the processor invoking the program instructions to perform the method described in the first aspect or any one of the first aspects.

[0015] The energy storage device and fault detection method of the present invention have at least the following beneficial effects: In this embodiment of the invention, the presence of a fault in the energy storage device is determined based on whether the key configuration files in the energy storage device have been tampered with and whether the internal services are operating normally. Fault alerts are then issued for different fault states. Optionally, different fault alerts can be issued locally on the energy storage device for different fault states, allowing local maintenance personnel to promptly detect faults. Furthermore, since different fault alerts can be issued for different fault states, local maintenance personnel can intuitively determine the type of fault in the energy storage device based on the fault state, facilitating the resolution of the fault. Attached Figure Description

[0016] Figure 1 A flowchart illustrating a fault detection method for an energy storage device provided in an embodiment of the present invention; Figure 2 A flowchart of another fault detection method for energy storage devices provided in an embodiment of the present invention; Figure 3 A flowchart illustrating another fault detection method for an energy storage device provided in an embodiment of the present invention; Figure 4 This is a schematic diagram of the structure of an energy storage device provided in an embodiment of the present invention. Detailed Implementation

[0017] To better understand the technical solution of this application, the embodiments of this application will be described in detail below with reference to the accompanying drawings.

[0018] It should be understood that the described embodiments are merely some, not all, of the embodiments in this application. All other embodiments obtained by those skilled in the art based on the embodiments in this application without inventive effort are within the scope of protection of this application.

[0019] The terminology used in the embodiments of this application is for the purpose of describing particular embodiments only and is not intended to be limiting of this application. The singular forms “a,” “the,” and “the” used in the embodiments of this application and the appended claims are also intended to include the plural forms unless the context clearly indicates otherwise.

[0020] It should be understood that the term "and / or" used in this article is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. Additionally, the character " / " in this article generally indicates that the preceding and following related objects have an "or" relationship.

[0021] To maintain the safe and stable operation of energy storage devices, this invention provides a fault detection method for energy storage devices. This method operates on the energy storage device side, can detect faults in the device, and can provide fault alerts locally on the energy storage device, making it easier for local maintenance personnel to promptly identify faults in the energy storage device.

[0022] See Figure 1 The flowchart below shows a fault detection method for an energy storage device provided in an embodiment of the present invention. Figure 1 The method shown is applied in energy storage devices, such as... Figure 1 As shown, the processing steps of this method include: 101. Detect whether the critical configuration files in the energy storage device have been tampered with.

[0023] 102. Check whether the internal services in the energy storage device are operating normally.

[0024] 103. If critical configuration files in the energy storage device are tampered with and internal services are operating normally, a warning will be issued according to the first fault state.

[0025] 104. If the critical configuration files in the energy storage device have not been tampered with and the internal services are not operating abnormally, then a fault alert will be issued according to the second fault state.

[0026] 105. If critical configuration files in the energy storage device are tampered with or internal services malfunction, a fault alert will be issued according to the third fault state.

[0027] In this embodiment of the invention, the presence of a fault in the energy storage device is determined based on whether the key configuration files in the energy storage device have been tampered with and whether the internal services are operating normally. Fault alerts are then issued for different fault states. Optionally, different fault alerts can be issued locally on the energy storage device for different fault states, allowing local maintenance personnel to promptly detect faults. Furthermore, since different fault alerts can be issued for different fault states, local maintenance personnel can intuitively determine the type of fault in the energy storage device based on the fault state, facilitating the resolution of the fault.

[0028] In some embodiments, the energy storage device operates according to the configuration file. When the critical configuration file in the energy storage device is tampered with but the internal services are running normally, it indicates that the change in the critical configuration file in the energy storage device is not enough to affect the normal operation of the internal services. At this time, the energy storage device can issue a fault alert according to the first fault state.

[0029] In some embodiments, when the critical configuration file in the energy storage device has not been tampered with but the internal services in the energy storage device are malfunctioning, it indicates that a serious problem has occurred in the internal services of the energy storage device. In this case, the energy storage device can issue a fault alert according to the second fault state.

[0030] In some embodiments, when a critical configuration file in an energy storage device is tampered with and internal services malfunction, it indicates that a serious problem has occurred in the energy storage device. In this case, the energy storage device can issue a warning according to the third fault state.

[0031] In some embodiments, when the internal services of an energy storage device malfunction, regardless of whether the critical configuration files in the energy storage device have been tampered with, it indicates that a serious problem has occurred in the energy storage device. Therefore, the same fault state can be used for fault alerts, that is, the second fault state and the third fault state are the same fault state.

[0032] In some embodiments, after determining that a critical configuration file in the energy storage device has been tampered with, the security configuration items associated with the tampered critical configuration file can also be identified, and it can be detected whether the associated security configuration items have undergone configuration changes. If the associated security configuration items have undergone configuration changes, it indicates that the tampering of the critical configuration file may have been caused by the configuration change of the associated security configuration items. Therefore, a fault alert can be issued according to the fourth fault state. Optionally, the fourth fault state, the second fault state, and the third fault state can be the same fault state or different fault states. Further, if the associated security configuration items do not have configuration changes but have format problems, it indicates that the change of the critical configuration file may have been caused by the format problem of the associated security configuration items. In this case, if the critical configuration file in the energy storage device has been tampered with and the internal services are operating normally, a fault alert can still be issued according to the first fault state.

[0033] In some embodiments, detecting whether a critical configuration file in an energy storage device has been tampered with includes: pre-configuring a list of critical configuration files, which contains multiple critical configuration files. When tampering is detected in at least one critical configuration file in the list, it indicates that a critical configuration file in the energy storage device has been tampered with. Optionally, a hash value of the critical configuration file can be calculated. If the hash value of the critical configuration file matches a preset initial value, it is determined that the critical configuration file has not been tampered with; if the hash value of the critical configuration file matches a preset initial value, it is determined that the critical configuration file has not been tampered with. That is, embodiments of the present invention can determine whether a critical configuration file has been tampered with based on its hash value.

[0034] In some embodiments, the critical configuration files in the critical configuration file list may include one or more of the following: operating system kernel file, network configuration file, audit log, operating system file for remote login, PAM configuration file, database configuration file, and custom file containing critical data.

[0035] In some embodiments, detecting whether the internal services in an energy storage device are operating normally may include: pre-setting an internal service list, which contains multiple internal services. When at least one internal service in the internal service list is operating abnormally, it can be determined that there is an abnormality in the operation of the internal services of the energy storage device.

[0036] In some embodiments, fault alerts for different fault states of energy storage devices include using different colored indicator lights to indicate different fault states. The color, flashing frequency, and number of lights on the indicator lights can represent different fault states. For example, when the critical configuration file in the energy storage device has not been tampered with and the internal services of the energy storage device are operating normally, a green light can be illuminated, indicating that the energy storage device is operating normally. When the critical configuration file in the energy storage device has been tampered with but the internal services of the energy storage device are operating normally, a yellow light can be illuminated, indicating that there is a critical configuration file fault in the energy storage device. Further, when the critical configuration file in the energy storage device has been tampered with, the internal services of the energy storage device are operating normally, and the tampering of the critical configuration file is caused by a format error in a related security configuration item, two yellow lights can be illuminated to indicate that the critical configuration file of the energy storage device has been tampered with, and that the tampering is caused by a format error in a related security configuration item; if the tampering of the critical configuration file is caused by a configuration change in a related security configuration item, a red light or two yellow lights can be illuminated, and the flashing frequencies of the two yellow lights can be set to be different. Furthermore, if the critical configuration file in the energy storage device has not been tampered with, but the internal services are malfunctioning, a red light can be illuminated to indicate that the internal operating services of the energy storage device are malfunctioning. In some embodiments, if the critical configuration file in the energy storage device has been tampered with and the internal services are malfunctioning, one red light or two red lights can be illuminated. In this embodiment of the invention, there are various other ways to use indicator lights of different colors to remind users of different fault states, which will not be described in detail here.

[0037] In some embodiments, the list of critical configuration files is designated as List A. List A contains one or more of the following: operating system kernel file, network configuration file, audit logs, operating system files used for remote login, PAM configuration file, database configuration file, and custom files containing critical data. It should be noted that the critical configuration files in the critical file configuration list are typically those whose configuration items do not change; therefore, the critical file configuration list does not include database instance files, specific logs, or other files that change over time.

[0038] In some embodiments, it can be determined whether the key configuration files in list A have been tampered with by calculating hash values.

[0039] In this embodiment of the invention, the internal service list of the energy storage device is referred to as List B. List B contains information such as whether a process or thread with a specific name of the energy storage software application has started and whether the thread status is normal.

[0040] In this embodiment of the invention, when the energy storage device is started, it can automatically scan the key configuration files in list A and record the initial hash of each key configuration file in list A. Subsequently, it automatically scans each configuration file again at regular intervals, such as every 7 days. After each scan, the hash of each key configuration file is recalculated, and the recalculated hash is compared with the initial hash. If the recalculated hash matches the initial hash, it means that the key configuration file has not been tampered with; if the recalculated hash does not match the initial hash, it means that the key configuration file has been tampered with. In this way, the energy storage device can automatically scan the list of key configuration files at a certain time period, and can promptly detect whether the key configuration files have been tampered with.

[0041] In this embodiment of the invention, after the energy storage device is started, it automatically scans whether each internal service in list B is running normally. Whether the internal services in the energy storage device are running normally includes whether the process is started, whether the process is suspended, and whether the process is in a dead state. Based on the judgment result, it is determined whether each internal service in list B is running normally. If at least one internal service is running abnormally, it is marked as abnormal.

[0042] Furthermore, this embodiment of the invention also sets up a list C, which contains security configuration items associated with critical configuration files. When it is determined that there is a hash inconsistency in the critical configuration files in list A, it is possible to check line by line in list C to determine whether the inconsistency in list A is a false alarm.

[0043] In some embodiments, a yellow light is triggered when the hash of at least one critical configuration file in list A changes, but the internal services in list B are functioning normally.

[0044] Incremental checks are performed using list C, such as examining each security configuration item line by line to see if any changes have occurred. If a security configuration item has changed, it indicates that the change in the critical configuration file's hash was caused by that change. If no security configuration item has changed, but a newline or blank line appears within the security configuration item, it indicates that the newline or blank line within the security configuration item caused the hash change in the critical configuration file. In this case, a warning message can be displayed on the command line indicating a false alarm indicating tampering with the critical configuration file. If it is confirmed that the hash change in the critical configuration file was caused by a change in the security configuration item, maintenance personnel need to manually modify the security configuration item to restore the hash of the critical configuration file to its initial hash.

[0045] A red light is triggered when both List A and List B contain anomalies. If it is confirmed that the change in the HASH of the critical configuration file is caused by a change in the security configuration item, maintenance personnel need to manually modify the security configuration item to restore the HASH of the critical configuration file to its initial HASH. After the HASH of the critical configuration file is restored to its initial HASH, the energy storage device can re-check whether the internal services in List B are operating normally.

[0046] When both List A and List B show red warnings for abnormalities, incremental checks can be performed on List C. For example, check line by line to see if any security configuration items have changed. If a security configuration item has changed, it indicates that the change in the critical configuration file's hash was caused by that change. If no security configuration item has changed, but a carriage return or blank line exists within it, it indicates that the carriage return or blank line in the security configuration item caused the hash change in the critical configuration file. A prompt will be displayed in the command line indicating a false alarm indicating tampering with the critical configuration file. If it is confirmed that the hash change in the critical configuration file was caused by a change in the security configuration item, maintenance personnel need to manually modify the security configuration item to restore the hash of the critical configuration file to its initial hash.

[0047] See Figure 2 The flowchart below shows another method for fault detection of energy storage devices provided in an embodiment of the present invention. Figure 2 The method shown is applied in energy storage devices, such as... Figure 2 As shown, the processing steps of this method include: 201. Identify a list of critical configuration files, A. List A contains the operating system kernel file, network configuration file, audit log, operating system files used for remote login, PAM configuration file, database configuration file, and custom files containing critical data.

[0048] 202. Determine internal service list B, which contains multiple internal services of the energy storage device.

[0049] 203. When the energy storage device is initially started, calculate the initial hash value of the key configuration files in list A, and set the running status of the internal services in list B to normal.

[0050] 204. In response to the arrival of the detection time, check whether the hash values ​​of each key configuration file in list A are consistent with the initial hash values, and also check whether each internal service in list B is running normally.

[0051] 205. If the hash values ​​of each key configuration file in list A are consistent with the initial hash value, and each internal service in list B is running normally, then the green light of the external setting of the energy storage device will be turned on.

[0052] 206. If the hash value of at least one critical configuration file in list A is inconsistent with the initial hash value, but the internal services in list B are functioning normally, then the yellow light on the outside of the energy storage device will be turned on.

[0053] 207. If the hash value of at least one critical configuration file in list A is inconsistent with the initial hash value, and at least one internal service in list B is not functioning properly, then the red light on the outside of the energy storage device will be turned on.

[0054] 208. If the hash values ​​of each key configuration file in list A are consistent with the initial hash value, but at least one internal service in list B is not functioning properly, then the red light on the outside of the energy storage device will be turned on.

[0055] In this embodiment of the invention, the illumination status of the green, yellow, and red lights in the energy storage device can indicate the faults in the energy storage device, which helps maintenance personnel to detect faults in the energy storage device in a timely manner.

[0056] See Figure 3 This is a flowchart of another fault detection method for energy storage devices provided in an embodiment of the present invention. Figure 3 The method shown is applied in energy storage devices, such as... Figure 3 As shown, the processing steps of this method include: 301. Identify a list of critical configuration files, A. List A contains the operating system kernel file, network configuration file, audit log, operating system files used for remote login, PAM configuration file, database configuration file, and custom files containing critical data.

[0057] 302. Determine internal service list B, which contains multiple internal services for the energy storage device.

[0058] 303. Determine security configuration item list C, which contains security configuration items associated with the critical configuration files in list A.

[0059] 304. When the energy storage device is initially started, calculate the initial hash value of the key configuration files in list A, set the running status of the internal services in list B to normal, and set the security configuration items in list C to the preset configuration.

[0060] 305, in response to the arrival of the detection time, checks whether the hash values ​​of each key configuration file in list A are consistent with the initial hash values, and also checks whether each internal service in list B is running normally.

[0061] 306. If the hash values ​​of each key configuration file in list A are consistent with the initial hash value, and each internal service in list B is running normally, then the green light of the external settings of the energy storage device will be turned on.

[0062] 307. If the hash value of at least one critical configuration file in list A is inconsistent with the initial hash value, but the internal services in list B are functioning normally, then turn on the yellow light on the outside of the energy storage device and execute step 310.

[0063] 308. If the hash value of at least one critical configuration file in list A is inconsistent with the initial hash value, and at least one internal service in list B is not functioning properly, then turn on the red light on the outside of the energy storage device and proceed to step 310.

[0064] 309. If the hash values ​​of each critical configuration file in List A are consistent with the initial hash value, but at least one internal service in List B is not functioning properly, then the red light on the outside of the energy storage device will be turned on.

[0065] 310. Check whether the security configuration items in list C have undergone configuration changes.

[0066] 311. If the security configuration item in list C changes, then add an additional yellow light on top of the currently lit light.

[0067] 312. If the security configuration item in list C has not been changed but has a formatting problem, then add an extra yellow light on top of the current lit light, and the yellow light flashes at the set frequency.

[0068] 313. If the security configuration items in list C have not changed and there are no formatting issues, then keep the current lit state.

[0069] It is understood that, in this embodiment of the invention, when the energy storage device has a green light, it indicates that the critical configuration files and internal services within the energy storage device are in a normal state. When the energy storage device has two yellow lights, it indicates that at least one critical configuration file within the energy storage device has been tampered with, but the internal services are operating normally. These two yellow lights also indicate that there is a problem with the security configuration items of the energy storage device, meaning that the tampering of the critical configuration file may be caused by a change in the security configuration items. When the energy storage device has two yellow lights, and one of the yellow lights is flashing, it indicates that at least one critical configuration file within the energy storage device has been tampered with, but the internal services are operating normally. This flashing yellow light also indicates that there is a formatting problem with the security configuration items in list C, meaning that the tampering of the critical configuration file may be caused by a formatting problem. When the energy storage device has one red light and one yellow light, it indicates that at least one critical configuration file within the energy storage device has been tampered with, and at least one internal service is not operating normally. This yellow light also indicates that there is a problem with the security configuration items of the energy storage device, meaning that the tampering of the critical configuration file may be caused by a change in the security configuration items. When an energy storage device illuminates one red light and one yellow light, with one of the yellow lights flashing, it indicates that at least one critical configuration file in the energy storage device has been tampered with, and at least one internal service is malfunctioning. The flashing yellow light also indicates a formatting issue with the security configuration item in list C, suggesting that the tampering with the critical configuration file may be due to a formatting problem. Further, when the energy storage device illuminates only one red light, there are two possibilities: one is that the critical configuration file in the energy storage device has not been tampered with, but at least one internal service in list B is malfunctioning; the other is that at least one critical configuration file in the energy storage device has been tampered with, and at least one internal service is malfunctioning, but the security configuration item in list C has not been changed and there is no formatting issue. Optionally, embodiments of the present invention can further distinguish between the two scenarios of a single red light. In embodiments of the present invention, the illumination status of the green, yellow, and red lights in the energy storage device further subdivides the fault status of the energy storage device, facilitating timely detection of faults by local maintenance personnel and enabling them to accurately locate the faults. In this embodiment of the invention, when a critical configuration file is tampered with, it may be due to a change in the configuration of security configuration items or a format problem. The configuration change or format problem of the relevant security configuration items can be changed. After modification, it can be re-determined whether the critical configuration file has been tampered with and whether the internal service is running normally. If both are normal, the light color of the energy storage device can be changed.

[0070] In some embodiments, a red light is also triggered when an internal service in list B fails, but a critical configuration file in list A does not fail.

[0071] Table 1 Initial State Table for Lists A, B, and C

[0072] Refer to Table 1, which provides an initial state table for List A, List B, and List C according to an embodiment of the present invention. As shown in Table 1, List A contains critical file 1, critical file 2, and critical file 3; List B contains critical service 1 and critical service 2; and List C contains the security configuration item in critical file 1, i.e., root access is disabled via SSH. List A - Critical file 1: This is a critical file specified by the operating system for remote SSH login to the server. Damage to this file will affect subsequent maintenance operations, leading to the inability to log in to the device. List B - Critical service 1: This is the corresponding process. File modification and service unavailability will affect subsequent operations. This file is often hardened to disable root login due to customer information security hardening requirements. Typically, during maintenance, the hardening is removed first, and then the file is restored to prevent malicious access. In Table 1, the initial hashes of critical file 1, critical file 2, and critical file 3 in List A are HASH-A1, HASH-A2, and HASH-A3, respectively. The initial states of critical service 1 and critical service 2 in List B are normal. The initial state of the security configuration item in critical file 1 in List C is normal. In some equipment maintenance work, in order to quickly locate the problem, the maintenance personnel disable the root login restriction in / etc / ssh / sshdconfig, that is, change "PermitRootLogin no" to "PermitRootLogin Yes" and restart the ssh service. However, due to the input error, sshd cannot be used normally. At this time, Table 1 changes to Table 2.

[0073] Table 2 Initial State Table for Lists A, B, and C

[0074] As shown in Table 2, because "PermitRootLogin no" in List C was changed to "PermitRootLoginYes", the HASH value in List A - Critical File 1 changed, causing List B - Critical Service 2 to malfunction. At this time, a red light illuminates in the energy storage device, reminding maintenance personnel to open the cabinet and check the service status of the energy storage device. Optionally, the energy storage device can also display the detection information of critical configuration files and / or internal services on the energy storage device's display interface or send it to the terminal device, so that maintenance personnel can more accurately locate the faults in the energy storage device.

[0075] After maintenance personnel checked the SSH service status and the integrity of the / etc / ssh / sshdconfig file and repaired the relevant faults, the energy storage device re-checked lists A and B, and finally the red light in the energy storage device turned green.

[0076] In another example, when maintaining the "Disable root login in / etc / ssh / sshdconfig" setting, an incorrect line break was added, causing a hash inconsistency. List 1 now becomes List 3: Table 3 shows examples of tables with formatting errors in list C.

[0077] Referring to Table 3, the addition of a space to "PermitRootLogin no" in list C caused a change in the hash of critical file 1 in list A, resulting in a yellow light on the energy storage device. After maintenance personnel removed the space from list C, the yellow light on the energy storage device eventually turned green.

[0078] Table 4 shows that there are inconsistencies in the unique identifiers of the devices listed in list A.

[0079] In another example, the unique identifier of the device, either burned into the chip of the energy storage device or stored in the isolation device, may change. For example, in a scenario where an incorrect device is replaced due to a production line or shipping error, the unique identifier inside the energy storage device may be inconsistent with the expected identifier. In this case, the hash of key file 3 in Table 4 will change, and the energy storage device will light up a yellow light. Maintenance personnel can open the cabinet to check whether the unique identifier of the device matches the device shipping information. If they do not match, since the problem is not a system operation issue, the energy storage device will remain in a yellow light. When maintenance personnel verify the unique identifier of the device against the shipping log and maintenance list and re-execute list A, the yellow light will eventually turn green.

[0080] This invention introduces a safety configuration self-test strategy into energy storage devices. By mapping the safety configuration status of energy storage devices with color indicator lights, it is possible to quickly detect and display the fault status of energy storage devices, making it easier for maintenance personnel to discover and repair faults in energy storage devices in a timely manner.

[0081] Corresponding to the above-mentioned fault detection method for energy storage devices, this embodiment of the invention also provides an energy storage device. For example... Figure 4As shown, the energy storage device 400 includes a processor 401, a memory 402, and a communication unit 403. These components communicate via one or more buses. Those skilled in the art will understand that the structure of the energy storage device 400 shown in the figure does not constitute a limitation on the embodiments of this application. It can be a bus topology, a star topology, and may include more or fewer components than shown, or combine certain components, or have different component arrangements.

[0082] The communication unit 403 is used to establish a communication channel, enabling the energy storage device to communicate with other devices. It can receive user data sent by other devices or send user data to other devices.

[0083] The processor 401 serves as the control center of the energy storage device 400. It connects various parts of the device via various interfaces and lines, and executes software programs, instructions, and / or modules stored in the memory 402, as well as calling data stored in the memory, to perform various functions of the energy storage device and / or process data. The processor can be composed of integrated circuits (ICs), such as a single packaged IC or multiple packaged ICs with the same or different functions connected together. For example, the processor 401 may include a central processing unit (CPU), a microcontroller unit (MCU), etc.

[0084] The memory 402 is used to store the execution instructions of the processor 401. The memory 402 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk. When the execution instructions in the memory 402 are executed by the processor 401, the energy storage device 400 is able to execute the fault detection method of the energy storage device in the embodiments of this application.

[0085] In a specific implementation, this application also provides a computer storage medium, wherein the computer storage medium may store a program, which, when executed, may include some or all of the steps of the fault detection method for energy storage devices provided in this application. The storage medium may be a magnetic disk, optical disk, read-only memory (ROM), or random access memory (RAM), etc.

[0086] In a specific implementation, this application also provides a computer program product, wherein the computer program product includes executable instructions, and when the executable instructions are executed on a computer, the computer executes the fault detection method for energy storage devices provided in this application.

[0087] This application also provides a non-transitory computer-readable storage medium that stores computer instructions, which cause the computer to execute the fault detection method for energy storage devices provided in this application.

[0088] The same or similar parts between the various embodiments in this specification can be referred to mutually. In particular, the device embodiments and terminal embodiments are basically similar to the method embodiments, so the description is relatively simple, and the relevant parts can be referred to the description in the method embodiments.

Claims

1. A fault detection method for an energy storage device, characterized in that, The method includes: Detect whether critical configuration files in energy storage devices have been tampered with; Detecting whether the internal services in the energy storage device are operating normally includes detecting whether the processes in the energy storage device are started, whether the processes are suspended, or whether the processes are in a state of apparent death. If the critical configuration file in the energy storage device is tampered with and the internal services are operating normally, a fault alert will be issued according to the first fault state. If the critical configuration files in the energy storage device have not been tampered with and the internal services are malfunctioning, a fault alert will be issued according to the second fault state. If the critical configuration file in the energy storage device is tampered with or the internal service malfunctions, a fault alert will be issued according to the third fault state. Once it is determined that a critical configuration file in the energy storage device has been tampered with, the method further includes: Identify the security configuration items associated with the critical configuration file that has been tampered with; Check whether the security configuration item has undergone configuration changes; If the security configuration item undergoes a configuration change, a fault alert will be issued according to the fourth fault state. If the security configuration items have not been changed or if there is a formatting problem with the security configuration items, then even if the critical configuration files in the energy storage device have been tampered with and the internal services are running normally, the fault alert will still be issued according to the first fault state.

2. The fault detection method for energy storage equipment according to claim 1, characterized in that, The method further includes: A list of key configuration files is pre-defined, which contains multiple key configuration files; The tampering of critical configuration files in the energy storage device includes: at least one critical configuration file in the list of critical configuration files being tampered with.

3. The fault detection method for energy storage equipment according to claim 1 or 2, characterized in that, Detecting whether critical configuration files in energy storage devices have been tampered with includes: Calculate the hash value of the key configuration file; If the hash value of the key configuration file is consistent with the preset initial value, it is determined that the key configuration file has not been tampered with; If the hash value of the critical configuration file is inconsistent with the preset initial value, it is determined that the critical configuration file has been tampered with.

4. The fault detection method for energy storage equipment according to claim 1, characterized in that, The method further includes: An internal service list is pre-set, which contains multiple internal services; The internal service malfunction includes at least one internal service in the internal service list that is malfunctioning.

5. The fault detection method for energy storage equipment according to claim 1, characterized in that, Provide fault status alerts, including: Different colored indicator lights are used to provide fault alerts for different fault states.

6. The fault detection method for energy storage equipment according to claim 5, characterized in that, The second fault state and the third fault state are indicated by color-coded indicator lights of the same color.

7. The fault detection method for energy storage equipment according to claim 2, characterized in that, The key configuration files in the list of key configuration files include one or more of the following: Operating system kernel files, network configuration files, audit logs, operating system files used for remote login, PAM configuration files, database configuration files, and custom files containing critical data.

8. The fault detection method for energy storage equipment according to claim 1, characterized in that, Fault status alerts also include: The detection information of the key configuration files and / or the internal services is displayed on the display interface of the energy storage device or sent to the terminal device.

9. An energy storage device, characterized in that, include: At least one processor; And at least one memory communicatively connected to the processor, wherein the memory stores program instructions executable by the processor, the processor invoking the program instructions to perform the method according to any one of claims 1 to 8.

Images