ENERGY STORAGE SYSTEM AND METHOD FOR OPERATING AN ENERGY STORAGE SYSTEM - Patent application
The energy storage system addresses the vulnerability of operational data by using encryption codes generated from essential and sampled data, effectively preventing tampering and optimizing computational resources.
Patent Information
- Application Number
- JP2024516504
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Priority Date
- 2021-12-14
- Filing Date
- 2022-11-22
- Publication Date
- 2025-03-18
- Estimated Expiration
- 2042-11-22
AI Technical Summary
Conventional energy storage systems have insufficient protection levels for operational data, making it vulnerable to tampering by third parties, and excessive computing resources are consumed when storing data in an encrypted manner.
The energy storage system employs a battery management system that randomly samples additional data, generates a first encryption code based on essential and sampled data, and transmits it to a recording device. The recording device further generates second and third encryption codes to ensure data integrity and prevent tampering.
This method efficiently encrypts operational data, preventing arbitrary tampering by third parties, while reducing the computational burden by only encrypting specific patterns of data, thus maintaining data integrity and security.
Smart Images

Figure 0007648299000001 
Figure 0007648299000002 
Figure 0007648299000003
Abstract
Description
[Technical field]
[0001] The present invention claims the benefit of priority based on Korean Patent Application No. 10-2021-0179153 filed on December 14, 2021, and all contents disclosed in the documents of the Korean patent application are incorporated as part of this specification.
[0002] SUMMARY OF THE DISCLOSURE The embodiments disclosed herein relate to energy storage systems and methods of operating energy storage systems. [Background technology]
[0003] An energy storage system (ESS) is a system that stores electrical energy and manages it so that it can be used when needed, and is generally installed in power plants that operate large-scale energy networks or buildings with high energy consumption, etc., and includes hundreds to thousands of batteries. A battery management system (BMS) included in an energy storage system constantly monitors the status of each battery (e.g., the voltage, current, temperature, and charge state of the battery cell) and selectively charges / discharges the batteries or controls connections with other devices for efficient operation of the entire system.
[0004] Operational data required for the operation of an energy storage system includes additional information such as battery status information (battery cell current, voltage, temperature, charging state, etc.) collected by sensors, network information for communication between devices, and BMS setting values, and is stored in a logging device by the battery management system and the controller that controls it. The integrity of such operational data must be maintained as it is core information that is the basis for quality assurance services for customers, but the protection level of operational data in conventional energy storage systems is insufficient, making it easy for third parties to arbitrarily tamper with the data. In addition, most energy storage systems are operated as standalone systems, and real-time collection of data and storage in a server are limited, making it difficult to protect the data, and there is a problem of excessive consumption of computing resources when the entire data is encrypted and stored to prevent tampering. Summary of the Invention [Problem to be solved by the invention]
[0005] It is an object of the embodiments disclosed herein to provide a method of operation for encrypting and storing operational data of an energy storage system in an efficient manner to prevent tampering with the data. Another object of the embodiments disclosed herein is to provide an energy storage system that operates according to said method of operation.
[0006] The technical problems of the embodiments disclosed in this document are not limited to the technical problems mentioned above, and other technical problems not mentioned will be clearly understood by those skilled in the art from the following description. [Means for solving the problem]
[0007] A battery management system according to one embodiment includes a BMS controller that acquires operational data of an energy storage system including essential data and additional data related to a battery state, randomly samples the additional data to acquire sampling data, and generates a first encryption code based on the essential data and the sampling data, and a communication unit that transmits the operational data with the first encryption code added to a recording device.
[0008] According to one embodiment, the first encryption code may include first data indicating an index of the sampling data, and second data generated by encrypting the essential data and the sampling data.
[0009] An energy storage system according to one embodiment includes a battery management system that acquires operational data of an energy storage system including essential data and additional data related to a battery state, randomly samples the additional data to acquire sampling data, generates a first encryption code based on the essential data and the sampling data, adds the first encryption code to the operational data, and transmits the generated data to a recording device; and a recording device that receives and stores the operational data with the first encryption code added from the battery management system.
[0010] According to one embodiment, the recording device can generate a second cryptographic code based on the operational data to which the first cryptographic code has been added, and add the second cryptographic code to the operational data and store it in a memory of the recording device.
[0011] According to an embodiment, the second encryption code may be generated based on a first encryption code of operational data received in a current cycle and a second encryption code of operational data received in a previous cycle.
[0012] According to one embodiment, when operational data stored in the recording device branches, the recording device can generate a third encryption code based on the second encryption code added to the operational data in the cycle immediately before the branch.
[0013] According to one embodiment, the third cryptographic code can be generated based on the second cryptographic code added to the operational data in the cycle immediately before branching, the identification number of the recording device, and information on the time when the operational data began to be stored in the recording device.
[0014] According to an embodiment, the second data, the second encryption code, and the third encryption code constituting the first encryption code may be generated by a CRC (Cyclic Redundancy Check) encryption method.
[0015] In one embodiment, the essential data may include at least one of current time information, the voltage, current, temperature, and charging state of the battery, and the additional data may include at least one of network setting information, internet protocol information, and settings of a battery management system.
[0016] According to one embodiment, a method for operating an energy storage system includes the steps of acquiring operational data of the energy storage system, the operational data including essential data and additional data related to a battery state, randomly sampling the additional data to acquire sampling data, generating a first encryption code based on the essential data and the sampling data, and adding the first encryption code to the operational data and transmitting the operational data to a recording device.
[0017] According to one embodiment, the method may further include a step of generating a second encryption code based on the operational data to which the first encryption code has been added, and a step of adding the second encryption code to the operational data and storing it in a memory of the recording device.
[0018] According to one embodiment, when the operational data stored in the memory branches, the recording device may further include a step of generating a third encryption code based on the second encryption code added to the operational data in the cycle immediately before the branch. Effect of the Invention
[0019] According to the above embodiment, the operation data of the energy storage system is encrypted, and the data can be prevented from being tampered with by a third party. Specifically, by adding an encryption code generated using the operation data to the data, it is possible to prevent tampering such as stealing the operation data received by the recording device at each period, mixing the order of the periodic data to falsify the pattern, or using the entire data branched from another recording device to falsify the usage pattern. In addition, this document may provide a variety of other benefits that may be perceived directly or indirectly. [Brief description of the drawings]
[0020] In order to more clearly describe the embodiments disclosed in this document or the technical solutions of the prior art, drawings necessary for the description of the embodiments are briefly introduced below. It should be understood that the following drawings are only for describing the embodiments of the present specification and are not intended to be limiting. In addition, for the sake of clarity, the expressions of some components in the drawings may be exaggerated or omitted.
[0021] [Figure 1] FIG. 1 is a block diagram showing a configuration of an energy storage system according to an embodiment. [Diagram 2] 1 is a block diagram showing a configuration of a battery management system according to an embodiment; [Diagram 3] FIG. 1 is a block diagram showing a configuration of a recording apparatus according to an embodiment. [Figure 4] 1 is a flow chart illustrating a method of operating an energy storage system according to an embodiment. [Diagram 5] 1 illustrates operational data to which a first encryption code has been added, according to one embodiment. [Figure 6] 10 is a flowchart illustrating a method of operating an energy storage system according to another embodiment. [Figure 7]13 illustrates operational data to which a second encryption code has been added, according to one embodiment. [Figure 8] 10 is a flowchart illustrating a method of operating an energy storage system according to still another embodiment. [Figure 9] 13 illustrates operational data to which a third encryption code has been added, according to one embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0022] Hereinafter, the embodiments disclosed in this document will be described in detail with reference to the exemplary drawings. When referring to components in each drawing, it should be noted that the same components are referred to by the same reference numerals as much as possible when they are displayed in other drawings. In addition, when describing the embodiments disclosed in this document, if a detailed description of related publicly known configurations or functions is deemed to hinder understanding of the embodiments disclosed in this document, the detailed description will be omitted.
[0023] The terms used in this document are currently selected as widely used as possible while taking into consideration the functions, but this may vary depending on the intention or practice of the technical personnel in the field, or the emergence of new technology. In addition, in certain cases, the applicant may arbitrarily select some terms, and in such cases, the meanings of these terms will be described in the description of the specification. Therefore, it is clear that the terms used in this document must be interpreted based on the substantial meanings of the terms and the overall content of this document, rather than simply the names of the terms.
[0024] The terms used in this document are merely used to describe a particular embodiment and are not intended to limit the scope of other embodiments. A singular expression may include a plural expression unless otherwise clearly indicated in the context.
[0025] Energy storage system configuration 1 is a block diagram showing a configuration of an energy storage system according to an embodiment. Referring to FIG. 1, an energy storage system 10 according to an embodiment may include a battery module 100, a battery management system 110, and a recording device 120.
[0026] The battery module 100 includes at least one battery cell, and is an assembly in which a certain number of battery cells are bundled and placed in a frame to protect the battery cells from external impact, heat, vibration, etc., and to manage information. A battery cell is a basic unit of a battery configured to be able to use electrical energy by charging and discharging it, and is fabricated by placing components such as a positive electrode, a negative electrode, a separator, and an electrolyte in a pouch, cylindrical, or rectangular case. According to an embodiment, the battery cell may be, but is not limited to, a lithium-ion (Li-ion) battery, a lithium-ion polymer (Li-ion polymer) battery, a nickel-cadmium (Ni-Cd) battery, a nickel-metal hydride (Ni-MH) battery, etc.
[0027] The battery management system 110 collects information on the battery cells included in the battery module 100, such as the voltage, current, temperature, resistance, SOC (State of Charge), and SOH (State of Health) of each battery cell, in order to control and manage the battery module 100. Also, for efficient operation of the battery, the battery management system 110 can selectively charge or discharge the battery cells or control connection with other battery cells. The battery management system 110 acquires essential data (e.g., data related to the battery state, such as current, voltage, and temperature) collected from the battery module 100 and other remaining additional data (e.g., additional data required for system operation, such as network information and BMS setting values) every period and transmits them to the recording device 120.
[0028] 2 is a block diagram showing a configuration of a battery management system according to an embodiment. Referring to FIG. 2, the battery management system 110 includes a BMS controller 111 and a communication unit 112.
[0029] The BMS controller 111 may acquire operational data of the energy storage system including required data and additional data related to the state of the battery, randomly sample the additional data to acquire sampling data, and generate a first encryption code based on the required data and the sampling data. The communication unit 112 can transmit the operation data to which the first encryption code has been added to the recording device 120 .
[0030] 1 shows only one battery module 100, the energy storage system 10 of the embodiment is not limited to using a single cell module, and may use multiple battery modules. In this case, the battery management system 110 may be composed of multiple slave battery management systems (e.g., a module battery management system) that control the respective battery modules, and a master battery management system (e.g., a rack battery management system, a bank battery management system, etc.) that receives information from the slave battery management systems and transmits it to other devices, or performs integrated control of the slave battery management systems.
[0031] According to an embodiment, the energy storage system 10 may further include an integrated controller (not shown) for controlling the operation of the battery management system 110 and / or the recording device 120 according to a user operation or a preprogrammed algorithm. According to an embodiment, the integrated controller may control the operation of the battery management system 110 according to setting values (e.g., a period at which operational data is recorded, network settings, etc.) inputted via a user interface. The integrated controller may be, for example, a Battery System Controller (BSC) commonly used in battery control systems.
[0032] The recording device 120 receives and stores operational data of the energy storage system 10 from the battery management system 110 (consisting of essential data related to the state of the batteries and the remaining additional data).
[0033] 3 is a block diagram showing the configuration of a recording device according to an embodiment of the present invention. Referring to FIG. 3, a recording device 120 is made up of a recording device controller 121 and a memory 122.
[0034] The recording device controller 121 may be configured to read the operation data stored in the memory 122 in response to a call from the outside (e.g., a user terminal, the battery management system 110, etc.), process the operation data according to an instruction, and transmit or display the operation data to an external device. In addition, in order to ensure the continuity of the operation data received from the battery management system 110, the recording device controller 121 may generate a second encryption code based on the first encryption code.
[0035] The memory 122 stores the operational data for which the second encryption code is generated. The memory 122 may be, for example, a RAM, a ROM, a semiconductor memory such as a flash memory, a magnetic disk, an optical disk, or other storage medium, and is shown as being located inside the recording device 120, but may be located outside.
[0036] The configuration of the energy storage system described above is merely an example, and components necessary for performing the operation method described below may be added or non-essential components may be removed. Although each component is shown as a single unit in FIG. 1, this is not limiting, and two or more units may be combined to operate as one component or may operate in parallel.
[0037] Method of operating an energy storage system Hereinafter, an embodiment of an operating method for encrypting and storing operational data using components of the energy storage system will be described. The components of the energy storage system will be described with reference to FIGS. 1 to 3, and the reference numerals used in FIGS. 1 to 3 are also included.
[0038] FIG. 4 is a flow chart illustrating a method of operating an energy storage system according to one embodiment. First, the battery management system 110 included in the energy storage system 10 performs a step of acquiring operation data of the energy storage system 10 (S410). The operation data is composed of required data related to the state of the battery and the remaining additional data. For example, the required data may include one or more pieces of data directly related to the state of the battery, such as current time information (time) and the voltage (V), current (I), temperature (T), and state of charge (SOC) of each battery cell at the current time. The additional data may include one or more pieces of data not directly related to the state of the battery, such as network setting information, IP information, and BMS setting values. The required data and additional data in this document are terms used merely for distinction, and data not listed as examples may be further included or excluded.
[0039] The battery management system 110 can obtain essential data through sensors provided in the battery cells. It can also obtain additional data from information input through a user interface or from information already stored in the memory. The battery management system 110 obtains operational data every period (e.g., every second), and the period for obtaining data can be set arbitrarily.
[0040] Next, the battery management system 110 performs a step (S420) of generating a first encryption code (also called a "Check Byte") to ensure the integrity of the operational data transmitted to the recording device 120. The first encryption code can be generated based on the required data and the additional data.
[0041] Next, a step S430 is performed in which the first encryption code is added to the operation data and transmitted to the recording device 120. The step S430 may be performed via the communication unit 112 of the battery management system 110.
[0042] Figure 5 shows the structure of the operational data to which the first encryption code generated in step S420 has been added. Referring to Figure 5, the operational data (Dn) in the nth period is composed of essential data (time (Time), battery voltage (V), current (I), temperature (T), state of charge (SOC)) and additional data (network setting information (ETC1), IP information (ETC2), BMS setting value (ETC3), ...), and the first encryption code (CAn) is added to ensure complete transmission of the operational data (Dn).
[0043] According to one embodiment, the first encryption code (CAn) may be composed of first data (2-byte size) indicating an index of sampling data obtained by randomly sampling additional data, and second data (2-byte size) generated by encrypting the essential data and the sampling data in a specified manner.
[0044] According to an embodiment, the second data may be generated by a CRC 16 or CRC 32 encryption method. A cyclic redundancy check (CRC) is a method for determining a check value for checking whether an error exists in transmitted data when transmitting data through a network. Before transmitting data, a CRC value is calculated based on a value of given data, and the CRC value is attached to the data and transmitted. After the data transmission is completed, a CRC value is calculated based on a value of received data, and the two values are compared to detect an error. CRC 16 applies a 16-bit polynomial to a data block, and CRC 32 applies a 32-bit polynomial. The administrator may adopt the CRC 32 encryption method for more accurate error detection.
[0045] The steps (S410 to S430) are repeated every period. The recording device 120 can calculate the CRC value again using the first encryption code (CAn) to check whether the operational data has been tampered with during transmission. If the CRC values do not match (i.e., if tampering of the operational data is suspected), the operational data can be notified to the administrator without being stored in the memory 122.
[0046] Fig. 6 is a flowchart showing an operation method of an energy storage system according to another embodiment. Steps (S610 to S630) in Fig. 6 performed by the battery management system 110 are similar to steps (S410 to S430) in Fig. 4, so duplicated descriptions will be omitted.
[0047] Following steps (S610 to S630), the controller 121 of the recording device 120 performs step (S640) of generating a second encryption code (also called a "Chain Byte") based on the operational data to which the first encryption code has been added in order to ensure the continuity of the operational data received every cycle. This is to prevent a third party from falsifying the usage pattern by arbitrarily mixing the order of the operational data. According to one embodiment, the second encryption code (CBn) of the operational data received in the nth cycle can be generated by encrypting the first encryption code (CAn) and the second encryption code (CBn-1) of the operational data received in the previous cycle in a specified method (e.g., CRC 16 or CRC 32 encryption method).
[0048] 7 shows operational data to which a second encryption code has been added according to one embodiment. Referring to FIG. 7, a first encryption code (CA1) has been added to operational data (D1) received by the recording device 120 in a first period. The second encryption code (CB1) in the first period can be preset to a specific value since it cannot be generated using data from a previous period.
[0049] The operational data (D2) received in the second cycle has a first encryption code (CA2) added thereto, and the recording device 120 encrypts the first encryption code (CA2) and the second encryption code (CB1) of the operational data (D1) of the first cycle in a specified manner to generate a second encryption code (CB2). In a similar manner, the second encryption code (CB3) of the operational data (D3) of the third cycle can be generated based on the first encryption code (DA3) and the second encryption code (CB2) of the operational data (D2) of the previous cycle (second cycle).
[0050] In this way, the recording device 120 can ensure the continuity of data in the form of a block chain by adding a second encryption code (Chain Byte) to the operation data every cycle. If the second encryption code is again CRC-converted and the values do not match (i.e., if the order of the operation data chart is suspected to have been tampered with), the operation data is not stored in the memory 122 and the administrator is notified.
[0051] 8 is a flowchart showing an operation method of the energy storage system according to another embodiment. Steps (S810 to S850) in FIG. 8 performed by the battery management system 110 and the recording device 120 are similar to steps (S610 to S650) in FIG. 6, so that the overlapping description will be omitted.
[0052] Following steps (S810 to S850), the recording device 120 performs a step (S860) of determining whether or not the operational data stored in the recording device 120 has branched, and if data branching has occurred (S860 → Yes), performs a step (S870) of generating a third encryption code based on the second encryption code added to the operational data for the cycle immediately before the branching.
[0053] The third encryption code (also called "Device Byte") is a code for identifying the series of operational data before the branch and for preventing the series of operational data from being tampered with after the branch. For example, the encryption code is added to the set of operational data before the branch to prevent a third party from reusing the entire data of another recording device to falsify the usage pattern.
[0054] According to one embodiment, the third encryption code of the operational data may be generated based on the second encryption code added to the operational data of the cycle immediately before the branch, the identification number (serial number) of the recording device 120, and information (Unixtime) of the time when the series of operational data started to be stored in the memory 122 of the recording device 120. The third encryption code may be generated by encrypting the information in a specified manner (e.g., CRC 16 or CRC 32).
[0055] FIG. 9 shows operational data to which a third encryption code has been added according to an embodiment. Referring to FIG. 9, the recording device 120 receives and stores operational data (D1, D2, ..., Dn) from the first period to the nth period, and the first encryption code and the second encryption code are added to each operational data. If a branch occurs after storing the operational data (Dn) up to the nth period (the first branch occurs), the recording device 120 generates a third encryption code (CC1) corresponding to the first branch using the second encryption code (CBn) of the operational data (Dn) and adds it to the last operational data (Dn) immediately before the branch. The third encryption code can be generated by encrypting the second encryption code (CBn), the identification number of the recording device 120 currently recording, and storage start time information (i.e., the time when D1 is stored).
[0056] After the first branch, the recording device 120 receives the operational data (Dn+1, Dn+2, ..., Dm) corresponding to the n+1th cycle, the n+2th cycle, ..., the mth cycle. If another branch occurs after the mth cycle (second branch occurs), the recording device 120 generates a third encryption code (CC2) corresponding to the second branch using the second encryption code (CBm) of the operational data (Dm) and adds it to the last operational data (Dm) immediately before the branch. The third encryption code can be generated by encrypting the second encryption code (CBm), the identification number of the recording device 120 currently recording, and storage start time information (i.e., the time when Dn+1 is stored).
[0057] Referring back to FIG. 8, if no data branch has occurred (S860→No), the process returns to step S810 to obtain the operation data for the next period and store it in the recording device 120, and the process is repeated.
[0058] The method of operating the energy storage system according to the above-described embodiment may be implemented as an application or may be implemented in the form of program instructions executable by various computer components and recorded on a computer-readable recording medium. The computer-readable recording medium may include program instructions, data files, data structures, and the like, alone or in combination.
[0059] According to the above-described operation method, the operation data of the energy storage system is encrypted, and the data can be prevented from being arbitrarily tampered with by a third party. In the conventional energy storage system, the protection level of the operation data is insufficient, and the data can be easily arbitrarily tampered with. When the entire data is encrypted and stored to prevent tampering, there is a problem of consuming an excessive amount of computing resources. According to the embodiment provided in this document, instead of encrypting the entire operation data, a cryptographic code generated using a pattern of a part of the data is added, so that it is possible to efficiently prevent tampering such as stealing the operation data received by the recording device for each period, mixing the order of the periodic data to falsify a pattern, or falsifying a usage pattern by utilizing the entire data branched from another recording device.
[0060] Although it has been described above that all components constituting the embodiments are combined or operate in combination, the present invention is not necessarily limited to such an embodiment, and all components may be selectively combined and operate in one or more combinations within the scope of the purpose. Furthermore, the terms "include," "constitute," "have," and the like described above mean that the relevant component can be contained within the description, unless otherwise specified, and therefore should not be interpreted as excluding other components, but as including other components.
[0061] The above description is merely an illustrative example of the technical ideas disclosed in this document, and a person having ordinary knowledge in the technical field to which the embodiments disclosed in this document belong can make various modifications and variations within the scope of the essential characteristics of the embodiments disclosed in this document. Therefore, the embodiments disclosed in this document are intended to explain, not to limit, the technical ideas disclosed in this document, and such embodiments do not limit the scope of the technical ideas disclosed in this document. The scope of protection of the technical ideas disclosed in this document should be interpreted according to the claims below, and all technical ideas within the equivalent scope should be interpreted as being included in the scope of rights of this document.
Claims
1. a BMS controller that acquires operational data of the energy storage system, the operational data including essential data and additional data related to a state of a battery, randomly samples the additional data to acquire sampling data, and generates a first encryption code based on the essential data and the sampling data; a communication unit that transmits the operation data to which the first encryption code has been added to a recording device; a battery management system including:
2. 2. The battery management system according to claim 1, wherein the first encryption code includes first data indicating an index of the sampling data, and second data generated by encrypting the essential data and the sampling data.
3. a BMS controller that acquires operation data of an energy storage system including essential data and additional data related to a state of a battery, randomly samples the additional data to acquire sampling data, and generates a first encryption code based on the essential data and the sampling data; and a communication unit that transmits the operation data to which the first encryption code has been added to a recording device; a recording device that receives the operation data to which the first encryption code has been added from the battery management system and stores the operation data; 23. An energy storage system comprising:
4. The energy storage system of claim 3 , wherein the first encryption code includes first data indicating an index of the sampling data, and second data generated by encrypting the essential data and the sampling data.
5. 5. The energy storage system of claim 4, wherein the recording device includes: a recording device controller that generates a second encryption code based on the operational data to which the first encryption code has been added; and a memory that adds the second encryption code to the operational data and stores the data.
6. The energy storage system of claim 5 , wherein the second encryption code is generated based on the first encryption code of operational data received in a current cycle and a second encryption code of operational data received in a previous cycle.
7. 6. The energy storage system of claim 5, wherein when the operational data stored in the recording device branches, the recording device generates a third encryption code based on the second encryption code added to the operational data in the cycle immediately before the branch.
8. 8. The energy storage system of claim 7, wherein the third encryption code is generated based on the second encryption code added to the operational data in the cycle immediately before the branch, an identification number of the recording device, and information on the time when the operational data began to be stored in the recording device.
9. The energy storage system according to claim 8 , wherein the second data, the second encryption code, and the third encryption code constituting the first encryption code are generated by a Cyclic Redundancy Check (CRC) encryption method.
10. The required data includes at least one of current time information, voltage, current, temperature, and charging state of the battery; The energy storage system of claim 3 , wherein the additional data includes at least one of network configuration information, internet protocol information, and battery management system settings.
11. 1. A method of operating an energy storage system, comprising: acquiring operational data of the energy storage system, including essential and additional data related to a battery condition; randomly sampling the additional data to obtain sampled data, and generating a first encryption code based on the essential data and the sampled data; adding the first encryption code to the operational data and transmitting the operational data to a recording device; A method of operating an energy storage system comprising:
12. 12. The method of claim 11, wherein the first encryption code includes first data indicating an index of the sampling data, and second data generated by encrypting the essential data and the sampling data.
13. generating a second encryption code based on the operation data to which the first encryption code has been added; The method of claim 12, further comprising the step of adding the second encryption code to the operational data and storing the operational data in a memory of the recording device.
14. 14. The method of claim 13, wherein the second encryption code is generated based on the first encryption code of the operational data received in a current cycle and a second encryption code of the operational data received in a previous cycle.
15. 14. The method for operating an energy storage system according to claim 13, further comprising the step of, when the operational data stored in the memory diverges, the recording device generating a third encryption code based on the second encryption code added to the operational data in the cycle immediately before the divergence.
16. 16. The method for operating an energy storage system according to claim 15, wherein the third encryption code is generated based on information about the second encryption code added to the operational data in the cycle immediately before the branching, an identification number of the recording device, and a time when the operational data began to be stored in the memory of the recording device.
17. 17. The method of claim 16, wherein the second data, the second encryption code, and the third encryption code constituting the first encryption code are generated by a CRC 16 or CRC 32 encryption method.
18. The required data includes at least one of current time information, voltage, current, temperature, and charging state of the battery; 12. The method of claim 11, wherein the additional data includes at least one of network configuration information, internet protocol information, and battery management system settings.
Citation Information
Patent Citations
Battery information management server, battery information recording medium, and battery information management system
JP2013218909A
Battery monitoring system
JP2019221050A
Methods and system for multi-level data security
KR1020140032307A
Encoder, decoder and method
KR1020170036100A
Battery management system and communication method thereof
KR1020210051462A