Large battery management system

Abstract

A battery system with a large lithium-ion battery powers auxiliary devices by discharging battery cells distributed among multiple battery packs. The discharge of the battery cells is effectively controlled while maintaining the expected lifespan of the lithium-ion battery cells. Each battery pack internally supports a battery management system and can have identical components, thus supporting easy scalability to higher power / energy architectures. Battery packs can be added or removed without interfering with the user, wherein one of the battery packs serves as the master battery pack and the remaining battery packs serve as slave battery packs. When the master battery pack is removed, one of the slave battery packs becomes the master battery pack. The master battery pack and the slave battery packs coordinate the charging and discharging of the battery cells via a communication channel such as a Controller Area Network (CAN) bus.

Description

Technical Field

[0001] The battery system includes multiple battery packs. Each battery pack includes a battery management system in which one battery pack is flexibly configured as a primary (e.g., a master) battery pack, while the other battery packs are configured as slave (e.g., secondary) battery packs.

[0002] The battery management systems and methods described herein can be implemented in industrial and commercial vehicle applications such as off-road multi-purpose vehicles, hybrid electric vehicles, battery electric vehicles, trucks / tractors, forklifts / pallet trucks, lawn and garden / outdoor power equipment, large mining equipment, automated guided vehicles, aerial work platforms, and others. Additionally, the systems and methods described herein can be implemented in other applications, including but not limited to wireless power tools (e.g., drills, saws, grinders, nail drivers, welding machines, etc.), aerospace / defense applications, appliances, and others. Furthermore, the systems and methods described herein can be implemented in other applications, including but not limited to grid energy storage, solar power storage systems, sustainable power storage systems, smart grid systems, telecommunications and data communication backup systems, unified power supply (UPS) systems, server applications, and others.

[0003] For example, in some industrial and commercial vehicle applications, battery management systems such as those disclosed herein may require a wide range of output currents, e.g., higher currents when the vehicle's engine is initially started, but lower currents during normal vehicle operation. In some embodiments, the battery management system and method may also include a limp-home mode feature as disclosed herein to accommodate a faulty battery in, for example, a large battery pack in an industrial or commercial vehicle application. Battery management systems including various battery pack configurations and one or more buses (e.g., CAN bus) can be integrated into industrial and commercial vehicle applications.

[0004] In another example, in some telecommunications and / or data communications backup systems and / or computer server applications, the battery management system disclosed herein, for instance, can provide an alternative to lead-acid battery installations that have previously dominated these applications due to their low cost, direct scalability, accessible recycling infrastructure, and accessible manufacturers. In some embodiments, the battery management system and methods disclosed herein offer high energy density, high discharge rate capability, and low self-discharge characteristics, which enable suitable integration into telecommunications and / or data communications backup systems, unified power supply (UPS) systems, and / or computer server applications. For example, the aforementioned applications desire longer operating times, which is made possible by battery management systems such as those disclosed herein, which extend the lifespan of batteries in a battery pack by implementing intelligent algorithms for charging, discharging, and balancing—such as intelligent converter balancing, initiating direct balancing, initiating staggered balancing, etc. Additionally, in some instances, the battery management system and methods disclosed herein can be used in conjunction with technologies such as fuel cells, supercapacitors, flywheels, and other electrochemical batteries used in telecommunications / data communications backup applications.

[0005] In yet another example, in some grid energy storage systems, solar power storage systems, sustainable power storage systems, smart grid systems, and / or unified power supply (UPS) systems, battery management systems such as those disclosed herein can optimize the power grid and make sustainable energy sources such as wind and solar more economical. In one example, the system can be used to store solar energy received from photovoltaic panels, and in some embodiments, the battery management system disclosed herein can be used to manage a bidirectional three-phase inverter system. Renewable energy storage systems can include multiple batteries in a battery pack integrated into a rack-mount chassis and enclosure. Solar integrators can use the disclosed battery management system and methods with large battery chemistry to meet the growing demand for renewable energy storage. While lead-acid, supercapacitors, sodium-sulfur, vanadium redox, flywheels, compressed air, fuel cells, and pumped water have been used in solar storage applications, solar integrators can conveniently utilize lithium-ion batteries for large-scale applications according to the disclosed battery management system and methods. Additionally, solar integrators may be expected to be used for ancillary services in the electricity market, using micropulses of energy to maintain the appropriate frequency of current on the grid, such as frequency regulation, and advanced smart grid functionality such as microgrid operation, demand response, time-shifting, and power dispatch. Compared to previous battery technologies, lithium chemistry offers advantages including lighter weight, smaller volume / footprint, longer cycle life, the ability to use lithium batteries with a larger percentage capacity without shortening rated cycle life, faster charging times, and lower effective capacity loss at high discharge rates. In some examples, inverter and gateway interoperability can be coupled to a disclosed battery management system to manage, distribute, and store energy within the smart grid. In some examples, the smart grid system can be housed in a scalable, mobile transport container.

[0006] Beyond grid-connected energy storage systems, the battery management systems and methods disclosed herein can be integrated with off-grid power products suitable for consumer, recreational, automotive, offshore, and / or industrial applications. In the automotive sector, auxiliary power units (APUs) can be used for transportation, construction, and / or maintenance of critical infrastructure. Battery APUs provide robust and reliable off-grid power for commercial vehicles. Other off-grid power applications include offshore power, remote location power, traffic regulations, security monitoring, and emergency generators. Furthermore, battery APUs can be used in short- and long-range trucks, construction equipment, off-road transport (e.g., logging trucks), and buses. For example, commercial trucks may rely on battery APUs for overnight comfort loads (e.g., air conditioning / heating / accessories). For several off-grid applications, reliability is a primary concern because the costs of failures and / or downtime are very high. Background Technology

[0007] Battery technology evolved from the early days of automation, when vehicle batteries were typically large, heavy-duty devices using lead-acid technology. Battery technology has progressed to deliver more energy in a smaller space. For example, lithium-ion (Li-ion) batteries are rapidly replacing conventional zinc-carbon and lead-acid batteries because they are smaller and lighter than traditional batteries and can retain up to three times the charge for longer than their bulky and heavy counterparts. Therefore, lithium-ion batteries are finding applications to power tools, appliances, and vehicles, including forklifts, cars, and trucks. Furthermore, battery technology is not stagnant. For example, new solid-state batteries, using glass electrolytes and lithium or sodium metal electrodes, offer approximately three times the energy density of lithium-ion batteries. However, in general, newer battery technologies can be damaged or degraded if the battery's sensitive chemistry is compromised. For instance, it is known that lithium-ion batteries can malfunction / degrade if overcharged or overcharged / over-discharged improperly.

[0008] Battery management systems (BMS) are sometimes included in new technology batteries (such as nickel-metal hydride or lithium-ion) to provide battery protection, improve efficiency, and offer a better user experience than previous battery technologies. Sometimes a battery management system is implemented to facilitate one or more objectives. For example, a BMS can be used to protect users of battery-powered applications. As another example, a BMS can be used to protect the battery pack itself from damage and abuse, as batteries are often an expensive investment. Furthermore, since batteries can be a costly investment, a BMS can be used to maximize the performance of the battery system. Even further, a BMS can be used to maximize the lifespan of the constituent battery cells. Summary of the Invention

[0009] A battery system may include multiple battery packs, which may have the same or similar electrical and electronic components and / or chemistry. Each battery pack may support battery cells (typically lithium-ion). The battery packs do not require specific configuration before being installed in the battery system. Instead, after the battery packs are inserted into the system and begin activity on the communication channel without user intervention, they can function as either a primary (e.g., a main) or secondary (e.g., a secondary) battery pack.

[0010] In another scenario, the battery system does not require an external battery management system. Instead, each battery pack may include an internal battery management system that manages the battery cells of the pack and can coordinate with other battery packs in the system via a communication channel through message transmission.

[0011] In another scenario, the main battery pack can collect battery status information from one or more slave battery packs via message transmission over a communication channel. Based on this status information, the main battery pack can appropriately enable / disable the charging or discharging of the battery cells located in the slave battery packs.

[0012] In another scenario, the configuration list can be sent from the master battery pack to the slave battery packs via a communication channel (e.g., a serial communication channel such as a Controller Area Network (CAN) bus), where the configuration list can include entries for each of the master and slave battery packs. The entry at the top position can be used as the master battery pack, while the other battery packs can be used as slave battery packs. When a battery pack is added or removed, the configuration list can be revised to reflect the change.

[0013] On the other hand, battery packs in a battery system can be charged and balanced to mitigate and / or prevent inrush currents that may occur in one or more of the multiple battery packs in the battery system when there are significant changes in the state of charge (SoC) between battery packs. For example, large SoC changes may occur when a new battery pack is installed in a battery system, such as when the SoC of the new battery pack differs significantly from that of the existing battery packs in the battery system (e.g., discharging vs. fully charging). Inrush currents may be particularly undesirable because the lifespan of lithium-ion batteries can be significantly shortened.

[0014] On the other hand, different battery pack balancing technologies are supported in the battery system. Based on the SoC characteristics of the battery pack, one of a variety of balancing technologies can be selected. Balancing technologies may include, for example, "smart converter balancing," "start direct balancing," and / or "start staggered balancing."

[0015] On the other hand, when the battery pack in the battery system experiences a catastrophic failure, such as when its battery cells are characterized by very low voltage output, the battery system can support a "limp-home mode." The internal battery management system can diagnose the failure and can mitigate it by configuring unused battery packs in the battery system (if available) or by initiating a partial shutdown of the battery system, enabling the device to operate at least partially powered until it "limp-home."

[0016] On the other hand, the battery system supports "smart discharge" to power the device (end device). A battery pack with varying SoCs can be connected to the end device to provide power. However, battery packs with large SoC variations cannot be immediately connected together to power the end device and may require charge balancing. Battery packs are then selectively activated from among the multiple battery packs in the battery system, allowing them to discharge appropriately.

[0017] On the other hand, the battery system supports "smart charging" to restore charging of its battery cells. A battery system with battery packs having varying System of Design (SoC) can be connected to a charger to restore the SoC of each battery pack and reduce SoC variability between battery packs. If a battery pack has large SoC variations, the battery packs cannot be connected to the charger simultaneously and immediately. Therefore, measures to avoid this situation are supported by enabling charging of selected battery packs at appropriate times based on dynamic SoC characteristics. Attached Figure Description

[0018] The foregoing description of the invention and the following detailed description of exemplary embodiments can be better understood when read in conjunction with the accompanying drawings, which are included as examples and not as limitations on the claimed invention.

[0019] Figure 1 A terminal device powered by multiple battery packs is shown according to an embodiment.

[0020] Figure 2A A battery pack with an internal battery management system (BMS) according to an embodiment is shown.

[0021] Figure 2B A battery pack with an internal battery management system (BMS) according to an embodiment is shown.

[0022] Figure 3 A flowchart illustrating the entire process of powering a terminal device with multiple battery packs according to an embodiment is shown.

[0023] Figure 4 An updated configuration list of multiple battery packs according to an embodiment is shown.

[0024] Figure 5 A flowchart for configuring multiple battery packs according to an embodiment is shown.

[0025] Figure 6A A general message flow scenario for configuring multiple battery packs is illustrated according to an embodiment.

[0026] Figure 6B A message flow scenario on a controller area network (CAN) bus for configuring multiple battery packs is illustrated according to an embodiment.

[0027] Figure 6C Another message flow scenario on a controller area network (CAN) bus for configuring multiple battery packs, according to an embodiment, is shown.

[0028] Figure 6D Another message flow scenario on a controller area network (CAN) bus for configuring multiple battery packs, according to an embodiment, is shown.

[0029] Figure 7A A flowchart for determining the balance type of multiple battery packs according to an embodiment is shown.

[0030] Figure 7B A flowchart is shown according to an embodiment for selecting one of three balance types for multiple battery packs.

[0031] Figure 7C A flowchart for determining the balance type of multiple battery packs according to an embodiment is shown.

[0032] Figure 8 A message flow scenario for determining the balance type of multiple battery packs is illustrated according to an embodiment.

[0033] Figure 9 A flowchart for converter balancing of multiple battery packs according to an embodiment is shown.

[0034] Figure 10 A message flow scenario for converter balancing of multiple battery packs is illustrated according to an embodiment.

[0035] Figure 11 A flowchart for directly balancing multiple battery packs according to an embodiment is shown.

[0036] Figure 12 A message flow scenario for directly balancing multiple battery packs according to an embodiment is shown.

[0037] Figure 13 A flowchart for cross-balancing multiple battery packs according to an embodiment is shown.

[0038] Figure 14 and Figure 15 A message flow scenario for interleaving and balancing multiple battery packs is illustrated according to an embodiment.

[0039] Figure 16 An example of charging multiple battery packs according to an embodiment is shown.

[0040] Figure 17 A flowchart for charging multiple battery packs according to an embodiment is shown.

[0041] Figure 18A A message flow scenario for charging multiple battery packs according to an embodiment is shown.

[0042] Figure 18B A message flow scenario for charging multiple battery packs according to an embodiment is shown.

[0043] Figure 18CA flowchart of a method for intelligently charging multiple battery packs according to an embodiment is shown.

[0044] Figure 19A Examples of multiple battery packs being discharged to power a terminal device according to an embodiment are shown.

[0045] Figure 19B Examples of multiple battery packs being discharged to power a terminal device according to an embodiment are shown.

[0046] Figure 20A A flowchart for discharging multiple battery packs according to an embodiment is shown.

[0047] Figure 20B A flowchart for discharging multiple battery packs according to an embodiment is shown.

[0048] Figure 21 A message flow scenario for discharging multiple battery packs according to an embodiment is shown.

[0049] Figure 22 This is a flowchart illustrating the operation of the limp home mode according to an embodiment.

[0050] Figure 23A A message stream scenario for limp home mode operation is illustrated according to an embodiment.

[0051] Figure 23B A message stream scenario for limp home mode operation is illustrated according to an embodiment. Detailed Implementation

[0052] According to one aspect of the embodiments, a battery system having a large battery (e.g., a lithium-ion battery) powers an auxiliary device (terminal device) by discharging battery cells distributed in multiple battery packs. The discharge of the battery cells is controlled in an efficient manner while maintaining the expected lifespan of the lithium-ion battery cells.

[0053] According to another aspect of the embodiments, the battery system can support different advanced technology batteries with different chemical substances and / or structures, including but not limited to lithium-ion batteries and solid-state batteries.

[0054] Each battery pack internally supports a Battery Management System (BMS), thus eliminating the need for external battery management compared to traditional methods. Furthermore, each battery pack can have identical electrical and electronic components, supporting an architecture that can easily scale to higher power / energy output as needed by the end device. Battery packs can be added or removed individually, with one pack serving as the master and the remaining packs as slaves. Moreover, battery pack configuration can be performed automatically without user interaction. When the master pack is removed, one of the slave packs is automatically reconfigured to become the master. The master (e.g., primary) and slave (e.g., secondary) packs coordinate the charging and discharging of the battery cells via a communication channel such as a Controller Area Controller (CAN) bus.

[0055] In addition, the battery system can be effectively charged to restore the charging of the battery cells while maintaining the expected lifespan of the battery cells.

[0056] Rechargeable medium to large battery packs with battery management systems power small portable devices and extend to larger mobile and stationary applications. Furthermore, rechargeable batteries can be considered to expand smaller applications, such as small motorcycles, into larger transportation applications, such as full-size cars. Industrial applications are also under consideration, as battery-based designs are replacing small internal combustion engines in commercial and consumer products used in lawnmowers and patio equipment. Electrification offers several advantages, including, but not limited to, eliminating pollution emissions, reducing noise, and reducing maintenance needs. Additionally, independent backup power systems for residential and commercial sites benefit from battery-based designs, eliminating the problems associated with on-site hydrocarbon-based fuel storage.

[0057] Figure 1 A terminal device 101 according to an embodiment is shown, which is powered by a plurality of battery packs 100 (battery systems). Each battery pack 102, 103, and 104 includes its own internal battery management system (BMS) 112, 113, and 114, respectively. Battery packs 102, 103, and 104 are electrically connected to a direct current (DC) power bus 151 (including positive and negative connections) such that the voltage presented to the terminal device 101 is substantially the same as the voltage provided by each battery pack 102, 103, and 104, while the current provided to the terminal device 101 is the sum of the individual currents provided by each battery pack. The battery packs 100 may be housed within the terminal device 101, mounted to the terminal device 101, or located externally relative to the terminal device 101.

[0058] Terminal equipment 101 can be of different types, including but not limited to power tools, lawnmowers, gardening tools, implements and vehicles including forklifts, cars, trucks, etc.

[0059] Battery management systems 112, 113, and 114 communicate with all battery packs and terminal devices 101 and / or chargers 1601 via communication channel 152 (e.g., ...). Figure 16 (As shown). For example, communication channel 152 may include a serial communication channel (e.g., a controller area network (CAN) bus) or a parallel communication bus. However, embodiments may support other types of communication channels, such as Ethernet, Industrial Ethernet, etc. 2 C. Microwire or Bluetooth Low Energy (BLE). In some cases, the communication channel can support synchronous communication (e.g., CAN) or asynchronous communication (e.g., RS-232, RS-422, RS-485, etc.).

[0060] CAN and Ethernet protocols support the lower two layers of the OSI model, while the BLE protocol spans both lower layers and higher layers, including the application layer. Therefore, implementations utilizing protocols such as CAN and Ethernet must support equivalent higher layers through software applications built on top of the two lower layers.

[0061] Implementation examples can support different messaging protocols. For example, a protocol can support node-to-node communication by supporting source and destination addresses. The destination address can specify a particular node address or can be a global address, allowing messages to be broadcast to more than one node. In some cases, protocols (such as CAN, Modbus, etc.) can support only a single source address (e.g., a master address), enabling all nodes to process messages broadcast over the communication channel.

[0062] Battery packs 102, 103, and 104 can each be connected in parallel to communication channel 152. However, embodiments can support different arrangements, such as group-to-group communication on a separate bus or daisy-chaining of each battery pack.

[0063] Battery packs 102, 103, and 104 may have similar or identical electrical and electronic components. After being inserted into the battery system, one of battery packs 102, 103, or 104 can be configured as a master or slave battery pack. Furthermore, if a battery pack is initially used as a slave battery pack, it can subsequently be used as a new master battery pack if the current master battery pack is removed.

[0064] Figure 2A A battery pack 200 with an internal battery management system (BMS) according to an embodiment is shown. The battery management system may be implemented by a processor 201 (which may include one or more microprocessors, controllers, microcontrollers, computing devices, and / or the like) to execute computer-executable instructions stored at a storage device 202.

[0065] As will be discussed, the battery pack 200 can be configured as a main battery pack or a secondary battery pack without any changes to the electrical or electronic components.

[0066] As will be discussed, when the battery pack 200 is discharging, charging and / or balancing relative to other battery packs, the power supply circuitry of the battery pack 200 (including battery cells 203) interacts with the power bus 151 via the power bus interface circuitry 206.

[0067] The battery pack 200 also interacts with the communication channel 152 via the communication channel interface circuit 205. For example, the battery pack 200 can support message transmission with other configured battery packs, battery-powered terminal devices, or chargers that charge battery cells 203. Figures 6A to 6B , Figure 8 , Figure 10 , Figure 12 , Figure 14 , Figure 15 , Figures 18A to 18B , Figure 21 and Figures 23A to 23B An exemplary message flow is shown, as will be discussed in further detail.

[0068] The battery pack 200 supports core battery monitoring and / or management functions via core battery function circuitry 204. For example, core battery functions may include battery cell status, battery cell balancing, short-circuit protection, high-temperature cutoff, overcurrent cutoff, and overcharge protection.

[0069] refer to Figure 2A Battery cell 203 may include multiple battery cells connected in series to achieve a desired voltage level. For example, for lithium-ion technology, each battery cell may have a nominal voltage of approximately 3.6 volts. In the case of four battery cells connected in series, the total nominal voltage provided by battery pack 200 is approximately 14.4 volts. When battery cell 203 includes multiple battery cells, core battery function circuitry 204 can internally balance the charge between the different battery cells. Additionally, battery pack 200 can perform charge balancing relative to other battery packs in the battery system. Battery packs are typically configured in parallel such that the combined current supplied to the end device is the sum of the currents in the battery pack at approximately the voltage levels of the individual battery packs.

[0070] Status information may include battery cell and / or battery pack state of charge (SoC) information, state of health (SoH) information, temperature information, charging time information, discharging time information and / or capacity information.

[0071] Those skilled in the art will understand that SoC is understood as the charge level of a battery relative to its capacity. SoC is typically measured in percentage points (0% = empty; 100% = full).

[0072] SoH (Solar Hours) does not typically correspond to a specific physical mass because there is generally no consensus in industry on how to determine SoH. However, SoH is derived from factors such as internal resistance, battery storage capacity, battery output voltage, number of charge-discharge cycles, cell temperature during previous use, total energy of charge or discharge, and / or cell lifespan. Knowing the SoH of the cells in a battery pack of 200 and the SoH threshold for a given end device (application) can help determine whether current battery conditions are suitable for the application and estimate the useful life of the battery pack for that application.

[0073] When performing processes associated with battery management, battery pack 200 may receive or send at least SoC and / or SoH values ​​to other battery packs, as will be discussed in further detail.

[0074] The power bus interface circuit 206 may include switching circuitry, such as semiconductor array 210 (e.g., a MOSFET array or other power semiconductor switching devices such as an insulated-gate bipolar transistor (IGBT) array, a thyristor array, etc.) and semiconductor array 211. Semiconductor array 210 allows current to flow out of battery pack 200 when battery pack 200 is discharging, and semiconductor array 211 allows current to flow into battery pack 200 when battery pack 200 is charging. Arrays 210 and 211 are appropriately enabled by processor 201 in response to message transmission from the main battery pack controller. (In the case where the battery pack is the main battery pack, message transmission occurs internally within battery pack 200, rather than via communication channel 152.) Power MOSFET arrays (e.g., N-channel MOSFETs) may be used as switches to control the power flow into and out of the battery cells. The gates of the MOSFET arrays may be controlled by signals generated by a microcontroller and / or a battery management IC.

[0075] The power bus interface circuit 206 can be configured to prevent the battery pack 200 from charging or discharging via the power bus 206 based on the state of the battery cells 203 (e.g., SoC, SOH, and / or voltage). Typically, arrays 210 and 211 are disabled when the battery pack is inserted into the battery system, so that the battery pack is not charged or discharged until commanded and / or controlled by the main battery pack.

[0076] Battery pack 200 interacts with power bus 151 via electrical switch 208 (which may include one or more semiconductor devices). As shown in FIG2, direct exposure to power bus 151 bypasses converter 207. However, if battery cells are charged when they have small SoCs, the cells may cause current inrush, which often leads to damage or degradation. Therefore, when the battery management system detects this condition, electrical switch 208 can be configured to control the charging of battery pack 200 to minimize the inrush current from power bus 151 via converter 207.

[0077] Converter 207 can take different forms capable of controlling power transfer between the power bus and the battery pack, such as by providing an output voltage that gradually decreases relative to the input voltage (e.g., buck converter, UK converter, buck-boost converter, single-ended primary inductor converter (SEPIC), etc.) to protect battery cell 203 from current inrush and enable battery cell 203 to charge slowly (e.g., corresponding to...). Figure 9 The converter balancing flowchart 713 is shown. However, when converter 207 is bypassed, battery cell 203 can be charged at a faster rate (e.g., corresponding to...). Figure 11 The direct balancing flowchart shown in Figure 714).

[0078] Processor 201 can support the battery management process discussed in this paper (e.g., respectively as follows) Figure 5 , Figure 7A , Figure 9 , Figure 11 , Figure 13 , Figure 17 Figure 20 and Figure 22 The processes shown are 500, 700, 713, 714, 715, 1700, 2000, and 2200. Processor 201 can control the overall operation of battery pack 200 and its associated components. Processor 201 can access and execute computer-readable instructions from storage device 202, which can take the form of various computer-readable media. For example, computer-readable media can be any available medium accessible by processor 201, and can include volatile and non-volatile media, as well as removable and non-removable media. By way of example and not limitation, computer-readable media can include a combination of computer storage media and communication media.

[0079] Computer storage media can include volatile and non-volatile media, as well as removable and non-removable media, implemented using any method or technology for storing information such as computer-readable instructions, data structures, program modules, or other data. Computer storage media includes, but is not limited to, random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other storage technologies, CD-ROM, digital versatile optical disc (DVD) or other optical disc storage, magnetic tape cassettes, magnetic tape, disk storage or other magnetic storage devices, or any other medium that can be used to store desired information and is accessible by a computing device.

[0080] Communication media can include computer-readable instructions, data structures, program modules, or other data in modulated data signals, such as carrier waves or other transmission mechanisms, and include any information transmission medium. A modulated data signal can be a signal whose one or more characteristics are set or altered in a manner that encodes information within the signal. By way of example, and not limitation, communication media can include wired media such as wired networks or direct-line connections, and wireless media such as acoustic media, RF media, infrared media, etc.

[0081] Although the processor 201 and the communication channel interface circuitry 205 can be powered by the battery cell 203, embodiments may have separate power supplies for the processor 201 and the interface circuitry 205. Therefore, the battery pack 200 can continue to interact with other battery packs via the communication channel, regardless of the state of the battery cell 203.

[0082] Figure 2B It shows Figure 2A The battery pack 200 shown is a variation. Battery cell 210 interacts with the power bus via power bus connector 214, switch 217, converter 218, and connector 219. Switch 217 may include two sets (arrays) of semiconductor devices (e.g., MOSFETs, IGBTs, thyristors, etc.) to allow current to flow in either direction (inflow into the battery pack for charging, outflow from the battery pack for discharging). Both arrays can be disabled to isolate the battery pack from the power bus. Typically, both arrays are disabled when the battery pack is inserted into the battery system. Additionally, the enabled converter 218 can be used to reduce the input voltage level to control the charging of the battery cells, thereby preventing current inrushes that may occur in some cases discussed later.

[0083] The controller 213 executes computer-executable instructions to perform the processes discussed herein. For example, the controller 213 acquires status information (e.g., SoC value) from the battery cell 210 via the battery monitor 211, provides battery pack status information via the status display 215, and interacts with a communication channel (e.g., CAN bus) via the communication bus interface 216.

[0084] In addition, the heater control circuit 212 can be used to ensure that the temperature of the battery cell 210 does not drop below a minimum value, so that the battery cell 210 can operate properly as expected.

[0085] Figure 3 This illustrates the use of multiple battery packs (e.g., battery pack 100) to power a terminal device (e.g., such as...) according to an embodiment. Figure 1 The flowchart 300 shows the entire process of powering the terminal device 101.

[0086] At box 301, terminal device 101 is activated. For example, a user can close the battery compartment of terminal device 101, turn a key and / or toggle a switch to generate an interlock signal.

[0087] At box 302, when the battery compartment has more than two battery packs, the main battery pack's battery management system determines whether to balance the battery packs. If so, at box 303, the charge difference between the battery packs can be reduced by discharging one or more battery packs to charge one or more other battery packs, as will be discussed in further detail.

[0088] After balancing (if necessary), at box 304, the end device is powered by discharging one or more battery packs. For example, based on the end device's power requirements and the battery pack's SoC value, the main battery pack's battery management system can enable the appropriate battery pack.

[0089] If a catastrophic failure is detected in one of the enabled battery packs at box 305 while powering the terminal device, limp home mode can be initiated at box 306 to continue powering the terminal device, as will be discussed in further detail.

[0090] When the user finishes using the terminal device at box 307, it is determined at box 308 whether charging is required. If so, the charger can be connected to the battery system to restore the battery cells, where charging can be initiated at box 309.

[0091] Although not explicitly shown, battery balancing can be performed at box 308 before charging the battery pack when the SoC values ​​of the battery packs are sufficiently different.

[0092] In these embodiments, all the multiple battery packs may have the same electrical and electronic components. Typically, no configuration is required when the battery packs are installed in the battery system. Instead, after the battery packs are inserted into the system and begin activity on the communication channel, they assume the role of either a master or slave battery pack based on the process discussed herein. As will be discussed in further detail, a configuration list, including entries for each of the master and slave battery packs, can be transmitted via the communication channel.

[0093] The processes discussed in this article are shown from the perspective of the main battery pack and are typically performed by the main battery pack in a battery system. Other battery packs installed in the battery system act as slave battery packs. However, slave battery packs interact with the main battery pack via communication channels. For example, a slave battery pack provides its cell status information and activates / deactivates a power switch in response to message transmissions from the main battery pack to interact with the power bus (e.g., allowing current (charge) to flow into or out of the battery pack). Therefore, although not explicitly shown, there are corresponding processes performed by each of the slave battery packs.

[0094] Figure 4 The diagram illustrates the updates to configuration lists 401a, 401b, 401c, and 401d for multiple battery packs as they are inserted into and removed from the battery system. Each battery pack is assigned an identifier (ID) according to a standardized process, such as the SAE J1939 address declaration process and / or similar procedures. For example, configuration list 401a contains four entries: battery pack 1 (configured as the primary battery pack) and three secondary battery packs (battery packs 2 through 4).

[0095] As will be discussed in more detail, the main battery pack collects status information about other battery packs (slave battery packs) and thus commands the slave battery packs, as well as itself, to discharge or charge in response to operating conditions.

[0096] exist Figure 4 In the illustrated embodiment, the first (top) member of configuration lists 401a, 401b, 401c, and 401d is configured as the main battery pack. When a battery pack is added to the battery system, an entry for that battery pack is created at the bottom of the configuration list. Therefore, the oldest member of configuration lists 401a, 401b, 401c, and 401d is configured as the main battery pack.

[0097] Choosing the oldest (top) member of configuration list 401c may be advantageous over traditional methods. For example, regarding determining the main battery pack based on its ID value, this could reduce the number of times the main battery pack is changed. Using the latter approach, a second change would occur from configuration list 401d, where battery pack 5 would become the main battery pack.

[0098] exist Figure 4In the installation scenario shown, battery pack 1 (which serves as the primary battery pack) is removed, as shown in configuration list 401b. Therefore, battery pack 2 (the oldest slave battery pack) becomes the new primary battery pack, as shown in configuration list 401c. To complete the transition, battery pack 2 can request battery pack information from other battery packs so that it can appropriately command the other battery packs.

[0099] Subsequently, battery pack 5 is inserted into the battery system, causing a new entry to be added to configuration list 401d, where ID 243 is the same as the ID of the previously removed battery pack 1. Figure 4 In the embodiment shown, battery pack 5 can be an old main battery pack that has been reinserted or a new battery pack that has been inserted into the battery system.

[0100] In some embodiments, battery pack information may be lost when the battery pack is removed from the battery system. When the battery pack is reinserted, the reinserted battery pack can retrieve the battery information from the configured battery pack. However, some embodiments may support memory persistence (e.g., flash memory) so that the battery pack information is retained at the battery pack even when the battery pack is removed and reinserted.

[0101] Figure 5 A flowchart 500 for configuring multiple battery packs according to an embodiment is shown. At block 501, a battery pack is added to the battery system. If no other battery pack is connected to the communication channel, as determined at block 502, an entry is added to the top of the configuration list, and at block 504, the battery pack becomes the primary battery pack. Otherwise, at block 503, the added battery pack is added to the bottom of the configuration list and becomes a secondary battery pack.

[0102] At box 504, the battery pack is removed from the secondary battery system. If it is determined at box 505 that the battery pack is the first member of the configuration list, then the entry is removed at box 506, and the battery pack corresponding to the next entry is designated as the primary battery pack at box 507. Otherwise, the entry for the removed battery pack is deleted at box 508.

[0103] Figure 6A It shows the method for using according to Figure 5 The flowchart shown configures a common message flow scenario for multiple battery packs. Common messages represent messages supported by different communication channels, such as Controller Area Network (CAN) bus, Ethernet, Industrial Ethernet, MODBUS, or Bluetooth Low Energy (BLE) and / or similar.

[0104] Figure 6A The message flow in the system is based on a centralized approach, where the main battery pack maintains a configuration list and repeatedly (e.g., periodically) sends it to other battery packs via a communication channel. However, embodiments (e.g., such as...) Figure 6D(As shown) can support a distributed approach, where each battery pack locally maintains its own configuration list and repeatedly broadcasts it on the communication channel. Because a battery pack receives all broadcasts from other battery packs, it can modify its own configuration list to be consistent with the configuration lists broadcast by other battery packs.

[0105] When battery pack 601 (battery pack 1) becomes the master battery pack at event 631, battery pack 601 sends periodic update messages 661a, 661b, and 661c to battery packs 602, 603, and 604, respectively. If the messaging protocol supports a single broadcast message (e.g., with a global destination address) that can be received and processed by all battery packs connected to the communication channel, battery pack 601 sends only one message. Otherwise, battery pack 601 sends separate messages to battery packs 602, 603, and 604 (which are configured as slave battery packs).

[0106] In some embodiments, messages 661a, 661b, and 661c may be sent repeatedly but not periodically.

[0107] Periodic update messages 661a, 661b, and 661c can contain configuration information (e.g., ... Figure 4 The configuration lists 401a, 401b, 401c, and 401d are shown. In some embodiments, the battery pack 601 periodically sends broadcast messages. However, if the battery pack 601 is removed (e.g., corresponding to event 632), the periodic transmission of update messages will be interrupted.

[0108] When the oldest slave battery pack (battery pack 602) detects an interruption at event 633, battery pack 602 assumes the role of the master battery pack. Therefore, battery pack 602 removes the top entry from the configuration list (corresponding to battery pack 601) and periodically sends a revised configuration list via update messages 662a, 662b.

[0109] When battery pack 605 (battery pack 5) is added at event 634, battery pack 605 sends an add request 663 according to the SAE J1939 address declaration procedure. Therefore, battery pack 605 is added by battery pack 602 (currently the main battery pack) at event 635, and battery pack 602 periodically sends update messages 664a, 664b, 664c and update messages 665a, 665b, 665c.

[0110] Figure 6B A message flow scenario on a CAN bus for configuring multiple battery packs is illustrated according to an embodiment.

[0111] The CAN communication protocol (ISO-11898:2003) describes how information is transmitted between devices on a network and conforms to the Open Systems Interconnection (OSI) model defined by layers. The actual communication between devices connected by a physical medium is defined by the physical layer of the model. The ISO 11898 architecture defines the lowest two layers of the seven-layer OSI / ISO model, called the data link layer and the physical layer.

[0112] The CAN communication protocol supports a standard version (11-bit identifier field) and an extended version (29-bit identifier field). However, implementations typically use the standard version because the supported identifier space is usually large enough.

[0113] The CAN bus is often referred to as a broadcast bus, where each message contains a source address (e.g., device ID) instead of a destination address. Therefore, all battery packs (corresponding to nodes) can "hear" all transmissions. Battery packs can selectively ignore messages, or they can process messages by providing local filtering, allowing each battery pack to respond to relevant messages.

[0114] The implementation can use data frame messages as defined in the CAN protocol. This message type carries a payload of 0-8 bytes, where data fields (typically executed by a software application at the battery pack) are interpreted at a higher protocol layer. For example, when sending status information from the battery pack back to the main battery pack, the data fields can convey SoC and / or SoH information.

[0115] To assign identification values ​​(addresses) to battery packs, terminal devices, or chargers, implementations can use industry standards such as the SAE J1939 address declaration process. The SAE J1939 protocol is a higher protocol layer built on top of the CAN data link and physical layer.

[0116] refer to Figure 6B When battery pack 601 (battery pack 1) becomes the main battery pack at event 636, battery pack 601 sends periodic data frame messages 671 to battery packs 602, 603, and 604 respectively. (Because the CAN protocol only supports source addresses, all battery packs can receive and process a single broadcast message sent via the CAN bus.) Data frame message 671 corresponds to... Figure 6A The periodic update messages 661a, 661b, and 661c are shown. Data frame message 671 contains at least the configuration list in the payload.

[0117] When battery pack 601 is removed (e.g., corresponding to event 637), the periodic transmission of periodic data frame messages is interrupted.

[0118] When an interruption is detected at event 638 by the oldest slave battery pack (battery pack 602), battery pack 602 assumes the role of the master battery pack. Therefore, battery pack 602 removes the top entry from the configuration list (corresponding to battery pack 601) and periodically sends a revised configuration list via data frame message 672.

[0119] When battery pack 605 (battery pack 5) is added at event 639, battery pack 605 initiates address declaration process 673 to declare its identifier (ID) value. Upon successful completion, the entry with the identifier of battery pack 605 is added to the bottom of the configuration list by the main battery pack 602 at event 640.

[0120] Subsequently, battery pack 602 (now the main battery pack) periodically sends broadcast data frame messages 674.

[0121] Figure 6C An embodiment of a method for configuring multiple battery packs is shown. Figure 6B The changes in the message flow scenario shown. (Compared to...) Figure 6B Similarly, battery pack 601 (designated as the primary battery pack at event 641) periodically sends a configuration list via message 681. However, acknowledgment messages 682a to 682c are returned from battery packs 602, 603, and 604 to confirm receipt.

[0122] At event 642, battery pack 604 is removed from the battery system. When battery pack 601 periodically sends message 683, only messages 684a to 684b are returned. Therefore, a message timeout occurs at event 643, and the main battery pack 601 detects that battery pack 604 has been removed and removes the entry for battery pack 604 from the configuration list. The modified configuration list is included in the next periodic broadcast.

[0123] Figure 6D It shows Figure 6B The message flow scenario shown here is a change where the configuration list is maintained in a distributed rather than centralized manner.

[0124] Battery pack 601 is designated as the master battery pack at event 644. Each of the active battery packs 601 through 604 maintains its own configuration list and broadcasts it to other battery packs via the CAN bus through messages 691a through 691d. The master battery pack, however, does not maintain and send its configuration list to other battery packs. Lists _1, _2, _3, and _4 correspond to the configuration messages maintained at battery packs 601 through 604, respectively. If necessary, battery packs 601 through 604 may modify their own configuration lists to be consistent with the configuration lists broadcast by other battery packs. For example, a battery pack may have been recently inserted into the battery system and may need to revise its configuration list to be consistent with the current configuration.

[0125] When battery pack 601 is removed (e.g., corresponding to event 645), the periodic transmission of periodic data frame messages from battery pack 601 terminates.

[0126] When battery packs 602 to 604 detect termination at event 646, battery pack 602 assumes the role of the main battery pack. Therefore, battery packs 602 to 604 remove the top entries of the configuration list (corresponding to battery pack 601) maintained locally at battery packs 602 to 604, and periodically send the revised configuration list via data frame messages 692a to 692c.

[0127] When battery pack 605 (battery pack 5) is added at event 647, battery pack 605 initiates address declaration process 693 to declare its identifier (ID) value. Upon successful completion, battery packs 602 through 604 add battery pack 5 to the bottom of a local copy of the configuration list. At event 648, and subsequently, the revised configuration list is broadcast via data frame messages 694a through 694d. According to one aspect of the embodiment involving balancing, as will be discussed, current inrush between multiple lithium-ion battery packs in a large battery pack system is an undesirable phenomenon in lithium-ion battery cells because large inrush currents can reduce the lifespan of lithium-ion battery cells. This phenomenon can occur due to large variations in SoC values ​​between battery packs in the battery system. For example, when a brand-new lithium-ion battery pack is added to the battery pack system, its capacity (e.g., energy level) at the start of its new lifespan may be significantly different from the capacity of the battery cells in the older battery packs already present in the battery pack system. This energy level difference between the batteries in the new battery pack and the batteries in the older battery packs can damage other lithium-ion battery cells in the battery pack system. This aspect involves balancing techniques utilizing an internal (non-external) battery management system and a master-slave topology.

[0128] As previously described, some embodiments sort the configuration list based on the time the battery packs have been connected to a communication channel (e.g., a CAN bus). Using this method, the oldest battery pack is designated as the master battery pack. However, other embodiments may use different methods. For example, members of the configuration list can be sorted from top to bottom by decreasing the open-circuit voltage value of the battery packs. The open-circuit voltage of the battery packs can be measured when the battery pack's discharge array is disabled (in other words, the battery pack is not discharging to the battery system's power bus).

[0129] Each battery pack can share its measured open-circuit voltage with other battery packs connected to the communication channel. A configuration list is maintained based on the measured open-circuit voltage, with entries for each battery pack listed in descending order. The battery pack corresponding to the top entry has the highest open-circuit voltage and serves as the main battery pack for the battery system. In an exemplary embodiment, the battery system includes packs each having an open-circuit voltage V.open1 V open2 and V open3 The first battery pack, the second battery pack, and the third battery pack, wherein V open2 >V open3 >V open1 The top entry in the configuration list is associated with the second battery pack (main battery pack), followed by the entry for the third battery pack, and then the entry for the first battery pack. Therefore, if the second battery pack fails, the third battery pack will take over the role of the main battery pack.

[0130] In some embodiments, battery packs in the battery system are assigned IDs, and their open-circuit voltages are measured and stored in a configuration list. In cases where the open-circuit voltages of two battery packs are infrequently equal, a battery pack can be randomly selected or selected using the highest-ranking numerical ID.

[0131] When a battery pack is installed into the battery system, the configuration list may be updated. For example, a battery pack installed after discharge begins will initially enter standby mode (where the discharge array is disabled), allowing the battery pack to measure its open-circuit voltage. The newly installed battery pack can then share the measured open-circuit voltage with other battery packs via a communication channel. In some embodiments, the configuration list can then be updated with entries for the newly installed battery pack based on the measured open-circuit voltage. However, in some embodiments, the current configuration list may remain unchanged until the battery pack being discharged is disconnected from the battery system.

[0132] In some embodiments, the configuration list may be centrally maintained by the main battery pack. However, in some embodiments, each battery pack in the battery system may maintain its own copy of the configuration list based on information shared via a communication channel.

[0133] According to one aspect of the embodiment involving balancing, as will be discussed, current inrush between multiple lithium-ion battery packs in a large battery pack system is an undesirable phenomenon in lithium-ion battery cells because large inrush currents can reduce the lifespan of lithium-ion battery cells. This phenomenon can occur due to large variations in the SoC values ​​between battery packs in the battery system. For example, when a brand-new lithium-ion battery pack is added to a battery pack system, its capacity (e.g., energy level) at the start of its new lifespan may differ significantly from the capacity of the battery cells in the older battery packs already present in the battery pack system. This energy level difference between the cells in the new battery pack and the cells in the older battery packs can damage other lithium-ion battery cells in the battery pack system. This aspect relates to balancing techniques utilizing an internal (non-external) battery management system and a master-slave topology.

[0134] According to one aspect of the embodiments, different balancing techniques for lithium-ion battery cells can be supported in large battery pack systems. For example, this aspect includes three balancing techniques: “smart converter balancing,” “start direct balancing,” and “start staggered balancing,” which can be used in medium to large battery pack implementations to ensure the safe use and lifespan of lithium-ion battery cells. This aspect can utilize a converter (with battery pre-charging circuitry) to perform charge balancing on each battery pack to prevent and / or limit inrush current, overcurrent faults, and / or short-circuit faults.

[0135] Figure 7A A flowchart 700 for determining the balance type of multiple battery packs according to an embodiment is shown.

[0136] At box 701, the main battery pack transitions from sleep mode. For example, when the terminal device is not in use, the main battery pack may periodically wake up to determine if there are any changes in its operating state.

[0137] At box 702, the main battery pack determines the number of battery packs installed in the battery system. For example, the main battery pack can verify that all battery packs on the confirmation list are active on the communication channel.

[0138] At box 704, the main battery pack determines whether a minimum number of battery packs (including itself) are installed based on the device’s power requirements (e.g., obtained from the terminal device via a communication channel).

[0139] If a minimum number of battery packs are not available to properly power the terminal device, at box 705, the appropriate discharge array from the battery pack (and itself) is activated via a main battery pack command to prevent the configured battery pack from discharging. A fault indicator is activated at box 706, indicating that not enough battery packs are installed to power the terminal device. If an additional battery pack is installed at box 707, the fault indicator is cleared at box 708. If the terminal device is activated or otherwise enabled at box 709 (e.g., the key is in the "ON" position), process 700 returns to box 704. Otherwise, process 700 returns to box 701.

[0140] Returning to box 704, when the main battery pack determines that a sufficient number of battery packs exist, at box 710, the main battery pack collects battery pack information (e.g., SoC, SoH, and voltage information) from each of the slave battery packs, as well as its own battery pack information. For example, as will be discussed in further detail, the main battery pack may send a "Request Battery Pack Information" message to each of the configured slave battery packs, and receive a "Battery Pack Information" message from each slave battery pack in response to the requested information.

[0141] In box 711, the main battery pack determines whether balancing is needed based on the collected SoC data. For example, some battery packs may have a high SoC, while others may have a low SoC. By balancing the battery packs, a sufficient number of battery packs can be used to discharge appropriately in order to power the end device.

[0142] If balancing is not required, the battery system can discharge at box 717 to power the end device.

[0143] If balancing is required, the type of balancing is determined at box 712. As will be discussed in more detail, the embodiment may support three different types of balancing: converter balancing (box 713), direct balancing (box 714), and interleaved balancing (box 715).

[0144] Tables 1 and 2 provide examples of balancing according to the embodiments.

[0145]

[0146]

[0147] The examples above illustrate that the type of balance can change when the battery pack is balanced. For instance, according to Table 1, the balance type changes from converter balancing to interleaved balancing, while according to Table 2, the balance type changes from converter balancing to direct balancing.

[0148] Following balancing, as determined at box 716, if the number of battery packs available for discharge, the end device can be powered at box 717. Otherwise, the battery packs can be rebalanced based on revised SoC values ​​obtained from the previous balancing.

[0149] When rebalancing occurs, as defined in box 716, the rebalancing can utilize a different type of balancing than that previously used. For example, a converter balancing can be applied first, and a subsequent rebalancing can utilize an interleaved balancing.

[0150] Figure 7B Expanded Figure 7A The block 712 shown is used to determine the type of charging balance. For example, one embodiment may support multiple balance types, such as direct balance, converter balance, and interleaved balance as previously described.

[0151] At box 721, if the variability of the SoC values ​​between battery packs is small enough, then at box 722, the battery system is able to power the end device. (For example, the SoC difference between all battery pack pairs is less than a predetermined threshold.) Otherwise, process 712 continues to balance the battery packs.

[0152] The battery pack with the highest SoC value is identified at box 723, allowing the identified battery pack to discharge and thus provide charge to other battery packs during balancing.

[0153] At block 724, process 712 determines whether direct balancing cannot be applied (e.g., when the SoC difference between the highest SoC battery pack and the identified battery pack is higher than a predetermined SoC threshold). If so, converter balancing is applied to the identified battery pack at block 728 (where the highest SoC battery pack is discharged onto the power bus and the identified battery pack is charged via its converter through the power bus). When converter balancing is complete, process 712 may return to block 721 and determine whether balancing can be applied to different combinations of battery packs, where the balancing type can be the same or different (e.g., direct balancing or interleaved balancing).

[0154] Returning to reference box 724, if direct balancing can be applied (e.g., when the SoC difference between the highest SoC battery pack and the identified battery pack is below a predetermined SoC threshold), process 712 determines at box 725 whether converter balancing can be applied to one or more other battery packs. If so, staggered balancing is applied at box 727 to the highest SoC battery pack, the identified battery pack, and one or more other packs. Otherwise, at box 726, direct balancing is applied between the highest SoC battery pack and the identified battery pack.

[0155] Figure 7C A flowchart 700 for determining the balance type of multiple battery packs according to an embodiment is shown.

[0156] Table 3 shows the relationship between the battery system's operating modes and the safety interlock pin (indicator) and wake-up pin (indicator). For example, the safety interlock pin is "on" when the battery pack is correctly inserted into the battery system (as sensed by the interlock connection through the battery pack connector), and the wake-up pin is "on" when the user turns the key to activate the electrical appliance (terminal device).

[0157]

[0158] When in disconnect (sleep) mode, the battery pack's discharge and charge arrays are disabled, and the battery pack only consumes enough power to allow it to switch to another state (e.g., balanced mode) when it detects an appropriate signal (e.g., a wake-up indicator).

[0159] In some embodiments, as shown in Table 3, the battery system can support multiple operating modes: disconnect (sleep), balancing, and charge / discharge. While a single mode for charge / discharge is shown, charging and discharging are separate operations based on the interaction between the battery system and its external environment. For example, the battery system enters a charging state when the wake-up indicator and safety interlock indicator are activated, and if a charger (typically external to the battery system) is sensed via the CAN bus. However, if the battery system senses an end device (e.g., an appliance), it enters a discharging state. As will be discussed in further detail, the battery system can support “smart charging” when in charging mode and “smart discharging” when in discharging mode.

[0160] Figure 7C Similar to 7A; however, according to the relationships shown in Table 3, process 730 includes interactions with sleep, balancing, and charge / discharge modes. At box 731, the battery system enters sleep mode when no safety interlock indicator is detected. Otherwise, the battery system (typically the main battery pack) collects configuration information (e.g., SoC information about different battery packs). At box 732, the battery system determines whether a wake-up indicator is detected. If not, the battery system enters balancing mode. Otherwise, the battery system enters charge / discharge mode.

[0161] Figure 8 A message flow scenario 800 for determining the balance type of multiple battery packs is illustrated based on flowchart 700 and according to an embodiment. The main battery pack 802 confirms the availability of battery packs 803 and 804 at event 851, corresponding to messages 861a, 861b, 862, and 863, based on entries in the current confirmation list. As previously stated, the embodiment may support different messaging protocols. For example, according to the CAN protocol, data frame messages may include data in the data field indicating a confirmation request or confirmation response. As previously stated, the interpretation of the data depends on the application software executed at terminal device 801 and battery packs 802 to 804.

[0162] Terminal device 801 provides its power requirements in message 886, enabling main battery pack 801 to determine the number of battery packs required by terminal device 801 at event 852.

[0163] At event 853, the main battery pack 802 collects SoC data about other battery packs via messages 865 to 868. (The main battery pack 802 can use internal message passing within the battery pack to obtain information about its own SoC.) For example, according to the CAN protocol, data contained in the request battery pack information message 865 can be interpreted as a request from the target battery pack, while data in the packet information message 866 can be interpreted as data requested from the destination battery pack (e.g., SoC data).

[0164] Based on the collected SoC data, the main battery pack 801 determines the type of balancing required (if necessary) and initiates the appropriate balancing process (e.g., Figure 9 , Figure 11 and Figure 13 (The process shown).

[0165] As previously described, the embodiments can support different types of balancing, such as converter balancing, direct balancing, and interleaved balancing. Converter balancing typically requires a longer time period than direct balancing.

[0166] Although Figure 9 , Figure 11 and Figure 13 The process shown is typically performed at the main battery pack, but the main battery does not need to be altered or discharged during balancing. This determination is based on the SoC values ​​of battery cells 203 and 210 (respectively in...). Figure 2A and Figure 2B (as shown in the image), rather than based on whether the battery pack is the main battery pack or a secondary battery pack.

[0167] Figure 9 A flowchart 713 for converter balancing of multiple battery packs according to an embodiment is shown (reference). Figure 7A Converter balancing begins at box 901, where one of the battery packs (either the main battery pack or one from the main battery pack) charges one or more of the other battery packs.

[0168] In the case of converter balancing, the charge of a single battery pack is transferred to one or more battery packs via a converter on each of the charging battery packs. Therefore, this type of balancing involves two or more battery packs.

[0169] Although not explicitly stated, the main battery pack collects SoC data about all battery packs, including itself. For example, the main battery pack can request battery status information from other battery packs via the CAN bus and internally retrieve its own SoC data.

[0170] At box 902, the main battery pack enables the battery pack with the highest SoC to discharge by enabling the discharge array. By enabling the charging array and on-board converter, the main battery pack also enables one or more of the battery packs with the lowest SoC to accept charge from the discharging battery pack.

[0171] At box 904, the main battery pack obtains the SoC value from the aforementioned battery pack and continues the balancing process at box 905 until the desired charge balance is achieved at box 905. If the charge balance is sufficient, the battery pack can be used to power the end device. However, a faster balancing mode (e.g., direct balancing, as will be discussed later) can then be applied.

[0172] Figure 10 A message flow scenario for converter balancing of multiple battery packs according to an embodiment is illustrated. Battery packs 1002, 1003, and 1004 initially have SoC values ​​of 100%, 65%, and 65%, respectively. As previously described, the main battery pack 1002 can obtain its SoC value by requesting battery status information and receiving the status information via data frame messages on the CAN bus.

[0173] At event 1051, main battery pack 1002 determines that battery packs 1003 and 1004 will be charged by themselves (battery pack 1002). To this end, the main battery pack activates its own discharge array and enables the charging array and converter via messages 1061 and 1062. At event 1052, balancing continues until the required balance charge (80%, 75%, and 75%) is achieved. At this point, balancing ends, causing the main battery pack to disable its charging array, and the charging arrays and converters of battery packs 1003 and 1004 are disabled via messages 1063 and 1064.

[0174] Figure 11 A flowchart 714 for directly balancing multiple battery packs according to an embodiment is shown. Figure 7A As shown, when process 700 determines that direct balancing should be performed, the main battery pack initiates direct balancing at block 1101.

[0175] In direct balancing, one battery pack charges the other through a low-impedance electrical path. Therefore, only two battery packs are involved in the balancing type.

[0176] Although not explicitly shown, the main battery pack acquires the SoC values ​​of all battery packs installed in the battery system. To do this, the main battery pack sends status requests to the slave battery packs and receives status information (e.g., SoC values) from the slave battery packs via message transmission on a communication channel. However, because the main battery knows its own cell status, only internal message transmissions for the main battery are required.

[0177] At box 1102, the main battery pack commands the battery pack with the higher SoC to begin discharging by enabling its discharge array, and at box 1103, the main battery pack commands one of the battery packs with the lower SoC to begin charging by enabling its charging array.

[0178] At box 1104, the main battery pack collects SoC data from the battery pack being charged and balanced. Direct balancing terminates at box 1106 when an acceptable SoC is reached at box 1105.

[0179] Figure 12A message flow scenario for direct balancing of multiple battery packs according to an embodiment is illustrated. The main battery pack (battery pack 1201) collects initial SoC values ​​of 80%, 70%, and 90% for battery pack 1201, and initial SoC values ​​for battery packs 1202 and 1203, respectively.

[0180] Because battery pack 1202 has the lowest SoC and battery pack 1203 has the highest SoC, the main battery pack commands battery pack 1202 to enable its charging array and commands battery pack 1203 to enable its discharging array via messages 1261 and 1262, respectively.

[0181] When the SoC values ​​of battery packs 1202 and 1203 reach 80%, the main battery pack (battery pack 1202) determines that direct balancing has been completed at event 1251, and therefore disables the charging array and discharging array via messages 1263 and 1264 respectively.

[0182] Figure 13 A flowchart 714 for staggered balancing of multiple battery packs according to an embodiment is shown. Figure 7A As shown, when process 700 determines that interleaving balancing should be performed, the main battery pack initiates interleaving balancing at block 1301.

[0183] Interleaved balancing utilizes an algorithm for direct balancing. With interleaved balancing, one battery pack (typically the highest SoC value) directly charges another battery pack with a lower SoC, while simultaneously balancing one or more other lower SoC battery packs via a converter (where the converter located on the charged battery pack is enabled). To keep other lower SoC battery packs within acceptable limits, direct balancing can switch to different lower SoC battery packs, while the previously lower SoC battery packs are now balanced via converters.

[0184] With Figure 11 Similar to blocks 1101 and 1102, at blocks 1301 and 1302, a direct balance is established using the battery pack with the highest SOC and another battery pack from the group with a low SOC. However, at block 1304, converter balance is established using some or all of the battery packs from the low SOC group.

[0185] At box 1305, the main battery pack collects updated SoC values ​​for the participating battery packs. When a directly charged battery pack reaches a defined SoC threshold (e.g., when an imbalance occurs in one of the battery packs in the low SoC group), a direct balance is established with another battery pack in the low SoC group at box 1307.

[0186] When all battery packs are within acceptable SoC ranges, as defined in box 1308, the interleaved balancing terminates at box 1309.

[0187] Figure 14 and Figure 15 A message flow scenario for interleaving and balancing multiple battery packs according to an embodiment is illustrated. The main battery pack (battery pack 1401) collects initial SoC values ​​of 60%, 60%, and 100% at battery pack 1401, and initial SoC values ​​at battery packs 1402 and 1403, respectively.

[0188] At event 1451, main battery pack 1401 initiates direct balancing between battery pack 1402 (in the low SoC group) and battery pack 1403 (highest SoC), and establishes converter balancing between battery pack 1403 and itself (also in the low SoC group). Therefore, main battery pack 1401 sends messages 1461 and 1462 corresponding to battery packs 1461 and 1462 respectively via communication channels, and generates any internal message transmissions as needed to enable its charging array and converter.

[0189] As a result of balancing, the SoC values ​​of battery packs 1401, 1402, and 1403 become 62%, 70%, and 88%, respectively. Due to the charging imbalance between battery packs 1401 and 1402, the main battery pack 1401 establishes a direct balance between battery pack 1403 and itself, and establishes a converter balance for battery pack 1402. Therefore, at event 1452, the main battery pack 1401 commands battery pack 1402 to enable its converter via message 1463 (so that charging now occurs via the converter instead of directly), and disables its own converter, so that its battery cells are directly exposed to charging.

[0190] refer to Figure 15 As a result of balancing, the SoC values ​​of battery packs 1401, 1402, and 1403 become 72%, 72%, and 76%, respectively. At event 1453, the main battery pack 1401 determines that balancing has been completed and terminates the interleaved balancing by sending messages 1464 and 1465 to battery packs 1403 and 1402, respectively, and internally disables its charging array.

[0191] Intelligent systems and algorithmic methods (e.g., Figure 17 The illustrated process 1700 can ensure that the SoC corresponding to multiple battery packs can be more balanced, for example, ensuring that multiple battery packs can be charged together. In various embodiments, a battery pack may include one or more batteries and / or may include a device that may include one or more batteries. The one or more batteries in a battery pack may share various characteristics (e.g., state of charge, state of health, etc.). Furthermore, each battery pack can be enabled or disabled, for example, in terms of its ability to charge or discharge other battery packs or terminal devices.

[0192] Still referencing Figure 16 Battery packs with large SoC variations cannot be immediately connected to charger 1601. For example, as Figure 16 As shown, each battery pack 1602a and 1603a, having a lower SoC (e.g., 20% and 20% respectively) than other battery packs, can be charged earlier (e.g., before the other battery packs) until a set threshold is reached at which the battery pack with a higher SoC (e.g., battery pack 1604b) can be charged. For example, it may be necessary to prioritize charging the battery packs with lower SoCs before charging the battery packs with higher SoCs, because without doing so, charging the higher battery packs with higher SoCs first could cause a rapid inrush current to the lower SoC battery packs. In some aspects, the systems and devices proposed herein can cause charging of various battery packs by enabling the flow of a discharge array between the charger and the respective battery packs.

[0193] like Figure 16 As shown, initial charging of battery packs 1602a and 1603a increases their SoC from 20% to 40% (e.g., as shown in 1602b and 1603b). Charging of battery packs 1602b through 1604b can continue until the SoC level of battery pack 1605b is reached. At this point, battery pack 1605b can be enabled, allowing charging of battery packs 1602b through 1605b to continue.

[0194] Figure 17 An exemplary flowchart of a method 1700 for charging multiple battery packs according to an embodiment is shown. Method 1700 may be executed by a computing device having one or more processors communicatively linked to one or more of the multiple battery packs and / or linked to a charger. Similarly or alternatively, the computing device executing method 1700 may include battery packs (e.g., a “master battery pack” or a “slave battery pack”) having the ability to manage one or more functions of the other battery packs among the multiple battery packs. After obtaining the SoC values ​​of the battery packs in the battery system, at block 1701, a subset of the battery packs may be grouped into lower SoC groups. For example, the obtained SoC values ​​(e.g., SoC readings) may be categorized into various levels, for example, based on a predetermined range. Those battery packs with the lowest SoC values ​​may be grouped into the lowest level. Battery packs within a particular level may have SoC values ​​within a specific or predetermined range from each other. Those battery packs with a second lowest SoC value (e.g., SoC values ​​higher than the lowest level but lower than the SoC values ​​of the remaining battery packs) may be placed in the second lowest level. As used herein, “lower SoC battery pack” may refer to a list of battery packs that includes: (1) a group of battery packs with the lowest SoC value and (2) a group of battery packs with the second lowest SoC value.

[0195] At box 1702, a SoC threshold can be determined. The SoC threshold can be approximately equal to the SoC value of a group of one or more battery packs that has a SoC value just higher than the group of battery packs with the lowest SoC value. For example, the SoC threshold can be based on a second lowest level of SoC values ​​(e.g., the average of the SoC values ​​of the second lowest level of battery packs).

[0196] At box 1703, the battery pack of the group with the lowest-level SoC can be enabled for charging, thereby facilitating, for example, charging of the battery pack of the SoC with the lowest-level SoC. In some aspects, charging can be enabled if one or both of the safety interlock pin or the wake-up pin are set to "on", as previously described.

[0197] When the SoC value of a charging battery pack reaches a SoC threshold, as determined at box 1704, process 1700 may include determining whether to expand the list (e.g., the "lower SoC battery packs" list of step 1701) for subsequent charging at box 1705. Determining whether to expand the list may be based on whether there is significant variability in the SoC of the battery pack (e.g., whether the SoC variability of the battery pack meets the SoC variability threshold), as per the relevant... Figure 18C Further description: If the list is to be expanded, the SoC threshold can be updated (e.g., based on determining the second lowest level of the SoC in the updated list), the selected battery pack can be enabled, and charging can continue at boxes 1706 and 1707.

[0198] Figure 18A It shows the Figure 16 The example illustrates a message flow scenario involving the charging of multiple battery packs. In this scenario, charger 1801a may perform one or more iterations of the following: collecting SoC data (e.g., receiving SoC readings) from multiple battery packs (e.g., battery packs 1802a to 1805a), identifying SoC levels to form a list based on SoC levels, and enabling the charging of selected battery packs to SoC thresholds via a communication channel (e.g., a CAN bus). For example, at event 1851a, charger 1801a may collect initial SoC values ​​of 20%, 20%, 40%, and 60% from battery packs 1802a, 1803a, 1804a, and 1805a, respectively.

[0199] At event 1851b, charger 1801a can determine that the group of battery packs with the lowest SoC values ​​includes battery packs 1802a and 1803a, and the group of battery packs with higher (e.g., second lowest) SoC values ​​includes battery pack 1804a. A list of battery packs can be formed, and the list of battery packs can include battery packs with the lowest SoC values ​​and battery packs with higher (e.g., second lowest) SoC values.

[0200] At event 1851c, charger 1801a may enable charging of the group of battery packs (e.g., battery packs 1802a and 1803a) with the lowest SoC values ​​via messages 1861 and 1862. Charging may continue until the SoC values ​​of these battery packs meet a SoC threshold based on the group of one or more battery packs with higher SoC values ​​(e.g., the battery pack with the second lowest SoC value (e.g., battery pack 1804a at 40%)).

[0201] At event 1852a, charger 1801a can collect the SoC values ​​of the entire battery pack. For example... Figure 18A As shown, as a result of the aforementioned charging at event 1851c, the SoC values ​​of battery packs 1802a and 1803a will increase to 40%. At event 1852b, charger 1801a can determine to expand the list of battery packs determined at event 1851a. For example, SoC variability can be determined for battery packs 1802a to 1805a, and the list can be expanded based on SoC variability significant enough to meet an SoC variability threshold. Figure 18A In the scenario shown, battery pack 1806a has a 60% SoC value, which differs from the updated SoC value of 40% for battery packs 1802a, 1803a, and 1804a. Therefore, battery packs 1802a, 1803a, 1804a, and 1805a exhibit SoC variability, which may allow charger 1801a to expand its list. The expanded list could include groups of one or more battery packs with the lowest SoC value (e.g., battery packs 1802a, 1803a, and 1804a) and groups of one or more battery packs with higher SoC values ​​(e.g., battery pack 1805a). The former group (e.g., the group of battery packs with the lowest SoC value) could therefore include battery pack 1804a. At event 1852c, charger 1852c can therefore enable charging of battery packs 1802a, 1803a, and 1804a via message 1863.

[0202] Figure 18B It shows the use for Figure 16The example shown illustrates a message flow scenario of multiple battery packs being charged. However, instead of charger 1801b collecting SoC data and enabling the battery packs, the main battery pack 1802b does so when it detects charger 1801b via connection indicator 1871. Connection indicator 1871 can be obtained through various methods, including message transmission via communication channels, pins, etc.

[0203] Figure 18C An exemplary flowchart of a method 1800C for intelligently charging multiple battery packs according to a non-limiting embodiment is shown. Method 1800C can be executed by a computing device having one or more processors. The computing device can be a separate device communicatively linked to one or more of the battery packs and / or a charger. Similarly or alternatively, the computing device may include one of the battery packs (e.g., the main battery pack) having the capability to manage one or more of the other battery packs among the multiple battery packs. Similarly or alternatively, the computing device may include a charger.

[0204] As previously described, each battery pack may have a State of Charge (SoC) indicating, for example, the degree or level of charge relative to its capacity. At step 1874, the computing device may receive a reading of the SoC of each of the multiple battery packs (e.g., a first reading). This reading may be acquired via a sensor or monitor at each battery pack. As previously described, the SoC may vary among the multiple battery packs or may remain relatively constant. SoC variability (e.g., a first SoC variability) may be calculated to indicate the degree of variability of the SoCs of the multiple battery packs (e.g., as in step 1875).

[0205] SoC variability can be based on the SoC of each of the respective battery packs obtained in step 1874. For example, SoC variability can be based on one or more of the following: variance, standard deviation, range (e.g., interquartile range), mean absolute difference, median absolute deviation, mean absolute deviation, distance standard deviation, or a similar measure based on the SoC value of each of the multiple battery packs. For example, in Table 1 discussed above, which includes multiple battery packs (e.g., battery pack 1, battery pack 2, battery pack 3, and battery pack 4), the SoC variability at time T0 is greater than the SoC variability at time T6. In one aspect, when SoC variability is determined based on the calculated range of SoC values, the SoC variability of the battery pack at T0 is 85 (i.e., 100% to 15%), while the SoC variability at T6 is only 4 (e.g., 45% to 41%). If “5” is set as the SoC variability threshold, it can be said that the SoC variability at T6 has been satisfied as described (e.g., decreased to below) that threshold.

[0206] In some aspects, interlocking safety pins may need to allow interaction with the battery pack before the computing device can receive SoC readings. For example, the computing device may initially determine that the interlocking safety pins allow receiving SoC readings from multiple battery packs.

[0207] The computing device may, for example, store in storage device 202 a metric indicating a threshold for SoC variability, to indicate, for example, whether SoC variability is insignificant. For instance, if the SoC of a battery pack (e.g., the first battery pack) is significantly lower than the SoC of another battery pack (e.g., the second battery pack), the SoC variability is likely large and therefore does not meet the SoC variability threshold. At step 1876, the computing device can thus determine whether the SoC variability (e.g., as calculated in step 1875) meets the SoC variability threshold.

[0208] If the SoC variability does not meet the SoC variability threshold (e.g., the SoC variation between multiple battery packs is significant), the computing device can establish an SoC threshold (e.g., as in step 1878). The SoC threshold can be based on the SoC reading of a battery pack (e.g., a second battery pack) with the next higher SoC reading, following the battery pack with the lowest SoC (e.g., the first battery pack). Therefore, the computing device can identify the lowest SoC reading to determine the next higher SoC reading (e.g., as in step 1877). For example, as per [reference to...] Figure 16 The battery pack 1604a under discussion has a SoC of 40%, which is the next higher SoC after the lowest SoC of 20% for battery packs belonging to battery packs 1602a and 1603a. Therefore, based on the information regarding... Figure 16 In the example shown, the SoC threshold can be set to 40%.

[0209] Furthermore, at step 1879, the computing device may, for example, enable a charge array from the charger to the battery pack to charge the battery pack, which has a SoC lower than the established SoC threshold. Charging may increase the SoC of the battery pack to, for example, bring it closer to, match, and / or meet the SoC threshold.

[0210] In some aspects, a wake-up pin may need to allow charging to occur before the computing device can enable charging of any battery pack as previously described. For example, the wake-up pin may need to be set to "on" before charging occurs. The computing device may initially determine that the wake-up pin is set to "on" before enabling charging of the battery pack.

[0211] This can be detected by a computing device via additional readings (e.g., a second reading) of the SoC of each of the multiple battery packs. Furthermore, the computing device can determine or calculate a second SoC variability of the multiple battery packs based on these additional readings. It can be found that the second SoC variability satisfies an SoC variability threshold.

[0212] If no second SoC variability is found that satisfies the SoC variability threshold, one or more steps of method 1800C can be repeated until the SoC variability threshold is met. For example, a new SoC threshold can be set based on the next higher SoC after the lowest SoC, and the battery pack with the lowest SoC can be charged.

[0213] Therefore, after the updated SOC variability of multiple battery packs satisfies the SOC variability threshold, one or more iterations of the following can be performed: the computing device can identify the Nth group of one or more battery packs within the multiple backup battery devices, where the Nth group may have the lowest level of the previously read SOC of the multiple battery packs; the computing device can also identify the (N+1)th group of one or more battery packs within the multiple backup battery devices, where the (N+1)th group may have a second lowest level of the previously read SoC of the multiple battery packs; and the computing device can generate a list including the nth group and the N+1th group. In each iteration, the computing device can determine that the SOC variability of the list in the current iteration does not satisfy the SOC variability threshold. If the SoC variability does satisfy the SoC threshold, the computing device can exit the iteration loop. However, assuming that the SoC variability does not satisfy the SoC variability threshold in each iteration, the computing device can use the SoC threshold of the previously read SOC of the N+1th group. Subsequently, the computing device can charge the Nth group of battery packs via a charge array, thereby increasing the SOC of the Nth group and satisfying the SOC threshold. The computing device can receive subsequent readings of the SoC of each of the multiple battery packs. Therefore, the updated SoC variability of the multiple battery packs can be determined based on the subsequent readings of the SoC of each of the multiple battery packs. As discussed, the above steps can be repeated until the SoC variability (in each iterative update) meets an SoC variability threshold (e.g., the SoC change of the battery pack is less than a specified range).

[0214] The following Figure 19A and Figure 19B Two examples of battery systems that power terminal devices based on their power requirements are shown. Figure 19A In this configuration, only one battery pack is needed to power the terminal devices 1901a and 1901b, while... Figure 19B In this case, more than one battery pack is required to power the terminal devices 1911a and 1911b.

[0215] Figure 19A Examples of multiple battery packs being discharged to power a terminal device according to an embodiment are shown. The initial SoC values ​​of battery packs 1902a to 1905a are 40%, 40%, 40%, and 60%, respectively. Figure 19A As shown, a single battery pack (e.g., battery pack 1905a with 60% SoC) can initially be used to power the terminal device 1901a until the SoC value of the single battery pack reaches 40% (the same SoC value as other battery packs) (e.g., as in battery pack 1905b). Only a group of one or more battery packs with the highest or higher SoC level (in this case, a single battery pack 1905a) is used to initially power the terminal device until the SoC value of said group reaches the SoC value of the rest of said group. This may be a more efficient and / or safer method of utilizing battery packs to power the terminal device. Figure 19A As shown, after a single battery pack with an initial high SoC value has been used to initially power the terminal device, and its SoC reading reaches the readings of other battery packs (e.g., battery packs 1902b to 1905b), other battery packs can be added to power the terminal device 1901b.

[0216] Figure 19B Another example is shown where multiple battery packs are discharged according to an embodiment to power a terminal device. For example... Figure 19B As shown, the initial SoC values ​​of battery packs 1912a to 1915a are 40%, 40%, 40%, and 60%, respectively. In some aspects, more than one battery pack may be needed to power terminal devices 1911a to 1911b. In these aspects, the various systems and methods presented herein can be used to balance the battery packs before powering terminal devices 1911a to 1911b. Balancing of battery packs 1912a to 1914a can be performed, for example, to prevent the risk of unwanted current inrush from battery pack 1915a, which could occur without balancing. When balancing is achieved, battery packs 1912b to 1915b can then power terminal device 1911b.

[0217] Connecting battery packs with varying SoCs can be problematic when powering end devices (e.g., machines). Therefore, to prevent this, a process (typically implementing a smart approach) may be needed to ensure that the required number of battery packs are connected for system discharge and that those battery packs are activated when appropriate.

[0218] Generally, when multiple battery packs are needed to power a terminal device, it is best not to connect battery packs with large SoC variations simultaneously. Instead, battery pack balancing can be performed initially.

[0219] Discharge can begin with one or more battery packs with higher SoC values ​​until a set threshold for lower SoC battery packs is exceeded, at which point the lower SoC battery packs can be enabled.

[0220] Based on the above criteria, Process 2000 and Process 2010 respectively... Figure 20A and Figure 20B As shown in the image.

[0221] Figure 20A A process 2000 for discharging multiple battery packs to power an end device is illustrated. In blocks 2001-2003, initial SoC values ​​of the battery packs are collected, and balancing can be performed based on SoC changes and the power requirements of the end device. As previously described, Figure 19B These are exemplary illustrations of the process of balancing battery packs as described in boxes 2001-2003. However, as will be described in boxes 2004-2008, some aspects of the invention may involve initially powering a terminal device with a single or limited number of battery packs having a higher SoC level before other battery packs can participate in powering the terminal device. As previously stated, Figure 19A This is an exemplary illustration of the process of powering a terminal device with an initial limited number of battery packs and expanding the list of backup batteries that can power the terminal device.

[0222] Referring now to box 2001a, the power requirements of the terminal device can be obtained, and a first reading of the SoC (System-on-Chips) for each of multiple battery packs can be acquired. The multiple battery packs may include various battery packs or groups of battery packs with varying SoC values. At box 2001b, SoC variability can be calculated to determine the extent of SoC value variation among the multiple battery packs. Similarly or alternatively, a highest SoC level can be identified, and the computing device can determine that not all battery packs have the highest SoC value.

[0223] Based on SoC variability, if multiple battery packs are used to power the terminal device simultaneously, multiple battery packs may pose a risk. As previously discussed... Figure 19A If one or more groups of battery packs have a SoC value significantly greater than the SoC of the remaining battery packs, it may be recommended to initially power the end device using only the group with the significantly larger SoC value (e.g., in the absence of simultaneous power from other battery packs). The computing device may allow a single or limited number of battery pack groups to power the end device by enabling only the corresponding discharge array of said group. Paths allowing a group to power the end device are illustrated in boxes 2004-2008.

[0224] Another way to address the aforementioned and similar risks is to balance the battery packs, thereby reducing the SoC variability of multiple battery packs, as previously discussed... Figure 19B As described above. For example, one group of battery packs (e.g., the first group) may have a lower SoC value than another group of battery packs (e.g., the second group). Based on the SoC variation between the first and second groups, the SoC variability of multiple devices can be calculated and it can be found that SoC variability thresholds are not met (e.g., the range between the highest and lowest SoC values ​​is too large). The computing device can therefore determine the need for balancing (e.g., at box 2002) based on the SoC variability that does not meet (e.g., falls within) the SoC variability threshold. Therefore, it can be based on Figure 19B The previously described method is used to balance the battery pack.

[0225] The computing device can thus determine whether balancing is unnecessary (e.g., "No" at box 2002). This decision can be a preference provided to the computing device by its operator (e.g., configured to). Similarly or alternatively, this decision can be based on two or more SoC variability thresholds. For example, if the SoC variability of multiple battery packs is higher than a higher SoC variability threshold (e.g., a first SoC variability threshold), a path to balance the battery packs can be triggered. If the SoC variability is not higher than the first SoC variability threshold but is still higher than a second SoC variability threshold (which is not as high as the first SoC variability threshold), a path depicted in boxes 2004 through 2008 can be triggered (e.g., causing one or more battery packs with higher SoCs to initially power the end device).

[0226] Referring now to boxes 2004 and 2005, a group of one or more battery packs can be identified and enabled (e.g., by enabling a corresponding discharge array) to power the end device. This group can be identified by identifying a battery pack with the highest SoC level or at least a higher level than other battery packs. The computing device can then enable this group to power the end device, thereby initiating the discharge of the group of battery packs (e.g., as in box 2005). The discharging group of battery packs can reach a lower SoC level. The resulting lower SoC level from the initial group with a higher SoC level can lead to lower SoC variability for multiple battery packs. Therefore, the computing device can determine the updated SoC variability at box 2006. If the updated SoC variability does not meet the SoC variability threshold (e.g., there are still battery packs with higher SoC levels), then, similarly at boxes 2004 and 2005, additional battery packs can be identified and enabled to power the end device. After the SoC variability of multiple battery packs meets the SoC variability threshold (e.g., there is not much change in the SoC levels of the multiple battery packs), the computing device can allow all battery packs to power the end device.

[0227] Similarly or alternatively, the two paths described above (e.g., boxes 2002-2003 and boxes 2004-2008, respectively) can be combined. For example, after balancing has been performed at box 2003, a second reading of the SoC for each of the multiple battery packs can be obtained, and a second SoC variability can be calculated. The SoC variability can satisfy an SoC variability threshold; for example, the SoCs of the multiple battery packs can vary little and / or have a reduced range. Subsequently, the multiple battery packs can simultaneously power the terminal device.

[0228] Figure 20B A process 2010 for discharging multiple battery packs according to an exemplary embodiment is shown. Process 2010 is similar to process 2000; however, some battery packs may be isolated based on the battery pack's state of health (SoH). Battery packs with low SoH can be isolated and used only when needed.

[0229] In boxes 2011-2013, the SoC value and SoH value of the battery pack can be collected. Battery packs with SoH values ​​that do not meet a predetermined SoH threshold can be isolated for later use after a non-isolated battery pack has been deployed. Non-isolated battery packs (e.g., battery packs with SoH levels that meet the SoH threshold) can be used to initially power the end device based on the end device requirements and the SoC value of the battery pack, as explained herein.

[0230] For example, at box 2013, a battery pack with a SoC value that meets a SoC threshold (e.g., a SoC value higher than the next highest SoC level among multiple battery packs) can be enabled to power the end device, thereby discharging these battery packs at box 2014. As shown in boxes 2014-2016, the enabled battery packs can discharge until a lower SoC value is reached (e.g., the SoC does not meet the SoC threshold). At this point, an additional non-isolated battery pack can be enabled at box 2017. However, when no non-isolated battery packs are available, isolated battery packs can be considered in boxes 2018-2020.

[0231] Isolating low-SoH battery packs can be beneficial because it reduces the use of older battery packs (which are often associated with low SoH values), thereby extending the lifespan of these packs.

[0232] Figure 21 It shows Figure 19AThe example shown illustrates a message flow scenario for discharging multiple battery packs. Battery packs 2002 to 2005 initially have SoC values ​​of 40%, 40%, 40%, and 60%, respectively. The power requirement of terminal device 2101 can be obtained from main battery pack 2102 via message 2161 on a communication channel (e.g., CAN bus), where only one battery pack is needed to power terminal device 2101. Therefore, according to process 2100, main battery pack 2102 can enable battery pack 2105 to discharge via message 2162.

[0233] When battery pack 2105 reaches the SoC value of other battery packs, main battery pack 2102 enables battery packs 2103 and 2104 via messages 2163 and 2164, and can also enable itself via internal message transmission.

[0234] In some aspects, processes (e.g., process 2200, which will be discussed) may involve “limp-home mode” operation in the event of a failure in a lithium-ion battery cell in a large battery pack system. “Limp-home mode” operation can safely mitigate catastrophic failures in the system. For example, the voltage of a battery cell may become very low (e.g., below a predetermined voltage threshold), indicating a battery cell failure. For medium to large battery pack implementations, the internal battery management system can pre-diagnose the failure and thus mitigate it by initiating a partial shutdown of the battery pack, allowing the battery-powered devices (terminal devices) to “limp-home” without needing to be completely shut down.

[0235] Figure 22 This is a flowchart illustrating operation for limp-home mode according to an embodiment. At block 2201, the main battery pack detects a catastrophic failure of one or more battery cells in one of the battery cells of the battery pack powering the terminal device. For example, the battery voltage in the battery pack may drop below an acceptable minimum threshold; exceed the maximum current; and / or the battery cell temperature may be above the permissible range.

[0236] When the main battery pack detects a catastrophic failure, at box 2202, the main battery pack determines whether an additional battery pack is needed. For example, if the terminal device only requires three battery packs with a given SoC level, the battery system may already have four battery packs activated. If so, process 2200 disables the faulty battery pack at box 2203 and continues operation.

[0237] However, if an additional battery pack is required, at box 2204, the main battery pack determines whether an unused battery pack in the battery system (which could be the main battery pack itself) is available. If so, at box 2205, the main battery pack disables the faulty battery pack (e.g., disables the discharge array) and enables the additional battery pack (e.g., enables the discharge array). If more than one additional battery pack is available, the main battery pack can select the additional battery pack with the largest SoC value to continue service for the longest possible time. However, as determined at box 2206, when no additional battery pack is available and degraded operation of the terminal device is permitted, at box 2208, the main battery pack disables the faulty battery pack and sends a fault alarm message to the terminal device regarding degraded operation. However, if degraded operation is unacceptable for the terminal device, power is removed from the terminal device at box 2207 to shut down the terminal device.

[0238] When a slave battery pack fails, it may not send messages to the master battery pack under various failure modes. However, the master battery pack can determine that there is no longer any communication from the slave battery pack and adjust the power level to the end device (reduce the rating).

[0239] While a faulty battery pack can be a secondary battery pack, the primary battery pack itself can also be faulty. For example, even when the primary battery pack's processing power is not impaired, one of its battery cells may fail. If so, the primary battery pack can internally disable its own discharge array, attempt to enable the discharge array of the backup battery pack, and continue operating as the primary battery pack.

[0240] In some embodiments, a new main battery pack can be assigned even if the faulty main battery pack is still operating, when the main battery pack has failed. This method ensures that the faulty main battery pack does not compromise the integrity of the overall processing of other battery packs.

[0241] In some embodiments, when a main battery pack has failed, a new main battery pack can be allocated to allow performance degradation to continue even when communication with the failed main battery is lost.

[0242] Figure 23A A message stream scenario for limp-home mode operation according to an embodiment is illustrated. In this scenario, a backup battery pack (battery pack 2104a) is available when a catastrophic failure is detected at battery pack 2103a.

[0243] At event 2151a, in response to fault notification message 2161, main battery pack 2102a detects a catastrophic failure of battery pack 2103a. For example, battery pack 2103a may provide battery status information indicating low cell voltages. This status information may be sent in response to a query from main battery pack 2102a, or it may be sent automatically upon the occurrence of a catastrophic event. Therefore, main battery pack 2102a enables backup battery pack 2104a and disables the faulty battery pack 2103a via messages 2163 and 2162, respectively.

[0244] Figure 23A A message stream scenario for limp-home mode operation is illustrated according to an embodiment. In this scenario, the backup battery pack is unavailable.

[0245] At event 2152, similar to Figure 23A In the message scenario, when the main battery pack 2102b receives a fault notification message 2164 from 2103b, it detects a catastrophic failure at battery pack 2103b. Because the main battery pack 2102b determines that no backup battery pack is available, it disables battery pack 2103b via message 2165 and sends a degradation message 2166 to the terminal device 2101b, where the terminal device 2101b is capable of operating in degradation mode.

[0246] refer to Figures 23A to 23B Fault notification messages 2161 and 2163 can be sent automatically from the battery pack that caused the catastrophic failure, or in response to a request for battery status information from the main battery packs 2102a and 2102b. When sent autonomously, the battery packs can detect when battery parameters (e.g., SOH or battery voltage) drop to a predetermined threshold and then send a fault notification message to the main battery packs 2102a and 2102b. When a status request is sent, the main battery packs 2102a and 2102b repeat (e.g., periodically) the status request. The battery packs receive the status request and provide current battery status information in response. When one or more of the returned battery parameters drop below the predetermined threshold, the main battery packs 2102a and 2102b detect a catastrophic failure at the battery pack.

[0247] In some embodiments, the main battery packs 2102a and 2102b can receive periodic battery status information from other battery packs. When the main battery packs 2102a and 2102b detect a sudden drop in one of the battery parameters (e.g., battery voltage) (e.g., exceeding a predetermined difference relative to a previous value), the main battery packs 2102a and 2102b can determine that a catastrophic failure at the corresponding battery pack is predicted or is about to occur, and take preemptive action and / or generate a warning notification.

[0248] In some embodiments, battery cells 203 and 210 (respectively in...) Figure 2A and Figure 2B (As shown in the diagram) may have a battery structure (e.g., a parallel structure) that allows the battery pack to deactivate a faulty battery cell while keeping other battery cells active. In this case, the battery pack can operate in a degradation mode and report to the main battery packs 2102a, 2102b that the battery pack is operating in a degradation mode.

[0249] Numerous illustrative embodiments are set forth below based on one or more aspects disclosed herein. Although many of the embodiments listed below are described as dependent on other embodiments, such dependence is not limited thereto. For example, Embodiment 5 (below) is explicitly described as incorporating features of Embodiment 1 (below); however, this disclosure is not limited thereto. For example, Embodiment 5 may depend on any one or more of the foregoing embodiments (i.e., Embodiment 1, Embodiment 2, Embodiment 3, and / or Embodiment 4). Furthermore, this disclosure contemplates that any one or more of Embodiments 2 to 12 may be incorporated into Embodiment 1. Similarly, any one of Embodiments 1, 14, 17, and 22 may be combined with one or more of the features described in Embodiments 2 to 13, 15 to 16, 18 to 21, and / or 23 to 26. Further, similarly, any one of Embodiments 27, 39, and 43 may be combined with one or more of the features described in Embodiments 28 to 38, 40 to 42, and 44 to 46. Further, similarly, any one of Embodiments 47, 59, and 64 may be combined with one or more of the features described in Embodiments 48 to 58, 60 to 63, and 65 to 69. Similarly, any one of embodiments 70, 87, and 92 can be combined with one or more of the features described in embodiments 71 to 86, 88 to 91, and 93 to 94. Similarly, any one of embodiments 95, 105, and 109 can be combined with one or more of the features described in embodiments 96 to 104, 106 to 108, and 110 to 114. Furthermore, this disclosure is contemplated that any one or more of the features in embodiments 1, 14, 17, 22, 27, 39, 43, 47, 59, 64, 70, 87, 92, 95, 105, and 109 can be combined. Moreover, this disclosure is contemplated that any one or more of the features in embodiments 1 to 114 can be combined.

[0250] Example 1: A first battery pack configured to power a terminal device within a battery system, wherein all installed battery packs within the battery system have substantially identical electrical and electronic components. The first battery pack includes:

[0251] A communication interface circuit, configured to interface to a communication channel;

[0252] A power bus interface circuit is configured to interface with a power bus and provide power to the terminal device.

[0253] The controller includes at least one processor; and

[0254] A memory storing controller instructions, which, when executed by the at least one processor, cause the controller to:

[0255] Obtain a configuration list of battery packs installed in the battery system, wherein the first entry corresponds to the first battery pack;

[0256] When the first entry in the configuration list has the highest priority position in the configuration list, the first battery pack is configured to be used as the main battery pack of the battery system, wherein the highest priority position indicates that the first battery pack is installed before any other active battery pack in the battery system;

[0257] The configuration list is revised when a second battery pack is installed or removed from the battery system; and

[0258] The configuration list is repeatedly broadcast to all installed battery packs via the communication interface circuit through the communication channel.

[0259] Example 2: According to the first battery pack of Example 1, wherein the controller instructions, when executed by the at least one processor, further cause the controller to:

[0260] When a third battery pack is added to the battery system, the insertion of the third battery pack is detected; and

[0261] A third entry is created for the third battery pack in the configuration list, wherein the third entry is located at the bottom of the configuration list.

[0262] Example 3: According to the first battery pack of Example 2, wherein the controller instructions, when executed by the at least one processor, further cause the controller to:

[0263] When the second battery pack is removed from the battery system, the removal of the second battery pack is detected; and

[0264] Delete the second entry for the second battery pack in the configuration list.

[0265] Example 4: According to the first battery pack of Example 3, wherein the controller instructions, when executed by the at least one processor, further cause the controller to:

[0266] Advance the list position of the third entry of the third battery pack in the configuration list.

[0267] Example 5: According to the first battery pack of Example 1, wherein the controller instructions, when executed by the at least one processor, further cause the controller to:

[0268] When the first entry of the first battery pack is not in the highest priority position in the configuration list, the first battery pack is configured to be used as the first slave battery pack.

[0269] Example 6: According to the first battery pack of Example 5, wherein the controller instructions, when executed by the at least one processor, further cause the controller to:

[0270] When another battery pack is removed from the battery system and the first entry is moved to the highest priority position in the configuration list, the first battery pack is configured to be used as the main battery pack.

[0271] Example 7: According to the first battery pack of Example 1, wherein the communication channel includes a Controller Area Network (CAN) bus, and wherein the controller instructions, when executed by the at least one processor, further cause the controller to:

[0272] The identifier (ID) of the first battery pack is obtained using the SAE J1939 address declaration procedure, wherein the ID is included in the first entry.

[0273] Example 8: According to the first battery pack of Example 5, wherein the controller instructions, when executed by the at least one processor, further cause the controller to:

[0274] When the first battery pack is used as the first slave battery pack:

[0275] Receive a first request from the main battery pack; and

[0276] In response to receiving the first request, the main battery pack responds to the first request.

[0277] Example 9: According to the first battery pack of Example 1, wherein the controller instructions, when executed by the at least one processor, further cause the controller to:

[0278] When the first battery pack is used as the main battery pack:

[0279] Send a second request to the second slave battery pack; and

[0280] In response to sending, a response message is received from the second battery pack.

[0281] Example 10: According to the first battery pack of Example 1, wherein the controller instructions, when executed by the at least one processor, further cause the controller to:

[0282] When the first battery pack is removed from and reinserted into the battery system, a join request is sent via the communication channel; and

[0283] The configuration list is received with a fourth entry at the bottom position, wherein the fourth entry is associated with the first battery pack.

[0284] Example 11: According to the first battery pack of Example 1, the first battery pack includes non-volatile memory, and wherein the controller instructions, when executed by the at least one processor, further cause the controller to:

[0285] Battery pack information is stored in the non-volatile memory; and

[0286] When the first battery pack is removed from the battery system and reinserted into the battery system, the battery pack information is retained.

[0287] Example 12: According to the first battery pack of Example 2, wherein the controller instructions, when executed by the at least one processor, further cause the controller to:

[0288] When the first battery pack is used as the main battery pack:

[0289] The communication interface circuit transmits repeated broadcast messages to all the installed battery packs via the communication channel; and

[0290] When no duplicate broadcast messages are received from the third battery pack, the third entry is removed from the configuration list.

[0291] Example 13: According to the first battery pack of Example 12, the repetitive broadcast message is sent periodically, and wherein the controller instructions, when executed by the at least one processor, further cause the controller to:

[0292] When a timer set to a predetermined time expires without receiving the repeated broadcast message, the third entry is removed from the configuration list.

[0293] Example 14 A battery system configured to power a terminal device and comprising a plurality of battery packs, the battery system comprising:

[0294] The first battery pack includes:

[0295] The first communication interface circuit is configured to interface to the Controller Area Network (CAN) bus;

[0296] A first controller, comprising at least one processor; and

[0297] A first memory stores controller instructions that, when executed by the at least one processor, cause the first controller to:

[0298] Obtain a configuration list of battery packs installed in the battery system, wherein the first entry corresponds to the first battery pack;

[0299] When the first entry in the configuration list has the highest priority position in the configuration list, the first battery pack is configured to be used as the main battery pack of the battery system, wherein the highest priority position indicates that the first battery pack is installed before any other active battery pack in the battery system;

[0300] When the first battery pack is used as the main battery pack, the configuration list is revised when a third battery pack is installed or removed from the battery system; and

[0301] The configuration list is repeatedly broadcast to all installed battery packs via the CAN bus through the first communication interface circuit; and

[0302] A second battery pack, wherein the second battery pack has the same electrical and electronic components as the first battery pack.

[0303] Example 15: The battery system according to Example 14, wherein the second battery pack includes:

[0304] The second communication interface circuit is configured to interface to the controller area network (CAN) bus;

[0305] A second controller, comprising one or more processors; and

[0306] A second memory stores controller instructions that, when executed by the one or more processors, cause the second controller to:

[0307] Obtain the configuration list of the battery packs installed in the battery system, wherein the second entry corresponds to the second battery pack;

[0308] When the second entry in the configuration list has the highest priority position in the configuration list, the second battery pack is configured to be used as the main battery pack of the battery system, wherein the highest priority position indicates that the second battery pack is installed before any other active battery pack in the battery system;

[0309] The configuration list is revised when the third battery pack is installed or removed from the battery system; and

[0310] The configuration list is repeatedly broadcast to all installed battery packs via the CAN bus through the second communication interface circuit.

[0311] Example 16: According to the battery system of Example 15, wherein the first controller instruction, when executed by the one or more processors, further causes the first controller to:

[0312] When the first entry is in the second position of the highest priority position in the configuration list, the first battery pack is configured to be used as the main battery pack when the second battery pack was previously used as the main battery pack.

[0313] Example 17 A method for powering a terminal device by a battery system, the method comprising:

[0314] Obtain a configuration list of battery packs installed in the battery system, wherein the first entry corresponds to the first battery pack;

[0315] When the first entry in the configuration list has the highest priority position in the configuration list, the first battery pack is configured to be used as the main battery pack of the battery system, wherein the highest priority position indicates that the first battery pack is installed before any other active battery pack in the battery system;

[0316] The configuration list is revised when a second battery pack is installed or removed from the battery system; and

[0317] The configuration list is repeatedly broadcast to all installed battery packs via a communication channel through a communication interface circuit.

[0318] Example 18, according to the method of Example 17, further includes:

[0319] When a third battery pack is added to the battery system, the insertion of the third battery pack is detected.

[0320] Create a third entry for the third battery pack in the configuration list, wherein the third entry is located at the bottom of the configuration list; and

[0321] In response to creation, the configuration list is broadcast via the communication channel to all installed battery packs configured in the battery system.

[0322] Example 19 The method according to Example 18 further includes:

[0323] When the second battery pack is removed from the battery system, the removal of the second battery pack is detected; and

[0324] Delete the second entry for the second battery pack in the configuration list.

[0325] Example 20, according to the method of Example 17, further includes:

[0326] When the first entry of the first battery pack is not in the highest priority position in the configuration list, the first battery pack is configured to be used as a slave battery pack.

[0327] Example 21: The method according to Example 20 further includes:

[0328] When another battery pack is removed from the battery system and the first entry is moved to the highest priority position in the configuration list, the first battery pack is configured to be used as the main battery pack.

[0329] Example 22 A battery system configured to power a terminal device and comprising a plurality of battery packs, the battery system comprising:

[0330] A power bus, which is coupled to the terminal device to provide power to the terminal device;

[0331] A communication channel, which is coupled to the plurality of battery packs;

[0332] The first battery pack includes:

[0333] A first communication interface circuit is configured to interface to the communication channel;

[0334] First discharge array;

[0335] First processor; and

[0336] A first memory stores computer-executable instructions that, when executed by the first processor, cause the first battery pack to:

[0337] Disable the first discharge array to prevent discharge from the first battery pack to the power bus;

[0338] Obtain the first open-circuit voltage measurement value of the first battery pack; and

[0339] The first open-circuit voltage measurement value is shared with the plurality of battery packs via the communication channel;

[0340] A first copy of the configuration list is maintained based on the first open-circuit voltage measurement and shared open-circuit voltage measurements from the plurality of battery packs; and

[0341] Enable the first discharge array to allow discharge to the power bus; and

[0342] The second battery pack includes:

[0343] A second communication interface circuit is configured to interface to the communication channel;

[0344] The second discharge array is electrically connected to the power bus of the battery system;

[0345] Second processor; and

[0346] A second memory stores computer-executable instructions that, when executed by a second processor, cause the second battery pack to:

[0347] Disable the second discharge array to prevent discharge from the second battery pack to the power bus;

[0348] Obtain the second open-circuit voltage measurement value of the second battery pack; and

[0349] The second open-circuit voltage measurement value is shared with the plurality of battery packs via the communication channel;

[0350] A second copy of the configuration list is maintained based on the second open-circuit voltage measurement and the shared open-circuit voltage measurement from the plurality of battery packs, wherein the configuration list is sorted based on decreasing open-circuit voltage measurements, and wherein the top member of the configuration list is designated as the main battery pack of the battery system; and

[0351] Enable the second discharge array to allow discharge to the power bus.

[0352] Example 23 The battery system according to Example 22 includes:

[0353] A third battery pack, wherein the third battery pack is installed in the battery system when the first battery pack and the second battery pack are discharged to the power bus, the third battery pack comprising:

[0354] A third communication interface circuit is configured to interface to the communication channel;

[0355] Third discharge array;

[0356] A third processor; and

[0357] A third memory stores computer-executable instructions that, when executed by the third processor, cause the third battery pack to:

[0358] Disable the third discharge array to prevent discharge from the third battery pack to the power bus;

[0359] Obtain the third open-circuit voltage measurement value of the third battery pack; and

[0360] The third open-circuit voltage measurement value is shared with the plurality of battery packs via the communication channel.

[0361] Example 24: According to the battery system of Example 23, wherein the third memory stores computer-executable instructions, which, when executed by the third processor, cause the third battery pack to:

[0362] The third copy of the configuration list is updated based on the third open-circuit voltage measurement and the shared open-circuit voltage measurement from the plurality of battery packs.

[0363] Example 25: The battery system according to Example 24, wherein the update occurs after the first battery pack and the second battery pack are disconnected from the battery system.

[0364] Example 26: The battery system according to Example 24, wherein the update occurs when the first battery pack and the second battery pack discharge to the power bus.

[0365] Example 27 A method for powering a terminal device by a battery system, the battery system including a plurality of previously installed battery packs, wherein the plurality of previously installed battery packs includes a main battery pack, the method comprising:

[0366] An additional battery pack is inserted into the battery system, establishing a first connection to the power bus and a second connection to the communication bus;

[0367] Interacting with the main battery pack via the additional battery pack; and

[0368] In response to the interaction, inrush current from the additional battery pack to one of the plurality of previously installed battery packs is prevented.

[0369] Example 28: The method according to Example 27, wherein the prevention includes:

[0370] The additional battery pack receives a first disable message from the main battery pack via the communication bus, wherein the first disable message commands the additional battery pack to disable charging and discharging via the power bus.

[0371] Example 29: The method described in Example 27 further includes:

[0372] In response to insertion, the additional battery pack provides an insertion instruction via the communication bus, wherein the insertion instruction includes the identifier (ID) of the additional battery pack.

[0373] Example 30: The method according to Example 29 further includes:

[0374] In response to providing, a configuration message is received, wherein the configuration message includes a configuration list indicating the configuration of the battery system, wherein the entry for the additional battery pack in the configuration list is located at the bottom of the configuration list, and wherein the additional battery pack is used as a slave battery pack in the battery system.

[0375] Example 31: The method according to Example 30 further includes:

[0376] The additional battery pack obtains first battery state information about the battery cells located at the additional battery pack, wherein the first battery state information includes a first state of charge (SoC) value of the battery cells;

[0377] The additional battery pack receives a first status request for the first battery status information from the main battery pack via the communication bus; and

[0378] In response to receiving the first status request, the first SoC value is sent to the main battery pack via the communication bus.

[0379] Example 32, according to the method of Example 31, further includes:

[0380] Receive the first SoC value from the additional battery pack;

[0381] Based on the first SoC value, the main battery pack determines whether to initiate charging balancing, including the additional battery pack; and

[0382] In response to the confirmation, the main battery pack sends an enable message to the auxiliary battery pack to configure the auxiliary battery pack with the power bus.

[0383] Example 33, according to the method of Example 32, further includes:

[0384] The additional battery pack receives the enable message from the main battery pack via the communication bus; and

[0385] The additional battery pack is configured to interact with the power bus according to the enable message.

[0386] Example 34: According to the method described in Example 32, determining whether to initiate charging balancing includes:

[0387] When the first SoC value is a high SoC value relative to the plurality of previously installed battery packs, the main battery pack sends the enable message, which commands the additional battery packs to enable the discharge of the battery cells onto the power bus; and

[0388] When the first SoC value is a low SoC value relative to the plurality of previously installed battery packs, the main battery pack sends the enable message, which commands the additional battery pack to enable charging of the battery cells from the power bus.

[0389] Example 35: According to the method described in Example 34, the method of determining whether to initiate charging balancing further includes:

[0390] When the first SoC value is equal to the low SoC value and the difference between the high SoC value and the low SoC value is greater than a predetermined amount, the enable message is sent, which commands the additional battery pack to enable the charging of the battery cell from the power bus through a converter located at the additional battery pack.

[0391] Example 36: The method according to Example 34 further includes:

[0392] After receiving the enable message from the main battery pack by the additional battery pack, the second SoC value of the battery cell is obtained;

[0393] The additional battery pack receives a second status request for the second battery status information from the main battery pack via the communication bus; and

[0394] In response to receiving the second status request, the second SoC value is sent to the main battery pack via the communication bus.

[0395] Example 37: The method described in Example 36 further includes:

[0396] Receive the second SoC value from the additional battery pack;

[0397] When the first SoC value is equal to the high SoC value and the second SoC value is lower than the first threshold, the main battery pack sends a second disable message, which commands the auxiliary battery pack to terminate the discharge of the battery cell to the power bus; and

[0398] When the first SoC value is equal to the low SoC value and the second SoC value is greater than the second threshold, the main battery pack sends the second disable message, which commands the auxiliary battery pack to terminate charging of the battery cell from the power bus.

[0399] Example 38: The method described in Example 27, wherein the communication bus includes a Controller Area Network (CAN) bus.

[0400] Example 39 A first battery pack configured to be installed in a battery system to power a terminal device, wherein all installed battery packs in the battery system have identical electrical and electronic components, the first battery pack comprising:

[0401] A communication interface circuit, configured to interface to a communication channel;

[0402] A power bus interface circuit is configured to interface with a power bus and provide power to the terminal device.

[0403] The controller includes at least one processor; and

[0404] A memory storing controller instructions, which, when executed by the at least one processor, cause the controller to:

[0405] When the first battery pack is inserted into the battery system, an insertion instruction is generated via the communication channel, wherein the insertion instruction includes the identifier (ID) of the first battery pack.

[0406] In response to generating the insertion instruction, a disable message is received from the main battery pack of the battery system via the communication interface circuit through the communication channel; and

[0407] In response to receiving the disable message, charging and discharging via the power bus are disabled.

[0408] Example 40: According to the first battery pack of Example 39, wherein the controller instructions, when executed by the at least one processor, further cause the controller to:

[0409] In response to generating the insertion instruction, a configuration message is received, wherein the configuration message includes a configuration list indicating the configuration of the battery system, wherein the entry for the first battery pack in the configuration list is located at the bottom of the configuration list, and wherein the first battery pack is used as a slave battery pack in the battery system.

[0410] Example 41: According to the first battery pack of Example 40, wherein the controller instructions, when executed by the at least one processor, further cause the controller to:

[0411] Obtain battery status information about the battery cells located in the first battery pack, wherein the battery status information includes the state of charge (SoC) value of the battery cells;

[0412] Receive a status request for the battery status information from the main battery pack via the communication channel; and

[0413] In response to receiving the status request, the SoC value is sent to the main battery pack via the communication channel.

[0414] Example 42: According to the first battery pack of Example 41, wherein the controller instructions, when executed by the at least one processor, further cause the controller to:

[0415] In response to sending the SoC value, an enable message is received from the main battery pack via the communication channel; and

[0416] The power bus interface circuit is configured to interact with the power bus according to the enable message.

[0417] Example 43 A battery system configured to power a terminal device and comprising a plurality of battery packs, the battery system comprising:

[0418] The first battery pack includes:

[0419] A power bus interface circuit is configured to interface with a power bus and provide power to the terminal device.

[0420] The first communication interface circuit is configured to interface to the Controller Area Network (CAN) bus;

[0421] A first controller, comprising at least one processor; and

[0422] A first memory stores controller instructions that, when executed by the at least one processor, cause the first controller to:

[0423] When the first battery pack is inserted into the battery system, an insertion instruction is provided via the CAN bus, wherein the insertion instruction includes the identifier (ID) of the first battery pack;

[0424] In response to the provision, a first disable message is received from the main battery pack of the battery system via the first communication interface circuit through the CAN bus; and

[0425] In response to receiving, disable charging and discharging via the power bus; and

[0426] The second battery pack serves as the main battery pack of the battery system.

[0427] Example 44: The battery system according to Example 43, wherein a first memory stores controller instructions, which, when executed by the at least one processor, cause the first controller to:

[0428] Obtain battery status information about the battery cells located in the first battery pack, wherein the battery status information includes the state of charge (SoC) value of the battery cells;

[0429] Receive status requests for battery status information from the main battery pack via the CAN bus; and

[0430] In response to receiving the status request, the SoC value is sent to the main battery pack via the CAN bus.

[0431] Example 45: The battery system according to Example 44, wherein the second battery pack comprises:

[0432] A second communication interface circuit is configured to interface to the CAN bus;

[0433] A second controller, comprising one or more processors; and

[0434] A second memory stores controller instructions that, when executed by the one or more processors, cause the second controller to:

[0435] Receive the SoC value from the first battery pack;

[0436] Based on the SoC value, the main battery pack determines whether to initiate charging balancing, including the first battery pack; and

[0437] In response to determining whether to initiate charging balancing, the main battery sends an enable message to the first battery pack to configure the first battery pack with the power bus.

[0438] Example 46: The battery system according to Example 45, wherein the second memory stores controller instructions, which, when executed by the one or more processors, further cause the second controller to:

[0439] When the SoC value is high relative to multiple previously installed battery packs, the main battery pack sends the enable message, which commands the first battery pack to enable the discharge of the battery cells onto the power bus; and

[0440] When the SoC value is low relative to the plurality of previously installed battery packs, the main battery pack sends the enable message, which commands the first battery pack to enable charging of the battery cells from the power bus.

[0441] Example 47 A first battery pack configured to be installed in a battery system to power a terminal device, wherein all installed battery packs in the battery system have identical electrical and electronic components, the first battery pack comprising:

[0442] One or more battery cells;

[0443] A communication interface circuit, configured to interface to a communication channel;

[0444] A power bus interface circuit is configured to interface with a power bus and provide power to the terminal device.

[0445] The controller includes at least one processor; and

[0446] A memory storing controller instructions, which, when executed by the at least one processor, cause the controller to:

[0447] The first battery pack is identified as the main battery pack of the battery system.

[0448] When the first battery pack receives a first fault notification message from the second battery pack via the communication interface circuit through the communication channel and when an additional battery pack is needed, it determines whether the first backup battery pack is available, wherein the first fault notification message indicates a first catastrophic failure at the second battery pack;

[0449] When the first backup battery pack is the only backup battery pack and when the additional battery pack is needed, a first activation message is sent to the first backup battery pack via the communication channel, wherein the first activation message commands the first backup battery pack to discharge to the power bus; and

[0450] When the first battery pack receives the first fault notification message from the second battery pack, it sends a first disable message to the second battery pack through the communication channel, wherein the first disable message commands the second battery pack to terminate discharging to the power bus.

[0451] Example 48: According to the first battery pack of Example 47, wherein the controller instructions, when executed by the at least one processor, further cause the controller to:

[0452] When the first battery pack is the main battery pack of the battery system:

[0453] When no backup battery pack is available, a degradation alarm message is sent to the terminal device.

[0454] Example 49: According to the first battery pack of Example 48, wherein the controller instructions, when executed by the at least one processor, further cause the controller to:

[0455] When the first battery pack is the main battery pack of the battery system:

[0456] When the degraded operation becomes unacceptable to the terminal device, the battery system is shut down.

[0457] Example 50: According to the first battery pack of Example 49, wherein the controller instructions, when executed by the at least one processor, further cause the controller to:

[0458] When the first battery pack is the main battery pack of the battery system:

[0459] The command discharges all battery packs of the battery system onto the power bus.

[0460] Example 51: According to the first battery pack of Example 47, wherein the controller instructions, when executed by the at least one processor, further cause the controller to:

[0461] When the first battery pack is the main battery pack of the battery system:

[0462] When multiple backup battery packs are available, the backup battery pack with the highest SoC is selected from the multiple backup battery packs, wherein the highest SoC backup battery pack is characterized by the highest state-of-charge (SoC) value of all the multiple backup battery packs; and

[0463] A second enable message is sent to the highest SoC backup battery pack, wherein the second enable message commands the highest SoC backup battery pack to discharge onto the power bus.

[0464] Example 52 is based on the first battery pack of Example 47, wherein the communication channel includes a controller area network (CAN) bus.

[0465] Example 53: According to the first battery pack of Example 47, wherein the controller instructions, when executed by the at least one processor, further cause the controller to:

[0466] When the first battery pack is the main battery pack of the battery system:

[0467] Monitor the one or more battery cells;

[0468] Based on monitoring, determine whether a second catastrophic failure has occurred;

[0469] When the second catastrophic failure has occurred, determine whether the first backup battery pack is available;

[0470] When the first battery pack is available, the first enable message is sent to the first backup battery pack, wherein the first enable message commands the first backup battery pack to discharge to the power bus; and

[0471] Disable itself to prevent discharge onto the power bus.

[0472] Example 54: According to the first battery pack of Example 47, wherein the controller instructions, when executed by the at least one processor, further cause the controller to:

[0473] When the first battery pack is the slave battery pack of the battery system:

[0474] Monitor the one or more battery cells;

[0475] Based on monitoring, determine whether a third catastrophic failure has occurred; and

[0476] When the third catastrophic failure has occurred, a second failure notification message is sent to the main battery pack of the battery system.

[0477] Example 55: According to the first battery pack of Example 54, wherein the controller instructions, when executed by the at least one processor, further cause the controller to:

[0478] In response to sending, a second disable message is received from the main battery pack; and

[0479] In response to receiving, the discharge to the power bus is terminated.

[0480] Example 56: According to the first battery pack of Example 47, wherein the controller instructions, when executed by the at least one processor, further cause the controller to:

[0481] When the first battery pack detects an internal catastrophic failure, it internally terminates the discharge to the power bus;

[0482] When at least one backup battery pack is available, activate one of the at least one backup battery pack;

[0483] When no backup battery pack is available, a degradation alarm message is sent to the terminal device; and the battery pack continues to operate as the main battery pack of the battery system.

[0484] Example 57: According to the first battery pack of Example 47, wherein the controller instructions, when executed by the at least one processor, further cause the controller to:

[0485] When the first battery pack detects an internal catastrophic failure, it internally terminates discharge to the power bus; and

[0486] The battery pack is reassigned from one of the battery packs to a new main battery pack.

[0487] Example 58: According to the first battery pack of Example 47, wherein the controller instructions, when executed by the at least one processor, further cause the controller to:

[0488] When the first battery pack fails to receive any message from the second battery pack via the communication channel, an attempt is made to disable the second battery pack to prevent discharge to the power bus; and

[0489] Adjust the power level of the power bus of the terminal device.

[0490] Example 59 A method for powering a terminal device by a battery system, the method comprising:

[0491] When the main battery pack receives a fault notification message from the slave battery pack via a communication channel and when an additional battery pack is needed, it determines whether a first backup battery pack is available, wherein the fault notification message indicates a catastrophic failure at the slave battery pack.

[0492] When the first backup battery pack is the only backup battery pack and when the additional battery pack is needed, the main battery pack sends an enable message to the first backup battery pack, wherein the enable message commands the first backup battery pack to discharge to the power bus; and

[0493] When the main battery pack receives the fault notification message from the slave battery pack, the main battery pack sends a disable message to the slave battery pack, wherein the disable message commands the slave battery pack to terminate discharging to the power bus.

[0494] Example 60: The method according to Example 59 includes:

[0495] When the degraded operation becomes unacceptable to the terminal device, the battery system is shut down.

[0496] Example 61: The method according to Example 59 includes:

[0497] When multiple backup battery packs are available, the backup battery pack with the highest SoC is selected from the multiple backup battery packs, wherein the highest SoC backup battery pack is characterized by the highest state-of-charge (SoC) value of all the multiple backup battery packs; and

[0498] Send the enable message to the highest SoC backup battery pack, wherein the enable message commands the highest SoC backup battery pack to discharge onto the power bus.

[0499] Example 62: The method according to Example 59 includes:

[0500] The battery pack monitors one or more battery cells;

[0501] Based on monitoring, determine whether the aforementioned catastrophic failure has occurred; and

[0502] When the catastrophic failure has occurred, a failure notification message is sent to the main battery pack of the battery system.

[0503] Example 63: The method according to Example 62 includes:

[0504] In response to sending, the slave battery pack receives the disable message from the master battery pack; and

[0505] In response to receiving the disable message, discharge to the power bus is terminated.

[0506] Example 64 A battery system configured to power a terminal device and comprising a plurality of battery packs, the battery system comprising:

[0507] From the battery pack; and

[0508] The main battery pack includes:

[0509] The first communication interface circuit is configured to interface to the Controller Area Network (CAN) bus;

[0510] A first controller, comprising at least one processor; and

[0511] A first memory stores controller instructions that, when executed by the at least one processor, cause the first controller to:

[0512] When the main battery pack receives a fault notification message from the slave battery pack via the first communication interface circuit through the CAN bus and when an additional battery pack is needed, it determines whether the first backup battery pack is available, wherein the fault notification message indicates a catastrophic failure at the slave battery pack.

[0513] When the first backup battery pack is the only backup battery pack and when the additional battery pack is needed, an enable message is sent to the first backup battery pack, wherein the enable message commands the first backup battery pack to discharge to the power bus; and

[0514] When the main battery pack receives the fault notification message from the slave battery pack, it sends a disable message to the slave battery pack, wherein the disable message commands the slave battery pack to terminate discharging to the power bus.

[0515] Example 65: The battery system according to Example 64, wherein a first memory stores controller instructions, which, when executed by the at least one processor, cause the first controller to:

[0516] When the degraded operation becomes unacceptable to the terminal device, the battery system is shut down.

[0517] Example 66: The battery system according to Example 65, wherein a first memory stores controller instructions, which, when executed by the at least one processor, cause the first controller to:

[0518] The command discharges all battery packs of the battery system onto the power bus.

[0519] Example 67: According to the battery system of Example 64, a first memory stores controller instructions, which, when executed by the at least one processor, cause the first controller to:

[0520] When multiple backup battery packs are available, the backup battery pack with the highest SoC is selected from the multiple backup battery packs, wherein the highest SoC backup battery pack is characterized by the highest state-of-charge (SoC) value of all the multiple backup battery packs; and

[0521] Send the enable message to the highest SoC backup battery pack, wherein the enable message commands the highest SoC backup battery pack to discharge onto the power bus.

[0522] Example 68: The battery system according to Example 64, wherein the slave battery pack includes:

[0523] The second communication interface circuit is configured to interface to the Controller Area Network (CAN) bus;

[0524] The second controller includes one or more processors;

[0525] One or more battery cells; and

[0526] A second memory stores controller instructions that, when executed by the one or more processors, cause the first controller to:

[0527] Monitor the one or more battery cells;

[0528] Based on monitoring, determine whether the aforementioned catastrophic failure has occurred; and

[0529] When the catastrophic failure has occurred, a failure notification message is sent to the main battery pack of the battery system.

[0530] Example 69: The battery system according to Example 68, wherein the second memory stores controller instructions, which, when executed by the one or more processors, cause the second controller to:

[0531] In response to sending the fault notification message, the disable message is received from the main battery pack; and

[0532] In response to receiving the disable message, discharge to the power bus is terminated.

[0533] Example 70: A method for supplying power to a terminal device by a battery system, the battery system comprising multiple battery packs, the method comprising:

[0534] The main battery pack of the battery system collects battery status information from the plurality of battery packs, wherein the plurality of battery packs includes the main battery pack and all slave battery packs, and wherein the battery status information includes state of charge (SoC) data.

[0535] Based on the battery status information, the main battery pack determines whether a first subset of the plurality of battery packs needs to be charged for balancing.

[0536] The main battery pack selects a first balance type from a first subset of balance types suitable for the plurality of battery packs; and

[0537] The first balance type is selected by the main battery pack via the power bus until the desired SoC value is obtained for the first subset of the plurality of battery packs.

[0538] Example 71 is based on the method described in Example 70, wherein the multiple balancing types include converter balancing technology, direct balancing technology, and interleaved balancing technology.

[0539] Example 72: The method according to Example 71 includes:

[0540] The main battery pack identifies a first battery pack with a high SoC value from the collected battery state information; and

[0541] The high SoC value is compared by the main battery pack with the SoC values ​​of all remaining battery packs.

[0542] Example 73: The method according to Example 72 includes:

[0543] In response to the comparison, when the first SoC difference between the first battery pack and the second battery pack is greater than a first predetermined amount, the main battery pack activates the converter balancing technology for the first battery pack and the second battery pack.

[0544] Example 74 The method according to Example 73 includes:

[0545] The main battery pack sends a first enable message to the first battery pack via a communication channel, wherein the first enable message commands the first battery pack to discharge via the power bus; and

[0546] The main battery pack sends a second enable message to the second battery pack via the communication channel, wherein the second enable message commands the second battery pack to enable its converter and charge from the power bus.

[0547] Example 75: The method according to Example 73 includes:

[0548] In response to the comparison, when the second SoC difference between the first battery pack and the third battery pack is greater than a first predetermined amount, the main battery pack activates the converter balancing technology for the first battery pack, the second battery pack and the third battery pack.

[0549] Example 76: According to the method described in Example 75, one of the first battery pack, the second battery pack, and the third battery pack is used as the main battery pack of the battery system.

[0550] Example 77 The method according to Example 72 includes:

[0551] In response to the comparison, when the third SoC difference between the first battery pack and the fourth battery pack is less than a second predetermined amount, the main battery pack initiates the direct balancing technology for the first battery pack and the fourth battery pack.

[0552] Example 78: The method according to Example 77 includes:

[0553] The main battery pack sends a third enable message to the first battery pack via a communication channel, wherein the third enable message commands the first battery pack to discharge via the power bus; and

[0554] The main battery pack sends a fourth enable message to the fourth battery pack through the communication channel, wherein the fourth enable message commands the fourth battery pack to charge from the power bus.

[0555] Example 79: According to the method described in Example 77, one of the first battery pack and the fourth battery pack is used as the main battery pack.

[0556] Example 80: The method according to Example 72 includes:

[0557] In response to the comparison, when the fourth SoC difference between the first battery pack and the fifth battery pack is less than the third predetermined amount, the fifth SoC difference between the first battery pack and the sixth battery pack is greater than the fourth predetermined amount, and the sixth SoC difference between the first battery pack and the seventh battery pack is greater than the fourth predetermined amount, the interleaved balancing technology is activated for the first battery pack, the fifth battery pack, and the sixth battery pack.

[0558] Example 81 The method according to Example 80 includes:

[0559] The main battery pack sends a fifth enable message to the first battery pack through a communication channel, wherein the fifth enable message commands the first battery pack to discharge through the power bus;

[0560] The main battery pack sends a sixth enable message to the fifth battery pack via the communication channel, wherein the sixth enable message commands the fifth battery pack to charge from the power bus, and wherein the direct balancing technology is applied to both the first and fifth battery packs; and

[0561] The main battery pack sends a seventh enable message to the sixth battery pack via the communication channel, wherein the seventh enable message commands the sixth battery pack to enable its converter and charge from the power bus, wherein the converter balancing technology is applied to the first battery pack and the sixth battery pack.

[0562] Example 82: The method according to Example 81 includes:

[0563] Obtain the current SoC values ​​of the fifth battery pack and the sixth battery pack; and

[0564] In response to the acquisition, when an eighth difference between the first current SoC value of the fifth battery pack and the second current SoC value of the sixth battery pack is greater than a fifth predetermined value, the direct balancing technology is switched from the first battery pack and the sixth battery pack to the first battery pack and the seventh battery pack.

[0565] Example 83: The method according to Example 82 includes:

[0566] The main battery pack sends an eighth enable message to the fifth battery pack via the communication channel, wherein the eighth enable message commands the fifth battery pack to activate its converter and charge from the power bus, wherein converter balancing technology is applied to the first battery pack and the fifth battery pack; and

[0567] The main battery pack sends a ninth enable message to the sixth battery pack via the communication channel, wherein the ninth enable message commands the sixth battery pack to disable its converter and charge from the power bus, wherein the direct balancing technology is applied to both the first battery pack and the sixth battery pack.

[0568] Example 84: According to the method described in Example 75, one of the first battery pack, the fifth battery pack, and the sixth battery pack is used as the main battery pack of the battery system.

[0569] Example 85: The method according to Example 70 further includes:

[0570] The main battery pack obtains the current SoC value from the plurality of battery packs;

[0571] Based on the current SoC value, the main battery pack determines whether a second subset of the plurality of battery packs needs charging balancing.

[0572] The main battery pack selects a second balance type from a plurality of balance types suitable for a second subset of the plurality of battery packs, wherein the first balance type and the second balance type are different; and

[0573] The second balance type is selected by the main battery pack for the second subset of the plurality of battery packs.

[0574] Example 86: The method according to Example 70, wherein the application includes:

[0575] Obtain the safety interlock indicator and wake-up indicator; and

[0576] The application is enabled only when the safety interlock indicator indicates that it is on and the wake-up indicator indicates that it is off.

[0577] Example 87 A first battery pack configured to be installed in a battery system to power a terminal device, wherein all installed battery packs in the battery system have identical electrical and electronic components, the first battery pack comprising:

[0578] A communication interface circuit, configured to interface to a communication channel;

[0579] A power bus interface circuit is configured to interface with a power bus and provide power to the terminal device.

[0580] The controller includes at least one processor; and

[0581] A memory storing controller instructions, which, when executed by the at least one processor, cause the controller to:

[0582] When the first battery pack is used as the main battery pack of the battery system:

[0583] Battery status information is collected from multiple battery packs, wherein the multiple battery packs include the main battery pack and all slave battery packs, and wherein the battery status information includes state of charge (SoC) data.

[0584] Based on the battery status information, determine whether a first subset of the multiple battery packs needs to be charged for balancing.

[0585] Select a first balance type from a plurality of balance types suitable for the first subset of the plurality of battery packs; and

[0586] The first balance type selected by the application is applied until the desired SoC value of the first subset of the plurality of battery packs is obtained.

[0587] Example 88: According to the first battery pack of Example 87, wherein the memory stores controller instructions, which, when executed by the at least one processor, cause the controller to:

[0588] Identify the first battery pack with a high SoC value from the collected battery state information; and

[0589] The high SoC value is compared with the SoC values ​​of all remaining battery packs.

[0590] Example 89: According to the first battery pack of Example 88, wherein the memory stores controller instructions, which, when executed by the at least one processor, cause the controller to:

[0591] In response to the comparison, when the first SoC difference between the first battery pack and the second battery pack is greater than a first predetermined amount, the main battery pack initiates converter balancing technology for the first battery pack and the second battery pack.

[0592] Example 90: According to the first battery pack of Example 88, wherein the memory stores controller instructions, which, when executed by the at least one processor, cause the controller to:

[0593] In response to the comparison, when the third SoC difference between the first battery pack and the fourth battery pack is less than the second predetermined amount, the main battery pack initiates direct balancing technology for the first battery pack and the fourth battery pack.

[0594] Example 91: According to the first battery pack of Example 88, wherein the memory stores controller instructions, which, when executed by the at least one processor, cause the controller to:

[0595] In response to the comparison, when the fourth SoC difference between the first battery pack and the fifth battery pack is less than a third predetermined amount, the fifth SoC difference between the first battery pack and the sixth battery pack is greater than a fourth predetermined amount, and the sixth SoC difference between the first battery pack and the seventh battery pack is greater than the fourth predetermined amount, the staggered balancing technology is activated for the first battery pack, the fifth battery pack, and the sixth battery pack.

[0596] Example 92 A battery system configured to power a terminal device and comprising a plurality of battery packs, the battery system comprising:

[0597] Multiple from battery packs; and

[0598] The main battery pack includes:

[0599] The first communication interface circuit is configured to interface to the Controller Area Network (CAN) bus;

[0600] The controller includes at least one processor; and

[0601] A memory storing controller instructions, which, when executed by the at least one processor, cause the controller to:

[0602] Battery status information is collected from all battery packs of the battery system, wherein all battery packs include the main battery pack and the plurality of slave battery packs, and wherein the battery status information includes state of charge (SoC) data;

[0603] Based on the battery status information, determine whether a first subset of all battery packs needs to be charged and balanced.

[0604] Select a first balance type from a plurality of balance types suitable for the first subset of the entire battery pack; and

[0605] Apply the selected first balance type until the desired SoC value of the first subset of the entire battery pack is obtained.

[0606] Example 93: The battery system according to Example 92, wherein the memory stores controller instructions, which, when executed by the at least one processor, cause the controller to:

[0607] Identify a first battery pack with a high SoC value from the collected battery state information, wherein the plurality of batteries are described; and

[0608] The high SoC value is compared with the SoC values ​​of all remaining battery packs.

[0609] Example 94: The battery system according to Example 93, wherein the memory stores controller instructions, which, when executed by the at least one processor, cause the controller to:

[0610] In response to comparison:

[0611] When the first SoC difference between the first battery pack and the second battery pack is greater than the first predetermined amount, the converter balancing technology is activated for the first battery pack and the second battery pack.

[0612] When the first SoC difference between the first battery pack and the second battery pack is less than a second predetermined amount, direct balancing technology is initiated for the first battery pack and the second battery pack; and

[0613] When the first SoC difference between the first battery pack and the second battery pack is less than the second predetermined amount, the second SoC difference between the first battery pack and the third battery pack is greater than the first predetermined amount, and the third SoC difference between the first battery pack and the fourth battery pack is greater than the first predetermined amount, the interleaved balancing technology is activated for the first battery pack, the second battery pack, the third battery pack and the fourth battery pack.

[0614] Example 95 A method comprising:

[0615] A computing device having one or more processors receives a first reading of the state of charge (SOC) of each of a plurality of battery packs, wherein the plurality of battery packs includes at least a first group of one or more battery packs and a second group of one or more battery packs;

[0616] Based on a first reading of the State of Charge (SOC) received from each of the plurality of battery packs, and based on an identifier of a minimum level of the first SOC reading and a second minimum level of the first SOC reading, the following is identified by the computing device:

[0617] The first group is the lowest level of the first reading with the SOC, and

[0618] The second group is the second lowest level of the first reading having the SOC;

[0619] The computing device generates a first list comprising the first group and the second group based on the identifiers of the lowest level and the second lowest level.

[0620] The computing device determines the first SOC variability of the first list based on the first reading of the SOC of the first group and based on the first reading of the SOC of the second group;

[0621] The computing device determines, based on the first SOC variability, that the first SOC variability does not meet the SOC variability threshold;

[0622] The computing device uses the first reading of the SOC of the second group to establish a first SOC threshold;

[0623] The charging of the first group by the computing device and via the charge array increases the SOC of the first group;

[0624] The computing device receives a second reading of the SOC of each of the plurality of battery packs;

[0625] The computing device determines, based on a second reading of the SOC of the first group, that the second reading of the SOC of the first group satisfies the first SOC threshold.

[0626] Example 96, according to the method of Example 95, further includes:

[0627] The computing device determines the first SOC variability of the first list based on a second reading of the SOC of each of the plurality of battery packs received.

[0628] The computing device determines that the updated first SOC variability satisfies the SOC variability threshold.

[0629] Example 97, according to the method of Example 95, further includes receiving the first reading of the SOC of each of the plurality of battery packs:

[0630] The computing device identifies the main battery pack as one of the plurality of battery packs; and

[0631] The computing device receives the first reading of the SOC of each of the plurality of battery packs from the main battery pack.

[0632] Example 98 describes the method according to Example 95, wherein the charging further includes enabling a discharge array of the one or more battery packs from the charger to the first group of one or more battery packs via a converter.

[0633] Example 99: According to the method of Example 95, the plurality of battery packs further includes a third group of at least one or more battery packs, and the method further includes:

[0634] Based on the second reading of the SOC received for each of the plurality of battery packs, and based on an identifier of the lowest level of the second SOC reading and a second lowest level of the second SOC reading, the computing device identifies:

[0635] The first group and the second group are the lowest levels of the second reading with the SOC, and

[0636] The third group is the second lowest level of the second reading of the SOC;

[0637] A second list comprising the first group, the second group, and the third group is generated by the computing device based on the lowest level of the second reading of the SOC and the second lowest level of the second reading of the SOC;

[0638] The computing device determines the second SOC variability of the second list based on the second reading of the SOC of the first group, the second reading of the SOC of the second group, and the second reading of the SOC of the third group.

[0639] Example 100 is based on the method of Example 99, wherein generating the second list includes expanding the first list to include battery packs having a second minimum level for the second reading of the SOC.

[0640] Example 101: The method according to Example 99 further includes:

[0641] The computing device determines that the second SOC variability does not meet the SOC variability threshold;

[0642] The computing device establishes a second SOC threshold based on a second reading of the SOC from the third group;

[0643] By the computing device and via the charge array, such that:

[0644] The charging of the first group causes the SOC of the first group to increase, and

[0645] The charging of the second group causes the SOC of the second group to increase;

[0646] The computing device receives a third reading of the SOC of each of the plurality of battery packs;

[0647] The computing device determines that the third reading of the SOC of the first group and the third reading of the SOC of the second group each satisfy the second SOC threshold.

[0648] Example 102, according to the method of Example 101, further includes:

[0649] Perform one or more iterations as follows until the determined updated SOC variability of the plurality of battery packs satisfies the SOC variability threshold:

[0650] Identified by the computing device,

[0651] The Nth group of one or more battery packs of the plurality of backup battery devices, wherein the nth group has the lowest level of the previous SOC reading of the plurality of battery packs, and

[0652] The (N+1)th group of one or more battery packs of the plurality of backup battery devices, wherein the (N+1)th group has the second lowest level of the previous reading of the SOC of the plurality of battery packs, and

[0653] The computing device generates a list including the nth group and the (N+1)th group;

[0654] The computing device determines that the SOC variability of the list does not meet the SOC variability threshold;

[0655] The computing device uses the previous readings of the SOC from the N+1 groups to establish the SOC threshold;

[0656] The computing device and the charge array cause the charging of the n groups to increase the SOC of the n groups and satisfy the SOC threshold;

[0657] The computing device receives subsequent SOC readings for each of the plurality of battery packs; and

[0658] The updated SOC variability of the plurality of battery packs is determined by the computing device and based on subsequent readings of the SOC of each of the plurality of battery packs.

[0659] Example 103, according to the method of Example 95, further includes:

[0660] Before receiving the first reading of the SOC of each of the plurality of battery packs, it is determined that an interlock safety pin associated with the plurality of battery packs is set to ON, wherein the interlock safety pin allows the receipt of the first reading of the SOC of each of the plurality of battery packs to occur.

[0661] Example 104: The method according to Example 95 further includes:

[0662] Prior to initiating the charging process, it is determined that a wake-up pin associated with the plurality of battery packs is set to ON, wherein the wake-up pin allows the charging to occur.

[0663] Example 105 A method comprising:

[0664] The power requirements of the terminal device are received by a computing device having one or more processors and communicatively linked to the terminal device;

[0665] The computing device receives the first reading of the state of charge (SOC) of each of the multiple battery packs.

[0666] The plurality of battery packs includes at least a first group of one or more battery packs and a second group of one or more battery packs, and

[0667] The first SOC reading of the second group is greater than the first SOC reading of the first group;

[0668] The computing device determines the first SOC variability of the plurality of battery packs based on the first SOC reading received for each of the plurality of battery packs;

[0669] The computing device, based on the first SOC variability that does not meet the SOC variability threshold, determines to enable the second group to initially power the terminal device without simultaneously powering the terminal device through other battery packs in the plurality of battery packs; and

[0670] The second group supplies power to the terminal device to a first power level via the computing device and via a charge array, wherein supplying power to the terminal device reduces the SOC of the second group.

[0671] Example 106: The method according to Example 105 further includes:

[0672] The computing device receives a second reading of the SOC of each of the plurality of battery packs; and

[0673] The second SOC variability of the plurality of battery packs is determined by the computing device and based on a second reading of the SOC of each of the plurality of battery packs received.

[0674] The computing device determines that the second SOC variability satisfies the SOC variability threshold; and

[0675] The computing device and via one or more charge arrays cause the first group and the second group to supply power to the terminal device to a second power level, wherein supplying power to the terminal device causes a decrease in the second reading of the SOC of the first group and the second reading of the SOC of the second group.

[0676] Example 107 The method according to Example 105 further includes:

[0677] The computing device receives a second reading of the SOC of each of the plurality of battery packs.

[0678] The plurality of battery packs also includes a third group of one or more battery packs.

[0679] Wherein the second reading of the SOC in the second group and the second reading of the SOC in the third group are within each other's predetermined readings, and

[0680] The second reading of SOC in the second group and the second reading of SOC in the third group are each greater than the second reading of SOC in the first group.

[0681] The computing device determines the first SOC variability of the plurality of battery packs based on the first SOC reading received for each of the plurality of battery packs;

[0682] The computing device determines that the second SOC variability does not meet the SOC variability threshold; and

[0683] The computing device and one or more charge arrays cause the second group and the third group to simultaneously power the terminal device to a second power level, wherein powering the terminal device reduces the SOC of the second group and the SOC of the third group.

[0684] Example 108: According to the method of Example 105, receiving the first reading of the SOC of each of the plurality of battery packs further includes:

[0685] The computing device identifies the main battery pack as one of the plurality of battery packs; and

[0686] The computing device receives the first reading of the SOC of each of the plurality of battery packs from the main battery pack.

[0687] Example 109 A method comprising:

[0688] The power requirements of the terminal device are received by a computing device having one or more processors and communicatively linked to the terminal device;

[0689] The computing device receives the first reading of the state of charge (SOC) of each of the multiple battery packs.

[0690] The plurality of battery packs includes at least a first group of one or more battery packs and a second group of one or more battery packs.

[0691] The first SOC reading of the second group is greater than the first SOC reading of the first group, and

[0692] The computing device determines the first SOC variability of the plurality of battery packs based on the first SOC reading received for each of the plurality of battery packs;

[0693] The computing device determines that the first SOC variability does not meet the SOC variability threshold; and

[0694] The computing device and one or more charge arrays cause the second group to charge the first group, wherein charging the first group reduces the SOC of the second group and increases the SOC of the first group.

[0695] Example 110: The method according to Example 109 further includes:

[0696] The computing device receives a second reading of the SOC of each of the plurality of battery packs;

[0697] The second SOC variability of the plurality of battery packs is determined by the computing device and based on a second reading of the SOC of each of the plurality of battery packs received; and

[0698] The computing device determines that the second SOC variability satisfies the SOC variability threshold. Example 111: The method according to Example 110 further includes:

[0699] The terminal device is powered by the computing device and via one or more charge arrays, wherein the power supply reduces the state of charge (SOC) of the battery packs.

[0700] Example 112 The method according to Example 109 further includes:

[0701] The computing device receives a first reading of the state of health (SOH) of each of the plurality of battery packs, wherein the plurality of battery packs further includes a third group of one or more battery packs;

[0702] The computing device determines that the first reading of the SOH in the third group does not meet the SOH threshold; and

[0703] The computing device isolates the third group from power to the terminal device until subsequent SOC readings of each of the plurality of battery packs other than the one or more battery packs in the third group do not meet the SOC threshold.

[0704] Example 113 According to the method of Example 109, receiving the first reading of the SOC of each of the plurality of battery packs further includes:

[0705] The computing device identifies the main battery pack as one of the plurality of battery packs; and

[0706] The computing device receives the first reading of the SOC of each of the plurality of battery packs from the main battery pack.

[0707] Example 114 describes the method according to Example 109, wherein the second group charges the first battery pack via one or more of converter balancing, direct connection balancing, or interleaved balancing.

[0708] In some embodiments, the term "large" includes medium-sized battery embodiments and use cases. For example, medium-sized and large-scale applications are achieved through extensive descriptions herein.

[0709] While many of the systems and methods described herein involve lithium-ion battery storage chemistry, this disclosure is not limited thereto. In many cases, those skilled in the art will understand that other key chemistry used in rechargeable batteries can be suitably replaced with lithium-ion (Li-ion), nickel-cadmium (Ni-Cd), nickel metal hydride (Ni-MH), lead-acid, and other chemistry without substantially departing from the spirit of the solution. In some embodiments, the battery management systems disclosed herein can be included in these technology batteries to provide battery protection, improved efficiency, and a better user experience than previous battery technologies. Variations of lithium cobalt cathodes, such as nickel-cobalt-aluminum (NCA) and nickel-manganese-cobalt (NMC), may be ideal in electric vehicles and other applications. Other novel cathode chemistry, such as lithium manganese spinel (LMO) and lithium iron phosphate (LFP), can be used where appropriate. Furthermore, large battery packs offer lower system integration costs, particularly because they enable a reduction in the number of battery interconnects, thereby further improving battery pack reliability and providing a higher value proposition.

[0710] Those skilled in the art will understand that the exemplary embodiments disclosed herein can be implemented using a computer system having an associated computer-readable medium containing instructions for controlling the computer system. The computer system may include at least one computer, such as a microprocessor, a digital signal processor, and associated peripheral electronic circuitry.

Claims

1. A battery system configured to power a terminal device and comprising a plurality of battery packs, the battery system comprising: The first battery pack includes: The first communication interface circuit is configured to interface to the controller area network CAN bus. A first controller, comprising at least one processor; and A first memory stores controller instructions that, when executed by the at least one processor, cause the first controller to: Obtain a configuration list of battery packs installed in the battery system, wherein the first entry corresponds to the first battery pack; When the first entry in the configuration list has the highest priority position in the configuration list, the first battery pack is configured to be used as the main battery pack of the battery system, wherein the highest priority position indicates that the first battery pack is installed before any other active battery pack in the battery system; When the first battery pack is used as the main battery pack, the configuration list is revised when a third battery pack is installed or removed from the battery system; and The configuration list is repeatedly broadcast to all installed battery packs via the CAN bus through the first communication interface circuit; and A second battery pack, wherein the second battery pack has the same electrical and electronic components as the first battery pack.

2. The battery system according to claim 1, wherein the second battery pack comprises: A second communication interface circuit is configured to interface to the CAN bus; The second controller includes one or more processors; as well as A second memory stores controller instructions that, when executed by the one or more processors, cause the second controller to: Obtain the configuration list of the battery packs installed in the battery system, wherein the second entry corresponds to the second battery pack; When the second entry in the configuration list has the highest priority position in the configuration list, the second battery pack is configured to be used as the main battery pack of the battery system, wherein the highest priority position indicates that the second battery pack is installed before any other active battery pack in the battery system; The configuration list is revised when the third battery pack is installed or removed from the battery system; as well as The configuration list is repeatedly broadcast to all the installed battery packs via the CAN bus through the second communication interface circuit.

3. The battery system according to claim 1, wherein, The first battery pack is the main battery pack, and wherein, when the controller instructions are executed by the at least one processor, the controller further causes the controller to: When a third battery pack is added to the battery system, the insertion of the third battery pack is detected; and A third entry is created for the third battery pack in the configuration list, wherein the third entry is located at the bottom of the configuration list.

4. The battery system according to claim 3, wherein, When executed by the at least one processor, the controller instructions also cause the controller to: When the second battery pack is removed from the battery system, the removal of the second battery pack is detected; and Delete the second entry for the second battery pack from the configuration list.

5. The battery system according to claim 4, wherein, When executed by the at least one processor, the controller instructions also cause the controller to: Advance the list position of the third entry of the third battery pack in the configuration list.

6. The battery system according to claim 1, wherein, When executed by the at least one processor, the controller instructions also cause the controller to: When the battery pack is removed from the battery system and the first entry is moved to the highest priority position in the configuration list, the first battery pack is configured to be used as the main battery pack.

7. The battery system according to claim 1, wherein, When executed by the at least one processor, the controller instructions also cause the controller to: Obtain the identifier ID of the first battery pack, wherein the ID is included in the first entry.

8. The battery system according to claim 1, wherein, When executed by the at least one processor, the controller instructions also cause the controller to: When the first battery pack is used as the first slave battery pack: Receive a request from the main battery pack; and In response to receiving the request, the main battery pack responds to the request.

9. The battery system according to claim 1, wherein, When executed by the at least one processor, the controller instructions also cause the controller to: When the first battery pack is used as the main battery pack: Send a request to the second slave battery pack; and In response to sending, a response message is received from the second battery pack.

10. The battery system according to claim 1, wherein, When executed by the at least one processor, the controller instructions also cause the controller to: When the first battery pack is removed from the battery system and reinserted into the battery system, a join request is sent via the CAN bus; as well as The configuration list is received with subsequent entries at the bottom position of the configuration list, wherein the subsequent entries are associated with the first battery pack.

11. The battery system according to claim 1, wherein, The first battery pack includes non-volatile memory, and wherein the controller instructions, when executed by the at least one processor, further cause the controller to: Battery pack information is stored in the non-volatile memory; as well as When the first battery pack is removed from the battery system and reinserted into the battery system, the battery pack information is retained.

12. The battery system according to claim 3, wherein, When executed by the at least one processor, the controller instructions also cause the controller to: When the first battery pack is used as the main battery pack: The communication interface circuit sends repeated broadcast messages to all installed battery packs via the CAN bus; and When no duplicate broadcast messages are received from the third battery pack, the third entry is removed from the configuration list.

13. The battery system of claim 12, wherein the repetitive broadcast message is transmitted periodically, and wherein the controller instructions, when executed by the at least one processor, further cause the controller to: When a timer set to a predetermined time expires without receiving the repeated broadcast message, the third entry is removed from the configuration list.

Images