Single cell-oriented full life cycle data binding method and device, and storage medium

Abstract

The invention discloses a full life cycle data binding method and device for a single cell, and a storage medium, and relates to the technical field of battery management. The method comprises the following steps: acquiring battery cell identity information carried by a two-dimensional code attached to a battery cell body; carrying out structured coding on the battery cell identity information and the currently collected battery cell initial state data to generate a coded data packet; and writing the coded data packet into a first storage area of a special data storage chip arranged in the battery cell body to complete physical binding of the battery cell identity information and the initial state data. The identity information and the initial state data of the battery cell are written into the special chip arranged in the battery cell body, so that the battery cell becomes an inseparable physical attribute, the risk of'identity loss' of the battery cell is fundamentally eradicated, and a physical guarantee is provided for tracing of a whole industrial chain.

Description

Technical Field

[0001] This application belongs to the field of battery management technology, and in particular relates to a method, device and storage medium for full life cycle data binding for a single battery cell. Background Technology

[0002] In fields such as new energy vehicles and large-scale energy storage, batteries are core components, and their safety, reliability, and traceability are of paramount importance. Effective identification management and full lifecycle data recording of individual battery cells are key prerequisites for ensuring battery system safety, achieving accurate condition assessment, optimizing use and maintenance, and promoting tiered utilization.

[0003] Currently, battery cell identification primarily relies on QR codes and barcodes printed or laser-engraved on the cell casing. These surface markings are highly susceptible to wear, contamination, or complete detachment during subsequent handling, assembly, use, and harsh environments (such as vibration, high and low temperatures, and chemical corrosion). Once the markings are damaged, the cell becomes a "black box," its identification information is lost, and it cannot be linked to performance data in the backend database, leading to a disruption of traceability throughout the entire supply chain. Furthermore, initial performance data (such as capacity, internal resistance, and open-circuit voltage) is stored in the Manufacturing Execution System (MES); post-assembly test data resides in the module / PACK factory's system; vehicle operation data is stored in the Battery Management System; and new data is generated during maintenance and recycling. This data is scattered across different systems, lacking a unified data carrier and exchange standard strongly linked to the physical entity of the cell, making it difficult to efficiently connect them into a complete "cell life record."

[0004] In summary, there is currently a lack of reliable technical solutions that can ensure the inseparability of battery cell identity information, accompany the battery cell throughout its lifespan, and systematically and structurally record complete battery cell data. Summary of the Invention

[0005] In view of this, the embodiments of this application provide a method, device and storage medium for full life cycle data binding of a single battery cell. By structurally encoding the battery cell identity information and initial state data and writing them into a specific area of ​​a dedicated chip built into the battery cell, the physical binding of the battery cell identity information and data is realized, fundamentally eliminating the risk of battery cell "identity loss" and providing physical protection for traceability of the entire industry chain.

[0006] This application provides a method for full lifecycle data binding for individual battery cells, including the following steps: Obtain the battery cell identification information carried by the QR code attached to the battery cell body; The cell identification information and the currently collected initial state data of the cell are structured and encoded to generate an encoded data packet; The encoded data packet is written into the first storage area of ​​the dedicated data storage chip built into the battery cell body, thus completing the physical binding of the battery cell identity information and the initial state data.

[0007] In one embodiment, the method further includes: During the use or testing cycle of the battery cell, process status data of the battery cell is generated; The process status data is structured and encoded to generate process data records; The process data is recorded and written into the second storage area of ​​the dedicated data storage chip.

[0008] In one embodiment, the second storage area employs a circular write strategy, whereby the earliest written data record is overwritten when the storage space is full.

[0009] In one embodiment, the structured encoding includes: converting each data item in the cell identity information and initial state data into an encoded record containing a type identifier, data length, and data value according to a preset encoding rule, and combining multiple encoded records to form the encoded data packet.

[0010] In one embodiment, the type identifier is used to distinguish at least one or more of the following: unique cell identification code, initial capacity, DC internal resistance, production date, production line number, and material batch information.

[0011] In one embodiment, the first storage area is a read-only or write-once area; and / or, the dedicated data storage chip communicates via an I2C or single-bus interface.

[0012] In one embodiment, the step of obtaining the cell identity information includes: scanning an encrypted QR code and decrypting the obtained encrypted data to obtain plaintext identity information.

[0013] A second aspect of this application provides a data binding device for the entire lifecycle of a single battery cell, comprising: The acquisition module is used to acquire the battery cell identification information carried by the QR code attached to the battery cell body; The encoding module is used to perform structured encoding of the cell identity information and the currently collected initial state data of the cell to generate an encoded data packet; The first writing module is used to write the encoded data packet into the first storage area of ​​the dedicated data storage chip built into the battery cell body, thereby completing the physical binding of the battery cell identity information and the initial state data.

[0014] In one embodiment, the device further includes: The first generation module is used to generate process status data of the battery cell during the use or testing cycle of the battery cell. The second generation module is used to perform structured encoding on the process state data to generate process data records; The second writing module is used to write the process data records into the second storage area of ​​the dedicated data storage chip.

[0015] In one embodiment, the second storage area employs a circular write strategy, whereby the earliest written data record is overwritten when the storage space is full.

[0016] In one embodiment, the structured encoding includes: converting each data item in the cell identity information and initial state data into an encoded record containing a type identifier, data length, and data value according to a preset encoding rule, and combining multiple encoded records to form the encoded data packet.

[0017] In one embodiment, the type identifier is used to distinguish at least one or more of the following: unique cell identification code, initial capacity, DC internal resistance, production date, production line number, and material batch information.

[0018] In one embodiment, the first storage area is a read-only or write-once area; and / or, the dedicated data storage chip communicates via an I2C or single-bus interface.

[0019] In one embodiment, the step of obtaining the cell identity information includes: scanning an encrypted QR code and decrypting the obtained encrypted data to obtain plaintext identity information.

[0020] A third aspect of this application provides a data binding device for the entire lifecycle of a single battery cell, 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.

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

[0022] The data binding method for the entire lifecycle of a single battery cell provided in this application includes: acquiring the battery cell identity information carried by a QR code attached to the battery cell; performing structured encoding on the battery cell identity information and the currently collected initial state data of the battery cell to generate an encoded data packet; and writing the encoded data packet into the first storage area of ​​a dedicated data storage chip embedded in the battery cell, thus completing the physical binding of the battery cell identity information and the initial state data. By writing the battery cell identity information and initial state data into a dedicated chip embedded in the battery cell, they become inseparable physical attributes of the battery cell, fundamentally eliminating the risk of "identity loss" of the battery cell and providing physical protection for traceability throughout the entire industry chain. Attached Figure Description

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

[0024] Figure 1 A flowchart illustrating a method for full lifecycle data binding of a single battery cell according to an embodiment of this application; Figure 2 A flowchart illustrating a method for full lifecycle data binding of a single battery cell, provided in another embodiment of this application; Figure 3 A schematic diagram of a data binding device for the entire life cycle of a single battery cell provided in an embodiment of this application; Figure 4 This is a schematic diagram of a data binding device for the entire life cycle of a single battery cell, provided as an embodiment of this application. Detailed Implementation

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

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

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

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

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

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

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

[0032] This application provides a method for full lifecycle data binding for individual battery cells. By structurally encoding the cell's identity information and initial state data and writing them into a specific area of ​​a dedicated chip embedded in the cell, the method achieves physical binding between the cell's identity information and data, fundamentally eliminating the risk of "identity loss" for the cell and providing physical protection for traceability across the entire industry chain.

[0033] Please see Figure 1 As shown, Figure 1 This is a flowchart illustrating a method for full lifecycle data binding of a single battery cell according to an embodiment of this application. Figure 1As can be seen, the method for full lifecycle data binding of a single battery cell in this application includes steps S110 to S160. Details are as follows: S110: Obtain the cell identity information carried by the QR code attached to the cell body.

[0034] The purpose of this step is to reliably extract unique identification information for subsequent binding from the QR code on the surface of the battery cell. Specifically, using an image acquisition device, the QR code encrypted at a predetermined location on the battery cell casing is scanned, and the acquired encrypted data is decrypted to extract the plaintext identification information encoded in the QR code. Specifically, the data extracted from the QR code is encrypted data; a decryption operation is performed to obtain the plaintext battery cell identification information. The final obtained plaintext battery cell identification information (e.g., a string sequence conforming to a specific format) is output as input for subsequent steps.

[0035] Optionally, in a more specific embodiment, the above steps can be implemented as follows: the image acquisition device can be an industrial fixed barcode scanner or a handheld terminal, which uses a CCD or CMOS image sensor and is equipped with an auxiliary lighting source. The decoding process may include: converting the image to grayscale and binarization, using the inherent position detection pattern of the QR code for image positioning and geometric distortion correction, and then performing module reading and error correction decoding according to the QR code's encoding format (such as QR code or Data Matrix code). The decryption operation can be completed using a symmetric encryption algorithm (such as the AES algorithm) combined with a preset decryption key. Before output, the validity of the obtained identity information can also be verified, for example, by checking its format or comparing it with database records.

[0036] S120: The cell identification information and the currently collected initial state data of the cell are structured and encoded to generate an encoded data packet.

[0037] This step aims to organize and convert the cell identification information and initial cell state data according to a predefined format to generate a complete encoded data packet, which can then be stored efficiently and reliably in a dedicated data storage chip.

[0038] Specifically, the cell identification information and the currently collected initial state data of the cell are structured and encoded to generate an encoded data packet. This includes: collecting a data packet to be encoded that includes at least the cell identification information and the initial state data of the cell, wherein the initial state data may include initial performance parameters and production-related information; converting each data item in the cell identification information and initial state data into an encoded record containing a type identifier, data length, and data value according to a preset encoding rule, and combining multiple encoded records to form an encoded data packet. The preset encoding rule defines how to convert data items of different types and meanings into a standardized format containing a type identifier, data length, and data value. The type identifier is used to uniquely distinguish data items with different meanings, for example, at least to distinguish one or more of the following: cell unique identification code, initial capacity, DC internal resistance, production date, production line number, and material batch information.

[0039] Specifically, the values ​​of each data item are converted into binary representations according to their data type (such as numbers, strings, dates). Based on the converted binary representations, at least one encoded record is generated, and all encoded records are combined to form the final encoded data packet. The encoded data packet is self-contained and may contain auxiliary information for parsing and verification (such as packet headers, checksums, etc.).

[0040] In one specific embodiment, the encoding rule adopts a "type-length-value" structure. That is, a record is generated for each data item, which sequentially includes: a type field identifying the data item type, a length field indicating the number of bytes of subsequent data content, and a value field storing the converted binary data. A field mapping table can be predefined to map data items such as "cell unique identification code" and "initial capacity" to specific type identifiers (e.g., using 0x0010 to represent initial capacity). For numerical data (such as capacity), its storage unit and precision can be agreed upon before conversion (e.g., using 0.1Ah as the unit, storing 102.3Ah as the integer 1023). For string data, it can be converted to an ASCII or UTF-8 encoded byte sequence.

[0041] The assembly of the encoded data packet may include: arranging multiple "type-length-value" records in a predetermined order; adding a header containing protocol version and total length information before the record sequence; and adding a checksum calculated based on a specific algorithm (e.g., cyclic redundancy check algorithm) to the end of the data packet.

[0042] S130: Write the encoded data packet into the first storage area of ​​the dedicated data storage chip built into the battery cell body to complete the physical binding of the battery cell identity information and the initial state data.

[0043] In one embodiment, the first storage area is a read-only or write-once area; and / or, the dedicated data storage chip communicates via an I2C or single-bus interface.

[0044] Specifically, the purpose of this step is to reliably store the encoded data packet into a dedicated data storage chip built into the battery cell, and to utilize the physical characteristics of the chip's storage area to achieve an immutable physical binding between the battery cell's identity information and its initial state data. By establishing a data communication connection with the dedicated data storage chip built into the battery cell, a first storage area for storing fixed information is selected within the chip's storage space. Through this communication connection, the encoded data packet generated in step S120 is written into the first storage area. After successful writing, it is confirmed that the battery cell's identity information and initial state data have been stored within the battery cell, completing the physical binding. The first storage area is configured such that its stored content cannot be changed or erased after the data is written (i.e., it has read-only or one-time programming characteristics).

[0045] In one specific embodiment, the dedicated data storage chip communicates with an external writing device through a serial communication interface (e.g., an I2C bus or a single bus). The chip is addressed through the communication interface, and device identification and status checks are performed. When writing data, the encoded data packet can be split into multiple data blocks for sequential writing according to the chip's programming characteristics, and the completion of each writing operation is confirmed.

[0046] To ensure data integrity, a read verification operation can be performed after the write operation is complete, comparing the written data with the original encoded data packet. To further ensure the immutability of the data, the first storage area can be set to a permanent read-only state via software commands after the data writing is complete.

[0047] As can be seen from the above analysis, the full lifecycle data binding method for individual battery cells provided in this application includes: obtaining the battery cell identity information carried by the QR code attached to the battery cell body; performing structured encoding on the battery cell identity information and the currently collected initial state data of the battery cell to generate an encoded data packet; and writing the encoded data packet into the first storage area of ​​a dedicated data storage chip built into the battery cell body to complete the physical binding of the battery cell identity information and the initial state data. By writing the battery cell identity information and initial state data into a dedicated chip built into the battery cell body, they become inseparable physical attributes of the battery cell, fundamentally eliminating the risk of "identity loss" of the battery cell and providing physical protection for traceability throughout the entire industry chain.

[0048] Please see Figure 2 , Figure 2 This is a schematic diagram illustrating the implementation process of a full lifecycle data binding method for a single battery cell, provided in another embodiment of this application.

[0049] Depend on Figure 2 It can be seen that this embodiment is similar to... Figure 1 Compared to the illustrated embodiment, S210 to S230 are implemented in the same way as S110 to S130, except that S240 to S260 are included after S230. Details are as follows: S210: Obtain the cell identity information carried by the QR code attached to the cell body.

[0050] S220: The cell identification information and the currently collected initial state data of the cell are structured and encoded to generate an encoded data packet.

[0051] S230: Write the encoded data packet into the first storage area of ​​the dedicated data storage chip built into the battery cell body to complete the physical binding of the battery cell identity information and the initial state data.

[0052] S240: Generates process status data of the battery cell during its use or testing cycle.

[0053] This step is used to capture and generate process data reflecting the state changes of the battery cell during subsequent use, testing, or maintenance. Specifically, during the battery cell's use or testing cycle, a process data recording is initiated based on preset trigger conditions. Data recording can be triggered based on time periods, changes in battery cell state, specific operating conditions, or abnormal events to collect process state data related to the current state of the battery cell. The battery cell's process state data includes at least the time information of the event and state parameters related to the event.

[0054] S250: Structure and encode the process status data to generate process data records.

[0055] The process status data is encapsulated according to a predefined record format to generate a process data record. The record format of the process data record encapsulates the event's time information, type information, and specific status parameter data.

[0056] S260: Write process data records into the second storage area of ​​the dedicated data storage chip.

[0057] A second storage area within the dedicated data storage chip is selected for storing dynamic process data. Specifically, the second storage area employs a circular write strategy, where the oldest written data record is overwritten when the storage space is full. The process data records are written to the second storage area, and the circular write strategy is used for storage space management. This strategy ensures that when the storage space is exhausted, new data records will overwrite older data records, thereby continuously preserving the latest process data within a limited space.

[0058] In one specific embodiment, steps S240 to S260 described above can be implemented collaboratively in the following manner: When a predetermined time interval is reached, a specific number of charge-discharge cycles are completed, the estimated health status of the battery cell exceeds a threshold, or a system-defined abnormal event occurs, the collection of process status data for the battery cell is triggered. The collected process status data may specifically include: a timestamp, an event type identifier, real-time acquired voltage, current, and temperature values, and derived parameters such as health status, capacity, and internal resistance calculated based on these values. The process status data can be structured and encoded using a record format that includes a fixed header and a data body. The fixed header may include a serial number, timestamp, record type, and length information; the data body may contain one or more status parameter items organized according to a "type-length-value" structure.

[0059] The circular write strategy can be implemented by maintaining a write pointer. This pointer is updated after each write; when the pointer reaches the end of the storage area, it is reset back to the starting address, thereby achieving circular reuse of the storage space.

[0060] As can be seen from the above analysis, the embodiments of this application further record the key processes and state changes of the battery cell throughout its entire life cycle in an automatic and structured manner in its internal chip through continuous operation. Together with the written fixed initial data, they constitute the battery cell's complete and portable "digital life archive".

[0061] The above description is merely a specific embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in the present invention should be included within the scope of protection of the present invention. Therefore, the scope of protection of the present invention should be determined by the scope of the claims.

[0062] As can be seen from the above analysis, the full lifecycle data binding method for individual battery cells provided in this application includes: obtaining the battery cell identity information carried by the QR code attached to the battery cell body; performing structured encoding on the battery cell identity information and the currently collected initial state data of the battery cell to generate an encoded data packet; and writing the encoded data packet into the first storage area of ​​a dedicated data storage chip built into the battery cell body to complete the physical binding of the battery cell identity information and the initial state data. By writing the battery cell identity information and initial state data into a dedicated chip built into the battery cell body, they become inseparable physical attributes of the battery cell, fundamentally eliminating the risk of "identity loss" of the battery cell and providing physical protection for traceability throughout the entire industry chain.

[0063] Please see Figure 3 , Figure 3This is a schematic diagram of a data binding device for the entire lifecycle of a single battery cell, provided according to an embodiment of this application. The data binding device for the entire lifecycle of a single battery cell includes modules or units for performing... Figure 1 or Figure 2 The steps in the corresponding embodiments. Please refer to the details. Figure 1 or Figure 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 A data binding device 300 for the entire lifecycle of a single battery cell includes: The acquisition module 310 is used to acquire the battery cell identity information carried by the QR code attached to the battery cell body; Encoding module 320 is used to perform structured encoding of the cell identity information and the currently collected initial state data of the cell to generate an encoded data packet; The first writing module 330 is used to write the encoded data packet into the first storage area of ​​the dedicated data storage chip built into the battery cell body, thereby completing the physical binding of the battery cell identity information and the initial state data.

[0064] In one embodiment, the device further includes: The first generation module is used to generate process status data of the battery cell during the use or testing cycle of the battery cell. The second generation module is used to perform structured encoding on the process state data to generate process data records; The second writing module is used to write the process data records into the second storage area of ​​the dedicated data storage chip.

[0065] In one embodiment, the second storage area employs a circular write strategy, whereby the earliest written data record is overwritten when the storage space is full.

[0066] In one embodiment, the structured encoding includes: converting each data item in the cell identity information and initial state data into an encoded record containing a type identifier, data length, and data value according to a preset encoding rule, and combining multiple encoded records to form the encoded data packet.

[0067] In one embodiment, the type identifier is used to distinguish at least one or more of the following: unique cell identification code, initial capacity, DC internal resistance, production date, production line number, and material batch information.

[0068] In one embodiment, the first storage area is a read-only or write-once area; and / or, the dedicated data storage chip communicates via an I2C or single-bus interface.

[0069] In one embodiment, the step of obtaining the cell identity information includes: scanning an encrypted QR code and decrypting the obtained encrypted data to obtain plaintext identity information.

[0070] Please see Figure 4 , Figure 4 This is a schematic diagram of a data binding device for the entire lifecycle of a single battery cell, provided as an embodiment of this application. Figure 4 It is understood that the data binding device 400 for the entire lifecycle of a single battery cell 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 data binding method for the entire lifecycle of a single battery cell, 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.

[0071] For example, the computer program 430 may be divided into one or more modules / units, one or more of which are stored in the memory 420 and executed by the 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 the computer program 430 in a data binding device for the entire lifecycle of a single battery cell. For example, the computer program 430 may be divided into an acquisition module, an encoding module, and a first writing module.

[0072] The data binding device 400 for the entire lifecycle of a single battery cell provided in this embodiment may include, but is not limited to, a processor and a memory. Those skilled in the art will understand that... Figure 4 This is merely an example of a data binding device 400 for the entire lifecycle of a single battery cell and does not constitute a limitation on the data binding device 400 for the entire lifecycle of a single battery cell. It may include more or fewer components than shown in the figure, or combine certain components, or different components. For example, the data binding device 400 for the entire lifecycle of a single battery cell may also include input / output devices, network access devices, buses, etc.

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

[0074] The memory 420 can be an internal storage unit of the data binding device 400 for the entire lifecycle of a single battery cell, such as a hard disk or memory of the data binding device 400 for the entire lifecycle of a single battery cell. The memory 420 can also be an external storage device of the data binding device 400 for the entire lifecycle of a single battery cell, such as a plug-in hard disk, Smart Media Card (SMC), Secure Digital (SD) card, or Flash Card equipped on the data binding device 400 for the entire lifecycle of a single battery cell. Furthermore, the data binding device 400 for the entire lifecycle of a single battery cell can include both internal storage units and external storage devices. The memory 420 is used to store computer programs and other programs and data required by the data binding device 400 for the entire lifecycle of a single battery cell. The memory 420 can also be used to temporarily store data that has been output or will be output.

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

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

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

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

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

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

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

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

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

[0084] 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. These 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 full lifecycle data binding for individual battery cells, characterized in that, include: Obtain the battery cell identification information carried by the QR code attached to the battery cell body; The cell identification information and the currently collected initial state data of the cell are structured and encoded to generate an encoded data packet; The encoded data packet is written into the first storage area of ​​the dedicated data storage chip built into the battery cell body, thus completing the physical binding of the battery cell identity information and the initial state data.

2. The method according to claim 1, characterized in that, The method further includes: During the use or testing cycle of the battery cell, process status data of the battery cell is generated; The process status data is structured and encoded to generate process data records; The process data is recorded and written into the second storage area of ​​the dedicated data storage chip.

3. The method according to claim 2, characterized in that, The second storage area adopts a circular write strategy, which overwrites the earliest written data record when the storage space is full.

4. The method according to claim 1, characterized in that, The structured encoding includes: converting each data item in the cell identity information and initial state data into an encoded record containing a type identifier, data length, and data value according to a preset encoding rule, and combining multiple encoded records to form the encoded data packet.

5. The method according to claim 4, characterized in that, The type identifier is used to distinguish at least one or more of the following: unique cell identification code, initial capacity, DC internal resistance, production date, production line number, and material batch information.

6. The method according to claim 1, characterized in that, The first storage area is a read-only or write-once area; and / or, the dedicated data storage chip communicates via an I2C or single-bus interface.

7. The method according to claim 1, characterized in that, The steps for obtaining the cell identity information include: scanning the encrypted QR code and decrypting the obtained encrypted data to obtain the plaintext identity information.

8. A data binding device for the entire lifecycle of a single battery cell, characterized in that, include: The acquisition module is used to acquire the battery cell identification information carried by the QR code attached to the battery cell body; The encoding module is used to perform structured encoding of the cell identity information and the currently collected initial state data of the cell to generate an encoded data packet; The first writing module is used to write the encoded data packet into the first storage area of ​​the dedicated data storage chip built into the battery cell body, thereby completing the physical binding of the battery cell identity information and the initial state data.

9. A data binding device for the entire lifecycle of a single battery cell, 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