Energy storage system data verification method and device and storage medium

Abstract

The invention discloses an energy storage system data verification method and device and a storage medium, and the method comprises the steps: carrying out the processing of collected battery parameters based on a preset data coding rule, obtaining a verification data package, and packaging the verification data package into a target data package in a preset format; and sending the target data packet to each communication node, and controlling each communication node to verify the target data packet by adopting a distributed data verification rule. Through a multi-level data verification mechanism, the reliability of data transmission in the wireless BMS system is improved, the bit error rate is reduced, and the safety of system operation is ensured.

Description

Technical Field

[0001] This application belongs to the field of energy storage system technology, and in particular relates to a data verification method, device and storage medium for energy storage systems. Background Technology

[0002] With the development of energy storage technology, wireless BMS (Battery Management System) has been widely used in electric vehicles, energy storage power stations, and other fields due to its advantages such as simple wiring and high system flexibility. However, wireless communication is susceptible to interference, and problems such as packet loss, bit errors, or delays may occur during data transmission, affecting the security and stability of the system. Therefore, there is an urgent need for an efficient data verification method to ensure the accuracy of data transmission in wireless BMS systems. Summary of the Invention

[0003] In view of this, embodiments of this application provide a data verification method, device, and storage medium for an energy storage system. Through a multi-level data verification mechanism, the reliability of data transmission in a wireless BMS system is improved, the bit error rate is reduced, and the security of system operation is ensured.

[0004] This application provides a data verification method for an energy storage system, including: The collected battery parameters are processed according to preset data encoding rules to obtain a verification data packet; The test data packet is encapsulated into a target data packet of a preset format; The target data packet is sent to each communication node, and each communication node is controlled to verify the target data packet using distributed data verification rules.

[0005] In one embodiment, the process of processing the collected battery parameters based on a preset data encoding rule to obtain a verification data packet includes: Calculate the first cyclic checksum and the first hash digest of the battery parameters, and add a data timestamp to obtain the check data packet.

[0006] In one embodiment, the target data packet with the preset format includes: a start flag, communication node identification information, a verification field, and an end flag; the verification field includes: a first cyclic checksum, a first hash digest, and a data timestamp.

[0007] In one embodiment, controlling each of the communication nodes to verify the target data packet using distributed data verification rules includes: For any communication node, an instruction is sent to the communication node to calculate the second cyclic checksum of the received data and compare the second cyclic checksum with the first cyclic checksum carried in the data packet; If the second cyclic checksum received from the communication node is consistent with the first cyclic checksum, then an instruction is sent to the communication node to calculate the second hash digest of the received data and compare the calculated second hash digest with the first hash digest carried in the data packet. If the second hash digest received from the communication node is consistent with the first hash digest, then an instruction is sent to the communication node to calculate the time difference between the current time and the data timestamp, and to compare the time difference with a preset time difference threshold. If the time difference received from the communication node is less than a preset time difference threshold, a data validity instruction is sent to the communication node.

[0008] In one embodiment, after comparing the second cyclic checksum with the first cyclic checksum carried in the data packet, the method further includes: If the second cyclic checksum received from the communication node does not match the first cyclic checksum carried in the data packet, an instruction to discard the data packet is sent to the communication node, and the data packet is retransmitted.

[0009] In one embodiment, after comparing the calculated second hash digest with the first hash digest carried in the data packet, the method further includes: If the second hash digest received from the communication node is inconsistent with the first hash digest carried in the data packet, an instruction to discard the data packet is issued to the communication node, and the data packet is retransmitted.

[0010] In one embodiment, after controlling each of the communication nodes to verify the target data packet using distributed data verification rules, the method further includes: Send data packet cross-verification instructions to the multiple neighboring communication nodes.

[0011] A second aspect of this application provides a data verification device for an energy storage system, comprising: The processing module is used to process the collected battery parameters based on preset data encoding rules to obtain a verification data packet; The encapsulation module is used to encapsulate the inspection data packet into a target data packet of a preset format; The control module is used to send the target data packet to each communication node and control each communication node to verify the target data packet using distributed data verification rules.

[0012] In one embodiment, the processing module is specifically used for: Calculate the first cyclic checksum and the first hash digest of the battery parameters, and add a data timestamp to obtain the check data packet.

[0013] In one embodiment, the target data packet with the preset format includes: a start flag, communication node identification information, a verification field, and an end flag; the verification field includes: a first cyclic checksum, a first hash digest, and a data timestamp.

[0014] In one embodiment, the control module includes: The first instruction issuing unit is used to issue an instruction to any communication node to calculate the second cyclic check code of the received data and compare the second cyclic check code with the first cyclic check code carried in the data packet. The second instruction issuing unit is used to issue an instruction to the communication node to calculate the second hash digest of the received data and compare the calculated second hash digest with the first hash digest carried in the data packet if the second cyclic check code received from the communication node is consistent with the first cyclic check code. The third instruction issuing unit is used to issue an instruction to the communication node to calculate the time difference between the current time and the data timestamp and compare the time difference with a preset time difference threshold if the second hash digest received from the communication node is consistent with the first hash digest. The fourth instruction issuing unit is used to issue an instruction that the data is valid to the communication node if the time difference received from the communication node is less than a preset time difference threshold.

[0015] In one embodiment, the control module further includes: The fifth instruction issuing unit is used to issue an instruction to the communication node to discard the data packet and resend the data packet if the second cyclic check code received from the communication node is inconsistent with the first cyclic check code carried in the data packet.

[0016] In one embodiment, the control module further includes: The sixth instruction issuing unit is used to issue an instruction to the communication node to discard the data packet and resend the data packet if the second hash digest received from the communication node is inconsistent with the first hash digest carried in the data packet.

[0017] In one embodiment, the apparatus further includes: an instruction issuing module, configured to issue data packet cross-verification instructions to the plurality of neighboring communication nodes.

[0018] A third aspect of this application provides a data verification device for an energy storage system, characterized in that it includes: a processor, a memory, and a computer program stored in the memory and executable on the processor; the processor executes the computer program to implement the steps of the method described in the first aspect above.

[0019] A fourth aspect of this application provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the steps of the method described in the first aspect above.

[0020] The beneficial effects of this application's embodiments are as follows: By processing the collected battery parameters based on preset data encoding rules to obtain a verification data packet, the verification data packet is encapsulated into a target data packet of a preset format; the target data packet is sent to each communication node, and each communication node is controlled to verify the target data packet using distributed data verification rules. Through a multi-level data verification mechanism, the reliability of data transmission in the wireless BMS system is improved, the bit error rate is reduced, and the security of system operation is ensured. Attached Figure Description

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

[0022] Figure 1 A flowchart illustrating a data verification method for an energy storage system provided in an embodiment of this application; Figure 2 A flowchart illustrating a data verification method for an energy storage system provided in another embodiment of this application; Figure 3 A schematic diagram of an energy storage system data verification device provided in an embodiment of this application; Figure 4 A schematic diagram of a data verification device for an energy storage system provided in an embodiment of this application. Detailed Implementation

[0023] The embodiments of the technical solution of this application will now be described in detail with reference to the accompanying drawings. These embodiments are only used to more clearly illustrate the technical solution of this application and are therefore merely examples, and should not be used to limit the scope of protection of this application.

[0024] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application pertains; the terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit the application; the terms “comprising” and “having”, and any variations thereof, in the specification, claims, and foregoing description of the drawings are intended to cover non-exclusive inclusion.

[0025] In the description of the embodiments of this application, technical terms such as "first" and "second" are used only to distinguish different objects and should not be construed as indicating or implying relative importance or implicitly specifying the number, specific order, or primary and secondary relationship of the indicated technical features. In the description of the embodiments of this application, "multiple" means two or more, unless otherwise explicitly defined.

[0026] In this document, the term "embodiment" means that a particular feature, structure, or characteristic described in connection with an embodiment may be included in at least one embodiment of this application. The appearance of this phrase in various places throughout the specification does not necessarily refer to the same embodiment, nor is it a separate or alternative embodiment mutually exclusive with other embodiments. It will be explicitly and implicitly understood by those skilled in the art that the embodiments described herein can be combined with other embodiments.

[0027] In the description of the embodiments in this application, the term "and / or" 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, and B existing alone. Additionally, the character " / " in this document generally indicates that the preceding and following related objects have an "or" relationship.

[0028] In the description of the embodiments of this application, the term "multiple frames" refers to two or more (including two).

[0029] In the description of the embodiments of this application, the technical terms "center," "longitudinal," "lateral," "length," "width," "thickness," "upper," "lower," "front," "rear," "left," "right," "vertical," "horizontal," "top," "bottom," "inner," "outer," "clockwise," "counterclockwise," "axial," "radial," and "circumferential" indicate the orientation or positional relationship based on the orientation or positional relationship shown in the accompanying drawings. They are only for the convenience of describing the embodiments of this application and simplifying the description, and are not intended to indicate or imply that the device or element referred to must have a specific orientation, or be constructed and operated in a specific orientation. Therefore, they should not be construed as limitations on the embodiments of this application.

[0030] This application provides a data verification method for an energy storage system. Through a multi-level data verification mechanism, it improves the reliability of data transmission in a wireless BMS system, reduces the bit error rate, and ensures the safety of system operation.

[0031] Please see Figure 1 As shown, Figure 1 This is a flowchart illustrating a data verification method for an energy storage system provided in an embodiment of this application. Figure 1 As can be seen, the energy storage system data verification method in this application includes steps S110 to S130. Details are as follows: S110: The collected battery parameters are processed according to preset data encoding rules to obtain a verification data packet.

[0032] This step aims to transform raw, discrete sensor data into a robust, standardized data unit suitable for transmission over unreliable channels, whose integrity and authenticity can be verified. In energy storage systems, to ensure the integrity, reliability, and security of battery data, the acquired battery parameters need to be encoded to generate a verification data packet. For example, the acquired battery parameters undergo data formatting, cyclic checksum calculation, hash digest calculation, and timestamp addition to generate a verification data packet.

[0033] The process of processing the collected battery parameters based on a preset data encoding rule to obtain a verification data packet includes: calculating the first cyclic checksum and the first hash digest of the battery parameters, and adding a data timestamp to obtain the verification data packet.

[0034] Battery parameters include physical quantities such as voltage, current, and temperature, as well as derived parameters such as battery state or battery health status (e.g., SOC, SOH). These battery parameters are typically values ​​obtained by converting analog signals to digital signals using an analog-to-digital converter. To ensure data format consistency, preset data encoding rules are used to format the acquired battery parameters. Common encoding methods include fixed-length encoding. Specifically, a fixed number of bytes is reserved for each battery parameter. This encoding method is simple and efficient, suitable for scenarios with fixed battery parameters. For situations where out-of-range data may occur or where more types of parameters need to be supported, variable-length encoding can be used. This encoding method has strong scalability but requires additional storage of length information.

[0035] For the formatted raw data block, a timestamp, a cyclic checksum, and a hash digest are sequentially added. Specifically, the current time is first obtained from the system's high-precision clock source to generate a timestamp field. This timestamp is used to identify the precise moment of data acquisition and is crucial for subsequent data synchronization, historical tracing, and latency analysis. Then, the raw data block and the timestamp field are combined and calculated using a preset generator polynomial (e.g., CRC-16-CCITT or CRC-32) to obtain a first cyclic checksum. This first cyclic checksum is appended to the data and used by the receiving end to detect whether bit errors have occurred during data transmission due to channel noise or other reasons. Finally, a cryptographic hash function (e.g., SHA-256) is applied to the intermediate data body containing the raw data block, timestamp, and first cyclic checksum to generate a fixed-length first hash digest. The first hash digest serves as a digital fingerprint of the data. Its core function is that any alteration to the original data (even in specific error modes that cannot be detected by CRC check) will cause a significant change in the final calculated hash value, thereby enabling the receiving end to verify the authenticity and integrity of the data and preventing the data from being maliciously forged or altered before or after transmission.

[0036] The final generated verification data packet is a structured byte stream encapsulated in order. Its typical structure from beginning to end is as follows: formatted raw data block, timestamp field, first cyclic redundancy check code, and first hash digest.

[0037] S120: Encapsulate the verification data packet into a target data packet of a preset format.

[0038] The aim is to adapt the generated verification data packets, which contain integrity information, to specific communication links, forming standard communication frames that can be correctly identified and processed by each node in the network.

[0039] The target data packet with the preset format includes: a start flag, communication node identification information, a checksum field, and an end flag. The start flag is a specific sequence of bytes or bits used to identify the beginning of a data frame, facilitating frame synchronization by the receiver. The communication node identification information indicates the address or ID of the source node (sender) and / or the target node (receiver), enabling data directionality or multicast. The checksum field carries the checksum data packet generated in S110. This checksum field includes formatted battery parameters, a data timestamp, a first cyclic redundancy check (CRC) code, and a first hash digest. The end flag, also known as the frame end flag or frame checksum sequence, is used to identify the end of a frame or provide additional link-layer error detection codes.

[0040] Through this encapsulation process, the raw battery data is given the address, synchronization, and control information required for network transmission, becoming a complete, routable communication unit.

[0041] S130: Send the target data packet to each communication node, and control each communication node to verify the target data packet using distributed data verification rules.

[0042] It should be noted that the sending node, such as the master control unit, broadcasts or multicasts the target data packet to the network. Each communication node in the network, such as the slave control unit, independently receives the data packet. Each node has the same pre-configured distributed data verification rules, which define a multi-level verification pipeline. After receiving the data packet, the node automatically executes the verification steps in sequence. If any step fails, the subsequent verification is immediately terminated and appropriate action is taken.

[0043] Specifically, the step of controlling each communication node to verify the target data packet using distributed data verification rules includes: for any communication node, issuing an instruction to the communication node to calculate a second cyclic checksum of the received data, and comparing the second cyclic checksum with the first cyclic checksum carried in the data packet; if the second cyclic checksum received from the communication node matches the first cyclic checksum, it indicates that no bit errors occurred during data transmission, and the first level of verification is passed, proceeding to the second level, i.e., issuing an instruction to the communication node to calculate a second hash digest of the received data, and comparing the calculated second hash digest with the first hash digest ... hash digest, it indicates that no bit errors occurred during data transmission, and the first level of verification is passed, proceeding to the second level, i.e., issuing an instruction to the communication node to calculate a second hash digest of the received data, and comparing the calculated second hash digest with the first hash digest carried in the data packet; if the second cyclic The second hash digest is consistent with the first hash digest, indicating that the data has not been tampered with since its generation at the sending end and that the data source is authentic. Passing the second-level verification, it proceeds to the third level, which involves sending an instruction to the communication node to calculate the time difference between the current time and the data timestamp, and comparing this time difference with a preset time difference threshold. If the received feedback from the communication node that the time difference is less than the preset time difference threshold indicates that the data freshness is within an acceptable range, and passes the final verification, an instruction to the communication node that the data is valid is sent. If the received feedback from the communication node that the time difference is greater than or equal to the preset time difference threshold indicates that the data delay is too large and has lost its real-time reference value, the node automatically marks the data as expired, allowing it to be downgraded for use or discarded, and reports a delay alarm.

[0044] After comparing the second cyclic checksum with the first cyclic checksum carried in the data packet, the method further includes: if the second cyclic checksum received from the communication node does not match the first cyclic checksum carried in the data packet, indicating a transmission error, then an instruction to discard the data packet is issued to the communication node, and the data packet is retransmitted. It should be noted that this step can be performed by the current node automatically discarding the data packet, and can optionally send a negative acknowledgment to the sending node to trigger a retransmission mechanism. That is, this step can be performed without external instruction.

[0045] After comparing the calculated second hash digest with the first hash digest carried in the data packet, the method further includes: if the second hash digest received from the communication node is inconsistent with the first hash digest carried in the data packet, indicating that the data may have been maliciously tampered with or contains an unrecoverable complex error, then an instruction to discard the data packet is issued to the communication node, and the data packet is retransmitted. Similarly, this step can also be performed autonomously by the current node, i.e., the current node automatically discards the data packet and can report this event as a security alarm.

[0046] This step is crucial for ensuring data reliability at the end of transmission. Its innovation lies in distributing the verification logic across each communication node and achieving efficient and reliable collaborative verification through progressively more complex verification steps, rather than relying on a central node for unified checking.

[0047] As can be seen from the above analysis, the energy storage system data verification method provided in this application process the collected battery parameters based on preset data encoding rules to obtain a verification data packet. The verification data packet is then encapsulated into a target data packet of a preset format. The target data packet is sent to each communication node, and each communication node verifies the target data packet using distributed data verification rules. This multi-layered data verification mechanism improves the reliability of data transmission in the wireless BMS system, reduces the bit error rate, and ensures the security of system operation.

[0048] Please see Figure 2 As shown, Figure 2 This is a flowchart illustrating a data verification method for an energy storage system provided in another embodiment of this application. Figure 2 It can be seen that this embodiment is similar to... Figure 1 Compared with the illustrated embodiment, the specific implementation process of S210 to S230 is the same. Figure 1 In the illustrated embodiment, the specific implementation processes of S110 to S130 are the same, the difference being that S240 is included after S230. Details are as follows: S210: The collected battery parameters are processed according to preset data encoding rules to obtain a verification data packet.

[0049] S220: Encapsulate the verification data packet into a target data packet of a preset format.

[0050] S230: Send the target data packet to each communication node, and control each communication node to verify the target data packet using distributed data verification rules.

[0051] S240: Send data packet cross-verification instructions to the plurality of neighboring communication nodes.

[0052] By sending cross-validation commands to multiple neighboring communication nodes, the received data packets are compared among these nodes, further improving data reliability. Specifically, if a communication node detects an anomaly, it compares the data with that of its neighboring nodes. Through this comparison, individual communication node malfunctions or abnormal interference can be ruled out, and errors can be corrected using redundant data.

[0053] As can be seen from the above analysis, the energy storage system data verification method provided in this application improves the reliability of data transmission in the wireless BMS system, reduces the bit error rate, and ensures the security of system operation through a multi-level data verification mechanism. Furthermore, it effectively avoids the propagation of data errors caused by the abnormality of a single communication node by sending data packet cross-verification instructions to multiple neighboring communication nodes.

[0054] Please see Figure 3 , Figure 3 This is a schematic diagram of an energy storage system data verification device provided in an embodiment of this application. The energy storage system data verification device includes modules or units used for performing... Figures 1 to 2 The steps in the corresponding embodiments. Please refer to the details. Figures 1 to 2 The relevant descriptions in the corresponding embodiments are shown below. For ease of explanation, only the parts relevant to this embodiment are shown. See also... Figure 3 Energy storage system data verification device 300, including: The processing module 310 is used to process the collected battery parameters based on preset data encoding rules to obtain a verification data packet; Encapsulation module 320 is used to encapsulate the inspection data packet into a target data packet of a preset format; The control module 330 is used to send the target data packet to each communication node and control each communication node to verify the target data packet using distributed data verification rules.

[0055] In one embodiment, the processing module 310 is specifically used for: Calculate the first cyclic checksum and the first hash digest of the battery parameters, and add a data timestamp to obtain the check data packet.

[0056] In one embodiment, the target data packet with the preset format includes: a start flag, communication node identification information, a verification field, and an end flag; the verification field includes: a first cyclic checksum, a first hash digest, and a data timestamp.

[0057] In one embodiment, the control module 330 includes: The first instruction issuing unit is used to issue an instruction to any communication node to calculate the second cyclic check code of the received data and compare the second cyclic check code with the first cyclic check code carried in the data packet. The second instruction issuing unit is used to issue an instruction to the communication node to calculate the second hash digest of the received data and compare the calculated second hash digest with the first hash digest carried in the data packet if the second cyclic check code received from the communication node is consistent with the first cyclic check code. The third instruction issuing unit is used to issue an instruction to the communication node to calculate the time difference between the current time and the data timestamp and compare the time difference with a preset time difference threshold if the second hash digest received from the communication node is consistent with the first hash digest. The fourth instruction issuing unit is used to issue an instruction that the data is valid to the communication node if the time difference received from the communication node is less than a preset time difference threshold.

[0058] In one embodiment, the control module 330 further includes: The fifth instruction issuing unit is used to issue an instruction to the communication node to discard the data packet and resend the data packet if the second cyclic check code received from the communication node is inconsistent with the first cyclic check code carried in the data packet.

[0059] In one embodiment, the control module 330 further includes: The sixth instruction issuing unit is used to issue an instruction to the communication node to discard the data packet and resend the data packet if the second hash digest received from the communication node is inconsistent with the first hash digest carried in the data packet.

[0060] In one embodiment, the device 300 further includes: an instruction issuing module, used to issue data packet cross-verification instructions to the plurality of neighboring communication nodes.

[0061] Please see Figure 4 , Figure 4 This is a schematic diagram of a data verification device for an energy storage system provided in an embodiment of this application. Figure 4 It is understood that the energy storage system data verification device 400 includes: a processor 410, a memory 420, and a computer program 430 stored in the memory 420 and executable on the processor 410; when the processor 410 executes the computer program 430, it implements the steps in the above-described embodiments of the energy storage system data verification methods, for example... Figure 1 The steps S110 to S130 are shown. Alternatively, when the processor 410 executes the computer program 430, it implements the functions of each module / unit in the above-described device embodiments, for example... Figure 3 The functions of modules 310 to 330 are shown.

[0062] For example, computer program 430 may be divided into one or more modules / units, one or more of which are stored in memory 420 and executed by processor 410 to complete this application. The one or more modules / units may be a series of computer program instruction segments capable of performing specific functions, which describe the execution process of computer program 430 in a wireless communication-based energy storage system management device. For example, computer program 430 may be divided into processing modules, packaging modules, and control modules.

[0063] The energy storage system data verification device provided in this embodiment may include, but is not limited to, processors and memory. Those skilled in the art will understand that... Figure 4 This is merely an example of an energy storage system data verification device and does not constitute a limitation on the energy storage system data verification device. It may include more or fewer components than shown in the figure, or combine certain components, or different components. For example, the energy storage system data verification device may also include input / output devices, network access devices, buses, etc.

[0064] The processor 410 may be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or any conventional processor.

[0065] The memory 420 can be an internal storage unit of the energy storage system data verification device, such as a hard drive or memory. The memory 420 can also be an external storage device, such as a plug-in hard drive, smart media card (SMC), secure digital (SD) card, or flash card. Furthermore, the energy storage system data verification device can include both internal and external storage units. The memory 420 is used to store computer programs and other programs and data required by the energy storage system data verification device. The memory 420 can also be used to temporarily store data that has been output or will be output.

[0066] It should be noted that the information interaction and execution process between the above-mentioned devices / units are based on the same concept as the method embodiments of this application. For details on their specific functions and technical effects, please refer to the method embodiments section, and they will not be repeated here.

[0067] This application also provides a network device, which includes: at least one processor, a memory, and a computer program stored in the memory and executable on the at least one processor, wherein the processor executes the computer program to implement the steps in any of the above method embodiments.

[0068] This application also provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the steps described in the various method embodiments above.

[0069] This application provides a computer program product that, when run on a mobile terminal, enables the mobile terminal to implement the steps described in the above-described method embodiments.

[0070] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, all or part of the processes in the methods of the above embodiments of this application can be implemented by a computer program instructing related hardware. The computer program can be stored in a computer-readable storage medium, and when executed by a processor, it can implement the steps of the various method embodiments described above. The computer program includes computer program code, which can be in the form of source code, object code, executable files, or certain intermediate forms. The computer-readable medium can include at least: any entity or device capable of carrying computer program code to a photographing device / terminal device, a recording medium, a computer memory, a read-only memory (ROM), a random access memory (RAM), an electrical carrier signal, a telecommunication signal, and a software distribution medium. Examples include USB flash drives, portable hard drives, magnetic disks, or optical disks. In some jurisdictions, according to legislation and patent practice, computer-readable media cannot be electrical carrier signals or telecommunication signals.

[0071] In the above embodiments, the descriptions of each embodiment have different focuses. For parts that are not described in detail or recorded in a certain embodiment, please refer to the relevant descriptions of other embodiments.

[0072] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0073] In the embodiments provided in this application, it should be understood that the disclosed apparatus / network devices and methods can be implemented in other ways. For example, the apparatus / network device embodiments described above are merely illustrative. For instance, the division of modules or units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between devices or units may be electrical, mechanical, or other forms.

[0074] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0075] The above-described embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application, and should all be included within the protection scope of this application.

Claims

1. A method for verifying data in an energy storage system, characterized in that, include: The collected battery parameters are processed according to preset data encoding rules to obtain a verification data packet; The test data packet is encapsulated into a target data packet of a preset format; The target data packet is sent to each communication node, and each communication node is controlled to verify the target data packet using distributed data verification rules.

2. The data verification method for energy storage systems as described in claim 1, characterized in that, The process of processing the collected battery parameters based on preset data encoding rules to obtain a verification data packet includes: Calculate the first cyclic checksum and the first hash digest of the battery parameters, and add a data timestamp to obtain the check data packet.

3. The data verification method for energy storage systems as described in claim 2, characterized in that, The target data packet in the preset format includes: a start flag, communication node identification information, a verification field, and an end flag; the verification field includes: the first cyclic checksum, the first hash digest, and the data timestamp.

4. The data verification method for energy storage systems as described in claim 3, characterized in that, The control of each communication node to verify the target data packet using distributed data verification rules includes: For any communication node, an instruction is sent to the communication node to calculate the second cyclic checksum of the received data and compare the second cyclic checksum with the first cyclic checksum carried in the data packet; If the second cyclic checksum received from the communication node is consistent with the first cyclic checksum, then an instruction is sent to the communication node to calculate the second hash digest of the received data and compare the calculated second hash digest with the first hash digest carried in the data packet. If the second hash digest received from the communication node is consistent with the first hash digest, then an instruction is sent to the communication node to calculate the time difference between the current time and the data timestamp, and to compare the time difference with a preset time difference threshold. If the time difference received from the communication node is less than a preset time difference threshold, a data validity instruction is sent to the communication node.

5. The data verification method for energy storage systems as described in claim 4, characterized in that, After comparing the second cyclic checksum with the first cyclic checksum carried in the data packet, the method further includes: If the second cyclic checksum received from the communication node does not match the first cyclic checksum carried in the data packet, an instruction to discard the data packet is sent to the communication node, and the data packet is retransmitted.

6. The data verification method for energy storage systems as described in claim 4, characterized in that, After comparing the calculated second hash digest with the first hash digest carried in the data packet, the method further includes: If the second hash digest received from the communication node is inconsistent with the first hash digest carried in the data packet, an instruction to discard the data packet is issued to the communication node, and the data packet is retransmitted.

7. The data verification method for energy storage systems as described in claim 1, characterized in that, After the control of each communication node to verify the target data packet using distributed data verification rules, the method further includes: Send data packet cross-verification instructions to the multiple neighboring communication nodes.

8. A data verification device for an energy storage system, characterized in that, include: The processing module is used to process the collected battery parameters based on preset data encoding rules to obtain a verification data packet; The encapsulation module is used to encapsulate the inspection data packet into a target data packet of a preset format; The control module is used to send the target data packet to each communication node and control each communication node to verify the target data packet using distributed data verification rules.

9. A data verification device for an energy storage system, characterized in that, include: Processor, memory, and computer programs stored in said memory and executable on said processor; When the processor executes the computer program, it implements the steps of the method as described in any one of claims 1 to 7.

10. A computer-readable storage medium storing a computer program, characterized in that, When the computer program is executed by a processor, it implements the steps of the method as described in any one of claims 1 to 7.

Images