Centralized battery pack management

The centralized battery pack management system addresses the challenge of monitoring and managing voltage and temperature imbalances in battery packs during transit and storage by using a connected device to collect and display real-time data, allowing for effective balancing and prevention of safety hazards.

WO2024237910A1PCT designated stage expired Publication Date: 2024-11-21COULOMB SOLUTIONS INC
View PDF 3 Cites 0 Cited by

Patent Information

Application Number
PCT/US2023/022294
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Filing Date
2023-05-16
Publication Date
2024-11-21

AI Technical Summary

Technical Problem

Battery packs face challenges in monitoring voltage and temperature imbalances during transit and storage, making it difficult to manage and prevent safety hazards and damage.

Method used

A centralized battery pack management system that includes a battery management device connected to each battery pack, which collects real-time voltage and temperature data, sends it to a server, and displays it on user devices, allowing for remote monitoring and balancing of cell states of charge to address imbalances.

Benefits of technology

Enables effective remote management of battery packs, preventing voltage imbalances and temperature-related issues, ensuring safe storage and transit by providing real-time data for corrective actions.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure US2023022294_21112024_PF_FP_ABST
    Figure US2023022294_21112024_PF_FP_ABST
Patent Text Reader

Abstract

Aspects of a system include a first device connected to a first battery pack. The first battery pack comprises a first plurality of cells. The system includes at least one user device located remote to the first device. The at least one user device is configured to display real time information associated with the first battery pack. The system comprises a server in communication with the at least one user device and the first device. The server is configured to receive, from the first device, first real time voltage information associated with each of the first plurality of cells. The server is configured to populate an interface of the at least one user device based on the first real time voltage information. The populated interface displays data indicating whether a voltage imbalance exists amongst the first plurality of cells.
Need to check novelty before this filing date? Find Prior Art

Description

CENTRALIZED BATTERY PACK MANAGEMENTTECHNICAL FIELD

[0001] The present disclosure generally relates to the management of state for battery packs.BACKGROUND

[0002] Battery packs provide power to a variety of different systems and devices, such as to electric vehicles and energy storage systems. Such battery packs may spend a large quantity of time in transit (e.g., on a boat, truck, etc.) and / or in storage before they are integrated into the system or device to which they are to provide power. However, it may be difficult or impossible to monitor the status of the battery packs while they are in transit and / or in storage. For example, it may be difficult or impossible to monitor voltage and / or temperature information associated with the battery packs while they are in transit and / or in storage. Therefore, improvements in batteries for battery pack management are desirableDISCLOSURE

[0003] Systems, methods, and devices are disclosed herein for centralized battery pack management. Aspects of a system include a first device connected to a first battery pack. In some instances, the battery pack includes a first plurality of cells. In some instances, the system includes at least one user device located remote to the first device. The at least one user device displays real time information associated with the first battery pack. In some instances, the system includes a server in communication with the at least one user device and the first device. In some instances, the server receives, from the first device, first real time voltage information associated with each of the first plurality of cells. In some instances, the server populates an interface of the at least one user device based on the first real time voltage information. In some instances, the populated interface displays data indicating whether a voltage imbalance exists amongst the first plurality of cells.

[0004] Aspects of a method include receiving, from a first device connected to a battery pack comprising a first plurality of cells and at a server located remote to the first device, first real time voltage information associated with each of the first plurality of cells. In some instances, an interface of at least one user device located remote to the first device is populated. In someinstances, the interface is populated based on the first real time voltage information. Tn some instances, the populated interface displays data indicating whether a voltage imbalance exists amongst the first plurality of cells.

[0005] This Disclosure is provided to introduce a selection of concepts in a simplified form that are further described below in the Further Disclosure. This is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter. Furthermore, the claimed subject matter is not limited to features that solve any or all disadvantages noted in any part of this disclosure.BRIEF DESCRIPTION OF THE DRAWINGS

[0006] The present application is further understood when read in conjunction with the appended drawings. For the purpose of illustrating the subject matter, there are shown in the drawings exemplary aspects of the subject matter; however, the presently disclosed subject matter is not limited to the specific methods, devices, and systems disclosed. In the drawings:

[0007] FIG. 1 is an example battery pack.

[0008] FIG. 2 is an example battery pack connected to a battery management device.

[0009] FIG. 3 is an example battery pack connected to a battery management device.

[0010] FIG. 4 is an example system for centralized battery pack management.

[0011] FIG. 5 is an example system for storing battery packs.

[0012] FIG. 6 is an example system for storing battery packs.[0013JFIG. 7 is an example method for centralized battery pack management.

[0014] FIG. 8 is an example method for centralized battery pack management.

[0015] FIG. 9 is an example method for centralized battery pack management.

[0016] FIG. 10 is an example computing device.FURTHER DESCRIPTION

[0017] Battery packs may be purchased by customers (e.g., original equipment manufacturers (OEMs)). In some instances, the battery packs spend a large amount of time in transit (e.g., on a boat, truck, etc.). For example, the battery packs may spend a large amount of time in transit between the battery pack manufacturer(s) and the battery pack distributor(s). Additionally, or alternatively, the battery packs may spend a large amount of time in transitbetween the battery pack distributor(s) and the customer(s). Tn some instances, the battery packs spend a large amount of time in storage. For example, the battery packs may spend a large amount of time sitting in warehouse(s) associated with the battery pack manufacturer(s), the battery pack distributors(s), and / or the customer(s).

[0018] However, it may be difficult or impossible to manage the battery packs while they are in transit and / or in storage. For example, it may be difficult or impossible to manage voltage imbalances associated with the battery packs while they are in transit and / or in storage. The individual cells in a battery pack may self-discharge over time. Each cell in the battery pack may have different self-discharge characteristics. For example, each of the individual cells in a battery pack may comprise a lithium-ion battery. Lithium-ion batteries may be associated with a selfdischarge rate of between 0.5 and 3% per month. Thus, each of the individual cells in the battery pack may lose between 0.5 and 3% of its charge per month. At lower temperatures, this selfdischarge rate may increase drastically. Thus, over time, voltage imbalances may occur between the cells in a battery pack. Voltage imbalances may additionally occur between different battery packs that need to be connected together and / or integrated into the same system or device by the customer. Such voltage imbalances may need to be addressed by the customers after the customers receive the battery packs and connect the battery packs to an external battery management system.

[0019] Further, it may be difficult or impossible to manage other properties of the battery packs, such as temperature, while the battery packs are in transit and / or in storage. For example, it may not be possible to determine whether the temperature of a battery pack in transit or storage is approaching or has exceeded a safe temperature threshold. As such it may be difficult to prevent safety hazards and / or damage to the battery pack. Accordingly, improved techniques for the management of battery packs are desirable.

[0020] Presently disclosed are systems for the centralized management of battery packs. FIG. 1 is an example battery pack 100. In some instances, the battery pack 100 includes an enclosure 104. In some instances, the battery pack 100 includes a plurality of cells 102a-n positioned within the enclosure 104. In some instances, the plurality of cells 102a-n include any quantity of cells, such as twenty, fifty, one hundred, two hundred, etc. cells. In some instances, each of the plurality of cells 102a-n include a lithium-ion battery. The identification of lithium-ion as a battery material is not a limitation and both the skilled artisan and one of ordinary skill in the artwill understand that battery chemistry is evolving and varied and cells formed from different chemistry placed in packs are within the scope of this disclosure.

[0021] The plurality of cells 102a-n are electrically connected to each other. The plurality of cells 102a-n may be configured in a series, parallel, or a mixture of both to deliver a desired voltage, capacity, or power density. In some instances, each of the plurality of cells 102a-n include a cell enclosure and a plurality of layers enclosed within the cell enclosure. In some instances, the plurality of layers includes a cathode with an active coating, a separator, and an anode with an active coating. The plurality of layers are wound to form a jelly roll structure or are stacked to form a stacked-cell structure. In some instances, the plurality of layers are enclosed within the cell enclosure and immersed in an electrolyte.

[0022] In some instances, a battery management device is attached to a battery pack, such as the battery pack 100. If attached to the battery pack, the battery management device enables remote management of the battery pack, such as management of SOC and / or temperature of the battery pack while the battery pack is in transit or storage.

[0023] FIG. 2 is an example battery pack connected to a battery management device 202. The battery pack 100 is connected to the battery management device 202. In some instances, the battery management device 202 is configured to receive power from at least one of a battery, a USB port, or the battery pack 100 itself. In some instances, the battery management device 202 includes at least one of a circuit board, such as a double-sided circuit board.

[0024] In some instances, the battery management device 202 includes a case 204. The case 204 encloses one or more processors and a memory storing instructions. In some instances, the battery management device 202 includes a connector 206. The connector 206 is configured to attach the case 204 to the battery pack 100. For example, the connector 206 may be attached to an outer wall of the enclosure 104 of the battery pack 100 at one end and may be attached to the case 204 at the other end. In some instances, the battery management device 202 is attached to the outer wall of the battery pack 100 after manufacture of the battery pack 100. For example, the battery management device 202 may be attached to (e.g., plugged into) the battery pack 100 by a distributor associated with the battery pack 100 or by a customer associated with the battery pack 100.

[0025] In some instances, the battery management device 202 is in communication with each of the plurality of cells 102a-n. The battery management device 202 is configured to receivevoltage information from each of the plurality of cells 102a-n. The voltage information comprises real time (or near real time) voltage information. In some instances, the real time voltage information associated with a particular cell from the plurality of cells 102a-n includes data indicating a current state of charge (SOC) associated with that cell. In some instances, the real time voltage information associated with the plurality of cells 102a-n indicates if one or more of the plurality of cells 102a-n is associated with a different SOC than the remainder of the plurality of cells 102a-n. Thus, the real time voltage information associated with the plurality of cells 102a-n indicates if a voltage imbalance exists amongst or between the plurality of cells 102a-n. A voltage imbalance that exists amongst or between the plurality of cells 102a-n is herein be referred to as an “intra-pack voltage imbalance.” One or more of the plurality of cells 102a-n can be charged to remedy (e.g., eliminate) an intra-pack voltage imbalance.

[0026] In some instances, the battery management device 202 is configured to determine that an intra-pack voltage imbalance associated with the battery pack 100 exists. The battery management device 202 determines that an intra-pack voltage imbalance associated with the battery pack 100 exists based on the voltage information. In some instances, to determine that the intra-pack voltage imbalance exists, the battery management device 202 compares the current SOC associated with each of the plurality of cells 102a-n. If one or more of the plurality of cells 102a-n is associated with a different SOC than the remainder of the plurality of cells 102a-n, then an intra-pack voltage imbalance exists.

[0027] In some instances, the battery management device 202 is configured to remedy, at least in part, the intra-pack voltage imbalance associated with the battery pack 100. To remedy, at least in part, the intra-pack voltage imbalance associated with the battery pack 100, the battery management device 202 is configured to turn on a bypass resistor (e.g., discharge resistor). If turned on, the bypass resistor, over time, brings down the SOC of one or more of the plurality of cells 102a-n associated with a high SOC. The SOC of the cell(s) associated with a high SOC is brought down towards an average SOC associated with the battery pack 100. Thus, by turning on the bypass resistor, the battery management device 202 remedies, at least in part, the intra- pack voltage imbalance. In this manner, the battery management device 202 ensures that the cell- to-cell imbalances remain minimal.

[0028] In some instances, the battery management device 202 is configured to determine that the intra-pack voltage imbalance associated with the battery pack 100 no longer exists (e g., hasbeen remedied). In some instances, the battery management device 202 determines that the intrapack voltage imbalance associated with the battery pack 100 no longer exists based on the voltage information. In some instances, to determine that the intra-pack voltage imbalance no longer exists, the battery management device 202 compares the current SOC associated with each of the plurality of cells 102a-n. If each the plurality of cells 102a-n is associated with the same (or substantially the same) SOC, then the intra-pack voltage imbalance no longer exists. In some instances, based on determining that the intra-pack voltage imbalance no longer exists, the battery management device 202 turns off the bypass resistor.

[0029] In some instances, the battery management device 202 is configured to cause data indicative of the voltage information to be displayed. The voltage information is displayed via at least one user device located remote to the battery management device 202. In some instances, the battery management device 202 is configured to cause data indicative of the voltage information to be displayed via the user device(s) by sending the voltage information to a server. In some instances, the server is located remote to the battery management device 202. In some instances, the battery management device 202 is configured to send the voltage information to the server using any suitable wireless communication protocol, including but not limited to cellular communication, Wi-Fi, and / or Bluetooth. In some instances, the server receives the voltage information from the battery management device 202. If the server receives the voltage information from the battery management device 202, the server is configured to populate at least one dashboard(s) displayed on an interface of the user device(s) based on the received voltage information. The server, the user device(s), and the dashboard(s) are discussed in more detail below with regard to FIGS. 4-8.

[0030] In some instances, the device 202 is configured to receive temperature information from each of the plurality of cells 102a-n. In some instances, the temperature information includes real time (or near real time) temperature information. The real time temperature information associated with a particular cell from the plurality of cells 102a-n includes data indicating a current temperature associated with that cell.

[0031] In some instances, the battery management device 202 is configured to cause data indicative of the temperature information to be displayed. In some instances, the temperature information is displayed via the dashboard(s) displayed on an interface of the user device(s). The battery management device 202 is configured to cause data indicative of the temperatureinformation to be displayed via the dashboard(s) by sending the temperature information to the server. The server is configured to receive the temperature information from the battery management device 202. The server populates the dashboard(s) based on the received temperature information. In some instances, the server causes an alert to be displayed via the dashboard(s) if a real time temperature associated with at least one of the plurality of cells 102a- n exceeds a temperature threshold. The server and the dashboard(s) are discussed in more detail below with regard to FIGS. 4-8.

[0032] FIG. 3 is an example battery pack connected to a battery management device 302. The battery pack 100 is connected to the battery management device 302. The battery management device 302 is configured to receive power from at least one of a battery, a USB port, or the battery pack 100 itself. In some instances, the battery management device 302 includes at least one of a circuit board, such as a double-sided circuit board.

[0033] In some instances, the battery management device 302 includes a case 304. If the battery management device 302 includes a case 304, the case 304 encloses one or more processors and a memory storing instructions. In some instances, the battery management device 302 includes a connector 306. If the battery management device 302 includes a connector 306, the connector 306 is configured to attach the case 304 to the battery pack 100. For example, the connector 306 may be attached to an inner wall of the enclosure 104 of the battery pack 100 at one end and may be attached to the case 304 at the other end. In some instances, the battery management device 302 is attached to the inner wall of the battery pack 100 during manufacture of the battery pack 100. For example, the battery management device 302 may be attached to (e.g., plugged into) the battery pack 100 by the manufacturer of the battery pack 100.

[0034] In some instances, the battery management device 302 is in communication with each of the plurality of cells 102a-n. In some instances, the battery management device 302 is configured to receive voltage information from each of the plurality of cells 102a-n. In some instances, the voltage information includes real time (or near real time) voltage information. The real time voltage information associated with a particular cell from the plurality of cells 102a-n includes data indicating a current state of charge (SOC) associated with that cell. In some instances, the real time voltage information associated with the plurality of cells 102a-n indicates if one or more of the plurality of cells 102a-n is associated with a different SOC than the remainder of the plurality of cells 102a-n. Thus, in some instances, the real time voltageinformation associated with the plurality of cells 102a-n indicates if a voltage imbalance exists amongst or between the plurality of cells 102a-n. A voltage imbalance that exists amongst or between the plurality of cells 102a-n is herein be referred to as an “intra-pack voltage imbalance.” One or more of the plurality of cells 102a-n can be charged to remedy (e.g., eliminate) an intra-pack voltage imbalance.

[0035] In some instances, the battery management device 302 is configured to determine that an intra-pack voltage imbalance associated with the battery pack 100 exists. In some instances, the battery management device 302 determines that an intra-pack voltage imbalance associated with the battery pack 100 exists based on the voltage information. In some instances, to determine that the intra-pack voltage imbalance exists, the battery management device 302 compares the current SOC associated with each of the plurality of cells 102a-n. If one or more of the plurality of cells 102a-n is associated with a different SOC than the remainder of the plurality of cells 102a-n, then an intra-pack voltage imbalance exists.

[0036] In some instances, the battery management device 302 is configured to remedy, at least in part, the intra-pack voltage imbalance associated with the battery pack 100. In some instances, to remedy, at least in part, the intra-pack voltage imbalance associated with the battery pack 100, the battery management device 302 turns on a bypass resistor (e.g., discharge resistor). If turned on, the bypass resistor is configured to, over time, bring down the SOC of one or more of the plurality of cells 102a-n associated with a high SOC. The SOC of the cell(s) associated with a high SOC is be brought down towards an average SOC associated with the battery pack 100. Thus, turning on the bypass resistor can remedy the intra-pack voltage imbalance by ensuring that the cell-to-cell imbalances remain minimal.

[0037] In some instances, the battery management device 302 is configured to determine that the intra-pack voltage imbalance associated with the battery pack 100 no longer exists (e.g., has been remedied). In some instances, the battery management device 302 is configured to determine that the intra-pack voltage imbalance associated with the battery pack 100 no longer exists based on the voltage information. In some instances, to determine that the intra-pack voltage imbalance no longer exists, the battery management device 302 compares the current SOC associated with each of the plurality of cells 102a-n. If each the plurality of cells 102a-n is associated with the same (or substantially the same) SOC, then the intra-pack voltage imbalance no longer exists. In some instances, based on determining that the intra-pack voltage imbalanceno longer exists, the battery management device 302 turns off the bypass resistor.

[0038] In some instances, the battery management device 302 is configured to cause data indicative of the voltage information to be displayed. In some instances, the voltage information is displayed via at least one user device located remote to the battery management device 302. The battery management device 302 is configured to cause data indicative of the voltage information to be displayed via the user device(s) by sending the voltage information to a server. In some instances, the server is located remote to the battery management device 302. The battery management device 302 can send the voltage information to the server using any suitable wireless communication protocol, including but not limited to cellular communication, Wi-Fi, and / or Bluetooth. The server receives the voltage information from the battery management device 302. In some instances, the server is configured to populate at least one dashboard(s) displayed on an interface of the user device(s) based on the received voltage information. The server, the user device(s), and the dashboard(s) are discussed in more detail below with regard to FIGS. 4-8.

[0039] In some instances, the device 302 is configured to receive temperature information from each of the plurality of cells 102a-n. The temperature information can comprise real time (or near real time) temperature information. In some instances, the real time temperature information associated with a particular cell from the plurality of cells 102a-n comprises data indicating a current temperature associated with that cell.

[0040] In some instances, the battery management device 302 is configured to cause data indicative of the temperature information to be displayed. The temperature information is displayed via the dashboard(s). In some instances, the battery management device 302 is configured to cause data indicative of the temperature information to be displayed via the board(s) by sending the temperature information to the server. In some instances, the server is configured to receive the temperature information from the battery management device 302. The server can populate the dashboard(s) based on the received temperature information. For example, the server can cause an alert to be displayed via the user device(s), such as via the dashboard(s), if a real time temperature associated with at least one of the plurality of cells 102a- n exceeds a temperature threshold. The server, the user device(s), and the dashboard(s) are discussed in more detail below with regard to FIGS. 4-8.

[0041] FIG. 4 is an example system 400 for centralized battery pack management. Thesystem 400 comprises a facility 402, facilities 404a-b, a server 410, a cellular tower 406, a transportation vessel 415, and a network 408.

[0042] In some instances, the facility 402 is associated with a manufacturer or a distributor of battery packs. The facility 402 may comprise, for example, a warehouse or any other suitable facility for manufacturing and / or storing battery packs. A plurality of manufactured battery packs 418a-n, at least one user device 412, and a gateway device 414 are located at the facility 402. In some instances, each of the plurality of battery packs 418a-n comprises the battery pack 100. In some instances, a battery management device, such as the battery management device 202 or the battery management device 302, is attached to each of the plurality of battery packs 418a-n. The battery management devices attached to the plurality of battery packs 418a-n, the user device(s) 412, and the gateway device 414 are in communication via at least one network 416.

[0043] In some instances, the battery management devices attached to the plurality of battery packs 418a-n collects real time (or near real time) voltage and / or temperature information from the plurality of battery packs 418a-n. In some instances, the battery management devices attached to the plurality of battery packs 418a-n send the voltage and / or temperature information to the gateway device 414. The gateway device 414 sends (e.g., forward) the voltage and / or temperature information to the server 410. The server 410 populates at least one dashboard displayed on an interface of the user device(s) 412 in response to receiving the voltage and / or temperature information from the gateway device 414.

[0044] In some instances, the dashboard(s) displayed on the interface of the user device(s) 412 display data indicating a SOC associated with each cell in each of the plurality of battery packs 418a-n. In some instances, the dashboard(s) displayed on the interface of the user device(s) 412 display data indicating if one or more of the cells in a particular battery pack of the plurality of battery packs 418a-n is associated with a different SOC than the remainder of the cells in that particular battery pack. Thus, the dashboard(s) displayed on the interface of the user device(s) 412 can display data indicating whether an intra-pack voltage imbalance exists for any of the plurality of battery packs 418a-n. In some instances, if an intra-pack voltage imbalance exists for any of the plurality of battery packs 418a-n, the dashboard(s) displayed on the interface of the user device(s) 412 indicate which of the battery packs are associated with an intra-pack voltage imbalance.

[0045] In some instances, if an intra-pack voltage imbalance exists for a battery pack of theplurality of battery packs 418a-n, the dashboard(s) displayed on the interface of the user device(s) 412 display data indicating a target voltage to which the at least one of the cells in that battery pack needs to be charged to eliminate the intra-pack voltage imbalance. A user (e.g., an owner or employee of the facility 402) can utilize the data displayed via the dashboard(s) to easily determine which cells in which battery packs need to be charged and / or to determine how much those cells need to be charged in order to remedy the intra-pack voltage imbalance. Thus, the plurality of battery packs 418a-n will not be associated with intra-pack voltage imbalances when they are loaded onto a transportation vessel (e.g., boat, truck, etc.) for delivery to customers.

[0046] In some instances, a first subset of the plurality of battery packs 418a-n located the facility 402 is associated with a first customer and a second subset of the plurality of battery packs 418a-n located the facility 402 is associated with a second customer. For example, the first subset of the plurality of battery packs 418a-n may have been purchased by the first customer, but not yet transported to the first customer. The second subset of the plurality of battery packs 418a-n may have been purchased by the second customer, but not yet transported to the second customer.

[0047] In some instances, the first customer is associated with the facility 404a. The facility 404a may comprise, for example, a warehouse or any other suitable facility for storing battery packs. In some instances, at least one user device 424 and a gateway device 422 are located at the facility 404a. The battery management devices attached to the first subset of the plurality of battery packs 418a-n are configured to send the voltage and / or temperature information associated with the first subset of battery packs to the gateway device 414. The gateway device 414 can send (e.g., forward) the voltage and / or temperature information associated with the first subset of battery packs to the server 410. The server 410 can populate at least one dashboard displayed on an interface of the user device(s) 424 based on the voltage and / or temperature information associated with the first subset of battery packs. Thus, the first customer is able to monitor voltage and / or temperature information associated with the first subset of the plurality of battery packs 418a-n while the first subset of the plurality of battery packs 418a-n are still located at the facility 402.

[0048] In some instances, the second customer is associated with the facility 404b. The facility 404b may comprise, for example, a warehouse or any other suitable facility for storingbattery packs. Tn some instances, at least one user device 434 and a gateway device 432 are located at the facility 404b. The battery management devices attached to the second subset of the plurality of battery packs 418a-n can send the voltage and / or temperature information associated with the second subset of battery packs to the gateway device 414. The gateway device 414 can send (e.g., forward) the voltage and / or temperature information associated with the first subset of battery packs to the server 410. The server 410 can populate at least one dashboard displayed on an interface of the user device(s) 434 based on the voltage and / or temperature information associated with the first subset of battery packs. Thus, the second customer is able to monitor voltage and / or temperature information associated with the second subset of the plurality of battery packs 418a-n while the second subset of the plurality of battery packs 418a-n are still located at the facility 402.

[0049] In some instances, a transportation vessel 415 is utilized to transport battery packs from the facility 402 to the facility 404a and / or to the facility 404b. The transportation vessel 415 may comprise any vehicle capable of transporting battery packs. The transportation vessel 415 is configured to transport a plurality of battery packs 440a-b to the first customer at the facility 404a and a plurality of battery packs 442a-d to the second customer at the facility 404b. In some instances, the plurality of battery packs 440a-b and the plurality of battery packs 442a-d are located on the transportation vessel 415.

[0050] In some instances, each of the plurality of battery packs 440a-b comprise the battery pack 100. A battery management device, such as the battery management device 202 or the battery management device 302, is attached to each of the plurality of battery packs 440a-b. The battery management devices attached to the plurality of battery packs 440a-b are configured to collect real time (or near real time) voltage and / or temperature information from the plurality of battery packs 440a-b. The battery management devices attached to the plurality of battery packs 440a-b are in communication with the cellular tower 406 while the transportation vessel 415 is in the process of transporting the plurality of battery packs 440a-b to the facility 404a. The battery management devices attached to the plurality of battery packs 440a-b are configured to send the voltage and / or temperature information to the cellular tower 406. The cellular tower 406 can send (e.g., forward) the voltage and / or temperature information to the server 410. The server 410 is configured to populate at least one dashboard displayed on an interface of the user device(s) 424 in response to receiving the voltage and / or temperature information from the cellular tower406.

[0051] In some instances, the dashboard(s) displayed on the interface of the user device(s) 424 display data indicating a SOC associated with each cell in each of the plurality of battery packs 440a-b. In some instances, the dashboard(s) displayed on the interface of the user device(s) 424 display data indicating if one or more of the cells in a particular battery pack of the plurality of battery packs 440a-b is associated with a different SOC than the remainder of the cells in that particular battery pack. Thus, the dashboard(s) displayed on the interface of the user device(s) 424 can display data indicating whether an intra-pack voltage imbalance exists for any of the plurality of battery packs 440a-b. In some instances, if an intra-pack voltage imbalance exists for any of the plurality of battery packs 440a-b, the dashboard(s) displayed on the interface of the user device(s) 424 indicate which of the battery packs are associated with an intra-pack voltage imbalance. Thus, the first customer is able to monitor voltage information associated with the plurality of battery packs 440a-b while the plurality of battery packs 440a-b are in the process of being transported to the facility 404a.

[0052] In some instances, the dashboard(s) displayed on the interface of the user device(s) 424 display data indicating a temperature associated with each cell in each of the plurality of battery packs 440a-b. The dashboard(s) displayed on the interface of the user device(s) 424 can display data indicating whether the temperature associated with any of the cells in the plurality of battery packs 440a-b is approaching or has exceeded a safe temperature threshold. In some instances, an alert is displayed via the dashboard(s) displayed on the interface of the user device(s) 424 if a real time temperature associated with at least one of the plurality of cells in the plurality of battery packs 440a-b exceeds a temperature threshold. Thus, the first customer is able to monitor temperature information associated with the plurality of battery packs 440a-b while the plurality of battery packs 440a-b are in the process of being transported to the facility 404a.

[0053] In some instances, each of the plurality of battery packs 442a-d comprises the battery pack 100. A battery management device, such as the battery management device 202 or the battery management device 302, is attached to each of the plurality of battery packs 442a-d. The battery management devices attached to the plurality of battery packs 442a-d are configured to collect real time (or near real time) voltage and / or temperature information from the plurality of battery packs 442a-d. The battery management devices attached to the plurality of battery packs 442a-d are in communication with the cellular tower 406 while the transportation vessel 415 is inthe process of transporting the plurality of battery packs 442a-d to the facility 404b. The battery management devices attached to the plurality of battery packs 442a-d are configured to send the voltage and / or temperature information to the cellular tower 406. The cellular tower 406 can send (e.g., forward) the voltage and / or temperature information to the server 410. The server 410 is configured to populate at least one dashboard displayed on an interface of the user device(s) 434 in response to receiving the voltage and / or temperature information from the cellular tower 406.

[0054] In some instances, the dashboard(s) displayed on the interface of the user device(s) 434 display data indicating a SOC associated with each cell in each of the plurality of battery packs 442a-d. In some instances, the dashboard(s) displayed on the interface of the user device(s) 434 display data indicating if one or more of the cells in a particular battery pack of the plurality of battery packs 442a-d is associated with a different SOC than the remainder of the cells in that particular battery pack. Thus, the dashboard(s) displayed on the interface of the user device(s) 434 can display data indicating whether an intra-pack voltage imbalance exists for any of the plurality of battery packs 442a-d. In some instances, if an intra-pack voltage imbalance exists for any of the plurality of battery packs 442a-d, the dashboard(s) displayed on the interface of the user device(s) 434 indicate which of the battery packs are associated with an intra-pack voltage imbalance. Thus, the second customer is able to monitor voltage information associated with the plurality of battery packs 442a-d while the plurality of battery packs 442a-d are in the process of being transported to the facility 404b.

[0055] In some instances, the dashboard(s) displayed on the interface of the user device(s) 434 display data indicating a temperature associated with each cell in each of the plurality of battery packs 442a-d. In some instances, the dashboard(s) displayed on the interface of the user device(s) 434 display data indicating whether the temperature associated with any of the cells in the plurality of battery packs 442a-d is approaching or has exceeded a safe temperature threshold. In some instances, an alert is displayed via the dashboard(s) displayed on the interface of the user device(s) 434 if a real time temperature associated with at least one of the plurality of cells in the plurality of battery packs 442a-d exceeds a temperature threshold. Thus, the second customer is able to monitor temperature information associated with the plurality of battery packs 442a-d while the plurality of battery packs 442a-d are in the process of being transported to the facility 404b.

[0056] Tn some instances, the first customer stores battery packs it has purchased at the facility 404a. FIG. 5 shows a more detailed view of the facility 404a. The user device(s) 424 and a gateway device 422 are located at the facility 404a. The first customer receives the plurality of battery packs 440a-b. For example, the transportation vessel 415 may deliver the plurality of battery packs 440a-b to the facility 404a. The first customer may store the plurality of battery packs 440a-b at the facility 404a. The first customer may store other battery packs in addition to the plurality of battery packs 440a-b. For example, the plurality of battery packs 428a-n may be stored at the facility 404a along with the plurality of battery packs 440a-b.

[0057] As described above, a battery management device is attached to each of the plurality of battery packs 440a-b. The battery management devices attached to the plurality of battery packs 440a-b is in communication with the gateway 422 while located at the facility 404a. The battery management devices attached to the plurality of battery packs 440a-b send the voltage and / or temperature information to the gateway 422. The gateway 422 sends (e.g., forward) the voltage and / or temperature information to the server 410. The server 410 populates at least one dashboard displayed on an interface of the user device(s) 424 in response to receiving the voltage and / or temperature information from the gateway 422.

[0058] In embodiments, the dashboard(s) displayed on the interface of the user device(s) 424 display data indicating a SOC associated with each cell in each of the plurality of battery packs 440a-b. The dashboard(s) displayed on the interface of the user device(s) 424 display data indicating if one or more of the cells in a particular battery pack of the plurality of battery packs 440a-b is associated with a different SOC than the remainder of the cells in that particular battery pack. Thus, the dashboard(s) displayed on the interface of the user device(s) 424 display data indicating whether an intra-pack voltage imbalance exists for any of the plurality of battery packs 440a-b. In some instances, if an intra-pack voltage imbalance exists for any of the plurality of battery packs 440a-b, the dashboard(s) displayed on the interface of the user device(s) 424 indicate which of the battery packs are associated with an intra-pack voltage imbalance. In some instances, if an intra-pack voltage imbalance exists for a battery pack of plurality of battery packs 440a-b, the dashboard(s) displayed on the interface of the user device(s) 424 display data indicating a target voltage to which the at least one of the cells in that battery pack needs to be charged to eliminate the intra-pack voltage imbalance.

[0059] In some instances, the plurality of battery packs 440a-b form a multi-pack system. Theplurality of battery packs 440a-b form a multi-pack system if each of the plurality of battery packs 440a-b are going to be connected together and / or integrated into the same end-system or device by the first customer. A voltage imbalance that exists between different battery packs that need to be connected together and / or integrated into the same system or device by the customer are herein be referred to as an “inter-pack voltage imbalance.”

[0060] In some instances, the dashboard(s) displayed on the interface of the user device(s) 424 display data indicating a SOC associated with each of the plurality of battery packs 440a-b. The dashboard(s) displayed on the interface of the user device(s) 424 display data indicating if one of the plurality of battery packs 440a-b is associated with a different SOC than the other of the plurality of battery packs 440a-b. Thus, the dashboard(s) displayed on the interface of the user device(s) 424 display data indicating whether an inter-pack voltage imbalance exists between the battery pack 440a and the battery pack 440b. In some instances, if an inter-pack voltage imbalance exists between the plurality of battery packs 440a-b, the dashboard(s) displayed on the interface of the user device(s) 424 display data indicating a target voltage to which at least one of the plurality of battery packs 440a-b needs to be charged to eliminate the voltage imbalance between the battery pack 440a and the battery pack 440b.

[0061] Thus, the first customer is able to monitor voltage information associated with the plurality of battery packs 440a-b while the plurality of battery packs 440a-b are stored at the facility 404a. A user (e.g., an owner or employee of the facility 404a) can utilize the data displayed via the dashboard(s) to easily determine which cells in which battery packs need to be charged and / or to determine how much those cells need to be charged in order to remedy any intra-pack voltage imbalances or inter-pack voltage imbalances. Thus, the plurality of battery packs 440a-b will not be associated with intra-pack voltage imbalances or an inter-pack voltage imbalance when they are integrated into the end system or device to which they are configured to provide power.

[0062] In some instances, the dashboard(s) displayed on the interface of the user device(s) 424 display data indicating a temperature associated with each cell in each of the plurality of battery packs 440a-b. In some instances, the dashboard(s) displayed on the interface of the user device(s) 424 display data indicating whether the temperature associated with any of the cells in the plurality of battery packs 440a-b is approaching or has exceeded a safe temperature threshold In some instances, an alert is displayed via the dashboard(s) displayed on the interfaceof the user device(s) 424 if a real time temperature associated with at least one of the plurality of cells in the plurality of battery packs 440a-b exceeds a temperature threshold. Thus, the first customer is able to monitor temperature information associated with the plurality of battery packs 440a-b while the plurality of battery packs 440a-b are stored at the facility 404a.

[0063] In some instances, each of the plurality of battery packs 428a-n comprises the battery pack 100. A battery management device, such as the battery management device 202 or the battery management device 302, is attached to each of the plurality of battery packs 428a-n. The battery management devices attached to the plurality of battery packs 428a-n, the user device(s) 424, and the gateway device 422 are in communication via at least one network 426.

[0064] The battery management devices attached to the plurality of battery packs 428a-n collect real time (or near real time) voltage and / or temperature information from the plurality of battery packs 428a-n. The battery management devices attached to the plurality of battery packs 428a-n send the voltage and / or temperature information to the gateway device 422. The gateway device 422 sends (e.g., forward) the voltage and / or temperature information to the server 410. The server 410 populates at least one dashboard displayed on an interface of the user device(s) 424 in response to receiving the voltage and / or temperature information from the gateway device 422.

[0065] In some instances, the dashboard(s) displayed on the interface of the user device(s) 424 display data indicating a SOC associated with each cell in each of the plurality of battery packs 428a-n. In some instances, the dashboard(s) displayed on the interface of the user device(s) 424 display data indicating if one or more of the cells in a particular battery pack of the plurality of battery packs 428a-n is associated with a different SOC than the remainder of the cells in that particular battery pack. Thus, the dashboard(s) displayed on the interface of the user device(s) 424 can display data indicating whether an intra-pack voltage imbalance exists for any of the plurality of battery packs 428a-n. In some instances, if an intra-pack voltage imbalance exists for any of the plurality of battery packs 428a-n, the dashboard(s) displayed on the interface of the user device(s) 424 indicate which of the battery packs are associated with an intra-pack voltage imbalance. In some instances, if an intra-pack voltage imbalance exists for a battery pack of the plurality of battery packs 428a-n, the dashboard(s) displayed on the interface of the user device(s) 424 display data indicating a target voltage to which the at least one of the cells in that battery pack needs to be charged to eliminate the intra-pack voltage imbalance

[0066] Tn some instances, a first subset of the plurality of battery packs 428a-n (e g., the battery packs 428a-h) form a multi-pack system. The battery packs 428a-h form a multi-pack system if each of the battery packs 428a-h are going to be connected together and / or integrated into the same end-system or device by the first customer.

[0067] In some instances, the dashboard(s) displayed on the interface of the user device(s) 424 display data indicating a SOC associated with each of the battery packs 428a-h. The dashboard(s) displayed on the interface of the user device(s) 424 display data indicating if one of the battery packs 428a-h is associated with a different SOC than the other of the battery packs 428a-h. Thus, the dashboard(s) displayed on the interface of the user device(s) 424 can display data indicating whether an inter-pack voltage imbalance exists between any of the battery packs 428a-h. In some instances, if an inter-pack voltage imbalance exists between any of the battery packs 428a-h, the dashboard(s) displayed on the interface of the user device(s) 424 indicate which of the battery packs 428a-h are associated with an inter-pack voltage imbalance. In some instances, the dashboard(s) displayed on the interface of the user device(s) 424 display data indicating a target voltage to which at least one of the battery packs 428a-h need to be charged to eliminate the voltage imbalance between the battery packs 428a-h.

[0068] In some instances, a second subset of the plurality of battery packs 428a-n (e.g., the battery packs 428i-n) form a multi-pack system. The battery packs 428i-n form a multi-pack system if each of the battery packs 428i-n are going to be connected together and / or integrated into the same end-system or device by the first customer.

[0069] In some instances, the dashboard(s) displayed on the interface of the user device(s) 424 display data indicating a SOC associated with each of the battery packs 428i-n. In some instances, the dashboard(s) displayed on the interface of the user device(s) 424 display data indicating if one of the battery packs 428i-n is associated with a different SOC than the other of the battery packs 428i-n. Thus, the dashboard(s) displayed on the interface of the user device(s) 424 can display data indicating whether an inter-pack voltage imbalance exists between any of the battery packs 428i-n. In some instances, if an inter-pack voltage imbalance exists between any of the battery packs 428i-n, the dashboard(s) displayed on the interface of the user device(s) 424 indicate which of the battery packs 428i-n are associated with an inter-pack voltage imbalance. In some instances, the dashboard(s) displayed on the interface of the user device(s) 424 display data indicating a target voltage to which at least one of the battery packs 428i-n needto be charged to eliminate the voltage imbalance between the battery packs 428i-n

[0070] Thus, the first customer is able to monitor voltage information associated with the plurality of battery packs 428a-n while the plurality of battery packs 428a-n are stored at the facility 404a. A user (e.g., an owner or employee of the facility 404a) can utilize the data displayed via the dashboard(s) to easily determine which cells in which battery packs need to be charged and / or to determine how much those cells need to be charged in order to remedy any intra-pack voltage imbalances or inter-pack voltage imbalances. Thus, the plurality of battery packs 428a-n will not be associated with intra-pack voltage imbalances or an inter-pack voltage imbalance when they are integrated into the end system or device to which they are configured to provide power.

[0071] In some instances, the second customer stores battery packs it has purchased at the facility 404b. FIG. 5 shows a more detailed view of the facility 404b. The user device(s) 434 and a gateway device 432 are located at the facility 404b. The second customer receives the plurality of battery packs 442a-d. For example, the transportation vessel 415 may deliver the plurality of battery packs 442a-d to the facility 404b. The second customer stores the plurality of battery packs 442a-d at the facility 404b. The second customer may store other battery packs in addition to the plurality of battery packs 442a-d. For example, the plurality of battery packs 438a-n may be stored at the facility 404b along with the plurality of battery packs 442a-d.

[0072] As described above, a battery management device is attached to each of the plurality of battery packs 442a-d. The battery management devices attached to the plurality of battery packs 442a-d is in communication with the gateway 432 while located at the facility 404b. The battery management devices attached to the plurality of battery packs 442a-d send the voltage and / or temperature information to the gateway 432. The gateway 432 sends (e.g., forward) the voltage and / or temperature information to the server 410. The server 410 populates at least one dashboard displayed on an interface of the user device(s) 434 in response to receiving the voltage and / or temperature information from the gateway 432.

[0073] In some instances, the dashboard(s) displayed on the interface of the user device(s) 434 displays data indicating a SOC associated with each cell in each of the plurality of battery packs 442a-d. In some instances, the dashboard(s) displayed on the interface of the user device(s) 434 displays data indicating if one or more of the cells in a particular battery pack of the plurality of battery packs 442a-d is associated with a different SOC than the remainder of the cells in thatparticular battery pack. Thus, the dashboard(s) displayed on the interface of the user device(s) 434 can display data indicating whether an intra-pack voltage imbalance exists for any of the plurality of battery packs 442a-d. In some instances, if an intra-pack voltage imbalance exists for any of the plurality of battery packs 442a-d, the dashboard(s) displayed on the interface of the user device(s) 434 indicate which of the battery packs are associated with an intra-pack voltage imbalance. In some instances, if an intra-pack voltage imbalance exists for a battery pack of plurality of battery packs 442a-d, the dashboard(s) displayed on the interface of the user device(s) 434 display data indicating a target voltage to which the at least one of the cells in that battery pack needs to be charged to eliminate the intra-pack voltage imbalance.

[0074] In some instances, the plurality of battery packs 442a-d form a multi-pack system. The plurality of battery packs 442a-d form a multi -pack system if each of the plurality of battery packs 442a-d are going to be connected together and / or integrated into the same end-system or device by the second customer.

[0075] In some instances, the dashboard(s) displayed on the interface of the user device(s) 434 display data indicating a SOC associated with each of the plurality of battery packs 442a-d. In some instances, the dashboard(s) displayed on the interface of the user device(s) 434 display data indicating if one of the plurality of battery packs 442a-d is associated with a different SOC than the other of the plurality of battery packs 442a-d. Thus, the dashboard(s) displayed on the interface of the user device(s) 434 can display data indicating whether an inter-pack voltage imbalance exists between any of the battery packs 442a-d. In some instances, if an inter-pack voltage imbalance exists between the plurality of battery packs 442a-d, the dashboard(s) displayed on the interface of the user device(s) 434 indicate which of the battery packs 442a-d are associated with the inter-pack voltage imbalance. In some instances, the dashboard(s) displayed on the interface of the user device(s) 434 display data indicating a target voltage to which at least one of the plurality of battery packs 442a-d needs to be charged to eliminate the inter-pack voltage imbalance.

[0076] Thus, the second customer is able to monitor voltage information associated with the plurality of battery packs 442a-d while the plurality of battery packs 442a-d are stored at the facility 404b. A user (e.g., an owner or employee of the facility 404b) can utilize the data displayed via the dashboard(s) to easily determine which cells in which battery packs need to be charged and / or to determine how much those cells need to be charged in order to remedy anyintra-pack voltage imbalances or inter-pack voltage imbalances. Thus, the plurality of battery packs 442a-d will not be associated with intra-pack voltage imbalances or an inter-pack voltage imbalance when they are integrated into the end system or device to which they are configured to provide power.

[0077] In some instances, the dashboard(s) displayed on the interface of the user device(s) 434 display data indicating a temperature associated with each cell in each of the plurality of battery packs 442a-d. In some instances, the dashboard(s) displayed on the interface of the user device(s) 434 display data indicating whether the temperature associated with any of the cells in the plurality of battery packs 442a-d is approaching or has exceeded a safe temperature threshold. In some instances, an alert is displayed via the dashboard(s) displayed on the interface of the user device(s) 434 if a real time temperature associated with at least one of the plurality of cells in the plurality of battery packs 442a-d exceeds a temperature threshold. Thus, the second customer is able to monitor temperature information associated with the plurality of battery packs 442a-d while the plurality of battery packs 442a-d are stored at the facility 404b.

[0078] In some instances, each of the plurality of battery packs 438a-n comprises the battery pack 100. A battery management device, such as the battery management device 202 or the battery management device 302, is attached to each of the plurality of battery packs 438a-n. The battery management devices attached to the plurality of battery packs 438a-n, the user device(s) 434, and the gateway device 432 are in communication via at least one network 436.

[0079] The battery management devices attached to the plurality of battery packs 438a-n collect real time (or near real time) voltage and / or temperature information from the plurality of battery packs 438a-n. The battery management devices attached to the plurality of battery packs 438a-n send the voltage and / or temperature information to the gateway device 432. The gateway device 432 sends (e g., forward) the voltage and / or temperature information to the server 410. The server 410 populates at least one dashboard displayed on an interface of the user device(s) 434 in response to receiving the voltage and / or temperature information from the gateway device 432.

[0080] In some instances, the dashboard(s) displayed on the interface of the user device(s) 434 display data indicating a SOC associated with each cell in each of the plurality of battery packs 438a-n. In some instances, the dashboard(s) displayed on the interface of the user device(s) 434 display data indicating if one or more of the cells in a particular battery pack of the pluralityof battery packs 438a-n is associated with a different SOC than the remainder of the cells in that particular battery pack. Thus, the dashboard(s) displayed on the interface of the user device(s) 434 can display data indicating whether an intra-pack voltage imbalance exists for any of the plurality of battery packs 438a-n. In some instances, if an intra-pack voltage imbalance exists for any of the plurality of battery packs 438a-n, the dashboard(s) displayed on the interface of the user device(s) 434 indicate which of the battery packs are associated with an intra-pack voltage imbalance. In some instances, if an intra-pack voltage imbalance exists for a battery pack of the plurality of battery packs 438a-n, the dashboard(s) displayed on the interface of the user device(s) 434 display data indicating a target voltage to which the at least one of the cells in that battery pack needs to be charged to eliminate the intra-pack voltage imbalance.

[0081] In some instances, a first subset of the plurality of battery packs 438a-n (e.g., the battery packs 438a-d) form a multi -pack system. The battery packs 438a-d form a multi-pack system if each of the battery packs 438a-d are going to be connected together and / or integrated into the same end-system or device by the second customer.

[0082] In some instances, the dashboard(s) displayed on the interface of the user device(s) 434 display data indicating a SOC associated with each of the battery packs 438a-d. In some instances, the dashboard(s) displayed on the interface of the user device(s) 434 display data indicating if one of the battery packs 438a-d is associated with a different SOC than the other of the battery packs 438a-d. Thus, the dashboard(s) displayed on the interface of the user device(s) 434 can display data indicating whether an inter-pack voltage imbalance exists between any of the battery packs 438a-d. In some instances, if an inter-pack voltage imbalance exists between any of the battery packs 438a-d, the dashboard(s) displayed on the interface of the user device(s) 434 indicate which of the battery packs 438a-d are associated with the inter-pack voltage imbalance. In some instances, the dashboard(s) displayed on the interface of the user device(s) 434 display data indicating a target voltage to which at least one of the battery packs 438a-d need to be charged to eliminate the inter-pack voltage imbalance.

[0083] In some instances, a second subset of the plurality of battery packs 438a-n (e.g., the battery packs 438e-j) form a multi-pack system. The battery packs 438e-j form a multi-pack system if each of the battery packs 438e-j are going to be connected together and / or integrated into the same end-system or device by the second customer.

[0084] In some instances, the dashboard(s) displayed on the interface of the user device(s)434 display data indicating a SOC associated with each of the battery packs 438e-j. Tn some instances, the dashboard(s) displayed on the interface of the user device(s) 434 display data indicating if one of the battery packs 438e-j is associated with a different SOC than the other of the battery packs 438e-j. Thus, the dashboard(s) displayed on the interface of the user device(s) 434 can display data indicating whether an inter-pack voltage imbalance exists between any of the battery packs 438e-j. In some instances, if an inter-pack voltage imbalance exists between any of the battery packs 438e-j, the dashboard(s) displayed on the interface of the user device(s) 434 indicate which of the battery packs 438e-j are associated with the inter-pack voltage imbalance. In some instances, the dashboard(s) displayed on the interface of the user device(s) 434 display data indicating a target voltage to which at least one of the battery packs 438e-j need to be charged to eliminate the inter-pack voltage imbalance.

[0085] In some instances, a third subset of the plurality of battery packs 438a-n (e.g., the battery packs 438k-n) form a multi -pack system. The battery packs 438k-n form a multi-pack system if each of the battery packs 438k-n are going to be connected together and / or integrated into the same end-system or device by the second customer.

[0086] In some instances, the dashboard(s) displayed on the interface of the user device(s) 434 display data indicating a SOC associated with each of the battery packs 438k-n. In some instances, the dashboard(s) displayed on the interface of the user device(s) 434 display data indicating if one of the battery packs 438k-n is associated with a different SOC than the other of the battery packs 438k-n. Thus, the dashboard(s) displayed on the interface of the user device(s) 434 can display data indicating whether an inter-pack voltage imbalance exists between any of the battery packs 438k-n. In some instances, if an inter-pack voltage imbalance exists between any of the battery packs 438k-n, the dashboard(s) displayed on the interface of the user device(s) 434 indicate which of the battery packs 438k-n are associated with the inter-pack voltage imbalance. In some instances, the dashboard(s) displayed on the interface of the user device(s) 434 display data indicating a target voltage to which at least one of the battery packs 438k-n need to be charged to eliminate the inter-pack voltage imbalance.

[0087] Thus, the second customer is able to monitor voltage information associated with the plurality of battery packs 438a-n while the plurality of battery packs 438a-n are stored at the facility 404b. A user (e.g., an owner or employee of the facility 404b) can utilize the data displayed via the dashboard(s) to easily determine which cells in which battery packs need to becharged and / or to determine how much those cells need to be charged in order to remedy any intra-pack voltage imbalances or inter-pack voltage imbalances. Thus, the plurality of battery packs 438a-n will not be associated with intra-pack voltage imbalances or an inter-pack voltage imbalance when they are integrated into the end system or device to which they are configured to provide power.

[0088] FIG. 7 shows an example method 700 for battery pack management. At operation 702, real time voltage information is received. The real time voltage information is received from a device (e.g., the battery management device 202 and / or the battery management device 302). The device is connected to a battery pack. The device is configured to be integrated into the battery pack during manufacture of the battery pack. Additionally, or alternatively, the device is configured to be attached to the battery pack after manufacture of the battery pack. The device is configured to receive power from at least one of a battery, a USB port, or the battery pack. In some instances, the device comprises a chip. For example, the device may comprise a doublesided circuit board. The real time voltage information is received at a server. In some instances, the server is located remotely to at least one user device and the device.

[0089] The battery pack comprises a plurality of cells. The real time voltage information is associated with each of the plurality of cells. The real time voltage information associated with a particular cell from the plurality of cells comprises data indicating a current SOC associated with that cell. The real time voltage information comprises data indicating whether which (if any) of the plurality of cells need to be charged. The device is configured to send the real time voltage information to the server located remote to the device using at least one of cellular communication, Wi-Fi, or Bluetooth. At operation 704, an interface of the at least one user device is populated. The interface is populated based on the real time voltage information The populated interface displays data indicating whether a voltage imbalance exists amongst the plurality of cells[0090JFIG. 8 shows a method 800 for battery pack management. At operation 802, first real time voltage information is received. The first real time voltage information is received from a first device (e.g., the battery management device 202 and / or the battery management device 302). The first device is connected to a first battery pack. The first device is configured to be integrated into the first battery pack during manufacture of the first battery pack. Additionally, or alternatively, the device is configured to be attached to the first battery pack after manufacture ofthe first battery pack. The first device is configured to receive power from at least one of a battery, a USB port, or the first battery pack. In some instances, the first device comprises a chip. For example, the first device may comprise a double-sided circuit board. The first real time voltage information is received at a server. In some instances, the server is located remotely to at least one user device and the first device.

[0091] The first battery pack comprises a first plurality of cells. The first real time voltage information is associated with each of the first plurality of cells. The first real time voltage information associated with a particular cell from the first plurality of cells comprises data indicating a current SOC associated with that cell. The first real time voltage information comprises data indicating whether which (if any) of the first plurality of cells need to be charged. The first device is configured to send the first real time voltage information to the server located remote to the device using at least one of cellular com unication, Wi-Fi, or Bluetooth.

[0092] At operation 804, second real time voltage information is received. The second real time voltage information is received from a second device (e.g., the battery management device 202 and / or the battery management device 302). The second device is connected to a second battery pack. The second device is configured to be integrated into the second battery pack during manufacture of the second battery pack. Additionally, or alternatively, the device is configured to be attached to the second battery pack after manufacture of the second battery pack. The second device is configured to receive power from at least one of a battery, a USB port, or the second battery pack. In some instances, the second device comprises a chip. For example, the second device may comprise a double-sided circuit board. The second real time voltage information is received at a server. In some instances, the server is located remotely to at least one user device and the second device.

[0093] The second battery pack comprises a second plurality of cells. The second real time voltage information is associated with each of the second plurality of cells. The second real time voltage information associated with a particular cell from the second plurality of cells comprises data indicating a current SOC associated with that cell. The second real time voltage information comprises data indicating whether which (if any) of the second plurality of cells need to be charged. The second device is configured to send the second real time voltage information to the server located remote to the device using at least one of cellular communication, Wi-Fi, or Bluetooth

[0094] At 806, an interface of the at least one user device is populated. The interface is populated based on the first and second real time voltage information. The populated interface displays data indicating whether a voltage imbalance exists amongst the first plurality of cells. In some instances, the populated interface displays data indicating whether a voltage imbalance exists amongst the second plurality of cells. In some instances, the populated interface displays data indicating whether a voltage imbalance between the first battery pack and the second battery pack.

[0095] FIG. 9 shows a method 900 for battery pack management. At operation 902, information indicating real time temperature is received. The information indicating the real time temperature is received from a device (e g., the battery management device 202 and / or the battery management device 302). The device is connected to a battery pack. The device is configured to be integrated into the battery pack during manufacture of the battery pack. Additionally, or alternatively, the device is configured to be attached to the battery pack after manufacture of the battery pack. The device is configured to receive power from at least one of a battery, a USB port, or the battery pack. In some instances, the device comprises a chip. For example, the device may comprise a double-sided circuit board. The information indicating real time temperature is received at a server. In some instances, the server is located remotely to at least one user device and the device.

[0096] The battery pack comprises a plurality of cells. The information indicates a real time temperature associated with each of the plurality of cells. The temperature information comprises real time (or near real time) temperature information. The real time temperature information associated with a particular cell from the plurality of cells comprises data indicating a current temperature associated with that cell. The device is configured to send the information indicating the real time temperature to the server located remote to the device using at least one of cellular communication, Wi-Fi, or Bluetooth. At 904, an alert is caused to be displayed. The alert indicates that a real time temperature associated with at least one of the plurality of cells exceeds a threshold. The alert is caused to be displayed via the dashboard(s). The alert is caused to be displayed based on the real time temperature associated with at least one of the plurality of cells exceeding a threshold. In some instances, the server causes the alert to be displayed based on the real time temperature information.[0097JFIG 10 shows an example computing device. FIG. 10 depicts a computing device thatcan be used in various aspects, such as the servers and / or devices depicted in FIGS. 1 -6. For example, the battery management device 202, the battery management device 302, the server 410, the user device(s) 412, the user devices(s) 424, the user devices(s) 434, the gateway 414, the gateway 422, the gateway 432, and / or the cellular tower 406 can each be implemented in an instance of a computing device 1000 of FIG. 10.

[0098] The computer architecture shown in FIG. 10 shows a conventional server computer, workstation, desktop computer, laptop, tablet, network appliance, PDA, e-reader, digital cellular phone, or other computing node, and can be utilized to execute any aspects of the computers described herein, such as to implement the methods described in relation to FIG. 7, FIG. 8, and FIG. 9.

[0099] The computing device 1000 can include a baseboard, or “motherboard,” which is a printed circuit board to which a multitude of components or devices can be connected by way of a system bus or other electrical communication paths. One or more central processing units (CPUs) 1004 can operate in conjunction with a chipset 1006. The CPU(s) 1004 can be standard programmable processors that perform arithmetic and logical operations necessary for the operation of the computing device 1000.

[0100] The CPU(s) 1004 can perform the necessary operations by transitioning from one discrete physical state to the next through the manipulation of switching elements that differentiate between and change these states. Switching elements can generally include electronic circuits that maintain one of two binary states, such as flip-flops, and electronic circuits that provide an output state based on the logical combination of the states of one or more other switching elements, such as logic gates. These basic switching elements can be combined to create more complex logic circuits including registers, adders-subtractors, arithmetic logic units, floating-point units, and the like.

[0101] The CPU(s) 1004 can be augmented with or replaced by other processing units, such as GPU(s) 1005. The GPU(s) 1005 can comprise processing units specialized for but not necessarily limited to highly parallel computations, such as graphics and other visualization- related processing.

[0102] A chipset 1006 can provide an interface between the CPU(s) 1004 and the remainder of the components and devices on the baseboard. The chipset 1006 can provide an interface to a random access memory (RAM) 1008 used as the main memory in the computingdevice 1000. The chipset 1006 can further provide an interface to a computer-readable storage medium, such as a read-only memory (ROM) 1020 or non-volatile RAM (NVRAM) (not shown), for storing basic routines that can help to start up the computing device 1000 and to transfer information between the various components and devices. ROM 1020 or NVRAM can also store other software components necessary for the operation of the computing device 1000 in accordance with the aspects described herein.

[0103] The computing device 1000 can operate in a networked environment using logical connections to remote computing nodes and computer systems through local area network (LAN) 1016. The chipset 1006 can include functionality for providing network connectivity through a network interface controller (NIC) 1022, such as a gigabit Ethernet adapter. A NIC 1022 can be capable of connecting the computing device 1000 to other computing nodes over a network 1016. It should be appreciated that multiple NICs 1022 can be present in the computing device 1000, connecting the computing device to other types of networks and remote computer systems.

[0104] The computing device 1000 can be connected to a mass storage device 1028 that provides non-volatile storage for the computer. The mass storage device 1028 can store system programs, application programs, other program modules, and data, which have been described in greater detail herein. The mass storage device 1028 can be connected to the computing device 1000 through a storage controller 1024 connected to the chipset 1006. The mass storage device 1028 can consist of one or more physical storage units. A storage controller 1024 can interface with the physical storage units through a serial attached SCSI (SAS) interface, a serial advanced technology attachment (SATA) interface, a fiber channel (FC) interface, or other type of interface for physically connecting and transferring data between computers and physical storage units.

[0105] The computing device 1000 can store data on a mass storage device 1028 by transforming the physical state of the physical storage units to reflect the information being stored. The specific transformation of a physical state can depend on various factors and on different implementations of this description. Examples of such factors can include, but are not limited to, the technology used to implement the physical storage units and whether the mass storage device 1028 is characterized as primary or secondary storage and the like.

[0106] For example, the computing device 1000 can store information to the massstorage device 1028 by issuing instructions through a storage controller 1024 to alter the magnetic characteristics of a particular location within a magnetic disk drive unit, the reflective or refractive characteristics of a particular location in an optical storage unit, or the electrical characteristics of a particular capacitor, transistor, or other discrete component in a solid-state storage unit. Other transformations of physical media are possible without departing from the scope and spirit of the present description, with the foregoing examples provided only to facilitate this description. The computing device 1000 can further read information from the mass storage device 1028 by detecting the physical states or characteristics of one or more particular locations within the physical storage units.

[0107] In addition to the mass storage device 1028 described above, the computing device 1000 can have access to other computer-readable storage media to store and retrieve information, such as program modules, data structures, or other data. It should be appreciated by those skilled in the art that computer-readable storage media can be any available media that provides for the storage of non-transitory data and that can be accessed by the computing device 1000.

[0108] By way of example and not limitation, computer-readable storage media can include volatile and non-volatile, transitory computer-readable storage media and non-transitory computer-readable storage media, and removable and non-removable media implemented in any method or technology. Computer-readable storage media includes, but is not limited to, RAM, ROM, erasable programmable ROM (“EPROM”), electrically erasable programmable ROM (“EEPROM”), flash memory or other solid-state memory technology, compact disc ROM (“CD- ROM”), digital versatile disk (“DVD”), high definition DVD (“HD-DVD”), BLU-RAY, or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage, other magnetic storage devices, or any other medium that can be used to store the desired information in a non-transitory fashion.

[0109] A mass storage device, such as the mass storage device 1028 depicted in FIG. 10, can store an operating system utilized to control the operation of the computing device 1000. The operating system can comprise a version of the LINUX operating system. The operating system can comprise a version of the WINDOWS SERVER operating system from the MICROSOFT Corporation. According to further aspects, the operating system can comprise a version of the UNIX operating system. Various mobile phone operating systems, such as IOSand ANDROID, can also be utilized. It should be appreciated that other operating systems can also be utilized. The mass storage device 1028 can store other system or application programs and data utilized by the computing device 1000.

[0110] The mass storage device 1028 or other computer-readable storage media can also be encoded with computer-executable instructions, which, when loaded into the computing device 1000, transforms the computing device from a general -purpose computing system into a special-purpose computer capable of implementing the aspects described herein. These computer-executable instructions transform the computing device 1000 by specifying how the CPU(s) 1004 transition between states, as described above. The computing device 1000 can have access to computer-readable storage media storing computer-executable instructions, which, when executed by the computing device 1000, can perform the methods described in relation to FIG. 7, FIG. 8, and FIG. 9.

[0111] A computing device, such as the computing device 1000 depicted in FIG. 10, can also include an input / output controller 1032 for receiving and processing input from a number of input devices, such as a keyboard, a mouse, a touchpad, a touch screen, an electronic stylus, or other type of input device. Similarly, an input / output controller 1032 can provide output to a display, such as a computer monitor, a flat-panel display, a digital projector, a printer, a plotter, or other type of output device. It will be appreciated that the computing device 1000 can not include all of the components shown in FIG. 10, can include other components that are not explicitly shown in FIG. 10, or can utilize an architecture completely different than that shown in FIG. 10.

[0112] As described herein, a computing device can be a physical computing device, such as the computing device 1000 of FIG. 10. A computing node can also include a virtual machine host process and one or more virtual machine instances. Computer-executable instructions can be executed by the physical hardware of a computing device indirectly through interpretation and / or execution of instructions stored and executed in the context of a virtual machine.

[0113] As used throughout this application, the word “can” is used in a permissive sense (i.e., meaning having the potential to), rather than the mandatory sense (i.e., meaning must). The words “include,” “including,” and “includes” and the like mean including, but not limited to. As used herein, the singular form of “a,” “an,” and “the” include plural referencesunless the context clearly dictates otherwise

[0114] As used herein, the statement that two or more parts or components are “coupled” or “connected” shall mean that the parts are joined or operate together either directly or indirectly, i.e., through one or more intermediate parts or components, so long as a link occurs. As used herein, “directly coupled” means that two elements are directly in contact with each other. As used herein, “fixedly coupled” or “fixed” means that two components are coupled so as to move as one while maintaining a constant orientation relative to each other. Directional phrases used herein, such as, for example and without limitation, top, bottom, left, right, upper, lower, front, back, and derivatives thereof, relate to the orientation of the elements shown in the drawings and are not limiting upon the claims unless expressly recited therein.

[0115] These drawings can not be drawn to scale and can not precisely reflect structure or performance characteristics of any given embodiment and should not be interpreted as defining or limiting the range of values or properties encompassed by example embodiments.

[0116] As used in the specification and the appended claims, ranges can be expressed herein as from “about” one particular value, and / or to “about” another particular value. Unless otherwise expressly stated, it is in no way intended that any method set forth herein be construed as requiring that its steps be performed in a specific order. Accordingly, where a method claim does not actually recite an order to be followed by its steps or it is not otherwise specifically stated in the claims or descriptions that the steps are to be limited to a specific order, it is no way intended that an order be inferred, in any respect.

[0117] It will be apparent to those skilled in the art that various modifications and variations can be made without departing from the scope or spirit. Other embodiments will be apparent to those skilled in the art from consideration of the specification and practice disclosed herein. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit being indicated by the following claims.

Claims

What is claimed is:

1. A system comprising: a first device connected to a first battery pack, the first battery pack comprising a first plurality of cells; at least one user device located remote to the first device, the at least one user device configured to display real time information associated with the first battery pack; and a server in communication with the at least one user device and the first device, the server configured to: receive, from the first device, first real time voltage information associated with each of the first plurality of cells; and populate an interface of the at least one user device based on the first real time voltage information, wherein the populated interface displays data indicating whether a voltage imbalance exists amongst the first plurality of cells.

2. The system of claim 1, wherein the populated interface further displays data indicating a target voltage to which the at least one of the first plurality of cells needs to be charged to eliminate an existing voltage imbalance amongst the first plurality of cells.

3. The system of claim 1, further comprising: a second device connected to a second battery pack comprising a second plurality of cells, wherein the server and the at least one user device are located remote to the second device, the server further configured to: receive, from the second device, second real time voltage information associated with each of the second plurality of cells; and based on the second real time voltage information, populate the interface, wherein the populated interface further displays data indicating whether a voltage imbalance exists amongst the second plurality of cells.

4. The system of claim 3, wherein the first battery pack and the second battery pack are associated with a single original equipment manufacturer (OEM), and wherein the populatedinterface further displays data indicating whether a voltage imbalance exists between the first battery pack and the second battery pack.

5. The system of claim 4, wherein the populated interface further displays data indicating a target voltage to which the second battery pack needs to be charged to eliminate the voltage imbalance between the first battery pack and the second battery pack.

6. The system of claim 1, wherein the server is further configured to: receive, from the first device, information indicating a real time temperature associated with each of the first plurality of cells; and cause an alert to be displayed via the interface based on the real time temperature associated with at least one of the first plurality of cells exceeding a threshold.

7. The system of claim 1, wherein the interface is accessible by at least one of a manufacturer or distributor of the first battery pack when the first battery pack is located at a facility associated with the manufacturer or the distributor or when the first battery pack is in transit from the facility associated with the manufacturer or the distributor.

8. The system of claim 1, wherein the interface is accessible by an original equipment manufacturer (OEM) associated with the first battery pack when the first battery pack is in transit to a facility associated with the OEM or when the first battery pack is located at a facility associated with the OEM.

9. The system of claim 1, wherein the first device is configured to: based on determining that the voltage imbalance exists amongst the first plurality of cells, turn on a bypass resistor associated with the first battery pack to lower a state of charge (SOC) of at least one of the first plurality of cells.

10. The system of claim 1, wherein the server is configured to communicate with the at least one user device and the first device using at least one of cellular communication, Wi-Fi, or Bluetooth11. A method to provide real time information about the state of charge within battery packs, the method comprising: receiving, from a first device connected to a battery pack comprising a first plurality of cells and at a server located remote to the first device, first real time voltage information associated with each of the first plurality of cells; and populating an interface of at least one user device located remote to the first device based on the first real time voltage information, wherein the populated interface displays data indicating whether a voltage imbalance exists amongst the first plurality of cells.

12. The method of claim 11, wherein the populated interface further displays data indicating a target voltage to which the at least one of the first plurality of cells needs to be charged to eliminate an existing voltage imbalance amongst the first plurality of cells.

13. The method of claim 11, further comprising: receiving, from a second device connected to a second battery pack comprising a second plurality of cells and at the server, second real time voltage information associated with each of the second plurality of cells; and based on the second real time voltage information, populating the interface, wherein the populated interface further displays data indicating whether a voltage imbalance exists amongst the second plurality of cells.

14. The method of claim 13, wherein the first battery pack and the second battery pack are associated with a single original equipment manufacturer (OEM), and wherein the populated interface further displays data indicating whether a voltage imbalance exists between the first battery pack and the second battery pack.

15. The method of claim 14, wherein the populated interface further displays data indicating a target voltage to which the second battery pack needs to be charged to eliminate the voltage imbalance between the first battery pack and the second battery pack.

16. The method of claim 1 1 , further comprising: receiving, at the server and from the first device, information indicating a real time temperature associated with each of the first plurality of cells; and causing an alert to be displayed via the interface based on the real time temperature associated with at least one of the first plurality of cells exceeding a threshold.

17. The method of claim 11, wherein the interface is accessible by at least one of a manufacturer or distributor of the first battery pack when the first battery pack is located at a facility associated with the manufacturer or the distributor or when the first battery pack is in transit from the facility associated with the manufacturer or the distributor.

18. The method of claim 11, wherein the interface is accessible by an original equipment manufacturer (OEM) associated with the first battery pack when the first battery pack is in transit to a facility associated with the OEM or when the first battery pack is located at a facility associated with the OEM.

19. The method of claim 11, wherein the first device is configured to: based on determining that the voltage imbalance exists amongst the first plurality of cells, turn on a bypass resistor associated with the first battery pack to lower a state of charge (SOC) of at least one of the first plurality of cells.

20. The method of claim 11, wherein the server is configured to communicate with the at least one user device and the first device using at least one of cellular communication, Wi-Fi, or Bluetooth.21 . A method comprising to provide real time information about the state of charge between battery packs, the method comprising: receiving, from a first device connected to a first battery pack comprising a first plurality of cells and at a server located remote to the first device, first real time voltage information associated with each of the first plurality of cells;receiving, from a second device connected to a second battery pack comprising a second plurality of cells and at the server, second real time voltage information associated with each of the second plurality of cells; and populating an interface of at least one user device located remote to the first device and the second device based on the first real time voltage information and the second real time voltage information, wherein the populated interface displays data indicating whether a voltage imbalance exists between the first plurality of cells and the second plurality of cells.

22. The method of claim 21, wherein the populated interface further displays data indicating a target voltage to which the at least one of the first plurality of cells or at least one of the second plurality of cells needs to be charged to eliminate the existing voltage imbalance between the first plurality of cells and the second plurality of cells.

23. The method of claim 21, wherein the interface is accessible by an original equipment manufacturer (OEM) associated with the first battery pack and the second battery pack when the first battery pack and the second battery pack are in transit to a facility associated with the OEM or when the first battery pack and the second battery pack are located at a facility associated with the OEM.

Citation Information

Patent Citations

  • Battery energy storage system and control system and applications thereof

    US20160141894A1

  • Electric automobile energy monitoring and swapping network in remote monitoring of cloud computing network

    US20190126775A1

  • Battery management systems for energy storage devices

    US20220077508A1