Battery pack traceability methods, systems, devices, and media

Abstract

The application discloses a battery pack tracing method, system, device and medium. The method comprises the following steps: establishing a digital file among an identity code, a pointer code pointing to real-time data, and factory data; determining an assembly blueprint of the relationship between the battery cell and the installation position based on the assembly requirement and the digital file, wherein the assembly blueprint comprises a matching relationship between the identity code and a virtual position code of the installed slot; screening the battery cell from the battery pack exclusive material based on the assembly blueprint and the physical position code of the installation slot, and verifying; adding the mapping relationship of the battery pack identification, the virtual position code of the installation slot, and the identity code of the battery cell to the digital file for tracing. The application establishes a digital file of the mapping relationship in-depth battery cell layer, and the exact route of the matching between each battery cell and the installation slot is determined based on the assembly requirement at the initial stage of assembly. The whole life process is accurately positioned, the information fault is avoided, and the technical problem that the tracing effect of the battery pack is poor in the prior art is solved.

Description

Technical Field

[0001] This application relates to the field of battery health management, and in particular to battery pack traceability methods, systems, devices and media. Background Technology

[0002] Power battery packs are core components of new energy vehicles, and their safety, reliability, and traceability are of paramount importance. With the rapid development of the new energy vehicle industry, establishing a comprehensive power battery traceability system is particularly crucial, as battery safety incidents have serious consequences. Traceability allows for the rapid identification of problematic batches, precise recalls, and analysis of the root causes of failure. It also helps assess battery health, conduct residual value evaluations, and promote secondary use. In particular, key strategic resources and hazardous substances such as cobalt, lithium, and nickel can be effectively recycled and utilized at the end of their lifespan through traceability, preventing environmental pollution.

[0003] Since a battery pack typically consists of dozens to hundreds of cells connected in series and parallel, current traceability systems face severe challenges, including coarse traceability granularity, static data, error-prone assembly, and disconnected maintenance information. Existing traceability systems are mostly limited to the battery pack or module level. Once a cell experiences a thermal runaway or other failure, it's difficult to quickly and accurately trace back to the cell's original production batch, pairing information, and precise physical location within the pack. This leads to delayed fault analysis, excessively broad recall scope, and limitations of static traceability. Traditional QR codes provide fixed static information and cannot carry dynamic data on cell performance degradation, health status, and historical cycles during subsequent lifecycles such as reuse and maintenance, hindering accurate assessment and safe management of battery assets. Furthermore, there is a gap in maintenance traceability; information on new components after module replacement cannot be reliably and seamlessly integrated into the original battery pack's data chain, creating information gaps. Therefore, there is an urgent need for an intelligent traceability process that enables precise cell-level management, covers the entire battery pack process from "birth" to "retirement," and prevents incorrect assembly. Therefore, existing technologies suffer from poor traceability of battery packs. Summary of the Invention

[0004] This application provides a battery pack traceability method, system, device, and medium, which can solve the technical problem of poor traceability effect of battery packs.

[0005] In a first aspect, embodiments of this application provide a battery pack traceability method, the battery pack traceability method comprising:

[0006] In response to a battery pack assembly instruction, the system acquires the static identification code, dynamic pointer code, factory data, and battery pack assembly order data of the target cell, wherein the dynamic pointer code points to the real-time status data of the cell.

[0007] A digital file is established for the target battery cell to establish a first mapping relationship between the static identification code, the dynamic pointer code, and the factory data;

[0008] The battery pack assembly order data is parsed to obtain the assembly requirements for assembling the battery pack. Based on the assembly requirements and the digital file, an electronic assembly blueprint with pre-matched relationships between battery cells and their installation positions is determined. The electronic assembly blueprint includes a static identification code for each battery cell reserved in each installation slot, a virtual position code for each battery cell in the battery pack's reserved installation slot, and a matching relationship between the static identification code and the virtual position code of the installation slot. Each virtual position code of the installation slot corresponds to the physical position code of the installation slot in the physical world.

[0009] In response to the verification command for the pre-assembled battery pack dedicated kit, the target battery cell is selected from the pre-assembled battery pack dedicated kit based on the electronic assembly blueprint and the obtained physical location code of the installation slot.

[0010] The target battery cell is verified, and the battery pack is assembled after the verification is confirmed to be successful.

[0011] Upon successful verification, a second mapping relationship is established between the battery pack identifier, the virtual location code of the installation slot, and the static identification code of the battery cell. This second mapping relationship is then added to the digital file to facilitate the traceability of the battery cells in the battery pack.

[0012] In some embodiments, after establishing a second mapping relationship between the battery pack identifier, the virtual location code of the mounting slot, and the static identification code of the battery cell when verification is passed, and adding the second mapping relationship to the digital file for traceability of the battery cells in the battery pack, the process includes:

[0013] A battery pack that has been successfully assembled and removed from the assembly line is identified as a finished battery pack, wherein the finished battery pack is managed by a corresponding battery management system.

[0014] The dynamic pointer code corresponding to the cell in the finished battery pack is integrated into the external communication interface of the battery management system where the finished battery pack is located;

[0015] Through the external communication interface, monitoring and collection data for monitoring the finished battery pack are obtained from the battery management system where the finished battery pack is located.

[0016] The digital files corresponding to the cells in the finished battery pack are updated based on the monitored and collected data, wherein the update of the digital files corresponding to the cells in the finished battery pack is triggered based on the obtained digital signature.

[0017] If a read instruction is received for the dynamic pointer code corresponding to the cell in the finished battery pack, the corresponding information is searched in the updated digital file based on the dynamic pointer code corresponding to the cell in the finished battery pack and then output.

[0018] In some embodiments, if a read instruction for the dynamic pointer code corresponding to the cell in the finished battery pack is received, searching for and outputting the corresponding information in the updated digital file based on the dynamic pointer code corresponding to the cell in the finished battery pack includes:

[0019] If a read instruction is received for the dynamic pointer code corresponding to the cell in the finished battery pack, the battery pack's usage data, health status data, charge / discharge record data, and abnormal event data are retrieved from the updated digital archive on the cloud server based on the dynamic pointer code corresponding to the cell in the finished battery pack. The battery management system reports the health status data to the cloud server, and the vehicle networking device where the battery management system is located reports the battery pack's usage data, charge / discharge record data, and abnormal event data to the cloud server.

[0020] If, based on the usage data, health status data, charge / discharge record data, and abnormal event data, it is determined that the battery pack is faulty, then the battery pack is determined to be a replacement battery pack, and a replacement instruction for the replacement battery pack is generated to replace it based on the replacement instruction.

[0021] In some embodiments, after establishing a second mapping relationship between the battery pack identifier, the virtual location code of the mounting slot, and the static identification code of the battery cell when verification is passed, and adding the second mapping relationship to the digital file for traceability of the battery cells in the battery pack, the process includes:

[0022] In response to a replacement command for a battery pack to be replaced, pointer scan data for scanning the dynamic pointer code corresponding to the battery pack to be replaced and slot scan data for scanning the virtual position code corresponding to the mounting slot of the battery pack to be replaced are acquired.

[0023] The fault status of the battery pack to be replaced is verified based on the pointer scan data.

[0024] When the fault verification result indicates that a fault exists, the identity of the battery pack to be replaced is performed based on the slot scanning data.

[0025] When the identity verification result is determined to be an identity match, the replacement is authorized, and the new battery pack is verified based on the dynamic pointer code of the new battery pack authorized for replacement and the virtual position code of the corresponding installation slot of the battery pack to be replaced.

[0026] When the replacement is confirmed to be complete, a new event is added to the digital file. The new event cannot be modified. The new event includes the replacement time of the battery pack, the installation slot of the replacement cell in the battery pack, the static identification code of the battery pack to be replaced, and the static identification code of the new battery pack.

[0027] In some embodiments, the verification of the target battery cell includes:

[0028] The target battery cell is authenticated based on the static identity code and its own real static identity code.

[0029] Based on the static identification code, the dynamic pointer code mapped from the digital file is searched to obtain the real-time status data of the target battery cell;

[0030] Based on the real-time status data and the electronic assembly blueprint, the performance of the target battery cell is verified.

[0031] Based on the identity verification result and the performance verification result, the overall verification result for the target battery cell is determined.

[0032] In some embodiments, after verifying the target cell, the process includes:

[0033] If the verification fails, the current battery pack assembly process is locked.

[0034] An alert will be issued for authentication failures and / or performance failures.

[0035] Upon receiving a secondary verification instruction for the pre-assembled battery pack dedicated kit, in response to the secondary verification instruction, the target battery cell is re-selected from the pre-assembled battery pack dedicated kit based on the electronic assembly blueprint and the obtained physical location code of the installation slot.

[0036] The target cell is re-verified. If the verification fails, the process returns to control and locks the current battery pack assembly process until the verification passes.

[0037] In some embodiments, the step of selecting the target battery cell from the pre-assembled battery pack-specific kit in response to a verification command for the pre-assembled battery pack-specific kit, based on the electronic assembly blueprint and the obtained physical location code of the mounting slot, includes:

[0038] In response to the verification command for the pre-assembled battery pack-specific kit, the virtual location code of the corresponding installation slot is found from the electronic assembly blueprint based on the obtained physical location code of the installation slot.

[0039] Based on the virtual location code of the installation slot, the static identification code of the matching battery cell indicated by the electronic assembly blueprint is found to obtain the first static identification code;

[0040] Based on the first static identification code, the target battery cell is selected from the pre-assembled battery pack's exclusive kit.

[0041] Secondly, embodiments of this application also provide a battery pack traceability system, the battery pack traceability system comprising:

[0042] The acquisition module is used to acquire the static identification code, dynamic pointer code, factory data, and battery pack assembly order data of the target cell in response to the battery pack assembly instruction, wherein the dynamic pointer code points to the real-time status data of the cell;

[0043] The digital file creation module is used to create a digital file for the target battery cell, which is a first mapping relationship between the static identification code, the dynamic pointer code and the factory data.

[0044] The blueprint creation module is used to parse the battery pack assembly order data to obtain the assembly requirements for assembling the battery pack, and based on the assembly requirements and the digital file, to determine an electronic assembly blueprint that pre-matches the relationship between the battery cells and their installation positions. The electronic assembly blueprint includes a static identification code for each battery cell reserved in each installation slot, a virtual position code for each battery cell in the battery pack's reserved installation slot, and a matching relationship between the static identification code and the virtual position code of the installation slot. Each virtual position code of the installation slot corresponds to the physical position code of the installation slot in the physical world.

[0045] The screening module is used to screen the target battery cell from the pre-assembled battery pack dedicated kit in response to the verification command for the pre-assembled battery pack dedicated kit, based on the electronic assembly blueprint and the obtained physical location code of the installation slot.

[0046] The verification module is used to verify the target battery cell, wherein the battery pack is assembled after the verification is confirmed to be successful.

[0047] The digital archive update module is used to establish a second mapping relationship between the battery pack identifier, the virtual location code of the installation slot, and the static identification code of the battery cell when the verification is confirmed to be successful. The second mapping relationship is added to the digital archive for the purpose of tracing the battery cells in the battery pack.

[0048] Thirdly, embodiments of this application also provide a battery pack traceability device, which includes a memory and a processor. The memory stores a computer program, and the processor executes the computer program to implement the above-described method.

[0049] Fourthly, embodiments of this application also provide a computer-readable medium storing a computer program, the computer program including program instructions that, when executed by a processor, can implement the above-described method.

[0050] This application provides a battery pack traceability method, system, device, and medium. In response to a battery pack assembly instruction, the system acquires the static identification code, dynamic pointer code, factory data, and battery pack assembly order data of the target cell, wherein the dynamic pointer code points to the real-time status data of the cell. A digital file is established for the target cell, showing a first mapping relationship between the static identification code, the dynamic pointer code, and the factory data. The battery pack assembly order data is parsed to obtain the assembly requirements for assembling the battery pack. Based on the assembly requirements and the digital file, an electronic assembly blueprint is determined, pre-matching the relationship between the cells and their installation positions. The electronic assembly blueprint includes the static identification code of the cell reserved in each installation slot and the virtual position of each cell in the reserved installation slot within the battery pack. The system establishes a matching relationship between the static identification code and the virtual location code of the installation slot, where each virtual location code of the installation slot corresponds to the physical location code of the installation slot in the physical world. In response to a verification command for the pre-assembled battery pack-specific kit, the system selects the target cell from the pre-assembled battery pack-specific kit based on the electronic assembly blueprint and the obtained physical location code of the installation slot. The target cell is verified, and the battery pack is assembled after verification. Upon successful verification, a second mapping relationship is established between the battery pack identifier, the virtual location code of the installation slot, and the static identification code of the cell, and this second mapping relationship is added to the digital archive for traceability of the cells in the battery pack. This application delves into the cell level within the battery pack, integrating static identification codes, dynamic pointer codes, and factory data to establish a digital archive with mapping relationships. From the initial stage of battery assembly, the precise matching route between each cell and its installation slot is clearly defined based on the requirements of assembling the battery pack. This allows for finer-grained traceability of cells throughout the entire battery pack lifecycle. Traceability leads directly to the battery cell, enabling precise location and zero mismatches during assembly. This avoids information gaps and achieves a truly granular and complete traceability chain that penetrates deep into the battery pack. Therefore, it solves the technical problem of poor traceability of battery packs in existing technologies. Attached Figure Description

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

[0052] Figure 1 A schematic flowchart illustrating the battery pack traceability method provided in this application embodiment;

[0053] Figure 2 A schematic block diagram of a battery pack traceability system provided in an embodiment of this application;

[0054] Figure 3 A schematic block diagram of the device provided in the embodiments of this application. Detailed Implementation

[0055] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this application. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0056] It should be noted that any AI models, software tools, or components not belonging to this company appearing in the embodiments of this application are merely illustrative examples and do not represent actual use. The user personal information involved in the embodiments of this application is obtained by an entity authorized (with the knowledge and consent) or fully authorized by all parties through various legal and compliant means. The collection, storage, use, processing, transmission, provision, and disclosure of the information, data, and signals involved all comply with relevant laws and regulations and do not violate public order and good morals.

[0057] It should be understood that, when used in this specification and the appended claims, the terms "comprising" and "including" indicate the presence of the described features, integrals, steps, operations, elements and / or components, but do not exclude the presence or addition of one or more other features, integrals, steps, operations, elements, components and / or collections thereof.

[0058] It should also be understood that the terminology used in this application specification is for the purpose of describing particular embodiments only and is not intended to limit the application. As used in this application specification and the appended claims, the singular forms “a,” “an,” and “the” are intended to include the plural forms unless the context clearly indicates otherwise.

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

[0060] Power battery packs are core components of new energy vehicles, and their safety, reliability, and traceability are of paramount importance. With the rapid development of the new energy vehicle industry, establishing a comprehensive power battery traceability system is particularly crucial, as battery safety incidents have serious consequences. Traceability allows for the rapid identification of problematic batches, precise recalls, and analysis of the root causes of failure. It also helps assess battery health, conduct residual value evaluations, and promote secondary use. In particular, key strategic resources and hazardous substances such as cobalt, lithium, and nickel can be effectively recycled and utilized at the end of their lifespan through traceability, preventing environmental pollution.

[0061] Since a battery pack typically consists of dozens to hundreds of cells connected in series and parallel, current traceability systems face severe challenges, including coarse traceability granularity, static data, error-prone assembly, and disconnected maintenance information. Existing traceability systems are mostly limited to the battery pack or module level. Once a cell experiences a thermal runaway or other failure, it's difficult to quickly and accurately trace back to the cell's original production batch, pairing information, and precise physical location within the pack. This leads to delayed fault analysis, excessively broad recall scope, and limitations of static traceability. Traditional QR codes provide fixed static information and cannot carry dynamic data on cell performance degradation, health status, and historical cycles during subsequent lifecycles such as reuse and maintenance, hindering accurate assessment and safe management of battery assets. Furthermore, there is a gap in maintenance traceability; information on new components after module replacement cannot be reliably and seamlessly integrated into the original battery pack's data chain, creating information gaps. Therefore, there is an urgent need for an intelligent traceability process that enables precise cell-level management, covers the entire battery pack process from "birth" to "retirement," and prevents incorrect assembly. Therefore, existing technologies suffer from poor traceability of battery packs.

[0062] This application's battery pack traceability method delves deep into the cell level within the battery pack, establishing static identification codes and dynamic pointer codes at the cell level. In addition to these static identification codes and dynamic pointer codes, it also integrates factory data, creating a digital archive mapping the relationships between these three types of data. From the initial battery assembly stage, the precise matching route between each cell and its mounting slot is clearly defined based on the battery pack assembly requirements. This precisely matched route between the cell and its mounting slot constitutes an electronic assembly blueprint. Therefore, traceability can be achieved at a finer granular level throughout the entire lifecycle of the battery pack, from its inception to its retirement. This goes beyond the coarse-grained level of the battery pack itself, encompassing all processes from initial battery assembly to repair or replacement, avoiding information gaps and achieving a truly comprehensive, fine-grained traceability chain that penetrates deep into the battery pack's interior.

[0063] The battery pack traceability method described in this application is applied to a battery pack traceability system. In some embodiments, the battery pack traceability system can be a Manufacturing Execution System (MES). The core function of traceability in power battery production is related to this system. The MES is the source system for traceability data in the battery production process, generating and recording all key data of the battery during its initial stages. As an example, the MES reports necessary traceability data, such as product codes, production dates, key material batches, and initial performance data, to the battery traceability management platform according to standards; or, after the battery pack leaves the factory, its unique identifier, such as a QR code, is bound to the vehicle manufacturer's system with the vehicle's VIN code. Vehicle operation data is uploaded to the vehicle networking platform via a T-BOX (a key physical hardware device on the vehicle connecting the vehicle to a cloud server). When the battery is retired, the recycling company scans the code to retrieve its production file and usage history on the traceability platform. The MES is responsible for managing the digital twin files of the battery cells, generating and executing assembly blueprints, processing real-time verification logic, and maintaining the entire chain of relationships.

[0064] Figure 1 This is a flowchart illustrating the battery pack traceability method provided in an embodiment of this application. Figure 1 As shown, the method includes the following steps S110-S160:

[0065] S110. In response to the battery pack assembly instruction, obtain the static identification code, dynamic pointer code, factory data and battery pack assembly order data of the target cell, wherein the dynamic pointer code points to the real-time status data of the cell;

[0066] A battery pack is a complete energy system and structural assembly. It comprises a core unit and a supporting system. The core unit consists of dozens to thousands of cells connected in series or parallel to form the electrical system; the supporting system includes the casing, thermal management system, and electrical system.

[0067] A target cell is a specific, identifiable individual component that forms the core of a large battery pack system. The target cell is precisely installed in a specific mounting slot within a particular module, becoming part of the circuitry through soldering or connectors.

[0068] A digital link is built through MES, BMS, and the cloud. On the assembly line, the MES system forcibly binds the unique identification code of the target cell to the unique identification code of the battery pack and the specific installation slot number. Simultaneously, the cell's production data, such as materials, processes, and test records, are also linked to the overall data file of the battery pack. During vehicle operation, the BMS continuously monitors the voltage and temperature of each slot. The BMS's sampling channels correspond one-to-one with the physical slots. Therefore, any abnormal data reported by the BMS, such as "Cell No. 7 in Module 3 has low voltage," can be immediately mapped to the target cell's identification code through the previously bound relationship. This identified operational data is uploaded to the cloud via a T-Box, collected into the cell's independent digital file, and also aggregated into the overall operational file of the battery pack. The target cell's dynamic data throughout its entire lifecycle is continuously recorded and updated, always clearly indicating which battery pack and vehicle it belongs to.

[0069] The Battery Management System (BMS) enables the battery pack to manage target cells, monitoring their health status in real time, such as voltage, temperature, and internal resistance. When a target cell differs from other cells in the pack, the BMS initiates active or passive balancing to replenish or deplete its power, maintaining overall pack consistency. Based on the target cell's temperature, the BMS controls the entire battery pack's cooling or heating system to provide a suitable operating environment. In extreme fault conditions, such as thermal runaway of a target cell, the BMS can instruct the high voltage to be disconnected and initiate emergency cooling, attempting to isolate and control the fault locally, protecting the entire battery pack and the vehicle.

[0070] The static identification code of the target battery cell is a location identifier for the cell, usually engraved or attached to the physical entity in the form of a QR code, laser code, or RFID. A pre-set laser marking and identification unit is used to mark the static identification code of the battery cell and the location code of the battery pack.

[0071] The target cell's dynamic pointer code is an intelligent service interface derived from a static identification code, pointing to a real-time dynamic data aggregation view. The target cell's factory data refers to the set of static data characterizing its initial performance and state when the cell leaves the manufacturing plant. This includes identification information such as the associated static identification code, production batch, model, and production date; performance parameters such as initial capacity, nominal voltage, internal resistance, and open-circuit voltage; and key process parameters such as coating weight, electrolyte injection volume, charge-discharge curves, factory test reports, and batch information of the main raw materials used. An associated, updatable dynamic pointer code is generated for each cell, initially printed on the cell's insulating packaging or accompanying documentation. This is used to establish a digital profile of the target cell in the MES system.

[0072] As an example, scanning the physical static identification code of a battery cell yields its unique ID. The device sends a request to a cloud-based pointer code parsing service, containing the cell's static identification code and request context, such as the scanner's identity (e.g., production quality inspector, maintenance engineer, or recycler). Based on the cell's static identification code and the visitor's permissions, the parsing service dynamically retrieves information from multiple data sources in real time, assembling it into a complete data view. This assembled, dynamic data view, suitable for the current scenario, is then returned to the terminal for display. Dynamic data refers to the real-time data pointed to by the dynamic pointer code, stored in various specialized systems. The data for the battery cell pointed to by the dynamic pointer code is updated and continuously enriched in real time. After scanning, a dynamic data view based on the current time, visitor identity, and the battery cell's real-time status is obtained.

[0073] Battery pack assembly order data includes an assembly list for the battery packs. During the assembly process of assembling battery packs, there is relational data outlining how to integrate and bind numerous cells and other components into a single system.

[0074] In response to a battery pack assembly instruction, the system acquires the target cell's static identification code, dynamic pointer code, factory data, and battery pack assembly order data, wherein the dynamic pointer code points to the cell's real-time status data.

[0075] S120. Establish a digital file for the target battery cell, showing a first mapping relationship between the static identification code, the dynamic pointer code, and the factory data.

[0076] In the MES system, a digital file for the battery cell is established, initially binding a static identification code, a dynamic pointer code, and factory data (capacity, internal resistance, voltage, production batch, formation data, etc.). The static identification code, the dynamic pointer code, and the factory data are mutually mapped, and this mapping relationship is called the first mapping relationship.

[0077] The digital profile of the target battery cell originates from the target battery cell's static factory data (factory data), the associated data in the assembly order (data associated with static identification codes), and the dynamic data throughout the battery cell's lifecycle in the vehicle networking platform (data pointed to by dynamic pointer codes). In some embodiments, it also includes state transition data from the operation and maintenance recycling platform. Based on these data, the relationships between them are established, and the mapping relationships between each pair of data are determined to obtain the overall mapping relationship diagram between these three sets of data.

[0078] Digital archives for battery cells completely break through the black box limitation of cell status during use, enabling visible and assessable status. Maintenance is no longer based on experience, but rather on predictive data, resulting in more precise maintenance, accurate recycling, and objective assessment of residual value based on the archive data.

[0079] S130. The battery pack assembly order data is parsed to obtain the assembly requirements for assembling the battery pack. Based on the assembly requirements and the digital file, an electronic assembly blueprint with pre-matched relationships between the battery cells and their installation positions is determined. The electronic assembly blueprint includes a static identification code for each battery cell reserved in each installation slot, a virtual position code for each battery cell in the battery pack's reserved installation slot, and a matching relationship between the static identification code and the virtual position code of the installation slot. The virtual position code of each installation slot corresponds to the physical position code of the installation slot in the physical world.

[0080] Battery pack assembly order data can be obtained in the form of a file. Parsing the order file reveals the specific assembly requirements for assembling the battery pack. These requirements include the total number of battery cells required in the battery pack and the performance requirements of each cell.

[0081] Electronic assembly blueprints refer to the planning of how battery cells will be assembled, down to a specific installation location. In other words, electronic assembly blueprints provide fine-grained planning at the cell level, improving the efficiency of future cell traceability and providing a basis for traceability.

[0082] After a battery pack production order is placed, the MES system generates an electronic assembly blueprint for the specific battery pack based on design requirements and measured performance data pointed to by dynamic pointer codes in the digital archive. This blueprint precisely specifies the pre-installed position of each cell within the battery pack, the performance index range of cells at each position (for error prevention and verification), and the total number of cells required, as well as performance grouping, such as clustering based on capacity and internal resistance. Cell performance grouping is a crucial process in power battery manufacturing, directly determining the performance, safety, lifespan, and cost of the battery pack. It involves screening and classifying cells based on their key performance parameters after production to group cells with consistent performance together. Without cell performance grouping, cells with high internal resistance may generate more heat during operation, while cells with low internal resistance may charge and discharge more deeply, leading to a continuous increase in inconsistencies during cycling. As an example, grouping is not based on a single parameter but on a comprehensive clustering based on multiple parameters. For instance, capacity grouping, based on the core static parameter of capacity, typically involves constant current charging and discharging to measure the actual release of electricity. When grouping cells, those with very similar capacities are grouped together. Another example is capacity grouping based on the core static parameter of DC internal resistance, a key indicator reflecting the cell's output power capability and heat generation. Measured at 50% SOC, cells with similar internal resistance values ​​are grouped together.

[0083] The electronic assembly blueprint includes: a static identification code reserved for each battery cell in each mounting slot, a virtual location code for each battery cell in the mounting slot reserved in the battery pack, and a matching relationship between the static identification code and the virtual location code of the mounting slot. The virtual location code of each mounting slot corresponds to the physical location code of the mounting slot in the physical world.

[0084] S140. In response to the verification command for the pre-assembled battery pack dedicated kit, the target battery cell is selected from the pre-assembled battery pack dedicated kit based on the electronic assembly blueprint and the obtained physical location code of the installation slot.

[0085] In response to the verification instruction for the pre-assembled battery pack's dedicated kit, the warehouse staff, according to the blueprint instructions, selects the battery cells with the specified static identification codes from the warehouse to assemble the dedicated battery pack kit.

[0086] A battery pack-specific kit is a complete package of materials, individually selected from the warehouse and bound to a specific production work order number. This kit contains all the components needed to assemble a battery pack, ensuring the correct type, model, quantity, and batch. The battery pack-specific kit is a core material management model in the power battery assembly process, enabling high-efficiency, zero-error, and fully traceable production management. It refers to the pre-planning, precise, and complete preparation, distribution, and management of all materials required for producing a specific model or batch of battery packs, according to production orders and process requirements.

[0087] In S140, in response to the verification command for the pre-assembled battery pack-specific kit, the step of selecting the target battery cell from the pre-assembled battery pack-specific kit based on the electronic assembly blueprint and the obtained physical location code of the mounting slot includes steps S1401 to S1403:

[0088] S1401. In response to the verification command for the pre-assembled battery pack dedicated kit, based on the obtained physical location code of the mounting slot, find the virtual location code of the corresponding mounting slot from the electronic assembly blueprint.

[0089] An installation slot refers to a unique physical location and logical numbering space within a battery pack, reserved and defined for each cell or module. The physical location code of an installation slot is a specific physical space with dimensional and interface requirements, typically formed by module structural components or the battery pack's frame structure, used to fix and accommodate cells or standard modules. The virtual location code of an installation slot is a unique number, a coordinate within the battery pack. It explicitly tells production personnel and the system where a particular cell / module should be placed. This location is strongly associated with the unique identification code (such as a QR code) of the cell / module installed there and its corresponding real-time operating data.

[0090] At each installation station on the module assembly line or battery pack assembly line, the operator first scans the physical location code of the current installation slot. Since each installation slot's virtual location code uniquely corresponds to a physical location code in the physical world, the corresponding virtual location code of the installation slot can be found based on the electronic assembly blueprint by scanning the physical location code of the current installation slot.

[0091] S1402. Based on the virtual location code of the installation slot, find the static identification code of the matching cell indicated by the electronic assembly blueprint to obtain the first static identification code;

[0092] Locate the matching battery cell to be installed in the mounting slot from the electronic assembly blueprint. Find the static identification code of the matching battery cell based on the virtual location code of the mounting slot. Use the static identification code corresponding to the virtual location code as the first static identification code.

[0093] S1403. Based on the first static identification code, select the target battery cell from the pre-assembled battery pack exclusive kit.

[0094] The static identification code uniquely identifies the identity of the battery cell. Therefore, the target battery cell is selected from the pre-assembled battery pack's exclusive kit based on the first static identification code.

[0095] S150. Verify the target battery cell, wherein the battery pack is assembled after the verification is confirmed to be successful.

[0096] The step of verifying the target battery cell in S150 includes steps S1501-S1504:

[0097] S1501. Based on the static identity code and the target battery cell's own real static identity code, verify the identity of the target battery cell;

[0098] The robotic arm grasps the battery cell and scans its static identification code to obtain the target battery cell's own true static identification code. Based on the static identification code and the target battery cell's own true static identification code, the target battery cell is authenticated to verify whether the battery cell's true static identification code is consistent with the expectation indicated in the blueprint.

[0099] S1502. Based on the static identification code, search for the mapped dynamic pointer code in the digital file to obtain the real-time status data of the target battery cell;

[0100] S1503. Based on the real-time status data and the electronic assembly blueprint, the performance of the target battery cell is verified.

[0101] Based on the static identification code, the dynamic pointer code mapped from the digital archive is retrieved to obtain the real-time status data of the target battery cell. Based on the real-time status data and the electronic assembly blueprint, the performance of the target battery cell is verified. The latest performance data of the battery cell is obtained from the digital twin archive, and the latest performance data of the battery cell is verified to ensure it meets the performance requirements of the blueprint for that slot.

[0102] S1504. Based on the authentication result and the performance verification result, determine the total verification result for the target battery cell.

[0103] If both the identity verification result and the performance verification result pass, the overall verification result of the target battery cell is determined to be passed. If either the identity verification result or the performance verification result fails, or if neither of them fails, the overall verification result of the target battery cell is determined to be failed.

[0104] Among these measures, verifying the identity of battery cells can prevent incorrect selection and pairing caused by accidental grasping by robotic arms, thus reducing the probability of battery pack failure. Verifying the performance of battery cells can prevent cells with inconsistent performance from being grouped together, improving the overall quality of the assembled battery pack.

[0105] Following step S150, which verifies the target cell, steps A1 through A4 are included:

[0106] A1. If the verification fails, lock the current battery pack assembly process.

[0107] When verification fails, the assembly process of the current battery pack is locked. Locking the assembly process in the MES system prevents any unqualified, mismatched, or unclear cells from entering the battery pack system at the source, ensuring the absolute safety, traceability, and consistency of the final product. The locking procedure for the current battery pack assembly process is an automated quality control logic driven by data and rules. If a cell barcode is unidentifiable or its key information, such as its performance group, material batch, or test results, does not match the requirements of the current production order, the system will determine it as an illegal component. Locking the process at this time forces manual verification to ensure one item, one code, and accurate information. This prevents workers from accidentally mixing cells of different grades, thus avoiding problems such as uneven charging and discharging and accelerated degradation due to inconsistent internal resistance and capacity. It also avoids the error of installing before scanning. If installation is allowed before scanning, disassembly and replacement would result in wasted time, equipment damage, and high rework costs if scanning fails. Locking the process eliminates this possibility by design. It can also prevent greater losses. If a battery cell with serious internal defects is welded or tightened on the assembly line, it may cause a short circuit, fire or explosion due to stress or high temperature, endangering the production line and personnel safety.

[0108] A2. Issue alerts for failed authentication results and / or failed performance verification results;

[0109] If the verification fails, it could be due to a failure in identity verification, performance verification, or both. If verification fails, the system will issue an alert and lock the process.

[0110] If authentication fails, an alarm will be triggered to report the failure, prompting professionals to check and remove any mismatched cells based on the alarm signal. Similarly, if performance verification fails, an alarm will be triggered to report the failure, prompting technical personnel to perform performance reconfiguration based on the alarm signal.

[0111] A3. Upon receiving a secondary verification instruction for the pre-assembled battery pack dedicated kit, in response to the secondary verification instruction, based on the electronic assembly blueprint and the obtained physical location code of the installation slot, the target battery cell is re-selected from the pre-assembled battery pack dedicated kit.

[0112] Since the verification failed, this application has a re-verification mechanism, which can receive adjustment feedback from users, such as professional technicians, to continue secondary verification. When professional technicians detect the alarm signal of verification failure, they will perform targeted adjustment actions. For example, if a professional technician replaces a cell with an incompatible identity, a secondary verification instruction for the battery pack's dedicated kit is triggered. Upon receiving a second verification instruction for the pre-assembled battery pack's dedicated kit, the target cell is re-selected from the pre-assembled battery pack's dedicated kit in response to the instruction. This re-verification mechanism provides more opportunities for error correction during the battery pack assembly process, improves the assembly error tolerance rate, and reduces the probability of failure in the final successfully assembled battery pack. This reflects the true meaning of battery pack traceability. One of the significances of battery pack traceability is the full utilization of resources throughout the entire process of battery packs, from production to use and finally to retirement and reuse, based on a clear traceability path. This reduces the probability of errors in the production stage, improves the utilization rate of battery resources while meeting usage requirements in the usage stage, and allows for continued traceability and tiered utilization of battery packs after retirement, rationally utilizing remaining resources based on the differences in retired battery packs.

[0113] Here, the step of re-selecting the target battery cell from the pre-assembled battery pack dedicated kit based on the secondary verification instruction, the electronic assembly blueprint, and the obtained physical location code of the installation slot is no different from the above step of selecting the target battery cell from the pre-assembled battery pack dedicated kit. The implementation steps are consistent and can be referenced synchronously.

[0114] A4. Re-verify the target cell. If the verification fails, return to control and lock the current battery pack assembly process until the verification passes.

[0115] Similarly, the target cell is re-verified. If the verification fails, the process returns to control and locks the current battery pack assembly process until the verification passes. Multiple verifications ensure the rationality of the assembly, adding an extra layer of protection to the finished battery pack.

[0116] S160. When the verification is confirmed to be successful, a second mapping relationship is established between the battery pack identifier, the virtual location code of the installation slot, and the static identification code of the battery cell. The second mapping relationship is added to the digital file for traceability of the battery cells in the battery pack.

[0117] If the verification passes—meaning both identity verification and performance verification are successful—it indicates that the target battery cell grasped by the robotic arm matches the assembly cell indicated in the blueprint, and that the grasped target battery cell will achieve the expected performance effect after successful assembly, according to the performance requirements indicated in the blueprint. After confirming successful verification, battery pack assembly can begin. Upon completion of assembly, the assembly time is recorded in the battery pack traceability system, and the record is updated in the digital archive. This update and re-recording mechanism further enhances the traceability method.

[0118] In some embodiments, after assembly, the successfully assembled battery pack is obtained, and each battery pack is assigned a unique identifier.

[0119] After step S160 confirms successful verification, establishes a second mapping relationship between the battery pack identifier, the virtual location code of the mounting slot, and the static identification code of the battery cell, and adds the second mapping relationship to the digital file for traceability of the battery cells in the battery pack, the process includes steps B1-B5:

[0120] B1. A battery pack that has been successfully assembled and removed from the assembly line is identified as a finished battery pack, wherein the finished battery pack is managed by a corresponding battery management system.

[0121] Battery pack off-line refers to the removal of a battery pack from the production line after all assembly processes in an electric vehicle or energy storage system have been completed. This marks the end of the physical production phase of the battery pack. After off-line, a successfully assembled battery pack that has been removed from the assembly line is considered a finished battery pack. A dedicated Battery Management System (BMS) manages the finished battery pack. The BMS manages the entire battery pack lifecycle, from deployment and use to final recycling. Key features include: voltage monitoring (real-time monitoring of the voltage of each cell or group of cells to prevent overcharging and over-discharging); temperature monitoring (monitoring the temperature of cells, connection points, and other critical components through temperature sensors throughout the pack to provide a basis for thermal management and trigger alarms or circuit cutoff in case of abnormal temperatures); current monitoring (high-precision measurement of the current flowing into and out of the battery pack to calculate charge and determine short circuits or overcurrent conditions); insulation monitoring (regularly checking the insulation resistance between the battery's high-voltage circuit and the vehicle body / chassis, immediately triggering an alarm upon detection of insulation failure to prevent electric shock); and equalization management (due to manufacturing differences, the voltage and internal resistance of cells cannot be perfectly uniform). The BMS will passively equalize the discharge resistors of high-voltage cells or actively equalize the transfer of energy from high-voltage cells to low-voltage cells, actively leveling the differences between cells, improving the overall usable capacity and extending lifespan; for thermal management control, the BMS controls the cooling or heating system of the battery pack based on temperature data to maintain the battery temperature within the optimal operating window.

[0122] B2. Integrate the dynamic pointer code corresponding to the cell in the finished battery pack into the external communication interface of the battery management system where the finished battery pack is located;

[0123] The protocol for the external communication interface is defined. For example, it is specified that when sending a CAN message with ID 0x2A1, the data in bytes 3-6 represents the voltage value of cell 2 in module 1, which is parsed from the dynamic pointer code A.

[0124] In addition to integrating the dynamic pointer code into the external communication interface of the battery management system (BMS) of the finished battery pack, a unique corresponding data index structure is generated based on the design of this battery pack model. This index structure is then configured in the dedicated BMS for that battery pack, specifying how the BMS organizes and packages the massive amounts of internal data collected.

[0125] Its dynamic data pointer is integrated into the external communication interface of the battery management system. Throughout the battery pack's lifecycle, any critical state change triggers an update to its digital profile, generating a new version of the data record. This includes health reports every hundred cycles, records of each fast charge, abnormal alarms, and maintenance events. Each update is digitally signed to ensure trustworthiness, and the data is uploaded to a blockchain-based notarization platform to solidify the time and prevent tampering.

[0126] Scanning the dynamic data pointer code of the battery pack reveals a complete and reliable data chain containing all historical states and events.

[0127] B3. Through the external communication interface, obtain monitoring data for monitoring the finished battery pack from the battery management system where the finished battery pack is located;

[0128] B4 updates the digital profiles corresponding to the cells in the finished battery pack based on the monitored and collected data, wherein the update of the digital profiles corresponding to the cells in the finished battery pack is triggered based on the obtained digital signature;

[0129] B5. If a read instruction is received for the dynamic pointer code corresponding to the cell in the finished battery pack, the corresponding information is searched in the updated digital file based on the dynamic pointer code corresponding to the cell in the finished battery pack and then output.

[0130] The battery management system monitors data such as voltage, temperature, and current. The battery pack traceability system obtains this monitoring data from the battery management system and updates the data archive based on the monitoring data. The dynamic data pointed to by the pointer in the digital archive is constantly being updated. If real-time data is needed, the corresponding information is retrieved from the updated digital archive based on the read command of the dynamic pointer code.

[0131] If a read instruction for the dynamic pointer code corresponding to the cell in the finished battery pack is received in B5, the steps of searching for and outputting the corresponding information in the updated digital file based on the dynamic pointer code of the cell in the finished battery pack include steps C1-C2:

[0132] C1. If a read instruction is received for the dynamic pointer code corresponding to the cell in the finished battery pack, based on the dynamic pointer code corresponding to the cell in the finished battery pack, the battery pack usage data, health status data, charge / discharge record data, and abnormal event data are retrieved from the updated digital archive on the cloud server. The battery management system reports the health status data to the cloud server, and the vehicle networking device where the battery management system is located reports the battery pack usage data, the charge / discharge record data, and the abnormal event data to the cloud server.

[0133] In some embodiments, relevant information is searched in the updated digital archive, including battery pack usage data, health status data, charge / discharge record data, and abnormal event data.

[0134] The data is directed to the cloud server by the dynamic correction code. The cloud server receives data from the battery management system (BMS) and the connected vehicle devices that house the BMS. Specifically, the BMS uploads monitored battery health data to the cloud server. The connected vehicle devices upload recorded battery pack usage data, charge / discharge records, and abnormal battery pack data to the cloud server.

[0135] C2. If, based on the usage data, health status data, charge / discharge record data, and abnormal event data, it is determined that the battery pack is faulty, then the battery pack is determined to be a battery pack to be replaced, and a replacement instruction for the battery pack to be replaced is generated to replace it based on the replacement instruction.

[0136] Based on the retrieved data, fault diagnosis of the battery pack is performed, enabling dynamic monitoring of the battery pack's condition. This allows for monitoring of the battery pack during its use, achieving true traceability of its operation. If a fault is determined based on this data, the battery pack needs to be replaced.

[0137] After step S160 confirms successful verification, establishes a second mapping relationship between the battery pack identifier, the virtual location code of the mounting slot, and the static identification code of the battery cell, and adds the second mapping relationship to the digital file for traceability of the battery cells in the battery pack, the process includes steps D1-D5:

[0138] D1. In response to the replacement command of the battery pack to be replaced, acquire pointer scan data that scans the dynamic pointer code corresponding to the battery pack to be replaced and acquire slot scan data that scans the virtual position code corresponding to the installation slot of the battery pack to be replaced.

[0139] As an example, when a cell in a battery pack needs to be replaced, the technician scans the battery pack's dynamic code and the slot code where the faulty cell is located. After system verification, the replacement is authorized. The battery pack to be replaced is scanned to obtain real-time data, specifically the dynamic scan data pointed to by the dynamic pointer code, and the installation slot information of the faulty cell is obtained through the virtual location code.

[0140] D2. Verify the fault status of the battery pack to be replaced based on the pointer scan data;

[0141] Verify whether a fault truly exists based on the real-time data obtained from the scan, and perform status verification on the fault.

[0142] D3. When the fault verification result indicates that a fault exists, the identity of the battery pack to be replaced is performed based on the slot scanning data.

[0143] If a fault is indeed found, the identity of the battery pack is verified to be correct by scanning the slot data.

[0144] D4. When the identity verification result is determined to be an identity match, the replacement is authorized, and the new battery pack is verified based on the dynamic pointer code of the new battery pack authorized for replacement and the virtual position code of the corresponding installation slot of the battery pack to be replaced.

[0145] If the verified identity matches, it means the battery pack that needs to be replaced is the current one. The battery pack traceability system authorizes the replacement.

[0146] The new battery cell also has its own static identification code and dynamic pointer code. The dynamic pointer code of the authorized replacement battery pack is used to verify whether the performance of the new battery pack matches the performance requirements of this slot. The virtual position code of the installation slot for the battery pack to be replaced determines the correct installation location for the new battery pack.

[0147] D5. When the replacement is confirmed to be complete, add a new event to the digital file. The new event cannot be modified. The new event includes the replacement time of the battery pack, the installation slot of the replacement cell in the battery pack, the static identification code of the battery pack to be replaced, and the static identification code of the new battery pack.

[0148] After the replacement is completed, the system records an unalterable maintenance event in the battery pack's digital twin file: "At [xx time], in [xx slot], the original cell [Static Identification Code A] was replaced with a new cell [Static Identification Code B]", and links it to the new cell's file. From then on, the new cell's data link is inherited and integrated into the battery pack's main data link.

[0149] In some embodiments, a pre-defined blockchain evidence storage service platform provides trusted timestamps and tamper-proof evidence storage for all critical data updates. Seamless integration of maintenance data and an innovative data chain inheritance mechanism ensure the integrity of the battery pack data chain after maintenance, addressing the industry pain point of after-sales traceability. Combining digital signatures and blockchain evidence storage provides an unforgeable archive for the battery pack, enhancing the ability to provide evidence in product quality disputes.

[0150] This application enables millisecond-level reverse tracing from the battery pack to a specific cell in a particular slot, greatly improving fault analysis efficiency and recall accuracy. Through blueprint guidance and real-time dual verification, it fundamentally prevents human errors such as incorrect cell installation and performance mismatch, thereby enhancing battery pack consistency and safety.

[0151] This application provides a battery pack traceability method, system, device, and medium. In response to a battery pack assembly instruction, the system acquires the static identification code, dynamic pointer code, factory data, and battery pack assembly order data of the target cell, wherein the dynamic pointer code points to the real-time status data of the cell. A digital file is established for the target cell, showing a first mapping relationship between the static identification code, the dynamic pointer code, and the factory data. The battery pack assembly order data is parsed to obtain the assembly requirements for assembling the battery pack. Based on the assembly requirements and the digital file, an electronic assembly blueprint is determined, pre-matching the relationship between the cells and their installation positions. The electronic assembly blueprint includes the static identification code of the cell reserved in each installation slot and the virtual position of each cell in the reserved installation slot within the battery pack. The system establishes a matching relationship between the static identification code and the virtual location code of the installation slot, where each virtual location code of the installation slot corresponds to the physical location code of the installation slot in the physical world. In response to a verification command for the pre-assembled battery pack-specific kit, the system selects the target cell from the pre-assembled battery pack-specific kit based on the electronic assembly blueprint and the obtained physical location code of the installation slot. The target cell is verified, and the battery pack is assembled after verification. Upon successful verification, a second mapping relationship is established between the battery pack identifier, the virtual location code of the installation slot, and the static identification code of the cell, and this second mapping relationship is added to the digital archive for traceability of the cells in the battery pack. This application delves into the cell level within the battery pack, integrating static identification codes, dynamic pointer codes, and factory data to establish a digital archive with mapping relationships. From the initial stage of battery assembly, the precise matching route between each cell and its installation slot is clearly defined based on the requirements of assembling the battery pack. This allows for finer-grained traceability of cells throughout the entire battery pack lifecycle. Traceability leads directly to the battery cell, enabling precise location and zero mismatches during assembly. This avoids information gaps and achieves a truly granular and complete traceability chain that penetrates deep into the battery pack. Therefore, it solves the technical problem of poor traceability of battery packs in existing technologies.

[0152] Figure 2 This is a schematic block diagram of a battery pack traceability system provided in an embodiment of this application. Figure 2 As shown, corresponding to the above battery pack traceability method, this application also provides a battery pack traceability system 600. The battery pack traceability system 600 includes a unit for performing the above-described battery pack traceability, and can be configured in terminals such as desktop computers, tablet computers, and laptops. Specifically, please refer to... Figure 2 The battery pack traceability system 600 includes an acquisition module 601, a digital file creation module 602, a blueprint creation module 603, a screening module 604, a verification module 605, and a digital file update module 606, wherein:

[0153] The acquisition module 601 is used to acquire the static identification code, dynamic pointer code, factory data and battery pack assembly order data of the target cell in response to the battery pack assembly instruction, wherein the dynamic pointer code points to the real-time status data of the cell;

[0154] The digital file creation module 602 is used to create a digital file for the target battery cell, which is a first mapping relationship between the static identification code, the dynamic pointer code and the factory data.

[0155] The blueprint creation module 603 is used to parse the battery pack assembly order data to obtain the assembly requirements for assembling the battery pack, and based on the assembly requirements and the digital file, to determine an electronic assembly blueprint that pre-matches the relationship between the battery cells and their installation positions. The electronic assembly blueprint includes a static identification code for each battery cell reserved in each installation slot, a virtual position code for each battery cell in the battery pack's reserved installation slot, and a matching relationship between the static identification code and the virtual position code of the installation slot. The virtual position code of each installation slot corresponds to the physical position code of the installation slot in the physical world.

[0156] The screening module 604 is used to screen the target battery cell from the pre-assembled battery pack dedicated kit in response to the verification command for the pre-assembled battery pack dedicated kit, based on the electronic assembly blueprint and the obtained physical location code of the installation slot.

[0157] The verification module 605 is used to verify the target battery cell, wherein the battery pack is assembled after the verification is confirmed to be successful.

[0158] The digital archive update module 606 is used to establish a second mapping relationship between the battery pack identifier, the virtual location code of the installation slot, and the static identification code of the battery cell when the verification is confirmed to be successful, and add the second mapping relationship to the digital archive for traceability of the battery cells in the battery pack.

[0159] In some embodiments, after establishing a second mapping relationship between the battery pack identifier, the virtual location code of the mounting slot, and the static identification code of the battery cell when verification is passed, and adding the second mapping relationship to the digital archive for traceability of the battery cells in the battery pack, the digital archive update module 606 is specifically used for:

[0160] A battery pack that has been successfully assembled and removed from the assembly line is identified as a finished battery pack, wherein the finished battery pack is managed by a corresponding battery management system.

[0161] The dynamic pointer code corresponding to the cell in the finished battery pack is integrated into the external communication interface of the battery management system where the finished battery pack is located;

[0162] Through the external communication interface, monitoring data for monitoring the finished battery pack is obtained from the battery management system where the finished battery pack is located.

[0163] The digital files corresponding to the cells in the finished battery pack are updated based on the monitored and collected data, wherein the update of the digital files corresponding to the cells in the finished battery pack is triggered based on the obtained digital signature.

[0164] If a read instruction is received for the dynamic pointer code corresponding to the cell in the finished battery pack, the corresponding information is searched in the updated digital file based on the dynamic pointer code corresponding to the cell in the finished battery pack and then output.

[0165] In some embodiments, if a read instruction for the dynamic pointer code corresponding to the cell in the finished battery pack is received, the digital file update module 606 searches for and outputs the corresponding information in the updated digital file based on the dynamic pointer code corresponding to the cell in the finished battery pack. Specifically, this digital file update module 606 is used for:

[0166] If a read instruction is received for the dynamic pointer code corresponding to the cell in the finished battery pack, the battery pack's usage data, health status data, charge / discharge record data, and abnormal event data are retrieved from the updated digital archive on the cloud server based on the dynamic pointer code corresponding to the cell in the finished battery pack. The battery management system reports the health status data to the cloud server, and the vehicle networking device where the battery management system is located reports the battery pack's usage data, charge / discharge record data, and abnormal event data to the cloud server.

[0167] If, based on the usage data, health status data, charge / discharge record data, and abnormal event data, it is determined that the battery pack is faulty, then the battery pack is determined to be a replacement battery pack, and a replacement instruction for the replacement battery pack is generated to replace it based on the replacement instruction.

[0168] In some embodiments, after establishing a second mapping relationship between the battery pack identifier, the virtual location code of the mounting slot, and the static identification code of the battery cell when verification is passed, and adding the second mapping relationship to the digital archive for traceability of the battery cells in the battery pack, the digital archive update module 606 is specifically used for:

[0169] In response to a replacement command for a battery pack to be replaced, pointer scan data for scanning the dynamic pointer code corresponding to the battery pack to be replaced and slot scan data for scanning the virtual position code corresponding to the mounting slot of the battery pack to be replaced are acquired.

[0170] The fault status of the battery pack to be replaced is verified based on the pointer scan data.

[0171] When the fault verification result indicates that a fault exists, the identity of the battery pack to be replaced is performed based on the slot scanning data.

[0172] When the identity verification result is determined to be an identity match, the replacement is authorized, and the new battery pack is verified based on the dynamic pointer code of the new battery pack authorized for replacement and the virtual position code of the corresponding installation slot of the battery pack to be replaced.

[0173] When the replacement is confirmed to be complete, a new event is added to the digital file. The new event cannot be modified. The new event includes the replacement time of the battery pack, the installation slot of the replacement cell in the battery pack, the static identification code of the battery pack to be replaced, and the static identification code of the new battery pack.

[0174] In some embodiments, the verification module 605 performs verification of the target battery cell, specifically for:

[0175] The target battery cell is authenticated based on the static identity code and its own real static identity code.

[0176] Based on the static identification code, the dynamic pointer code mapped from the digital file is searched to obtain the real-time status data of the target battery cell;

[0177] Based on the real-time status data and the electronic assembly blueprint, the performance of the target battery cell is verified.

[0178] Based on the identity verification result and the performance verification result, the overall verification result for the target battery cell is determined.

[0179] In some embodiments, after the verification of the target battery cell, the verification module 605 is specifically used for:

[0180] If the verification fails, the current battery pack assembly process is locked.

[0181] An alert will be issued for authentication failures and / or performance failures.

[0182] Upon receiving a secondary verification instruction for the pre-assembled battery pack dedicated kit, in response to the secondary verification instruction, the target battery cell is re-selected from the pre-assembled battery pack dedicated kit based on the electronic assembly blueprint and the obtained physical location code of the installation slot.

[0183] The target cell is re-verified. If the verification fails, the process returns to control and locks the current battery pack assembly process until the verification passes.

[0184] In some embodiments, the screening module 604, in response to a verification instruction for the pre-assembled battery pack-specific kit, selects the target battery cell from the pre-assembled battery pack-specific kit based on the electronic assembly blueprint and the obtained physical location code of the mounting slot, specifically for:

[0185] In response to the verification command for the pre-assembled battery pack-specific kit, the virtual location code of the corresponding installation slot is found from the electronic assembly blueprint based on the obtained physical location code of the installation slot.

[0186] Based on the virtual location code of the installation slot, the static identification code of the matching battery cell indicated by the electronic assembly blueprint is found to obtain the first static identification code;

[0187] Based on the first static identification code, the target battery cell is selected from the pre-assembled battery pack's exclusive kit.

[0188] This application provides a battery pack traceability method, system, device, and medium. In response to a battery pack assembly instruction, the system acquires the static identification code, dynamic pointer code, factory data, and battery pack assembly order data of the target cell, wherein the dynamic pointer code points to the real-time status data of the cell. A digital file is established for the target cell, showing a first mapping relationship between the static identification code, the dynamic pointer code, and the factory data. The battery pack assembly order data is parsed to obtain the assembly requirements for assembling the battery pack. Based on the assembly requirements and the digital file, an electronic assembly blueprint is determined, pre-matching the relationship between the cells and their installation positions. The electronic assembly blueprint includes the static identification code of the cell reserved in each installation slot and the virtual position of each cell in the reserved installation slot within the battery pack. The system establishes a matching relationship between the static identification code and the virtual location code of the installation slot, where each virtual location code of the installation slot corresponds to the physical location code of the installation slot in the physical world. In response to a verification command for the pre-assembled battery pack-specific kit, the system selects the target cell from the pre-assembled battery pack-specific kit based on the electronic assembly blueprint and the obtained physical location code of the installation slot. The target cell is verified, and the battery pack is assembled after verification. Upon successful verification, a second mapping relationship is established between the battery pack identifier, the virtual location code of the installation slot, and the static identification code of the cell, and this second mapping relationship is added to the digital archive for traceability of the cells in the battery pack. This application delves into the cell level within the battery pack, integrating static identification codes, dynamic pointer codes, and factory data to establish a digital archive with mapping relationships. From the initial stage of battery assembly, the precise matching route between each cell and its installation slot is clearly defined based on the requirements of assembling the battery pack. This allows for finer-grained traceability of cells throughout the entire battery pack lifecycle. Traceability leads directly to the battery cell, enabling precise location and zero mismatches during assembly. This avoids information gaps and achieves a truly granular and complete traceability chain that penetrates deep into the battery pack. Therefore, it solves the technical problem of poor traceability of battery packs in existing technologies.

[0189] It should be noted that those skilled in the art can clearly understand that the specific implementation process of the above-mentioned battery pack traceability system and each unit can be referred to the corresponding description in the foregoing method embodiments. For the sake of convenience and brevity, it will not be repeated here.

[0190] The aforementioned battery pack traceability system can be implemented as a computer program, which can, for example... Figure 3 It runs on the device shown.

[0191] Please see Figure 3 , Figure 3This is a schematic block diagram of a device provided in an embodiment of this application. The device 700 can be a terminal or a server. The terminal can be an electronic device with communication functions, such as a smartphone, tablet, laptop, desktop computer, personal digital assistant, or wearable device. The server can be a standalone server or a server cluster composed of multiple servers.

[0192] See Figure 3 The device 700 includes a processor 702, a memory, and a network interface 705 connected via a system bus 701, wherein the memory may include a non-volatile medium 703 and internal memory 704.

[0193] The non-volatile medium 703 may store an operating system 7031 and a computer program 7032. The computer program 7032 includes program instructions that, when executed, cause the processor 702 to perform a battery pack trace.

[0194] The processor 702 provides computing and control capabilities to support the operation of the entire device 700.

[0195] The internal memory 704 provides an environment for the execution of the computer program 7032 in the non-volatile medium 703. When the computer program 7032 is executed by the processor 702, the processor 702 can perform a battery pack trace.

[0196] This network interface 705 is used for network communication with other devices. Those skilled in the art will understand that... Figure 3 The structure shown is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the device 700 to which the present application is applied. The specific device 700 may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.

[0197] The processor 702 is used to run the computer program 7032 stored in the memory to perform the following steps:

[0198] In response to a battery pack assembly instruction, the system acquires the static identification code, dynamic pointer code, factory data, and battery pack assembly order data of the target cell, wherein the dynamic pointer code points to the real-time status data of the cell.

[0199] A digital file is established for the target battery cell to establish a first mapping relationship between the static identification code, the dynamic pointer code, and the factory data;

[0200] The battery pack assembly order data is parsed to obtain the assembly requirements for assembling the battery pack. Based on the assembly requirements and the digital file, an electronic assembly blueprint with pre-matched relationships between battery cells and their installation positions is determined. The electronic assembly blueprint includes a static identification code for each battery cell reserved in each installation slot, a virtual position code for each battery cell in the battery pack's reserved installation slot, and a matching relationship between the static identification code and the virtual position code of the installation slot. Each virtual position code of the installation slot corresponds to the physical position code of the installation slot in the physical world.

[0201] In response to the verification command for the pre-assembled battery pack dedicated kit, the target battery cell is selected from the pre-assembled battery pack dedicated kit based on the electronic assembly blueprint and the obtained physical location code of the installation slot.

[0202] The target battery cell is verified, and the battery pack is assembled after the verification is confirmed to be successful.

[0203] Upon successful verification, a second mapping relationship is established between the battery pack identifier, the virtual location code of the installation slot, and the static identification code of the battery cell. This second mapping relationship is then added to the digital file to facilitate the traceability of the battery cells in the battery pack.

[0204] It should be understood that in the embodiments of this application, the processor 702 may be a central processing unit (CPU), or it may be 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. The general-purpose processor may be a microprocessor or any conventional processor.

[0205] It will be understood by those skilled in the art that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program includes program instructions and can be stored in a medium, which is a computer-readable medium. The program instructions are executed by at least one processor in the computer system to implement the process steps of the embodiments of the above methods.

[0206] Therefore, this application also provides a medium. This medium can be a computer-readable medium. The medium stores a computer program, wherein the computer program includes program instructions. When executed by a processor, the program instructions cause the processor to perform the following steps:

[0207] In response to a battery pack assembly instruction, the system acquires the static identification code, dynamic pointer code, factory data, and battery pack assembly order data of the target cell, wherein the dynamic pointer code points to the real-time status data of the cell.

[0208] A digital file is established for the target battery cell to establish a first mapping relationship between the static identification code, the dynamic pointer code, and the factory data;

[0209] The battery pack assembly order data is parsed to obtain the assembly requirements for assembling the battery pack. Based on the assembly requirements and the digital file, an electronic assembly blueprint with pre-matched relationships between battery cells and their installation positions is determined. The electronic assembly blueprint includes a static identification code for each battery cell reserved in each installation slot, a virtual position code for each battery cell in the battery pack's reserved installation slot, and a matching relationship between the static identification code and the virtual position code of the installation slot. Each virtual position code of the installation slot corresponds to the physical position code of the installation slot in the physical world.

[0210] In response to the verification command for the pre-assembled battery pack dedicated kit, the target battery cell is selected from the pre-assembled battery pack dedicated kit based on the electronic assembly blueprint and the obtained physical location code of the installation slot.

[0211] The target battery cell is verified, and the battery pack is assembled after the verification is confirmed to be successful.

[0212] Upon successful verification, a second mapping relationship is established between the battery pack identifier, the virtual location code of the installation slot, and the static identification code of the battery cell. This second mapping relationship is then added to the digital file to facilitate the traceability of the battery cells in the battery pack.

[0213] The medium can be any computer-readable medium that can store program code, such as a USB flash drive, external hard drive, read-only memory (ROM), magnetic disk, or optical disk.

[0214] 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, computer software, or a combination of both. To clearly illustrate the interchangeability of hardware and software, the components and steps of the various examples have been generally described in terms of functionality in the foregoing description. 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 implementations should not be considered beyond the scope of this application.

[0215] In the several embodiments provided in this application, it should be understood that the disclosed apparatus and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative. For example, the division of each unit is merely a logical functional division, and there may be other division methods in actual implementation. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed.

[0216] The steps in the methods of this application embodiment can be adjusted, merged, or deleted according to actual needs. The units in the apparatus of this application embodiment can be merged, divided, or deleted according to actual needs. Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0217] 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 medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a medium and includes several instructions to cause a device (which may be a personal computer, a terminal, or a network device, etc.) to execute all or part of the steps of the methods of the various embodiments of this application.

[0218] The above are merely specific embodiments of this application, but the scope of protection of this application is not limited thereto. Any person skilled in the art can easily conceive of various equivalent modifications or substitutions within the technical scope disclosed in this application, and these modifications or substitutions should all be covered within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A battery pack traceability method, characterized in that, The battery pack traceability method includes: In response to a battery pack assembly instruction, the system acquires the static identification code, dynamic pointer code, factory data, and battery pack assembly order data of the target cell, wherein the dynamic pointer code points to the real-time status data of the cell. A digital file is established for the target battery cell to establish a first mapping relationship between the static identification code, the dynamic pointer code, and the factory data; The battery pack assembly order data is parsed to obtain the assembly requirements for assembling the battery pack. Based on the assembly requirements and the digital file, an electronic assembly blueprint with pre-matched relationships between battery cells and their installation positions is determined. The electronic assembly blueprint includes a static identification code for each battery cell reserved in each installation slot, a virtual position code for each battery cell in the battery pack's reserved installation slot, and a matching relationship between the static identification code and the virtual position code of the installation slot. Each virtual position code of the installation slot corresponds to the physical position code of the installation slot in the physical world. In response to the verification command for the pre-assembled battery pack dedicated kit, the target battery cell is selected from the pre-assembled battery pack dedicated kit based on the electronic assembly blueprint and the obtained physical location code of the installation slot. The target battery cell is verified, and the battery pack is assembled after the verification is confirmed to be successful. Upon successful verification, a second mapping relationship is established between the battery pack identifier, the virtual location code of the installation slot, and the static identification code of the battery cell. This second mapping relationship is then added to the digital file to facilitate the traceability of the battery cells in the battery pack.

2. The method according to claim 1, characterized in that, Upon successful verification, a second mapping relationship is established between the battery pack identifier, the virtual location code of the mounting slot, and the static identification code of the battery cell. This second mapping relationship is then added to the digital file for traceability of the battery cells within the battery pack. A battery pack that has been successfully assembled and removed from the assembly line is identified as a finished battery pack, wherein the finished battery pack is managed by a corresponding battery management system. The dynamic pointer code corresponding to the cell in the finished battery pack is integrated into the external communication interface of the battery management system where the finished battery pack is located; Through the external communication interface, monitoring and collection data for monitoring the finished battery pack are obtained from the battery management system where the finished battery pack is located. The digital files corresponding to the cells in the finished battery pack are updated based on the monitored and collected data, wherein the update of the digital files corresponding to the cells in the finished battery pack is triggered based on the obtained digital signature. If a read instruction is received for the dynamic pointer code corresponding to the cell in the finished battery pack, the corresponding information is searched in the updated digital file based on the dynamic pointer code corresponding to the cell in the finished battery pack and then output.

3. The method according to claim 2, characterized in that, If a read instruction for the dynamic pointer code corresponding to the cell in the finished battery pack is received, the process of searching for and outputting the corresponding information in the updated digital file based on the dynamic pointer code of the cell in the finished battery pack includes: If a read instruction is received for the dynamic pointer code corresponding to the cell in the finished battery pack, the battery pack's usage data, health status data, charge / discharge record data, and abnormal event data are retrieved from the updated digital archive on the cloud server based on the dynamic pointer code corresponding to the cell in the finished battery pack. The battery management system reports the health status data to the cloud server, and the vehicle networking device where the battery management system is located reports the battery pack's usage data, charge / discharge record data, and abnormal event data to the cloud server. If, based on the usage data, health status data, charge / discharge record data, and abnormal event data, it is determined that the battery pack is faulty, then the battery pack is determined to be a replacement battery pack, and a replacement instruction for the replacement battery pack is generated to replace it based on the replacement instruction.

4. The method according to claim 1, characterized in that, The verification of the target battery cell includes: The target battery cell is authenticated based on the static identity code and its own real static identity code. Based on the static identification code, the dynamic pointer code mapped from the digital file is searched to obtain the real-time status data of the target battery cell; Based on the real-time status data and the electronic assembly blueprint, the performance of the target battery cell is verified. Based on the identity verification result and the performance verification result, the overall verification result for the target battery cell is determined.

5. The method according to claim 4, characterized in that, After verifying the target battery cell, the process includes: If the verification fails, the current battery pack assembly process is locked. An alert will be issued for authentication failures and / or performance failures. Upon receiving a secondary verification instruction for the pre-assembled battery pack dedicated kit, in response to the secondary verification instruction, the target battery cell is re-selected from the pre-assembled battery pack dedicated kit based on the electronic assembly blueprint and the obtained physical location code of the installation slot. The target cell is re-verified. If the verification fails, the process returns to control and locks the current battery pack assembly process until the verification passes.

6. The method according to claim 1, characterized in that, In response to the verification command for the pre-assembled battery pack-specific kit, based on the electronic assembly blueprint and the obtained physical location code of the mounting slot, the target battery cell is selected from the pre-assembled battery pack-specific kit, including: In response to the verification command for the pre-assembled battery pack-specific kit, the virtual location code of the corresponding installation slot is found from the electronic assembly blueprint based on the obtained physical location code of the installation slot. Based on the virtual location code of the installation slot, the static identification code of the matching battery cell indicated by the electronic assembly blueprint is found to obtain the first static identification code; Based on the first static identification code, the target battery cell is selected from the pre-assembled battery pack's exclusive kit.

7. A battery pack traceability system, characterized in that, The battery pack traceability system includes: The acquisition module is used to acquire the static identification code, dynamic pointer code, factory data, and battery pack assembly order data of the target cell in response to the battery pack assembly instruction, wherein the dynamic pointer code points to the real-time status data of the cell; The digital file creation module is used to create a digital file for the target battery cell, which is a first mapping relationship between the static identification code, the dynamic pointer code and the factory data. The blueprint creation module is used to parse the battery pack assembly order data to obtain the assembly requirements for assembling the battery pack, and based on the assembly requirements and the digital file, to determine an electronic assembly blueprint that pre-matches the relationship between the battery cells and their installation positions. The electronic assembly blueprint includes a static identification code for each battery cell reserved in each installation slot, a virtual position code for each battery cell in the battery pack's reserved installation slot, and a matching relationship between the static identification code and the virtual position code of the installation slot. Each virtual position code of the installation slot corresponds to the physical position code of the installation slot in the physical world. The screening module is used to screen the target battery cell from the pre-assembled battery pack dedicated kit in response to the verification command for the pre-assembled battery pack dedicated kit, based on the electronic assembly blueprint and the obtained physical location code of the installation slot. The verification module is used to verify the target battery cell, wherein the battery pack is assembled after the verification is confirmed to be successful. The digital archive update module is used to establish a second mapping relationship between the battery pack identifier, the virtual location code of the installation slot, and the static identification code of the battery cell when the verification is confirmed to be successful. The second mapping relationship is added to the digital archive for the purpose of tracing the battery cells in the battery pack.

8. A battery pack traceability device, characterized in that, The method includes a memory, a processor, and a battery pack tracing program stored in the memory and executable on the processor, wherein the processor executes the battery pack tracing program to implement the steps of the battery pack tracing method according to any one of claims 1 to 6.

9. A medium, characterized in that, The medium stores a program for implementing a battery pack traceability method, which is executed by a processor to implement the steps of the battery pack traceability method as described in any one of claims 1 to 6.

Images