Hierarchical wireless battery management system

Abstract

In one example, the method includes, in a superframe (402A), receiving a first downlink (406A) on a first channel at a radio head node (306.1) in the WBMS from a radio master node (302), where the radio head node is the head node of a subcluster of one or more radio devices (308). The method includes, in a superframe, transmitting a second downlink (408) on a second channel from the radio head node to each of the one or more radio devices; in a superframe, receiving an uplink (420) on a second channel at the radio head node from each of the one or more radio devices; and in a superframe, transmitting an aggregated uplink (424) from the radio head node to the radio master node on a first channel, where the aggregated uplink includes data from each of the one or more radio devices.

Description

Technical Field

[0001] Modern vehicles may include multiple battery cells. Information related to the cells, such as temperature, voltage, and other indicators of cell state and health, can be monitored for the safety of the vehicle and to ensure proper operation. In conventional wired battery management systems, rechargeable batteries are managed by circuit elements for safe and efficient battery operation. Using a wired communication interface, a main microcontroller (main node or master node) is connected to each battery module (secondary node), and each battery module is connected to the remaining battery modules in a daisy-chain manner. In a wired communication interface, the main microcontroller cannot monitor and control all parallel battery modules without complex wiring. This wiring makes the repair and replacement of individual battery cells more difficult and, importantly, increases the weight and volume of the entire system.

[0002] A wireless connection between the battery module and the microcontroller makes the management of the battery module more flexible and the repair easier. In a wireless battery management system (WBMS), the microcontroller monitors each battery module and communicates with the battery module using a wireless communication interface. The main microcontroller controls all battery modules using the WBMS protocol. The wireless communication interface is susceptible to wireless communication channel bandwidth fluctuations, interference, and / or other problems, which may prevent proper monitoring and management in the WBMS.

Summary of the Invention

[0003] In accordance with at least one example described herein, a method includes, in a superframe, a radio head node in a WBMS receiving a first downlink on a first channel from a radio master node, the radio head node being the head node of a subcluster of one or more radio devices. This method also includes, in a superframe, a second downlink on a second channel from the radio head node to each of the one or more radio devices in the subcluster. This method also includes, in a superframe, receiving uplinks from each of the one or more radio devices at the radio head node on the second channel. This method also includes, in a superframe, an aggregated uplink from the radio head node to the radio master node on the first channel, the aggregated uplink containing data from each of the one or more radio devices in the subcluster.

[0004] In accordance with at least one example described herein, the system includes a wireless head node in the WBMS, the wireless head node being the head node of a subcluster of one or more wireless devices. The wireless head node is configured in the superframe to receive a first downlink on a first channel from the wireless master node. The wireless head node is also configured in the superframe to transmit a second downlink on a second channel to each of the one or more wireless devices in the subcluster. The wireless head node is also configured in the superframe to receive uplinks from each of the one or more wireless devices on the second channel. The wireless head node is also configured in the superframe to transmit aggregated uplinks to the wireless master node on the first channel, the aggregated uplinks containing data from each of the one or more wireless devices in the subcluster.

[0005] In accordance with at least one example described herein, the system includes a first radio head node in the WBMS, the first radio head node being the head node of a subcluster of one or more radio devices. The first radio head node is configured in the superframe to receive a first downlink from a radio master node on a first channel. The first radio head node is also configured in the superframe to transmit a second downlink on the configured channel to each of the one or more radio devices in the subcluster. The first radio head node is configured to wait for the second radio head node to transmit a third downlink on the configured channel. The first radio head node is also configured in the superframe to receive uplinks from each of the one or more radio devices on a second channel. The first radio head node is configured in the superframe to transmit aggregated uplinks to the radio master node on the first channel, the aggregated uplinks containing data from each of the one or more radio devices in the subcluster. [Brief explanation of the drawing]

[0006] [Figure 1] This is a perspective view of illustrative systems, such as those found in automobiles, including wireless battery management systems (WBMS), following various examples.

[0007] [Figure 2A] This is an example of a WBMS following various examples.

[0008] [Figure 2B] This is an example of a WBMS following various examples.

[0009] [Figure 3] This is a hierarchical WBMS block diagram following various examples.

[0010] [Figure 4A] This is a block diagram of a superframe structure following various examples.

[0011] [Figure 4B] It is a block diagram of a superframe structure according to various examples.

[0012] [Figure 5] It is a superframe structure for network formation according to various examples.

[0013] [Figure 6] It shows data channels and configuration channels according to various examples.

[0014] [Figure 7A] It is an alternative superframe structure according to various examples.

[0015] [Figure 7B] It is an alternative superframe structure according to various examples.

[0016] [Figure 8A] It is a superframe structure for network formation according to various examples.

[0017] [[ID=-38]] [Figure 8B] It is a superframe structure for network formation according to various examples. <000008~> ...

[0018] [Figure 9A] It is a superframe structure for network formation according to various examples.

[0019] [Figure 9B] ... It is a superframe structure for network formation according to various examples.

[0020] [Figure 10A] It is a superframe structure for network formation according to various examples.

[0021] Note: There seems to be an issue with the tags in the original text. For example, tag has an incorrect format <000008~>. It should be something like for proper translation consistency. I've translated it as best as possible with the given text. [Figure 10B] This is a superframe structure for network formation following various examples.

[0022] [Figure 11A] This is a superframe structure for network formation following various examples.

[0023] [Figure 11B] This is a superframe structure for network formation following various examples.

[0024] [Figure 12A] This is a keep-alive action following various examples.

[0025] [Figure 12B] This is a keep-alive action following various examples.

[0026] [Figure 13] This is a flowchart illustrating methods for hierarchical network operation of WBMS, following various examples.

[0027] In drawings, the same reference number or other reference symbols are used to refer to the same or similar (functional and / or structural) features. [Modes for carrying out the invention]

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

[0029] A battery management system (BMS) can manage the battery cells of an electronic device in various ways. For example, a BMS can monitor the health of battery cells within an electronic device (e.g., voltage, current, temperature). A BMS can also control various battery cells to manage the amount of power they provide and where that power is delivered within the electronic device. Generally, a BMS includes multiple components, such as multiple battery modules and a controller that manages the battery modules. Each battery module may be coupled with multiple battery cells and may include a battery monitor to monitor those battery cells. Therefore, the battery cells coupled to a battery module provide power to the electronic device, the battery monitor within the battery module monitors the health and operation of the battery cells within that module, and the controller communicates with the battery monitor to ensure that the battery module and its cells operate properly. The controller also communicates with the battery monitor to control the operation of the battery cells, for example, by turning them on / off, redirecting them, or otherwise balancing the power they provide.

[0030] A BMS may incorporate wireless technology to construct a wireless battery management system (WBMS). For example, a primary network node may include or be coupled with a controller, and a secondary network node may include a battery module that controls multiple battery cells. Primary and secondary network nodes (e.g., a master node and end nodes) may communicate wirelessly with each other, for example, using radio frequencies. In some protocols, superframes (SFs) are useful to facilitate wireless communication between primary and secondary network nodes. In an SF, the primary network node first broadcasts downlink communication (or packets) to a number of secondary network nodes. The secondary network nodes then respond sequentially and individually to the primary network node using uplink communication (or packets). Additional detailed examples of WBMS are described in U.S. Patent Application No. 17 / 828,895, filed May 31, 2022, entitled “Efficient Unicast Superframe Communication,” by the same applicant, which is incorporated herein by reference in its entirety. [Patent Document 1] U.S. Patent Application No. 17 / 828,895

[0031] In WBMS, latency issues can arise as the number of nodes increases. A primary network node communicating directly with numerous secondary network nodes receives individual responses sequentially from each secondary network node, and these responses may take a long time to be transmitted to the primary network node. The duration of the Service Stream (SF) increases with the number of nodes. In large networks, some secondary nodes may be outside the communication range of the primary node.

[0032] The examples described herein illustrate a hierarchical WBMS network structure capable of handling a large number of nodes using low latency and one-hop extension. A primary node (also referred to herein as a radio master (WM)) acts as the master node for the entire network of nodes. Secondary nodes are divided into subclusters, each subcluster comprising one or more secondary nodes. A secondary node within each subcluster acts as a radio head (WH) node and acts as the master node for the subcluster to which it belongs. Other secondary nodes within each subcluster are referred herein as radio devices (WDs). In some examples, instead of selecting one of the WDs as the WH, a dedicated WH node may be used within the subcluster. The WM and WH use a master hopping sequence (MHS) to manage the communication channels used by the nodes.

[0033] In the hierarchical system described in this specification, the WM communicates with the WH, and the WH communicates with the WD. In at least some examples, the WM and WD generally do not communicate directly. The WM is within communication range of the WH, and the WH is within communication range of each WD within a subcluster. Subclusters may have the same number of WDs or different numbers of WDs. Several SF structures for managing communication between nodes located within the hierarchical system are described herein.

[0034] In the case of a WBMS with a large number of nodes, latency is reduced by the hierarchical system and SF structure described herein. Throughput is also improved due to the efficient SF structure. In the examples described herein, the number of network restarts can be reduced and power consumption can also be reduced. Furthermore, by using the methods disclosed herein, it may be easier to re-establish communication with WDs.

[0035] Figure 1 is a perspective view of an exemplary system 98, such as an automobile, including a WBMS 100, according to various examples of this specification. In some examples, system 98 is any system, which may include a WMBS for supplying power to one or more components of system 98. As shown in the figure, the WBMS 100 includes a primary network node 102, a battery controller 104, a plurality of secondary network nodes 106, and a plurality of battery cells 108. The primary network node 102 may be a WM, and the secondary network nodes 106 may be WHs and WDs, where the WDs are located in subclusters, and each subcluster has a WH for managing its respective WDs. Figure 1 shows the WHs and WDs as a single stack of secondary network nodes 106, but other drawings of the application (e.g., Figure 3) show network architectures that distinguish between WHs and WDs. Although this disclosure primarily describes communication techniques in relation to wireless systems, these techniques may also be useful for wired systems (e.g., when the connection between nodes 102 and 106 is wired).

[0036] In one example, a primary network node 102 is coupled to a battery controller 104 using a first wired connection 110. In one example, the first wired connection 110 between the primary network node 102 and the battery controller 104 is a universal asynchronous receiver / transmitter (UART), inter-integrated communication (I2C), etc. A warehouse heater (WH) in a secondary network node 106 is wirelessly coupled to a primary network node 102 (e.g., a warehouse heater (WM)). A warehouse heater (WH) and a warehouse drive (WD) in a secondary network node are coupled to a battery cell 108 using a second wired connection 112. Figure 1 shows a single primary network node 102 and a single battery controller 104, but the techniques of this disclosure can also be implemented using other exemplary network architectures having multiple primary / main nodes. An additional detailed example of multiple primary nodes in a WBMS is described in U.S. Patent Application No. 17 / 823,138, filed August 30, 2022, entitled "Multiple Primary Nodes for Robustness of a Wireless Battery Management System," by the same applicant, and is incorporated in its entirety by reference. [Patent Document 2] U.S. Patent Application No. 17 / 823,138

[0037] In one example, WBMS100 provides radio frequency (RF) communication between the primary network node 102 and the secondary network node 106's WH, and between the WH and the WD. In one example, the radio RF communication uses the unlicensed 2.4 GHz Industrial, Scientific, and Medical (ISM) band from 2.4 gigahertz (GHz) to 2.483 GHz, compliant with the Bluetooth Special Interest Group (SIG). In some examples, WBMS100 uses 2 megabits per second (Mbps) Bluetooth Low Energy (BLE) across the physical layer (PHY). The Open Systems Interconnection (OSI) model includes the PHY as a layer for communicating raw bits over a physical medium. In this case, the PHY is free space, and WBMS100 uses it to wirelessly communicate between the primary network node 102 and the secondary network node 106's WH. In one example, the transmit power of WBMS100 is 10 decibels milliwatts (dBm) or less.

[0038] In one example, radio RF communication between the primary network node 102 and the secondary network node 106's WH utilizes frequency hopping and time slot allocation to transmit and receive data across the SF, and similarly RF communication between the WH and their respective WDs. The SF, also called the superframe interval, is a time interval that includes time and frequency allocation for data exchange between the primary network node 102 and the secondary network node 106's WH (and between the WH and the WD), and includes the interframe intervals between these allocations. Frequency hopping involves transmitting an RF signal by rapidly changing the transmission frequency between many distinct frequencies occupying the spectral band. In one example, frequency hopping occurs based on the primary network node 102's linear shift-back register and master identification (ID). The linear shift-back register uses linear bit rotation to indicate the frequency pattern with which the primary network node 102 and the secondary network node 106 communicate. A time slot assignment is a time slot allocated to either the primary network node 102 or one or more secondary network nodes 106 for transmission to either one or more secondary network nodes 106 or the primary network node 102. Time slot assignment is performed in half-duplex mode, with both the primary network node 102 and the secondary network nodes 106 switching between transmit and receive modes depending on the temporal moment identified in the scan / pairing frame of the exchanged data for downlink (DL) / uplink (UL) duration.

[0039] In one example, the WBMS 100 enhances robustness against interference by using Frequency Division Multiple Access (FDMA) to change the frequency on which frames are transmitted between the primary network node 102 and each secondary network node 106 (and between the WH and WD). In another example, the WBMS 100 uses frequency hopping tables, frequency blacklisting, and configured channels to mitigate interference with other radio networks. Frequency hopping is performed in SF units, and during SF, time slot allocation is used for frame exchange. Blacklisting temporarily suspends the use of frequency channels that may be susceptible to interference. Configured channels may be used for scanning, pairing, and negotiating communications between the primary network node 102 and the WH of the secondary network node 106, and between the WH and WD.

[0040] In one example, wireless RF communication between the primary network node 102 and the secondary network node 106 uses 40 channels. A subset of these 40 channels (e.g., channels 37, 38, and 39) is used for system configuration, and the remaining 37 channels are used for data exchange. The WH can also communicate with the WD using configuration channels and data channels. In one example, a single channel may also be used as the configuration channel.

[0041] In one example, the WBMS 100 supports periodic and aperiodic data exchange from the secondary network node 106 to the primary network node 102, and between the WH and WD, using wireless RF communication. The primary network node 102 and the secondary network node 106 use a common data format structure for both periodic and aperiodic data exchange. Periodic data exchange is based on repetitive intervals, while aperiodic data exchange is not. The data format is a description of the rules that data stored in a file must follow. Generally, the more detailed the description of the data format, the easier it is to create verification rules on both the transmitting and receiving sides of the wireless battery management system 100.

[0042] In one example, the primary network node 102 scans the network to obtain a master ID and discovers the secondary network node 106 or the WH of the secondary network node 106. The primary network node 102 scans the network by sending management frames to coordinate media access, wake-up schedules, and clock synchronization within the secondary network node 106. The primary network node 102 also uses management frames to learn about the secondary network node 106 in the network. Initially, the primary network node 102 performs a passive scan to obtain (or confirm) the master ID value currently in use by other nodes and / or devices. Subsequently, the primary network node 102 selects a master ID different from the master ID used by other nodes and / or devices.

[0043] In one example, after the primary network node 102 selects a master ID, the primary network node 102 sends a scan request frame at each SF period as long as there are unconnected secondary network nodes 106. In one example, the primary network node 102 is programmed with the total number of secondary network nodes 106 to be connected to it. After all secondary network nodes 106 have been connected and confirmed, the primary network node 102 does not send any further scan requests. The scan request frame contains information about the structure of the SF, as well as the frame format of the DL slots and UL slots.

[0044] To scan for secondary network node 106, primary network node 102 enters a scan state. In this state, primary network node 102 sends a scan request frame at each SF period. Secondary network node 106 responds to primary network node 102 with a scan response and waits for a pairing request frame from primary network node 102. After secondary network node 106 receives a pairing request, it responds within the same SF in the frequency slot allocated by primary network node 102. In some examples, this exchange takes place within the configured channel. No data exchange occurs in this state. Further details of additional examples of establishing a communication channel are described in U.S. Patent Application Publication No. 2022 / 0332213, filed April 16, 2021, “Wireless Protocol for Battery Management,” and U.S. Patent Application Publication No. 2023 / 0051689, filed August 11, 2021, “Wireless Battery Management System Configuration,” which are incorporated in their entirety by reference. [Patent Document 3] U.S. Patent Application Publication Number 2022 / 0332213 [Patent Document 4] U.S. Patent Application Publication Number 2023 / 0051689

[0045] In one example, the transmit cycle or SF depends on the number of secondary network nodes 106 and / or battery cells 108 in the network. The primary network node 102 determines the SF interval based on the number of secondary network nodes 106, or the number and size of subclusters, as described herein. Given the number of secondary network nodes 106 and / or subclusters, the primary network node 102 estimates the number of DL slots available for transmitting packets to the secondary network nodes 106.

[0046] The WBMS 100 manages the battery cell 108 using the primary network node 102, the battery controller 104, and the secondary network node 106. The primary network node 102 and the secondary network node 106 (e.g., WH) communicate with each other about the status of the battery cell 108. The primary network node 102 and the secondary network node 106 can communicate with each other or between each other using various protocol formats. For example, the primary network node 102 and the secondary network node 106 use the DL protocol format and the UL protocol format, each of which includes a frame control field for communicating battery management information. When the battery cell 108 notifies the secondary network node 106 of its status, the secondary network node 106 communicates to the primary network node 102 (or each WH in the subcluster) that the status exists. The primary network node 102 receives the status notification from the secondary network node 106 (e.g., WH) and warns the battery controller 104 about the status. The battery controller 104 determines the appropriate response to the state and sends a command to the primary network node 102. The primary network node 102 sends a command to the secondary network node 106 (e.g., WH). The WH sends a command to the WD in the subcluster. The secondary network node 106 receives the command to manage the battery cell 108 in response to the state. The secondary network node 106 manages the battery cell 108 in response to the state.

[0047] Figure 2A illustrates an exemplary WBMS 200, which is an example of the wireless battery management system 100 described above. As shown in the figure, the WBMS 200 includes a primary network node 102, a battery controller 104, memory 202, a processor 204, a first secondary network node 206, a first set of battery cells 208, a second secondary network node 210, and a second set of battery cells 212. Additional secondary network nodes 206 and 210 may be included but are not explicitly shown. In one example, the primary network node 102 is a WM, and the secondary network nodes 206 and 210 are WHs. In another example, the primary network node 102 is a WH, and the secondary network nodes 206 and 210 are WDs. In this regard, Figures 2A and 2B provide examples of communication that takes place across the multilevel network architecture described herein. The primary network node 102 includes a memory 202 and a processor 204 configured to perform one or more actions attributed to the primary network node 102 herein by executing code 205 stored in the memory 202. In one example, part of the memory 202 may be non-temporary and part of the memory 202 may be temporary. Secondary network nodes 206, 210 may also include processors and memories. For example, as shown in the figure, the secondary network node 206 includes a processor 262 connected to a memory 264, which stores code 265 that is executable by the processor 262 and performs one or more actions attributed to the secondary network node 206 herein.

[0048] The primary network node 102 (if it is a WM) is connected to the battery controller 104 using a first wired connection 110 and wirelessly connected to each of the secondary network nodes 206 and 210. The first secondary network node 206 is connected to the first set of battery cells 208 using a third wired connection 214 and wirelessly connected to the primary network node 102. The second secondary network node 210 is connected to the second set of battery cells 212 using a fourth wired connection 216 and wirelessly connected to the primary network node 102. Figure 2A does not limit the number of secondary network nodes in the wireless battery management system 200; rather, this naming convention indicates that each secondary network node is connected to multiple battery cells.

[0049] In one example, the primary network node 102 is wirelessly coupled to at least eight secondary network nodes 206, 210. In another example, each of the secondary network nodes 206, 210 can be coupled to at least 16 battery cells using wired connections. In one example, the wireless battery management system 200 includes one primary network node. In another example, the wireless battery management system 200 includes multiple primary network nodes, each network having its own hierarchical structure.

[0050] The WBMS200 manages a first set of battery cells 208 and a second set of battery cells 212 using a primary network node 102, a battery controller 104, memory 202, a processor 204, a first secondary network node 206, and a second secondary network node 210. Instructions in memory 202 instruct the processor 204 to command the primary network node 102 to wirelessly communicate the status of the first set of battery cells 208 and the second set of battery cells 212 with the first secondary network node 206 and the second secondary network node 210. The primary network node 102 and the secondary network nodes 206 and 210 communicate using various protocol formats. For example, the primary network node 102 and the secondary network nodes 206 and 210 use the DL protocol format and the UL protocol format, each of which includes a frame control field for communicating battery management information. When the first set of battery cells 208 notifies the first secondary network node 206 of a certain state, the first secondary network node 206 communicates with the primary network node 102 (or WH) that the state exists. The primary network node 102 (or WH) receives notification of the state from the first secondary network node 206 and warns the battery controller 104 (or WM) of the state. The battery controller 104 determines an appropriate response to the state and sends a command to the primary network node 102. The primary network node 102 transmits the command to the first secondary network node 206 (or WH). The first secondary network node 206 receives a command to manage the first set of battery cells 208 in response to the state of the first set of battery cells 208. The first secondary network node 206 manages the first set of battery cells 208 in response to the state. A similar process can be applied to a second secondary network node 210 when a certain state exists in a second set of battery cells 212. Using a hierarchical structure as described herein, the WM communicates with the WH, and the WH communicates with its respective WD and then relays the response from the WD to the WM.

[0051] Figure 2B shows an example of WBMS250, which is an example of WBMS100 described above. As shown in the figure, WBMS250 includes a first secondary network node 206 (which may be a WD), a first set of battery cells 208, a set of primary network nodes 252 (which may be WHs), memory 254, a processor 256, a first wired connection 258, and a set of battery controllers 260. The set of primary network nodes 252 includes memory 254 and a processor 256. In one example, part of memory 254 may be non-temporary and part of memory 254 may be temporary. In some examples, memory 254 includes executable code 255, which, when executed by the processor 256, causes the processor 256 to perform actions attributed to the primary network nodes 252 as described herein.

[0052] Multiple primary network nodes 252 are coupled to multiple battery controllers 260 using a first wired connection 258 and wirelessly coupled to a secondary network node 206. The first secondary network node 206 is coupled to multiple first battery cells 208 using a wired connection 214 and wirelessly coupled to multiple primary network nodes 252. As shown in Figure 2A, the first secondary network node 206 may include a processor and memory (e.g., processor 262 and memory 264). Figure 2B does not limit the number of secondary network nodes in the wireless battery management system 250. In one example, each of the multiple primary network nodes 252 is wirelessly coupled to at least eight secondary network nodes. In one example, the first secondary network node 206 can be coupled to at least sixteen battery cells using a fourth wired connection 216.

[0053] The WBMS250 manages a first set of battery cells 208 using a plurality of primary network nodes 252, a plurality of battery controllers 260, memory 254, a processor 256, and a first secondary network node 206. Instructions in memory 254 instruct the processor 256 to command the plurality of primary network nodes 252 to wirelessly communicate the status of the first set of battery cells 208 with the first secondary network node 206. The plurality of primary network nodes 252 and the first secondary network node 206 communicate using various protocol formats. For example, the plurality of primary network nodes 252 and the first secondary network node 206 use the DL protocol format and the UL protocol format, each of which includes a frame control field for communicating battery management information. When the first set of battery cells 208 notifies the first secondary network node 206 of a certain state, the first secondary network node 206 notifies the plurality of primary network nodes 252 that the state exists. Multiple primary network nodes 252 receive notifications of their status from the first secondary network node 206 and warn the multiple battery controllers 260 of the status. The multiple battery controllers 260 determine the appropriate response to the status and send commands to the multiple primary network nodes 252. The multiple primary network nodes 252 transmit the commands to the first secondary network node 206. The first secondary network node 206 receives commands to manage the first multiple battery cells 208 in response to the status of the first multiple battery cells 208. The first secondary network node 206 manages the first multiple battery cells 208 in response to the status.

[0054] In one example, the first secondary network node 206 communicates with a first primary network node among a plurality of primary network nodes 252 based on instructions from a master controller (not shown). The first secondary network node 206 can transfer communication from the first primary network node to a second primary network node among the plurality of primary network nodes 252. The first and second primary network nodes communicate with each other to coordinate the transfer of the active connection of the first secondary network node 206 from the first primary network node to the second primary network node. In one example, the first primary network node communicates with the first secondary network node 206, and the second primary network node monitors the status of the first primary network node. This status can indicate whether the first primary network node has power and is operating within normal operating conditions. The first primary network node provides a clock signal to the second primary network node to synchronize the communication. The first primary network node and the second primary network node select different frequencies to communicate with the first secondary network node 206. By selecting different frequencies, interference between multiple primary network nodes 252 and the first secondary network node 206 can be minimized. For example, if the first primary network node loses power or its state deviates from normal operating conditions, the second primary network node can connect to the first secondary network node 206 and supplement communication until the first primary network node can operate normally again.

[0055] Figure 3 is a block diagram of a hierarchical WBMS 300 according to various examples herein. The WBMS 300 includes a WM (Wireless Master) 302, a subcluster 304, a wireless head (WH) 306, and a wireless device (WD) 308. In this example, one WM 302 manages the subcluster 304, but the technology of this disclosure can also be implemented using other network architectures with two or more WMs. The subcluster 304 may be referred to collectively as subcluster 304 or individually as subcluster 304. Four subclusters 304 (304.1, 304.2, 304.3, and 304.N) are shown in the WBMS 300, but any number of subclusters 304 may exist in other examples.

[0056] Each subcluster 304 has a WH306 that manages the subcluster 304. Figure 3 shows four WH306s (WH1, WH2, WH3, and WHN). The WH306s are collectively referred to as WHs306 or individually as WH306. Each WH306 communicates with a WM302 and each WD308 within its subcluster 304. Each subcluster 304 has one or more WD308s that communicate with the WH306s within the subcluster 304. The WD308s may be collectively referred to as WD308 or individually as WD308.

[0057] In this example, WH1306.1 manages WD308.1 to 308.6 in subcluster 304.1. Although subcluster 304.1 is shown to contain six WD308s (e.g., WD308.1 to 308.6), any number of WD308s may exist in subcluster 304 in other examples. Subcluster 304.2 contains WH2 306.2 and WD308.7 to 308.12. Subcluster 304.3 contains WH3 306.3 and WD308.13 to 308.18. Subcluster 304.N contains WHN306.N (where N can be any number) and WD308.19 to 308.24. In some examples, WH306 may also function as a WD308 in addition to the WH communication functions described herein, performing the monitoring and management of battery cells 108 that WD308 performs. However, this monitoring function is not assumed to be in accordance with WH306 in all examples of this disclosure.

[0058] In the examples described herein, when installed in a WBMS, WM302 is within communication range of WH306, and each WH306 is within communication range of each WD308 within its subcluster 304. Subclusters 304 may have the same number of WD308s or different numbers. In this example, six WD308s are shown in each subcluster 304, but other numbers may exist in other examples. As will be discussed later, WM302, WH306, and WD308 may use a master hopping sequence to select a channel for communication. Also, as will be discussed later, various superframe structures for handling communication within the hierarchical WBMS described herein will be discussed later.

[0059] Figures 4A and 4B are block diagrams of superframe structures 400A and 400B according to various examples herein. These superframe structures are referred to as Type 2 structures. Superframe structures 400A and 400B include uplinks (ULs) and downlinks (DLs) for various devices (WM302, WH1 306.1, WH2 306.2, WD2 308.2, and WD14 308.14) shown on the left side of Figures 4A and 4B. The ULs and DLs shown in each row are links that the specific device described on the left sends or receives. For example, the top row of Figures 4A and 4B shows the ULs and DLs related to WM302, which are sent by or received by WM302. Similarly, the bottom row of Figures 4A and 4B shows the ULs and DLs related to WD14 308.14, which are sent by or received by WD14 308.14.

[0060] Superframe structure 400A includes the first superframe 402A, and superframe structure 400B includes the second superframe 402B. Superframe structures 400A and 400B include various ULs and DLs 404-454. These ULs and DLs represent communication between devices within an exemplary WBMS (e.g., WBMS300). Details of each of the ULs and DLs 404-454 are described below.

[0061] The superframe structures 400A and 400B also indicate the channels used by devices within WBMS300 for communication. The first superframe 402A uses channels M1, A1, and B1. The second superframe 402B uses channels M2, A2, and B2. Specific ULs and DLs transmitted on each channel are described later.

[0062] In the WBMS300, the WM302 communicates with the WH306. The WM302 can send commands or requests to the WH306 regarding battery cell information or battery management information. The WH306 receives the commands or requests and transmits them to each WD308 managed by each WH306. The WD308 collects information (if necessary) and responds to the WH306 managing its respective subcluster 304. Each WH306 may then be configured to aggregate the responses from the WD308s within its respective subcluster 304 and transmit the response to the WM302. Thus, the WH306 may be configured to act as an intermediary between the WM302 and the WD308.

[0063] Figures 4A and 4B show examples of processes using superframe structures 400A and 400B. In the first superframe 402A in Figure 4A, WM302 sends DL404 (DL-WM) to each of the WH306 on channel M1. In this case, WH1 306.1 receives DL406A and WH2 306.2 receives DL406B. DL404 may contain a command for WH306 to query the WD308 in each subcluster 304 for information such as the status of the battery cell 108. After WM302 sends this DL404, the WM waits for WH306 to receive a response from the WD308 and provide those responses to WM302. This is indicated in Figure 4A as "WM is not listening" for part of the first superframe 402A.

[0064] In response to DL404, each WH306 sends a DL to the WD308 in its respective subcluster 304. In this example, WH1 306.1 sends DL408 (DL WH1) to WD2-WD7 308. DL408 is transmitted on channel A1. WH1 306.1 communicates with its WD308 in the first superframe 402A using channel A1. WH2 306.2 sends DL410 (DL WH2) to WD9 via WD14 308. DL410 is transmitted on channel B1. WH2 306.2 communicates with its WD308 in the first superframe 402A using channel B1. In this example, each subcluster 304 uses a different channel for communication between the WH306 and WD308 in the subcluster 304.

[0065] Each WD308 receives a DL (408 or 410 in this example) from its respective WH306. Although only WD2 308.2 and WD14 308.14 are shown in Figure 4A, other WD308s operate similarly. WD2 308.2 receives DL412, and WD14 308.14 receives DL414. Each WD308 responds to its respective WH306 with a UL. Here, WD2 308.2 sends UL416 to WH1 306.1 on channel A1. WD14 308.14 sends UL418 to WH2 306.2 on channel B1. Although not shown in Figure 4A, other WD308s also send ULs to their respective WH306s on the appropriate channels.

[0066] After receiving ULs from each WD308 within each subcluster, each WH306 aggregates the information in the ULs from the WD308s within its subcluster and sends the UL to the WM302. Here, WH1 306.1 sends UL424 to the WM302 on channel M1. WH2 306.2 sends UL426 to the WM302 on channel M1. As shown in the diagram, UL424 and 426 are sent at different times on channel M1 and do not interfere with each other. The WM302 receives UL428A to 428D from each WH306 it manages. At this point, the first superframe 402A is completed and the second superframe 402B is started.

[0067] In the second superframe 402B in Figure 4B, the same UL and DL as described for the first superframe 402A are transmitted. The second superframe 402B uses different channels than those used in the first superframe 402A. Channel M2 is used instead of channel M1. Channel A2 is used instead of channel A1, and channel B2 is used instead of channel B1.

[0068] In the second superframe 402B, WM302 sends DL430 (DL-WM) on channel M2 to each of the WH306s. In this case, WH1 306.1 receives DL432A and WH2 306.2 receives DL432B. After WM302 sends this DL430, the WM waits for WH306 to receive responses from WD308 and provide those responses to WM302.

[0069] In response to DL430, each WH306 sends a DL to a WD308 in its respective subcluster 304. In this example, WH1 306.1 sends DL434 (DL WH1) to WD2-WD7 308. DL434 is transmitted on channel A2. WH2 306.2 sends DL436 (DL WH2) to WD9 via WD14 308. DL436 is transmitted on channel B2.

[0070] Each WD308 receives a DL (434 or 436 in this example) from its respective WH306. WD2 308.2 receives DL438, and WD14 308.14 receives DL440. Each WD308 responds to its respective WH306 with a UL. Here, WD2 308.2 sends UL442 to WH1 306.1 on channel A2. WD14 308.14 sends UL444 to WH2 306.2 on channel B2.

[0071] After receiving ULs from each WD308 in the subcluster, each WH306 aggregates the information in the ULs from the WD308s in its subcluster and sends the UL to the WM302. Here, WH1 306.1 sends UL450 to the WM302 on channel M2. WH2 306.2 sends UL452 to the WM302 on channel M2. The WM302 receives UL454A~454D from each WH306 under its control. At this point, the second superframe 402B is completed, and another superframe 402 may be initiated. The next superframe may hop channels again according to the master hopping sequence, and may use channels M3, A3, and B3 for communication.

[0072] Using the channel hopping sequence described herein, channels A and B can be derived from channel M using a set of offsets. For example, channel A can be found by calculating M-2, and channel B can be found by calculating M-4. In other examples, any other offset may be useful. Also, in one example, channel A or channel B may be channel M. As shown in Figures 4A and 4B, if channel A is also channel M, no interference occurs because those channels are not used at the same time in superframe 402. Any channel selection can be used as long as the transmissions on the channels do not collide with each other.

[0073] In the examples provided herein, any suitable process may be used for network formation. In one example, WM302 forms a network with all WH306 in the first phase. In the second phase, each WH306 forms a network with its respective WD308.

[0074] The network topology can be provided by one of two examples. In the first example, WM302 is aware of the network topology before it is formed. Other nodes are informed of the network topology during the scan phase. The network topology is enforced by whitelisting selected nodes that conform to the topology. In this example, only WH306 is allowed to pair with WM302. The paired WH306 receives a list of each WD308 to form subcluster 304. WH306 may be configured to whitelist only the received list of WD308 for subcluster 304 in order to form subcluster 304.

[0075] In the second example, before network formation, each node is programmed with the cluster ID to which it should join. Each WH306 (and WM302) is programmed with the cluster ID to which it will be the master before network formation. Each WM302 is programmed with the cluster ID of each WH306, and each WH306 is programmed with the cluster ID of each WD308 within its subcluster 304. The cluster ID is advertised in the scan request. When a node receives a scan request, it sends a response only if the cluster ID in the request matches.

[0076] Network formation can be carried out in two phases. In the first phase, the WM302 may be configured to perform a passive scan to select its master ID. The WD308 may be configured to refrain from participating in phase 1, which can be enforced by whitelisting in the WM302. The superframe format that can be used is the type 1 format, which will be described later. A scan and pairing are performed for the WH306 to pair with the WM302. In one example, the scan may be performed using the configuration channel. After phase 1 is completed, the WM302 switches the network to a master hopping sequence for the data channel. After the WH306 is paired with the WM302, phase 2 begins.

[0077] In Phase 2, the WM302 coordinates the WH306s to form their respective subclusters 304 through their own scanning and pairing phases. A dedicated hopping sequence is communicated to each paired WH306 for use in the mini-superframe by the WM302 for data exchange. The hopping sequence (described below) can be selected from a set of orthogonal hopping sequences or shift hopping sequences. A superframe type 2 structure may be used throughout for network formation and operation. Three options (options 1, 2, and 3) for network formation are described below. Option 3 introduces an additional superframe type, type 3. Different options may have different network formation speeds, with some options being faster than others. However, faster options may be more complex than slower options.

[0078] Figure 5 shows a Type 1 superframe structure 500 for network formation according to various examples of this specification. The superframe structure 500 includes two superframes 502A and 502B in this example. Three configuration channels 504A, 504B, and 504C are shown in this example. The superframe structure 500 includes DL506 and 512, as well as UL508, 510, 514, and 516.

[0079] In a Type 1 superframe, the duration of the superframe includes one DL slot and N UL slots, where N is the number of WH306s managed by the WM302. A Type 1 superframe may be useful in the scanning and pairing phases of the WH306 described herein. In superframe 502A, the WM302 sends a DL scan request 506 on configuration channel 1 504A. A WH306 may respond on configuration channel 1 504A in superframe 502A. In this example, WH4 sends a UL508 scan response to the WM302. WH2 sends a UL510 scan response to the WM302.

[0080] In superframe 502B, WM302 sends a DL scan request 512 on configuration channel 2 504B. WH306 may respond on configuration channel 2 504B within superframe 502B. In this example, WH5 sends an UL514 scan response to WM302. WH1 sends an UL516 scan response to WM302.

[0081] Figure 6 shows data and configuration channels 600 according to various examples of this specification. Channel 600 may be a Bluetooth Low Energy (BLE) frequency channel in several examples, with the illustrative frequencies shown in Figure 6. This example includes three configuration or advertise channels (602A, 602B, and 602C), which are channels 37, 38, and 39. Channel 604 is a data channel and includes a total of 37 data channels from channels 0 to 36.

[0082] In the examples provided herein, for each subcluster 304, WM302 transmits the master hopping sequence and a unique offset to calculate the channels. The offset for a given subcluster 304 is subtracted from the channel number and folded back in the range [0-36]. This offset also excludes constituent channels 37, 38, and 39. For example, if a section of the master hopping sequence is for non-adjacent channels [5, 27, 0, 16] and the offset for subcluster 304 is 3, then the subcluster follows channels [2, 24, 34, 13], while the MHS follows channels [5, 27, 0, 16]. The offset should be large enough to minimize adjacent channel interference. In this example, WM302 only needs to send the master hopping sequence and offset to WH306.

[0083] In some examples herein, a discrepancy in measurement timing may occur due to the hierarchical structure. For example, WM302 may send a command to WH306 to perform a measurement, and WH306 may send that command to WD308 within each subcluster 304. Thus, WH306 receives the command before WD308. If WH performs the measurement before WD, a discrepancy in measurement timing occurs, where the measurements at each node are not performed simultaneously. Depending on the measurement being performed, this discrepancy may result in inaccurate data. In one example herein, by delaying the command by an appropriate duration (e.g., in software) in WH306, the measurement by WH306 may be performed approximately simultaneously with the measurement by WD308.

[0084] In the examples herein, each WH306 receives data from N WD308s and transfers the aggregated data to the WM302 in its own time slot (e.g., UL424 and 426 in Figure 4A). This time slot may potentially be longer than other time slots. The duration of the aggregated UL time slots (e.g., 424 and 426) is less than N times the duration of the original UL time slots because the WH306 does not need to transfer the entire frame from the WD308s, but only the payload and identification information of each WD308. This thus reduces the net overhead for transferring information from N WD308s compared to a single-tier network.

[0085] Figures 7A and 7B show alternative superframe structures 700A and 700B according to various examples herein. In these examples, WH306 receives DL from WM302 and then sends it back to WM302 before transmitting it to WD308 in their respective subclusters 304. This example has a superframe 702, which is type 2 but is divided into three type 1 superframes (704A, 704B, and 704C). Superframes 704A, 704B, and 704C may have different durations in some examples. Any number of WH306 and WD308 may exist in examples using superframe structures 700A and 700B. Superframe structures 700A and 700B may also be used in other examples described herein.

[0086] In this example, during the Type 1 superframe 704A in Figure 7A, WM302 sends DL706 to WH1 306.1 and WH2 306.2 on channel M1. WH1 306.1 receives DL708A, and WH2 306.2 receives DL708B. WH1 306.1 responds with UL710 on channel M1, and WH2 306.2 responds with UL712 on channel M1. WM302 receives UL714A-714D from all of each WH306 in the cluster. WD308 is not listening during the superframe 704A. UL714A-714D are additional frame transmissions and may not be present in other examples herein.

[0087] During the Type 1 superframe 704B in Figure 7A, WH306 sends DLs to each WD308, and the WD308 responds with ULs. WM302 is not listening at this time. In this example, WH1 306.1 sends DL716 to a WD308 in subcluster 304 on channel A1. WH2 306.2 sends DL718 to a WD308 in subcluster 304 on channel B1. WD2 308.2 receives DL720 on channel A1. WD14 308.14 receives DL722 on channel B1. WD2 308.2 sends UL724 to WH1 306.1 on channel A1. WD14 308.14 sends UL726 to WH2 306.2 on channel B1. Other WD308s (not shown in Figure 7A) may also send ULs to their respective WH306s during the superframe 704B. These aggregated ULs may be longer than other ULs in some cases. WH1 306.1 receives ULs 728A-728F from its WD308. WH2 306.2 receives ULs 730A-730F from its WD308.

[0088] During the Type 1 superframe 704C shown in Figure 7B, the WH306 aggregates ULs from each WD308 and transmits the aggregated ULs to the WM302. First, the WM302 sends DL732 to the WH306. WH1 306.1 receives DL734A, and WH2 306.2 receives DL734B. Each WH306 aggregates ULs from the WD308s in their respective subcluster 304 and transmits those aggregated ULs to the WM302. As previously mentioned, each WH306 may be configured to generate aggregated ULs based on the ULs received from the WD308s in their respective subcluster. WH1 306.1 transmits UL736 to the WM302 on channel M1, and WH2 306.2 transmits UL738 to the WM302 on channel M1. WM302 receives UL740A~740D on channel M1 in Superframe 704C.

[0089] Figures 8A and 8B show superframe structures 800A and 800B for network formation, according to various examples herein. Figures 8A and 8B provide an example of network formation option 1. In option 1, subclusters 304 are formed one by one using a process coordinated by WM302. One subcluster 304 is formed at a time (e.g., by scanning and pairing). A similar scanning and pairing mechanism is used for each subcluster 304 using a configuration channel. Each WH306 may be configured to use a whitelist received from WM302 for admission control of WD308. WH306 in the network formation phase uses only the configuration channel. After the subclusters 304 are formed, they follow their hopping sequence as instructed by WM302. The main cluster also follows a master hopping sequence.

[0090] In this example, in each Type 2 superframe, the corresponding WH306 reports the status of its subcluster 304 formation to the WM302. After a WH306 (e.g., WHN) has completed forming its subcluster 304, the WM302 instructs the next WH306 (e.g., WH(N+1)) to form its own cluster, starting from the next Type 2 superframe. After any subcluster 304 has formed, it switches to its own hopping sequence derived from the master hopping sequence. The subcluster 304 then enters the network operation phase and participates in normal data exchange, as described above with respect to Figures 4A and 4B, for example. After network formation for all subclusters 304 is complete and confirmed by the WM302 from each WH306, all subclusters 304 enter a normal data exchange operation state.

[0091] Superframe structures 800A and 800B illustrate an example of Option 1 network formation. Superframe structure 800A includes superframe 802A, and superframe structure 800B includes superframe 802B, which is a Type 2 superframe. In superframe 802A, WH1 306.1 is in the network formation phase. WH2 306.2 has already completed its network formation and is in the normal data exchange phase. The process begins when WM302 sends DL804 to each WH306 in the cluster. In this example, WH1 306.1 receives DL806A, and WH2 306.2 receives DL806B. DL804 contains instructions that WH1 306.1 is in the scan phase and WH2 306.2 has completed network formation. Other WH306s that have not completed the scan phase wait until WH1 306.1 completes the scan phase. Other WH306s that have completed the scan phase may perform normal data exchange operations, such as WH2 306.2 in this example. DL804 may also include acknowledgments for UL frames from all WH306s.

[0092] Subsequently, WH1 306.1 performs the scan phase. WH1 306.1 sends a scan request DL808 to each WD308 in its respective subcluster 304 on configuration channel 1. As shown in the figure, the WD308 in this subcluster (e.g., WD2 308.2) receives the scan request with DL810. Next, the WD308 in WH1 306.1's subcluster sends individual responses to WH1 306.1 on configuration channel 1. In superframe 802A, WD3 308 sends UL812 to WH1 306.1 and WD5 308 sends UL814 to WH1 306.1. UL812 and 814 are not sent by WD2 308.2, but are shown in the WD2 308.2 line for simplification. WH1 306.1 receives these responses UL816 and 818, respectively. WH1 306.1 aggregates the responses from its WD308 and transmits them to WM302 via UL820 on channel M1. UL820 may indicate that WH1 306.1 is in the scan phase and may include acknowledgments for the last frame from WM302.

[0093] While WH1 306.1 is scanning with superframe 802A, WH2 306.2 is performing normal data exchange with WD308 within its subcluster. WH2 306.2 transmits DL822 on channel B1. In this example, WD308.9~308.14 are in subcluster 304 managed by WH2 306.2. For simplicity, only WH14 308.14 is shown here. Each WD308 in this subcluster 304 receives DLs such as DL824, which WD14 308.14 receives, on channel B1. Each WD308 sends responses such as UL826 from WD14 308.14 to WH2 306.2. WH2 306.2 receives UL828A~828F from the WD308 in subcluster 304 on channel B1. WH2 306.2 aggregates the responses and provides UL830 to WM302 on channel M1. UL830 may indicate that WH2 306.2 has completed its network formation phase and may include aggregated data from WD308 within each subcluster 304. UL830 may also include acknowledgments for the last frame from WM302. In this example, UL832A-832D are received by WM302, but the system may include any number of subclusters 304 and WH306. This terminates superframe 802A.

[0094] In Superframe 802B shown in Figure 8B, the same process as described above for Superframe 802A is performed. In Superframe 802B, WH1 306.1 has not yet completed the scan and pairing phase, so it continues scanning and pairing with the unpaired WD308s in its subcluster 304. WH2 306.2 continues normal data exchange with each of its WD308s.

[0095] WM302 sends DL834 to each WH306 in the cluster on channel M2. In this example, WH1 306.1 receives DL836A and WH2 receives DL836B. DL834 can be the same as DL804 mentioned above.

[0096] WH1 306.1 sends scan request DL838 to each WD308 in its own subcluster 304 on configuration channel 2. As shown in the figure, the WD308s in this subcluster (such as WD2 308.2) receive the scan request with DL840. Subsequently, the WD308s in WH1 306.1's subcluster send individual responses back to WH1 306.1 on configuration channel 2 for WD308s that did not pair with WH1 306.1 in the previous subframe 802. In superframe 802B, WD2 308.2 sends UL842 to WH1 306.1 and WD4 308 sends UL844 to WH1 306.1. WH1 306.1 receives responses UL846 and 848, respectively. WH1 306.1 aggregates the responses from the WD308 and transmits them to the WM302 on channel M2 using the UL850. The UL850 may be the same as the aforementioned UL820.

[0097] While WH1 306.1 is scanning in superframe 802B, WH2 306.2 is performing normal data exchange with WD308s in the subcluster, similar to what is done within superframe 802A. WH2 306.2 transmits DL852 on channel B2. Each WD308 in subcluster 304, managed by WH2 306.2, receives DLs such as DL854 received by WD14 308.14 on channel B2. Each WD308 sends responses such as UL856 from WD14 308.14 to WH2 306.2. WH2 306.2 receives UL858A~858F from the WD308s in subcluster 304 on channel B2. WH2 306.2 aggregates the responses and provides UL860 to WM302 on channel M2. UL860 may be similar to the aforementioned UL830. In this example, UL862A~862D are received by WM302, but the system can include any number of subclusters 304 and WH306. This terminates the superframe 802B. Therefore, Figures 8A and 8B illustrate option 1 for network formation.

[0098] Figures 9A and 9B show superframe structures 900A and 900B for network formation according to various examples herein. Figures 9A and 9B provide an example of network formation option 2. In option 2, a group of subclusters 304 are formed simultaneously, rather than one at a time as in option 1. In option 2, three subclusters 304 may be formed at once using three configuration channels. In other examples, if more configuration channels are available, even more subclusters 304 may be formed at once.

[0099] In Option 2, the formation of subclusters 304 is coordinated by WM302. Each WH306 is instructed by WM302 to use one of the configuration channels, which cycle through with each superframe. For each subcluster 304 within a configuration channel, the same scan and pairing mechanism as described above in Option 1 may be used. The clusters use the master hopping sequence described herein. In each Type 2 superframe, the corresponding WH306 reports the status of their subcluster 304 formation to WM302. After any of the current three subclusters 304 are formed, WM302 instructs a new WH306 or a new set of WH306 to begin network formation. After any subcluster 304 is formed, it switches to its own derived hopping sequence, derived from the master hopping sequence, for normal data exchange. Option 2 operates three times faster than Option 1, but uses the same superframe structure and timing.

[0100] Superframe structures 900A and 900B illustrate an example of network formation for Option 2. Superframe structure 900A includes superframe 902A, and superframe structure 900B includes superframe 902B. These are Type 2 superframes. In superframe 902A, WH1 306.1, WH2 306.2, and WH4 306.4 are in the network formation phase. WH3 306.3 has already completed network formation and is in the normal data exchange phase. In this example, WD308 is not shown, but WH306 communicates with WD308 in its respective subcluster 304, as in Option 1 described above.

[0101] In Option 2, the process begins with a superframe 902A in which WM302 sends DL904s to each WH306 in the cluster. WH1 306.1 receives DL906A, WH2 306.2 receives DL906B, WH3 306.3 receives DL906C, and WH4 306.4 receives DL906D. The DL904 from WM302 includes instructions that WH1 306.1, WH2 306.2, and WH4 306.4 are in the scanning or network formation phase, and that WH3 306.3 has completed network formation. WM302 allocates the selected configuration channels to WH1 306.1, WH2 306.2, and WH4 306.4. WH3 306.3 follows the master hopping sequence. Other WH306s that have not yet formed a network will not transmit until the WM302 assigns them configuration channels.

[0102] During the network formation phase, each WH306 sends a scan request DL to each WD308 in its respective subcluster 304 on its own configuration channel. WH1 306.1 sends DL908 on configuration channel 1, WH2 306.2 sends DL910 on configuration channel 2, and WH4 306.4 sends DL912 on configuration channel 3. Subsequently, each WD308 (not shown) corresponding to each WH306 responds with UL for pairing. In this example, WH1 306.1 receives UL914A and 914B from its WD308, WH2 306.2 receives UL914C and 914D from its WD308, and WH4 306.4 receives UL914E and 914F from its WD308. Then, each WH306 aggregates the ULs it received from its WD308 and sends a UL to WM302 on channel M1. Here, WH1 306.1 sends UL916, WH2 306.2 sends UL918, and WH4 306.4 sends UL920.

[0103] During superframe 902A, WH1 306.1, WH2 306.2, and WH4 306.4 are in the scanning phase, while WH3 306.3 is exchanging normal data with its WD308. WH3 306.3 sends DL922 to its WD308 on channel B1. The WD308 responds to WH3 306.3 on channel B1 using UL924A~924F. WH3 306.3 aggregates the responses from the WD308 and sends UL926 to WM302. UL926 indicates that WH3 306.3 has completed the network formation phase and contains aggregated data from all WD308s in the WH3 306.3 subcluster. WM302 receives UL928A to 928D (one from each WH306 in the cluster), and superframe 902A ends.

[0104] In Superframe 902B shown in Figure 9B, the same process as described above for Superframe 902A is performed. In Superframe 902B, since WH1 306.1, WH2 306.2, and WH4 306.4 have not yet completed the scan and pairing phase, these WH306s continue scanning and pairing with unpaired WD308s within their respective subclusters 304. WH1 306.1, WH2 306.2, and WH4 306.4 may be configured to use a different configuration channel in Superframe 902B than the configuration channel used by each WH in Superframe 902A. WH3 306.3 continues normal data exchange with its respective WD308.

[0105] The Superframe 902B process begins when WM302 sends DL930 to each WH306 in the cluster on channel M2. WH1 306.1 receives DL932A, WH2 306.2 receives DL932B, WH3 306.3 receives DL932C, and WH4 306.4 receives DL932D. DL930 may be the same as DL904 mentioned above.

[0106] During the network formation phase, each WH306 sends a scan request DL to each WD308 in its respective subcluster 304 on its respective configuration channel. WH1 306.1 sends DL934 on configuration channel 2, WH2 306.2 sends DL936 on configuration channel 3, and WH4 306.4 sends DL938 on configuration channel 1. Subsequently, each WD308 (not shown) for each WH306 responds to its respective WH306 with UL for pairing. In this example, WH1 306.1 receives UL940A and 940B from its WD308, WH2 306.2 receives UL940C, 940D, and 940E from its WD308, and WH4 306.4 receives UL940F, 940G, and 940H from its WD308. Subsequently, each WH306 aggregates the ULs it received from its WD308 and transmits them to the WM302 on channel M2. Here, WH1 306.1 sends UL942, WH2 306.2 sends UL944, and WH4 306.4 sends UL946.

[0107] During Superframe 902B, WH1 306.1, WH2 306.2, and WH4 306.4 are in the scan phase, while WH3 306.3 is exchanging data normally with its WD308 (similar to Superframe 902A). WH3 306.3 sends DL948 to its WD308 on channel B2. The WD308 responds to WH3 306.3 on channel B2 with UL950A-950F. WH3 306.3 aggregates the responses from the WD308 and sends UL952 to WM302. WM302 receives UL954A-954D (one from each WH306 in the cluster), and Superframe 902B ends.

[0108] As mentioned above, Option 2 in Figures 9A and 9B shows that the configuration channels are circulated between each superframe 902 for WH306, which is in the network formation phase. Therefore, Figures 9A and 9B describe Option 2 for network formation.

[0109] Figures 10A and 10B show superframe structures 1000A and 1000B for network formation, according to various examples described herein. Figures 10A and 10B show an example of network formation option 3. Option 3 is more complex than options 1 or 2. In option 3, a new superframe type (type 3) is used until all subclusters 304 are formed. Superframe type 3 is similar to type 2, but type 3 contains longer mini-superframes within the superframe than type 2. In type 3, all subclusters 304 are formed simultaneously using a coordination process by WM302. Each WH306 is instructed by WM302 to use one of the configuration channels for each mini-superframe, and the configuration channels cycle through each superframe. After network formation is complete, the network normally switches to superframe type 2 for data exchange. The main cluster follows a master hopping sequence. In each type 3 superframe, all WH306 report the status of subcluster 304 formation to WM302. After WH306 completes the formation of subcluster 304, WH306 switches subcluster 304 to the appropriate hopping sequence within a mini-superframe. After all subclusters 304 have been formed, WM302 switches the network to superframe type 2.

[0110] Superframe structures 1000A and 1000B illustrate an example of Option 3 network formation. Superframe structures 1000A and 1000B include Superframes 1002A and 1002B, which are Type 3 Superframes, respectively. In Superframe 1002A, WH1 306.1, WH2 306.2, WH3 306.3, and WH4 306.4 are in the network formation phase. Although WD308 is not shown in this example, WH306 communicates with WD308 in its respective subcluster 304, similar to Options 1 and 2 described above.

[0111] In Option 3, the process is initiated in Superframe 1002A of Figure 10A by WM302 sending DL1004 to each WH306 in the cluster. WH1 306.1 receives DL1006A, WH2 306.2 receives DL1006B, WH3 306.3 receives DL1006C, and WH4 306.4 receives DL1006D. The DL1004 from WM302 contains information indicating that WH1 306.1, WH2 306.2, WH3 306.3, and WH4 306.4 are in the scan or network formation phase. WM302 allocates the selected configuration and data channels to WH1 306.1, WH2 306.2, WH3 306.3, and WH4 306.4.

[0112] Each WH306 in the network formation phase sends a scan request DL on its respective configuration channel to each WD308 within its subcluster 304. WH1 306.1 sends DL1008 on configuration channel 1, WH2 306.2 sends DL1010 on configuration channel 2, and WH3 306.3 sends DL1012 on configuration channel 3. Since there are four WH306s but only three configuration channels, WH4 306.4 must wait during the waiting period 1014 for a configuration channel to become available. After DL1008, 1010, and 1012 are sent, the configuration channel is released, and WM302 allocates configuration channel 1 to WH4 306.4. Subsequently, WH4 306.4 sends DL1016 to the WD308 within subcluster 304. During the time DL1016 is sent, the other WH306s wait for DL1016 to finish. These waiting periods are indicated as 1018A, 1018B, and 1018C for the first three WH306s.

[0113] After a scan request DL is sent to the WD308, the WD308 responds to each WH306 in a mini-superframe. This response uses the data channel, not the configuration channel. WH1 306.1 uses channel A1, WH2 306.2 uses channel B1, WH3 306.3 uses channel C1, and WH4 306.4 uses channel D1. WH1 306.1 receives ULs 1020 and 1022, WH2 306.2 receives ULs 1024 and 1026, WH3306.3 receives ULs 1028 and 1030, and WH4 306.4 receives ULs 1032 and 1034.

[0114] After each WH306 receives a UL from the WD308, each WH306 aggregates its own response from the WD308 and sends the UL to the WM302 on channel M1. WH1 306.1 sends UL1036, WH2 306.2 sends UL1038, WH3 306.3 sends UL1040, and WH4 306.4 sends UL 1042. The WM302 receives ULs 1044A to 1044D, and superframe 1002A ends.

[0115] Superframe 1002B in Figure 10B operates similarly to superframe 1002A. In this example, since none of the WH306s have completed network formation in superframe 1002A, network formation continues in superframe 1002B.

[0116] In superframe 1002B, the process is initiated when WM302 sends DL 1046 to each WH306 in the cluster. WH1 306.1 receives DL 1048A, WH2 306.2 receives DL 1048B, WH3 306.3 receives DL 1048C, and WH4 306.4 receives DL 1048D. DL1004 from WM302 indicates that WH1 306.1, WH2 306.2, WH3 306.3, and WH4 306.4 are in the scan or network formation phase. WM302 allocates the selected configuration and data channels to WH1 306.1, WH2 306.2, WH3 306.3, and WH4 306.4.

[0117] Each WH306 in the network formation phase sends a scan request DL on its respective configuration channel to each WD308 in its respective subcluster 304. WH1 306.1 sends DL 1050 on configuration channel 2, WH2 306.2 sends DL 1052 on configuration channel 3, and WH3 306.3 sends DL 1054 on configuration channel 1. WH4 306.4 waits for a configuration channel to become available during a waiting period of 1056. After DLs 1050, 1052, and 1054 have been sent, the configuration channel is released and WM302 allocates configuration channel 2 to WH4 306.4. WH4 306.4 then sends DL 1058 to the WD308 in subcluster 304. While DL 1058 is being sent, the other WH306s wait for DL ​​1058 to finish. These standby periods are indicated as 1060A, 1060B, and 1060C for the first three WH306 tubes.

[0118] After the scan request DL is sent to the WD308, the WD308 responds to each WH306 in a mini-superframe. This response uses the data channel, not the configuration channel used in superframe 1002A. In this superframe 1002B, the data channel also cycles, just as the configuration channel cycled. WH1 306.1 uses channel A2, WH2 306.2 uses channel B2, WH3 306.3 uses channel C2, and WH4 306.4 uses channel D2. WH1 306.1 receives ULs 1062 and 1064, WH2 306.2 receives ULs 1066 and 1068, WH3 306.3 receives ULs 1070 and 1072, and WH4 306.4 receives ULs 1074 and 1076.

[0119] After each WH306 receives a UL from the WD308, each WH306 aggregates its own response from the WD308 and sends the UL to the WM302 on channel M2. WH1 306.1 sends UL 1078, WH2 306.2 sends UL 1080, WH3 306.3 sends UL 1082, and WH4 306.4 sends UL 1084. The WM302 receives ULs 1086A to 1086D, and superframe 1002B ends.

[0120] Once any of the WH306s have completed forming a subcluster 304, the WH306s continue to send DL frames on their assigned configuration channels and receive UL frames in the appropriate hopping sequence. This process continues until all subclusters 304 are formed and the WM302 notifies all WH306s to switch to superframe type 2. In some examples, option 3 is more complex than options 1 or 2, but may be faster if the number of subclusters 304 is very large.

[0121] Figures 11A and 11B show superframe structures 1100A and 1100B for network formation, respectively, according to various examples described herein. Figures 11A and 11B are extended examples of network formation option 3, in which a type 3 superframe is used for network formation, and the network then switches to a type 2 superframe for data exchange.

[0122] The superframe structure 1100A in Figure 11A includes superframe 1102A, and the superframe structure 1100B in Figure 11B includes superframe 1102B. Superframe 1102A is a type 3 superframe for network formation. After superframe 1102A, the network is formed, and WM302 switches the network to superframe type 2 for superframe 1102B. In this example, WD308 is not shown, but WH306 communicates with WD308 in its respective subcluster 304 as described above in options 1 and 2.

[0123] In the superframe structure 1100A, superframe 1102A operates similarly to superframe 1002A described above with respect to Figure 10A. The process begins with superframe 1102A, in which WM302 sends DL 1104 to each WH306 in the cluster.

[0124] WH1 306.1 receives DL 1106A, WH2 306.2 receives DL 1106B, WH3 306.3 receives DL 1106C, and WH4 306.4 receives DL 1106D. DL 1104 from WM302 includes an instruction that WH1 306.1, WH2 306.2, WH3 306.3, and WH4 306.4 are in the scan or network formation phase. WM302 allocates the selected configuration and data channels to WH1 306.1, WH2 306.2, WH3 306.3, and WH4 306.4.

[0125] Each WH306 in the network formation phase sends a scan request DL to each WD308 in its respective subcluster 304 on its respective configuration channel. WH1 306.1 sends DL 1108 on configuration channel 1, WH2 306.2 sends DL 1110 on configuration channel 2, and WH3 306.3 sends DL 1112 on configuration channel 3. WH4 306.4 waits for a configuration channel to become available during a waiting period 1114. After DLs 1108, 1110, and 1112 have been sent, the configuration channel is released and WM302 allocates configuration channel 1 to WH4 306.4. WH4 306.4 then sends DL 1116 to the WD308 in subcluster 304. While DL 1116 is being sent, the other WH306s wait for DL ​​1116 to finish. These standby periods are indicated as 1118A, 1118B, and 1118C for the first three WH306 units, respectively.

[0126] After a scan request DL is sent to the WD308, the WD308 responds to each WH306 in a mini-superframe. This response uses the data channel, not the configuration channel. WH1 306.1 uses channel A1, WH2 306.2 uses channel B1, WH3 306.3 uses channel C1, and WH4 306.4 uses channel D1. WH1 306.1 receives ULs 1120 and 1122, WH2 306.2 receives ULs 1124 and 1126, WH3 306.3 receives ULs 1128 and 1130, and WH4 306.4 receives ULs 1132 and 1134.

[0127] After the UL is received by the WH306 from the WD308, each WH306 aggregates its own response from the WD308 and sends the UL to the WM302 on channel M1. WH1 306.1 sends UL 1136, WH2 306.2 sends UL 1138, WH3 306.3 sends UL 1140, and WH4 306.4 sends UL 1142. The WM302 receives ULs 1144A to 1144D, and superframe 1002A ends.

[0128] In this example, network formation is completed after superframe 1102A. WH306 indicates to WM302 that network formation is complete using UL 1136, 1138, 1140, and 1142. Therefore, after receiving UL 1144A-1144D, WM302 switches to superframe type 2 for superframe 1102B. Superframe 1102B operates similarly to the aforementioned type 2 structures, such as superframe structure 400A in Figure 4A.

[0129] In the superframe 1102B of Figure 11B, WM302 sends a request or command to WH306, which then communicates with its respective WD308 to collect information and sends it back to WM302. In this example, WM302 sends DL 1146 to each WH306 on channel M2. WH306.1 receives DL 1148A, WH306.2 receives DL 1148B, WH306.3 receives DL 1148C, and WH306.4 receives DL 1148D. Subsequently, each WH306 communicates with its WD308 (not shown in Figure 11B) by sending a DL on the channel allocated to subcluster 304 by WM302. WH306.1 sends DL 1150 on channel A2, WH306.2 sends DL 1152 on channel B2, WH306.3 sends DL 1154 on channel C2, and WH306.4 sends DL 1156 on channel D2.

[0130] The WD308 responds to the WH306 using ULs as shown here. WH1 306.1 receives ULs 1158A-1158F from its WD308 on channel A2, WH2 306.2 receives ULs 1160A-1160F from its WD308 on channel B2, WH3 306.3 receives ULs 1162A-1162F from its WD308 on channel C2, and WH4 306.4 receives ULs 1164A-1164F from its WD308 on channel D2.

[0131] Each WH306 aggregates the responses from the WD308 and sends a UL to the WM302 on channel M2. WH1 306.1 sends UL 1166, WH2 306.2 sends UL 1168, WH3 306.3 sends UL 1170, and WH4 306.4 sends UL 1172. The WM302 receives ULs 1174A to 1174D, and superframe 1102B ends. Thus, Figures 11A and 11B illustrate how the superframe type 3 structure is used for network formation and the superframe type 2 structure is used for data exchange in WBMS.

[0132] Figures 12A and 12B illustrate keep-alive operation according to various examples described herein. Figure 12A shows a superframe structure 1200A including a complete type 2 superframe 1202A. Figure 12B shows a superframe structure 1200B including a partial type 2 superframe 1202B. Here, the WM302 functions as the master node throughout the process. As mentioned above, in some examples, delegation of the master role is impossible because only the WM302 is within the communication range of all WH306s. Based on the latency requirements of the WBMS, complete, partial, and idle superframes are scheduled. The average power consumption of the WM302 can be reduced because the listening time is shorter compared to a single-layer network. The average power consumption in the WH306 can exceed the average power consumption in the WD308.

[0133] In superframe 1202A of Figure 12A, standard data exchange between WH1 306.1, WH2 306.2, and their subclusters is shown, as explained in Figure 4A. WM302 sends DL 1204 (DL-WM) to each WH306 on channel M1. In this case, WH1 306.1 receives DL 1206A, and WH2 306.2 receives DL 1206B. After WM302 sends this DL 1204, the WM waits for WH306 to receive responses from WD308 and provide those responses to WM302.

[0134] In response to DL 1204, each WH306 sends a DL to the WD308 within its respective subcluster 304. In this example, WH1 306.1 sends DL1208 (DL WH1) to WD2-WD7 308. DL 1208 is transmitted on channel A1. WH1 306.1 communicates with its own WD308 using channel A1 in the first superframe 1202A. WH2 306.2 sends DL 1210 (DL WH2) to WD9 via WD14 308. DL 1210 is transmitted on channel B1. WH2 306.2 communicates with its own WD308 using channel B1 in the first superframe 1202A. In this example, each subcluster 304 uses a different channel for communication between the WH306 and WD308 within the subcluster 304.

[0135] Each WD308 receives a DL (1208 or 1210 in this example) from its respective WH306. Although only WD2 308.2 and WD14 308.14 are shown in Figure 12A, other WD308s operate similarly. WD2 308.2 receives DL 1212, and WD14 308.14 receives DL 1214. Each WD308 responds to its respective WH306 with a UL. Here, WD2 308.2 sends UL 1216 to WH1 306.1 on channel A1. WD14 308.14 sends UL 1218 to WH2 306.2 on channel B1. Although not shown in Figure 12A, other WD308s also send ULs to their respective WH306s on the appropriate channels.

[0136] After receiving ULs from each WD308 within each subcluster, each WH306 aggregates the information contained in the ULs from the WD308s within its subcluster and sends the UL to the WM302. Here, WH1 306.1 sends UL 1224 to the WM302 on channel M1. WH2 306.2 sends UL 1226 to the WM302 on channel M1. As ULs 1224 and 1226 are sent at different times on channel M1 as shown in the diagram, they do not interfere with each other. The WM302 receives ULs 1228A to 1228D from each WH306 it manages. At this point, the first superframe 1202A is completed and the second superframe 1202B is started.

[0137] The superframe 1202B in Figure 12B is a partial type 2 superframe used for keep-alive operation. WM302 sends DL 1230, which contains the keep-alive command, to WH306 on channel M2. WH1 306.1 receives DL 1232A, and WH2 306.2 receives DL 1232B. Subsequently, WH306 sends DLs to each WD308 on their respective data channels. WH1 306.1 sends DL 1234 to its own WD308 (including WD2 308.2), and WH2 306.2 sends DL 1236 to its own WD308 (including WD14 308.14). WH1 306.1 communicates with the subcluster on channel A2, and WH2 306.2 communicates with the subcluster on channel B2. WD2 308.2 receives DL 1238 from WH1 306.1, and WD14 308.14 receives DL 1240 from WH2 306.2. In this superframe 1202B, WD308 does not send a response back to WH306, and WH306 does not send a response back to WM302. DL maintains synchronization between components while reducing power consumption. UL is not used in superframe 1202B.

[0138] The examples in this specification may include the procedure for a node reconnection process. If a particular WD308 in subcluster 304 stops communicating during normal operation, after a timeout, WH306 can instruct the WD308s in subcluster 304 to scan for configuration channels. WH306 notifies WM302 that it is entering the pairing phase. Other WHs may continue normal operation. After all WD308s in subcluster 304 have responded to WH306, WH306 notifies WM302, and WM302 initiates a master hopping sequence for WH306. In a single-tier network, even if only one WD308 loses connectivity, all nodes are required to scan for configuration channels. Here, while another subcluster 304 is performing a reconnection operation, other subclusters 304 may continue operation.

[0139] If a WH306 stops communicating with a WM302, the WM302 may restart the pairing process for all WH306s. To initiate the restart, the WD308 is requested to scan for configuration channels.

[0140] Figure 13 is a flowchart of Method 1300 for hierarchical network operation of a WBMS, following various examples herein. The various steps of Method 1300 can be performed in any suitable order. The hardware components described above with respect to Figures 1 to 3 can implement Method 1300 in some examples. In some examples, any suitable hardware, software, or digital logic can implement Method 1300.

[0141] Method 1300 begins in 1310 when a wireless head node (WH306) receives a first downlink on a first channel from a wireless master node (WM302) in the WBMS in a superframe. The wireless head node is the head node of a subcluster 304 of one or more wireless devices 308. An example of the first downlink is DL406A in superframe 402A in Figure 4A.

[0142] Method 1300 continues in 1320, where the wireless head node (WH306) transmits a second downlink on a second channel to each of the one or more wireless devices 308 in the subcluster 304 in the superframe. The second downlink may be DL408 in Figure 4A.

[0143] Method 1300 continues in 1330, where the wireless head node (WH306) receives uplinks from each of the one or more wireless devices 308 on the second channel in the superframe. In one example, the uplinks from the wireless devices 308 are UL420A-420F in Figure 4A.

[0144] Method 1300 continues in 1340, where the wireless head node (WH306) transmits an aggregated uplink from the wireless head node (WH306) to the wireless master node (WM302) on a first channel in the superframe, the aggregated uplink containing data from each of one or more wireless devices within the subcluster. In one example, the aggregated uplink is UL424 in Figure 4A.

[0145] In several examples described herein, a hierarchical WBMS network structure is described that can handle a large number of nodes with low latency and one-hop extension. The primary node (WM302) acts as the master node for the entire network of nodes. The secondary nodes are divided into subclusters 304, each containing one or more secondary nodes. The secondary nodes within each subcluster act as radio head (WH306) nodes and function as the master node of the subcluster 304 to which they belong. The other secondary nodes within each subcluster 304 are WDs (radio devices) 308. In some examples, instead of selecting one of the WDs 308 as the WH306, a dedicated WH306 node may be used in the subcluster 304. The WM302 and WH306 can manage the communication channels used by the nodes using a master-hopping sequence.

[0146] In the hierarchical system described herein, WM302 communicates with WH306, and WH306 communicates with WD308. WM302 is within communication range of WH306, and WH306 is within communication range of each WD308 in subcluster 304. Subcluster 304 may have the same number of WD308 or different numbers of WD308. Multiple superframe structures for managing communication between nodes arranged in the hierarchical system are described herein.

[0147] In the case of a WBMS with a large number of nodes, latency is reduced by the hierarchical system and superframe structure described herein. Throughput is also improved due to the efficient superframe structure. In the examples described herein, reduced network restart time and reduced power consumption can also be achieved.

[0148] In this specification, the term “to couple” may include connections, communications, or signaling paths that enable a functional relationship consistent with this specification. For example, if device A generates a signal to control device B to perform a certain action, then (a) in the first example, device A is coupled to device B by a direct connection, or (b) in the second example, device A is coupled to device B via intermediate component C, such that device B is controlled by device A via a control signal generated by device A, provided that intermediate component C does not alter the functional relationship between device A and device B.

[0149] A device "configured to perform" a certain task or function may be configured by the manufacturer at the time of manufacture to perform that function (e.g., by programming and / or wiring connections) and may be reconfigurable (or reconfigurable) by the user after manufacture to perform that function and / or other additional or alternative functions. Such configuration may be achieved by the device's firmware and / or software programming, the configuration and / or layout of hardware components, the interconnection of devices, or a combination thereof.

[0150] In this specification, unless otherwise specified, “about,” “approximately,” or “substantially” preceding a parameter means within ±10 percent of that parameter. Within the scope of the claims, the examples described may be modified, and other examples may also be made.

Claims

1. It is a method, In a superframe, a wireless head node in a wireless battery management system (WBMS) receives a first downlink on a first channel from a wireless master node, wherein the wireless head node is the head node of one or more subclusters of wireless devices, and the receiving of the first downlink is... In the superframe, the wireless head node transmits a second downlink on a second channel to each of the one or more wireless devices in the subcluster, In the superframe, the wireless head node on the second channel receives an uplink from each of the one or more wireless devices, In the superframe, the aggregated uplink is transmitted from the wireless head node to the wireless master node on the first channel, Includes, The aggregated uplink includes data from each of the one or more wireless devices in the subcluster. method.

2. The method according to claim 1, wherein the superframe is a first superframe, and the method further comprises In the second superframe, the wireless head node receives a third downlink on a third channel from the wireless master node, In the second superframe, the wireless head node transmits a fourth downlink on a fourth channel to each of the one or more wireless devices in the subcluster, In the second superframe, the wireless head node receives an uplink from each of the one or more wireless devices on the fourth channel, In the second superframe, a second aggregated uplink is transmitted from the wireless head node to the wireless master node on the third channel, Includes, The second aggregated uplink includes data from each of the one or more wireless devices within the subcluster. method.

3. The method according to claim 1, wherein the second channel is a constituent channel.

4. The method according to claim 1, wherein the wireless head node is a first wireless head node, the subcluster is a first subcluster, and the method further comprises In the superframe, the second wireless head node, which is the head node of the second subcluster, receives the first downlink on the first channel from the wireless master node, In the superframe, the second wireless head node transmits a third downlink on a third channel to each of the one or more wireless devices in the second subcluster. Methods that include...

5. The method according to claim 1, wherein the wireless head node is a first wireless head node, the subcluster is a first subcluster, and the aggregated uplink is a first aggregated uplink. The method further includes, in the superframe, transmitting a second aggregated uplink from the second wireless head node to the wireless master node on the first channel, The second aggregated uplink includes data from each of one or more wireless devices within the second subcluster. method.

6. The method according to claim 1, wherein the first channel and the second channel are non-adjacent channels selected in a master hopping sequence.

7. It is a system, Includes a wireless head node within the Wireless Battery Management System (WBMS), The wireless head node is the head node of one or more subclusters of wireless devices, and the wireless head node is In a superframe, the first downlink is received from the wireless master node on the first channel. In the superframe, a second downlink is transmitted on a second channel to each of the one or more wireless devices in the subcluster. In the superframe, an uplink is received from each of the one or more wireless devices on the second channel. In the superframe, the aggregated uplink is transmitted to the wireless master node on the first channel. It is configured in such a way, The aggregated uplink includes data from each of the one or more wireless devices in the subcluster. system.

8. The system according to claim 7, wherein the superframe is a first superframe, The wireless head node is further configured to receive a keep-alive downlink from the wireless master node on a third channel in a second superframe. system.

9. The system according to claim 8, wherein the keep-alive downlink is a first keep-alive downlink, The wireless head node is further configured to transmit a second keep-alive downlink to each of the one or more wireless devices in the subcluster in the second superframe. system.

10. The system according to claim 7, wherein the aggregated uplink includes data from the wireless head node.

11. The system according to claim 7, wherein each of the one or more wireless devices is coupled to at least one battery cell.

12. The system according to claim 7, wherein the first downlink includes requests for battery cell information from one or more wireless devices.

13. A system according to claim 12, wherein the wireless head node is configured to delay the measurement of battery cell information for a battery cell coupled to the wireless head node.

14. The system according to claim 7, wherein the first downlink and the second downlink are requests for network information.

15. The system according to claim 14, wherein the wireless head node is a first wireless head node, and the first wireless head node is configured to complete network information for the subcluster before the second wireless head node starts network information.

16. It is a system, Includes a first wireless head node within the Wireless Battery Management System (WBMS), The first wireless head node is the head node of a subcluster of one or more wireless devices, and the first wireless head node is In a superframe, the first downlink is received from the wireless master node on the first channel. In the superframe, a second downlink is transmitted on the configured channel to each of the one or more wireless devices within the subcluster. The second wireless head node waits for the third downlink to be transmitted on the configuration channel. In the superframe, an uplink is received from each of the one or more wireless devices on the second channel. In the superframe, the aggregated uplink is transmitted to the wireless master node on the first channel. It is configured in such a way, The aggregated uplink includes data from each of the one or more wireless devices in the subcluster. system.

17. The system according to claim 16, The WBMS further includes a second wireless head node, The second wireless head node is the head node of a second subcluster of one or more wireless devices, and the second wireless head node is In the superframe, the first downlink is received from the wireless master node on the first channel. The first wireless head node waits for the second downlink to be transmitted on the configuration channel. In the superframe, the third downlink is transmitted over the configuration channel to each of the one or more wireless devices within the second subcluster. In the superframe, an uplink is received from each of the one or more wireless devices on the third channel. In the superframe, a second aggregated uplink is transmitted to the wireless master node on the first channel. It is configured in such a way, The second aggregated uplink includes data from each of the one or more wireless devices in the second subcluster. system.

18. The system according to claim 16, wherein the second downlink is a request for network information of one or more wireless devices within the subcluster.

19. The system according to claim 16, wherein each of the one or more wireless devices is coupled to a battery cell.

20. The system according to claim 16, wherein the superframe is a first superframe, the configuration channel is a first configuration channel, and the first wireless head node further In the second superframe, the fourth downlink is received from the wireless master node on the third channel. In the second superframe, a fifth downlink is transmitted on the second configuration channel to each of the one or more wireless devices in the subcluster. It is configured in such a way. system.

Images