PLANNING FOR MULTIPLE PRIMARY NODES

The simultaneous superframe protocol in battery management systems addresses data loss by transmitting redundant data on different frequencies, enhancing reliability and efficiency in wireless communication.

DE102025000643A1Pending Publication Date: 2025-08-28TEXAS INSTRUMENTS INC
View PDF 3 Cites 0 Cited by

Patent Information

Application Number
DE102025000643
Authority / Receiving Office
DE · DE
Patent Type
Applications
Current Assignee / Owner
Priority Date
2024-04-26
Filing Date
2025-02-20
Publication Date
2025-08-28

AI Technical Summary

Technical Problem

Wireless communication systems in battery management face data loss due to interference, physical obstructions, and shared bandwidth issues, leading to inefficiencies and reliance on primary device integrity, which are not adequately addressed by existing retransmission methods.

Method used

Implementing a simultaneous superframe protocol where multiple superframes occur simultaneously, allowing for redundant data transmission on different frequencies to increase robustness and reduce packet loss.

Benefits of technology

Enhances data redundancy and system robustness by ensuring data reaches intended destinations with higher reliability and efficiency, reducing the risk of interference and environmental obstructions.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 00000000_0000_ABST
    Figure 00000000_0000_ABST
Patent Text Reader

Abstract

A device includes a transceiver capable of wirelessly transmitting and receiving data, and a processor coupled to the transceiver.The processor may receive, from the transceiver and in a first time slot, first data transmitted by a first primary device; receive, from the transceiver and in a second time slot following the first time slot, second data transmitted by a second primary device; provide, to the transceiver and in a third time slot following the second time slot, third data to be transmitted to the first primary device on a first frequency, the third data including a battery cell status; and provide, to the transceiver and in a fourth time slot following the second time slot, the third data to be transmitted to the second primary device, the transceiver being configured to transmit the third data to the second primary device on a second frequency that is different from the first frequency.
Need to check novelty before this filing date? Find Prior Art

Description

BACKGROUND

[0001] Modern vehicles may contain multiple battery cells. Sensors can monitor cell-associated information such as temperature, voltage, and other indicators of cell status and integrity to ensure vehicle safety and proper operation. SUMMARY

[0002] In examples, a device includes a transceiver capable of wirelessly transmitting and receiving data, and a processor coupled to the transceiver.The processor may receive, from the transceiver and in a first time slot, first data transmitted by a first primary device; receive, from the transceiver and in a second time slot following the first time slot, second data transmitted by a second primary device; provide, to the transceiver and in a third time slot following the second time slot, third data to be transmitted to the first primary device on a first frequency, the third data including a battery cell status; and provide, to the transceiver and in a fourth time slot following the second time slot, the third data to be transmitted to the second primary device, the transceiver being configured to transmit the third data to the second primary device on a second frequency that is different from the first frequency. BRIEF DESCRIPTION OF THE DRAWINGS Fig. 1 is a schematic diagram of an automotive system including multiple primary and secondary devices configured to communicate using concurrent superframes, according to various examples. Fig. 2 is a block diagram of a system including multiple primary and secondary devices configured to communicate using concurrent superframes, according to various examples. Fig. 3A-3B show a timing diagram illustrating a concurrent superframe communication protocol according to various examples. Fig. 4 is a flowchart of a method for wireless communication using simultaneous superframes according to various examples. Fig. 5 is a flowchart of a method for wireless communication using simultaneous superframes according to various examples. Fig. 6 is a block diagram of a system configured to communicate using concurrent superframes, according to various examples. Fig. 7 is a block diagram of a system configured to communicate using concurrent superframes, according to various examples. DETAILED DESCRIPTION

[0003] Some electronic devices operate using batteries. For example, electric vehicles include multiple battery cells that provide power to these vehicles. Because battery cells in an electronic device can provide large amounts of power, and further because the power provided by the battery cells may be essential to the operation of the electronic device, the electronic device may include a system for managing the battery cells.

[0004] Battery management systems (BMSs) can manage the battery cells of an electronic device in various ways. For example, a BMS can monitor the integrity (e.g., voltage, current, temperature) of battery cells in an electronic device. Furthermore, the BMS can control various battery cells to manage the amount of power provided by the battery cells and direct that power within the electronic device. Generally, a BMS includes multiple components, such as multiple battery modules and a controller for managing the battery modules. Each battery module, in turn, can be coupled to multiple battery cells and include a battery monitor for monitoring those battery cells.Thus, the battery cells coupled to a battery module supply power to the electronic device; the battery monitoring device in the battery module monitors the integrity and operation of the battery cells in that battery module; and the controller communicates with the battery monitoring device to ensure that the battery module and its cells are operating properly. The controller may also communicate with the battery monitoring device to control the operation of the battery cells, such as turning on, turning off, redirecting, or otherwise balancing the power provided by those battery cells.

[0005] BMSs can incorporate wireless technology to implement a wireless battery management system (WBMS). For example, a primary device contains or is coupled to a controller, and a secondary device contains a battery module that controls multiple battery cells. The primary and secondary devices can communicate wirelessly, for example, using radio frequencies. In some protocols, a superframe is useful to enable wireless communication between the primary and secondary devices. A superframe is a wireless data communication scheme that enables the ordered communication of data between two or more wireless devices. In a superframe, the primary device first sends a downlink (DL) communication (or DL ​​packet) to multiple secondary devices.The secondary devices respond individually to the primary device with uplink (UL) communications (or UL packets) in a serial manner.

[0006] Wireless communications systems can experience data loss due to a suboptimal communications environment. Data loss can occur due to interference caused by competing wireless signals (e.g., traffic in the same or similar frequency band), physical obstructions, or environmental conditions such as excessive humidity. Data can encounter obstacles that can degrade signal quality and lead to data loss. Furthermore, wireless networks operate on shared bandwidth, meaning multiple devices compete for the same frequency spectrum, leading to collisions and data congestion. In some cases, multipath propagation, in which transmitted signals take multiple, different paths to reach the receiver, leads to phase cancellation. These and other factors can contribute to packet loss in wireless communications.

[0007] Previous solutions have attempted to address such data losses by retransmitting packets in subsequent superframes. For example, a data packet destined for a primary device that was lost during transmission in a first superframe would be retransmitted to the primary device in a second, subsequent superframe. This approach is time-consuming and inefficient. Furthermore, this approach relies heavily on the integrity of the primary device. If the primary device ceases to function (e.g., due to power loss, malfunction, etc.), the system also ceases to function. These previous solutions are therefore inadequate.

[0008] This disclosure describes various examples of a wireless communication technique for resolving data loss by increasing data transmission redundancy using concurrent superframes. In particular, example systems (e.g., WBMSs) may include first and second primary devices coupled to a common battery controller. The first and second primary devices are configured for wireless communication. Example systems may further include first and second secondary devices, each coupled to one or more battery cells, configured to monitor parameters of those battery cells (e.g., battery cell status) and configured to wirelessly communicate with other devices.

[0009] The primary and secondary devices described herein may be configurable to communicate wirelessly using a concurrent superframe protocol. Each superframe contains multiple time slots, and in each time slot, communications occur according to a schedule. For example, Device A may transmit synchronization data to Device B in a first time slot, and Device B may transmit measurement data (e.g., battery status data) to Device A in a second time slot. Superframes are generally transmitted serially, one superframe at a time. Superframes are not transmitted in parallel (i.e., simultaneously). However, in the example systems described herein, superframes are transmitted in parallel (i.e.,simultaneously), and superframe slot communications are scheduled in a manner that significantly improves data redundancy and system robustness compared to systems that do not use the concurrent superframe scheme described here.

[0010] In the concurrent superframe scheme, a first superframe and a second superframe occur simultaneously, which means that the first slot of the first superframe occurs simultaneously with the first slot of the second superframe; the second slots of the first and second superframes occur simultaneously, and so on. During the first slots of the first and second superframes, the aforementioned first primary device sends synchronization data by broadcast to the second primary device and to the first and second secondary devices.The second primary device and the first and second secondary devices each receive this synchronization data and use the synchronization data to identify and store clock differences between that device and the first primary device, and further use such clock differences to enable synchronized, timely communication between the various devices. Similarly, during the second slots of the first and second superframes, the aforementioned second primary device broadcasts synchronization data to the first primary device and to the first and second secondary devices.The first primary device and the first and second secondary devices each receive this synchronization data and use the synchronization data to identify and store clock differences between that device and the second primary device, and further use such clock differences to enable synchronized, timely communication between the various devices.

[0011] During the third slots of the first and second superframes (which, as described above, are concurrent slots), the first secondary device transmits data to the first primary device, and the second secondary device transmits data to the second primary device. The two transmissions may occur on different frequencies or channels that are sufficiently separated in the frequency domain to avoid interference. During the fourth and final slot of the first and second superframes (which, as described above, are concurrent slots), the first secondary device transmits the same data it transmitted during the third slots, but this time the first secondary device transmits the data to the second primary device.Similarly, during the fourth slots, the second secondary device transmits the same data it transmitted during the third slots, but this time the second secondary device transmits the data to the first primary device. The two transmissions may occur on different frequencies or channels that are sufficiently separated in the frequency domain to avoid interference. In examples, all four transmissions in the third and fourth slots occur on different frequencies or channels to reduce the risk of packet loss.By transmitting the same data twice during concurrent superframes to different primary devices at different frequencies, the probability that at least one instance of each data element will reach the intended primary device (and thus also the battery controller coupled to the first and second primary devices) is significantly increased. This increases the overall robustness of the system. Furthermore, the use of concurrent superframes increases both data throughput and performance compared to solutions that use consecutive superframes, since the same amount of data is transmitted in half the time compared to consecutive superframes.

[0012] Fig. 1 is a schematic diagram of an automotive system 98 including multiple primary and secondary devices configured to communicate using simultaneous superframes, according to various examples. The system 98 may be a vehicle, such as an automobile, a watercraft, an aircraft, a spacecraft, or a military vehicle. The system 98 may also be a non-vehicle-based system that includes battery cells being monitored. Further, the system 98 may be any type of system in which information is to be repeatedly communicated between wireless devices. Additional examples of the system 98 may include one or more of the following in any combination: smartphones; laptop computers; desktop computers; tablets; notebooks; appliances; and entertainment devices.The remainder of this description assumes that system 98 is an automobile, but the scope of this disclosure is not limited to automobiles or any other particular type of system. Furthermore, although the concurrent superframe scheme is described herein in the context of wireless battery management systems, the teachings of this disclosure may be further extended to other types of systems, including home automation, industrial automation, and wireless sensor networks.

[0013] The exemplary system 98 includes a wireless battery management system (WBMS) 100. The WBMS 100 may be located in any part of the automobile, but in some examples, the WBMS 100 is located in, on, or near a lower portion of a chassis of the automobile, such as under one or more seats of the automobile. The WBMS 100 may include one or more battery controllers 102 that monitor and control the WBMS 100 (e.g.,by balancing loads between devices and determining whether to measure current, voltage, temperature, or other parameters of battery cells); one or more primary devices 104 coupled to the battery controllers 102 via one or more wired or wireless connections 110; one or more secondary devices 106; and one or more battery cells 108 coupled to the one or more secondary devices 106 via one or more wired or wireless connections 112. The primary devices 104 communicate wirelessly with the secondary devices 106 using a concurrent superframe protocol as described herein.

[0014] Fig. 2 is a block diagram of the WBMS 100 according to various examples. The WBMS 100 may include one or more battery controllers 102 coupled to primary devices 104a and 104b via one or more wired or wireless connections 110a and 110b, respectively. The primary device 104a includes a processor 114a, a transceiver 115a coupled to the processor 114a, and a memory 116a (e.g., random access memory (RAM), read-only memory (ROM)) coupled to the processor 114a. The memory 116a stores executable code 118a. The processor 114a, upon execution of the executable code 118a, performs some or all of the actions attributed herein to the primary device 104a and / or the processor 114a. An antenna 120a is coupled to the transceiver 115a and is configured to transmit and receive signals to and from other devices in the WBMS 100.The primary device 104b includes a processor 114b coupled to a transceiver 115b and a memory 116b (e.g., RAM or ROM). The memory 116b stores executable code 118b. The processor 114b, upon execution of the executable code 118b, performs some or all of the actions attributed herein to the primary device 104b and / or the processor 114b. An antenna 120b is coupled to the transceiver 115b and is configured to transmit and receive signals to and from other devices in the WBMS 100.

[0015] Any processors described here may be implemented using any type of programmable circuitry. Examples of programmable circuitry include, but are not limited to, programmable microprocessors, field-programmable gate arrays (FPGAs) capable of instantiating instructions, central processing units (CPUs), graphics processing units (GPUs), digital signal processors (DSPs), XPUs, or microcontrollers, and integrated circuits such as application-specific integrated circuits (ASICs).

[0016] Furthermore, any transceivers described herein may use the license-free 2.4 gigahertz (GHz) ISM (Industrial, Scientific, and Medical) band from 2.4 GHz to 2.483 GHz, which is compliant with the Bluetooth Special Interest Group (SIG). Additionally or alternatively, the transceivers may use 2 megabits per second (Mbps) Bluetooth Low Energy (BLE) over the physical layer (PHY). The Open Systems Interconnection (OSI) model includes the PHY as a layer used to communicate raw bits over a physical medium. In examples described herein, the PHY is free space that the WBMS 100 uses to wirelessly communicate between the various devices of the WBMS 100. In some examples, the transceivers described herein are instantiated by programmable circuitry that executes RF instructions.

[0017] A secondary device 106a may include a processor 122a coupled to a memory 124a that stores executable code 126a. The processor 122a, upon execution of the executable code 126a, may perform some or all of the actions attributed herein to the secondary device 106a and / or the processor 122a. One or more transceivers 128a are coupled to the processor 122a, and one or more antennas 130a are coupled to the one or more transceivers 128a. The secondary device 106a is coupled to one or more battery cells 108a via one or more connections 112a.

[0018] A secondary device 106b may include a processor 122b coupled to a memory 124b that stores executable code 126b. The processor 122b, upon execution of the executable code 126b, may perform some or all of the actions attributed herein to the secondary device 106b and / or the processor 122b. One or more transceivers 128b are coupled to the processor 122b, and one or more antennas 130b are coupled to the one or more transceivers 128b. The secondary device 106b is coupled to one or more battery cells 108b via one or more connections 112b.

[0019] A secondary device 106c may include a processor 122c coupled to a memory 124c that stores executable code 126c. The processor 122c, upon execution of the executable code 126c, may perform some or all of the actions attributed herein to the secondary device 106c and / or the processor 122c. One or more transceivers 128c are coupled to the processor 122c, and one or more antennas 130c are coupled to the one or more transceivers 128c. The secondary device 106c is coupled to one or more battery cells 108c via one or more connections 112c.

[0020] The primary devices 104a, b of Fig. 2 may be collectively referred to herein as primary devices 104. Similarly, secondary devices 106a-c may be collectively referred to herein as secondary devices 106, etc. A similar convention may be used for any or all of the features illustrated in the drawings.

[0021] The primary and secondary devices described herein (e.g., primary devices 104, secondary devices 106) may be implemented as a CC2662 and / or a BQ79616, manufactured by TEXAS INSTRUMENTS INC. ®in Dallas, TX. Further example details of the CC2662 and BW79616 can be found in the datasheet "CC2662R-Q1 SimpleLinkTM Wireless BMS MCU," revised July 2023, available at https: / / www.ti.com / product / CC2662R-Q1, and the datasheet "BQ79616-Q1, BQ79614-Q1, BQ79612-Q1, Functional Safety-Compliant Automotive 16S / 14S / 12S Battery Monitor, Balancer and Integrated Hardware Protector," revised September 2022, available at https: / / www.ti.com / product / BQ79616-Q1, each of which is incorporated by reference in its entirety.

[0022] Each of the secondary devices 106 is configured to monitor the status of respective battery cells 108 (e.g., the voltage provided by the battery cells 108, the temperatures of the battery cells 108). For example, each of the secondary devices 106 may include, be coupled to, or communicate with one or more sensors configured to measure a variety of parameters associated with the battery cells 108. The sensors may forward the sensed data to the processors 122 of the secondary devices 106 via a UART (Universal Asynchronous Receiver / Transmitter) protocol or any other suitable protocol. Further, each of the secondary devices 106 is configured to communicate with both of the primary devices 104.For example, secondary device 106a may communicate with primary device 104a during one slot of a superframe, and secondary device 106a may communicate with primary device 104b during a different slot of the superframe. Alternatively, secondary device 106a may communicate with primary devices 104a,b simultaneously using different transceivers 128a. Secondary devices 106b,c may communicate with primary devices 104a,b similarly to secondary device 106a. In some examples, each of secondary devices 106a-c is configured to communicate with one or more of the remaining secondary devices 106a-c. For example, secondary device 106a may be configured to communicate with one or more of secondary devices 106b,c.The primary devices 104a, b may also communicate with the secondary devices 106a-c and with each other. For example, the primary device 104a may transmit data to the primary device 104b and / or the secondary device 106a and / or the secondary device 106b and / or the secondary device 106c. The primary device 104b may operate similarly to the primary device 104a. The communications transmitted by the primary devices 104 may be received by one or more of the battery controllers 102. Likewise, the communications received by the primary devices 104 may be provided to one or more of the battery controllers 102.

[0023] The Fig. The WBMS 100 shown in Figure 2 is illustrative. In some examples, the WBMS 100 may include any number of primary devices, secondary devices, battery controllers, battery cells, other components, and wired and / or wireless connections between any one or more of the foregoing. Any and all such variations are contemplated and included within the scope of this disclosure.

[0024] Further examples of the Fig. 1 and Fig. The components shown in Figure 2 can be found in the references incorporated herein by reference, including U.S. Application No. 17 / 823,138, filed August 30, 2022, entitled “Multiple Primary Nodes for Wireless Battery Management System Robustness,” which is hereby incorporated by reference in its entirety.

[0025] As described above, the various components of the WBMS 100 can communicate with each other according to a concurrent superframe protocol. A superframe interval is the period of time during which a superframe occurs. Thus, "concurrent superframes" are multiple superframes that overlap in time such that they occur during a single superframe interval. Fig. 3A-3B show a timing diagram 300 illustrating a simultaneous superframe communication protocol such as that used in the WBMS 100 of Fig. 1 and Fig. 2, according to various examples. In particular, the timing diagram 300 includes a superframe 301 and a separate superframe 302 that occur concurrently during a single superframe interval. Each superframe includes multiple slots in which various devices in the WBMS 100 may transmit or receive data. For example, superframe 301 includes slots 311-316, and superframe 302 includes slots 317-322. Because superframes 301, 302 are concurrent superframes, each of slots 311-316 occurs concurrently with a respective slot 317-322, as shown.

[0026] The superframe 301 describes the behavior of the devices 303-306. In the example shown, the device 303 may be a primary device, such as the primary devices 104a, b. The remaining devices 304-306 may be secondary devices, such as the secondary devices 106a-c. To simplify the description, Fig. 3A-3B, devices 303-306 are referred to as "Main 1", "Device 1", "Device 2", and "Device n", respectively. The superframe 302 describes the behavior of devices 304, 305, 307, and 308. In the example shown, device 307 may be a primary device, such as primary devices 104a, b. The remaining devices 304, 305, and 308 may be secondary devices, such as secondary devices 106a-c. For ease of description, Fig. 3A-3B, devices 307, 305, 304, and 308 are referred to as “Main 2,” “Device 2,” “Device 1,” and “Device n-1,” respectively.

[0027] Before the first slots 311 and 317, superframes 301 and 302 allow DL protection transmission periods 323 and 356, respectively, which are useful for reducing the risk of interference with other superframes that occurred before superframes 301 and 302. At the time of DL protection transmission periods 323 and 356, secondary devices 304 (e.g., node 1), 305 (e.g., node 2), 306 (e.g., node N), and 308 (e.g., node N-1) enter receive modes 338, 344, 350, and 383 (TsRxWait), respectively, meaning that these secondary devices 304, 305, 306, and 308 are ready to receive transmissions from other device(s).

[0028] After the DL protection transmission periods 323 and 356 expire, concurrent slots 311 and 317 begin. In slot 311, the primary device 303 (e.g., Main 1) broadcasts data 324 to the remaining devices 304-308. For example, the primary device 104a may broadcast data to the primary device 104b and the secondary devices 106a-c during slots 311 and 317. The data broadcast by the primary device 303 may include synchronization information that the receiving devices can use to synchronize their clocks with a clock of the primary device 303. For example, the data broadcast by the primary device 303 may include timestamp data that the receiving devices can use to synchronize their clocks with the clock of the primary device 303.The data transmitted by the primary device 303 via broadcast may be referred to here as downlinks. Numeral 325 indicates that the primary device 303 is in a transmit mode (TsMaxTx) during transmission. At the same time, the secondary devices 304, 305, 306, and 308 are in receive modes 338, 344, 350, and 383 (TsRxWait), respectively, and the primary device 307 (e.g., Main 2) is in a receive mode 358. During slots 311 and 317, the primary device 303 transitions from a transmit mode to a receive mode, as indicated by numeral 326 (Tx2Rx). Similarly, during slots 311 and 317, primary device 307 transitions from a receive mode to a transmit mode, as indicated by numeral 359 (Rx2Tx). Secondary devices 304, 305, 306, and 308 remain in their receive modes.

[0029] Slots 312 and 318 occur concurrently after slots 311 and 317. During slots 312 and 318, primary device 307 broadcasts data 360 to the remaining devices 303-306 and 308. The broadcast data may be similar to the synchronization data described above with reference to slots 311 and 317. During the transmission of data 360, primary device 307 is in transmit mode 361 (TsMaxTx), while primary device 303 is in receive mode 328. Secondary devices 304, 305, 306, and 308 are also in receive modes at this time. Accordingly, the primary device 303 and the secondary devices 304, 305, 306 and 308 receive the data 360 broadcast by the primary device 307.For example, primary device 104b may broadcast synchronization data to primary device 104a and secondary devices 106a-c. After completing the transmission and reception in slots 312 and 318, primary device 307 transitions from a transmit mode to a receive mode, as indicated by numeral 362 (Tx2Rx), and secondary devices 304 and 305 transition from receive modes to transmit modes, as indicated by numerals 341 and 374 (Rx2Tx).

[0030] Synchronization is complete after slots 312 and 318. Slots 313 and 319 occur concurrently after slots 312 and 318. During slots 313 and 319, multiple secondary devices simultaneously transmit data (e.g., status information acquired from any of the battery cells 108a-c) to various primary devices 303, 307. For example, secondary device 304 may transmit data 343 to primary device 303, and concurrently, secondary device 305 may transmit data 376 to primary device 307. To enable such transmissions, secondary device 304 is in transmission mode 342 (TsMaxTx), and secondary device 305 is in transmission mode 375 (TsMaxTx). To enable reception of the transmitted data, the primary device 303 is in receive mode 331 (TsRxWait), and the primary device 307 is in receive mode 364 (TsRxWait).The data sent by secondary devices via broadcast to primary devices can be referred to here as uplinks.

[0031] Slots 314 and 320 occur concurrently after slots 313 and 319. During slots 314 and 320, secondary device 305 retransmits the same data 376 that secondary device 305 transmitted during slot 319, and secondary device 304 retransmits the same data 376 that secondary device 304 transmitted during slot 313. Although secondary device 305 transmits the same data 376 in both slots 319 and 314, the destinations of the data 376 are different. During slot 319, secondary device 305 transmits data 376 to primary device 307, while in slot 314, secondary device 305 transmits data 376 to primary device 303.By transmitting data 376 during multiple slots and to different primary devices, secondary device 305 increases the likelihood that data 376 will be received by at least one of primary devices 303 and 307, and thus also by a battery controller (e.g., battery controllers 102) coupled to primary devices 303 and 307. In this way, the risk of data loss is reduced. Likewise, although secondary device 304 transmits the same data 343 in both slots 313 and 320, the destinations of the data 343 differ. During slot 313, secondary device 304 transmits data 343 to primary device 303, while in slot 320, secondary device 304 transmits data 343 to primary device 307.By transmitting data 343 during multiple slots and to different primary devices, secondary device 304 increases the likelihood that data 343 will be received by at least one of primary devices 303 and 307 and thus also by a battery controller (e.g., battery controllers 102) coupled to primary devices 303 and 307.

[0032] Slots 315 and 321 occur concurrently after slots 314 and 320. During slot 315, secondary device 306 transitions from receive mode to transmit mode, as indicated by numeral 353 (Rx2Tx). Similarly, during slot 321, secondary device 308 transitions from receive mode to transmit mode, as indicated by numeral 386 (Rx2Tx). Although a single slot 315 is shown between slots 314 and 316 and a single slot 321 is shown between slots 320 and 322, any number of slots n may be included between slots 314 and 316, and the same number of slots n may be included between slots 320 and 322.

[0033] Slots 316 and 322 occur concurrently after slots 315 and 321. During slot 316, secondary device 306 transmits data 355 to primary device 303 (while in receive mode 354, TsMaxTx). Although this Fig. 3A-3B, the secondary device 306 has already transmitted data 355 to the primary device 307 during a previous slot between slots 314 / 320 and slots 316 / 322. Thus, by transmitting data 355 twice during different time slots and to different primary devices, the risk of data loss is reduced. Likewise, during slot 322, the secondary device 308 transmits data 388 to the primary device 307 (while in transmit mode 387, TsMaxTx). Although this is not explicitly shown in Fig. 3A-3B, the secondary device 308 has already transmitted data 388 to the primary device 303 during a previous slot between slots 314 / 320 and slots 316 / 322. Thus, transmitting data 388 twice during different time slots and to different primary devices reduces the risk of data loss.

[0034] Redundant data transmissions need not occur in consecutive slots in all implementations of the techniques of this disclosure. For example, although timing diagram 300 illustrates data 343 being transmitted in consecutive slots 313 and 320, in examples, data 343 may be transmitted in non-consecutive slots, such as slots 313 and 322. (Transmitting the same data in non-consecutive time slots may be advantageous, for example, if the passage of additional time between slots facilitates the removal of a condition or physical obstruction that prevented successful reception of the data in the first of the two time slots.)) The data transmission redundancy contemplated here can be achieved as long as a particular data item is transmitted twice in a given superframe interval to different primary devices and at different frequencies. This means that the data item is transmitted at a first frequency and in a first superframe to a first primary device, and then transmitted again at a second frequency, different from the first frequency, and in a second superframe concurrently with the first superframe to a second primary device. Data redundancy can be achieved even if the data item is transmitted twice to the same primary device.For example, a particular piece of data may be transmitted to a first primary device on a first frequency and in a first superframe, and then transmitted again to the same first primary device on a second frequency, different from the first frequency, and in a second superframe concurrent with the first superframe. Data redundancy may be achieved even if the piece of data is transmitted twice on the same frequency. For example, a particular piece of data may be transmitted to a first primary device on a first frequency and in a first superframe, and then transmitted again to a second primary device on the same first frequency and in a second superframe concurrent with the first superframe. Data redundancy may be achieved even if the piece of data is transmitted twice on the same frequency and to the same primary device.For example, a particular data item may be transmitted to a first primary device on a first frequency and in a first superframe, and then retransmitted to the same first primary device on the same first frequency but in a second superframe concurrent with the first superframe. Any and all such variations are contemplated and included within the scope of this disclosure.

[0035] To reduce the risk of interference between simultaneous data transmissions and further reduce the risk that transmissions of the same data during separate slots will not reach their intended destinations, secondary devices may employ any of a variety of frequency hopping schemes. For example, with reference to timing diagram 300, in simultaneous slots 313 and 319, data 343 may be transmitted on a first frequency, and data 376 may be transmitted concurrently on a second frequency that is different from the first frequency. The first and second frequencies may be separated by at least 5 MHz or by at least 10 MHz (or, in terms of channels, the channels used are separated by at least two channels, three channels, or five channels). Similarly, in simultaneous slots 314 and 320, data 343 and 376 may be transmitted concurrently on first and second frequencies, respectively.a second frequency, wherein the first and second frequencies are separated by at least 5 MHz or at least 10 MHz (or, with respect to channels, the channels used are separated by at least two channels, three channels, or five channels). Using different frequencies for simultaneous data transmission reduces the risk of interference between transmissions. Separations of at least 5 MHz or 10 MHz are examples of minimum separations; in some examples, the techniques of this disclosure may be implemented with a minimum frequency separation other than 5 MHz or 10 MHz.

[0036] Other frequencies may also be useful across different slots. For example, in the timing diagram 300, the data 343 in slot 313 may be transmitted at a first frequency and in slot 320 at a second frequency separated from the first frequency by at least 5 MHz or by at least 10 MHz (or, in terms of channels, the channels used are separated from each other by at least two channels, three channels, or five channels). Similarly, the data 376 in slot 319 may be transmitted at a first frequency and in slot 314 at a second frequency separated from the first frequency by at least 5 MHz or by at least 10 MHz (or, in terms of channels, the channels used are separated from each other by at least two channels, three channels, or five channels). To enable such separation of the transmission frequencies, primary devices (e.g.,Primary devices 104) may transmit specific frequency hopping schemes in their downlinks to secondary devices (e.g., secondary devices 106) to be used during data transmissions. Furthermore, in some examples, secondary devices may receive and transmit data at similar frequencies. For example, referring to timing diagram 300, secondary device 304 may receive data 324 in slot 311 at a first frequency, receive data 360 in slot 318 at a second frequency, transmit data 343 in slot 313 at a third frequency, and transmit data 343 in slot 320 at a fourth frequency. In examples, the first and third frequencies may be the same. In examples, the first and fourth frequencies may be the same. In examples, the second and third frequencies may be the same. In examples, the second and fourth frequencies may be the same.

[0037] As just one example, a primary device may use a frequency hopping sequence with thirty-seven channels in the ISM (Industrial, Scientific, and Medical) band. These bands have a random order in the hopping sequence and satisfy the condition that the adjacent frequencies are separated by 5 MHz or 10 MHz. For example, the first hopping sequence is {2410, 2404, 2416, ....}. The second hopping sequence may be a different version of the first hopping sequence, but shifted by one position. Therefore, the second hopping sequence is {2404, 2416, .... 2410}, maintaining a 5 MHz or 10 MHz separation for the primary device operating at a first frequency (2410) and another primary device operating at a second frequency (2404). After each hop, the first and second frequencies remain 5 MHz or 10 MHz apart.

[0038] In addition to transmitting frequency hopping schemes in downlinks, primary devices (e.g., primary devices 104) may transmit scheduling instructions to secondary devices (e.g., secondary devices 106) in downlinks. For example, one or more primary devices may be configured to instruct secondary devices regarding the specific slots of one or more given superframes and the specific channels and / or frequencies in which the secondary devices should transmit uplinks to the primary devices. Primary devices may change the scheduling instructions with each superframe interval or, alternatively, may maintain the same scheduling instructions for multiple consecutive superframe intervals.Primary devices may also transmit additional information to the secondary devices, such as acknowledgments for uplink transmissions from a previous superframe, an indication of when the next superframe can begin, an adaptive frequency hopping countdown, etc. In some examples, the primary devices do not transmit scheduling instructions to the secondary devices in the downlinks. Instead, some or all devices in the WBMS 100 are preprogrammed with a defined schedule to be followed for some or all superframe intervals unless instructed otherwise by one or more primary devices. Alternatively, primary devices may transmit a single downlink with scheduling instructions to be followed in all superframe intervals until further notice. A battery controller (e.g.,Battery controller 102) may provide scheduling instructions to the primary devices, which the primary devices may then distribute to the remaining devices of the WBMS 100.

[0039] The secondary devices transmit data to the primary devices according to the scheduling instructions and channel and / or frequency instructions provided by the primary devices or preprogrammed into the secondary devices. Upon receiving a downlink transmission from a primary device, a secondary device may parse the transmission to determine the slots and channels or frequencies in which the secondary device is scheduled to transmit uplink information to the one or more primary devices. In some examples, information regarding how to parse the downlink transmission may be provided to the secondary device during a WBMS network formation process.

[0040] In some examples, secondary devices include multiple transceivers. For example, as in Fig. 2, the secondary device 106a includes a plurality of transceivers 128a. In examples, the plurality of transceivers 128a may be Fig. 2 simultaneously (in the same slot) transmit data 343 twice using different transceivers 128a. Such simultaneous transmissions may occur on the same or different frequencies. The transmissions may be directed to the same or different primary devices 104 (e.g., both the secondary and primary devices may have multiple transceivers communicating simultaneously on different frequencies). Thus, the same level of redundancy achieved by secondary devices with a single transceiver transmitting the same data in different slots can be achieved by secondary devices with multiple transceivers in a more compressed time frame.

[0041] In some examples, primary devices (e.g., primary devices 104a, b) may be spatially spaced apart (e.g., by 6.25 cm (half the wavelength at 2.4 GHz)). Providing a threshold amount of separation between the primary devices increases the likelihood that environmental obstacles that impede the successful transmission of data packets to one primary device will not also impede the successful transmission of data packets to the other primary device.

[0042] In some examples, uplink data transmissions may be performed in consecutive slots of concurrent superframes to accommodate large amounts of data that otherwise could not be transmitted in a single uplink. Such techniques are described in U.S. Patent Application No. 18 / 227,821, filed July 28, 2023, entitled "Methods and Apparatus to Determine Communication Schedules for Wireless Battery Systems," which is hereby incorporated by reference in its entirety. All subject matter described in U.S. Patent Application No. 18 / 345,636, filed June 30, 2023, entitled "Hierarchical Wireless Battery Management System," is hereby incorporated by reference in its entirety.

[0043] Fig. 4 is a flowchart of a method 400 for wireless communication using simultaneous superframes according to various examples. In examples, a secondary device (e.g., secondary device 106a, b, or c) performs the method 400 using the method described in Fig. 3A-3B. Thus, the method 400 is described here from the perspective of the exemplary secondary device 106a and with reference to Fig. 2-4 described.

[0044] The method 400 includes receiving, from a transceiver and in a first time slot, first data transmitted by a first primary device (402). For example, the processor 122a of the secondary device 106a may receive, via a transceiver 128a and during slot 311 (occurring concurrently with slot 317), first data transmitted by the primary device 104a. This data may be, for example, the data 324 broadcast by the primary device 303 (such as the primary device 104a) to the remaining primary and secondary devices 304-308 (which may include the secondary device 106a), as described above.

[0045] The method 400 includes receiving, from the transceiver and in a second time slot following the first time slot, second data transmitted by a second primary device (404). For example, the processor 122a of the secondary device 106a may receive, via a transceiver 128a and during slot 312 (occurring concurrently with slot 317), second data transmitted by the primary device 104b. This data may be, for example, the data 360 broadcast by the primary device 307 (such as the primary device 104b), as described above, to the remaining primary and secondary devices 303-306 and 308 (which may include the secondary device 106a).

[0046] The method 400 includes providing, to the transceiver and in a third time slot following the second time slot, third data to be transmitted on a first frequency to the first primary device, wherein the third data includes battery cell status (406). For example, the processor 122a of the secondary device 106a may transmit third data to the first primary device via a transceiver 128a and during slot 313 (occurring concurrently with slot 319). This data may be, for example, the data 343 transmitted by the secondary device 304 (such as the secondary device 106a) to the primary device 303 (such as the primary device 104a), as described above. The data may include battery cell status, such as status information (e.g., voltage, current, temperature) regarding the battery cells 108a.Transceiver 128a may transmit the third data at a particular frequency that differs from the frequency at which other data is transmitted during the third slot (e.g., slot 313). In examples, the difference between frequencies is at least 5 MHz or at least 10 MHz.

[0047] The method 400 includes delivering, to the transceiver and in a fourth time slot following the second time slot, the third data to be transmitted to the second primary device, wherein the transceiver is configured to transmit the third data to the second primary device at a second frequency different from the first frequency (408). For example, the processor 122a of the secondary device 106a may transmit, via a transceiver 128a and during slot 314 (occurring concurrently with slot 320), the same third data that was transmitted in the third time slot of step 406. However, in the fourth slot of step 408, the third data (e.g., data 343) is transmitted to a different primary device (e.g., primary device 307, such as primary device 104b) and at a different frequency than the frequency used in step 406 (e.g.,wherein the transmission frequencies in steps 406 and 408 are separated by at least 5 MHz or by at least 10 MHz).

[0048] By transmitting the same data at different frequencies and in different slots, secondary device 106a increases the likelihood that the data will reach its intended destination. The risk of data loss is reduced.

[0049] Fig. 5 is a flowchart of a method 500 for wireless communication using simultaneous superframes according to various examples. In examples, a primary device (e.g., primary device 104a or b) performs the method 500 using the Fig. 3A-3B. Thus, the method 500 is described herein from the perspective of the exemplary primary device 104b.

[0050] The method 500 includes receiving, from a transceiver and in a first time slot, first data broadcast by a primary device (502). For example, the processor 114b of the primary device 104b (e.g., primary device 307) may receive first data (e.g., data 324) broadcast by the primary device 104a (e.g., primary device 303) from the transceiver 115b and in slot 311.

[0051] The method 500 includes providing, to the transceiver and in a second time slot, second data to be broadcast to the primary device and to first and second secondary devices (504). For example, the processor 114b of the primary device 104b (e.g., primary device 307) may provide second data (e.g., data 360) to the transceiver 115b and in slot 313 to be broadcast to the primary device (e.g., primary device 303, 104a) and to first and second secondary devices (e.g., secondary devices 304, 305, such as secondary devices 106a, b).

[0052] The method 500 includes receiving, from the transceiver 115b and in a third time slot following the second time slot, third data transmitted by the first secondary device, wherein the third data is transmitted on a different frequency than fourth data transmitted by the second secondary device to the primary device in the third time slot (506). For example, the processor 114b of the primary device 104b (e.g., primary device 307) may receive from the transceiver 115b and in slot 313 third data (e.g., data 376) transmitted on a different frequency than fourth data (e.g., data 343) transmitted by the second secondary device (e.g., secondary device 304, 106b) to the primary device 303 (e.g., primary device 104a). The data 376 may have been transmitted by the secondary device 305 (e.g., the secondary device 106a).The frequencies on which data 343 and 376 are transmitted in the third time slot are separated by at least 5 MHz or by at least 10 MHz.

[0053] The method 500 includes receiving, from the transceiver and in a fourth time slot following the third time slot, the fourth data transmitted by the second secondary device, wherein the fourth data is transmitted on a different frequency than the third data transmitted by the first secondary device to the primary device in the fourth time slot (508). For example, the processor 114b of the primary device 104b (e.g., primary device 307) may receive from the transceiver 115b and in slot 314 the fourth data (e.g., data 343) transmitted by the second secondary device (e.g., secondary devices 304, 106b). The third data (e.g., data 376) is also transmitted to the secondary device 305 (e.g., secondary device 106a) during slot 314.The third and fourth data are transmitted on different frequencies during slot 314, wherein the frequencies are separated by at least 5 MHz or by at least 10 MHz.

[0054] In this way, data 343 is transmitted twice (e.g., once during slot 313 and once during slot 320), and data 376 is transmitted twice (e.g., once during slot 319 and once during slot 314). By transmitting each data item twice in different slots of different, concurrent superframes (i.e., twice during the same superframe interval) and at different frequencies, the probability that at least one of the two data transmissions will reach the battery controllers 102 is significantly increased.

[0055] Fig. 6 is a block diagram of an exemplary implementation of the WBMS 100 of Fig. 1 and Fig. 2. The WBMS 100 from Fig. 6 is designed to operate according to the scheme of simultaneous superframes described here, such as that described with reference to Fig. 3-5. The WBMS 100 from Fig. 6 may be instantiated by programmable circuitry, such as a central processing unit (CPU), that executes first instructions (e.g., creating an instance of, creating for an arbitrary period of time, materializing, implementing, etc.). Additionally or alternatively, the WBMS 100 may be Fig. 6 may be instantiated by (i) an application-specific integrated circuit (ASIC) and / or (ii) a field-programmable gate array (FPGA) that is structured and / or configured to perform operations corresponding to the first instructions in response to the execution of second instructions. Part or all of the circuitry of Fig. 6 can therefore be instantiated at the same time or at different times. Part or all of the circuitry of Fig. 6 may, for example, be instantiated in one or more threads that execute concurrently on hardware and / or sequentially on hardware. Furthermore, in some examples, some or all of the circuitry of Fig. 6 be implemented by microprocessor circuitry executing instructions and / or FPGA circuitry performing operations to implement one or more virtual machines and / or containers.

[0056] The example block diagram of Fig. 6 includes the battery controller 102, the primary device 104 (e.g., primary device 104a or 104b), the secondary devices 106a-106h (corresponding to the secondary devices 106), and the battery cells 108a-108h (corresponding to the battery cells 108). The scope of this disclosure is not limited to a particular number of each type of device shown in Fig. 6. For example, while two instances of the primary device 104 are explicitly shown, the WBMS 100 may Fig. 6 may include any number of primary devices 104.

[0057] Each of the secondary devices 106 includes exemplary schedule request circuitry 202. As used herein, a secondary device 106a and its corresponding battery cell 108a are collectively referred to as a battery module 204a. Accordingly, the battery modules 204a-204h collectively form battery modules 204. The primary device 104 includes an exemplary antenna 206, an exemplary radio frequency (RF) transceiver 208, an exemplary processor 210, and exemplary wired interface circuitry 212. The battery controller 102 includes exemplary wired interface circuitry 214 and exemplary schedule determination circuitry 216. While Fig. While Figure 6 shows eight battery modules 204 and one battery controller 102, in other examples, the WBMS 100 includes any number of battery modules and battery controllers. For example, the WBMS 100 may include two or more battery controllers, with a first set of secondary devices assigned to communicate with a first battery controller and a second set of secondary devices assigned to communicate with a second battery controller. The first and second sets of secondary devices may or may not overlap.

[0058] The battery modules 204 communicate wirelessly with the primary device 104 using concurrent superframes. That is, a first superframe containing a first set of communications occurs concurrently with a second superframe containing a second set of communications. Within a given battery module 204a, the schedule request circuitry 202 determines whether a transmission regarding the corresponding battery cell 108a should occur in an upcoming set of concurrent superframes. The schedule request circuitry 202 may determine whether to perform a transmission based on factors including the status and performance of the corresponding battery cell 108a.

[0059] Schedule request circuitry 202 optionally requests to be included in a schedule for an upcoming superframe based on the result of the determination and in accordance with the teachings of this disclosure. Accordingly, battery modules 204 do not request to make a transmission in an upcoming superframe every time an opportunity to make a request is available. Schedule request circuitry 202 may provide additional information to battery controller 102 when requesting a transmission in an upcoming superframe. Schedule request circuitry 202 may also request a specific number of requested time slots, request a specific duration of uplink time, and / or request a specific data size to uplink (e.g., a specific number of blocks, bytes, or bits), etc.Alternatively, the request sent by the scheduling request circuitry 202 may only indicate that a corresponding battery module 204A requests more time to transmit, without details about the requested amount of time, the number of time slots, or the uplink size.

[0060] In the example of Fig. 6, each instance of the schedule request circuitry 202 is implemented within the secondary devices 106. In other examples, one or more instances of the schedule request circuitry 202 are implemented elsewhere within the respective battery modules 204. In some examples, the schedule request circuitry 202 is instantiated by programmable circuitry that executes schedule request instructions.

[0061] Within the primary device 104, the radio frequency (RF) transceiver 208 communicates wirelessly with the secondary devices 106 via the antenna 206. The RF transceiver 208 may use the license-exempt 2.4 gigahertz (GHz) ISM (Industrial, Scientific, and Medical) band from 2.4 GHz to 2.483 GHz, which is compliant with the Bluetooth Special Interest Group (SIG). Additionally or alternatively, the RF transceiver 208 may use 2 megabits per second (Mbps) Bluetooth Low Energy (BLE) over the physical layer (PHY). The Open Systems Interconnection (OSI) model includes the PHY as a layer used to communicate raw bits over a physical medium. In examples described here, the PHY is free space that the wireless battery management system 100 uses to wirelessly communicate between the primary device 104 and the secondary devices 106.In some examples, RF transceiver 208 is instantiated by programmable circuitry that executes RF instructions. The remaining transceivers in WBMS 100 may be configured to operate similarly to RF transceiver 208.

[0062] Within the primary device 104, the processor 210 not only interprets the content of data received by the primary device 104, but also determines the content of data to be transmitted by the primary device 104. In doing so, the processor 210 helps establish communication between the battery modules 204 and the battery controller 102. The exemplary processor 210 can be implemented using any type of programmable circuitry. Examples of programmable circuitry include, but are not limited to, programmable microprocessors, field-programmable gate arrays (FPGAs) capable of instantiating instructions, central processing units (CPUs), graphics processing units (GPUs), digital signal processors (DSPs), XPUs, or microcontrollers, and integrated circuits such as application-specific integrated circuits (ASICs).

[0063] Within the primary device 104, the wired interface circuitry 212 sends and receives communications with the battery controller 102 over the wired connection 110. The wired interface circuitry 212 may implement any suitable hardware components, including, but not limited to, terminals, pins, interconnects, etc., to implement wired communications. Similarly, the wired interface circuitry 214 within the battery controller 102 sends and receives communications with the primary device 104 over the wired connection 110. The wired interface circuitry 214 may implement any suitable hardware components to implement wired communications.In examples, the wired interfaces 212, 214 may be replaced by transceivers or other circuitry suitable for enabling wireless communications between the primary device 104 and the battery controller 102.

[0064] Schedule determination circuitry 216 determines different communication schedules for different superframes. Schedule determination circuitry 216 adjusts a schedule and / or creates new schedules for superframes based on the transmission request transmitted by the multiple instances of schedule request circuitry 202.

[0065] In the example of Fig. 6, the scheduler circuitry 216 is implemented within the battery controller 102. In other examples, the scheduler circuitry 216 is implemented within the primary device 104 or elsewhere within the WBMS 100. In some examples, the scheduler circuitry 216 is instantiated by programmable circuitry that executes scheduler instructions.

[0066] The battery modules 204 are heterogeneous in the sense that the design, manufacture, capabilities, and / or performance of a first battery module may differ from those of a second battery module. For example, Fig. 6, the battery cells 108a, 108b, 108d have a greater amount of charge than the battery cells 108c, 108e-108h. Furthermore, the amount of charge stored in the battery cells 108a, 108b, 108d is uneven. In an additional example, Fig. 6 shows the secondary devices 106a, 106e, 106g implemented by a first type of programmable circuitry, and the secondary devices 106b-106d, 106f, 106h implemented by another type of programmable circuitry. While the exemplary Fig. 6 illustrates a variance in battery capacity and type of programmable circuitry, in practice, the battery modules 204 may have other types of differences.

[0067] In some examples, the heterogeneity of the WBMS 100 causes some battery modules to seek communication with the battery controller 102 more frequently than other battery modules. Some battery modules may additionally or alternatively transmit different types of information within a superframe than other battery modules. For example, battery module 204a may attempt to report a storage capacity measurement when battery module 204b attempts to report an error code. The battery controller 102 enables such diverse forms of communication by receiving requests for transmissions sent by the battery modules 204 and determining a schedule for each superframe.

[0068] Fig. 7 is a block diagram of another exemplary WBMS 100. The architecture of the exemplary WBMS 100 in Fig. 7 includes a layer of intermediate devices between the primary and secondary devices, enabling a large scale in particularly large or complex systems. The exemplary WBMS 100 of Fig. 7 includes one or more primary devices 104 and a plurality of subclusters 704.1-704.N (collectively referred to herein as subcluster 704). Although Fig. 7 shows an exemplary WBMS 100 with a single primary device 104, the Fig. 7 shown partial cluster architecture in a WBMS 100 with multiple primary devices (e.g. the one shown in Fig. 2 shown WBMS 100). The Fig. 7 shown WBMS 100 can be configured to implement the functions described here with reference to Fig. 3-5 with the intermediate devices 706 communicating with multiple primary devices.

[0069] Subcluster 704.1 includes one or more intermediate devices 706.1 and a plurality of secondary devices 708.1-708.N (collectively referred to herein as secondary devices 708). Subcluster 704.2 includes one or more intermediate devices 706.2 and a plurality of secondary devices 710.1-710.N (collectively referred to herein as secondary devices 710). Subcluster 704.3 includes one or more intermediate devices 706.3 and a plurality of secondary devices 712.1-712.N (collectively referred to herein as secondary devices 712). Subcluster 704.N includes one or more intermediate devices 706.N and a plurality of secondary devices 714.1-714.N (collectively referred to herein as secondary devices 714).

[0070] In operation, each of the Fig. 7, such as the battery cell status data described above, and provides the data to a corresponding intermediate device 706. For example, each of the secondary devices 708 acquires data and transmits the data to the first and second intermediate devices 706.1. These transmissions occur according to the concurrent superframe scheme described herein, such as with reference to Fig.1-5. Thus, for example, the first and second intermediate devices 706.1 may broadcast downlink synchronization information during a first and a second slot of concurrent superframes, as described above. The secondary devices 708 may receive the broadcast information and use the broadcast information to synchronize communications with the first and second intermediate devices 706.1. Thereafter, during the concurrent superframes, each of the secondary devices 708 may transmit its respective data twice, once in one slot to the first intermediate device 706.1 and again in another slot to the second intermediate device 706.1, with both transmissions occurring at different frequencies. In this way, the first and second intermediate devices 706.1 are substantially likely to receive at least one instance of the data from each of the secondary devices 708.Each of the subclusters 704 operates in a similar manner.

[0071] After the intermediate devices 706 of each subcluster 704 receive the data from respective secondary devices, the intermediate devices 706 transmit the data to the primary devices 104 using the concurrent superframe scheme described herein. For example, in a first and a second concurrent superframe slot, the first and second primary devices 104 may broadcast downlink synchronization information to the intermediate devices 706, which the intermediate devices 706 may use to synchronize communications with the first and second primary devices 104.Thereafter, during the concurrent superframes, each of the intermediate devices 706 may transmit respective data twice, once in one slot to the first primary device 104 and again in another slot to the second primary device 104, with both transmissions possibly occurring at different frequencies. In this way, the first and second primary devices 104 are substantially likely to receive at least one instance of the data from each of the intermediate devices 706. The concurrent superframe scheme described herein can be scaled to any number of wireless devices in a WBMS or any system other than a WBMS where robust wireless communications are useful.For example, three or more primary devices 104 may be used, in which case a given intermediate device 706 may transmit the same data to the three or more primary devices 104 during different slots and at different frequencies. In some examples where three or more primary devices 104 may be used, a first intermediate device 706 may transmit data to the first and second primary devices 104 in different slots and at different frequencies, while a second intermediate device 706 may transmit different data to the second and third primary devices 104 in different slots and at different frequencies. Furthermore, the concepts described herein may be extended to any number of simultaneous superframes.

[0072] In this description, the term "couple" can cover connections, communications, or signal paths that enable a functional relationship consistent with this description. For example, if device A generates a signal to control device B to perform an action: (a) in a first example, device A is coupled to device B by a direct connection; or (b) in a second example, device A is coupled to device B via an intervening component C, where the intervening component C does not change the functional relationship between device A and device B, such that device B is controlled by device A via the control signal generated by device A.

[0073] A device "configured" to perform a task or function may be configured (e.g., programmed and / or hard-wired) at the time of manufacture by a manufacturer to perform the function, and / or may be configurable (or reconfigurable) by a user after manufacture to perform the function and / or other additional or alternative functions. Configuring may be accomplished through firmware and / or software programming of the device, through an assembly and / or layout of hardware components and interconnections of the device, or a combination thereof.

[0074] Unless otherwise specified, "about," "approximately," or "substantially" in this specification before a parameter means a range within + / - 10% of that parameter. Modifications to the described examples, as well as other examples, are possible within the scope of the claims. QUOTES CONTAINED IN THE DESCRIPTION

[0000] This list of documents submitted by the applicant was generated automatically and is included solely for the convenience of the reader. This list is not part of the German patent or utility model application. The DPMA assumes no liability for any errors or omissions. Cited patent literature

[0000] US 17 / 823,138

[0024] US 18 / 227,821

[0042] US 18 / 345,636

[0042] Cited non-patent literature

[0000] CC2662R-Q1 SimpleLink™ Wireless BMS MCU, revised July 2023, available at https: / / www.ti.com / product / CC2662R-Q1

[0021] BQ79616-Q1, BQ79614-Q1, BQ79612-Q1, Functional Safety-Compliant Automotive 16S / 14S / 12S Battery Monitor, Balancer and Integrated Hardware Protector, revised September 2022, available at https: / / www.ti.com / product / BQ79616-Q1

[0021]

Claims

[1] Device comprising: a transceiver configured to wirelessly transmit and wirelessly receive data; and a processor coupled to the transceiver, the processor configured to: Receiving, by the transceiver and in a first time slot, first data transmitted by a first primary device; Receiving, by the transceiver and in a second time slot following the first time slot, second data transmitted by a second primary device; Providing, to the transceiver and in a third time slot following the second time slot, third data to be transmitted on a first frequency to the first primary device, the third data including a battery cell status; and Delivering, to the transceiver and in a fourth time slot following the second time slot, the third data to be transmitted to the second primary device, wherein the transceiver is configured to transmit the third data to the second primary device at a second frequency different from the first frequency. [2] The apparatus of claim 1, wherein the third and fourth time slots are consecutive time slots. [3] The apparatus of claim 1, wherein the third and fourth time slots are non-consecutive time slots. [4] The apparatus of claim 1, wherein the first data or the second data specifies a timing of the third time slot or the fourth time slot. [5] The apparatus of claim 1, wherein the apparatus is configured to store a timing of the third time slot or the fourth time slot before receiving the first data and before receiving the second data. [6] The apparatus of claim 1, wherein the first and second frequencies are separated by at least 5 MHz. [7] The apparatus of claim 1, wherein the first and second time slots are consecutive time slots. [8] The apparatus of claim 1, wherein the processor is configured to receive the first data in the first time slot at a third frequency equal to the first frequency. [9] The apparatus of claim 1, wherein the processor is configured to receive the second data in the second time slot at a third frequency equal to the second frequency. [10] The apparatus of claim 1, wherein the processor is configured to receive the first data in the first time slot at a third frequency equal to the second frequency. [11] The apparatus of claim 1, wherein the processor is configured to receive the second data in the second time slot at a third frequency equal to the first frequency. [12] Wireless Battery Management System (WBMS), which includes: a first primary device configured to wirelessly broadcast first data during a first time slot; and a secondary device designed to: wirelessly receiving the first data during the first time slot; wirelessly receiving second data broadcast by a second primary device during a second time slot following the first time slot; wirelessly transmitting third data to the first primary device during a third time slot after the second time slot, the third data comprising a battery cell status; and wirelessly transmitting the third data to the second primary device during a fourth time slot after the second time slot. [13] The system of claim 12, wherein the first and second time slots are consecutive time slots. [14] The system of claim 12, wherein the first and second data together include timing information for the third and fourth time slots. [15] The system of claim 12, wherein the secondary device is configured to store timing information for the third and fourth time slots prior to receiving the first data and prior to receiving the second data. [16] The system of claim 12, wherein the secondary device is configured to transmit the third data in the third time slot on a first frequency and the third data in the fourth time slot on a second frequency different from the first frequency using a frequency hopping scheme. [17] The system of claim 12, wherein the secondary device is a first secondary device, the system further comprising a second secondary device configured to transmit fourth data to the first primary device during the fourth time slot. [18] The system of claim 17, wherein the second secondary device is configured to transmit the fourth data to the second primary device during the third time slot. [19] Non-transitory computer-readable medium that stores instructions that, when executed by a processor, cause the processor to: during a first time slot, receiving first data wirelessly transmitted by a first primary device to the processor and to a secondary device; during a second time slot, effecting a wireless transmission of second data to the first primary device simultaneously with a transmission of third data from the secondary device to a second primary device, the second and third data comprising battery cell status; and during a third time slot, causing a wireless transmission of the second data to the second primary device concurrently with the transmission of the third data from the secondary device to the first primary device. [20] The medium of claim 19, wherein the instructions cause the processor to transmit the second data to the first primary device and to the second primary device at different frequencies.

Citation Information

Patent Citations

  • US-PATENTANMELDUNGNR.18/227,821

  • US-PATENTANMELDUNGNR.18/345,636

  • US-ANMELDUNGNR.17/823,138