Node resynchronization mechanism for wireless battery management system

Abstract

In an example, a method includes receiving, in a first superframe (502B), a first downlink (522B) from a wireless master node (504) on a first channel at a wireless device (506.5) in a WBMS, where the first downlink (522B) indicates a second channel assigned to the wireless device (506.5). The method includes transmitting, in the first superframe (502B), a synchronization frame (530) from the wireless device (506.5) to an asynchronous wireless device (506.3) on the second channel, where the synchronization frame (530) indicates a third channel. The method also includes receiving, in the first superframe (502B), the synchronization frame (530) at the asynchronous wireless device (506.3) on the second channel. The method includes transmitting an uplink from the asynchronous wireless device (506.3) to the wireless master node (504) on the third channel in a second superframe following the first superframe (502B).

Description

Background Technology

[0001] Modern vehicles may contain multiple battery cells. Information associated with these cells, such as temperature, voltage, and other indicators of cell status and health, can be monitored for vehicle safety and to ensure proper operation. In conventional wired battery management systems, rechargeable batteries are managed via a circuit system for safe and efficient operation. A wired communication interface is used to connect a main microcontroller (primary node) to each battery module (secondary node), and each battery module is linked to the remaining battery modules in a daisy chain. With wired communication interfaces, the main microcontroller cannot monitor and control all battery modules in parallel without complex wiring. This wiring makes individual cell repair or replacement more difficult and, importantly, increases the weight and size of the entire system.

[0002] Wireless connectivity between the battery modules and the microcontroller makes battery module management more flexible and easier to maintain. In a Wireless Battery Management System (WBMS), the microcontroller monitors each battery module and communicates with it using a wireless communication interface. The main microcontroller uses the WBMS protocol to control all battery modules. However, the wireless communication interface may be susceptible to variations in wireless communication channel bandwidth, interference, and / or other issues, which can hinder proper monitoring and management within the WBMS. Summary of the Invention

[0003] According to at least one example of the specification, a method includes, in a first superframe, a wireless device in a WBMS receiving a first downlink from a wireless master node on a first channel, wherein the first downlink indicates a second channel assigned to the wireless device. The method also includes, in the first superframe, transmitting a synchronization frame from the wireless device to a asynchronous wireless device on the second channel, wherein the synchronization frame indicates a third channel. The method further includes, in the first superframe, receiving the synchronization frame at the asynchronous wireless device on the second channel. Finally, the method includes, in a second superframe following the first superframe, transmitting an uplink from the asynchronous wireless device to the wireless master node on a third channel.

[0004] According to at least one example of the specification, a method includes determining, at a wireless master node, that a wireless device in a WBMS is out of synchronization. The method includes instructing a first synchronized wireless device in the WBMS to transmit a synchronization frame on a first channel in a first superframe. The method further includes receiving an uplink from the out-of-synchronization wireless device in a second superframe following the first superframe.

[0005] According to at least one example of the specification, the wireless master node in the WBMS includes transceiver circuitry and processing circuitry. The processing circuitry is configured to determine when a wireless device in the WBMS loses synchronization. The processing circuitry is also configured to instruct a first synchronized wireless device in the WBMS to transmit a synchronization frame on a first channel via the transceiver circuitry in a first superframe. The transceiver circuitry is configured to receive uplink from a asynchronous wireless device in a second superframe following the first superframe. Attached Figure Description

[0006] Figure 1 This is a perspective view of an example system (e.g., a motor vehicle) that includes a wireless battery management system (WBMS) based on various examples.

[0007] Figure 2A It is a WBMS based on various instances.

[0008] Figure 2B It is a WBMS based on various instances.

[0009] Figure 3A and 3B Show an instance for asynchronous nodes before adding it to the program.

[0010] Figure 4 Displays data and configured channels based on various instances.

[0011] Figure 5A and 5B Demonstrates node resynchronization mechanisms based on various instances.

[0012] Figure 6A , 6B And 6C demonstrates the node resynchronization mechanism based on various instances.

[0013] Figure 7 It is a countdown program for node resynchronization based on various instances.

[0014] Figure 8 This is a flowchart illustrating various methods for node resynchronization in WBMS, based on different examples.

[0015] Figure 9 This is a flowchart illustrating various methods for node resynchronization in WBMS, based on different examples.

[0016] Figure 10 This is a flowchart illustrating various methods for node resynchronization in WBMS, based on different examples.

[0017] Figure 11 This is a flowchart illustrating various methods for node resynchronization in WBMS, based on different examples.

[0018] The same reference numerals or other reference indicators are used in the accompanying drawings to indicate (functionally and / or structurally) the same or similar features. Detailed Implementation

[0019] Some electronic devices use batteries to operate. For example, electric vehicles contain multiple battery cells that supply power to those vehicles. Because the battery cells in electronic devices can provide a large amount of power, and further because the power provided by the battery cells may be critical to the operation of the electronic devices, the electronic devices may include systems for managing the battery cells.

[0020] 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 status of the battery cells in an electronic device (e.g., voltage, current, temperature). Furthermore, a BMS can control various battery cells to manage the electrical power supplied by the battery cells and the location of that power within the electronic device. Typically, a BMS includes multiple components, such as multiple battery modules and a controller for managing the battery modules. Each battery module can be coupled to multiple battery cells and includes a battery monitor for monitoring those battery cells. Thus, the battery cells coupled to the battery modules provide power to the electronic device; the battery monitors in the battery modules monitor the health status and operating conditions of the battery cells in the battery modules; and the controller communicates with the battery monitors to ensure the proper operation of the battery modules and their cells. The controller can also communicate with the battery monitors to control the operation of the battery cells to connect, disconnect, redirect, or otherwise balance the power supplied by those battery cells.

[0021] A BMS can be combined with wireless technologies to create a Wireless Battery Management System (WBMS). For example, a primary network node contains or is coupled to a controller, and secondary network nodes contain battery modules that control multiple battery cells. The primary and secondary network nodes (e.g., primary / master node and end node) can communicate wirelessly with each other, for example, using radio frequency. In some protocols, superframes (SF) can be used to facilitate wireless communication between the primary and secondary network nodes. In an SF, the primary network node first broadcasts downlink communications (or packets) to multiple secondary network nodes. The secondary network nodes respond individually to the primary network node serially using uplink communications (or packets). Further details of examples of WBMS can be found in commonly assigned U.S. Patent Application No. 17 / 828,895, filed May 31, 2022, entitled “Efficient Unicast Super Frame Communications,” which is incorporated herein by reference in its entirety.

[0022] In WBMS, nodes can accidentally become out of sync, where a secondary node (wireless device, or WD) loses communication with the primary node (wireless master, or WM). It is desirable to quickly resynchronize out-of-sync WDs with minimal disruption to data service. WDs can become out of sync due to power resets, radio interference, conflicts between interrupts that cause resets, or missed frequency hopping sequence information. Out-of-sync WDs no longer follow the channel frequency hopping sequence and cannot receive data. If a WD becomes out of sync, the entire WBMS network can be reset to restore synchronization. However, resetting the entire network can cause disruption, where properly functioning synchronized WDs undergo unnecessary synchronization processes. Resetting the entire network can also require many superframes to restore normal operation, resulting in prolonged disruption to normal operation. In high-interference wireless environments, frequent interruptions and network resets may occur.

[0023] In the examples presented in this paper, the WM detects one or more asynchronous WDs. Upon detecting an asynchronous WD, the WM selects one or more synchronized WDs, and those selected synchronized WDs transmit a "synchronization frame" on one of the configured channels in the selected uplink time slot within the superframe. Each of the selected WDs transmits a synchronization frame in one or more uplinks in the superframe, in addition to its own uplink time slot. The synchronization frame specifies the selected timestamp and data channel for data transmission in the next superframe. The asynchronous WD listens for the synchronization frame on the configured channel. The asynchronous WD receives the synchronization frame, uses the information in the synchronization frame to synchronize its timing, and switches to the specified data channel for the next superframe. In the next superframe, the asynchronous WD receives the next downlink (DL) from the WM and is thus resynchronized. Therefore, in many instances, the time used to resynchronize the asynchronous WD is one superframe. Furthermore, the synchronized WDs continue to transmit their uplinks to the WM while the resynchronization process is in progress, thus avoiding disruption to the operation of the WBMS, except for the asynchronous WDs.

[0024] In one instance, the WM can implement a countdown process where the selected synchronized WD will not transmit the synchronization frame in the next superframe, but rather in a specified future superframe. In this instance, the selected WD can acknowledge to the WM that it has received the synchronization frame instruction. The WM can also wait to check the synchronization status until the specified future superframe, instead of checking every superframe.

[0025] In the examples described herein, a synchronized WD is used to assist node resynchronization to avoid service disruptions in the WBMS. During the node resynchronization process, the WM can continue to send DLs to the WD, and the synchronized WD can continue to respond to the WM in appropriate time slots. Therefore, the WM can preferably utilize one or more WDs to assist resynchronization by transmitting synchronization frames to reduce service disruptions, rather than the WM transmitting synchronization frames without assistance from any WD. Further details of examples of resynchronizing WDs can be found in commonly assigned U.S. Patent Application No. 17 / 977,906, filed October 31, 2022, entitled “Methods, Apparatus, and Articles of Manufacture to Improve One-Hop Extension in Wireless Battery Management Systems,” which is incorporated herein by reference in its entirety.

[0026] Figure 1 This is a perspective view of an example system 98 (e.g., a motor vehicle) incorporating WBMS 100, based on various examples herein. Although system 98 is described in an automotive context, the techniques disclosed herein can be implemented in other systems, such as home automation, industrial automation, and wireless sensor networks. In some examples, system 98 is for any system that may include WBMS 100 to power one or more components of system 98. As shown, WBMS 100 includes a master network node 102, a battery controller 104, multiple sub-network nodes 106, and multiple battery cells 108. In one example, master network node 102 may be a WM, and sub-network nodes 106 may be hierarchically arranged wireless headends (WHs) and WDs, wherein WDs are arranged in sub-clusters, and each sub-cluster has a WH to manage its respective WD. Additional details of examples of hierarchical structures in WBMS can be found in commonly assigned U.S. Patent Application No. 18 / 345,636, filed June 30, 2023, entitled "Hierarchical Wireless Battery Management System," which is incorporated herein by reference in its entirety. Although this disclosure describes communication techniques primarily in the context of wireless systems, these techniques can also be used in wired systems (e.g., where the connection between nodes 102 and 106 is wired).

[0027] In one example, the primary network node 102 is coupled to the 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), an Internal Integrated Circuit (I2C), etc. A secondary network node 106 is wirelessly coupled to the primary network node 102 (e.g., a WM). The WM in the secondary network node is coupled to the battery cell 108 using a second wired connection 112. Although... Figure 1 A single primary network node 102 and a single battery controller 104 are shown, but other instance network architectures with multiple primary / primary nodes may also be used to implement the techniques of this disclosure. Additional instance details of multiple primary nodes in a WBMS can be found in co-assigned U.S. Patent Application No. 17 / 823,138, filed August 30, 2022, entitled “Multiple Primary Nodes for Wireless Battery Management System Robustness,” which is incorporated herein by reference in its entirety.

[0028] In one example, WBMS 100 provides wireless radio frequency (RF) communication between the primary network node 102 and the secondary network node 106 (and, within the hierarchy, between WH and WD). In one example, the wireless RF communication uses the unlicensed 2.4 GHz Industrial, Scientific, and Medical (ISM) band from 2.4 GHz to 2.483 GHz, which conforms to the Bluetooth Special Interest Group (SIG). In this example, WBMS 100 uses 2 Mbps Bluetooth Low Energy (BLE) across the Physical Layer (PHY). The Open Systems Interconnection (OSI) model includes the PHY as a layer for transmitting raw bits over a physical medium. In this case, the PHY is free space, and WBMS 100 uses this free space to wirelessly communicate between the WH of the primary network node 102 and the secondary network node 106. In one example, the transmission power of WBMS 100 is less than or equal to 10 dBm.

[0029] In one example, wireless RF communication between primary network node 102 and secondary network node 106 utilizes frequency hopping and time slot allocation to transmit and receive data across the superframe interval (SF). SF, also known as superframe interval, is a time interval that includes the time and frequency allocation for data exchange between primary network node 102 and secondary network node 106, including the interframe spacing between these allocations. Frequency hopping involves transmitting RF signals by rapidly changing the transmission frequency among multiple different frequencies occupying a frequency band. In one example, frequency hopping occurs based on a linear shift-back register and the primary identifier (ID) of primary network node 102. The linear shift-back register uses linear bit rotation to indicate the frequency pattern in which primary network node 102 and secondary network node 106 will communicate. Time slot allocation refers to the time slots assigned to one or more of primary network node 102 or secondary network node 106 for transmission to one or more of secondary network node 106 or primary network node 102. Time slot allocation occurs in half-duplex mode because both the primary network node 102 and the secondary network node 106 switch between transmission and reception modes according to the time points specified in the scan / pairing frames for downlink (DL) / uplink (UL) durations in the data exchanged.

[0030] In one example, WBMS 100 uses Frequency Division Multiple Access (FDMA) and modifies the frequency at which frames are transmitted between the primary network node 102 and the corresponding secondary network node 106 to improve interference robustness. In another example, WBMS 100 uses a frequency hopping table, a frequency blacklist, and configuration channels to mitigate interference with other wireless networks. Frequency hopping occurs on a per-SF basis, during which time slots are allocated for frame switching. The blacklist suspends the use of frequency channels susceptible to interference. The configuration channels can be used for scanning, pairing, and negotiation communication between the primary network node 102 and the secondary network node 106.

[0031] In one example, wireless RF communication between primary network node 102 and secondary network node 106 uses 40 channels, of which subgroups (e.g., channels 37, 38, and 39) are used for system configuration, and the remaining 37 channels are used for data exchange. In another example, a single channel may be used as a configuration channel.

[0032] In one example, WBMS 100 supports periodic and aperiodic data exchange from secondary network node 106 to primary network node 102 using wireless RF communication. Primary network node 102 and secondary network node 106 use a shared data format structure for both periodic and aperiodic data exchange. Periodic data exchange occurs based on repetition intervals, while aperiodic data exchange does not. The data format is a description of the rules that the data in the populated file will follow. Generally, the more detailed the data format description, the easier it is to write verification rules on both the sending and receiving sides of WBMS 100.

[0033] In one example, the primary network node 102 scans the network to obtain a primary ID and discovers the secondary network node 106. The primary network node 102 scans the network by transmitting 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 check) primary ID values ​​used by other nodes and / or devices. The primary network node 102 then selects a primary ID that is different from the primary ID used by other nodes and / or devices.

[0034] In one example, after the primary network node 102 has selected a primary ID, it will transmit a scan request frame in each SF cycle as long as there are unconnected secondary network nodes 106. In one example, the primary network node 102 is programmed with a total number of secondary network nodes 106 connected to it. After all secondary network nodes 106 have connected and confirmed, the primary network node 102 will not transmit any further scan requests. The scan request frame contains information about the SF structure and the frame formatting of the DL and UL time slots.

[0035] In order for the primary network node 102 to scan the secondary network node 106, the primary network node 102 enters a scanning state. In this state, the primary network node 102 transmits a scan request frame in each SF period. The secondary network node 106 replies to the primary network node 102 with a scan response and waits for a pairing request frame from the primary network node 102. After receiving the pairing request, the secondary network node 106 responds within the same SF period in the frequency time slot assigned by the primary network node 102. In this example, this exchange occurs in the configuration channel. No data exchange occurs in this state. Additional details on establishing communication channels can be found in commonly assigned U.S. Patent Application No. 2022 / 0332213, filed April 16, 2021, entitled “Wireless Protocol for Battery Management”; and U.S. Patent Application No. 2023 / 0051689, filed August 11, 2021, entitled “Wireless Battery Management System Setup,” each of which is incorporated herein by reference in its entirety.

[0036] In one example, the transmission period, 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. Given a number of secondary network nodes 106, the primary network node 102 estimates the number of DL time slots available for transmitting packets to the secondary network nodes 106. Therefore, the total number of time slots in the communication time interval is as follows:

[0037] Total_slots = nr_of_WD+nr_DL_slots,

[0038] Where nr_of_WD is the number of sub-network devices, and nr_DL_slots is the number of DL slots available for the sub-network devices.

[0039] WBMS 100 manages battery cell 108 using a primary network node 102, a battery controller 104, and a secondary network node 106. The primary network node 102 and the secondary network node 106 communicate with each other regarding the status of battery cell 108. The primary network node 102 and the secondary network node 106 can communicate with 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 to convey battery management information. When battery cell 108 notifies the secondary network node 106 of a status condition, the secondary network node 106 communicates the presence of the status to the primary network node 102. The primary network node 102 receives the notification of the status from the secondary network node 106 and issues an alarm to the battery controller 104 regarding the status. The battery controller 104 determines the appropriate response to the status and sends instructions to the primary network node 102. The primary network node 102 transmits the instructions to the secondary network node 106. The secondary network node 106 receives instructions to manage the battery cell 108 in response to the aforementioned condition. The secondary network node 106 manages the battery cell 108 in response to the aforementioned condition.

[0040] Figure 2AThe diagram illustrates an example of WBMS 200. WBMS 200 is an example of the WBMS 100 described above. As shown, WBMS 200 includes a main network node 102, a battery controller 104, a memory 202, a processor 204, a first network node 206, a first plurality of battery cells 208, a second network node 210, and a second plurality of battery cells 212. Additional secondary network nodes 206 and 210 may be included, although these are not explicitly shown in the diagram. The main network node 102 includes a memory 202 and a processor 204, the processor being configured to execute code 205 stored in the memory 202 to perform one or more of the actions attributed to the main network node 102 herein. In one example, a portion of the memory 202 may be non-transitory, while a portion of the memory 202 may be transient. Secondary network nodes 206 and 210 may also include processors and memory. For example, as shown, the first network node 206 includes a processor 262 coupled to a memory 264 storing executable code 265, which can be executed by the processor 262 to perform one or more of the actions attributed herein to the first network node 206. The processors described herein can include any suitable processor or combination of processors. For example, a processor (e.g., processor 204 or 262) can be a central processing unit (CPU), a digital signal processor (DSP), a microcontroller unit (MCU), a DSP+MCU processor, a field-programmable gate array (FPGA), a processing circuit system, or an application-specific integrated circuit (ASIC). The primary network node 102 and the secondary network node 106 may also include transmitter and receiver circuitry or circuitry (e.g., transceiver circuitry) configured to perform the operations described herein. The transmitter and receiver circuitry may include any suitable hardware or software to perform the operations described herein.

[0041] The primary network node 102 is coupled to the battery controller 104 via a first wired connection 110 and wirelessly coupled to each of the secondary network nodes 206 and 210. The primary network node 206 is coupled to the primary battery cells 208 via a third wired connection 214 and wirelessly coupled to the primary network node 102. The secondary network node 210 is coupled to the secondary battery cells 212 via a fourth wired connection 216 and wirelessly coupled to the primary network node 102. Figure 2A There is no limit to the number of sub-network nodes in WBMS 200; instead, the naming convention indicates that each of the sub-network nodes is coupled to multiple battery cells.

[0042] 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 via a wired connection. In this example, the WBMS 200 includes one primary network node. In other examples, the WBMS 200 includes multiple primary network nodes, where each network has its own hierarchy.

[0043] WBMS 200 uses a master network node 102, a battery controller 104, a memory 202, a processor 204, a first network node 206, and a second network node 210 to manage a first plurality of battery cells 208 and a second plurality of battery cells 212. Instructions in the memory 202 cause the processor 204 to instruct the master network node 102 to wirelessly communicate with the first network node 206 and the second network node 210 regarding the status of the first plurality of battery cells 208 and the second plurality of battery cells 212. The master network node 102 and the second network nodes 206 and 210 communicate using various protocol formats. For example, the master network node 102 and the second network nodes 206 and 210 use the DL protocol format and the UL protocol format, each of which includes a frame control field to convey battery management information. When the first plurality of battery cells 208 notify the first network node 206 of its status, the first network node 206 conveys the existence of the status to the master network node 102. The master network node 102 receives a notification from the first network node 206 regarding the condition and issues an alarm to the battery controller 104 regarding the condition. The battery controller 104 determines the appropriate response to the condition and sends instructions to the master network node 102. The master network node 102 transmits the instructions to the first network node 206. The first network node 206 receives the instructions to manage the first plurality of battery cells 208 in response to the condition. The first network node 206 manages the first plurality of battery cells 208 in response to the condition. A similar process can be applied to the second network node 210 when a condition exists in the second plurality of battery cells 212. If the WBMS uses a hierarchical structure as described above, the WM communicates with the WH, and the WH communicates with the corresponding WD, and then relays the response from the WD back to the WM.

[0044] Figure 2BThe illustration illustrates example WBMS 250. WBMS 250 is an example of WBMS 100 described above. As shown, WBMS 250 includes a first network node 206, a first plurality of battery cells 208, a plurality of master network nodes 252, a memory 254, a processor 256, a first wired connection 258, and a plurality of battery controllers 260. The plurality of master network nodes 252 include memory 254 and processor 256. In one example, a portion of memory 254 may be non-transitory, and a portion of memory 254 may be transient. In this example, memory 254 includes executable code 255, which, when executed by processor 256, causes processor 256 to perform the actions attributed herein to the plurality of master network nodes 252.

[0045] Multiple master network nodes 252 are coupled to multiple battery controllers 260 via a first wired connection 258, and wirelessly coupled to a first network node 206. The first network node 206 is coupled to multiple battery cells 208 via a third wired connection 214, and wirelessly coupled to multiple master network nodes 252. (The text repeats itself here.) Figure 2B As shown, the first network node 206 may include a processor and memory (e.g., processor 262 and memory 264). Figure 2B There is no limit to the number of secondary network nodes in WBMS 250. In one instance, each of the multiple primary network nodes 252 is wirelessly coupled to at least eight secondary network nodes. In one instance, primary network node 206 can be coupled to at least sixteen battery cells using a fourth wired connection 216.

[0046] WBMS 250 uses multiple master network nodes 252, multiple battery controllers 260, memory 254, processor 256, and a first network node 206 to manage a first plurality of battery cells 208. Instructions in memory 254 cause processor 256 to instruct the multiple master network nodes 252 and the first network node 206 to wirelessly communicate regarding the status of the first plurality of battery cells 208. The multiple master network nodes 252 and the first network node 206 communicate using various protocol formats. For example, the multiple master network nodes 252 and the first network node 206 use DL protocol format and UL protocol format, each of which includes a frame control field to convey battery management information. When the first plurality of battery cells 208 notify the first network node 206 of a status, the first network node 206 communicates the presence of the status to the multiple master network nodes 252. The multiple master network nodes 252 receive the notification of the status from the first network node 206 and issue an alarm to the multiple battery controllers 260 regarding the status. Multiple battery controllers 260 determine the appropriate response to a condition and send instructions to multiple master network nodes 252. The master network nodes 252 transmit instructions to a first network node 206. The first network node 206 receives instructions to manage the first plurality of battery cells 208 in response to a condition. The first network node 206 manages the first plurality of battery cells 208 in response to the condition.

[0047] In one example, a first network node 206 communicates with a first master network node among multiple master network nodes 252 based on instructions from a master controller (not shown). The first network node 206 can transfer communication from the first master network node to a second master network node among the multiple master network nodes 252. The first and second master network nodes communicate with each other to coordinate the transfer of active connections of the first network node 206 from the first master network node to the second master network node. In one example, the first master network node communicates with the first network node 206, and the second master network node monitors the status of the first master network node. The status indicates whether the first master network node has power and is operating under normal conditions. The first master network node provides a clock signal to the second master network node to synchronize communication. The first and second master network nodes select different frequencies to communicate with the first network node 206. Selecting different frequencies allows the multiple master network nodes 252 to minimize interference when communicating with the first network node 206. For example, if the first primary network node loses power, or if the first primary network node is out of normal operating condition, the second primary network node can connect to the first network node 206 to supplement communication until the first primary network node can resume normal operation.

[0048] Figure 3A and 3B The instance rejoining procedure 300 is displayed for asynchronous nodes. The rejoining procedure 300 contains several instance superframes 302 (e.g., Figure 3A 302A, 302B, 302C, and Figure 3B (302D, 302E, and 302F in the example). Superframe 302 contains instance uplinks (UL) and downlinks (DL) for WM 304 and WD 306.1 and 306.3. In this example, WM304 may be the primary network node 102 as described above. WD1 306.1 and WD3 306.3 may be secondary network nodes 106 as described above. In this example, two WD 306s are shown, but any number of WD 306s may exist in other examples. Superframe 302 contains various ULs and DLs 308 to 346, which may be labeled Rx and Tx herein. These Tx and Rx represent communication between devices in an instance WBMS (e.g., WBMS 100). Details of each of Tx and Rx 308 to 346 are described below.

[0049] Rejoin procedure 300 is an instance of the rejoin procedure where WD1 306.1 remains synchronized with WM 304, while WD3 306.3 becomes out of sync. Therefore, the rejoin procedure is executed to synchronize WD3 306.3. Figure 3A In SF 302A, WM 304 transmits Tx 308 to each WD 306 on the data channel. Here, WD1 306.1 receives Rx 310A, and WD3 306.3 receives Rx 310B. Tx 308 may contain instructions for WD 306 to provide information such as the status of the battery cell 108 coupled to the corresponding WD 306. In response to receiving Rx 310A, WD1 306.1 sends Tx 312A back to WM 304 in the time slot assigned to SF 302A of WD1 306.1. In response to receiving Rx 310B, WD3 306.3 sends Tx 312B back to WM 304 in the time slot assigned to SF 302A of WD3 306.3. The UL received by WM 304 from each WD 306 is shown as Rx314.1 to Rx 314.N, where WBMS 100 contains N WD 306.

[0050] SF 302B begins in a similar manner to SF 302A. In SF 302B, WM 304 transmits Tx 316 to each WD 306 on the data channel. Here, WD1 306.1 receives Rx 318A. However, in this instance, WD3 306.3 has become out of sync in SF 302B, and therefore WD3 306.3 misses its Rx (shown as the missed Rx 318B). Thus, WD3 306.3 has missed a DL frame within one SF.

[0051] In response to receiving Rx 318A in SF 302B, WD1 306.1 sends Tx 320 back to WM 304 in the time slot assigned to SF 302B. The ULs received by WM 304 from each WD 306 are shown as Rx 322.1 to Rx 322.N. As shown in SF 302B, WD3 306.3 does not provide a UL to WM 304 in its time slot, which is shown in SF 302B as a missed Rx 322 (“No UL”). In one instance, WM 304 tracks the missed ULs from various WD 306s to determine if a rejoin procedure should be initiated.

[0052] SF 302C also begins in a similar manner to SF 302A. In SF 302C, WM 304 transmits Tx 324 to each WD 306 on the data channel. Here, WD1 306.1 receives Rx 326A. In SF 302C, WD3 306.3 remains asynchronous, and therefore WD3 306.3 misses its Rx (shown as the missed Rx 326B). Thus, WD3 306.3 has missed DL frames within two SF 302s (e.g., SF 302B and 302C).

[0053] In response to receiving Rx 326A in SF 302C, WD1 306.1 sends Tx 328 back to WM 304 in the time slot assigned to SF 302C. The ULs received by WM 304 in SF 302C from each WD 306 are shown as Rx 330.1 to Rx 330.N. As shown in SF 302C, WD3 306.3 did not provide a UL to WM 304 in its time slot, which is shown in SF 302C as another missed Rx 330 (“No UL”). WM 304 tracks that WD3 306.3 has missed ULs in two consecutive SF 302Cs.

[0054] exist Figure 3BIn this example, during SF 302D, WM 304 transmits Tx 332 to each WD 306 on the data channel. Here, WD1 306.1 receives Rx 334A. During SF 302D, WD3 306.3 is still asynchronous, and therefore WD3 306.3 misses its Rx (shown as the missed Rx 334B). Thus, WD3 306.3 has missed the DL frame within three SF 302s. In this example, WD306 is programmed to begin scanning the configuration channel if it misses the DL within three consecutive SF 302s. In other examples, a different number of missed SF 302s may be missed before WD306 scans the configuration channel.

[0055] In response to receiving Rx 334A in SF 302D, WD1 306.1 sends Tx 336 back to WM 304 in the time slot assigned to SF 302D. The ULs received by WM 304 in SF 302D from each WD 306 are shown as Rx 338.1 to Rx 330.N. As shown in SF 302D, WD3 306.3 did not provide a UL to WM 304 in its time slot, which is shown in SF 302D as another missed Rx 338 (“No UL”). WM 304 tracks that WD3 306.3 has missed ULs in three consecutive SF 302D sessions.

[0056] In SF 302E, WM 304 has determined that one or more WD 306 (WD3 306.3 in this case) have missed three SF 302. In response to this determination, WM 304 instructs all WD 306 to switch to the configuration channel for re-entry. WM 304 sends Tx 340 to each WD 306 on the data channel. Tx 340 contains instructions for the WD 306 to switch to the configuration channel. WD1 306.1 receives Rx 342 in SF 302E and sends Tx 344 to WM 304. WM 304 receives UL (Rx) from each WD306, shown in SF 302E as Rx 346.1 to Rx 346.N. SF 302E shows that WM 304 again does not receive Rx 346 from WD3 306.3.

[0057] In SF 302E, WD3 306.3 begins scanning the configuration channel using procedure 348. In SF 302F, WM 304 begins rejoining sequence 350 using the configuration channel. WD1 306.1 also scans the configuration channel in procedure 352. In this example, rejoining sequence 350 is performed for each WD 306 (even for WD 306s that are still synchronized (e.g., WD1 306.1)).

[0058] By performing a re-entry sequence 350 on each WD 306, the synchronized WD 306's operation is disrupted within the re-entry sequence 350 due to the execution of procedure 352. During the re-entry sequence 350, the WD 306 does not exchange data with the WM 304. Therefore, the normal operation of the WD 306 can be disrupted by the re-entry sequence 350. If there are a large number of WDs in the WBMS 100 and the system contains a lot of radio interference, the re-entry sequence 350 can be performed frequently, thus disrupting the normal operation of the WBMS 100. In other words, without any assistance from the synchronized WDs, the re-entry sequence 350 can be slow and disrupt the operation of the WBMS 100. In other examples described below, a node resynchronization mechanism is provided that re-enters a non-synchronized WD 306 without disrupting the operation of the synchronized WD 306.

[0059] Figure 4 This document demonstrates data and configurations for channel 400 based on various examples presented in this article. In some examples, channel 400 may be configured as a Bluetooth Low Energy (BLE) frequency channel, where the example frequency is... Figure 4 The example is shown below. This example includes three configuration or advertising channels (402A, 402B, and 402C), which are channels 37, 38, and 39. Channel 404 is a data channel and includes channels 0 through 36, for a total of 37 data channels. As will be described in further detail below, nodes in the network can be configured to communicate on channel 404 using frequency hopping. Additional details on examples of frequency hopping in WBMS can be found in commonly assigned U.S. Patent Application No. 17 / 898,614, filed August 30, 2022, entitled "Adaptive Frequency Hopping in a Wireless Battery Management System," which is incorporated herein by reference in its entirety.

[0060] like Figure 4 As shown, three configuration channels are adjacent to certain data channels. For example, configuration channel 38 is located in a frequency band adjacent to the bands used for data channels 10 and 11. Channels in adjacent or close frequency bands can interfere with each other. As described below, adjacency rules can be used to select configuration and data channels to reduce the possibility of interference between assigned channels. Adjacency rules can take into account transmission power spectrum characteristics, center frequency separation, signal-to-noise ratio requirements, etc., to select and assign channels.

[0061] In the examples presented in this paper, the node resynchronization mechanism includes: sending a synchronization frame (e.g., a "sync frame") from a synchronized WD that can be received by a non-synchronized WD. The synchronization frame specifies the selected timestamp and data channel for data transmission in the next superframe. The non-synchronized WD listens for the synchronization frame on the configured channel. The non-synchronized WD receives the synchronization frame, uses the information in the synchronization frame to synchronize timing, and switches to the specified data channel for the next superframe. The synchronized WD continues to transmit its uplink to the WM while the resynchronization process is in progress, thus avoiding disruption to the WBMS operation.

[0062] During instance operation, WM creates a list of synchronized and asynchronous WDs based on the previous superframe. Multiple SFs may be needed to confirm asynchronous nodes. If asynchronous WDs exist, WM selects three synchronized WDs. The selected synchronized WDs can be chosen randomly or using any suitable algorithm. WM then creates a schedule table for the current SF's resynchronization frame (synchronization frame) before transmitting its normal DL to the synchronized WDs. WM assigns a configuration channel to each selected WD.

[0063] Next, the WM checks for adjacent channel interference using predefined adjacency rules. If the current data channel used to transmit data between the WM and the WD is adjacent to the assigned configuration channel 1, 2, or 3, the WD corresponding to the adjacent configuration channel is removed from the scheduling table created by the WM. Adjacent channels can cause interference. As described above, adjacency rules may take into account transmission power spectrum characteristics, center frequency separation, and signal-to-noise ratio (SNR) requirements. In some instances, rules such as "at least two channels must be separated" may be used.

[0064] Then, the WM transmits a schedule table with configuration channel assignment and synchronization frame information in the next DL frame. The selected synchronized WD receives the DL frame from the WM. The selected WD prepares the synchronization frame for transmission in every UL time slot except its own UL time slot. The WD transmits to the WM in its own UL time slot. The synchronization frame is transmitted through each selected WD on its assigned configuration channel. The synchronization frame may contain the current timestamp, the timestamp of the next expected DL frame, and the data channel of the next expected DL frame. The asynchronous WD can then uniquely identify the WBMS network in time and frequency space and is able to synchronize and receive its next DL reception from the WM. The WM can then receive UL frame receptions from each WD, including those from previously asynchronous WDs in the next SF, and again monitor for missed ULs from the WDs.

[0065] Figure 5A and 5B This demonstrates the node resynchronization mechanisms based on the various examples in this article. Figure 5A Demonstrating the 500A superframe structure, and Figure 5BThis demonstrates the continuation of the 500B superframe architecture. The 500A and 500B superframe architectures include features for... Figure 5A and 5B The left side displays the UL and DL for various devices (WM 504, WD1 506.1, WD3 506.3, WD4 506.4, WD5 506.5, and WD6 506.6). The UL and DL shown in each row represent the links transmitted or received by the specific devices listed on the left. For example, Figure 5A and 5B The top row displays the UL and DL associated with WM 504 (sent or received by WM 504). Similarly, Figure 5A and 5B The last few lines show the UL and DL associated with WD6 506.6 (sent or received by WD6 506.6). In one instance, WM 504 could be the primary network node 102 as described above, and WD 506 could be the secondary network node 106.

[0066] Superframe structure 500A includes a first SF 502A and a second SF 502B. Superframe structure 500B includes a third SF 502C and a fourth SF 502D. Superframe structures 500A and 500B include various ULs and DLs 508 to 554. These ULs and DLs represent communication between devices in an instance WBMS (e.g., WBMS 100). Details of each of ULs and DLs 508 to 554 are described below.

[0067] The superframe architectures 500A and 500B also demonstrate channels used for communication by devices in WBMS 100. These channels may include both data channels and configuration channels. The specific ULs and DLs transmitted on each channel are described below.

[0068] Figure 5A and 5B This demonstrates the resynchronization process of an instance node using the superframe architecture 500A and 500B. Figure 5AIn the first SF 502A, WM 504 sends Tx 508 to WD 506 on the data channel (data channel a1 in this example). Here, WD1 506.1 receives Rx 510A, WD5 506.5 receives Rx 510B, and WD6 506.6 receives Rx 510C. Tx 508 may contain instructions for WD 506 to provide information such as the status of the battery cell 108 coupled to the corresponding WD 506. In response to receiving Rx 510A, WD1 506.1 sends Tx 512A back to WM504 in the time slot of SF 502A assigned to WD1 506.1. In response to receiving Rx 510B, WD5 506.5 sends Tx 512B back to WM 504 in the time slot assigned to SF 502A of WD5 506.5. In response to receiving Rx 510C, WD6 506.6 sends Tx 512C back to WM 504 in the time slot assigned to SF 502A of WD6 506.6. The UL received by WM 504 from each WD 506 is shown as Rx 514.1 to Rx514.N, where WBMS 100 contains N WD 506s (N is 7 in this example).

[0069] In this example, WD3 506.3 and WD4 506.4 are asynchronous. In SF series prior to SF 502A ( Figure 5A (Not shown in the diagram), WD3 506.3 and WD4 506.4 each determine that they have missed a certain number of DLs from WM 504. In response to this determination, WD3 506.3 and WD4 506.4 begin scanning configuration channels in SF 502A. WD3 506.3 is scanning configuration channel 39 (procedure 516), and WD4 506.4 is scanning configuration channel 38 (procedure 518). Asynchronous WD 506 can scan any configuration channel in response to determining that it is asynchronous. The configuration channels to be scanned can be programmed, randomly selected, or selected using any suitable algorithm.

[0070] SF 502A demonstrates the UL (Rx 514.1 to Rx 514.N) received from WD 506 by WM 504. In this example, WBMS 100 has 7 WD 506s, but in other examples any number of WDs may be present. For simplicity, Figure 5A and 5B WD2 and WD7 are not shown. In this example, WM 504 receives UL certifications from WD 1, 2, 5, 6, and 7. UL certifications from WD3 506.3 and WD4 506.4 are not shown. Figure 5AThe missing ULs are shown in the diagram (“No UL”). As described above, WM 504 may have also missed these ULs from WD3 506.3 and WD4 506.4 in SF prior to SF 502A. Therefore, in response to the missing ULs in SF 502A, WM 504 determines that a resynchronization process should begin in SF 502B.

[0071] For the resynchronization process, WM 504 creates a list of synchronized and unsynchronized WDs 506 based on one or more previous superframes (e.g., SF 502A in this example). In this example, WM 504 selects three synchronized WDs 506. In other examples, the number of WDs 506 selected may vary depending on the number of available configuration channels, channel adjacency rules, and other relevant factors. WM 504 then creates a schedule table (e.g., a table) for the current SF 502B's resynchronization frames (synchronization frames) before transmitting their normal DL to the synchronized WDs 506. WM 504 assigns a configuration channel to each selected WD 506.

[0072] In this example, WM 504 selects WD1 506.1, WD5 506.5, and WD6 506.6 to send synchronization frames to the asynchronous WD 506. WM 504 assigns a configuration channel to each selected WD 506. In this example, the configuration channels are channels 37, 38, and 39. In SF 502B, WM 504 sends Tx 520 to WD 506. Tx 520 contains synchronization frame information that WD1 506.1, WD5 506.5, and WD6 506.6 will send to the asynchronous WD 506. Tx 520 may also contain normal operation instructions for WBMS 100, so that the synchronized WD 506 can continue to send its data to WM 504. In this example, Tx 520 is sent on data channel a2. WD1 506.1 receives Rx 522A, WD5 506.5 receives Rx 522B, and WD6 506.6 receives Rx 522C.

[0073] In response to receiving Rx 522A, WD1 506.1 sends Tx524A back to WM 504 in the time slot assigned to SF 502B of WD1 506.1. In response to receiving Rx 522B, WD5 506.5 sends Tx 524B back to WM 504 in the time slot assigned to SF 502B of WD5 506.5. In response to receiving Rx 522C, WD6 506.6 sends Tx 524C back to WM 504 in the time slot assigned to SF502B of WD6 506.6. The UL received by WM 504 from each WD 506 is presented as Rx 526.1 to Rx 526.N. Again, the UL ratings from WD3 506.3 and WD4 506.4 are missing in SF 502B.

[0074] In the node resynchronization process described herein, WD 506 is selected to transmit multiple synchronization frames on the configured channel within its originally open time slot in SF 502B. For example, WD1 506.1 is assigned configured channel 37 by WM 504. WD1 506.1 transmits multiple synchronization frames on configured channel 37 in the time slot of SF 502B (in... Figure 5A The time slot shown as Sync-37 sends synchronization frame 528, and this time slot is not used by WD1 506.1 to communicate with WM 504. WD5 506.5 uses configuration channel 39 in the time slot of SF 502B (in... Figure 5A Synchronization frame 530 is transmitted on Sync-39, in a time slot not used by WD5 506.5 for communication with WM 504. WD6 506.6 transmits synchronization frame 530 on configuration channel 38 in the time slot of SF 502B (in... Figure 5A As shown in the diagram, synchronization frame 532 is transmitted on Sync-38, a time slot not used by WD5 506.5 to communicate with WM 504. Therefore, WM 504 uses an idle time slot of the synchronized WD 506 to transmit synchronization information on the configuration channel, where the asynchronous WD 506 is listening for synchronization frames. In this example, WD3 506.3 is listening for synchronization frames on configuration channel 39, and therefore it will receive synchronization frame 530. WD4 506.4 is listening for synchronization frames on configuration channel 38, and therefore it will receive synchronization frame 532. Each of WD 506.3 and 506.4 may receive its respective synchronization frames 530 and 532 at some point during SF 502B. Although... Figure 5A The time it takes for process 518 to extend into SF 502B is longer than the time it takes for process 516 to extend into SF 502B, but in some instances, the end time of process 518 may be the same as or earlier than the end time of process 516.

[0075] like Figure 5AAs shown, WD3 506.3 becomes synchronized using information from synchronization frame 530 in SF 502B. Synchronization frame 530 may contain the current timestamp, the timestamp of the next expected DL frame from WM 504, and the data channel of the next expected DL frame. In this example, the data channel of the next expected DL frame is channel a3. Therefore, WD3 506.3 synchronizes in the next SF (SF502C, in...) Figure 5B (As shown in the image) Switch to channel a3. Similarly, WD4 506.4 becomes synchronized using information from synchronization frame 532 in SF 502B. WD4 506.4 then switches to channel a3 in the next SF (SF 502C). Figure 5B (In the display) it also switches to channel a3.

[0076] Figure 5B The superframe structure 500B is shown. Superframe structure 500B includes a third SF 502C and a fourth SF 502D. For simplicity, WD2 and WD7 are not shown in this example. In SF 502C, WM 504 sends Tx 534 to WD 506 on data channel a3. Tx 534 may further contain synchronization frame schedules for WD1 506.1, WD5 506.5, and WD6 506.6. The synchronization frame information in Tx534 includes the current timestamp, the timestamp of the next SF 502D, and the channel within the next SF 502D (data channel a4 in this example). At the start of SF 502C, WM 504 is unaware whether the asynchronous WD 506 is synchronized because WM 504 has not yet received ULs from those WD 506. Therefore, the selected WD 506 (WD1 506.1, WD5 506.5 and WD6 506.6) will continue to transmit synchronization frames in SF 502C.

[0077] Here, WD1 506.1 receives Rx 536A, WD3 506.3 receives Rx 536B, WD4 506.4 receives Rx 536C, WD5 506.5 receives Rx 536D, and WD6 506.6 receives Rx 536E. In response to receiving Rx 536, each synchronized WD506 sends Tx 538 back to WM 504 in the corresponding timeslot of WD 506 (shown as Tx 538A to 538E in SF 502C). The UL received by WM 504 from each WD 506 is shown as Rx 540.1 to Rx 540.N. In this example, WM 504 receives Rx 540 from each WD 506 (WD1 to WD7) and determines that all WD 506 are now synchronized.

[0078] WD1 506.1 is configured in channel 37 in the SF 502C time slot (in Figure 5B The time slot shown as Sync-37 sends synchronization frame 542, and this time slot is not used by WD1 506.1 to communicate with WM 504. WD5 506.5 uses configuration channel 39 in the time slot of SF 502C (in... Figure 5B Synchronization frame 544 is transmitted on Sync-39, in a time slot not used by WD5 506.5 to communicate with WM504. WD6 506.6 transmits synchronization frame 544 on configuration channel 38 in the time slot of SF 502C. Figure 5B The synchronization frame 546 is sent on Sync-38, and the time slot is not used by WD6 506.6 to communicate with WM 504.

[0079] At the start of SF 502D, WM 504 has already determined that all WD 506 are synchronized. Therefore, WM 504 does not need to instruct any WD 506 to send a synchronization frame within SF 502D. Alternatively, WM 504 sends Tx 548 containing instructions for normal operation to the WD 506. WM 504 sends Tx 548 to each WD 506 on data channel a4. WD 506 receives Rx 550 from WM 504 (shown as Rx 550A to Rx 550E in SF 502D). Each WD 506 then sends Tx 552 back to WM 504 in its respective time slot within SF 502D (shown as Tx 552A to Tx 552E in SF 502D). The WM 504 receives UL554.1 to 554.N and confirms again that all WD 506s are synchronized.

[0080] Figure 5A and 5B This demonstrates an instance node resynchronization process where the synchronized WD 506 is instructed by WM 504 to transmit synchronization frames on various configuration channels. As described above, when WM 504 assigns a configuration channel to the synchronized WD 506, WM 504 checks for adjacent channel interference using predetermined adjacency rules. If the current data channel used for transmitting data between WM 504 and WD 506 is adjacent to the assigned configuration channel 1, 2, or 3, then WD 506 corresponding to the adjacent configuration channel is removed from the scheduling table created by WM 504. This removal is performed to reduce the possibility of interference in adjacent channels. Figure 6A and 6B Provides an example of applying the adjacent rule.

[0081] Figure 6A , 6B And 6C demonstrates the node resynchronization mechanism based on the various examples in this article. Figure 6ADemonstrating the 600A superframe architecture. Figure 6B Demonstrates the 600B superframe structure, and Figure 6C Demonstrates the 600C superframe architecture. Superframe architectures 600A, 600B, and 600C are included in... Figure 6A , 6B And the UL and DL of the various devices shown on the left side of 6C (WM 604, WD1 606.1, WD3 606.3, WD4 606.4, WD5 606.5, and WD6 606.6). The UL and DL shown in each row are the links sent or received by the specific devices listed on the left. In one example, WM 604 may be the primary network node 102 as described above, and WD 606 may be the secondary network node 106.

[0082] Superframe structure 600A includes a first SF 602A and a second SF 602B. Superframe structure 600B includes a third SF 602C. Superframe structure 600C includes a fourth SF 602D and a fifth SF 602E. Superframe structures 600A, 600B, and 600C include various ULs and DLs 608 to 666. These ULs and DLs represent communication between devices in an instance WBMS (e.g., WBMS 100). Details of each of ULs and DLs 608 to 666 are described below.

[0083] The superframe architectures 600A, 600B, and 600C also demonstrate channels used for communication by devices in WBMS 100. These channels may include both data channels and configuration channels. The specific ULs and DLs transmitted on each channel are described below.

[0084] Figure 6A , 6B The 6C demonstration showcases the resynchronization process of an instance node using the superframe architecture of 600A, 600B, and 600C. Figure 6AIn the first SF 602A, WM 604 sends Tx608 to WD 606 on the data channel (data channel a1 in this example). Here, WD1 606.1 receives Rx 610A, WD5 606.5 receives Rx 610B, and WD6 606.6 receives Rx 610C. Tx608 may contain instructions for WD 606 to provide information such as the status of the battery cell 108 coupled to the corresponding WD 606. In response to receiving Rx 610A, WD1 606.1 sends Tx 612A back to WM604 in the time slot of SF 602A assigned to WD1 606.1. In response to receiving Rx 610B, WD5 606.5 sends Tx 612B back to WM 604 in the time slot assigned to SF 602A of WD5 606.5. In response to receiving Rx 610C, WD6 606.6 sends Tx 612C back to WM 604 in the time slot assigned to SF 602A of WD6 606.6. The UL received by WM 604 from each WD 606 is shown as Rx 614.1 to Rx614.N, where WBMS 100 contains N WD 606s (N is 7 in this example).

[0085] In this example, WD3 606.3 and WD4 606.4 are asynchronous. In SF series prior to SF 602A ( Figure 6A (Not shown in the diagram), WD3 606.3 and WD4 606.4 each determine that they have missed a certain number of DLs from WM 604. In response to this determination, WD3 606.3 and WD4 606.4 begin scanning configuration channels in SF 602A. WD3 606.3 is scanning configuration channel 39 (procedure 616), and WD4 606.4 is scanning configuration channel 38 (procedure 618). Asynchronous WD 606 can scan any configuration channel in response to determining that it is asynchronous. The configuration channels to be scanned can be programmed, randomly selected, or selected using any suitable algorithm.

[0086] SF 602A demonstrates the UL (Rx 614.1 to Rx 614.N) received from WD 606 by WM 604. In this example, WBMS 100 has 7 WD 606s, but in other examples any number of WDs may be present. For simplicity, Figure 6A , 6B WD2 and WD7 are not shown in section 6C. In this example, WM 604 receives UL certifications from WD 1, 2, 5, 6, and 7. UL certifications from WD3606.3 and WD4 606.4 are also not shown. Figure 6AThe missing ULs are shown in the diagram (“No UL”). As described above, WM 604 may have also missed these ULs from WD3 606.3 and WD4 606.4 in several SFs prior to SF602A. Therefore, in response to missing these ULs in SF602A, WM 604 determines that a resynchronization process should begin in SF 602B.

[0087] The resynchronization process in SF 602B is similar to that described above for SF 502B. For resynchronization, WM 604 creates a list of synchronized and unsynchronized WDs 606 based on the previous superframe (e.g., SF 602A). In this example, WM 604 selects three synchronized WDs 606. In other examples, a different number of WDs 606 may be selected. WM 604 then creates a schedule table for the current SF 602B's resynchronization frames (synchronization frames) before transmitting their normal DL to the synchronized WDs 606. WM 604 assigns a configuration channel to each selected WD 606.

[0088] In this example, WM 604 selects WD1 606.1, WD5 606.5, and WD6 606.6 to send synchronization frames to asynchronous WD 606. WM 604 assigns a configuration channel to each selected WD 606. In this example, the configuration channels are channels 37, 38, and 39. In this example, the data channel a2 of SF 602B is channel 10. Figure 4 As shown, data channel 10 is adjacent to configuration channel 38. Therefore, WD 606 is removed from the list of WD 606s selected to transmit synchronization frames by assigning configuration channel 38. Here, WM 604 assigns WD6 606.6 to configuration channel 38. Since configuration channel 38 is adjacent to data channel 10, WM 604 will remove WD6 606.6, and WD6 606.6 will not transmit synchronization frames in SF 602B.

[0089] In SF 602B, WM 604 sends Tx 620 to WD 606. Tx 620 contains synchronization frame information that WD1 606.1 and WD5 606.5 will send to the asynchronous WD 606. Tx 620 may also contain normal operation instructions for WBMS 100, so the synchronized WD 606 can continue to send its data to WM 604. In this example, Tx 620 is sent on data channel a2 (channel 10). WD1 606.1 receives Rx 622A, WD5 606.5 receives Rx 622B, and WD6 606.6 receives Rx 622C.

[0090] In response to receiving Rx 622A, WD1 606.1 sends Tx624A back to WM 604 in the time slot assigned to SF 602B of WD1 606.1. In response to receiving Rx 622B, WD5 606.5 sends Tx 624B back to WM 604 in the time slot assigned to SF 602B of WD5 606.5. In response to receiving Rx 622C, WD6 606.6 sends Tx 624C back to WM 604 in the time slot assigned to SF602B of WD6 606.6. The UL received by WM 604 from each WD 606 is presented as Rx 626.1 to Rx 626.N. Again, the UL values ​​from WD3 606.3 and WD4 606.4 are missing in SF 602B.

[0091] In the node resynchronization process described herein, WD 606 is selected to transmit synchronization frames on the configured channel in its originally open time slot in SF 602B. WD1 606.1 transmits synchronization frames on configured channel 37 in the time slot of SF 602B. Figure 6A The synchronization frame 628 (shown as Sync-37) is sent in the time slot, which is not used by WD1 606.1 to communicate with WM 504. WD5 606.5 is configured in the time slot of SF602B in channel 39 (in... Figure 6A Synchronization frame 630 is transmitted on Sync-39, a time slot not used by WD5 606.5 to communicate with WM 604. WD6 606.6 will not transmit a synchronization frame in SF 602B due to removal from the scheduler via the adjacent rule described above. In this example, WD3 606.3 is listening for synchronization frames on configuration channel 39, and therefore will receive synchronization frame 630. WD4 606.4 is listening for synchronization frames on configuration channel 38. Since no synchronization frames were transmitted on configuration channel 38 during SF 602B, WD4 606.4 does not receive any synchronization frames in SF 602B. WD4 606.4 continues to listen for synchronization frames in SF 602C.

[0092] exist Figure 6B In the SF 602C, WM 604 again assigns the synchronized WD 606 to send synchronization frames to the asynchronous WD 606. WM 604 selects WD1 606.1, WD5 606.5, and WD6 606.6 to send synchronization frames to the asynchronous WD 606. In other instances, other WD 606s can be selected. WM 604 assigns a configuration channel to each selected WD 606. In this instance, the configuration channels are channels 37, 38, and 39. The data channel a3 of the SF 602C is not adjacent to any configuration channel, therefore all three selected WD 606s will send synchronization frames in the SF 602C.

[0093] In SF 602C, WM 604 sends Tx 632 to WD 606. Tx 632 contains synchronization frame information that WD1 606.1, WD5 606.5, and WD6 606.6 will send to the asynchronous WD 606. Tx 632 may also contain normal operation instructions for WBMS 100, so the synchronized WD 606 can continue to send its data to WM 604. In this example, Tx 632 is sent on data channel a3. WD1 606.1 receives Rx 634A, WD3 606.3 receives Rx 634B, WD5 606.5 receives Rx 634C, and WD6 606.6 receives Rx 634D.

[0094] In response to receiving Rx 634, each of the WD 606 receiving Rx 634 sends Tx 636 back to WM 604 in the appropriate timeslot of said WD 606. WD1 606.1 sends Tx 636A, WD3 606.3 sends Tx 636B, WD5 606.5 sends Tx 636C, and WD6 606.6 sends Tx 636D. The UL received by WM 604 from each WD 606 is presented as Rx638.1 to Rx 638.N. In SF 602C, the UL from WD4 606.4 is the only missed UL.

[0095] In the node resynchronization process described herein, the selected WD 606 retransmits the synchronization frame on the configuration channel in its originally open time slot in the SF 602C. WD1 606.1 transmits synchronization frame 640 on configuration channel 37 (in... Figure 6B (Shown as Sync-37). WD5 606.5 transmits synchronization frame 642 on configuration channel 39 (in... Figure 6B (Shown as Sync-39). WD6 606.6 transmits synchronization frame 644 on configuration channel 38 (in... Figure 6B (Shown as Sync-38). In this example, the WD4606.4 is configured to listen for synchronization frames on channel 38, so it will receive synchronization frame 644 in SF 602C. Therefore, the WD4606.4 will synchronize and proceed to channel a4 in the next SF 602D.

[0096] Figure 6CSuperframe structure 600C is shown. Superframe structure 600C includes a fourth SF 602D and a fifth SF 602E. WD2 and WD7 are not shown in this example for simplicity. In SF 602D, WM 604 sends Tx 646 to WD 506 on data channel a4. Tx 646 may further contain synchronization frame schedules for WD1 606.1, WD5 606.5, and WD6 606.6. The synchronization frame information in Tx646 includes the current timestamp, the timestamp of the next SF 602E, and the channel within the next SF 602E (data channel a5 in this example). At the start of SF 602D, WM 604 is unaware whether WD4 606.4 is synchronized because WM 604 has not yet received the UL from WD4 606.4. Therefore, WD 606 (WD1 606.1, WD5 606.5 and WD6606.6) will continue to transmit synchronization frames in SF 602D.

[0097] Here, WD1 606.1 receives Rx 648A, WD3 606.3 receives Rx 648B, WD4 606.4 receives Rx 648C, WD5 606.5 receives Rx 648D, and WD6 606.6 receives Rx 648E. In response to receiving Rx 648, each synchronized WD606 sends Tx 650 back to WM 604 in the corresponding timeslot of WD 606 (shown as Tx 650A to 650E in SF 602D). The UL received by WM 604 from each WD 606 is shown as Rx 652.1 to Rx 652.N. In this example, WM604 receives Rx 652 from each WD 606 (WD1 to WD7) and determines that all WD 606 are now synchronized.

[0098] WD1 606.1 is configured in channel 37 in the time slot of SF 602D (in Figure 6C The time slot shown as Sync-37 sends synchronization frame 654, and this time slot is not used by WD1 606.1 to communicate with WM 604. WD5 606.5 uses the configured channel 39 in the time slot of SF 602D (in... Figure 6C Synchronization frame 656 is transmitted on Sync-39, in a time slot not used by WD5 606.5 for communication with WM604. WD6 606.6 transmits synchronization frame 656 on configuration channel 38 in the time slot of SF 602D. Figure 6C The synchronization frame 658 is sent on Sync-38, and the time slot is not used by WD6 606.6 to communicate with WM 604.

[0099] At the start of SF 602E, WM 604 has already determined that all WD 606 are synchronized. Therefore, WM 604 does not need to instruct any WD 606 to send a synchronization frame within SF 602E. Alternatively, WM 604 can send Tx 660 containing instructions for normal operation to the WD 606. WM 604 sends Tx 660 to each WD 606 on data channel a5. WD 606 receives Rx 662 from WM 604 (shown as Rx 662A to Rx 662E in SF 602E). Each WD 606 sends Tx 664 to WM 604 within its corresponding time period in SF 602E (shown as Tx 664A to Tx 664E in SF 602E). The WM 604 receives UL 666.1 to 666.N and reconfirms that all WD 606s are synchronized.

[0100] Figure 7 This is a countdown procedure for node resynchronization based on the various examples in this document. In this example, the WM can implement a countdown process where the selected synchronized WD will not transmit the synchronization frame in the next superframe, but rather in a specified future superframe. The selected WD can acknowledge to the WM that the WD has received the synchronization frame instruction. The WM can also wait to check the synchronization status until the specified future superframe, instead of checking each superframe. If the resynchronization procedure described above fails to resynchronize one or more WDs, the countdown procedure described in this document can be executed. In another example, if the above-described... Figures 5A to 6C If the described procedure fails to resynchronize, or if resynchronization using a countdown procedure fails, the procedure described above with respect to Figure 3 can be executed for resynchronization. The various resynchronization procedures described herein can be executed in any order.

[0101] In a countdown procedure, the WM determines that resynchronization should be performed. The WM then previews a selected number of superframes (e.g., 3 SFs, 5 SFs, 7 SFs, etc.) in the frequency hopping sequence. After removing any interfering configuration channels from the selected SFs (using the adjacency rules described herein), the WM assigns configuration channels to three selected synchronized WDs for the selected SFs. Thus, the WM creates a synchronization frame table, or scheduling table, for the upcoming selected superframes. The WM communicates the synchronization frame table, in the form of DL frames, along with the countdown to each WD. The countdown is the selected number of superframes (e.g., a countdown frame) that the WD will wait for before it begins transmitting a synchronization frame. After the countdown ends, the selected WD transmits the synchronization frame on its assigned configuration channel. The WM can then check again whether resynchronization is needed.

[0102] Figure 7This demonstrates an example countdown procedure 700. At SF1 702, the WM determines whether resynchronization should be performed. At SF2 704, the WM sends a table of synchronization frames for the selected upcoming SF. In this example, synchronization frames will be sent between SF5 and SF9. At SF2 704, the WM also begins a countdown. During the countdown, the selected WD should transmit its synchronization frame after 2 SFs.

[0103] At SF3 706, the WM can again send a table of synchronization frames for the selected upcoming SFs (SF5 to SF9). The countdown continues, and the selected WD should transmit its synchronization frame one SF later.

[0104] At SF4 708, the WM can resend the table of synchronization frames for the selected upcoming SFs (SF5 to SF9). The countdown continues, and the selected WD should transmit its synchronization frame after 0 SFs.

[0105] At SF5 710, WD is selected to transmit its synchronization frame. The synchronization frame will be transmitted over five SFs (SF5 to SF9). SF5 710 is the first SF of the five SFs. At SF6 712, WD is selected to transmit its synchronization frame. SF6 712 is the second SF of the five SFs. At SF7 714, WD is selected to transmit its synchronization frame. SF7 714 is the third SF of the five SFs. At SF8 716, WD is selected to transmit its synchronization frame. SF8 716 is the fourth SF of the five SFs. At SF9 718, WD is selected to transmit its synchronization frame. SF9 718 is the fifth SF of the five SFs.

[0106] At SF10 720, WM again determines whether a resynchronization process is needed. If a resynchronization process is needed, it can be repeated. Figure 7 The steps in the process are used for additional resynchronization.

[0107] Figure 8 This is a flowchart of method 800 for node resynchronization in WBMS, based on the various examples in this article. The steps of method 800 can be performed in any suitable order. (See above for details.) Figures 1 to 2B The hardware components described herein may execute method 800 in some instances. In some instances, any suitable hardware, software, or digital logic may execute method 800.

[0108] Method 800 begins at 810, wherein the wireless device (WD) receives a first downlink from the wireless master node in the WBMS on a first channel in a first superframe, wherein the first downlink indicates a second channel assigned to the wireless device. As an example, the first channel may be data channel a1 as described above. The second channel may be a configuration channel, such as channel 37, 38, or 39.

[0109] Method 800 continues at 820, where the WD transmits a synchronization frame from the WD to the asynchronous WD on a second channel in the first superframe, wherein the synchronization frame indicates a third channel. The third channel in the synchronization frame may be a data channel for the next superframe following the first superframe. In some instances, the third channel may be the same as the first channel. In one instance, if the first channel is data channel a1 used for data transmission in the first superframe, then the next superframe following the first superframe may reuse data channel a1 for data transmission. In other instances, the third channel may be different from the first channel.

[0110] Method 800 continues at 830, where the asynchronous WD receives the synchronization frame on the second channel in the first superframe. As described above, the asynchronous WD can switch to the configuration channel to listen for the synchronization frame when it becomes asynchronous.

[0111] Method 800 continues at 840, where the asynchronous WD transmits the uplink to the wireless master node on the third channel in the second superframe following the first superframe. The synchronization frame contains the third channel information, and the asynchronous WD switches to the third channel within the second superframe, thus becoming synchronized with the WM again.

[0112] Figure 9 This is a flowchart of method 900 for node resynchronization in WBMS, based on the various examples in this article. The steps of method 900 can be performed in any suitable order. (See above regarding...) Figures 1 to 2B The hardware components described herein may execute method 900 in some instances. In some instances, any suitable hardware, software, or digital logic may execute method 900.

[0113] Method 900 begins at 910, where the Wireless Master Node (WM) determines that the Wireless Device (WD) in the WBMS has lost synchronization. Any suitable criterion can be used for this determination. In one instance, the WM determines that the WD has lost synchronization if it fails to receive a UL from the WD within a specified number of consecutive superframes (e.g., 3, 5, or 9 SFs).

[0114] Method 900 continues at 920, where WM indicates that in the first superframe, the first synchronized radio device in the WBMS transmits a synchronization frame on the first channel. In one instance, the first channel may be a configuration channel. WM may instruct any number of WDs to transmit synchronization frames on various channels.

[0115] Method 900 continues at 930, wherein the WM receives the uplink from the asynchronous radio device in a second superframe following the first superframe. The second superframe may immediately follow the first superframe, or may be any number of subsequent superframes. After receiving the UL, the WM may determine that the asynchronous WD is now synchronized. The WM may receive the uplink from the asynchronous radio device on the data channel during the second superframe.

[0116] Figure 10 This is a flowchart of method 1000 for node resynchronization in WBMS based on various examples in this article. Figure 10 The above text shows about Figure 7 The described instance countdown program. The steps of method 1000 can be executed in any suitable order. As mentioned above... Figures 1 to 2B The hardware components described herein may execute method 1000 in some instances. In some instances, any suitable hardware, software, or digital logic may execute method 1000.

[0117] Method 1000 begins at 1010, where WM determines that resynchronization should be performed. WM may make this determination based on a certain number of missed ULs from one or more WDs.

[0118] Method 1000 continues at 1020, where the WM sends a synchronization frame table and countdown information to the selected synchronized WD. The synchronized WD to which the synchronization frame will be sent can be selected as described above or using any suitable technique. The synchronization frame table may contain which configured channel is assigned to which WD. The countdown information may be included in the synchronization frame table and may indicate which superframe the WD should begin transmitting the synchronization frame for. In some instances, the WM may retransmit the synchronization frame table and updated countdown information in subsequent superframes, as described above regarding... Figure 7 As described.

[0119] Method 1000 continues at 1030, wherein the WD transmits synchronization frames on its correspondingly assigned configuration channel within a predetermined number of superframes. The WM may instruct the WD to transmit synchronization frames within a certain number of superframes (e.g., three superframes, five superframes, etc.). The WM can select the configuration channel for transmission and the selected WD by previewing the frequency hopping sequence and selecting an appropriate channel and WD to avoid interference between adjacent channels during the transmission of synchronization frames in the superframes. The configuration channel assigned to the WD may also change each superframe.

[0120] Method 1000 continues at 1040, where WM checks whether the resynchronization procedure should be performed again. If an out-of-synchronization WD still exists, and WM misses the expected UL determination from any WD, then WM may perform the resynchronization procedure again. If another resynchronization procedure should be performed, method 1000 may return to 1010 and execute method 1000 again.

[0121] Figure 11 This is a flowchart of a method 1100 for node resynchronization in WBMS based on various examples in this article. Figure 11 The above demonstrates the applications used in the above discussion. Figure 4 The method for describing the adjacency rules. The steps of method 1100 can be performed in any suitable order. As mentioned above regarding... Figures 1 to 2B The hardware components described herein may execute method 1100 in some instances. In some instances, any suitable hardware, software, or digital logic may execute method 1100.

[0122] Method 1100 begins at 1110, where WM creates a list of asynchronous WDs and synchronized WDs based on previous superframes. Any program can be used to determine if a WD is asynchronous, for example, if the WD has failed to send a UL to WM within a certain number of frames. If one or more asynchronous WDs exist, WM begins to rejoin the sequence.

[0123] Method 1100 continues at 1120, where the WM selects the synchronized WD to send the synchronization frame. The WM may select three WDs in one instance, but a different number in other instances. In some instances, if three WDs are unavailable, the WM may use another re-joining technique, such as the process described above with respect to Figure 3.

[0124] Method 1100 continues at 1130, where WM creates a synchronization frame scheduling table. The scheduling table may contain which configuration channel is assigned to which selected synchronized WD. In some instances, the scheduling table contains three synchronized WDs, where each synchronized WD is assigned to one of three configuration channels.

[0125] Method 1100 continues at 1140, where WM determines whether adjacent channel interference exists based on predetermined adjacency rules. If the current data channel used for transmitting data between WM and WD is adjacent to the assigned configuration channel 1, 2, or 3, the WD assigned to the adjacent configuration channel is removed from the scheduling table created by WM. As described above, adjacency rules may take into account transmission power spectrum characteristics, center frequency separation, and SNR requirements. In some instances, rules such as "at least two channels must be separated" may be used.

[0126] Method 1100 continues at 1150, where WM removes WD from the synchronization frame schedule table in the presence of adjacent channel interference. WM generates an updated synchronization frame schedule table that does not contain WDs removed due to the adjacent rule.

[0127] Method 1100 continues at 1160, wherein the WM updates the synchronization frame schedule table to the transmitting WD in the DL frame. After the WD has received the DL frame with synchronization frame information, the WD can prepare the synchronization frame as described herein for transmission on its assigned configuration channel.

[0128] In the examples presented in this paper, utilizing a synchronized WD to assist node resynchronization avoids or reduces service disruptions and data interruptions in the WBMS compared to the WM transmitting synchronization frames without the assistance of a synchronized WD. During the node resynchronization process, the WM can continue to send DLs to the WD, while the synchronized WD can continue to respond to the WM in appropriate time slots. Furthermore, nodes can resynchronize quickly, for example, within a superframe in some instances.

[0129] In this description, the term "coupled" may encompass a connection, communication, or signaling path that achieves a functional relationship consistent with this description. For example, if device A generates a signal to control device B to perform an action: (a) in a first instance, device A is coupled to device B via a direct connection; or (b) in a second instance, if intermediate component C does not alter the functional relationship between device A and device B, then device A is coupled to device B via intermediate component C such that device B is controlled by control signals generated by device A.

[0130] A device "configured to" perform a task or function may be configured (e.g., programmed and / or hardwired) at the time of manufacture to perform a function and / or may be configured (or reconfigurable) by the user after manufacture to perform a function and / or other additional or alternative functions. Such configuration may be achieved through firmware and / or software programming of the device, through the construction and / or layout of hardware components, and through the interconnection of the device, or a combination thereof.

[0131] In this specification, unless otherwise stated, "about," "approximately," or "generally" before a parameter means within + / - 10% of the parameter. Modifications may be made in the described examples, and other examples may be made within the scope of the claims.

Claims

1. A method comprising: In the first superframe, a wireless device in a wireless battery management system (WBMS) receives a first downlink from a wireless master node on a first channel, wherein the first downlink indicates a second channel assigned to the wireless device. In the first superframe, a synchronization frame is transmitted from the wireless device to the asynchronous wireless device on the second channel, wherein the synchronization frame indicates the third channel; In the first superframe, the synchronization frame is received at the asynchronous wireless device on the second channel; and In the second superframe following the first superframe, an uplink is transmitted from the asynchronous wireless device to the wireless master node on the third channel.

2. The method according to claim 1, The second channel is the configuration channel, and The frequency band of the configuration channel is not adjacent to the frequency band of the third channel.

3. The method of claim 1, wherein the wireless device transmits a plurality of synchronization frames on the second channel in the first superframe.

4. The method of claim 1, wherein the synchronization frame includes a current timestamp.

5. The method of claim 1, wherein the synchronization frame includes a timestamp of the next expected downlink frame.

6. The method of claim 1, wherein the first downlink indicates the number of countdown frames for the wireless device.

7. The method of claim 1, wherein the first downlink further indicates a fourth channel assigned to a third radio device in the WBMS.

8. A method comprising: The wireless device in the wireless battery management system (WBMS) is found to be out of sync at the wireless master node; In the first superframe, the first synchronized radio device in the WBMS is instructed to transmit a synchronization frame on the first channel; and In the second superframe following the first superframe, the uplink is received from the asynchronous radio device.

9. The method of claim 8, further comprising instructing a second synchronized radio device in the WBMS to transmit the synchronization frame on a second channel in the first superframe.

10. The method of claim 9, further comprising instructing a third synchronized radio device in the WBMS to transmit the synchronization frame on a third channel in the first superframe.

11. The method of claim 8, wherein the synchronization frame indicates a data channel for transmitting the uplink to the wireless master node.

12. The method of claim 8, wherein the synchronization frame includes a current timestamp.

13. The method of claim 8, wherein the synchronization frame includes a timestamp of the next expected downlink frame.

14. The method of claim 8, wherein the first channel is a configuration channel.

15. The method according to claim 14, Receiving the uplink from the asynchronous wireless device includes receiving the uplink on a data channel; and The frequency band of the data channel is not adjacent to the frequency band of the configuration channel.

16. The method of claim 8, further comprising: In the first superframe, the first synchronized wireless device is instructed to wait for a predetermined number of superframes before transmitting the synchronization frame.

17. A wireless master node located in a wireless battery management system (WBMS), comprising: Transceiver circuit; and The processing circuitry is configured to perform the following operations: The wireless device in the WBMS is found to be out of sync; and The transceiver circuitry instructs the first synchronized radio device in the WBMS to transmit a synchronization frame on the first channel in the first superframe. The transceiver circuitry is configured to receive uplink from an asynchronous radio device in a second superframe following the first superframe.

18. The wireless master node of claim 17, wherein the processing circuitry is further configured to instruct a second synchronized wireless device in the WBMS to transmit the synchronization frame on a second channel in the first superframe.

19. The wireless master node of claim 17, wherein the synchronization frame includes a data channel for transmitting the uplink to the wireless master node.

20. The wireless master node according to claim 17, wherein the first channel is a configuration channel. The transceiver circuitry is configured to receive the uplink from the asynchronous wireless device over the data channel, and The frequency band of the data channel is not adjacent to the frequency band of the configuration channel.

Images