Wireless battery devices based on radio time synchronization
By employing independent processor logic for the radio frequency core and the system core in the wireless battery management system, and utilizing the concurrent superframe protocol to achieve high-precision time synchronization between the master device and the auxiliary device, the accuracy of EIS measurements and system-level latency issues in WBMS are resolved, the stringent thermal runaway notification standards are met, and the safety and reliability of the system are improved.
Patent Information
- Application Number
- CN202610607742.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2025-11-25
- Filing Date
- 2026-05-06
- Publication Date
- 2026-11-17
AI Technical Summary
Existing wireless battery management systems (WBMS) struggle to achieve high-precision time synchronization when performing electrochemical impedance spectroscopy (EIS) measurements, failing to meet stringent thermal runaway notification standards and exhibiting inaccuracies due to system-level latency.
The system employs a processor with independent RF cores and system cores to execute logic, and achieves high-precision time synchronization between the master and auxiliary devices through a concurrent superframe protocol, ensuring the accuracy and robustness of EIS measurements.
It achieves high-precision EIS measurement in hybrid battery systems, meets stringent thermal runaway notification standards, and improves the safety and reliability of WBMS.
Smart Images

Figure CN123124077A_ABST
Abstract
Description
[0001] Cross-references to related applications
[0002] This patent application claims the benefit and priority of U.S. Provisional Patent Application No. 63 / 806,481, filed May 15, 2025, which is hereby incorporated herein by reference in its entirety. Technical Field
[0003] This specification generally relates to batteries, and more specifically, to radio-based time synchronization of wireless battery devices. Background Technology
[0004] Hybrid electric vehicles (HEVs) and electric vehicles (EVs) are powered by battery systems that include batteries such as lithium-ion batteries. The battery system may also include a battery management system that monitors the battery's health and reports it to the main electronic control unit (ECU) of the HEV or EV. A wide range of conditions can affect battery health. Summary of the Invention
[0005] For radio-based time synchronization in a wireless battery device, a first example device includes: a wireless receiver configurable to receive packets, programmable circuitry, and communication circuitry coupled to the wireless receiver and the programmable circuitry, wherein the communication circuitry is configurable to: identify a portion of the packet; and, in response to the identification of said portion of the packet, cause the device to send a first wired signal to a battery monitor circuitry.
[0006] The second example device includes a wireless receiver configurable to receive packets, programmable circuitry, and communication circuitry coupled to the wireless receiver and programmable circuitry, wherein the communication circuitry is configurable to: set a timer in response to a packet; and cause the device to send a first wired signal to a battery monitor circuitry when the timer expires.
[0007] The third example device includes a wireless transmitter configurable to transmit downlink packets, programmable circuitry, and communication circuitry coupled to the wireless transmitter and programmable circuitry, wherein the communication circuitry is configured to: set a timer in response to a message from the programmable circuitry after the transmission of the downlink packets; and cause the device to send a wired signal to a battery monitor circuitry when the timer expires. Attached Figure Description
[0008] Figure 1 This is an illustrative example of a wireless battery management system (WBMS).
[0009] Figure 2 yes Figure 1 A block diagram of the first example implementation of WBMS.
[0010] Figure 3 yes Figure 1 A block diagram of the second example implementation of WBMS.
[0011] Figure 4 yes Figure 1 A block diagram of the third example implementation of WBMS.
[0012] Figure 5 yes Figure 1 A block diagram of the fourth example implementation of WBMS.
[0013] Figure 6 yes Figure 1 A block diagram of the fifth example implementation of WBMS.
[0014] Figure 7 It is available Figure 6 An illustrative example of the superframe interval used in the sample implementation of WBMS.
[0015] Figure 8 yes Figure 6 A block diagram of an example implementation of the auxiliary device.
[0016] Figure 9 It is possible Figure 6 An illustrative example of timing signals exchanged between devices in a WBMS.
[0017] Figure 10 It is possible Figure 6 An illustrative example of a just-in-time protocol implemented within a WBMS.
[0018] Figure 11 It is possible Figure 6 An illustrative example of the scheduling protocol implemented within WBMS.
[0019] Figure 12 It is possible Figure 10 Just-in-time agreement or Figure 11 An illustrative example of a standby timer used within the scheduling protocol.
[0020] Figure 13 yes Figure 10 An illustrative example of the implementation of a just-in-time agreement.
[0021] Figure 14 yes Figure 11 The second illustrative example of the execution of the scheduling protocol.
[0022] Figure 15 It means that it can be used. Figure 6 The flowchart illustrates the implementation, instantiation, and / or execution of example machine-readable instructions or example operations of the example programmable circuit system implementation of the main device.
[0023] Figure 16 It means that it can be generated by Figure 6 A flowchart of example machine-readable instructions or example operations implemented, instantiated and / or executed by the auxiliary device to implement the just-in-time protocol.
[0024] Figure 17 It means that it can be generated by Figure 6 A flowchart of an example machine-readable instruction or example operation implemented, instantiated and / or executed by an auxiliary device to implement a scheduling protocol.
[0025] Figure 18 It means that it can be used. Figure 6 The flowchart illustrates the implementation, instantiation, and / or execution of example machine-readable instructions or example operations of an example programmable circuit system implementation of a battery quality (BQ) device.
[0026] Figure 19 This is a block diagram of an example processing platform, which includes components configured to implement, instantiate, or execute example machine-readable instructions or commands. Figure 15-18 Example operations to implement Figure 6 The programmable circuit system of WBMS 100.
[0027] The accompanying drawings are not necessarily drawn to scale. Generally, the same reference numerals in the drawings and this specification refer to the same or similar features and / or parts (functionally and / or structurally). Although the drawings show areas with clearly defined lines and boundaries, some or all of these lines and boundaries may be idealized. In reality, boundaries or lines may be invisible, mixed, or irregular. Detailed Implementation
[0028] Many HEVs and EVs incorporate battery systems, with each battery containing multiple (thousands) of storage cells. Using multiple distributed batteries and / or a large number of distributed cells allows for higher ampere-hour capacities compared to single-cell or smaller cell alternatives. Higher ampere-hour capacities improve system performance (e.g., increased range, torque, or vehicle speed) compared to single-cell alternatives. In some implementations of multiple distributed batteries, one or more individual batteries are connected to a controller that coordinates system-level operations. In some examples, individual battery cells or circuitry coupled to battery cells may be referred to as battery modules, auxiliary batteries, auxiliary nodes, auxiliary network nodes, auxiliary circuitry, monitor circuitry, etc. Similarly, the controller may be referred to as a battery controller, master node, master network node, master controller, etc.
[0029] In some examples, HV and EV combine multiple battery cells in series to generate a relatively high voltage and low current signal that supports efficient motor operation. However, battery cells coupled in series typically require: a) each battery cell to implement a master controller, and b) the master controllers to operate synchronously with each other. Conversely, battery cells combined in parallel generate a relatively low voltage and high current signal and can typically be controlled by a single master controller.
[0030] Some HVs and EVs communicate between the battery module and controller via a series of wired connections. HVs and EVs can additionally or alternatively use wireless connections for this communication. In some examples, implementations using wireless communication may be referred to as Wireless Battery Management Systems (WBMS). In some examples, WBMS is used instead of wired solutions because it offers advantages such as reduced weight, lower complexity, and lower cost compared to wired connections through the vehicle. For example, wired battery systems typically contain more components (including, but not limited to, choke capacitors for high / low voltage isolation / protection) and are more complex to maintain than WBMS.
[0031] Depending on the use case, WBMS can communicate using different protocols. For example, in some automotive applications, industry professionals might use WBMS superframes to establish communication between multiple battery modules and the controller. As used herein, the term "superframe" refers to a scheduled data exchange window that aggregates several bidirectional transmission time slots. As used herein, a superframe can refer to the Transport System 1 (T1) framework standard or any other bidirectional scheduled transmission protocol. A superframe combines at least... Figure 7 Further description is required.
[0032] As the performance requirements and complexity of HV and EV designs increase, the danger of thermal runaway is becoming increasingly prevalent. Thermal runaway generally refers to an uncontrolled rise in temperature that can lead to fire and / or explosion. Thermal runaway can be caused by a variety of factors that cause battery cells to operate beyond their thermal limits. These factors include, but are not limited to, dendrite growth in the battery, individual cell damage, and manufacturing anomalies. New WBMS (Wireless Battery Management Systems) need to meet stringent safety requirements to prevent thermal runaway. If the WBMS determines that thermal runaway is no longer preventable, some safety standards require the WBMS to notify the driver a threshold time (e.g., five minutes) before thermal runaway occurs.
[0033] Electrochemical impedance spectroscopy (EIS) is a specific technique for measuring the health status of battery cells. To perform EIS in a manner that supports stringent thermal runaway notification standards, devices within a battery cell management system (WBMS) must be synchronized with each other at extremely high precision not supported by the WBMS. In some examples, this use of EIS requires clocks within the WBMS to be approximately twenty times more accurate than known WBMSs. More generally, the synchronization levels in known WBMSs tolerate inaccuracies due to system-level latency in scheduling EIS measurements and subtasks, but the synchronization levels required for using EIS for stringent thermal runaway notification standards cannot support such system-level latency.
[0034] The example methods, devices, and systems described herein perform EIS measurements with high accuracy, independent of system-level latency and supporting stringent thermal runaway notification standards. An example battery management device within a WBMS includes a radio frequency (RF) core with a first processor that executes logic independently of a second processor within the system core. In the example described herein, the system core schedules EIS measurements and analyzes subsequent values to determine the risk of thermal runaway, while the RF core synchronizes the WBMS devices to each other and triggers EIS measurements. Therefore, the WBMS synchronization described herein is more accurate and robust than known systems.
[0035] Figure 1 This is a schematic diagram of an automotive system 98 comprising multiple master and auxiliary devices configured to communicate using concurrent superframes. System 98 can be a vehicle, such as a car, boat, aircraft, spacecraft, or military vehicle. System 98 can also be a non-vehicle system comprising monitored battery cells. Furthermore, system 98 can be any type of system in which information is repeatedly transmitted between wireless devices. Additional examples of system 98 may include one or more of the following in any combination: smartphones; laptop computers; desktop computers; tablets; notebooks; electrical equipment; and entertainment devices. The remainder of this specification assumes that system 98 is an automotive vehicle, but the scope of this specification is not limited to automotive vehicles or any other particular type of system. Furthermore, although this document describes a concurrent superframe scheme in the context of a wireless battery management system, the teachings of this specification can be extended to other types of systems, including smart homes, home automation, industrial automation (e.g., precision-calibrated machines), robotics, security monitoring, the Internet of Things, and wireless sensor networks.
[0036] Example system 98 includes a wireless battery management system (WBMS) 100. The WBMS 100 can be located in any part of the vehicle, but in some examples, it is located in, above, or near the bottom of the vehicle chassis, such as under one or more seats. The WBMS 100 may include: one or more battery controller devices 102 that supervise and control the WBMS 100 (e.g., by load balancing between devices and determining whether to measure current, voltage, temperature, or other register settings of battery cells); one or more master devices 104 coupled to the battery controller devices 102 via one or more wired or wireless connections 110; one or more auxiliary devices 106; and one or more battery cells 108 coupled to the one or more auxiliary devices 106 via one or more wired or wireless connections 112. The master devices 104 communicate wirelessly with the auxiliary devices 106 using a concurrent superframe protocol, as described herein.
[0037] Figure 2 yes Figure 1 A block diagram of WBMS 100 is provided. WBMS 100 may include one or more battery controller devices 102, which are coupled to master devices 104-1 and 104-2 via one or more wired or wireless connections 110-1 and 110-2, respectively. Master device 104-1 includes processor circuitry 114-1, transceiver 115-1 coupled to processor circuitry 114-1, and memory 116-1 (e.g., random access memory (RAM) and read-only memory (ROM)) coupled to processor circuitry 114-1. Memory 116-1 stores executable code 118-1. After executing executable code 118-1, processor circuitry 114-1 performs some or all of the actions attributed herein to master device 104-1 or processor circuitry 114-1. Antenna 120-1 is coupled to transceiver 115-1 and configured to transmit signals to and receive signals from other devices in WBMS 100. The master device 104-2 includes a processor circuitry 114-2 coupled to a transceiver 115-2 and a memory 116-2 (e.g., RAM or ROM). The memory 116-2 stores executable code 118-2. Upon execution of the executable code 118-2, the processor circuitry 114-2 performs some or all of the actions attributed herein to the master device 104-2 or the processor circuitry 114-2. An antenna 120-2 is coupled to the transceiver 115-2 and configured to transmit and receive signals from other devices in the WBMS 100. In some examples, the master device (e.g., 104-1) is referred to as the master wireless device.
[0038] Any processor described herein can be implemented using any type of programmable circuit system. Examples of programmable circuit systems include, but are not limited to, programmable microprocessors, field-programmable gate arrays (FPGAs) that can instantiate 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).
[0039] Furthermore, any transceiver described herein may use the unlicensed 2.4 GHz Industrial, Scientific, and Medical (ISM) band from 2.4 GHz to 2.483 GHz, which complies with Bluetooth Special Interest Group (SIG) requirements. Alternatively or concurrently, the transceiver may use Bluetooth Low Energy (BLE) at 2 Mbps on the physical layer (PHY). The Open Systems Interconnection (OSI) model includes the PHY as a layer for transmitting raw bits over a physical medium. In the examples described herein, the PHY is free space, which the WBMS 100 uses to enable wireless communication between various devices within the WBMS 100. In some examples, the transceivers described herein are instantiated by a programmable circuit system that executes RF instructions.
[0040] The auxiliary device 106-1 may include a processor 122-1 coupled to a memory 124-1 storing executable code 126-1. After executing the executable code 126-1, the processor 122-1 may perform some or all of the actions attributed herein to the auxiliary device 106-1 or the processor 122-1. One or more transceivers 128-1 are coupled to the processor 122-1, and one or more antennas 130-1 are coupled to the one or more transceivers 128-1. The auxiliary device 106-1 is coupled to one or more battery cells 108-1 via one or more connections 112-1.
[0041] The auxiliary device 106-2 may include a processor 122-2 coupled to a memory 124-2 storing executable code 126-2. After executing the executable code 126-2, the processor 122-2 may perform some or all of the actions attributed herein to the auxiliary device 106-2 or the processor 122-2. One or more transceivers 128-2 are coupled to the processor 122-2, and one or more antennas 130-2 are coupled to the one or more transceivers 128-2. The auxiliary device 106-2 is coupled to one or more battery cells 108-2 via one or more connections 112-2.
[0042] The auxiliary device 106-3 may include a processor 122-3 coupled to a memory 124-3 storing executable code 126-3. After executing the executable code 126-3, the processor 122-3 may perform some or all of the actions attributed herein to the auxiliary device 106-3 or the processor 122-3. One or more transceivers 128-3 are coupled to the processor 122-3, and one or more antennas 130-3 are coupled to the one or more transceivers 128-3. The auxiliary device 106-3 is coupled to one or more battery cells 108-3 via one or more connections 112-3.
[0043] Figure 2 The main devices 104-1 and 104-2 may be collectively referred to herein as main device 104. Similarly, auxiliary devices 106-1, 106-2, and 106-3 may be collectively referred to herein as auxiliary device 106, and so on. Similar conventions may be adopted for any or all features depicted in the figures. In some examples, one or more main devices 104 execute main instructions to perform, for example, by... Figure 14-18 The flowchart represents the operation of a programmable circuit system to be instantiated. In some examples, one or more auxiliary devices 106 execute auxiliary instructions to perform, for example, actions by... Figure 14-18 The flowchart represents the operation of a programmable circuit system to be instantiated.
[0044] The primary and auxiliary devices described herein (e.g., primary device 104, auxiliary device 106) can be implemented as the CC2662 or BQ79616 manufactured by Texas Instruments®, Dallas, Texas. For more example details on the CC2662 and BQ79616, please refer to the document entitled "CC2662R-Q1 SimpleLink". TM Wireless BMS MCU (CC2662R-Q1 SimpleLink) TMDatasheet for "Wireless BMS MCU" (July 2023 revision, website: https: / / www.ti.com / product / CC2662R-Q1) and the title "BQ79616-Q1, BQ79614-Q1, BQ79612-Q1 Functional Safety-Compliant Automotive 16S / 14S / 12S Battery Monitor, Balancer and Integrated Hardware Protector" The datasheet for “Protector” (revised September 2022, available at https: / / www.ti.com / product / BQ79616-Q1) is incorporated herein by reference in its entirety. As an example only, the auxiliary device 106 can be implemented as CC2662 for communication coupling to BQ79616 for battery monitoring. Further examples of WBMS architecture and communication can be found in U.S. Application No. 2025 / 0008491, filed June 30, 2023, entitled “Hierarchical Wireless Battery Management System”; U.S. Application No. 18 / 647,353, filed April 26, 2024, entitled “Scheduling for Multiple Primary Nodes”; and U.S. Application No. 18 / 647,353, filed May 20, 2025, entitled “Time Synchronization In Wireless Battery Management”. U.S. Application No. 19 / 213,653 entitled “Time Synchronization In Wireless Battery Management Systems”, filed May 20, 2025, is published hereto and is jointly assigned U.S. Application No. 19 / 213,668 entitled “Time Synchronization In Wireless Battery Management Systems”, filed May 20, 2025, each of which is hereby incorporated herein by reference in its entirety.
[0045] The auxiliary device 106 is configured to monitor the state of the corresponding battery cell 108 (e.g., the voltage provided by the battery cell 108, the temperature of the battery cell 108). For example, a given auxiliary device 106-1 may include, be coupled to, or communicate with one or more sensors configured to measure, measure, or communicate with various parameters associated with the corresponding battery cell 108-1. The sensors may relay the sensed data to the processor 122 of the auxiliary device 106 via the Universal Asynchronous Receiver / Transmitter (UART) protocol or any other suitable protocol. Furthermore, a given auxiliary device 106-1 may be configured to communicate with one or both of the master devices 104. For example, the auxiliary device 106-1 may communicate with the master device 104-1 during one time slot of a superframe, and the auxiliary device 106-1 may communicate with the master device 104-2 during another time slot of the superframe. Alternatively, the auxiliary device 106-1 may communicate with both master devices 104 simultaneously using different transceivers 128-1. Auxiliary devices 106-2 and 106-3 can communicate with two main devices 104, similar to auxiliary device 106-1. In some examples, a given auxiliary device 106-1 is configured to communicate with one or more of the remaining auxiliary devices 106-2 and 106-3. The main devices 104 can also communicate with auxiliary devices 106 and with each other. For example, main device 104-1 can transmit data to one or more of main devices 104-2, auxiliary devices 106-1, auxiliary devices 106-2, or auxiliary devices 106-3. Main device 104-2 can operate in a manner similar to main device 104-1. Communication transmitted by the main devices 104 can be received from one or more battery controller devices 102. Similarly, communication received by the main devices 104 can be provided to one or more battery controller devices 102.
[0046] Figure 2 The WBMS 100 depicted herein is illustrative. In some examples, the WBMS 100 may include any number of master devices, auxiliary devices, battery controllers, battery cells, other components, and wired or wireless connections between one or more of the foregoing. Any and all such variations are contemplated and are included within the scope of this specification.
[0047] Figure 1 and 2 Additional examples of the components shown can be found in U.S. Application No. 2024 / 0069110, filed August 30, 2022, entitled “Multiple Primary Nodes for Wireless Battery Management System Robustness,” which is hereby incorporated herein by reference in its entirety.
[0048] Figure 3 yes Figure 1 A block diagram of the implementation scheme for WBMS 100. Figure 3 The WBMS 100 is configured based on Figure 7 The concurrent superframe scheme is further described in the text and operates accordingly. Figure 3 The WBMS 100 can be instantiated (e.g., by creating an instance of it, making it exist for any length of time, materializing it, implementing it, etc.) through a programmable circuit system, such as a CPU that executes the first instruction. Alternatively or concurrently, Figure 3 The WBMS 100 can be instantiated by constructing or configuring an (i) ASIC or (ii) FPGA that performs an operation corresponding to the first instruction in response to the execution of the second instruction. Therefore, Figure 3 Some or all of the circuit systems can be instantiated at the same or different times. For example, Figure 3 Some or all of the circuitry can be instantiated in one or more threads that execute concurrently or sequentially on the hardware. Furthermore, in some examples, Figure 3 Some or all of the circuitry can be implemented by a microprocessor circuitry that executes instructions or by an FPGA circuitry that performs operations to implement one or more virtual machines or containers.
[0049] Figure 3 The example block diagram includes a battery controller device 102-1, a main device 104-1, auxiliary devices 106-1 to 106-8, and battery cells 108-1 to 108-8. The main device 104-1 includes an antenna 120-1 and a radio frequency (RF) transceiver 115-1. Figure 1 The processor circuit system 114-1 and the example wired interface circuit system 312 are included. The battery controller device 102-1 includes the example wired interface circuit system 314 and the example scheduler circuit system 316.
[0050] exist Figure 3 In the example, the corresponding auxiliary device 106 includes a dispatch requester circuit system 302. As used herein, the auxiliary device 106-1 and its corresponding battery unit 108-1 can be collectively referred to as battery module 304-1. Therefore, battery modules 304-1 to 304-8 together form battery module 304.
[0051] The scope of this specification is not limited to any particular number of... Figure 3 Each type of device is shown in the diagram. Therefore, Figure 3The WBMS 100 may contain any number of battery controller devices 102, main devices 104, or battery modules 304. In some examples, the WBMS 100 includes two or more battery controller devices 102, wherein a first set of auxiliary devices 106 is assigned to communicate with a first battery controller device 102-1, and a second set of auxiliary devices 106 is assigned to communicate with a second battery controller device 102-2. The first and second sets of auxiliary devices may or may not overlap.
[0052] Within the main device 104-1, a wired interface circuitry 312 transmits and receives communication with the battery controller device 102-1 via a wired connection 110. The wired interface circuitry 312 can implement any suitable hardware components, including but not limited to terminals, pins, interconnects, etc., to implement wired communication. Similarly, within the battery controller device 102-1, a wired interface circuitry 314 transmits and receives communication with the main device 104 via a wired connection 110. The wired interface circuitry 314 can implement any suitable hardware components to implement wired communication. In this example, the wired interface circuitries 312 and 314 can be replaced with a transceiver or other circuitry suitable for facilitating wireless communication between the main device 104 and the battery controller device 102-1.
[0053] The scheduling determiner circuit system 316 determines different communication schedules for different superframes. The scheduling determiner circuit system 316 adjusts the superframe schedule or creates new schedules based on the transmission requests transmitted by multiple instances of the scheduling requester circuit system 302. Figure 3 In one example, the scheduler determiner circuitry 316 is implemented within the battery controller device 102-1. In other examples, the scheduler determiner circuitry 316 is implemented within the main device 104 or elsewhere within the WBMS 100. In some examples, the scheduler determiner circuitry 316 is instantiated by a programmable circuitry that executes scheduler determiner instructions.
[0054] Battery module 304 communicates wirelessly with host device 104-1 using concurrent superframes. Therefore, a first superframe containing a first set of communications and a second superframe containing a second set of communications occur simultaneously. Within a given battery module 304-1, scheduling requester circuitry 302 determines whether to perform a transmission related to the corresponding battery cell 108-1 in an upcoming set of concurrent superframes. Scheduling requester circuitry 302 can determine when to schedule a given transmission based on factors including the state and performance of the corresponding battery cell 108-1.
[0055] The scheduling requester circuitry 302 optionally requests inclusion in the scheduling of an upcoming superframe based on the determined result. Therefore, the battery module 304 does not request transmission in an upcoming superframe every time it has the opportunity to request it. When requesting transmission in an upcoming superframe, the scheduling requester circuitry 302 may provide additional information to the battery controller device 102-1. The scheduling requester circuitry 302 may also request a specific number of requested time slots, request uplink time for a specific duration, or request a specific data size for uplink (e.g., a specific number of blocks, bytes, or bits). Alternatively, the request sent by the scheduling requester circuitry 302 may only indicate that the corresponding battery module 304-1 is requesting more time for transmission, without specifying the requested duration, number of time slots, or uplink size.
[0056] exist Figure 3 In one example, each instance of the dispatch requester circuitry 302 is implemented within the auxiliary device 106. In other examples, one or more instances of the dispatch requester circuitry 302 are implemented elsewhere within the corresponding battery module 304. In some examples, the dispatch requester circuitry 302 is instantiated by a programmable circuitry that executes dispatch requester instructions.
[0057] Battery module 304 exhibits heterogeneity because the design, manufacture, capability, or performance of the first battery module may differ from that of the second battery module. For example, in Figure 3 In this example, battery cells 108-1, 108-2, and 108-4 store more charge than battery cells 108-3, 108-5, and 108-8. Furthermore, the amount of charge stored in battery cells 108-1, 108-2, and 108-4 is non-uniform. In another example, Figure 3 Auxiliary devices 106-1, 106-5, and 106-7 implemented by a first type of programmable circuit system are shown, as well as auxiliary devices 106-2 - 106-4, 106-6, and 106-8 implemented by different types of programmable circuit systems. Although Figure 3 The example illustrates the differences in battery capacity and type for a programmable circuit system, but in reality, battery module 304 can contain other types of differences.
[0058] In some examples, the heterogeneity of WBMS 100 causes some battery modules to attempt to communicate with battery controller device 102-1 at a higher frequency 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 304-1 may attempt to report storage capacity measurements, while battery module 304-2 may attempt to report error codes. Battery controller device 102-1 implements these different forms of communication by receiving requests for transmissions sent by battery module 304 and determining the schedule for each superframe. Such technology is described in U.S. Application No. 2025 / 0039859, jointly assigned and filed July 28, 2023, entitled “Methods and Apparatus to Determine Communication Schedules for Wireless Battery Systems,” which is hereby incorporated herein by reference in its entirety.
[0059] Figure 4 yes Figure 1 A block diagram of another implementation of WBMS 100. Figure 4 In the example, the architecture of WBMS 100 includes an intermediate layer between the main unit and the auxiliary unit, which helps to scale up in particularly large or complex systems. Figure 4 Examples include one or more master devices 104 and multiple sub-clusters 404-1 to 404-n (collectively referred to as sub-clusters 404 in this document).
[0060] Sub-cluster 404-1 includes one or more intermediate devices 406-1 and multiple auxiliary devices 408-1 to 408-b (collectively referred to herein as auxiliary devices 408). Sub-cluster 404-2 includes one or more intermediate devices 406-2 and multiple auxiliary devices 410-1 to 410-c (collectively referred to herein as auxiliary devices 410). Sub-cluster 404-3 includes one or more intermediate devices 406-3 and multiple auxiliary devices 412-1 to 412-d (collectively referred to herein as auxiliary devices 412). Sub-cluster 404-a includes one or more intermediate devices 406-n and multiple auxiliary devices 414-1 to 414-e (collectively referred to herein as auxiliary devices 414). Although Figure 4 The letters a, b, c, d, and e are used to indicate multiple reference numerals, but the number of a given set of multiple reference numerals does not need to be equal to the number of any other set of multiple reference numerals. For example, in Figure 4 In this context, the number of auxiliary devices 408 may be the same as or different from the number of auxiliary devices 410, 412 or 414, the number of sub-clusters 404 may be the same as or different from the number of auxiliary devices 408, 410, 412 or 414, and so on.
[0061] During operation, Figure 4 The auxiliary devices shown collect data, such as the battery cell status data described above, and provide the data to the corresponding intermediate device 406. For example, each auxiliary device 408 collects data and transmits it to the first and second intermediate devices 406-1. These transmissions are performed according to the concurrent superframe scheme described herein, for example, referring to... Figure 7 Described. Therefore, for example, the first and second intermediate devices 406-1 can broadcast downlink synchronization information during the first and second time slots of a concurrent superframe. The auxiliary device 408 can receive the broadcast information and use it to synchronize communication with the first and second intermediate devices 406-1. Subsequently, during the concurrent superframe, each auxiliary device 408 can transmit its corresponding data twice, once to the first intermediate device 406-1 in one time slot and again to the second intermediate device 406-1 in another time slot, where these two transmissions are performed at different frequencies. In this way, the first and second intermediate devices 406-1 are highly likely to receive at least one instance of data from each auxiliary device 408. Each sub-cluster 404 operates in a similar manner.
[0062] After each intermediate device 406 in each sub-cluster 404 has received data from its corresponding auxiliary device, the intermediate device 406 transmits the data to the master device 104 using the concurrent superframe scheme described herein. For example, in the first and second time slots of the concurrent superframe, the first and second master devices 104 may broadcast downlink synchronization information to the intermediate device 406, which the intermediate device 406 can use to synchronize communication with the first and second master devices 104. Subsequently, during the concurrent superframe, each intermediate device 406 may transmit the corresponding data twice, once to the first master device 104 in one time slot and again to the second master device 104 in another time slot, where these two transmissions may occur on different frequencies. In this way, the first and second master devices 104 are highly likely to receive at least one instance of data from each intermediate device 406. The concurrent superframe scheme described herein can be scaled to accommodate any number of wireless devices in a WBMS, or any other system for which robust wireless communication outside of WBMS is useful. For example, three or more master devices 104 can be used, in which case a given intermediate device 406 can transmit the same data to the three or more master devices 104 at different frequencies during different time slots. In some examples where three or more master devices 104 can be used, the first intermediate device 406 can transmit data to the first and second master devices 104 in different time slots and at different frequencies, while the second intermediate device 406 can transmit different data to the second and third master devices 104 in different time slots and at different frequencies. Furthermore, the concepts described herein can be extended to any number of concurrent superframes.
[0063] Figure 5 yes Figure 1 A block diagram of the implementation scheme for WBMS 100. Figure 5 The example includes a battery controller device 102-1, two main devices 104, eleven auxiliary devices 106, and eleven battery cells 108, as described above. Figure 1-4 As described in one or more of them. Figure 5 It also includes example BQ circuits 502-1 to 502-11 (collectively referred to as BQ circuit 502) and current sensing device 504. The scope of this specification is not limited to any particular number of examples. Figure 5 The examples show each type of device.
[0064] A given BQ circuit 502-1 is configured to monitor the quality, state, and health of its corresponding battery cell 108-1. For example, electrochemical impedance spectroscopy (EIS) is a specific technique for measuring the health of battery cells. Within a set of operations performed across WBMS 100 to implement EIS, the given BQ circuit 502-1 measures the voltage on the corresponding battery cell 108-1. As part of the EIS technique, WBMS 100 is designed to perform battery measurements synchronously. For example, BQ circuit 502-1 is preferably used to measure the voltage on all battery cells 108-1 simultaneously with BQ circuit 502-2 measuring the voltage on all battery cells 108-2. In some examples, as part of the EIS technique, current sensing device 504 also measures the current on battery cell 108. Such current sensing operations are at least combined with… Figure 6 Further description. In some examples, a given BQ circuit is referred to as a BQ chip.
[0065] BQ circuit 502 can perform additional operations to monitor the quality, state, or health of the battery cells. Such additional operations include, but are not limited to, temperature measurement. In some examples, BQ circuit 502 is referred to as a module-level circuit because there is one BQ circuit 502-1 for each module 304-1 (or for each group of battery cells 108-1), such as... Figure 3 As described herein. In some examples, the given BQ circuit 502-1 is referred to as a monitor circuit or a battery monitor integrated circuit (BMIC). As used above and herein, the terms “quality,” “status,” and “health status” are used interchangeably when referring to monitoring operations performed by the BQ circuit 502. The BQ circuit 502 can be implemented by any type of programmable circuit system. In some examples, the BQ circuit 502 performs, for example, monitoring operations by executing module-level BQ instructions. Figure 19 The flowchart represents the operation of a programmable circuit system to be instantiated.
[0066] The BQ circuit 502 can be implemented in various architectures. Figure 3 In the example, the function of BQ circuit 502 is implemented within auxiliary device 106, as described above. Figure 5 In the example, BQ circuit 502 is implemented as a separate and independent device. BQ circuits 502-2 to 502-11 communicate with their respective master devices 104 using auxiliary devices 106-2 to 106-11, which act as intermediate devices. Therefore, BQ circuits 502-2 to 502-11 are wirelessly connected to master device 104. However, BQ circuit 502-1 is directly coupled to master device 104-2 via a wired connection (without intermediate devices). Therefore, Figure 5 The example illustrates a hybrid battery system incorporating communication via both wireless and wired connections. Known WBMSs do not support EIS technology in such hybrid battery systems because the communication latency differences between the wired and wireless transmission media conflict with the objective of all BQ circuits 502 simultaneously recording voltage measurements. Advantageously, the technique described in the example herein effectively overcomes these conflicts, thereby supporting EIS operation in hybrid battery systems.
[0067] Figure 5 The example also illustrates an environment where, as Figure 4 The large number of auxiliary devices 106 and battery units 108 necessitates the use of multiple main devices 104-1 and 104-2. In this example, auxiliary devices 106-7 to 106-11 communicate wirelessly with main device 104-1, while auxiliary devices 106-2 to 106-6 communicate wirelessly with main device 104-2.
[0068] Generally, WBMS protocols have strict performance requirements, which are difficult to meet using more than one master device. For example, in some WBMS protocols: bandwidth is approximately 600 kbps or higher, data latency is approximately 100 milliseconds or lower, packet error rate is approximately 10⁻⁵ or lower, power consumption of master device 104 is less than approximately 1 mA, and power consumption of auxiliary device 106 is less than approximately 300 μA. In some examples, master devices 104-1 and 104-2 operate using independent clocks, which may cause the superframe interval of master device 104-2 to lag or lead in time relative to the superframe interval of master device 104-1.
[0069] From the perspective of internal network interference, there are three challenges. First, within a given implementation of WBMS 100, the master device 104 (e.g., Figure 5 104-1 and 104-2 in the specification are preferably synchronized in time. Secondly, the concurrent superframes of the master device 104 are preferably non-overlapping in frequency. Thirdly, the master device 104 is preferably capable of starting and running simultaneously based on commands from the host device. The techniques in this specification at least solve the first and second challenges. These techniques at least in Figure 13 and 18 Further details are provided below.
[0070] Figure 6 yes Figure 1 A block diagram of the implementation scheme for WBMS 100. Figure 6 A WBMS can be instantiated through programmable circuit systems (e.g., creating instances of it, making it exist for any length of time, materializing it, implementing it, etc.), such as a central processing unit (CPU) executing the first instruction, a field-programmable gate array (FPGA), a programmable logic device (PLD), a general-purpose array logic (GAL) device, a programmable array logic (PAL) device, a complex programmable logic device (CPLD), a simple programmable logic device (SPLD), a microcontroller (MCU), a programmable system-on-a-chip (PSoC), etc. Alternatively, Figure 6 The WBMS can be instantiated (e.g., instantiated, made to exist for any length of time, materialized, implemented, etc.) by constructing or configuring an (i) application-specific integrated circuit (ASIC) or (ii) field-programmable gate array (FPGA) to perform operations corresponding to the first instruction in response to the execution of the second instruction. Therefore, Figure 6 Some or all of the circuit systems can be instantiated at the same or different times. For example, Figure 6 Some or all of the circuitry can be instantiated in one or more threads that execute concurrently or sequentially on the hardware. Furthermore, in some examples, Figure 6 Some or all of the circuitry can be implemented by a microprocessor circuitry that executes instructions or by an FPGA circuitry that performs operations to implement one or more virtual machines or containers.
[0071] Figure 6 The example includes a battery controller device 102-1, two main devices 104, (n-1) auxiliary devices 106, n battery cells 108, and n BQ circuits 502, as described above. Figure 1-5 As described in one or more of them. Figure 5 It also includes an example excitation source 602 and a BQ package-level device 604. The scope of this specification is not limited to any particular number of [devices / items]. Figure 5 The examples show each type of device.
[0072] as Figure 5 , Figure 6 The example illustrates a hybrid battery system that supports EIS operation. Figure 6In the example, battery controller device 102-1 manages EIS measurements and performs subsequent analysis of the EIS measurements. More generally, battery controller 102-1 is responsible for monitoring and regulating the health status of WBMS 100. Therefore, as further described below, battery controller device 102-1 includes logic for at least: synchronizing measurements of BQ circuit 502 with each other in time, synchronizing measurements of BQ package-level device 604 with measurements of BQ circuit 502 in time, determining when to perform EIS measurements, and monitoring battery health status using synchronized current and voltage measurements. In other examples, one or more portions of the above logic are distributed across any number of devices containing programmable circuitry (e.g., including, but not limited to, master device 104). For example, WBMS 100 can be implemented without battery controller device 102-1, wherein master device 104-1 can be configured to perform the operations attributed to battery controller device 102-1 herein. In some examples, master device 104 and auxiliary device 106 perform operations, for example, by executing wireless device instructions. Figure 15-17 The flowchart represents the operation of a programmable circuit system to be instantiated.
[0073] Generally, EIS refers to the technique of analyzing how a battery responds to an AC signal. The excitation source 602 generates this AC signal based on instructions from the battery controller device 102. In some examples, the AC signal may correspond to multiple pulses within a frequency range. The devices within the WBMS 100 then measure the impedance of the battery cell 108 based on their response to the AC signal. Figure 6 In the example, the impedance is measured using both the module-level voltage measurement of BQ circuit 502 and the package-level current measurement of BQ package-level device 604. As used above and here, "package" refers to all battery cells 108 within a given WBMS 100.
[0074] BQ package-level device 604 is Figure 5 An example embodiment of the current sensing device 504 is described above. Therefore, the BQ package-level device 604 measures the current flowing through the package of the battery cell 108, as described above. In some examples, the BQ package-level device 604 is referred to as a monitor circuit or a package monitor integrated circuit (PMIC). The BQ package-level device 604 can be implemented by any type of programmable circuit system. In some examples, the BQ package-level device 604 executes BQ package-level instructions to perform actions such as those described above. Figure 18 The flowchart represents the operation of a programmable circuit system to be instantiated.
[0075] In this example, the BQ package-level device 604 is coupled to the main device 104-1 via a wired connection. Therefore, Figure 6The example illustrates a hybrid battery system where some monitor circuits (502-1 and 604) communicate with the battery controller device 102-1 only via a wired medium, while other monitor circuits (502-2 to 502-n) communicate with the battery controller device 102-1 via a wireless medium. In other examples, the BQ package-level device 604 is coupled to the battery controller device 102-1 via a wireless medium. Furthermore, in Figure 6 In the example, master device 104-1 uses a wired connection to ensure that BQ package-level device 604 is synchronized with the rest of WBMS 100. Master device 104-1 does this by sending reference signals and messages to BQ package-level device 604 over the wired connection, such as at least in combination with Figure 9 Further description.
[0076] In other examples, the BQ package-level device 604 is directly coupled to the battery controller device 102-1 via a wired connection (without intermediate devices). In such examples, the master device 104-1 still sends reference signals and messages to the BQ package-level device 604, but the transmissions are routed through the battery controller device 102-1. In yet another example, the WBMS 100 does not include the excitation source 602 or the BQ package-level device 604.
[0077] as Figure 5 , Figure 6 The example also illustrates an implementation of a WBMS 100 comprising two master devices 104. In this example, master device 104-1 communicates with BQ circuit 502-1 via a wired medium and wirelessly with auxiliary devices 106-2 to 106-n. The example superframe interval of master device 104-1 is combined... Figure 7 Let me describe it further.
[0078] Figure 7 The illustration shows that it can be generated by Figure 1-6 The timing diagram 700 illustrates a concurrent superframe communication protocol implemented in one or more example implementations of the WBMS 100. Specifically, timing diagram 700 includes a superframe 701 containing multiple time slots during which various devices in the WBMS 100 can transmit or receive data using Time Division Multiple Access (TDMA) technology. For example, superframe 701 includes time slots 711-716.
[0079] Superframe 701 describes the behavior of devices 703-706. In the example shown, device 703 can be... Figure 6 The main device 104-1 is shown. The remaining devices 704-706 can be auxiliary devices 106-2 to 106-x, as referenced above. Figure 6 As described. For ease of description, Figure 7Devices 703-706 are labeled as “Main 1”, “Device 2”, “Device 3” and “Device x”, respectively.
[0080] In other examples, Figure 7 Devices 703-706 refer to different combinations of master device 104 and auxiliary device 106. In some such examples, a given auxiliary device can communicate with multiple master devices 104 over concurrent superframe intervals, or switch from a first master device 104-1 to a second master device 104-2 between consecutive superframe intervals. Such auxiliary devices can communicate with multiple master devices 104 over multiple time slots to reduce the risk of data loss through data retransmission.
[0081] Before the first time slot 711, superframe 701 implements a downlink (DL) protection transmission period 723, which is useful for reducing the risk of interference to other superframes occurring before superframe 701. During the DL protection transmission period 723, auxiliary devices 704-706 enter receive modes 738, 744, and 750 (TsRxWait) respectively, meaning that these auxiliary devices 704-706 are ready to receive transmissions from another device.
[0082] After the DL protection transmission period 723 expires, concurrent time slot 711 begins. In time slot 711, master device 703 (e.g., primary 1) broadcasts data 724 to other devices 704-706. For example, master device 104-1 may broadcast data to one or more of auxiliary devices 106 during time slot 711. The data broadcast by master device 703 may contain synchronization information that receiving devices can use to synchronize their clocks with the clock of master device 703. For example, the data broadcast by master device 703 may contain timestamp data that receiving devices can use to synchronize their clocks with the clock of master device 703. The data broadcast by master device 703 may be referred to herein as the downlink. The digit 725 indicates that during transmission, master device 703 is in transmission mode (TsMaxTx). Simultaneously, auxiliary devices 704-706 are in receive modes 738, 744, and 750 (TsRxWait), respectively. During time slot 711, the master device 703 switches from transmit mode to receive mode, as indicated by digit 726 (Tx2Rx).
[0083] In some examples, multiple master devices 104 within WBMS 100 implement concurrent superframe intervals. For example, master device 104-2 (in Figure 7(2) The synchronization data can be broadcast to the master device 104-1 and one or more auxiliary devices 106 during time slot 712. In such examples, after transmission and reception are completed in time slot 712, the master device 104-2 switches from transmit mode to receive mode. In some examples, the concurrent superframe interval can be beneficial by increasing the amount of time allocated per superframe interval to a given group of battery cells 108-1. Examples of multiple master devices 104 coordinating concurrent superframe intervals are further described in commonly assigned U.S. Patent Application Publication No. 19 / 213,653, which is incorporated herein by reference as described above.
[0084] exist Figure 7 In the example, synchronization is completed after time slot 712. Time slot 713 occurs after time slot 712, during which multiple auxiliary devices simultaneously transmit data (e.g., status information collected from any of the battery cells 108) to the master device 703. For example, auxiliary device 704 may transmit data 743 to the master device 703. To enable such transmission, auxiliary device 704 is in transmission mode 742 (TsMaxTx). To facilitate the reception of transmitted data, master device 703 is in reception mode 731 (TsRxWait). The data broadcast by the auxiliary device to the master device may be referred to herein as the uplink.
[0085] Time slot 714 appears after time slot 713, during which auxiliary device 705 transmits data 747. Time slot 715 appears after time slot 714, during which auxiliary device 706 switches from receive mode to transmit mode 753 (Rx2Tx). Although a single time slot 715 is depicted between time slots 714 and 716 in this example, any number of time slots may be contained between time slots 714 and 716.
[0086] Time slot 716 occurs after time slot 715, during which auxiliary device 706 transmits data 755 to master device 703 (while simultaneously in transmission mode 754, i.e., TsMaxTx). In some examples, auxiliary device 706 has already transmitted data 755 to master device 703 during a previous time slot between time slots 714 and 716. Therefore, by transmitting data 755 twice during different time slots, the risk of data loss is reduced.
[0087] Redundant data transmission does not need to be performed in consecutive time slots. Transmitting the same data in non-consecutive time slots can be beneficial, for example, as the extra elapsed time between time slots helps to remove conditions or physical obstacles that might prevent successful data reception in the first of the two time slots. Data transmission redundancy as described above can be achieved when data is transmitted twice to the same master device. For example, specific data can be transmitted to a first master device at a first frequency and in a first superframe, and then again to the same first master device at a second frequency different from the first frequency and in a second superframe concurrent with the first superframe. Data redundancy can also be achieved even if data is transmitted twice at the same frequency. For example, specific data can be transmitted to a first master device at a first frequency and in a first superframe, and then again to a second master device at the same first frequency and in a second superframe concurrent with the first superframe. Data redundancy can also be achieved even if data is transmitted twice at the same frequency and to the same master device. For example, specific data can be transmitted to a first master device at a first frequency and in a first superframe, and then again to the same first master device at the same first frequency but in a second superframe concurrent with the first superframe. In other examples, specific data is transmitted twice to different masters and at different frequencies within a given superframe interval. Any and all such variations are taken into account, and they are included within the scope of this specification.
[0088] To reduce the risk of interference between simultaneous data transmissions and further reduce the risk of identical data transmissions occurring during separate time slots failing to reach their destination, the auxiliary device can use any of a variety of frequency hopping schemes. For example, referring to timing diagram 700, in concurrent time slots 713 and 719, data 743 can be transmitted on a first frequency, while data 776 can be transmitted simultaneously on a second frequency different from the first frequency. The first and second frequencies can be spaced at least 5 MHz or at least 10 MHz apart (or, in terms of channels, the channels used are spaced at least two, three, or five channels apart). Similarly, in concurrent time slots 714 and 720, data 743 and 776 can be transmitted simultaneously on the first and second frequencies respectively, wherein the first and second frequencies are spaced at least 5 MHz or at least 10 MHz apart (or, in terms of channels, the channels used are spaced at least two, three, or five channels apart). Using different frequencies for simultaneous data transmission reduces the risk of mutual interference between transmissions. An interval of at least 5 MHz or 10 MHz is an example of a minimum interval; in some examples, the techniques of this specification can be implemented with minimum frequency intervals other than 5 MHz or 10 MHz. Technical combination to ensure that multiple master devices 104 maintain at least a predetermined minimum frequency interval Figure 13 Further description.
[0089] Different frequencies in different time slots can also be useful. For example, in timing diagram 700, a first frequency can be used for transmission in time slot 713 and a second frequency in time slot 714, wherein the first and second frequencies are spaced at least 5 MHz or at least 10 MHz apart (or, in terms of channels, the channels used are spaced at least two, three, or five channels apart). To facilitate such frequency spacing, the master device (e.g., master device 104) can transmit specific frequency hopping schemes in its downlink to the auxiliary device (e.g., auxiliary device 106), which will be used during data transmission. Furthermore, in some examples, the auxiliary device can receive and transmit data at similar frequencies. For example, referring to timing diagram 700, auxiliary device 704 can receive data 724 at the first frequency in time slot 711, receive data 727 at the second frequency in time slot 712, and transmit data 743 at the third frequency in time slot 713. In some examples, the first and third frequencies may be the same.
[0090] As an example only, a master device can use a frequency-hopping sequence with thirty-seven channels within the Industrial, Scientific, and Medical (ISM) bands. These bands are ordered randomly within the frequency-hopping sequence and satisfy the condition of a 5 MHz or 10 MHz interval between adjacent frequencies. For example, the first frequency-hopping sequence is {2410 MHz, 2404 MHz, 2416 MHz, ...}. The second frequency-hopping sequence can be a different version of the first frequency-hopping sequence, but shifted by one position. Thus, the second frequency-hopping sequence is {2404 MHz, 2416 MHz, ... 2410 MHz}, maintaining at least a 5 MHz interval or at least a 10 MHz interval for one master device to operate at the first frequency (2410 MHz) and another master device to operate at the second frequency (2404 MHz). After each hop, the first and second frequencies remain 5 MHz or 10 MHz apart.
[0091] In addition to transmitting frequency hopping schemes in the downlink, the master device 104 can transmit scheduling instructions to the auxiliary device 106 in the downlink. For example, one or more master devices 104 can be configured to instruct the auxiliary device 106 to transmit a specific time slot and specific channel or frequency for a given superframe of the uplink to the master device 104. The master device 104 can change the scheduling instructions in each superframe interval, or alternatively, can maintain the same scheduling instructions in multiple consecutive superframe intervals. The master device 104 can also transmit additional information to the auxiliary device 106, such as acknowledgments of uplink transmissions from the previous superframe, indications of when the next superframe can begin, adaptive frequency hopping countdowns, etc. In some examples, the master device 104 does not transmit scheduling instructions to the auxiliary device 106 in the downlink. Instead, some or all of the devices in WBMS 100 are pre-programmed with defined schedules that will be executed in some or all of the superframe intervals unless otherwise instructed by one or more master devices 104. Alternatively, the master device 104 may transmit a single downlink containing scheduling instructions that will be executed over all superframe intervals until further notice. The battery controller device 102 may provide the scheduling instructions to the master device 104, which may then distribute these instructions to the remaining devices in the WBMS 100.
[0092] The auxiliary device 106 transmits data to the master device according to scheduling instructions and channel or frequency instructions provided by the master device 104 or pre-programmed into the auxiliary device. After receiving downlink transmissions from the master device 104-1, the auxiliary device 106-2 can parse the transmissions to determine the time slot and channel or frequency for which the auxiliary device 106-2 is scheduled to perform uplink information transmissions to the master device. In some examples, information on how to parse downlink transmissions can be provided to the auxiliary device during the WBMS network formation process.
[0093] In some examples, the auxiliary device includes multiple transceivers. For example, such as... Figure 2 As shown, the auxiliary device 106-1 includes multiple transceivers 128-1. Therefore, the auxiliary device 106-1 can simultaneously (in the same time slot) transmit data 743 twice using different transceivers 128-1. Such simultaneous transmissions can occur at the same or different frequencies. The transmissions can be directed to the same or different master devices 104 (e.g., both the auxiliary device and the master device may have multiple transceivers communicating simultaneously at different frequencies). Therefore, the redundancy achieved by a single transceiver auxiliary device transmitting the same data in different time slots can be achieved within a shorter time frame using a multi-transceiver auxiliary device.
[0094] In some examples, uplink data transmission can be performed in consecutive time slots of concurrent superframes to accommodate large amounts of data that cannot be transmitted in a single uplink. Such technology is described in U.S. Application No. 2025 / 0039859, filed July 28, 2023, entitled “Methods and Apparatus to Determine Communication Schedules for Wireless Battery Systems,” which is hereby incorporated herein by reference in its entirety.
[0095] Figure 8 This is a block diagram of example device 800. Figure 8 In this example, the main device 104 or auxiliary device 106 includes a system core (sys core) 802, a memory 804, a radio frequency core (RF core) 806, general-purpose hardware peripherals and modules 808, a sensor interface 810, and clock and reference signals 812. In this example, Figure 6 The main device 104 and the auxiliary device 106 are each free Figure 8 This is implemented as one instance of device 800. In some examples, one or more of the battery management device 102-1, main device 104, or auxiliary device 106 are implemented using different computing architectures.
[0096] The sys core 802 contains a processor 814 responsible for the system-level operations of device 800. For example, when device 800 is implemented as a master device (e.g., 104-1), processor 814 interprets instructions from battery controller device 102-1, determines when and how to schedule superframe intervals, responds to battery controller device 102-1 using EIS measurements and status updates, and so on. Similarly, when device 800 is implemented as an auxiliary device (e.g., 106-2), processor 814 interprets instructions from one of the master devices 106, determines when to respond within a superframe interval, determines what data to include in the response, and so on. Processor 814 can be implemented by any type of programmable circuit system.
[0097] The sys core 802 performs system-level operations by supporting resources typically available for any component in device 800. Such resources include, but are not limited to, memory 804 and clock and reference signals 812. The speed at which the sys core 802 performs a given operation depends on various factors, including, but not limited to, the role of device 800 within WBMS 100, the rate of use of system-level resources in device 800, clock drift, etc. Therefore, the operation performed by the sys core 802 has a system-level latency unique to a specific implementation of device 800. For example, the sys core 802 in auxiliary device 106-2 may produce a different amount of system-level latency than that in main device 104-1 or auxiliary device 106-3.
[0098] RF core 806 refers to a set of components that operate independently of sys core 802. For example, RF core 806 includes processor 816, RAM 818, ROM 820, and radio timer (RAT) 822. As used herein, RAT 822 refers to the circuitry configured to generate clock signals separate from clock and reference signals 812. Processor 816 operates with the support of RAM 818, ROM 820, and RAT 822, and therefore does not depend on other components outside of RF core 806. Therefore, operations performed by RF core 806 do not exhibit the system-level latency present when operations are performed by sys core 802.
[0099] The RF core 806 is designed to perform radio operations (e.g., to implement wireless communication with other devices). However, the RF core 806 can also communicate with devices via wired communication, and transmit signals, for example, through general-purpose hardware peripherals and general-purpose input / output (GPIO) pins or serial peripheral interface (SPI) pins within module 808. In some examples, the RF core 806 is referred to as a communication circuit.
[0100] Figure 9 It is possible Figure 6 An illustrative example of timing signals exchanged between devices in a WBMS. Figure 9 The example includes a management device 902, a measurement device 904, an SPI interface 906, a GPIO interface 908, messages 910, 912, and 914, and a timeline. In this example, the management device 902 can be... Figure 6 The main device 104-1 or auxiliary device 106 may be implemented by one or more of them. Similarly, the measuring device 904 may be implemented by one or more of the module-level circuit BQ circuit 502 and the package-level circuit BQ circuit 604.
[0101] The management device 902 and the measuring device 904 are connected to each other via at least two wired connections, wherein the first wired connection implements the GPIO interface 908 and the second wired connection implements the SPI interface 906. In some examples, the management device 902 and the measuring device 904 are connected to each other via additional wired and / or wireless connections. In some examples, as a supplement or alternative to wires, the GPIO interface 908 and / or the SPI interface 906 are also implemented by interconnects, pins, ports, terminals, etc.
[0102] Figure 9 The diagram illustrates the transmission of a reference signal from management device 902 to measurement device 904 via GPIO interface 908. In this example, pulses appear in the reference signal at T1, T2, and T3. As used herein, pulses in the reference signal transmitted across GPIO interface 908 can be referred to as GPIO switching. Measurement device 904 performs several synchronization operations based on GPIO switching. First, measurement device 904 initiates EIS measurement in response to receiving a GPIO switching. Second, measurement device 904 uses the GPIO switching as a reference point to adjust its internal clock based on the difference between a) a local timestamp generated by measurement device 904 and b) a global timestamp reported by management device 902. For example, measurement device 904 receives a GPIO switching at T1. Figure 9 The first GPIO switch. Assume the internal clock of measurement device 904 indicates T1 = 600 microseconds (µs), but the global timestamp from management device 902 indicates T1 = 1.00 milliseconds (ms). In this example, management device 904 adjusts its internal clock by 400 µs after receiving the GPIO switch, synchronizing it with the rest of the module-level BQ circuit 502 and package-level BQ circuit 604. As used above and here, the global timestamp refers to the timestamp of a clock signal used globally throughout the WBMS 100 to synchronize operations (e.g., EIS measurements). In some examples, the global timestamp is called a reference timestamp because it can be used as a reference for performing clock adjustments. In some examples, management device 902 uses techniques other than GPIO interface 908 to transmit a reference signal to measurement device 904.
[0103] The management device 904 also transmits one or more messages to the measurement device 904 via the SPI interface 906. These messages from the SPI interface 906 use a global timestamp to describe the arrival of a GPIO switch. For example, suppose... Figure 9The reference signal is aperiodic, causing the difference between GPIO switches (e.g., the values of (T2-T1) and (T3-T2)) to be unequal. In such an example, the management device 902 transmits message 910 to the measurement device 904 before T1, the message describing T1 using a global timestamp. The measurement device 904 can extract the global timestamp from message 910. The measurement device 904 stores the value from message 910 in an internal register and then uses the value to adjust its internal clock at T1 (e.g., after receiving a GPIO switch), as described above. Similarly, when the reference signal is aperiodic, the management device 904 transmits message 912 before T2 to describe T2 using a global timestamp, and message 914 before T3 to describe T3 using a global timestamp.
[0104] Alternatively, if Figure 9 If the reference signal is periodic, then the management device 902 sends only one message to describe both: a) the first GPIO switch using a global timestamp, and b) the frequency of the periodic reference signal. For example, suppose message 910 describes T1 using a global timestamp and indicates that subsequent GPIO switches will occur every 10 ms. In such examples, messages 912 and 914 are not transmitted because the measurement device 904 can determine T2 = T1 + 10 ms, T3 = T1 + 20 ms, etc., using only message 910. In some examples, the management device 902 uses techniques other than the SPI interface 906 to transmit one or more messages to the measurement device 904.
[0105] The dual purpose of the reference signal (serving as a reference for internal clock synchronization of EIS measurements) underscores the need for the management devices 904 across the WBMS 100 to transmit GPIO switches as synchronously as possible with each other. Advantageously, the example described herein uses... Figure 8 The RF core 806 transmits reference signals via GPIO interface 908, while the sys core 802 simultaneously transmits messages via SPI interface 906. In these examples, the timing of messages 910, 912, and 914 can tolerate some inaccuracies caused by system-level latency because these messages only need to arrive at their respective measurement devices 904 before T1, T2, or T3, respectively. Conversely, the timing of the reference signal is synchronized across the WBMS100 with higher accuracy than messages 910-914 because a) the RF core 806 does not have the system-level latency of the sys core 802, and b) the speed and accuracy supported by GPIO pins are generally higher than those of pins implementing the SPI protocol. Furthermore, using the RF core 806 to transmit reference signals via GPIO interface 908 enables the examples described herein to be more accurate than known WBMS systems.
[0106] Figure 10 It is possible Figure 6An illustrative example of a just-in-time protocol implemented within a WBMS. Figure 10 The examples include timelines 1002, 1004, and 1006, which correspond to example operations performed by the main device 104-1, auxiliary device 106-2, and auxiliary device 106-3 during the superframe (SF) interval, respectively.
[0107] Figure 10 Examples begin with a Tstart that has DL protection before the start of the superframe interval (e.g., Figure 7 (723). After DL protection, an RF command from the master device 104-1 initiates a superframe interval by transmitting a DL frame. Timeline 1002 shows that in this example, the DL frame contains a preamble, a synchronization frame delimiter (SFD), and a payload.
[0108] The RF core 806 of the auxiliary device 106 receives DL frames and then uses SFD as a reference point to synchronously trigger EIS measurements. To receive DL frames, the RF core 806 of the auxiliary device 106 demodulates the signal from the main device 104 and extracts data from the demodulated signal. Figure 10 In the example, once an SFD is detected, the RF core 806 of the auxiliary device 106 transmits a GPIO switch to the corresponding BQ circuit 502. The RF core of the auxiliary device 106 can be configured to transmit GPIO switches without involving (e.g., independently of) the sys core 802 and any software running on the sys core 802. The RF core can also be configured to transmit GPIO switches using only the hardware within the RF core, i.e., independently of any software running on the RF core. For example, timeline 1004 shows the auxiliary device 106-2 in T... D1 SFD is detected and GPIO switching is transmitted. Similarly, timeline 1006 shows auxiliary device 106-2 at T D2 SFD is detected and a GPIO switch is transmitted. In some examples, Figure 10 The operation is called a just-in-time protocol because the auxiliary device 106 receives the SFD just before the EIS measurement is scheduled to occur. In other examples, the RF core 806 transmits a GPIO switch to the corresponding BQ circuit 502 after detecting the start of a packet and, or not after detecting the SFD within the DL frame. As used herein, the start of a packet can refer to the SFD, the preamble, and / or another indication of the start of a packet.
[0109] Within the main unit 104-1, when the timer implemented by the RAT 822 expires, the RF core 806 also transmits a GPIO switch to its corresponding BQ device (e.g., 502-1 and 604). Figure 10 In the example, the RAT timeout is marked as (RF command start + τ) in timeline 1002. Advantageously, (RF command start + τ), TD1 and T D2 The time difference between them is minimal because the transmission, reception, and GPIO switching of SFD are all performed by the RF core 806, thus avoiding system-level latency. More generally, the time difference between GPIO switching transmitted using a just-in-time protocol can support strict thermal runaway notification standards and is more accurate than known techniques.
[0110] Timelines 1004 and 1006 show that within auxiliary devices 106-2 and 106-3, the RF core 806 receives the SFD by appending it to the end of the frame (e.g., T, respectively). D1 and T D2 This modifies copies of their DL frames. Then, the RF core 806 transmits the modified DL frames to their corresponding sys core 802. The sys core 802 uses T... D1 and T D2 The reported values are used to reduce clock drift relative to the clock and reference signal 812, thereby preventing the accumulation of system-level latency effects. In some examples, the sys core 802 also uses timestamps describing SFD detection to prepare a response for its allocated time slots to the superframe (e.g., using timestamps to organize and / or generate data including the response). The sys core 802 can be configured to generate timestamps in response to the receipt of a DL frame, and the timestamps can indicate the time of SFD reception in the DL frame.
[0111] exist Figure 10 In the example, the reference signals sent to the module-level BQ circuit 502 and the package-level BQ device 604 are periodic. Therefore, the aforementioned operation is repeated at regular timing intervals, and Figure 10 The device transmits GPIO switching during the DL frame at the beginning of the next superframe interval.
[0112] Figure 11 It is possible Figure 6 The first illustrative example of a scheduling protocol implemented within WBMS. Figure 11 The examples include timelines 1102, 1104, and 1106, which correspond to example operations performed by the main device 104-1, auxiliary device 106-2, and auxiliary device 106-3 during the superframe (SF) interval, respectively.
[0113] Figure 11 The diagram illustrates the transmission of DL frames containing SFDs at the start of a superframe interval in both the just-in-time protocol and the scheduling protocol. However, in the scheduling protocol, the Sys core 802 uses the SFD timestamp to schedule GPIO switching transmissions at a later time point. For example, timeline 1104 shows the Sys core 802 within the auxiliary device 106-2 instructing the RF core 806 to transmit at (T... D1x =TD1 +Δ) transmits GPIO switching, where Δ refers to the time interval between consecutive GPIO switching. Upon receiving the instruction, the RF core 806 within the auxiliary device 106-2 starts a timer using the RAT 822, which is set at T... D1x Expiration. RF core 806 transmits GPIO switching after the RAT timer expires. Similarly, timeline 1106 shows sys core 802 within auxiliary device 106-3 instructing RF core 806 to switch GPIOs after the RAT timer expires. D2x =T D2 +Δ) transmit GPIO switching, and the RF core 806 sets the timer to T D2x Expiration. Timeline 1102 also shows that the RF core 806 in the main unit 104-1 sets its RAT 822 to T based on the previous instruction from the corresponding sys core 802. Mx maturity.
[0114] exist Figure 10 Just-in-time agreement and Figure 11 In both scheduling protocols, the time difference between the expiration of SFD and RAT 822 is typically less than 100 nanoseconds (ns). Therefore, clock drift from RAT 822 occurring within such a short duration is generally considered negligible, and the timestamp T... Mx T D1x and T D1x It occurs synchronously with high precision (e.g., simultaneously with each other). In the scheduling protocol, T D1x and T D1x The value is partly determined by the sys core 802. Figure 11 In the example, timelines 1104 and 1106 illustrate how system-level latency causes the sys core 802 in auxiliary devices 106-2 and 106-3 to send their TD1x and TD2x instructions to the corresponding RF core 806 at different times. Advantageously, the RF core 806 sets their RAT 822 to different values so that both times expire simultaneously. More generally, the use of RAT 822 allows GPIO tools to transmit regardless of system-level latency, even if the sys core 802 was involved in the previous operation. Therefore, the scheduling protocol described in this example provides flexibility (e.g., synchronous GPIO switching can occur not only at the start of a superframe but also at any time) while still maintaining high accuracy to support stringent thermal runaway notification standards.
[0115] Figure 12 It is possible Figure 10 Just-in-time agreement or Figure 11 An illustrative example of a standby timer used within the scheduling protocol. Figure 12The examples include timelines 1202, 1204, and 1206, which correspond to example operations performed by the RF core 806 of the main device 104-1, auxiliary device 106-2, and auxiliary device 106-3 during the superframe (SF) interval, respectively.
[0116] Both just-in-time protocols and scheduling protocols enable Figure 9 The management device 902 uses SFD to transmit GPIO switching. However, in some examples, the auxiliary device 106 discards packets and does not receive DL frames due to the volatility of wireless communication. Advantageously, the RF core 806 in the auxiliary device 106 uses RAT 822 to set a backup timer in case DL frames are discarded. For example, timelines 1204 and 1206 show both auxiliary devices 106-2 and 106-3 in T D1 =T D2 Receive DL frames, set RAT 822 to T D1x =T D2x The GPIO switch expires, and a GPIO switch is transmitted after RAT 822 expires. After the GPIO switch RAT transmission 822, both auxiliary devices 106-2 and 106-3 reset their RAT 822 to a new value that expires when the RF core 806 anticipates the next GPIO switch transmission. In some examples, this timer value is referred to as the spare RAT.
[0117] exist Figure 12 In the example, timeline 1206 shows the auxiliary device 106-3 in T E2 The next DL frame was successfully received. Therefore, the RF core 806 in auxiliary device 106-3 is in T E2 Cancel the standby RAT and, based on the scheduling protocol, set the new timer value in RAT 822 to T. E2x Expiration date. In contrast, timeline 1204 shows that auxiliary device 106-1 should have been due at T. E1 =T E2 The next DL frame was received, but this was not done. Therefore, the RF core 806 allowed the initial settings to be configured in T... D1x The backup RAT continues to run after T E1 And proceed to the next superframe interval. The spare RAT in timeline 1204 is in T... E1x =T E2x The expiration date allows the auxiliary device 106-2 to transmit its GPIO switching with high precision, even if it fails to receive SFD.
[0118] although Figure 12 It shows Figure 11 This is an example implementation of the scheduling protocol, but using a spare RAT to deal with dropped DL frames can also be applied. Figure 10The just-in-time protocol. In such an example, the backup RAT starts immediately after receiving the SFD / transmit GPIO switch and is set to expire at the time when the RF core 806 expects the next SFD to occur. If the RF core 806 receives the next SFD before the backup RAT expires, the backup RAT is canceled, and the GPIO switch is transmitted after the SFD is received. Alternatively, if the RF core 806 fails to receive the next SFD, the RF core 806 still transmits the GPIO switch when the backup RAT expires. Therefore, using RAT 822 as a backup in either of the protocols described in this example mitigates the relative unreliability of wireless communication and ensures that a given auxiliary device 106 transmits the GPIO switch when it is scheduled to transmit the GPIO switch. Furthermore, if a minimum clock drift in RAT 822 occurs due to the loss of a DL frame, which also indicates a resynchronization failure, then the drift is determined by the RF core 806 through the timestamp in the modified DL frame (e.g., T). D1 The data is quantified and reported to the system core 802, so that WBMS 100 can respond accordingly.
[0119] In some examples, the master device 104-1 transmits DL frames in each superframe interval, regardless of the content of the superframe or how many auxiliary devices 106 successfully receive the DL. This type of example can be referred to as active mode. In active mode, the master device 104-1 and the corresponding auxiliary device 106-2 can declare a synchronization loss and perform synchronization operations if the auxiliary device 106-2 fails to receive DL frames for a threshold number of consecutive times (e.g., 16 consecutive failures). In other examples, the master device 104-1 does not transmit DL frames in each superframe interval, but instead includes DL frames at a lower frequency (e.g., once every 300 ms). In some examples, this lower frequency can be referred to as keep-alive interval (KAI).
[0120] Besides timing accuracy, another advantage of using the RAT 822 as described above is that the RF core 806 automatically handles power management to minimize power consumption. For example, if the timer expiration time set on the RAT 822 is far enough away, the RF core 806 will put itself into a low-power mode while waiting for the timer to expire. In some examples, the RAT 822 is shut down during low-power operation, but the RAT 822 is calibrated by a real-time clock (RTC) and has the expected accuracy of one or two RAT clock cycles at power-up.
[0121] Compared to the RF core 806, low-power mode typically has a greater impact on the sys core 802. In such examples, software execution timing may be delayed during the wake-up process. Therefore, in examples requiring software execution from the sys core 802, software settings prevent the sys core 802 from entering a low-power (e.g., standby) mode to ensure timing accuracy.
[0122] Figure 13 yes Figure 10 An illustrative example of the implementation of a just-in-time agreement. Similarly, Figure 14 yes Figure 11 An illustrative example of the execution of the scheduling protocol. Figure 13 and 14 Examples are shown where each master device 104 has two auxiliary devices 106 and the superframe interval is 6ms. Figure 13 In the example, a GPIO switch is transmitted when an SFD is detected, according to the just-in-time protocol. Figure 14 In the example, according to the scheduling protocol, the GPIO is switched after the RAT 822 times out by 5 ms.
[0123] Figure 13 and 14 Both also illustrate: a) GPIO signals transmitted from auxiliary device 106-2 to BQ circuit 502-2, and b) GPIO signals transmitted from auxiliary device 106-3 to BQ circuit 502-3. Figure 13 and 14 In the examples above, the GPIO switching occurs on both the falling and rising edges of the GPIO signal. Therefore, in both examples, the aforementioned signals show that the synchronized GPIO switching occurs less than 1 µs apart. More generally, Figure 13 and 14 It is shown that both just-in-time and scheduling protocols can be used to synchronously perform EIS measurements with high precision, thereby facilitating reliable measurements of battery characteristics.
[0124] Figure 15 It means that it can be generated by Figure 6 The flowchart illustrates the example machine-readable instructions and / or example operations 1500 executed, instantiated, and / or performed by the main device 104. Although Figure 15 The following description is based on main device 104-1, but... Figure 15 The machine-readable instructions and / or example operations 1500 can be implemented by any of the master devices 104 in WBMS 100. Figure 15The flowchart begins with the RF core 806 of the master device 104-1 optionally transmitting an SPI message indicating when to schedule battery measurements (Box 1502). To achieve this, the RF core 806 generates an SPI message describing when one or more upcoming GPIO triggers will be transmitted. The reception of the SPI message and subsequent operations are then combined... Figure 18 Further description. In the example where GPIO switching is periodic, master device 104-1 can execute block 1502 only once by sending an SPI message describing a) the timestamp of the first GPIO switch and b) the frequency of subsequent GPIO switches. In the example where GPIO switching is not periodic, master device 104-1... Figure 15 Execute box 1502 once in each iteration of the flowchart.
[0125] The RF core 806 of the master device 104-1 transmits the synchronization frame delimiter (SFD) within the downlink (DL) frame at the start of the superframe interval (box 1504). The DL frame is transmitted via the radio interface to one or more auxiliary devices (e.g., Figure 6 (106-2 and 106-3 in the text). The DL frame of box 1504 may contain the following as described above. Figure 7 and 10 Additional information as described in the document. In some examples, the transmission of the DL frame at box 1504 is referred to as downlink communication.
[0126] The sys core 802 of the master device 104-1 instructs the RF core 806 to transmit a GPIO switch at a specific timestamp (box 1506). In the just-in-time protocol, the timestamp describes the time when the sys core 802 expects the auxiliary device 106 to receive the SFD from box 1504. In the scheduling protocol, the timestamp refers to the point in time after the SFD is received but before the end of the current superframe interval.
[0127] The RF core 806 of the main device 104-1 sets the RAT 822 with a timer value that expires at the timestamp in box 1506 (box 1508). Advantageously, the RAT 822 is used only by other components within the RF core 806 and therefore does not exhibit the system-level latency of the sys core 802.
[0128] The RF core 806 of the main device 104-1 determines whether RAT 822 has expired (Box 1510). If RAT has not expired (Box 1510: No), then control returns to Box 1510, where RF core 806 checks RAT 822 again after a time interval (e.g., after one or more clock cycles). In some examples, RF core 806 enters a low-power mode between subsequent iterations of Box 1510, as described above. If RAT has expired (Box 1510: Yes), then RF core 806 transmits a GPIO switch to one or more BQ circuits 502 (Box 1512). RF core 806 transmits the GPIO switch to prompt or cause the battery monitor circuitry to perform measurements and other operations, such as in conjunction with... Figure 18 Further description: The battery monitor circuit can be configured to perform measurements in response to a received GPIO switch.
[0129] The syscore 802 of the master device 104-1 determines whether to continue (box 1514). In some examples, the syscore 802 continues whenever the master device 104-1 is powered on. In other examples, the syscore 802 continues only during the measurement window defined by the battery controller device 102-1. If the syscore 802 does not continue, then machine-readable instructions and / or operation 1500 terminates (box 1514: No). Alternatively, if the syscore 802 continues (box 1514: Yes), then control returns to box 1502, where the RF core 806 optionally transmits another SPI message.
[0130] Although Figure 15 The foregoing description refers to main device 104-1, but Figure 15 The machine-readable instructions and / or operations 1500 can also be provided by Figure 6 The battery controller device 102-1 is used for implementation. In this example, the SPI messages of block 1502 and the GPIO switching of block 1512 are received by the BQ package-level device 604 instead of the module-level BQ circuit 502-1. The GPIO switching can prompt the BQ package-level device 604 to perform measurements.
[0131] Figure 16 It means that it can be generated by Figure 6 A flowchart illustrating example machine-readable instructions or example operations implemented, instantiated, and / or executed by the auxiliary device to implement the just-in-time protocol. Although Figure 16 The following description is based on auxiliary device 106-2, but... Figure 16 The machine-readable instructions and / or example operations 1600 can be implemented by any of the auxiliary devices 106 in WBMS 100.
[0132] Figure 16Execution begins with the optional transmission of an SPI message by the RF core 806 of auxiliary device 106-2, indicating when to schedule battery measurements (Box 1602). Auxiliary device 106-2 optionally uses the above combination Figure 15 The same techniques and logic described in box 1502 are used to execute box 1602.
[0133] The RF core 806 of auxiliary device 106-2 determines whether a DL frame has been received at the expected time (Box 1604). The RF core 806 determines the expected time of Box 1604 based on a) a previous instruction from master device 104-1 and / or b) the timing of a previous superframe interval. If a DL frame is received at the expected time (Box 1604: Yes), then the RF core 806 within auxiliary device 106-2 transmits a GPIO switch after detecting an SFD within the DL frame (Box 1606). The reception and subsequent operation of the GPIO switch are combined... Figure 18 Further description. In some examples, the RF core 806 also removes the standby RAT at box 1606, as described further below.
[0134] The RF core 806 of auxiliary device 106-2 adds a timestamp describing when the SFD was received to the end of the DL frame (Box 1608). Then, RF core 806 provides the modified DL frame of Box 1608 to the sys core 802 of auxiliary device 106-2 (Box 1610). The timestamp in Box 1608 allows both RF core 806 and sys core 802 to optionally adjust their clocks (Box 1612). For example, based on the difference between the expected and actual timestamp values, RF core 806 can adjust the clock generation circuitry system powered by the RAT 822, and / or sys core 802 can adjust one or more system-level clock signals.
[0135] Alternatively, if the RF core 806 of auxiliary device 106-2 does not receive the DL frame at the expected time (box 1604: No), then the RF core 806 transmits a GPIO switch once the timer set on RAT 822 expires (box 1614). Figure 16 In the example, the timer set on RAT 822 is called the standby RAT because it does not expire in the expected program execution path via box 1612 (box 1604: Yes).
[0136] The sys core 802 of auxiliary device 106-2 determines whether to continue. (Box 1616). The sys core 802 uses the above-described... Figure 15 The same techniques and logic described in box 1514 are used to execute box 1616.
[0137] If sys core 802 does not continue, then machine-readable instructions and / or operation 1600 terminates. (Box 1616: No). Alternatively, if sys core 802 continues (Box 1616: Yes), then RF core 806 sets the standby RAT to expire at the expected time of the next SFD. (Box 1618). The RF core 806 of auxiliary device 106-2 can determine the expected time to receive the next SFD based on a) instructions from battery controller device 102 and / or b) timing of the previous overframe interval. Control then returns to box 1602, where the RF core 806 of auxiliary device 106-2 optionally transmits SPI messages.
[0138] Figure 17 It means that it can be generated by Figure 6 A flowchart illustrating the auxiliary device's implementation, instantiation, and / or execution of example machine-readable instructions or example operations to implement the scheduling protocol. Although Figure 17 The following description is based on auxiliary device 106-2, but... Figure 17 The machine-readable instructions and / or example operations 1700 can be implemented by any of the auxiliary devices 106 in WBMS 100.
[0139] Figure 17 Execution begins with the optional transmission of an SPI message by the RF core 806 of auxiliary device 106-2, indicating when to schedule battery measurements (Box 1702). Auxiliary device 106-2 optionally uses the above combination Figure 15 The same techniques and logic described in box 1502 are used to execute box 1702.
[0140] The RF core 806 of auxiliary device 106-2 determines whether a DL frame has been received at the expected time (Box 1704). If a DL frame is received at the expected time (Box 1704: Yes), then RF core 806 adds a first timestamp describing when the SFD was received to the end of the DL frame (Box 1706), and then provides the modified DL to sys core 802 (Box 1708). The first timestamp allows both RF core 806 and sys core 802 to optionally adjust their clocks (Box 1710). Auxiliary device 106-2 performs Boxes 1704, 1706, 1708, and 1710 using the same techniques and logic as Boxes 1604, 1608, 1610, and 1612, respectively. In some examples, RF core 806 also cancels the spare RAT at Box 1706, as further described below.
[0141] The sys core 802 of auxiliary device 106-2 instructs RF core 806 to transmit GPIO switching at a second timestamp (Box 1712). The second timestamp occurs after the first timestamp (e.g., after SFD detection) but before the end of the current superframe interval. In some examples, the sys core 802 determines the value of the second timestamp based on instructions from battery controller device 102-1. Furthermore, execution... Figure 17 The one or more auxiliary devices 106 select the same value for the second timestamp at block 1712 to ensure synchronized EIS measurements.
[0142] The RF core 806 of auxiliary device 106-2 sets RAT 822 to expire at the second timestamp (box 1714). Advantageously, even if multiple auxiliary devices 106 execute box 1712 at different times due to different system-level delays, RAT 822 of box 1714 can maintain synchronized EIS measurements.
[0143] The RF core 806 of auxiliary device 106-2 transmits GPIO switching when the RAT expires (Box 1716). The reception and subsequent operations of the GPIO switching are combined. Figure 18 Further description.
[0144] Alternatively, if the RF core 806 of auxiliary device 106-2 does not receive the DL frame at the expected time (box 1704: No), then the RF core 806 transmits a GPIO switch once the standby timer set on RAT 822 expires (box 1718). The timer in box 1718 is referred to as standby in this example because a) it is separate from the timer running from box 1714 to box 1716, and b) the timer in box 1718 does not expire in the expected program execution path through box 1720 (box 1704: Yes). In some examples, the RF core 806 enters a low-power mode between failing to receive the DL frame (box 1704: No) and the standby RAT at box 1718 expiring.
[0145] The sys core 802 of auxiliary device 106-2 determines whether to continue. (Box 1720). The sys core 802 uses the above-described... Figure 15 The same techniques and logic described in box 1514 are used to execute box 1720.
[0146] If sys core 802 does not continue, then machine-readable instructions and / or operation 1600 terminates. (Box 1720: No). Alternatively, if sys core 802 continues (Box 1720: Yes), then RF core 806 sets the spare RAT to expire at the expected time for the next GPIO switchover transfer. (Box 1722). The RF core 806 of auxiliary device 106-2 can determine the expected time for executing the next iteration of box 1716 based on a) instructions from battery controller device 102 and / or b) timing of the previous superframe interval. Control then returns to box 1702, where the RF core 806 of auxiliary device 106-2 optionally transmits SPI messages.
[0147] Figure 18 It means that it can be used. Figure 9 The flowchart of example machine-readable instructions or example operations 1800 implemented, instantiated, and / or executed by the example programmable circuit system implementation of the measuring device 904. Figure 18 The flowchart can be implemented by either the module-level BQ circuit 502 and / or the package-level BQ circuit 604.
[0148] Machine-readable instructions or operations 1800 begin when measuring device 904 optionally receives SPI messages (box 1802). In some examples, when GPIO switching is not periodic, measuring device 904 targets... Figure 18 Each iteration of the flowchart receives a message at box 1802. In other examples, the measurement receives a total of one message at the start of a periodic GPIO switching sequence.
[0149] Measuring device 904 determines whether a GPIO switch has been received (box 1804). The GPIO switch can be transmitted by any suitable implementation of a management device (e.g., one of the battery controller devices 102-1, one of the main devices 104, one of the auxiliary devices 106, etc.). If a GPIO switch has not been received (box 1804: No), then control returns to box 1804, where measuring device 904 checks for a GPIO switch again after a certain time interval.
[0150] If a GPIO switch has been received (Box 1804: Yes), then the measurement device 904 performs one or more battery measurement operations (Box 1806). The measurement can be module-level or package-level, depending on the implementation. Figure 18 The flowchart describes the type of device. In some examples, the measurement in box 1806 is an EIS measurement.
[0151] The measuring device 904 reports the results of the battery measurement operation to the management device 902 (box 1808). Depending on the architecture of the WBMS 100, the corresponding measurement values can be reported in any suitable format and through any suitable medium.
[0152] Measurement device 904 performs one or more clock synchronization operations (box 1810). To achieve this, measurement device 904 compares the actual time when a GPIO switch at box 1804 is received with the expected time based on its internal clock. Measurement device 904 determines the expected time of receiving an upcoming GPIO switch based on one or more SPI messages previously received at box 1802.
[0153] Measurement device 904 determines whether to continue (box 1812). In some examples, measurement device 904 continues whenever the device is powered on. If measurement device 904 continues (box 1812: Yes), then control returns to box 1802, where measurement device 904 optionally receives another SPI message. If measurement device 904 does not continue (box 1812: No), then machine-readable instructions and / or operation 1800 terminates.
[0154] Figure 19 Is it constructed for execution or instantiation? Figure 15-18 One or more of the example machine-readable instructions or example operations are used to implement Figure 6 A block diagram of an example programmable circuit system platform 1900 for WBMS 100. For example, the programmable circuit system platform 1900 can be a server, personal computer, workstation, electronic control unit (ECU), or any other type of computing or electronic device. In this example, the programmable circuit system platform implements one or more of a battery controller device 102, a main device 104, or an auxiliary device 106.
[0155] The programmable circuit system platform 1900 shown in the example includes a programmable circuit system 1912. The programmable circuit system 1912 shown in the example is hardware. For example, the programmable circuit system 1912 can be implemented by one or more integrated circuits, logic circuits, FPGAs, microprocessors, CPUs, GPUs, DSPs, or microcontrollers from any desired family or manufacturer. The programmable circuit system 1912 can be implemented by one or more semiconductor-based (e.g., silicon-based) devices.
[0156] The programmable circuit system 1912 of the example shown includes local memory 1913 (e.g., cache, registers, etc.). The programmable circuit system 1912 of the example shown communicates via bus 1918 with main memories 1914 and 1916, which include volatile memory 1914 and non-volatile memory 1916. Volatile memory 1914 may be implemented by one or more synchronous dynamic random access memory (SDRAM), dynamic random access memory (DRAM), RAMBUS® dynamic random access memory (RDRAM®), or any other type of RAM device. Non-volatile memory 1916 may be implemented by flash memory or one or a combination of any other desired type of memory device. Access to the main memories 1914 and 1916 of the example shown is controlled by a memory controller 1917. In some examples, the memory controller 1917 may be implemented by one or more integrated circuits, logic circuits, microcontrollers, or any other type of circuit system from any desired family or manufacturer to manage data flow to and from the main memories 1914 and 1916.
[0157] The programmable circuit system platform 1900 shown in the example also includes an interface circuit system 1920. The interface circuit system 1920 can be implemented in hardware according to any type of interface standard, such as an Ethernet interface, a Universal Serial Bus (USB) interface, a Bluetooth® interface, a Near Field Communication (NFC) interface, a Peripheral Component Interconnect (PCI) interface, or a Peripheral Component Interconnect High Speed (PCIe) interface.
[0158] In the illustrated example, one or more input devices 1922 are connected to the interface circuit system 1920. The input devices 1922 allow a user (e.g., a human user, machine user, etc.) to input one or a combination of data or commands into the programmable circuit system 1912. The input devices 1922 may be implemented by, for example, a battery cell, a monitor circuit, an excitation source, or another controller device, or a combination thereof.
[0159] One or more output devices 1924 are also connected to the interface circuitry 1920 of the illustrated example. The output devices 1924 may be implemented by, for example, a battery cell, a monitor circuit, a trigger source, or another controller device, or a combination thereof. Therefore, the interface circuitry 1920 of the illustrated example includes one or a combination of a graphics driver card, a graphics driver chip, or a graphics processor circuitry system such as a GPU.
[0160] The interface circuit system 1920 of the example shown also includes communication devices, such as one or a combination of a transmitter, receiver, transceiver, modem, residential gateway, wireless access point, or network interface, to facilitate the exchange of data with external machines (e.g., any kind of computing device) via network 1926. Communication can be carried out via, for example, Ethernet connection, digital subscriber line (DSL) connection, telephone line connection, coaxial cable system, satellite system, out-of-line-of-sight wireless system, line-of-sight wireless system, cellular telephone system, optical connection, etc.
[0161] The programmable circuit system platform 1900 shown in the example also includes one or more mass storage disks or devices 1928 for storing one or more of firmware, software, or data. Examples of such mass storage disks or devices 1928 include one or more magnetic storage devices (e.g., floppy disks, drives, HDDs, etc.), optical storage devices (e.g., Blu-ray discs, CDs, DVDs, etc.), RAID systems, or solid-state storage disks or devices, such as flash memory devices and SSDs.
[0162] It can be by Figure 15-18 The machine-readable instructions 1932 implemented by the machine-readable instructions can be stored in one or a combination of the following: mass storage device 1928, volatile memory 1914, non-volatile memory 1916, or at least one non-transitory computer-readable storage medium such as a removable CD or DVD.
[0163] although Figure 6 The implementation is shown in the figure. Figure 1 The example method of WBMS 100, but Figure 6 One or more of the elements, processes, or devices shown may be combined, divided, rearranged, omitted, removed, or implemented in any other way. Furthermore, the battery controller device 102-1, main device 104, auxiliary device 106, BQ circuit 502, excitation source 602, BQ packaging level device 604, or more generally... Figure 6 The example WBMS 100 can be implemented solely by hardware, or by a combination of hardware, software, and firmware. Therefore, for example, the battery controller device 102-1, main device 104, auxiliary device 106, BQ circuit 502, excitation source 602, BQ package-level device 604, or more generally, the example WBMS 100, can be implemented by a programmable circuit system in conjunction with one or more machine-readable instructions (e.g., firmware or software), processor circuit system, analog circuitry, digital circuitry, logic circuitry, programmable processor, programmable microcontroller, graphics processing unit (GPU), digital signal processor (DSP), ASIC, programmable logic device (PLD), or field-programmable logic device (FPLD) such as FPGA. Furthermore, Figure 6Example WBMS 100 may contain one or more components, processes, or devices as Figure 6 The elements, processes, and apparatus shown may be supplements or alternatives to those shown, or may include any or all of more than one of the shown elements, processes, and apparatuses.
[0164] This indicates that it can be executed by a programmable circuit system to implement and / or instantiate. Figure 6 The example machine-readable instructions or representations of WBMS 100 can be executed by a programmable circuit system to implement and / or instantiate them. Figure 6 The flowchart of the example operation of WBMS 100 is in Figure 15-18 As shown below. Machine-readable instructions can be one or more executable programs or portions of one or more executable programs that are executed by a programmable circuit system, for example, as illustrated below. Figure 19 The programmable circuit system 1912 shown in the example programmable circuit system platform 1900 can be one or more functions or functional parts that will be executed by the example programmable circuit system (e.g., FPGA). In some examples, machine-readable instructions cause operations, tasks, etc., to be performed or executed automatically in the real world. As used herein, “automatic” means without human intervention.
[0165] The program may be embodied in instructions (e.g., software and / or firmware) stored on one or more non-transitory computer-readable and / or machine-readable storage media, such as one or a combination of the following: cache memory, magnetic storage devices or disks (e.g., floppy disks, hard disk drives (HDDs), etc.), optical storage devices or optical discs (e.g., Blu-ray discs, optical discs (CDs), digital versatile optical discs (DVDs), etc.), redundant arrays of independent disks (RAID), registers, ROM, solid-state drives (SSDs), SSD memory, non-volatile memory (e.g., electrically erasable programmable read-only memory (EEPROM), flash memory, etc.), volatile memory (e.g., any type of random access memory (RAM), etc.), or any other storage device or storage disk. The instructions on the non-transitory computer-readable and / or machine-readable media may be programmed or executed by a programmable circuit system located in one or more hardware devices, but the entire program or a portion thereof may alternatively be executed or instantiated or embodied in dedicated hardware by one or more hardware devices other than the programmable circuit system. Machine-readable instructions may be distributed across multiple hardware devices or executed by two or more hardware devices (e.g., server and client hardware devices). For example, client hardware devices may be implemented by end-user client hardware devices (e.g., hardware devices associated with human and / or machine users) or by an intermediate client hardware device gateway (e.g., a radio access network (RAN)) that facilitates communication between the server and the end-user client hardware devices. Similarly, non-transitory computer-readable storage media may contain one or more media. Furthermore, although the example programs are for reference only... Figure 15-18The flowcharts shown illustrate methods of WBMS 100, but many other implementation examples can be used alternatively. For example, the execution order of the flowchart blocks can be changed, and some of the described blocks can be altered, eliminated, or combined. Additionally or alternatively, any or all of the flowchart blocks can be implemented by one or more hardware circuits (e.g., processor circuitry, integrated analog and / or digital circuitry, FPGA, ASIC, comparator, operational amplifier, logic circuitry, etc.) configured to perform the corresponding operation without executing software or firmware. Programmable circuitry can be distributed across different network locations or local to one or more hardware devices (e.g., a single-core processor (e.g., a single-core CPU), a multi-core processor (e.g., a multi-core CPU, XPU, etc.)). As used herein, programmable circuitry includes any type of circuitry that can be programmed to perform the desired function, such as one or a combination of a CPU or FPGA. A programmable circuit system may include: one or more CPUs and / or one or more FPGAs located in the same package (e.g., the same integrated circuit (IC) package or in two or more separate housings); one or more CPUs or FPGAs in a single machine; one or more CPUs or FPGAs distributed across multiple servers in a server rack; or multiple processors distributed across one or more server racks. Alternatively or additionally, in any context as explained above, a programmable circuit system may include a programmable logic device (PLD), a general-purpose array logic (GAL) device, a programmable array logic (PAL) device, a complex programmable logic device (CPLD), a simple programmable logic device (SPLD), a microcontroller (MCU), a system-on-a-chip (PSoC), or any combination thereof.
[0166] The machine-readable instructions described herein can be stored in one or more of the following formats: compressed format, encrypted format, segmented format, compiled format, executable format, and encapsulated format. The machine-readable instructions described herein can be stored as data (e.g., computer-readable data, machine-readable data, one or more bits (e.g., one or more computer-readable bits, one or more machine-readable bits, etc.), bit streams (e.g., computer-readable bit streams, machine-readable bit streams, etc.)) or data structures (e.g., portions of instructions, code, representations of code, etc.), which can be used to create, manufacture, or generate machine-executable instructions. For example, machine-readable instructions can be segmented and stored on one or more storage devices, disks, or computing devices (e.g., servers) located in the same or different locations (e.g., in the cloud, at an edge device, etc.) within a network or network set. Machine-readable instructions may require one or more of the following processes: installation, modification, adaptation, updating, combination, supplementation, configuration, decryption, decompression, decapsulation, allocation, reassignment, compilation, etc., so that they can be directly read, interpreted, or executed by computing devices or other machines. For example, machine-readable instructions may be stored in multiple parts, which may be compressed, encrypted, or stored on separate computing devices, wherein the parts, when decrypted, decompressed, or combined, form a set of one or more computer-executable or machine-executable instructions for implementing one or more functions or operations that may together form, for example, the program described herein.
[0167] In another example, machine-readable instructions may be stored in a state readable by a programmable circuit system, but require the addition of libraries (e.g., dynamic link libraries (DLLs)), software development kits (SDKs), application programming interfaces (APIs), etc., to execute the machine-readable instructions on a particular computing device or another device. In another example, it may be necessary to configure the machine-readable instructions or corresponding programs (e.g., store settings, input data, record network addresses, etc.) before they can be fully or partially executed. Therefore, as used herein, machine-readable, computer-readable, or machine-readable media may contain one or a combination of instructions or programs, regardless of the specific format or state of the machine-readable instructions or programs.
[0168] The machine-readable instructions described in this article can be represented by any past, present, or future instruction language, scripting language, programming language, etc. For example, machine-readable instructions can be represented using any of the following languages: C, C++, Java, C-Sharp, Perl, Python, JavaScript, Hypertext Markup Language (HTML), Structured Query Language (SQL), Swift, etc.
[0169] As mentioned above, Figure 15-18Example operations can be implemented using executable instructions (e.g., computer-readable and / or machine-readable instructions) stored on one or more non-transitory computer-readable or machine-readable media. As used herein, the terms non-transitory computer-readable medium, non-transitory computer-readable storage medium, non-transitory machine-readable medium, and non-transitory machine-readable storage medium are explicitly defined as including any type of computer-readable storage device or disk, excluding propagation signals and transmission media. Examples of such non-transitory computer-readable media, non-transitory computer-readable storage media, non-transitory machine-readable media, or non-transitory machine-readable storage media include one or more optical storage devices, magnetic storage devices, HDDs, flash memory, read-only memory (ROM), CDs, DVDs, caches, any type of RAM, registers, or any other storage device or disk in which information is stored for any duration (e.g., extended time period, permanent, transient, for temporary buffering, for caching information). As used herein, the terms "non-transitory computer-readable storage device" and "non-transitory machine-readable storage device" are defined as comprising any physical (mechanical, magnetic, electromechanical, or electrical) hardware designed to retain information for a period of time, excluding the propagation of signals and the transmission medium. Examples of non-transitory computer-readable storage devices or non-transitory machine-readable storage devices include one or a combination of the following: any type of random access memory, any type of read-only memory, solid-state memory, flash memory, optical disk, magnetic disk, disk drive, or redundant array of independent disks (RAID) system. As used herein, the term "device" refers to a physical structure, such as one or a combination of the following: mechanical, electromechanical, or electrical equipment, hardware, or circuitry that may or may not be configured to execute computer-readable instructions, machine-readable instructions, etc., or that may or may not be manufactured to execute computer-readable instructions, machine-readable instructions, etc.
[0170] "Comprising" and "including" (and all their forms and tenses) are used herein as open-ended terms. Therefore, whenever a claim uses any form of "comprising" or "including" (e.g., includes, encompassing, including, having, etc.) as a preamble or in any type of claim statement, additional elements, items, etc., may be present without exceeding the scope of the corresponding claim or statement. As used herein, the phrase "at least" is open-ended when used as a transitional term, for example, in a claim preamble, in the same way as the terms "comprising" and "including". For example, the term "and / or" when used in the form of, for example, A, B, and / or C, refers to any combination or subset of A, B, C, such as (1) only A, (2) only B, (3) only C, (4) A and B, (5) A and C, (6) B and C, or (7) A and B and C. As used herein in the context of describing structures, components, projects, objects, and / or things, the phrase “at least one of A and B” refers to an implementation that includes any of the following: (1) at least one A; (2) at least one B; or (3) at least one A and at least one B. Similarly, as used herein in the context of describing structures, components, projects, objects, and things, the phrase “at least one of A or B” refers to an implementation that includes any of the following: (1) at least one A; (2) at least one B; or (3) at least one A and at least one B. As used herein in the context of describing the execution or conduct of processes, instructions, actions, activities, etc., the phrase “at least one of A and B” refers to an implementation that includes any of the following: (1) at least one A; (2) at least one B; or (3) at least one A and at least one B. Similarly, as used herein in the context of describing the execution or conduct of processes, instructions, actions, activities, etc., the phrase “at least one of A or B” refers to an implementation that includes any of the following: (1) at least one A; (2) at least one B; or (3) at least one A and at least one B.
[0171] As used herein, singular references (e.g., "a(a / an)", "first", "second", etc.) do not exclude plurals. As used herein, the term "a(a)" or "an" refers to one or more of the said objects. The terms "a(a)" (or "an"), "one or more", and "at least one" are used interchangeably herein. Furthermore, although listed separately, multiple components, elements, or actions may be implemented by, for example, the same entity or object. And, although individual features may be included in different examples or technical solutions, these features may be combined, and inclusion in different examples or technical solutions does not imply that at least one combination of features is infeasible or disadvantageous.
[0172] As used herein, unless otherwise indicated, a connection reference (e.g., attachment, coupling, connection, and joining) may include an intermediate member between elements referenced by the connection reference between those elements or by at least one of the elements in relative movement. Therefore, a connection reference does not necessarily imply that two elements are directly connected or fixed to each other. As used herein, the statement that any part is in “contact” with another part is defined to mean that there is no intermediate part between the two parts.
[0173] Unless otherwise specifically stated, this document uses descriptive terms such as “first,” “second,” and “third” without intending or otherwise indicating priority, physical order, arrangement, or any sorting in the list, but solely as markers or at least one of arbitrary names to distinguish elements for ease of understanding the described examples. In some examples, the descriptive term “first” may be used to refer to an element in the detailed description, while the same element may be referred to in the claims by different descriptive terms such as “second” or “third.” In such cases, such descriptive terms are used only to distinguish those elements within the context of discussion (e.g., within the claims), in which context the elements may, for example, originally share the same name.
[0174] As used herein, recognizing the variations that may occur in real-world applications, the terms “approximately” and “about” are used to modify objects / values. For example, “approximately” and “about” may modify dimensions that may be imprecise due to at least one of manufacturing tolerances or other real-world defects. For example, unless otherwise specified herein, “approximately” and “about” may indicate that such dimensions are within a tolerance of + / - 10%.
[0175] As used herein, the phrase “communication” includes variations thereof that cover one or a combination of direct communication or indirect communication through one or more intermediate components, and does not require direct physical (e.g., wired) communication or continuous communication, but also includes selective communication carried out at at least one of periodic intervals, predetermined intervals, non-periodic intervals or one-off events.
[0176] As used herein, a “programmable circuit system” can be understood to include: (i) one or more special-purpose circuits (e.g., application-specific integrated circuits (ASICs)) configured to perform specific operations and including one or more semiconductor-based logic devices (e.g., electrical hardware implemented by one or more transistors), or (ii) one or more general-purpose semiconductor-based circuits that can be programmed with instructions to perform one or more specific functions or operations and including one or more semiconductor-based logic devices (e.g., electrical hardware implemented by one or more transistors). Examples of programmable circuit systems include programmable microprocessors, such as a central processing unit (CPU) capable of executing first instructions to perform one or more operations or functions; a field-programmable gate array (FPGA) programmable with second instructions to configure or construct at least one of the FPGAs, thereby instantiating one or more operations or functions corresponding to the first instructions; a graphics processing unit (GPU) capable of executing first instructions to perform one or more operations or functions; a digital signal processor (DSP) capable of executing first instructions to perform one or more operations or functions; an XPU; a network processing unit (NPU); one or more microcontrollers capable of executing first instructions to perform one or more operations or functions; or an integrated circuit, such as an application-specific integrated circuit (ASIC). For example, an XPU can be implemented by a heterogeneous computing system that includes a variety of programmable circuit systems (e.g., one or more FPGAs, one or more CPUs, one or more GPUs, one or more NPUs, one or more DSPs, etc., and any combination thereof) and configuration technologies (e.g., application programming interfaces (APIs)) that can assign computing tasks to any one or more of the various types of programmable circuit systems that are suitable and can be used to perform the computing tasks.
[0177] In this description, the term "coupled" may encompass a connection, communication, or signaling path that enables the functional relationship to be consistent with this specification. For example, if device A generates a signal to control device B to perform an action, then: (a) in a first example, device A is coupled to device B via a direct connection; or (b) in a second example, device A is coupled to device B via an intermediate component C, provided that the intermediate component C does not alter 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.
[0178] A device “configured” to perform a task or function may be configured (e.g., programmed or hardwired at least) during manufacturing by the manufacturer to perform at least one of the following: performing the function, or configured (or reconfigurable) by the user after manufacturing to perform the function or other additional or alternative functions. Configuration may be performed by at least one of firmware or software programming of the device, by at least one of the construction or layout of the device’s hardware components and interconnects, or by a combination thereof.
[0179] As used herein, the terms “terminal,” “node,” “interconnect,” “pin,” and “lead” are used interchangeably. Unless otherwise specified, these terms are generally used to refer to interconnects or terminals between device elements, circuit elements, integrated circuits, devices, or other electronic or semiconductor components.
[0180] In the specification and claims, the described "circuit system" may comprise one or more circuits. A circuit or device described herein as including certain components may conversely be adapted to couple to components used to form the described circuit system or device. For example, a structure described as comprising one or more semiconductor elements (e.g., transistors), one or more passive elements (e.g., one or a combination of resistors, capacitors, or inductors), or one or more sources (e.g., voltage sources and / or current sources) may substantially comprise only a semiconductor element within a single physical device (e.g., at least one in a semiconductor die or integrated circuit (IC) package) and may be adapted to couple to at least some of said passive elements or sources to form the described structure during or after manufacturing, for example, by an end user or a third party.
[0181] The circuits described herein are reconfigurable to include alternative components to provide functionality at least partially similar to that available before the component replacement. Unless otherwise stated, components shown as resistors generally represent one or more elements that are coupled in series or in parallel to provide a certain amount of impedance represented by the resistor shown. For example, a resistor or capacitor shown and described herein as a single component can actually be multiple resistors or capacitors respectively coupled in parallel between the same nodes. Conversely, a resistor or capacitor shown and described herein as a single component can be multiple resistors or capacitors respectively coupled in series between the same two nodes as a single resistor or capacitor. While some elements in the described examples are included in the integrated circuit, and others are outside the integrated circuit, in other example embodiments, additional or fewer features may be incorporated into the integrated circuit. Additionally, some or all features shown as located outside the integrated circuit may be included in the integrated circuit, and some features shown as located inside the integrated circuit may be incorporated outside the integrated circuit. As used herein, the term "integrated circuit" means one or more circuits that are: (i) incorporated in / on a semiconductor substrate; (ii) incorporated in a single semiconductor package; (iii) incorporated in the same module; or (iv) incorporated in / on the same printed circuit board.
[0182] As can be understood from the foregoing, this document describes example systems, apparatuses, articles, and methods for performing EIS measurements with high accuracy, independent of system-level latency and supporting stringent thermal runaway notification standards. The described systems, apparatuses, articles, and methods synchronize battery measurements and adjust internal clock signals based on reference signals composed of GPIO switching, and improve the efficiency of using computing devices by utilizing RF cores that are separate from and independent of system-level computing resources to transmit GPIO switching. The described systems, apparatuses, articles, and methods also relate to one or more improvements in the operation of machines such as computers or other electronic, electromechanical, or mechanical devices.
Claims
1. An apparatus comprising: A wireless receiver that can be configured to receive packets; Programmable circuits; as well as A communication circuit coupled to the wireless receiver and the programmable circuit, wherein the communication circuit is configurable to: Identify a portion of the package; and In response to the identification of the portion of the package, the device sends a first wired signal to the battery monitor circuitry.
2. The apparatus of claim 1, wherein, in order to identify the portion of the packet, the communication circuit is configured to identify a synchronization frame delimiter in the packet.
3. The apparatus of claim 1, wherein, in order to identify the portion of the package, the communication circuit is configured to identify the start portion of the package.
4. The apparatus of claim 1, wherein the communication circuitry is configured to cause the apparatus to send the first wired signal to prompt the battery monitor circuitry to perform a battery measurement.
5. The apparatus of claim 4, wherein the communication circuitry is configured to send the first wired signal to prompt the battery monitor circuitry to perform the measurement of the battery upon receipt of the first wired signal.
6. The apparatus of claim 1, wherein the communication circuitry is configured to identify the portion of the packet and enable the apparatus to transmit the first wired signal independently of software executed by the programmable circuitry.
7. The apparatus according to claim 6, The wireless receiver is configured to receive signals that encode the packet. The communication circuitry is configured to demodulate the signal received by the wireless receiver, and The programmable circuitry described therein can be configured to extract data from the demodulated signal.
8. The apparatus of claim 1, wherein the programmable circuitry is configured to send a second wired signal to the battery monitor circuitry in response to receiving the packet.
9. The apparatus of claim 8, wherein the programmable circuitry is configured to transmit the second wired signal via a serial peripheral interface.
10. The apparatus of claim 9, wherein the communication circuitry is configured to transmit the first wired signal via a general-purpose input / output interface.
11. The apparatus of claim 1, wherein the communication circuit is configured to: Generate a first timestamp indicating the time of receipt of the portion of the packet; and The first timestamp is reported to the programmable circuit.
12. The apparatus of claim 11, wherein the programmable circuitry is configured to: Extract the reference timestamp from the package; Compare the reference timestamp with the first timestamp; and The internal clock is adjusted in response to comparing the reference timestamp with the first timestamp.
13. The apparatus according to claim 1, The device described is an auxiliary wireless device in a battery management system, and The wireless receiver is configured to receive the packets from the master wireless device in the battery management system as downlink communication.
14. An apparatus comprising: A wireless receiver that can be configured to receive packets; Programmable circuits; as well as A communication circuit coupled to the wireless receiver and the programmable circuit, wherein the communication circuit is configurable to: In response to the packet, a timer is set; and The device sends a first wired signal to the battery monitor circuit when the timer expires.
15. The apparatus of claim 14, wherein the communication circuitry is configured to cause the apparatus to send the first wired signal to prompt the battery monitor circuitry to perform a battery measurement upon receipt of the first wired signal.
16. The apparatus of claim 14, wherein the communication circuitry is configured to set the timer and enable the apparatus to transmit the first wired signal independently of software executed by the programmable circuitry.
17. The apparatus of claim 14, wherein the programmable circuitry is configured to send a second wired signal to the battery monitor circuitry via a serial peripheral interface in response to receiving the packet.
18. An apparatus comprising: A wireless transmitter that can be configured to transmit downlink packets; Programmable circuits; as well as A communication circuit coupled to the wireless transmitter and the programmable circuit, wherein the communication circuit is configurable to: After the transmission of the downlink packet, a timer is set in response to a message from the programmable circuit; and The device sends a wired signal to the battery monitor circuit when the timer expires.
19. The apparatus of claim 18, wherein the communication circuitry is configured to send the wired signal to prompt the battery monitor circuitry to perform a battery measurement upon receipt of the wired signal.
20. The apparatus of claim 18, wherein the communication circuitry is configured to set the timer and enable the apparatus to transmit the wired signal independently of software executed by the programmable circuitry.
Citation Information
Patent Citations
Multiple primary nodes for wireless battery management system robustness
US20240069110A1
Hierarchical wireless battery management system
US20250008491A1
Methods and apparatus to determine communication schedules for wireless battery systems
US20250039859A1
Scheduling for multiple primary nodes
US20250274000A1
Time synchronization in wireless battery management systems
US20260163088A1
