Replaceable battery apparatus and implementing method therefor
Patent Information
- Application Number
- PCT/CN2025/078763
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2025-02-24
- Publication Date
- 2026-08-27
Smart Images
Figure CN2025078763_27082026_PF_FP_ABST
Abstract
Description
REPLACEABLE BATTERY APPARATUS AND IMPLEMENTING METHOD THEREFORTECHNICAL FIELD
[0001] The present disclosure relates generally to batteries. More particularly, the present disclosure relates to a replaceable battery apparatus and a method for implementing the replaceable battery apparatus in devices powered therefrom.BACKGROUND
[0002] Rechargeable batteries have become the main power source for most smart or wearable devices, such as smartphones, headphones, smartwatches, etc. . Nowadays, however, most device batteries are non-swappable for users.
[0003] For the sustainability purpose, Europe released the European Battery Act in 2023. The Act requires that most of the battery-powered devices shall use replaceable batteries. It says in the Act that consumer replaceable batteries that come with commercially available tools shall be required for the products sold after Feb. 18, 2027.
[0004] Therefore, it is necessary to provide a solution for those devices to be able to recognize the legality of such replaceable batteries and to take relevant actions, in order to meet the requirements of replaceable batteries and ensure their safe usages and meet the product requirements.
[0005] SUMMARY OF THE DISCLOSURE
[0006] In order to overcome the shortcomings and deficiencies in the prior art, the purpose of the disclosure is to provide.
[0007] In one aspect, a replaceable battery apparatus is provided in the present disclosure provides. The replaceable battery apparatus may comprise a battery cell configured to charge from or discharge to a device, such as an electric device that can be powered by the battery cell of this replaceable battery device. A plurality of interfaces arranged therein may comprise at least one communication interface to be connected to and communicate with the device. The replaceable battery apparatus may further comprise a battery microcontroller unit (MCU) , which may be configured to communicate with the device, such as with one or more processors therein, through the at least one communication interface, and perform authentication with the device. In case that the authentication passes, the battery MCU may send battery information to the device, to charge or discharge the battery cell in necessary. The battery information may comprise, but not limited to, at least one of a nominal voltage, a battery capacity, a charge ending voltage, and battery temperature.
[0008] Further, the battery MCU in the rechargeable battery apparatus may be reset when triggering a reset circuit therein, by the device or by a user.
[0009] Further, the battery MCU in the rechargeable battery apparatus may be upgraded its firmware (FW) when receiving a new FW from the device, and then reboot after completing the FW upgrade.
[0010] Further, the battery MCU in the rechargeable battery apparatus may be enter to sleep mode and wake up periodically, to achieve low power consumption.
[0011] In another aspect, a method for implementing the replaceable battery apparatus, in a device that requires power supplied therefrom, is provided in the present disclosure. The method may comprise detecting the battery MCU being existed in the replaceable battery apparatus, and executing, by one or more processors, an authentication with the battery MCU. The method may further comprise, in case that the authentication passes, receiving the battery information, wherein the battery information comprises a battery max discharging current, setting the charging and discharging parameters, according to the battery information, and obtaining the battery temperature from the battery MCU. Otherwise, in case that the authentication fails, the method may comprise indicating to a user that the replaceable battery apparatus is informal.
[0012] Further, in case that the authentication fails, when the user chooses to continue to use the replaceable battery apparatus, the device may enable a local NTC in the device to get the battery temperature therefrom, wherein the battery cell may be charged with default charging parameters while the USB plug-in the device, and wherein the device works with basic functions and performance while discharging the battery cell. When the user chooses to stop using the replaceable battery apparatus, the device can be powered off.
[0013] Further, in case that the authentication passes, when discharging the battery cell, the device may work with downgraded or disabled functions, and indicate these downgraded or disabled functions to the user, when the battery max discharging current is lower than a device max working current. When the battery max discharging current is higher than the device max working current, the device works with full functions and performance.
[0014] Further, the device may send a reset signal to trigger the reset circuit to reset the battery MCU. The device may send a new FW to upgrade the battery MCU.
[0015] Otherwise, when the battery MCU is not populated on the IC board of the battery rechargeable apparatus, the device may still enable a batter NTC in the battery rechargeable apparatus, if there is, to obtain the battery temperature therefrom.BRIEF DESCRIPTION OF THE DRAWINGS
[0016] The present disclosure may be better understood from reading the following description of non-limiting embodiments, with reference to the attached drawings. In the figures, like reference numeral designates corresponding parts, wherein below:
[0017] FIG. 1A illustrates an exemplary schematic diagram of the replaceable battery apparatus, with the one-wire communication between the battery MCU and device, in accordance with one or more embodiments of the present disclosure;
[0018] FIG. 1B illustrates an exemplary schematic diagram of the replaceable battery apparatus, with the two-wire communication between the battery MCU and device, in accordance with one or more embodiments of the present disclosure;
[0019] FIG. 2 illustrates an exemplary main flowchart of the method for implementing the replaceable battery apparatus, in accordance with one or more embodiments of the present disclosure;
[0020] FIG. 3 illustrates an exemplary flowchart of the authentication of the replaceable battery apparatus, in accordance with one or more embodiments of the present disclosure;
[0021] FIG. 4 illustrates an exemplary flowchart for charging the replaceable battery apparatus, in accordance with one or more embodiments of the present disclosure;
[0022] FIG. 5 illustrates an exemplary flowchart for discharging the replaceable battery apparatus, in accordance with one or more embodiments of the present disclosure;
[0023] FIG. 6A illustrates an exemplary flowchart of the battery MCU operating, in a self-wake-up manner, after a successful authentication and the charging and discharging setting, in accordance with one or more embodiments of the present disclosure;
[0024] FIG. 6B illustrates an exemplary flowchart of the battery MCU operating, in a periodic waken-up manner by an interruption signal, after the successful authentication and the charging discharging setting, in accordance with one or more embodiments of the present disclosure;
[0025] FIG. 7 illustrates an exemplary flowchart of the battery MCU power off procedure, in accordance with one or more embodiments of the present disclosure;
[0026] FIG. 8 illustrates an exemplary flowchart of the battery MCU FW upgrade procedure, in accordance with one or more embodiments of the present disclosure;
[0027] FIG. 9A illustrates an exemplary schematic diagram of the battery MCU reset circuit triggered by manual, in accordance with one or more embodiments of the present disclosure; and
[0028] FIG. 9B illustrates an exemplary schematic diagram of the battery MCU reset circuit triggered by the device, accordance with one or more embodiments of the present disclosure.DETAILED DESCRIPTION
[0029] The detailed description of the one or more embodiments of the present disclosure is disclosed hereinafter; however, it is understood that the disclosed embodiments are merely exemplary of the disclosure that may be embodied in various and alternative forms. The figures are not necessarily to scale; some features may be exaggerated or minimized to show details of particular components. Therefore, specific structural and function details disclosed herein are not to be interpreted as limiting, but merely as a representative basis for teaching one skilled in the art to variously employ the present disclosure.
[0030] Different batteries have different parameters, such as power capacity, nominal voltage, end-of charge voltage, maximum charging current, maximum discharge current, trickle charging current, charging temperature and current requirements, discharge temperature, etc.. If the charging setting exceeds or falls below the battery parameters, there may be safety risks or the charging performance may deteriorate. For example, the end-of charge voltage of a product battery is 4.4V, and a third-party manufactured battery is 4.2V. When using this third-party manufactured battery in that product with a constant charging voltage of 4.4V, there may be charging risks, because the constant charging voltage is higher than that of the third-party manufactured battery.
[0031] In one replaceable battery design, the battery cell can be packaged in a plastic or metal housing. There may be a dedicated design on the housing to prevent the risk of using other batteries. It is easy to copy the mechanical design of the housing. This solution poses security risks.
[0032] In another replaceable battery design, in addition to a first pin for backup battery cell (VBAT) , a second pin for ground (GND) , a third pin for the Negative Temperature Coefficient (NTC) , there can be a fourth pin, which outputs a dedicated voltage level or voltage range. When the replaceable battery is installed in the device, the device may detect the fourth pin. If the voltage level or the voltage range thereon is correct, the device may confirm that the replaceable battery is the formal battery for the device. If not, the device shall consider it is an informal battery. The voltage level or the voltage range can be easily tested. This replaceable battery can be easily to replicate, and this solution poses security risks, either.
[0033] In yet another replaceable battery design, it may be encrypted through a battery protection IC integrated into the replaceable battery. Keys can be transmitted and received between the replaceable battery and the device. If the key is encrypted as correct, the device may confirm that the replaceable battery is the formal battery for the device. If not, the device may consider that the replaceable battery is an informal battery. The battery protection IC has the advantage of low power consumption. However, most battery protection ICs cannot provide the encryption function, and the device needs to follow the encryption algorithm embedded in the battery protection IC, which cannot be upgraded after it has been used in the battery.
[0034] In the disclosure, a battery MCU may be provided into a replaceable battery apparatus. The battery MCU may be equipped with a plurality of interfaces to connect with other components, to carry out various functions with the device. In addition to the VBAT, the GND, and the NTC pins, there may be one or more additional pins for the replaceable battery apparatus to interface with the device, allowing for more powerful communication between the battery MCU and the device. Moreover. A strong, flexible and effective encryption mechanism, a low power consumption design of the battery MCU, a charging and discharging design for a formal or informal battery, a battery MCU FW upgrade, and a battery MCU reset solution are all provided herein.
[0035] FIG. 1A illustrates an exemplary schematic diagram 100 of the replaceable battery apparatus, with the one-wire communication between the battery MCU and device, in accordance with one or more embodiments of the present disclosure. The replaceable battery apparatus may comprise several portions, including a battery cell 110, a battery MCU 120, a first battery protection IC 130, a second battery protection IC 140, a battery NTC 150, a reset circuit 160, and a plurality of interfaces through, such as, the four pins 170 shown in FIG. 1A.
[0036] For the one-wire communication used between the battery MCU and the device, the four pins 170 of the replaceable battery apparatus can be arranged as including the VBAT, a communication pin COM / NTC, a ground pin INT / NTC_GND, and the GND, as shown in FIG. 1A. Alternatively or additionally, if a two-wire communication is used, there may be five pins with one more communication pin added.
[0037] FIG. 1B illustrates an exemplary schematic diagram of the replaceable battery apparatus, with the two-wire communication between the MCU and device, in accordance with one or more embodiments of the present disclosure. Due to the two-wire communication used therein, there may be the five pins 170’ in the replaceable battery apparatus, including the VBAT, the COM1 / NTC, an additional COM2, the INT / NTC_GND and the GND. The one communication pin COM2 is added. Both the COM1 pin and the COM2 pin may implement the communication between the battery MCU and the device. In way of an example, such two-wire communication can be I2C or UART, etc..
[0038] As shown in FIGs. 1A and 1B, the VBAT pin is the battery power output pin. The COM / NTC pin in FIG. 1A, as well as both the COM1 / NTC pin and the COM2 pin in FIG. 1B, are the communication pins. The INT / NTC_GND pin is the interrupt pin to wake up the battery MCU or start communication from the device, for example. And, the GND pin is ground.
[0039] The battery MCU 120 may communicate with the device through the COM pin (s) . The communication can be in the one-wire communication (as shown in FIG. 1A) or in the two-wire communication (as shown in FIG. 1B) . To ensure the battery cell charge and discharge safely and properly, an authentication shall be done through the communication between the battery MCU 120 and the device. The battery MCU 120 may send the battery information to the device, such as the nominal voltage, the power capacity, the end-of charge voltage, the battery temperature, of the battery cell, while the device may send commands and / or data back to the battery MCU.
[0040] In the example shown in FIGs. 1A and 1B, two battery protection ICs may comprise the first battery protection IC 130 and the second battery protection IC 140, which may be both the logic ICs for monitoring and protecting the rechargeable battery apparatus from damaged by various abnormal conditions, such as overshooting, over-discharging, overcurrent, short circuit, overheating, and the like. By optimizing the battery protection ICs, the safety and performance of the battery can be significantly improved. In one or more embodiments, the first battery protection IC 130 and the second battery protection IC 140 can be used to improve the protection performance to meet the requirement of UL2054 (Standard for Household and Commercial Batteries) , to ensure that the rechargeable battery apparatus, especially the battery cell, can meet safety requirements during use and reduces risks such as fire, explosion or leakage.
[0041] The battery NTC 150 may be used for sensing the battery temperature. When the battery NTC 150 is connected to the battery MCU 120, the battery MCU 120 may read an NTC value and calculate the battery temperature. When the battery NTC 150 is connected to the device, the device may read the NTC value and calculate the battery temperature.
[0042] The battery MCU 120 can be reset through the reset circuit 160. The reset may be a manual reset, or the battery MCU 120 may be reset by triggering the reset circuit by the device.
[0043] As shown in FIGs. 1A and 1B, multiple resistors R1-R7 are also arranged around the battery MCU peripheral. These multiple resistors R1-R7 can be used for the replaceable battery compatibility design. In one or more embodiments, when the battery MCU 120 is provided in the replaceable battery apparatus with the one-wire communication applied between the battery MCU 120 and device, the battery NTC can be connected to a general ADC pin of the battery MCU 120, the resistors R1, R2, R5, and R6 may be populated, while the resistors R3 and R4 are not populated. The battery MCU 120 may read the NTC value to calculate the battery temperature. Alternatively or additionally, when the battery MCU 120 communicates with the device through the two-wire communication, the added COM2 pin shall be in use and the resister R7 is populated.
[0044] FIG. 2 illustrates an exemplary main flowchart 200 of the method for implementing the replaceable battery apparatus, in accordance with one or more embodiments of the present disclosure. When the device system is powered on by a power switch on or a USB plug in, for example, the device may start a battery authentication procedure, in step S210.
[0045] If the authentication fails, the device shall indicate an informal battery is installed, in step S220. There can be a lot of indication method, including but not limited to, a fast flashing red LED on the device, voice prompts from the device, messages on the smart phone, or the like. In step S230, if the user chooses to continue to use the informal battery, while the USB plug-in, the battery cell shall be charged with default charging parameters setting in step S232. If the user chooses to continue to use the informal battery in step S230, and the battery cell is discharging to the device, the device shall work with its basic functions and performance in step S234. If user chooses to stop using the informal battery while its USB is plugged-in, as shown with “No” in step S230, the device may stop charging the battery cell in step S236. If user chooses to stop using the informal battery and the battery cell is discharging in step S238, the device may power off automatically. As the battery NTC in the informal battery may not be used, there shall be a local NTC in the device. When the user chooses to continue to use the informal battery, the device may enable the local NTC in the device and obtain the temperature data from this local NTC, as described in steps S232 and S234.
[0046] If the authentication result is passed, in step S212, the device may get the battery information stored in the battery MCU. For, example, the battery information may include but not limited to the nominal voltage, the battery capacity, the end-of charge voltage, the battery temperature, the max battery discharge current and the like. The device then sets the charging and discharging parameters according to the battery information received from the battery MCU. In step S214, during charging or discharging the battery cell, the device may keep getting the battery temperature from the battery NTC. In an example, the battery MCU may send the battery temperature to the device when the battery temperature changes. Alternatively or additionally, the battery temperature may be sent from the battery MCU to the device upon request. Next, in step S216, when the device system is powered off, the battery MCU shall enter a sleep mode in step S218. The device system can be powered off when the device is powered off by such as the switch, or auto-power off, or the USB unplugged-in, for example.
[0047] As to the battery authentication procedure mentioned in the previous step S210, many appropriate algorithms can be used as the encryption algorithms, including various encryption algorithms such as signature encryption algorithms, digital signatures, etc., without limiting or predetermining the type of the encryption algorithm herein. The encryption algorithms can be changed or upgraded every time the FW is upgrading. As an example, the encryption method with differently defined data processing mechanism can be used herein.
[0048] FIG. 3 illustrates an exemplary flowchart 300 of the authentication of the replaceable battery apparatus, in accordance with one or more embodiments of the present disclosure. When the device system is powered on in step S310, or the device sends an interruption signal in step S312, to wake up the battery MCU in step S314, though its INT pin of the rechargeable battery apparatus, the device may generate a random number and save it in a local storage in step S316. The length of the random number can be defined. For example, a 4 bytes random number with Byte A, Byte B, Byte C and Byte D can be generated, where two bytes, such as Byte A and Byte B, of them are used for encryption, one byte, such as Byte C, for defining the encryption code shall be used in the battery MCU, and another one Byte D used for defining the encryption code shall be used in the device.
[0049] There can be many different encryption codes stored in the device. Byte D may decide which encryption code shall be used. For example, d0 ～ d3 bits are used for deciding which encryption code shall be used. Byte A and Byte B can be encrypted by those device encryption code with various methods. The logic XOR (exclusive or) can be used herein as an example.
[0050] Then, the device may send the random number to the battery MCU, in step S316, where Byte Ae and Byte Be after the encryption, as well as Byte C, may be sent to the battery MCU, respectively. After receiving the random numbers, the battery MCU may process them and send the processed data back to the device later, in step S318.
[0051] In this step S318, the battery MCU may encrypt the two Bytes Ae and Be into Bytes Aee and Bee, respectively. Then, the battery MCU may generate a random number, the length of which can be defined. For example, the battery MCU may generate a one-byte length random number named Byte F. The battery MCU may insert Byte F into Bytes Aee and Byte Bee. The another one-byte data Byte C in the random number received by the battery MCU defines the used encryption code and the position to where Byte F shall be inserted, as the encryption codes are saved in both the battery MCU and the device.
[0052] In particular, Byte Ae and Byte Be can be encrypted by the encryption code with various methods. For example, the logic XOR can be used herein, wherein Bit c0 to c3 of the Byte C may define what encryption code shall be used to encrypt Byte Ae and Byte Be, and Bit c4 and c5 define the position to where Byte F is inserted. Then, the battery MCU may send the data composed of Byte Aee, Byte Bee and Byte F back to the device.
[0053] Accordingly, in step S320, the device may further extract certain numbers therefrom, to compare the extracted numbers with the original random number to determine whether the rechargeable battery apparatus may act as a formal or not in the next step. In particular, upon the device receiving those data from the battery MCU, the device may find out the inserted data (Byte F) generated by the battery MCU according to the Bit c4 and c5 of Byte C, which is stored in the device. Then, the device may decrypt Byte Aee and Byte Bee with the encryption code defined by Bit c0 to c3 of Byte C. As the logic XOR is used in the encryption, the logic XOR shall be used in the decryption too. Then, Byte Aee and Byte Bee can be decrypted to Byte Ae1 and Byte Be1, respectively. Similarly, Byte Ae1 and Byte Be1 can be decrypted to Byte Ade and Byte Bde, respectively.
[0054] In step S322, the device thus may compare the decrypted data (Byte Ade and Byte Bde) with the original data (Byte A and Byte B) , except for the data (Byte C) used to select the encryption code and the insertion position in the battery MCU, and the data (Byte D) used to select the encryption code in the device. If Byte Ade and Byte Bde are the same with Byte A and Byte B, in step S324, the rechargeable battery apparatus can be determined as formal. Otherwise, if they are different in step S322, the rechargeable battery apparatus shall be determined as an informal in step S326. Then the device may indicate that an informal battery is installed in step S328, and the subsequent procedure of which can be described later in detail.
[0055] FIG. 4 illustrates an exemplary flowchart 400 for charging the replaceable battery apparatus, in accordance with one or more embodiments of the present disclosure. The battery MCU in the battery pack shall be powered by the battery cell. When the battery voltage is equal to or higher than the minimum work voltage of the battery MCU and the device system is in its off mode, the battery MCU is at sleep mode. In steps S410 and S412, the device system may be powered on when its USB is plugged in. The minimum work voltage of the battery MCU shall be smaller than the battery end-of discharge voltage. When the battery voltage is smaller than the minimum work voltage of the battery MCU in step S420, the battery cell shall be charged with default pre-charging parameters in step S422. The default pre-charging current is smaller than that of a formal battery for safety purpose. When the battery voltage is equal to or bigger than the minimum work voltage of the battery MCU, the battery MCU may be powered on in step S424.
[0056] After the battery MCU is waken up or powered on, the battery authentication shall start in step S430. If the authentication passes, the device shall get the battery information from the battery MCU and set accommodate charging parameters in step S432. The battery cell can be charged with the charging parameters as set above in step S434. Then, in step S436, the device may send a charging event notification to the battery MCU. The battery MCU shall record the battery capacity (Cs) at the beginning of charging in step S438. If charging ends in step S440, the device shall send a charge ending notification to the battery MCU in step S442. The battery MCU thus records the battery capacity (Ce) at the ending of charging in step S444. Then, in step S446, the battery MCU may calculate the charging cycle (Cyc) by Cyc + = (Ce-Cs) . The charging cycle reflects the SoH (State of Health) of the battery. And then, in step S448, the battery MCU enters its sleep mode.
[0057] In step S430, if the authentication fails, the device shall remind the user that an informal battery is installed in step S450, such as by a LED, or a voice prompt, or a message on the app in the user’s smart phone, for example. The device shall ask the user and then check that if the user wants to continue to use the informal battery in step S452. The device shall remind the user that the battery shall be charged with the default charging parameters for safety purpose in step S454, and the charging performance may not be promised if the informal battery is used, such as the full charging time, the fast charging, etc. . Otherwise the device may stop charging in step S456 when the user decides not to use the informal battery in step S452. The default charging parameter may be different from the charging parameters set for the formal battery for safety purpose. For example, the charging current and the end-of charge voltage may be smaller than normal. If the user agrees, the informal battery may be charged with such default parameters setting. Otherwise, if the user disagrees, the device shall stop charging in step. Moreover, there shall be a local NTC in the device as the battery NTC in the informal battery may not be used. When the user chooses continue to use the informal battery, the device may enable the local NTC in the device and get temperature data from this NTC, as described in step S454.
[0058] FIG. 5 illustrates an exemplary flowchart 500 for discharging the replaceable battery apparatus, in accordance with one or more embodiments of the present disclosure. As shown in FIG. 5, in steps S510 and S512, when the device is powered on by power switch on, for example, the battery MCU shall be waken up and the battery authentication starts in step S514. If the authentication passes in step S520, the device may get the battery information from the battery MCU in step S522. The device may set its functions that may consume a lot of current, according to the battery information in step S524. The device may further set the charging parameters at this moment. In the function setting, those functions can be upgraded, downgraded, enabled, or disabled. The formal batteries may have different capacities and maximum discharging currents. For the default formal battery of the device, the battery maximum discharging current shall be bigger than the maximum working current of the device. In step S530, if the maximum discharging current of the formal battery is bigger than the maximum working current of the device, the device can work with full functions and performance in step S532. If the maximum discharging current of the battery is equal to or smaller than the maximum working current of the device in step S532, the device may work with some of its functions downgraded or disabled to ensure safe working of the device and the replaceable battery apparatus, in step S534. If those functions of the device are downgraded or disabled, in step S536, the device shall remind the user that those functions are downgraded or disabled by such as a voice prompt, or a message on the application in the user’s smart phone, for example.
[0059] In step S520, if the authentication fails, the device may remind the user an informal battery is installed, in step S526 by such as a flashing LED, a voice prompt, or message on the application in the user’s smart phone, or the like. The device may ask the user and check if the user would continue to use the informal battery in step S540. The device shall remind the user that only basic functions and performance may be available if the informal battery is used for safety purpose in step S542, or the device may be auto-powered off in step S544. For example, the above reminding can be done via a voice prompt, a message on the application in the user’s smart phone, or the like. If the user agrees, the device may work with those basic functions and performance in step S542. If the user disagrees, the device may be auto-powered off in step S544. The user checking can be done by push the device button, or on the application in the smart phone, or else. As the batter NTC in the informal battery may not be useable, there shall be a local NTC in the device. If the user chooses continue to use the informal battery, the device may enable the local NTC in the device and get temperature data from this NTC. Such temperature data detected by the local NTC may also be considered as the battery temperature, for example.
[0060] Referring back to Fig. 2, after the authentication is passed, the device may request the battery information from the battery MCU. The device may also request further battery information in necessary. As an example, the device may check the current battery MCU FW version, before it starts a new FW upgrade.
[0061] The battery information stored in the battery MCU may comprise, but not limited to, the following items listed in the list below:
[0062] After the battery authentication is passed and the charging and discharging parameters and performance are set, the battery MCU may enter a sleep mode and periodically wake up to work, in order to maintain its low power consumption. There are two ways to perform such periodic operations.
[0063] FIG. 6A illustrates an exemplary flowchart 600 of the battery MCU operating, in a self-wake-up manner, after a successful authentication and the charging and discharging setting, in accordance with one or more embodiments of the present disclosure. In this way, the battery MCU may enter sleep and wake up by itself.
[0064] When the battery MCU is at sleep mode, in step S610, a wake-up timer may be set for the battery MCU. Depending on the battery MCU wake-up timer arrives, in step S620, the battery MCU may wake up in step S622. The battery MCU then may send messages to the device once it wakes up, such as the battery temperature, etc. . The battery MCU shall also receive commands or messages from the device when it is awake, as shown in step S624. As the battery MCU only works when it is awake, the battery MCU may not always response to the device on these commands or messages immediately in this way. It is possible to define the sleep and wake-up period of the battery MCU sleep and wake-up, such as on the apps via the user’s smartphone. To maintain the low power consumption, for example, this period can be set to approximately several hundred milliseconds to a few seconds, or even longer.
[0065] Before entering the next sleep mode, in step S626, the battery MCU may records the battery voltage level at that time. The number of the recorded battery voltage levels can be defined. The recorded battery voltage level can be checked in necessary. For example, when the battery being broken, the recorded battery voltage level can be checked to see how was the voltage level during the last period.
[0066] FIG. 6B illustrates an exemplary flowchart 600’ of the battery MCU operating, in a periodic waken-up manner by an interruption signal, after the successful authentication and the charging discharging setting, in accordance with one or more embodiments of the present disclosure. In this way, the device may send an interruption signal to the battery MCU to wake up the battery MCU periodically or in necessary.
[0067] After the battery passes the authentication and the charging parameters and discharging performance received from the device are set, the battery MCU may be in sleep mode in step S630 (this step may be the same as the step S610 of FIG. 5A) . When the device sends the interruption signal to the battery MCU in step S632 through the INT / NTC_GND pin, for example, the battery MCU can be waken up, and then the battery MCU may send messages to the device in step S634. The device may request the battery MCU for data, of the battery information, for example, such as the battery temperature, etc. in step S636. Next, the battery MCU may send the data to the device in step S638. The device may reply acknowledge characters (ACK) to the battery MCU in step S640. Then, the battery MCU may again enter the sleep mode later in step S644.
[0068] In one or more embodiments, the device may send the interruption signal to the battery MCU periodically. Thus the battery MCU and the device may both work in the way as above described procedure periodically. The battery MCU may response to the device on those commands or messages immediately in this way. It is possible to define the period of the interruption signal sent by the device, such as on the apps via the user’s smartphone. To maintain the low power consumption, the period can be set to approximately several hundred milliseconds to a few seconds, or even longer.
[0069] The battery MCU may record the battery voltage level at that time in step S642, before entering the next sleep mode in step S644. The number of the recorded battery voltage level can be defined. The recorded battery voltage level can be checked in necessary. For example, when the battery being broken, the recorded battery voltage level can be checked to see how was the voltage level during the last period.
[0070] FIG. 7 illustrates an exemplary flowchart 700 of the battery MCU power off procedure, in accordance with one or more embodiments of the present disclosure. The device in its switching off mode shall be in a non-working status for the user. For example, when the device is switched off and its USB is plugged in, the device may keep charging the battery cell, while the device is in switching off. At this state, the device system is working and performing the battery charging.
[0071] Once the device is switched off, or automatically switches off, from its working mode, or the USB thereof is unplugged in its switching off mode, the device may start its system switching off procedure in step S710. Accordingly, in step S712, when the device starts the system switching off procedure, the device shall send a power off command to the battery MCU in step S714. Upon receiving the power off command in step S716, the battery MCU may replies to the device that the command has been received, and then the battery MCU may enter a deep sleep mode in step S718.
[0072] FIG. 8 illustrates an exemplary flowchart 800 of the battery MCU FW upgrade procedure, in accordance with one or more embodiments of the present disclosure. The battery MCU FW needs to be able to be upgraded in several situations, such as updating the battery information, updating the authentication method or the authentication codes, or fixing some bugs, and the like. In one or more embodiments herein, the FW of the battery MCU in the replaceable battery apparatus can be upgraded by the device. The battery MCU FW upgrade method and procedure can be described as below.
[0073] As show in FIG. 8, in step S810, after the device waking up the battery MCU, the device may send a FW upgrade command to the battery MCU in step S812. The battery MCU may receive the command and then reply an ACK to the device in step S814. At this stage, the device may send the new FW to the battery MCU in step S816 frame by frame, while the battery MCU receives and check each frame and replies ACK to the device in step S818.
[0074] When the new FW transmitting completes, the device shall send a transmitting complete message to the battery MCU in step S820. The battery MCU may check the whole new FW. Accordingly, in step S822, if the FW check fails, the battery MCU may send a new FW error message to the device in step S824. The battery MCU FW upgrade thus fails and stops.
[0075] Otherwise, if the check is successful in step S822, the battery MCU shall send a ready to FW upgrade message to the device in step S828. When the message is received, the battery MCU my reply an ACK back to the battery MCU in step S830.
[0076] Then, the battery MCU may execute the FW upgrade in step S832. When the FW upgrade completes, the battery MCU shall reboot in step S834. At this stage, the battery MCU may send the message that the battery MCU upgrade is successful to the device in step S836. And after receiving the successful FW update message, the device shall close the battery FW upgrade procedure in step S838.
[0077] In one or more embodiments for implementing the replaceable battery apparatus provided herein, the battery MCU may need to reset for several purposes. In an example, when the battery MCU FW upgrade completes, the battery MCU shall reboot through its software reset, for example. In another example, when the battery MCU dumps, the battery MCU may need to be reset to restart it. The battery MCU may need to be reset for different purposes in various cases.
[0078] Except for the software reset, a reset circuit can be designed for the replaceable battery apparatus in this disclosure, which may trigger the battery MCU to be passively reset from outside of the battery rechargeable apparatus. There can be two ways to trigger the reset circuit.
[0079] The first way is to manually reset the battery MCU. FIG. 9A illustrates an exemplary schematic diagram 900 of the battery MCU reset circuit triggered by manual, in accordance with one or more embodiments of the present disclosure. The reset circuit mainly comprises a switch, such as a button S1, and several resistors and capacitors, such as R1 and C1, in FIG. 9A. The button S1 may be provided on the device and can be pressed by the user, to manually reset the battery MCU. For the manual reset, the battery MCU shall be reset when the user presses the button S1 for a period of time, for example. Normally, the reset circuit can be triggered by a low-level signal at an MCU reset pin MCU_RST of the batter MCU reset circuit. The ESD diode D1 may prevent Electrostatic Discharge (ESD) risks on the MCU_RST pin. Further, a low pass filter composed of the resistor R1 and the capacitor C1 may filter out the noise entering to the MCU_RST pin.
[0080] The second way to reset the battery MCU can be done by the device. FIG. 9B illustrates an exemplary schematic diagram 900’ of the battery MCU reset circuit triggered by the device, accordance with one or more embodiments of the present disclosure. The device may trigger the battery MCU to be reset through the INT / NTC_GND pin on the replaceable battery apparatus, as referring to FIGs. 1A and 1B. The reset signal and the interruption signal of the batter MCU may share the same pin. Normally, the interruption signal is a low-level pulse signal that lasts for about several milliseconds or shorter. In order to distinguish between the interruption signal and the reset signal, the reset signal shall be delayed for a period of time. The delay time can be longer than the duration of the interruption signal. The reset circuit can be arranged across the INT / NTC_GND pin and the MCU_RST pin to accomplish the delay. When the interruption signal is arrived at the INT / NTC_GND pin, its lasting time of the low-level signal shall be too short to pass though the reset circuit, so there shall be no change on the MCU_RST pin. Normally, the battery MCU can be reset when the MCU_RST pin is pulled down for the period of time. The lasting time of the low-level of the reset signal shall be longer than that of the interruption signal, and then, when the reset signal is on the INT / NTC_GND pin, the reset signal may go through the reset circuit and the MCU reset shall be triggered.
[0081] The reset circuit for the battery MCU triggered by the device can be shown in FIG. 8B. The reset circuit may be mainly composed of a P-channel MOSFET Q1, an N-channel MOSFET Q2, and several resistors and capacitors, such as R2, R3, R5 and C2. When the device sends the interruption signal to the battery MCU, the P-channel MOSFET Q1 shall be conducting for a period of time, which is the time duration reserved for the interruption signal. The capacitor C2 shall be charged through the resister R4 at the moment. Because the time duration of the interruption signal is too short to make the gate of the N-channel MOSFET Q2 to rise from the low voltage level to the threshold of the N-channel MOSFET Q2, the N-channel MOSFET Q2 cannot be switched on, and thus there shall be no change on the MCU_RST pin. Due to the possibility of the battery MCU waken up by the periodic interruption signal sent from the device, the cycle period of the interruption signal shall be set to intervals of about several hundred milliseconds to a few seconds, or longer. By selecting proper R4, R5, and C2, the N-channel MOSFET Q2 cannot be switched on by the periodic interruption signals, either.
[0082] While the signal on the INT / NTC_GND pin may stay low for a period of time and the period can be longer than the delay time Td, the P-channel MOSFE Q1 shall be switched on, and the capacitor C2 shall be charged to the voltage higher than the threshold of the N-channel MOSFTE Q2. Then the N-channel MOSFET Q2 can be switched on. the delay time Td depends on the value of R4 and C2. the delay time Td may increase as increasing of R4*C2. Then the signal on MCU_RST shall be pulled down.
[0083] While the signal on the MCU_RST pin may stay low for a period of time and the period can be longer than the reset triggering time Tt, the battery MCU shall be reset. The lasting time in the low-level for the reset signal shall be longer than that of the interruption signal. As an example, the low-level lasting time of the reset time Tr may comprise the delay time Td mentioned above and a reset triggering time Tt needed by the battery MCU.
[0084] In some products, it may be un-necessary to use the battery MCU in the replaceable battery apparatus, but an same IC board with similar protection circuit module (PCM) layout as the replaceable battery apparatus equipped with the battery MCU can be shared in these products. In one or more embodiments of the replaceable battery apparatus provided herein, a compatible design is provided to meet this requirement.
[0085] Referring to FIG. 1A or 1B, if the batter MCU is removed from the replaceable battery apparatus, and there shall still be the battery cell 110, the first and / or second protection ICs 120, 130, the battery NTC 150 and the multiple pins 170 therein. The battery NTC may be connected to the device, by changing the interface connection arrangements, allowing the device to read the battery temperatures.
[0086] For the 4-pin design of the replaceable battery apparatus shown in FIG. 1A, one pin of the battery NTC can be connected to the COM / NTC pin through the resistor R3, and the other pin of the battery NTC can be connected to the INT / NTC_GND pin through the resistor R4. In this case, the resistors R3 and R4 shall be populated, while the battery MCU, the resistors R1, R2, R5, and R6 may not be populated.
[0087] For 5-pin design of the replaceable battery apparatus shown in FIG. 1B, one pin of the battery NTC can be connected to the COM1 / NTC pin through the resistor R3, and the other pin of the battery NTC can be connected to the INT / NTC_GND pin through the resistor R4, and the resistors R3, R4 shall be populated, while the battery MCU, the resistors R1, R2, R5, R6 and R7 may not be populated.
[0088] In summary, the disclosure provides the rechargeable battery apparatus, wherein the battery MCU can be used for at least the battery encryption, and a strong, flexible, and effective encryption mechanism is also provided herein. The design of this battery MCU has low power consumption. The FW upgrade and reset design for this battery MCU is further provided.
[0089] In order to implement the rechargeable battery apparatus, the charging and discharging design with formal or informal batteries is further provided in the disclosure. In addition, a compatible design is provided to meet the requirement of batteries without MCU, such as a conventional battery.
[0090] Many benefits may be introduced herein by implementing this replaceable battery apparatus provided, where firstly the encryption method with differently defined data processing mechanism is provided for the battery certification, which can be defined based on such as random number and data processing mechanism. The random number can be used for encryption at each time, which may prevent data duplication problem, for example. Such an encryption method can be strong, flexible and effective. Under passed the battery certification, the battery MCU may provide a plurality of battery information to the device that may be powered by the rechargeable battery apparatus. The battery MCU may provide charging cycle to reflect the SoH of the battery. The battery MCU may record the battery voltage level, which can be checked in necessary, especially when malfunctions occur which may be related to the battery.
[0091] Alternatively or additionally, the charging and discharging design, not only for the formal but also for the informal battery, has been provided. Either the formal or the informal battery can be used safely with this design. Different formal batteries with various battery parameters can be used safely and properly, either.
[0092] The design of the battery MCU in the replaceable battery may wake up to work and enter sleep periodically to maintain the low power consumption.
[0093] With providing the battery MCU FW upgrade design and the battery MCU reset design, the battery MCU operation can be much more robust. The compatible design for the replaceable battery without MCU may further meet the requirement of the replaceable battery without encryption function, and the same PCM board for both types of the batteries can be achieved.
[0094] In the foregoing specification, the disclosure has been described with reference to specific embodiments thereof. It will, however, be evident that various modifications and changes may be made thereto without departing from the broader scope of the invention. For example, the above-described process flows are described with reference to a particular ordering of process actions. However, the ordering of many of the described process actions may be changed without affecting the scope or operation of the invention. The specification and drawings are, accordingly, to be regarded in an illustrative rather than restrictive sense.
[0095] Any combination of one or more computer-readable media may be used to perform the method provided in one and more embodiments of the present disclosure. The computer-readable medium may be a computer-readable signal medium or a computer-readable storage medium. The computer-readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples (non-exhaustive list) of the computer-readable storage medium may include, for example: an electrical connection with one or more wires, portable computer floppy disks, hard disks, random access memory (RAM) , read-read-only memory (ROM) , erasable programmable read only memory (EPROM or flash memory) , optical fibers, portable compact disc read only memory (CD-ROM) , optical storage devices, magnetic storage devices, or any suitable combinations of the foregoing. In the context of the disclosure, the computer-readable storage medium may be any tangible medium that can include or store a program for use by or in connection with an instruction execution system, apparatus, or device.
[0096] As used in the disclosure, an element or step listed in the singular form and preceded by the word “one / a” should be understood as not excluding a plurality of said elements or steps, unless such exception is specifically stated. Furthermore, references to “embodiments” or “examples” of the disclosure are not intended to be construed as exclusive, also including the existence of other embodiments of the recited features. The terms “first” , “second” , “third” , etc. are used only for identification and are not intended to emphasize a numerical requirement or positioning order of their objects.
[0097] References in the present disclosure to the replaceable battery apparatus and the method in the device to implement the replaceable battery apparatus may include the following content:
[0098] Item 1: In one or more embodiments, the present disclosure provides a replaceable battery apparatus, comprising:
[0099] a battery cell configured to charge from or discharge to a device,
[0100] at least one communication interface configured to communicate with the device; and
[0101] a battery microcontroller unit (MCU) configured to:
[0102] communicate with the device, through the at least one communication interface; and
[0103] perform authentication with the device.
[0104] wherein the battery MCU is further configured to:
[0105] send battery information to the device, in case that the authentication passes, wherein the battery information comprises at least one of a nominal voltage, a battery capacity, a charge ending voltage, and a battery temperature.
[0106] Item 2: The replaceable battery apparatus of item 1, wherein the at least one communication interface comprises a first communication interface, when the battery MCU is configured to communicate with the device through one-wire communication, and wherein the at least one communication interface further comprises a second communication interface, when the battery MCU is configured to communicate with the device through two-wire communication.
[0107] Item 3: The replaceable battery apparatus of item 1 or 2, wherein the battery MCU is further configured to receive charging parameters from the device, to charge the battery cell accordingly, wherein the battery MCU is further configured to record the battery capacity at both beginning and end of charging the battery cell, and wherein the battery MCU is further configured to enter the sleep mode, after the end of charging the battery cell, in case that the authentication passes.
[0108] Item 4: The replaceable battery apparatus of any of items 1 to 3, wherein the battery MCU is further configured to receive discharging parameters from the device, to discharge the battery cell accordingly, wherein the battery MCU is further configured to send the battery capacity and a maximum discharging current to the device in discharging the battery cell, and wherein the battery MCU is further configured to enter the sleep mode, after the end of discharging the battery cell, in case that the authentication passes.
[0109] Item 5: The replaceable battery apparatus of any of items 1 to 4, further comprising a battery negative temperature coefficient thermistor (NTC) configured to sense the battery temperature in the replaceable battery apparatus, wherein the battery temperature is read by the battery MCU to be sent the device as the battery information in case that the authentication passes, and wherein the device enables the battery NTC and gets the battery temperature therefrom in case that the authentication fails.
[0110] Item 6: The replaceable battery apparatus of any of items 1 to 5, further comprising at least one protection IC configured to improve protecting performance of the authentication.
[0111] Item 7: The replaceable battery apparatus of any of items 1 to 6, further comprising a reset circuit configured to reset the battery MCU.
[0112] Item 8: The replaceable battery apparatus of any of items 1 to 7, wherein the battery MCU is further configured to execute firmware (FW) upgrade upon receiving a new FW from the device, and then reboot after completing the FW upgrade.
[0113] Item 9: The replaceable battery apparatus of any of items 1 to 8, wherein the battery MCU is further configured to enter a sleep mode, in case that the authentication fails.
[0114] Item 10: in one or more embodiments, the present disclosure provides a method for implementing a replaceable battery apparatus of any of items 1-9, in a device that requires power supplied therefrom, comprising following steps:
[0115] detecting a battery microcontroller unit (MCU) existing in the replaceable battery apparatus;
[0116] executing, by one or more processors, an authentication with the battery MCU;
[0117] in case that the authentication passes:
[0118] receiving the battery information, wherein the battery information comprises a battery max discharging current;
[0119] setting the charging and discharging parameters, according to the battery information; and
[0120] obtaining the battery temperature from the battery MCU; and
[0121] in case that the authentication fails:
[0122] indicating to a user that the replaceable battery apparatus is informal.
[0123] Item 11: The method of item 10, further comprising: in case that the authentication fails,
[0124] when receiving an input from the user indicative of continuing to use the replaceable battery apparatus,
[0125] enabling a local NTC in the device to get the battery temperature therefrom, and
[0126] wherein the battery cell is charged with default charging parameters while the USB plug-in the device; and
[0127] wherein the device works with basic functions and performance while discharging the battery cell, and
[0128] when receiving the input from the user indicative of stopping using the replaceable battery apparatus,
[0129] powering off the device.
[0130] Item 12: The method of item 10 or 11, wherein in case that the authentication passes, when discharging the battery cell,
[0131] the device works with downgraded or disabled functions, and indicates, to the user, the downgraded or disabled functions, when the battery max discharging current is lower than a device max working current;
[0132] the device works with full functions and performance, when the battery max discharging current is higher than the device max working current.
[0133] Item 13: The method of any of items 10 to 12, further comprising sending a reset signal to trigger the reset circuit to reset the battery MCU by the device.
[0134] Item 14: The method of any of items 10 to 13, further comprising sending a new firmware (FW) to upgrade the battery MCU.
[0135] Item 15: The method of any of items 10 to 14, further comprising: enabling the batter NTC in the battery rechargeable apparatus to get the battery temperature therefrom, when the battery MCU is not populated on an IC board of the battery rechargeable apparatus.
Claims
1.A replaceable battery apparatus, comprising:a battery cell configured to charge from a device and discharge to the device; andat least one communication interface configured to communicate with the device;wherein the replaceable battery apparatus further comprises a battery microcontroller unit (MCU) configured to:communicate with the device, through the at least one communication interface; andperform authentication with the device; andwherein the battery MCU is further configured to:send battery information to the device, in case that the authentication passes, wherein the battery information comprises at least one of a nominal voltage, a battery capacity, a charge ending voltage, a battery max discharging current, and a battery temperature.2.The replaceable battery apparatus of claim 1, wherein the at least one communication interface comprises a first communication interface, when the battery MCU is configured to communicate with the device through one-wire communication, and wherein the at least one communication interface comprises the first communication interface and a second communication interface, when the battery MCU is configured to communicate with the device through two-wire communication.3.The replaceable battery apparatus of claim 1, wherein the battery MCU is further configured to receive charging parameters from the device, to charge the battery cell accordingly, wherein the battery MCU is further configured to record the battery capacity at both beginning and end of charging the battery cell, and wherein the battery MCU is further configured to enter a sleep mode, after the end of charging the battery cell, in case that the authentication passes.4.The replaceable battery apparatus of claim 1, wherein the battery MCU is further configured to receive discharging parameters from the device, to discharge the battery cell accordingly, wherein the battery MCU is further configured to send the battery capacity and the battery max discharging current to the device in discharging the battery cell, and wherein the battery MCU is further configured to enter a sleep mode, after the end of discharging the battery cell, in case that the authentication passes.5.The replaceable battery apparatus of claim 1, further comprising a battery negative temperature coefficient thermistor (NTC) configured to sense the battery temperature in the replaceable battery apparatus, wherein the battery temperature is read by the battery MCU to be sent to the device as the battery information in case that the authentication passes, and wherein the device enables the battery NTC and gets the battery temperature therefrom in case that the authentication fails.6.The replaceable battery apparatus of claim 4, further comprising at least one protection IC configured to improve protecting performance of the authentication.7.The replaceable battery apparatus of claim 1, further comprising a reset circuit configured to reset the battery MCU.8.The replaceable battery apparatus of claim 1, wherein the battery MCU is further configured to execute firmware (FW) upgrade upon receiving a new FW from the device, and then reboot after completing the FW upgrade.9.The replaceable battery apparatus of claim 1, wherein the battery MCU is further configured to enter a sleep mode, in case that the authentication fails.10.A method for implementing a replaceable battery apparatus of any of claims 1-9, in a device that requires power supplied therefrom, comprising following steps:detecting a battery microcontroller unit (MCU) existing in the replaceable battery apparatus;executing, by one or more processors, an authentication with the battery MCU;in case that the authentication passes:receiving the battery information, wherein the battery information comprises at least one of a nominal voltage, a battery capacity, a charge ending voltage, a battery max discharging current, and battery temperature;setting the charging and discharging parameters, according to the battery information; andobtaining the battery temperature from the battery MCU; andin case that the authentication fails:indicating to a user that the replaceable battery apparatus is informal.11.The method of claim 10, further comprising: in case that the authentication fails,when receiving an input from the user indicative of continuing to use the replaceable battery apparatus,enabling a local NTC in the device to get the battery temperature therefrom, andwherein the battery cell is charged with default charging parameters while the USB plug-in the device; andwherein the device works with basic functions and performance while discharging the battery cell, andwhen receiving the input from the user indicative of stopping using the replaceable battery apparatus,powering off the device.12.The method of claim 10, wherein in case that the authentication passes,when discharging the battery cell,the device works with downgraded or disabled functions, and indicates, to the user, the downgraded or disabled functions, when the battery max discharging current is lower than a device max working current;the device works with full functions and performance, when the battery max discharging current is higher than the device max working current.13.The method of claim 10, further comprising sending a reset signal to trigger the reset circuit to reset the battery MCU by the device.14.The method of claim 10, further comprising sending a new firmware (FW) to upgrade the battery MCU.15.The method of claim 10, further comprising: enabling the batter NTC in the battery rechargeable apparatus to get the battery temperature therefrom, when the battery MCU is not populated on an IC board of the battery rechargeable apparatus.