A verification method, a battery, a computer device and a storage medium
Patent Information
- Application Number
- CN202611161397.1
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2026-07-31
- Publication Date
- 2026-10-27
Smart Images
Figure CN122994036A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of battery technology, and in particular to a verification method, a battery, a computer device, and a storage medium. Background Technology
[0002] With the widespread use of portable electronic devices (such as smartphones, tablets, and laptops), battery safety has become an increasingly important concern. To ensure the safety of electronic devices and prevent safety hazards from substandard third-party batteries, a common solution is to integrate an encryption chip inside the battery. This encryption chip is typically located on the battery's protection board and performs two-way authentication with the electronic device's host device using a preset key.
[0003] However, third parties can disassemble the original manufacturer's protection board with the encryption chip and assemble it with non-original battery cells to impersonate an original battery. Since the encryption chip itself has not been cracked, the authentication between the electronic device and the protection board can still pass, and the electronic device will mistakenly believe that the battery is a legitimate original battery, thus providing normal power. Summary of the Invention
[0004] This application provides a verification method, a battery, a computer device, and a storage medium that can prevent the battery protection board from being illegally disassembled and used with non-original battery cells, thereby further improving the overall safety of the battery system.
[0005] In a first aspect, this application provides a verification method applied to a battery, the battery including a battery protection board, a battery cell, and a safety verification module, the safety verification module being used to connect an electronic device and the battery protection board, the battery protection board being connected to the battery cell; the method includes: in response to the safety verification module being connected to the electronic device, the safety verification module sending verification notification information to the battery protection board; in response to the verification notification information, the battery protection board obtaining the battery cell's identification identifier from the battery cell, and, if the battery cell's identification identifier passes verification, determining a target count value based on the current count value of a one-way counter; sending the target count value to the safety verification module; in response to the target count value being greater than or equal to a reference count value, the safety verification module storing the target calculated value and sending a first notification message to the electronic device, the first notification message being used to indicate successful battery verification; wherein, the reference count value is the count value previously stored by the safety verification module.
[0006] As can be seen, after the battery protection board verifies the identity of the battery cell, it determines the target count value based on the current count value of the unidirectional counter and sends the target count value to the security verification module. The security verification module only sends a successful verification notification to the electronic device when the target count value is greater than or equal to the reference count value. The unidirectional counter only supports monotonically increasing and cannot be rolled back, effectively preventing third parties from re-pairing the battery protection board with non-original battery cells by reverting to old data.
[0007] In one possible implementation, obtaining the battery cell's identity identifier from the battery cell may include: obtaining the battery cell's identity identifier from the battery cell through a hardware binding interface between the battery protection board and the battery cell.
[0008] As can be seen, the battery protection board and the battery cell can be connected via a hardware bonding interface. This interface is designed for easy connection (e.g., special snap-fit contacts). If the battery protection board and the battery cell are forcibly separated, the hardware bonding interface will be physically damaged and cannot be repaired. This forcibly bonds the battery protection board and the battery cell at the hardware level, preventing the battery protection board from being illegally disassembled and used with non-original battery cells, thereby further improving the overall safety of the battery system.
[0009] In one possible implementation, the battery cell may include a one-time programmable chip for storing the battery cell's identification identifier.
[0010] It is evident that by setting a one-time programmable chip in the battery cell to store the battery cell's identity, the data in the one-time programmable chip is unchangeable and indelible once written, thus ensuring the uniqueness and immutability of the battery cell's identity at the hardware level.
[0011] In one possible implementation, the above method may further include: the battery protection board determining the initial identity of the battery cell based on the binding key and the serial number of the battery protection board; and determining that the identity of the battery cell has been verified in response to the initial identity being the same as the identity of the battery cell; wherein the initial identity of the battery cell is the identity set at the factory of the battery, and the binding key is obtained by encrypting the initial identity of the battery cell and the serial number of the battery protection board.
[0012] As can be seen, the battery protection board and the battery cell are paired and bound together by a binding key during the battery manufacturing stage. If either one is replaced, the verification will fail, thus effectively preventing the original battery protection board from being used with non-original battery cells.
[0013] In one possible implementation, the above method may further include: the security verification module sending a second notification message to the electronic device in response to the target count value being less than the reference count value, the second notification message indicating that the battery verification has failed.
[0014] As can be seen, when the safety verification module detects that the target count value is lower than the reference count value, it can immediately send a second notification message to the electronic device to indicate that the battery verification has failed. The electronic device can then take appropriate measures in a timely manner to prevent the continued use of potentially unsafe batteries, thus ensuring the safety of the user and the electronic device.
[0015] In one possible implementation, the above method may further include: if the battery cell's identity identifier is not obtained, controlling the battery protection board to be in a locked state and sending an identity identifier acquisition failure message to the security verification module; in response to the identity identifier acquisition failure message, the security verification module sends a third notification message to the electronic device, the third notification message being used to indicate a battery abnormality.
[0016] It is evident that if the battery protection board cannot obtain the battery cell's identification information from the battery cell, it can immediately lock the battery protection board, thereby eliminating the possibility of illegal battery cells being used even without identification information.
[0017] In one possible implementation, the above method may further include: sending an identity verification failure message to the security verification module if the identity of the battery cell fails to be verified; and the security verification module, in response to the identity verification failure message, sending a fourth notification message to the electronic device, the fourth notification message being used to instruct the battery protection board to refuse to work.
[0018] It is evident that if the cell's identification fails verification, a fourth notification message can be immediately sent to the electronic device to instruct the battery protection board to refuse to work, effectively identifying and intercepting situations where the original battery protection board has been disassembled and reassembled with non-original cells.
[0019] Secondly, this application provides a battery, which includes a battery protection board, a battery cell, and a safety verification module. The safety verification module is used to connect an electronic device and the battery protection board, and the battery protection board is connected to the battery cell. The safety verification module is used to send verification notification information to the battery protection board in response to being connected to the electronic device. The battery protection board is used to obtain the battery cell's identification identifier from the battery cell in response to the verification notification information, and, if the battery cell's identification identifier is verified, determine a target count value based on the current count value of a one-way counter; and send the target count value to the safety verification module. The safety verification module is also used to store the target calculated value and send a first notification message to the electronic device in response to the target count value being greater than or equal to a reference count value. The first notification message indicates that the battery verification was successful. The reference count value is the count value previously stored by the safety verification module.
[0020] In one possible implementation, the aforementioned battery protection board can also be used to obtain the battery cell's identity identifier from the battery cell through a hardware bonding interface between the battery protection board and the battery cell.
[0021] In one possible implementation, the battery cell may include a one-time programmable chip for storing the battery cell's identification identifier.
[0022] In one possible implementation, the aforementioned battery protection board can also be used to determine the initial identity of the battery cell based on the binding key and the serial number of the battery protection board; in response to the initial identity being the same as the identity of the battery cell, it is determined that the identity of the battery cell has been verified; wherein, the initial identity of the battery cell is the identity set at the factory of the battery, and the binding key is obtained by encrypting the initial identity of the battery cell and the serial number of the battery protection board.
[0023] In one possible implementation, the aforementioned security verification module can also be used to send a second notification message to the electronic device in response to a target count value being less than a reference count value. The second notification message is used to indicate that the battery verification has failed.
[0024] In one possible implementation, the battery protection board can also be used to control the battery protection board to be locked and send an identity acquisition failure message to the security verification module when the identity of the battery cell is not obtained; the security verification module can also be used to send a third notification message to the electronic device in response to the identity acquisition failure message, the third notification message being used to indicate a battery abnormality.
[0025] In one possible implementation, the battery protection board can also be used to send an identity verification failure message to the security verification module if the identity of the battery cell fails to be verified; the security verification module can also be used to send a fourth notification message to the electronic device in response to the identity verification failure message, the fourth notification message being used to instruct the battery protection board to refuse to work.
[0026] Thirdly, embodiments of this application provide a computer device, the computer device comprising: a memory for storing a program; and a processor for executing the program stored in the memory, wherein when the program is executed by the processor, the processor executes a method as described in any possible implementation of the first aspect.
[0027] Fourthly, embodiments of this application provide a computer-readable storage medium storing a computer program, the computer program including program instructions, which, when executed by a processor, perform a method as described in the first aspect and any possible implementation thereof.
[0028] Fifthly, embodiments of this application provide a computer program product, which includes: instructions or a computer program; when the instructions or the computer program are executed, the method in the first aspect and any possible implementation of the first aspect is implemented.
[0029] Sixthly, embodiments of this application provide a chip, the chip including a processor, the processor being configured to execute instructions, such that when the processor executes the instructions, the chip performs the method as described in the first aspect and any possible implementation thereof. Attached Figure Description
[0030] Figure 1 This is a schematic diagram of the structure of a battery; Figure 2 This is a schematic diagram of the structure of a battery provided in an embodiment of this application; Figure 3 This is a schematic diagram of a battery replacement scenario; Figure 4 A flowchart illustrating a verification method provided in an embodiment of this application; Figure 5A An interface diagram showing a verification failure is provided in an embodiment of this application; Figure 5B Another interface diagram showing a verification failure is provided in this application embodiment; Figure 5C Another interface diagram showing a verification failure is provided in this application embodiment; Figure 5D Another interface diagram showing a verification failure is provided in this application embodiment; Figure 5E An interface diagram showing successful verification is provided for an embodiment of this application; Figure 6 A schematic flowchart illustrating a battery manufacturing method provided in this application embodiment; Figure 7 This is a schematic diagram of the structure of a computer device provided in an embodiment of this application. Detailed Implementation
[0031] The embodiments of this application will now be described with reference to the accompanying drawings.
[0032] The terms "first," "second," "third," and "fourth," etc., used in the specification, claims, and accompanying drawings of this application are used to distinguish different objects, not to describe a specific order. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or apparatus that includes a series of steps or units is not limited to the listed steps or units, but may optionally include steps or units not listed, or may optionally include other steps or units inherent to these processes, methods, products, or apparatuses.
[0033] It should be understood that in this application, "at least one (item)" means one or more, and "more than" means two or more. "And / or" is used to describe the relationship between related objects, indicating that three relationships can exist. For example, "A and / or B" can represent three cases: only A exists, only B exists, and both A and B exist simultaneously, where A and B can be singular or plural. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship. "At least one (item) of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one (item) of a, b, or c can represent: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", where a, b, and c can be single or multiple.
[0034] In this document, the term "embodiment" means that a particular feature, structure, or characteristic described in connection with an embodiment may be included in at least one embodiment of this application. The appearance of this phrase in various places throughout the specification does not necessarily refer to the same embodiment, nor is it a separate or alternative embodiment mutually exclusive with other embodiments. It will be explicitly and implicitly understood by those skilled in the art that the embodiments described herein can be combined with other embodiments.
[0035] The terms “component,” “module,” “system,” etc., used in this specification are used to refer to computer-related entities, hardware, firmware, combinations of hardware and software, software, or software in execution. For example, a component can be, but is not limited to, a process running on a processor, a processor, an object, an executable file, an execution thread, a program, and / or a computer. As illustrated, applications running on computing devices and computing devices can both be components. One or more components may reside in a process and / or an execution thread, and components may be located on a single computer and / or distributed among two or more computers. Furthermore, these components can be executed from various computer-readable media on which various data structures are stored. Components can communicate, for example, via local and / or remote processes based on signals having one or more data packets (e.g., data from two components interacting with another component between a local system, a distributed system, and / or a network, such as the Internet interacting with other systems via signals).
[0036] First, some of the terms used in this application will be explained to facilitate understanding by those skilled in the art.
[0037] I. Battery Batteries are energy storage components in electronic devices (such as smartphones, laptops, power tools, and new energy vehicles). Their core function is to stably release electrical energy when the electronic device needs it and to safely store electrical energy while the device is charging. Figure 1 As shown, Figure 1This is a schematic diagram of a battery structure. The battery 100 includes a battery cell 110 and a battery protection board 120. The battery cell 110 and the battery protection board 120 are connected by a conventional power supply to achieve power transmission, jointly ensuring the normal operation and safe use of the battery 100.
[0038] Cell 110 is the core component of battery 100 responsible for the actual storage and release of chemical energy. Its internal structure mainly consists of a positive electrode, a negative electrode, a separator, and an electrolyte. Taking a lithium-ion cell as an example, during charging, lithium ions are extracted from the positive electrode and inserted into the negative electrode through the electrolyte and separator; during discharging, they move in the reverse direction. The performance of cell 110 directly determines key parameters of battery 100 such as capacity, voltage plateau, internal resistance, and cycle life.
[0039] The battery protection board 120 is a printed circuit board integrating an integrated circuit (IC), a metal-oxide-semiconductor field-effect transistor (MOSFET), switches, resistors, and capacitors. Its core function is to monitor the voltage, current, and temperature of the battery cell 110 in real time. When an abnormal state is detected (such as voltage exceeding the overcharge threshold or falling below the over-discharge threshold, current exceeding the set limit, or temperature exceeding the safe range), the control IC on the battery protection board 120 will quickly drive the MOSFET to turn off, cutting off the charging and discharging circuit, thereby protecting the battery cell 110 from damage and preventing safety accidents. In addition, the battery protection board 120 can also integrate a fuel gauge function, accurately calculating the remaining state of charge (SoC) through coulomb integration or voltage modeling, and exchanging battery status information with the host of the electronic device (such as the motherboard of a mobile phone) in real time through a communication protocol.
[0040] Currently, to ensure battery safety and prevent safety hazards from substandard third-party batteries, the industry commonly adopts a technical solution that integrates an encryption chip inside the battery protection board 120. In scenarios where electronic devices require battery replacement, the encryption chip on the battery protection board 120 of the replaced battery will authenticate with the host device of the electronic device using a preset key. Only batteries that pass authentication can be recognized by the electronic device and used normally (such as allowing charging and providing full power).
[0041] The following are two commonly used authentication schemes between encryption chips and the host side of electronic devices: 1. Random code encryption / decryption scheme.
[0042] The main control chip integrated within the host unit of the electronic device first generates a random code and sends it as plaintext to the encryption chip of the battery protection board 120. Upon receiving the plaintext, the encryption chip encrypts it using its built-in encryption algorithm, generating ciphertext, and returns it to the main control chip. The main control chip then decrypts the ciphertext, obtaining a decrypted value, and compares this decrypted value with the previously sent original plaintext. If they match, authentication is successful, allowing the electronic device to power on and charge; otherwise, authentication fails, and the electronic device disables charging and shuts down.
[0043] 2. Unique identifier encryption / decryption scheme.
[0044] The main control chip integrated within the host unit of the electronic device directly reads the identifier stored inside the encryption chip of the battery protection board 120. The main control chip compares the read identifier with a preset unique identifier. If they match, authentication is successful, allowing the electronic device to power on and charge; if they do not match, authentication fails, and the electronic device will disable charging and power off.
[0045] However, the authentication process in both of the above schemes only occurs between the host device of the electronic device and the encryption chip on the battery protection board 120, without verifying the identity of the battery cell 110 itself. Currently, the binding between the battery protection board 120 and the battery cell 110 relies primarily on simple data recording at the software level, lacking hardware-level binding and anti-tampering mechanisms. This allows third parties to disassemble the original battery protection board 120 with its encryption chip and reassemble it with a non-original battery cell. Because the encryption chip on the battery protection board 120 can still pass the authentication process, the electronic device may mistakenly identify the battery as an original battery, thus impersonating it and posing a serious security risk.
[0046] In view of this, embodiments of this application provide a verification method, a battery, a computer device, and a storage medium. The method is applied to a battery, verifies the identity of the battery cell through a battery protection board, and records and compares the verification history by combining the non-rollback characteristic of a one-way counter, thereby realizing hardware-level binding between the battery cell and the battery protection board.
[0047] Please refer to Figure 2 , Figure 2 This is a schematic diagram of the structure of a battery provided in an embodiment of this application. Figure 2 As shown, the battery 200 includes a safety verification module 210, a battery protection board 220, and a battery cell 230.
[0048] The security verification module 210 communicates with the electronic device and with the battery protection board 220. The battery protection board 220 includes a security unit 221, which comprises a security chip 222, an encryption algorithm module 223, and a one-way counter 224. The security chip 222 stores a binding key, the encryption algorithm module 223 stores an encryption algorithm, and the one-way counter 224 stores the current count value, which is an incrementing value that cannot be rolled back and cannot be decreased by any means. The battery cell 230 includes a one-time programmable chip 231. The one-time programmable chip 231 stores the identification identifier of the battery cell 230.
[0049] The safety verification module 210 and the battery protection board 220 establish a bidirectional communication connection through an internal communication interface. This internal communication interface can be any one of a general-purpose input / output (GPIO) interface, a serial peripheral interface (SPI), an inter-integrated circuit (I²C) bus, or a custom single-wire protocol. This application embodiment does not specifically limit this.
[0050] In addition to the conventional power supply connections (such as positive and negative electrode nickel strips) used for power transmission, a dedicated Hardware Binding Interface (HBI) is added between the battery protection board 220 and the battery cell 230. This hardware binding interface is only used by the battery protection board 220 to read the identification of the battery cell 230 and does not carry out any power transmission function.
[0051] Please see Figure 3 , Figure 3 This is a schematic diagram of a battery replacement scenario. Figure 3 As shown, the electronic device 310 has a replaceable battery design. The first battery 320 is the battery currently installed inside the electronic device 310, and the second battery 330 is a spare battery or a new battery to be replaced. The first battery 320 and the second battery 330 are the aforementioned battery 200, including a battery protection board, battery cells, and a safety verification module.
[0052] When a user needs to replace the battery in electronic device 310, the first battery 320 can be removed from electronic device 310, and the second battery 330 can be installed in electronic device 310. After electronic device 310 and the second battery 330 are connected, a communication connection is established between electronic device 310 and the security verification module of the second battery 330, thereby triggering the verification process of the second battery 330. The verification process of the second battery 330 can be found in [link to relevant documentation]. Figure 4 A detailed description.
[0053] After the second battery 330 passes verification, the electronic device 310 allows the second battery 330 to charge and supply power normally; if the second battery 330 fails verification, the electronic device 310 refuses to recognize the second battery 330 or restricts its function, thereby preventing unauthorized or potentially dangerous batteries from being connected to the electronic device 310.
[0054] It should be noted that the electronic device 310 involved in the embodiments of this application may be a mobile phone, tablet computer, laptop computer, handheld computer, mobile internet device (MID), wearable device, virtual reality (VR) device, augmented reality (AR) device, smart screen, artificial intelligence (AI) speaker, headphones, terminal in industrial control, terminal in self-driving, terminal in remote medical surgery, terminal in smart grid, terminal in transportation safety, terminal in smart city, terminal in smart home, personal digital assistant (PDA), etc., and the embodiments of this application do not limit it in any way.
[0055] The following is combined with Figure 2 The battery structure shown illustrates the verification method provided in the embodiments of this application.
[0056] Please see Figure 4 , Figure 4 This is a flowchart illustrating a verification method provided in an embodiment of this application. Figure 4 As shown, the verification method may include, but is not limited to, the following steps: S401, the electronic device establishes a communication connection with the security verification module.
[0057] After the second battery to be replaced is installed into the electronic device, a communication connection is established between the electronic device and the safety verification module of the second battery.
[0058] The communication connection can be a wired communication method based on Single Wire Protocol (SWP), I²C, System Management Bus (SM Bus), or HDQ protocol (a single-wire communication protocol). The electronic device sends a handshake signal to the security authentication module through the communication pin (such as a data pin or a dedicated verification pin) in the second battery interface. After receiving the handshake signal, the security authentication module returns an acknowledgment signal, and both parties complete the initialization of the communication link, thereby establishing a stable bidirectional communication connection.
[0059] In one possible implementation, after the safety verification module of the second battery establishes a communication connection with the electronic device, the safety verification module can report the serial number of the battery protection board stored locally to the electronic device. This serial number is generated when the second battery leaves the factory; the battery protection board reads its own identifier and sends it to the safety verification module, which receives and stores the serial number in its internal memory (such as non-volatile memory). For details, please refer to [link to relevant documentation]. Figure 6 Description of step S605.
[0060] Accordingly, the electronic device receives the serial number of the battery protection board from the safety verification module. The electronic device compares this serial number with a locally pre-stored list of compatible serial numbers to determine if the serial number matches the electronic device model. This locally pre-stored list of compatible serial numbers includes battery protection board serial numbers that are compatible with the current electronic device model and are authorized by the manufacturer. Optionally, the electronic device may also compare the serial number with serial number matching rules to determine if the serial number matches the electronic device model. Serial number matching rules may include one or more of the following: determining whether the serial number belongs to a battery batch permitted for the electronic device model, determining whether the serial number is within the range of serial numbers authorized by the electronic device manufacturer, or determining whether specific fields in the serial number (such as manufacturer code or battery type code) are consistent with the model identifier of the electronic device.
[0061] If the electronic device determines that the serial number of the battery protection board matches the model of the electronic device, it continues to execute step S402. If the electronic device determines that the serial number of the battery protection board does not match the electronic device (e.g., the battery type corresponding to the serial number is not applicable to the current device, the serial number is not within the authorized range, or the serial number format is invalid), the electronic device can directly determine that the second battery is unqualified, prohibit the charging operation, and output the first prompt message to the user interface, such as... Figure 5A As shown, the first message may be "Battery incompatible, please use original battery".
[0062] In one possible implementation, after the safety verification module of the second battery establishes a communication connection with the electronic device, the electronic device can send a connection notification message to the safety verification module. Correspondingly, the safety verification module receives the connection notification message from the electronic device. This connection notification message is used to notify the safety verification module that it has connected to the electronic device.
[0063] S402, the safety verification module sends a verification notification to the battery protection board. Correspondingly, the battery protection board receives the verification notification from the safety verification module.
[0064] In this embodiment, in response to the security verification module being connected to the electronic device, the security verification module can send verification notification information to the battery protection board. The verification notification information is used to notify the battery protection board to verify the identity of the battery cell.
[0065] The safety verification module and the battery protection board are connected via an internal communication interface. The verification notification can be a preset level signal (such as a high-level pulse) or a command frame in a specific format. For example, the safety verification module pulls a dedicated GPIO pin high, and the battery protection board, upon detecting this level change, is awakened and begins executing step S403; alternatively, the safety verification module sends a command frame containing a verification trigger identifier to the battery protection board, which parses the command frame to confirm the identity of the battery cell requiring verification.
[0066] S403, the battery protection board responds to the verification notification information and obtains the cell's identity identifier from the cell.
[0067] In this embodiment of the application, after receiving the verification notification information from the security verification module, the battery protection board obtains the battery cell's identity identifier in response to the verification notification information.
[0068] The battery cell integrates a memory chip to store the cell's unique identifier. Optionally, the memory chip can be a one-time programmable (OTP) chip, whose internal data, once written at the factory, cannot be changed or erased, thus ensuring the uniqueness and immutability of the cell's identifier.
[0069] In one possible implementation, after receiving verification notification information from the security verification module, the battery protection board, in response to this notification, can obtain the battery cell's identification identifier from the battery cell through the hardware bonding interface between the battery protection board and the battery cell. This hardware bonding interface is designed with a fragile structure, for example, using special snap-fit contacts or brittle connectors. Under normal use, this interface reliably enables signal transmission between the protection board and the battery cell. If the battery protection board is forcibly removed or separated from the battery cell, the hardware bonding interface will suffer irreversible physical damage due to its fragile design, such as snap-fit breakage, contact detachment, or broken connection lines. Since this interface cannot be repaired after damage, and its absence prevents the battery protection board from reading the battery cell's identification identifier, the removed battery protection board cannot be reassembled with any other battery cell (such as a non-original battery cell) and pass verification. This physically achieves hardware-level bonding between the battery protection board and the battery cell, effectively preventing attacks involving "protection board reuse."
[0070] In one possible implementation, after the battery protection board receives the verification notification information from the security verification module, in response to the verification notification information, if the battery protection board fails to obtain the identity identifier of the battery cell within a preset time, it can determine that the battery cell has any one or more of the following situations: the memory chip integrated in the battery cell is damaged, the hardware bonding interface between the battery protection board and the battery cell is damaged, or the battery cell has been replaced with an illegal battery cell that does not have the ability to store identity identifiers.
[0071] In this situation, the battery protection board first performs a locking operation, which means it controls its internal charge / discharge control switch (such as a MOSFET switch) to be in the off state and prohibits any attempt to close the switch, thus locking the battery protection board. In this locked state, regardless of whether a charging or discharging command is subsequently received, the battery protection board will not conduct the charging / discharging circuit, thereby preventing the abnormal battery from charging or discharging at the hardware level.
[0072] Simultaneously, the battery protection board sends an identification retrieval failure message to the safety verification module. This message can be a preset fault code or a specific voltage level signal, used to notify the safety verification module that the identification of the current battery cell cannot be read. In response to this message, the safety verification module can send a third notification message to the electronic device. This third notification message indicates a battery malfunction.
[0073] Upon receiving the third notification message, the electronic device can directly determine that the second battery is defective, prohibit charging, or record an anomaly log for subsequent analysis. The electronic device can also output a second prompt message to the user interface, such as... Figure 5B As shown, the second message could be "Battery malfunction, please replace with an original battery".
[0074] For example, a third party obtains an original battery, which includes an original battery protection board and original battery cells. When the third party forcibly separates the original battery protection board and original battery cells from the original battery, the hardware bonding interface between the original battery protection board and the original battery cells suffers irreversible physical damage due to the force (e.g., broken clips, detached contacts, or broken connecting lines), resulting in a permanent interruption of the dedicated communication link between the battery protection board and the battery cells.
[0075] When a third party assembles a disassembled original battery protection board with non-original battery cells and installs the assembled battery into an electronic device, the battery protection board, in response to a verification notification, attempts to read the cell's identification identifier via the hardware binding interface. However, the hardware binding interface is not functioning properly, and the battery protection board fails to obtain the cell's identification identifier. The battery protection board determines that the current cell is invalid, immediately enters a locked state, and sends an identification identifier acquisition failure message to the security verification module. In response to this identification identifier acquisition failure message, the security verification module can send a third notification message to the electronic device. This third notification message indicates a battery malfunction. Upon receiving the third notification message, the electronic device can output a "Battery malfunction, please replace with an original battery" message to the user interface and simultaneously disable charging.
[0076] S404, the battery protection board determines the target count value based on the current count value of the one-way counter, provided that the cell's identity has been verified.
[0077] In this embodiment of the application, after the battery protection board obtains the battery cell's identification identifier from the battery cell, it needs to verify the battery cell's identification identifier.
[0078] In one possible implementation, the battery protection board can read its own stored binding key and serial number, and retrieve an encryption algorithm from its encryption algorithm module. This encryption algorithm is the same as the one used when the battery was manufactured. Using this encryption algorithm, based on the binding key and the battery protection board's serial number, the initial identity of the battery cell is determined. The initial identity of the battery cell is the identity set at the factory of the second battery, and the binding key is obtained by encrypting the initial identity of the battery cell and the serial number of the battery protection board.
[0079] like Figure 6 As shown, Figure 6 This is a schematic flowchart of a battery manufacturing method provided in an embodiment of this application.
[0080] S601, the battery protection board obtains the initial identification of the battery cell from the battery cell.
[0081] In this embodiment, the battery protection board can obtain the battery cell's identification identifier from the battery cell through the hardware binding interface between the battery protection board and the battery cell. For details, please refer to the description of S403, which will not be repeated here.
[0082] S602, the battery protection board encrypts the initial identification of the battery cell and the serial number of the battery protection board to obtain the binding key.
[0083] In this embodiment, after obtaining the initial identity of the battery cell, the battery protection board reads its own serial number and then reads an encryption algorithm (such as Advanced Encryption Standard (AES), SM4 (one of the commercial cryptographic algorithm standards issued by the State Cryptography Administration of China), or Hash-based Message Authentication Code (HMAC)) from the encryption algorithm module of the battery protection board. Using this encryption algorithm, the initial identity of the battery cell and the serial number of the battery protection board are encrypted to generate a binding key, which uniquely corresponds to the initial identity of the battery cell and the serial number of the battery protection board.
[0084] S603, the battery protection board stores the binding key and initializes the one-way counter to obtain the initial count value.
[0085] In this embodiment, the battery protection board can store the binding key in a read-only area within the battery protection board. Optionally, the battery protection board has a built-in security chip, in which the binding key can be stored.
[0086] S604, the battery protection board initializes the unidirectional counter to obtain the initial count value.
[0087] The initial count value can be set to 0, 1, or other preset non-negative integers; this embodiment does not specifically limit this. This initial value serves as the starting point for the subsequent monotonically increasing unidirectional counter.
[0088] It should be noted that the initialization operation of the unidirectional counter is performed only once before the battery leaves the factory. After initialization, the unidirectional counter enters normal operating mode, and its count value can only increase monotonically, and cannot be rolled back or reset to the initial value. The implementation methods of the unidirectional counter include, but are not limited to: hardware counter register, one-time programmable fuse array, or software counter with anti-rollback mechanism based on flash memory storage.
[0089] S605, the battery protection board sends its serial number and initial count value to the safety verification module. Correspondingly, the safety verification module receives the battery protection board's serial number and initial count value from the battery protection board.
[0090] After the battery protection board completes the initialization of the unidirectional counter and obtains the initial count value, it sends this initial count value along with its own serial number to the security verification module. The security verification module receives the initial count value and the battery protection board's serial number and stores them in its internal memory (such as non-volatile memory).
[0091] The initial count value is the starting value of the unidirectional counter. The safety verification module needs to store this initial count value as a reference count value in the next verification process. The serial number of the battery protection board can be used to distinguish different battery protection boards. The safety verification module can also send the serial number of the battery protection board to the electronic device to determine whether the serial number of the battery protection board matches the model of the electronic device.
[0092] The battery protection board compares the identification identifier read from the battery cell with the calculated initial identification identifier. If the initial identification identifier is the same as the battery cell's identification identifier, the current battery cell's identification identifier is verified, indicating that the battery cell is a legitimate battery cell that was bound to the protection board at the factory.
[0093] If the initial identification identifier differs from the cell's identification identifier, the current cell's identification identifier is confirmed to have failed verification. In the event of a cell's identification identifier failure, the battery protection board can immediately control its internal charge / discharge control switches (such as MOSFET switches) to remain in or switch to the off state, prohibiting any attempt to turn on the switch. That is, regardless of subsequent charging or discharging requests from electronic devices, the battery protection board will not activate the charging / discharging circuit, thus refusing to perform any charging or discharging operations at the hardware level. The battery protection board can also send an identification identifier verification failure message to the security verification module. In response to the identification identifier verification failure message, the security verification module sends a fourth notification message to the electronic device, which instructs the battery protection board to refuse operation.
[0094] Upon receiving the fourth notification message, the electronic device can determine that the second battery is defective, prohibit charging, or record an anomaly log for subsequent analysis. The electronic device can also output a third prompt message to the user interface, such as... Figure 5C As shown, the third prompt message could be "A non-original battery has been detected, and the device will not be able to charge."
[0095] In one possible implementation, the battery protection board reads the current count value of the unidirectional counter after the cell's identification is verified, and determines the target count value based on the current count value. Optionally, the battery protection board can increase the current count value by a preset step (e.g., a step of 1, 2, or other set value) to obtain the target count value.
[0096] It is understandable that during the next verification process of the second battery, the target count value will be the current count value during the next verification process.
[0097] S405, the battery protection board sends the target count value to the safety verification module. Correspondingly, the safety verification module receives the target count value from the battery protection board.
[0098] The battery protection board and the safety verification module are connected via an internal communication interface. The battery protection board encapsulates the target count value according to a preset data frame format and sends it to the safety verification module through this communication interface.
[0099] Accordingly, the security verification module monitors its communication interface with the battery protection board in real time. When the target count value is reached, the security verification module receives the data, parses it, and extracts the target count value.
[0100] S406, the security verification module stores the target calculated value in response to the target count value being greater than or equal to the reference count value.
[0101] The reference count value is the count value previously stored by the safety verification module. If the second battery is being verified for the first time since leaving the factory, the reference count value at this time is the initial count value of the unidirectional counter; if the second battery is being verified for the Nth time since leaving the factory, the reference count value at this time is the count value stored by the safety verification module when the second battery is verified for the (N-1)th time. N is an integer greater than 1.
[0102] In this embodiment, after receiving the target count value from the battery protection board, the security verification module compares the target count value with a reference count value. If the target count value is greater than or equal to the reference count value, it indicates that the currently received target count value satisfies the monotonically non-decreasing condition compared to the historically stored reference count value. Therefore, it can be determined that the target count value has not been maliciously tampered with during transmission, and that the one-way counter inside the battery protection board has not been rolled back by a third party. In other words, the comparison result proves that the one-way counter state used for this verification is legally increasing, and not forged by resetting the one-way counter. Under this premise, the security verification module stores the target count value as a new reference count value.
[0103] In one possible implementation, if the target count value is less than the reference count value, it may be due to one or more of the following situations occurring in the second battery: the unidirectional counter inside the battery protection board has been rolled back by a third party; the current battery protection board has been disassembled and reassembled with another cell with a lower count value, resulting in a mismatch in the counter state; or there is an abnormality in the count value storage logic inside the safety verification module or the battery protection board (such as data corruption).
[0104] In the above situation, the security verification module does not perform the storage operation of the target count value, and sends a second notification message to the electronic device, which is used to indicate that the battery verification has failed.
[0105] Accordingly, upon receiving the second notification message, the electronic device parses and identifies the "battery verification failed" status information. The electronic device can determine that the second battery is unqualified, prohibit the charging operation, and output a fourth prompt message to the user interface, such as... Figure 5D As shown, the fourth message could be "Battery verification failed, please replace with an original battery".
[0106] For example, assuming the preset step size is 1, after a third party obtains the original battery (reference count value is 5), it illegally rewrites the battery protection board data in the original battery back to the old version with the current count value of 3, assembles the battery protection board with non-original battery cells, and then installs the battery into an electronic device.
[0107] At this point, assuming the battery protection board can respond to the verification notification information, obtain the cell's identification identifier from the cell, and if the cell's identification identifier passes verification, increment the current count value (current count value is 3) by a preset step to obtain a target count value of 4. The battery protection board then sends the target count value to the safety verification module. The safety verification module compares the target count value with the reference count value. Since the target count value 4 is less than the reference count value 5, the count value is determined to be rolled back. The safety verification module does not perform the target count value storage operation and sends a second notification message to the electronic device. The second notification message indicates that the battery verification has failed. Upon receiving the second notification message, the electronic device can determine that the battery is unqualified, prohibit charging, and output a prompt message to the user interface: "Battery verification failed, please replace with an original battery."
[0108] S407, the security authentication module sends a first notification message to the electronic device. Correspondingly, the electronic device receives the first notification message from the security authentication module.
[0109] In this embodiment, after successfully storing the target count value, the security verification module can send a first notification message to the electronic device. The first notification message is used to indicate that the battery verification was successful.
[0110] Upon receiving the first notification message, the electronic device executes corresponding operational strategies based on the message, including but not limited to: allowing the device to power on normally, allowing the battery to charge, allowing the battery to provide full power, clearing the lock flag set due to previous verification failure, and outputting a fifth prompt message on the user interface, such as... Figure 5E As shown, the fifth prompt message could be "Original battery recognized".
[0111] For example, assume an initial count value of 0 and a preset step size of 1. The battery health in a user's electronic device deteriorates, and a new original battery is purchased and installed. In this original battery, in response to the safety verification module connecting to the electronic device, the safety verification module can send a verification notification to the battery protection board. In response to the verification notification, the battery protection board obtains the cell's identification identifier from the cell. If the cell's identification identifier is verified, it increments the current count value (which is the initial count value, i.e., the current count value is 0) by a preset step size to obtain a target count value of 1. The battery protection board sends this target count value to the safety verification module. The safety verification module, in response to the target count value being greater than or equal to the reference count value 0, stores the target calculated value and sends a first notification message to the electronic device. The first notification message indicates successful battery verification. After receiving the first notification message, the electronic device can normally identify the battery and allow it to charge and discharge. The electronic device can also output a "Original battery recognized" message on the user interface.
[0112] As can be seen, the verification method provided in this application combines cell identification verification with one-way counter increment verification, achieving dual safety authentication of the battery. This method can not only identify whether the cell is originally bound to the battery protection board, but also detect whether the one-way counter has been rolled back, thereby effectively preventing the battery protection board from being illegally disassembled and used with non-original cells, significantly improving the overall safety of the battery system.
[0113] In one possible implementation, the above Figure 2 The present invention provides a schematic diagram of a battery structure, wherein the battery 200 includes a safety verification module 210, a battery protection board 220, and a battery cell 230.
[0114] The battery protection board 220 includes a security unit 221, which includes a security chip 222, an encryption algorithm module 223, and a one-way counter 224. The battery cell 230 includes a one-time programmable chip 231.
[0115] The safety verification module 210 is used to send verification notification information to the battery protection board 220 in response to the safety verification module 210 being connected to the electronic device.
[0116] The battery protection board 220 is used to obtain the identity of the battery cell 230 from the battery cell 230 in response to the verification notification information, and if the identity of the battery cell 230 is verified, determine the target count value based on the current count value of the one-way counter 224; and send the target count value to the security verification module 210.
[0117] The security verification module 210 is also configured to, in response to a target count value being greater than or equal to a reference count value, store a target calculated value and send a first notification message to the electronic device, the first notification message being used to indicate that the battery verification was successful; wherein, the reference count value is the count value previously stored by the security verification module 210.
[0118] In one possible implementation, the battery protection board 220 can also be used to obtain the identity identifier of the battery cell 230 from the battery cell 230 through the hardware binding interface between the battery protection board 220 and the battery cell 230.
[0119] In one possible implementation, the battery cell 230 may include a one-time programmable chip 231, which is used to store the identification of the battery cell 230.
[0120] In one possible implementation, the battery protection board 220 can also be used to determine the initial identity of the battery cell 230 based on the binding key and the serial number of the battery protection board 220; in response to the initial identity being the same as the identity of the battery cell 230, it is determined that the identity of the battery cell 230 has been verified; wherein, the initial identity of the battery cell 230 is the identity set at the factory of the battery, and the binding key is obtained by encrypting the initial identity of the battery cell 230 and the serial number of the battery protection board 220.
[0121] In one possible implementation, the security verification module 210 described above can also be used to send a second notification message to the electronic device in response to the target count value being less than the reference count value. The second notification message is used to indicate that the battery verification has failed.
[0122] In one possible implementation, the battery protection board 220 can also be used to control the battery protection board 220 to be locked and send an identity acquisition failure message to the security verification module 210 when the identity of the battery cell 230 is not obtained from the battery cell 230; the security verification module 210 can also be used to send a third notification message to the electronic device in response to the identity acquisition failure message, the third notification message being used to indicate a battery abnormality.
[0123] In one possible implementation, the battery protection board 220 can also be used to send an identity verification failure message to the security verification module 210 if the identity of the battery cell 230 fails to be verified; the security verification module 210 can also be used to send a fourth notification message to the electronic device in response to the identity verification failure message, the fourth notification message being used to instruct the battery protection board 220 to refuse to work.
[0124] For a description of the technical effects of the battery and any of its possible implementations, please refer to the description of the technical effects of the foregoing method embodiments, which will not be repeated here.
[0125] According to the embodiments of this application, Figure 2 The individual units in the battery 200 shown can be individually or entirely combined into one or more other units, or some of the units can be further divided into multiple functionally smaller units. This achieves the same operation without affecting the technical effects of the embodiments of this application. The above units are based on logical function division. In practical applications, the function of one unit can also be implemented by multiple units, or the function of multiple units can be implemented by one unit.
[0126] This application also provides a computer device; please refer to [link / reference]. Figure 7 , Figure 7 This is a schematic diagram of the structure of a computer device provided in an embodiment of this application.
[0127] like Figure 7 As shown, the computer device 700 may include one or more processors 710, one or more memories 730, one or more communication interfaces 720, and a bus 740, wherein the processors 710, memories 730, and communication interfaces 720 are connected via the bus 740. The computer device may be the battery 200 described above.
[0128] The memory 730 is used to store a program; the processor 710 is used to execute the program stored in the memory. When the program is executed, the processor 710 performs the method in any possible implementation of the verification method described above.
[0129] It should be understood that, in the embodiments of this application, the memory 730 described above includes, but is not limited to, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), or compact disc read-only memory (CDROM), as well as external memory other than computer memory and processor cache. A portion of the memory 730 may also include non-volatile random access memory. For example, the memory 730 may also store device type information.
[0130] The processor 710 described above can be one or more central processing units (CPUs). If the processor 710 is a CPU, it can be a single-core CPU or a multi-core CPU. The processor 710 can also 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. A general-purpose processor can be a microprocessor or any conventional processor.
[0131] The steps performed in the foregoing embodiments can be based on the above. Figure 7 The computer device 700 shown is implemented such that the processor 710 can execute the implementation described in any optional embodiment of the verification method provided in this application, and can also execute the implementation of the battery 200 described in this application. The memory 730 can provide cache when the processor 710 executes the implementation of the battery 200 described in this application, and can also store the computer programs required by the processor 710 to execute the implementation of the battery 200 described in this application.
[0132] This application also provides a computer storage medium storing a computer program, the computer program including program instructions, which, when executed by a processor, enable the processor to implement the above-mentioned functions. Figure 4 or Figure 6 The method shown.
[0133] This application also provides a computer program product, which includes: instructions or a computer program; when the instructions or the computer program are executed, the above-mentioned functions can be achieved. Figure 4 or Figure 6 The method shown.
[0134] This application also provides a chip, which includes a processor. The processor executes instructions, enabling the chip to achieve the aforementioned... Figure 4 or Figure 6 The method shown.
[0135] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by hardware related to computer programs. The computer programs can be stored in computer storage media, and when executed, they can implement the processes of the above method embodiments. The aforementioned computer storage media include various media capable of storing computer program code, such as read-only memory (ROM) or random access memory (RAM), magnetic disks, or optical disks.
Claims
1. A verification method, characterized in that, The method is applied to a battery, the battery including a battery protection board, a battery cell, and a safety verification module, the safety verification module being used to connect an electronic device and the battery protection board, the battery protection board being connected to the battery cell; the method includes: In response to the security verification module being connected to the electronic device, the security verification module sends verification notification information to the battery protection board; In response to the verification notification information, the battery protection board obtains the identity identifier of the battery cell from the battery cell, and if the identity identifier of the battery cell is verified, determines a target count value based on the current count value of the one-way counter; and sends the target count value to the security verification module. In response to the target count value being greater than or equal to the reference count value, the security verification module stores the target calculated value and sends a first notification message to the electronic device. The first notification message is used to indicate that the battery verification is successful. The reference count value is the count value previously stored by the security verification module.
2. The method as described in claim 1, characterized in that, The step of obtaining the battery cell's identification identifier from the battery cell includes: The battery cell's identity is obtained from the battery cell through the hardware binding interface between the battery protection board and the battery cell.
3. The method as described in claim 1 or 2, characterized in that, The battery cell includes a one-time programmable chip, which is used to store the battery cell's identification identifier.
4. The method as described in claim 1, characterized in that, The method further includes: The battery protection board determines the initial identity of the battery cell based on the binding key and the serial number of the battery protection board; in response to the initial identity being the same as the identity of the battery cell, it is determined that the identity of the battery cell has been verified. The initial identification of the battery cell is the identification set at the factory of the battery, and the binding key is obtained by encrypting the initial identification of the battery cell and the serial number of the battery protection board.
5. The method as described in claim 1, characterized in that, The method further includes: In response to the target count value being less than the reference count value, the security verification module sends a second notification message to the electronic device, the second notification message indicating that the battery verification has failed.
6. The method as described in claim 1, characterized in that, The method further includes: If the battery cell's identity identifier is not obtained, the battery protection board is locked and an identity identifier acquisition failure message is sent to the security verification module. In response to the identity verification failure message, the security verification module sends a third notification message to the electronic device, which indicates that the battery is abnormal.
7. The method as described in claim 1, characterized in that, The method further includes: If the identity of the battery cell fails verification, an identity verification failure message is sent to the security verification module. In response to the identity verification failure message, the security verification module sends a fourth notification message to the electronic device, which instructs the battery protection board to refuse to work.
8. A battery, characterized in that, The battery includes a battery protection board, a battery cell, and a safety verification module. The safety verification module is used to connect an electronic device and the battery protection board, and the battery protection board is connected to the battery cell. The security verification module is used to send verification notification information to the battery protection board in response to the security verification module being connected to the electronic device; The battery protection board is used to respond to the verification notification information, obtain the identity identifier of the battery cell from the battery cell, and determine the target count value based on the current count value of the one-way counter if the identity identifier of the battery cell is verified. The target count value is sent to the security verification module; The security verification module is further configured to, in response to the target count value being greater than or equal to the reference count value, store the target calculated value and send a first notification message to the electronic device, wherein the first notification message is used to indicate that the battery verification is successful; wherein the reference count value is the count value previously stored by the security verification module.
9. A computer device, characterized in that, include: Memory, processor; where: The memory is used to store computer programs, the computer programs including program instructions; The processor is configured to invoke the program instructions to cause the computer device to perform the method as described in any one of claims 1-7.
10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by a processor, implements the method as described in any one of claims 1-7.