Networking method of wireless BMS and wireless BMS

Abstract

The invention discloses a networking method of a wireless BMS and the wireless BMS, and the networking method comprises the steps: when a slave node receives a networking invitation sent by a master node, shortening a default wake-up period to a preset wake-up period, and executing a wake-up operation and a networking response operation in the preset wake-up period, the duration of the default wake-up period being greater than the duration of the preset wake-up period; if the networking fails, maintaining the preset wake-up period and continuing to execute the networking response operation; if the continuous networking fails, prolonging the duration of the preset wake-up period; if the continuous networking failure reaches a preset failure frequency, executing a wake-up operation and a networking response operation in a default wake-up period; and if the networking is successful, restoring the default wake-up period. According to the method and the device, the problems that the networking time is multiplied and the networking efficiency is reduced due to the fact that a fixed period awakening mechanism is usually adopted during networking of an existing wireless BMS (Battery Management System) are solved.

Description

Technical Field

[0001] This invention relates to the field of power battery technology, and in particular to a networking method for a wireless BMS and a wireless BMS. Background Technology

[0002] In the battery safety and performance management of new energy vehicles, the BMS (Battery Management System) plays a crucial role. The main function of the BMS is to collect battery operating condition information and manage battery health.

[0003] Traditional Battery Management Systems (BMS) do not have slave nodes on each battery cell, and the number of slave nodes is limited. They are generally located in specific locations within the battery module or battery pack. Traditional BMS also do not monitor each individual cell; they are typically located within the battery module or battery pack. With the development of wireless communication technology, wireless BMS (Wireless Battery Management System) has gradually emerged. In the wireless BMS architecture, each slave node communicates with the master node wirelessly, eliminating the need for wiring. The master node processes the collected data and issues commands. This not only saves on wiring costs but also reduces vehicle weight, making it a promising technology with broad application prospects.

[0004] The main sources of power consumption in a wireless BMS are: modules that are not turned off during sleep (wireless module standby, sensor power supply, clock source leakage current), continuous power consumption of wake-up detection circuits (such as GPIO interrupt detection), and excessive quiescent current of the power management chip (PMIC). To reduce power consumption, slave nodes in a wireless BMS use sleep and wake-up methods, sending the collected data to the master node when they wake up.

[0005] However, existing wireless BMS typically employs a fixed-period wake-up mechanism during network deployment, such as waking up every 5 seconds. If network deployment fails during this wake-up period, a second 5-second interval is required, and waiting for the next cycle after a failure significantly increases deployment time. Furthermore, existing network deployment processes involve excessive handshake steps, such as channel scanning, key negotiation, and role assignment, which cannot be completed within a single wake-up window. In complex environments, high channel collision rates and increased retransmissions reduce network success rates, further decreasing network deployment efficiency. Therefore, a solution to improve the network deployment efficiency of wireless BMS is urgently needed. Summary of the Invention

[0006] This invention provides a networking method for a wireless BMS, aiming to solve the problem that existing wireless BMS typically use a fixed-period wake-up mechanism during networking, which leads to a significant increase in networking time and reduces networking efficiency.

[0007] To achieve the above objectives, the present invention proposes a wireless BMS networking method, wherein the wireless BMS includes a master node and multiple slave nodes that wirelessly communicate with the master node, and the wireless BMS networking method includes: When the slave node receives a network invitation sent by the master node, it shortens the default wake-up period to a preset wake-up period and performs a wake-up operation and a network response operation within the preset wake-up period. The duration of the default wake-up period is longer than the duration of the preset wake-up period. The default wake-up period is the default period set when the slave node switches from a dormant state to a working state when it has not received a network invitation sent by the master node. The preset wake-up period is the period set in advance when the slave node switches from a dormant state to a working state when it receives a network invitation sent by the master node. The wake-up operation is to switch the slave node from a dormant state to a working state, and the network response operation is to form a network with the master node according to the network invitation. If network formation fails, the preset wake-up period will be maintained and network response operations will continue to be performed; If network formation fails continuously, the duration of the preset wake-up period will be extended. If the number of consecutive network failures reaches the preset number, then the wake-up operation and network response operation will be performed according to the default wake-up cycle. If the network is successfully established, the default wake-up cycle will be restored.

[0008] In some embodiments, performing the wake-up operation includes: When the master node receives a wake-up beacon broadcast by the master node, which instructs the slave node to switch from a dormant state to a working state and contains network time window information, the master node parses the wake-up beacon to obtain the network time window, which includes the start and end times of the network formation between the slave node and the master node. Each slave node synchronously performs a wake-up operation within the network time window.

[0009] In some embodiments, the network response operation includes: Within the network time window, each slave node competes to access the network channel of the master node.

[0010] In some embodiments, the network response operation includes: The network response operation is performed by selecting a preset fast channel, wherein the preset fast channel is the channel with the least communication latency; and / or The network response operation combines authentication and key exchange, where authentication verifies the slave node device ID, and key exchange negotiates the communication encryption key between the master node and the slave node; and / or Multiple slave nodes execute the network response operation in parallel.

[0011] In some embodiments, the network response operation further includes: Upon receiving a network invitation from the master node, the pre-shared key, which is a key used to authenticate the slave node, is extracted locally. The pre-shared key is fed back to the master node so that the master node can authenticate the identity of the slave node.

[0012] In some embodiments, the network response operation includes: Receive polling network invitations from the master node on multiple channels; The network response operation is executed according to the preset frequency hopping sequence.

[0013] In some embodiments, the process before the slave node receives the networking invitation sent by the master node includes: The master node generates a networking instruction data packet with a byte count less than a preset byte count, and adds forward error correction (FEC) redundancy to the networking instruction data packet. The networking instruction is used to instruct the slave node to form a network with the master node. The network configuration command data packet is sent to the slave node.

[0014] In some embodiments, after sending the networking instruction data packet to the slave node, the process includes: Receive the network response operation results fed back from the node; The network is configured based on a priority strategy that prioritizes certain slave nodes, with the priority strategy used to indicate the network priority of each slave node.

[0015] In some embodiments, performing the priority strategy to preferentially network with multiple core slave nodes includes: The slave node that prioritizes network formation is used as the subnet coordinator, and the network formation invitation beacon is forwarded to the slave nodes that have not yet joined the network through the subnet coordinator.

[0016] The present invention also proposes a wireless BMS, which includes a master node and a plurality of slave nodes that communicate wirelessly with the master node, wherein the master node and the slave nodes are capable of executing the networking method of the wireless BMS described in any one of the above.

[0017] This invention shortens the default wake-up period to a preset wake-up period when a slave node receives a network invitation from a master node, and performs wake-up and network response operations within the preset wake-up period. The duration of the default wake-up period is longer than the duration of the preset wake-up period. The default wake-up period is the period set by default when a slave node switches from a dormant state to a working state when it has not received a network invitation from the master node, while the preset wake-up period is the period set in advance when a slave node switches from a dormant state to a working state when it receives a network invitation from the master node. The wake-up operation is to switch the slave node from a dormant state to a working state, and the network response operation is to establish a network with the master node according to the network invitation. If network establishment fails, the preset wake-up period is maintained and the network response operation continues. If network establishment fails consecutively, the duration of the preset wake-up period is extended. If consecutive network establishment failures reach a preset number of failures, the wake-up operation and network response operation are performed using the default wake-up period. If network establishment is successful, the default wake-up period is restored. This invention solves the problem that existing wireless BMS typically use a fixed-period wake-up mechanism during network establishment, which leads to a significant increase in network establishment time and reduces network establishment efficiency. Attached Figure Description

[0018] Figure 1 A flowchart illustrating the networking method of a wireless BMS provided in an embodiment of the present invention; Figure 2 This is another flowchart illustrating the networking method of the wireless BMS in this embodiment of the invention; Figure 3 This is another flowchart illustrating the networking method of the wireless BMS in this embodiment of the invention; Figure 4 This is another flowchart illustrating the networking method of the wireless BMS in this embodiment of the invention; Figure 5 This is another flowchart illustrating the networking method of the wireless BMS in this embodiment of the invention; Figure 6 This is another flowchart illustrating the networking method of the wireless BMS in this embodiment of the invention; Figure 7 This is another flowchart illustrating the networking method of the wireless BMS in this embodiment of the invention; Figure 8 This is a schematic diagram of the structure of a wireless BMS provided in an embodiment of the present invention. Detailed Implementation

[0019] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of the present invention.

[0020] It should be noted that all directional indications (such as up, down, left, right, front, back, etc.) in the embodiments of the present invention are only used to explain the relative positional relationship and movement of each component in a certain specific posture (as shown in the figure). If the specific posture changes, the directional indication will also change accordingly.

[0021] It should also be noted that when a component is described as "fixed to" or "set on" another component, it can be directly on the other component or there may be an intervening component present. When a component is described as "connected to" another component, it can be directly connected to the other component or there may be an intervening component present.

[0022] Furthermore, the use of terms such as "first" and "second" in this invention is for descriptive purposes only and should not be construed as indicating or implying their relative importance or implicitly specifying the number of technical features indicated. Therefore, a feature defined with "first" or "second" may explicitly or implicitly include at least one of that feature. Additionally, the technical solutions of the various embodiments can be combined with each other, but only on the basis of being achievable by those skilled in the art. When the combination of technical solutions is contradictory or impossible to implement, such a combination of technical solutions should be considered non-existent and not within the scope of protection claimed by this invention.

[0023] In some embodiments, the present invention provides a networking method for a wireless BMS, applied to a wireless BMS, wherein the wireless BMS includes a master node and multiple slave nodes that wirelessly communicate with the master node, and the networking method for the wireless BMS includes the following steps: In step S110, when the slave node receives the networking invitation sent by the master node, it shortens the default wake-up period to the preset wake-up period and performs the wake-up operation and networking response operation according to the preset wake-up period.

[0024] In step S120, if the network formation fails, the preset wake-up period is maintained and the network formation response operation continues.

[0025] Step S130: If networking fails continuously, the duration of the preset wake-up cycle is extended.

[0026] Step S140: If the number of consecutive network failures reaches the preset number, then the wake-up operation and network response operation are performed according to the default wake-up cycle.

[0027] Step S150: If the network is successfully established, restore the default wake-up cycle.

[0028] In this embodiment, refer to Figure 1 and Figure 8 The networking method for a wireless BMS is applied to a wireless BMS. A wireless BMS includes a master node and multiple slave nodes that wirelessly communicate with the master node. The master node and slave nodes are capable of executing the networking method for a wireless BMS according to embodiments of the present invention.

[0029] It is understandable that the default wake-up cycle is longer than the preset wake-up cycle.

[0030] During network formation, when a slave node receives a network invitation from the master node, it can shorten the default wake-up period to a preset wake-up period and perform wake-up and network formation operations according to the preset wake-up period. The wake-up period can be the time interval between the sleep state and the working state. The default wake-up period is the period set by default when a slave node switches from a sleep state to a working state if it has not received a network invitation from the master node. The preset wake-up period is the period set in advance when a slave node switches from a sleep state to a working state after receiving a network invitation from the master node. The preset wake-up period can be set according to actual needs to speed up the process of slave nodes joining the network. The wake-up operation is the process of switching the slave node from a sleep state to a working state. The network formation response operation is the process of forming a network with the master node according to the network invitation. The network formation response operation can refer to the slave node performing corresponding network configuration and connection operations based on the master node's invitation information.

[0031] For example, the default wake-up period for a slave node is 5 seconds, and the preset wake-up period is 1 second. When a slave node receives a network invitation sent by the master node, it can shorten the default wake-up period of 5 seconds to the preset wake-up period of 1 second. The slave node will wake up once every 1 second and complete the network response operation as soon as possible after each wake-up.

[0032] When network formation fails, the preset wake-up period can be maintained and network response operations can continue. In the event of consecutive network formation failures, the preset wake-up period can be extended using an exponential backoff algorithm. To reduce device power consumption and extend battery life in the event of consecutive network formation failures, an exponential backoff algorithm can be used to extend the wake-up period. Specifically, after each network formation failure, the wake-up period is multiplied by a fixed factor (e.g., 2) until it reaches its maximum value. Using the exponential backoff algorithm effectively avoids frequent network formation attempts, thereby saving energy.

[0033] For example, the preset wake-up period is 1 second. After the first network failure, the wake-up period changes to 2 seconds; after the second failure, it changes to 4 seconds; after the third failure, it changes to 8 seconds, and so on. Once the maximum value is reached, the wake-up period will not increase further even if network formation still fails.

[0034] The exponential backoff algorithm is an intelligent strategy that dynamically adjusts retry delay time to cope with failures or conflicts. The exponential backoff algorithm is based on the size of the conflict window. Each node has a conflict counter C. The backoff time has an exponential relationship with the number of conflicts. The more conflicts there are, the longer the backoff time may be. If the limit of the number of conflicts is reached, the node stops sending data.

[0035] For example, the exponential backoff algorithm can be expressed as: ```c / / Pseudocode example uint32_t wakeup_interval = 1000; / / Initial 1 second void handle_join_failure() { wakeup_interval = MIN(wakeup_interval * 2, 5000); / / The upper limit is 5 seconds set_timer(wakeup_interval); } ``` When the number of consecutive network connection failures reaches a preset number, a wake-up operation and a network response operation will be performed according to the default wake-up cycle. The preset number of failures can be a number of network connection failures pre-set by the system. For example, if the default wake-up cycle is 13 seconds and the preset number of failures is 5, when the number of consecutive network connection failures reaches 5, a wake-up operation and a network response operation will be performed according to the default wake-up cycle of 13 seconds. This can avoid the waste of resources and increased energy consumption caused by continuously attempting to connect to the network.

[0036] After successful network setup, the default wake-up cycle can be restored. Once a slave node successfully connects to the master node, it will resume its default wake-up cycle. For example, if the default wake-up cycle is once every 5 seconds, the timer will restart after a successful network connection and will wake up again in the next 5 seconds.

[0037] Understandably, the wake-up period is shortened during network setup, and the default period is restored after successful network setup. If network setup fails repeatedly, the wake-up period is extended. By reducing the wake-up period, the waiting time after network setup failure is reduced, thereby improving network setup efficiency.

[0038] The BMS networking method of this embodiment shortens the default wake-up period to a preset wake-up period when a slave node receives a networking invitation from the master node, and performs wake-up and networking response operations within the preset wake-up period. The duration of the default wake-up period is longer than the duration of the preset wake-up period. The default wake-up period is the period set by default when a slave node switches from a dormant state to a working state when it has not received a networking invitation from the master node, and the preset wake-up period is the period set in advance when a slave node switches from a dormant state to a working state when it receives a networking invitation from the master node. The wake-up operation is to switch the slave node from a dormant state to a working state, and the networking response operation is to form a network with the master node according to the networking invitation. If networking fails, the preset wake-up period is maintained and the networking response operation continues to be performed. If networking fails continuously, the duration of the preset wake-up period is extended. If the number of consecutive networking failures reaches a preset number, the wake-up operation and networking response operation are performed within the default wake-up period. If networking is successful, the default wake-up period is restored. This invention solves the problem that existing wireless BMS typically use a fixed-period wake-up mechanism during network deployment, which leads to a significant increase in network deployment time and reduces network efficiency.

[0039] In some embodiments, the aforementioned wake-up operation includes: Step S1101: When a wake-up beacon broadcast by the master node, which indicates that the slave node is switching from the sleep state to the working state and contains network time window information, is received, the wake-up beacon is parsed to obtain the network time window. In step S1102, each slave node synchronously performs a wake-up operation within the network time window.

[0040] In this embodiment, refer to Figure 2 When executing step S110, upon receiving a wake-up beacon broadcast by the master node indicating that a slave node is switching from a dormant state to a working state and containing network time window information, the wake-up beacon can be parsed to obtain the network time window. After obtaining the network time window, each slave node synchronously performs a wake-up operation within the network time window. The wake-up beacon can be a signal indicating that a slave node is switching from a dormant state to a working state and containing network time window information. The network time window includes the start and end times for the slave node to network with the master node, and can be a time range within which a slave node is allowed to join the network. Within the time window, the slave node can send a join request and establish a connection with the master node.

[0041] Understandably, the slave node only performs the wake-up operation after receiving the wake-up beacon, which can reduce the number of invalid wake-ups.

[0042] Specifically, when a slave node receives a wake-up beacon from the master node instructing it to switch from a dormant state to a working state and containing network time window information, the slave node parses the wake-up beacon to obtain the network time window. After obtaining the network time window, each slave node synchronously performs a wake-up operation within the network time window in order to establish a connection with the master node.

[0043] More specifically, the master node sends a wake-up beacon containing a timestamp and the length of the network time window to the slave node. After receiving the wake-up beacon from the master node, the slave node records the current time of receiving the wake-up beacon and compares the current time with the timestamp in the wake-up beacon to determine whether it is within the network time window.

[0044] For example, at time t=0, the master node sends a wake-up beacon containing a timestamp t=0 and a network time window length T=10 seconds. The slave node receives the wake-up beacon at time t=5, records the current time of receiving the wake-up beacon as t=5 seconds, and compares the current time with the timestamp in the wake-up beacon to determine that t=5-0=5 seconds is within the network time window. Then, each slave node immediately performs a wake-up operation to ensure that it wakes up at the correct time and communicates with the master node.

[0045] In some embodiments, the aforementioned network response operation includes: within the network time window, each slave node competes to access the network channel of the master node.

[0046] In this embodiment, during step S110, each slave node can compete to access the master node's networking channel within the networking time window. The networking channel can be a physical or logical channel that enables communication between the master node and slave nodes. Specifically, within the networking time window, the sending of a networking request can be determined by detecting the idle time of the networking channel. When a slave node detects that the networking channel has been idle for a period of time, it sends a networking request to attempt to establish a connection with the master node. When the master node receives the networking request and replies with an acknowledgment frame, the slave node successfully joins the network. If no reply is received or a conflict occurs, the slave node will wait for a period of time and then try to send the request frame again.

[0047] It is understandable that having nodes perform various network operations within the network time window can improve the network synchronization rate.

[0048] For example, there are three slave nodes A, B, and C, and a master node P. Within the network formation time window, slave nodes A, B, and C simultaneously detect that the channel has been idle for a certain period of time. Each slave node sends a request frame to attempt to establish a connection with the master node P. Before sending, each slave node A, B, and C will check whether the channel is idle. If the network channel is idle, it will send a network formation request; otherwise, it will wait for a period of time before retransmitting to ensure that each slave node A, B, and C can successfully establish a connection with the master node P and join the network.

[0049] In some embodiments, the aforementioned network response operation includes: Step S1103: Select a preset fast channel to perform network response operation; and / or Step S1104: Combine identity authentication and key exchange to perform network response operations; and / or Step S1105: Multiple slave nodes execute network response operations in parallel.

[0050] In this embodiment, refer to Figure 3 When executing step S110, a preset fast channel can be selected to perform the network response operation, and / or authentication and key exchange can be combined to perform the network response operation, and / or multiple nodes can perform the network response operation in parallel. The preset fast channel is the channel with the least communication latency, which can be a pre-set channel with low latency and high data transmission rate to improve network efficiency. Authentication verifies the slave node device ID, and key exchange negotiates the communication encryption key between the master node and the slave node. Combining authentication and key exchange can complete key negotiation while verifying the identities of both communicating parties. Selecting a preset fast channel to perform the network response operation can reduce latency and improve communication efficiency. Combining authentication and key exchange to perform the network response operation simplifies the operation and improves efficiency. Performing the network response operation in parallel by multiple slave nodes can speed up the network formation process, save network formation time, and improve efficiency.

[0051] It is understood that a preset fast channel can be selected to perform the network response operation; authentication and key exchange can be combined to perform the network response operation; multiple slave nodes can perform the network response operation in parallel; a preset fast channel can be selected and authentication and key exchange can be combined to perform the network response operation; a preset fast channel can be selected, authentication and key exchange can be combined, and multiple slave nodes can perform the network response operation in parallel; authentication and key exchange can be combined, and multiple slave nodes can perform the network response operation in parallel; a preset fast channel can be selected and multiple slave nodes can perform the network response operation in parallel. This invention can reduce the time required for network formation and improve network efficiency through various simplified network formation methods and their combinations.

[0052] In some embodiments, the aforementioned network response operation further includes: Step S1106: Upon receiving the networking invitation sent by the master node, extract the pre-shared key that has been preset locally; Step S1107: The pre-shared key is fed back to the master node so that the master node can authenticate the identity of the slave node.

[0053] In this embodiment, refer to Figure 4 When executing step S110, upon receiving a network invitation from the master node, the pre-shared key, pre-configured locally, can be extracted and sent back to the master node for authentication of the slave node's identity. The pre-shared key is used for slave node authentication and can be a pre-configured network key. By using the pre-shared key, the dynamic key negotiation process can be skipped, shortening the authentication time. The pre-shared key is injected locally through a secure channel, such as a production programming channel. The pre-shared key can be a string or a sequence of numbers. During the network formation process, the master node and slave node share a key in advance. When a slave node receives a network invitation from the master node, it extracts the pre-shared key and sends it back to the master node, which then uses the pre-shared key to verify the slave node's identity.

[0054] For example, slave node A and master node B pre-configure a shared key "abcdef" locally. When master node B sends a network invitation to slave node A, slave node A retrieves the pre-configured shared key "abcdef" and sends it to master node B. Master node B uses the shared key "abcdef" to verify slave node A's identity. If verification is successful, slave node A is allowed to join the network. This invention, through the use of shared keys, can reduce the time required for network key negotiation.

[0055] In some embodiments, the aforementioned network response operation includes: Step S1108: Receive polling network invitations from the master node on multiple channels; Step S1109: Perform network response operations according to the preset frequency hopping sequence.

[0056] In this embodiment, refer to Figure 5 In step S110, the slave node receives polling network invitations from the master node on multiple channels and performs a network response operation according to a preset frame hopping sequence. It can be understood that the master node polls and sends network invitations on multiple channels, and after receiving these invitations, the slave node responds according to a preset frequency hopping sequence, thus avoiding interference from fixed channels. The preset frame hopping sequence can be a predefined rule, ensuring that both the sender and receiver can synchronously change frequencies for effective data transmission. The network response operation involves establishing a network with the master node based on the network invitation.

[0057] It is understandable that when a slave node receives a polling network invitation from the master node on multiple channels, the slave node can select a channel to perform a network response operation according to a preset frequency hopping sequence. By sending network invitations through multiple channels in a polling manner, and responding according to the preset frequency hopping sequence, the slave node can avoid interference from fixed channels and improve the communication quality after networking.

[0058] For example, a slave node has three channels: channel A, channel B, and channel C, with a preset frequency hopping sequence of A→B→C→A→… When the master node sends a polling network invitation to the slave node, the slave node will send a response message on each channel sequentially according to the preset frequency hopping sequence.

[0059] For example, a preset frequency hopping sequence can be represented as: Python # Example frequency hopping sequence generation channels = [11, 15, 20, 26] # 2.4GHz non-WiFi channels current_channel = channels[hash(round(time() / 5) % len(channels))] ``` In some embodiments, the aforementioned process before the slave node receives the networking invitation sent by the master node includes: Step S610: The master node generates a network command data packet with a byte count less than the preset byte count and adds forward error correction (FEC) redundancy to the network command data packet. Step S620: Send the network configuration command data packet to the slave node.

[0060] In this embodiment, refer to Figure 6 Before a slave node receives a network invitation from the master node, the master node generates a network command data packet with a smaller than preset byte count, adds Forward Error Correction (FEC) redundancy to the packet, and then sends it to the slave node. The network command instructs the slave node to form a network with the master node. The byte count can be the number of bytes in the data packet. The preset byte count can be a pre-set number of bytes in the data packet. Forward Error Correction (FEC) redundancy is a technique that detects and corrects errors in data transmission by adding redundancy information.

[0061] Understandably, the master node will generate a network configuration command data packet with a smaller byte size than the preset byte size, and add forward error correction (FEC) redundancy to the network configuration command data packet. By using a small data packet and forward error correction to improve the success rate of a single transmission, it can ensure that the slave node can correctly receive and parse the network configuration command. If an error occurs in the network configuration command data packet during transmission, the slave node can detect and correct the error by adding FEC redundancy, thereby improving the reliability of the network configuration process.

[0062] For example, if the default byte count is 32, the master node will generate a network command data packet with a byte count less than 32, such as a 25-byte packet. Then, the master node will add forward error correction (FEC) redundancy to the network command data packet, ensuring the total byte count remains less than 32. Finally, the master node sends the network command data packet to the slave node. Using small data packets and forward error correction improves the success rate of single transmissions. By adding FEC redundancy, if errors occur during transmission of the network command data packet, the slave node can detect and correct them, thereby improving the reliability of the network setup process.

[0063] It should be noted that generating network command data packets with a smaller byte count than the preset byte count and adding forward error correction (FEC) redundancy to the network command data packets can improve the success rate of single transmissions.

[0064] In some embodiments, the aforementioned process of sending the networking instruction data packet to the slave node includes: Step S710: Receive the network response operation result from the slave node; Step S720: Based on the priority strategy, prioritize some slave nodes to form a network.

[0065] In this embodiment, refer to Figure 7After sending the network formation command data packet to the slave nodes, the master node can receive the network formation response results from the slave nodes and prioritize forming networks with some slave nodes according to a priority policy. The network formation response results can be the outcome of the slave nodes' network formation operations after receiving the master node's network formation command, including information such as whether they successfully joined the network and the network connection quality. The priority policy indicates the network formation priority of each slave node. The priority policy can be a pre-set priority policy, which optimizes resource allocation and processing speed by setting different processing priorities.

[0066] Understandably, during the network formation process, slave nodes will report the network formation response results to the master node, including whether they have successfully joined the network and the quality of the network connection. The master node can prioritize forming a network with some slave nodes based on priority policies, thereby shortening the overall network formation time.

[0067] Specifically, after sending the network formation command data packet, the master node, upon receiving feedback from the slave nodes, will sort the slave nodes according to a priority strategy and select the slave node with the highest priority for network formation. For example, if there are three slave nodes: slave node A, slave node B, and slave node C, with slave node A having the highest priority, followed by slave node B, and then slave node C, the master node, upon receiving feedback from the slave nodes, will prioritize selecting slave node A for network formation, then slave node B, and finally slave node C.

[0068] Prioritization strategies can also include emergency measures, mid-term optimizations, and long-term improvements. Emergency measures could involve deploying dynamic wake-up and backoff algorithms and performing firmware hot updates within 24 hours. Mid-term optimizations could involve simplifying the network setup process and enabling PSK pre-configured keys within a week. Long-term improvements could involve hardware upgrades within a month to support frequency hopping networking and instantaneous wake-up functionality.

[0069] In some embodiments, the aforementioned execution of prioritizing networking with multiple core slave nodes according to a priority policy includes: using the slave node with priority networking as a subnet coordinator, and forwarding networking invitation beacons to slave nodes that have not yet joined the network via the subnet coordinator.

[0070] In this embodiment, the slave node that prioritizes network formation can act as the subnet coordinator, and the subnet coordinator forwards the network formation invitation beacon to the slave nodes that have not yet joined the network. The subnet coordinator can be a key node responsible for managing and organizing the communication of other devices in the network during the network formation process.

[0071] It is understandable that prioritizing the network formation by using the slave node as the subnet coordinator, and then forwarding the network formation invitation beacon to the slave nodes that have not yet joined the network through the subnet coordinator, can help the slave nodes that have not yet joined the network to quickly discover the network and shorten the network formation time.

[0072] For example, consider four slave nodes: Slave Node A, Slave Node B, Slave Node C, and Slave Node D. Slave Node A has the highest priority, followed by Slave Node B, while Slave Node C and Slave Node D have the same and lowest priority. By designating Slave Node A, which prioritizes network formation, as the subnet coordinator, and sending network formation invitation beacons to Slave Nodes B, C, and D, and having the priority slave node relay these beacons, it can help unjoined slave nodes quickly discover the network and shorten the overall network formation time for all slave nodes.

[0073] The present invention also proposes a wireless BMS, which includes a master node and multiple slave nodes that wirelessly communicate with the master node. The master node and the slave nodes are capable of executing the wireless BMS networking method described in the embodiments of the present invention.

[0074] This invention also proposes a wireless BMS, see reference. Figure 8 , Figure 8 This is a schematic diagram of the structure of a wireless BMS in the hardware operating environment involved in the embodiments of the present invention.

[0075] The wireless BMS in this embodiment of the invention can be a computing device such as a desktop computer, laptop, handheld computer, or server. Figure 8 As shown, the wireless BMS may include: a processor 1001 (e.g., CPU), a network interface 1004, a user interface 1003, a memory 1005, and a communication bus 1002. The communication bus 1002 is used to enable communication between these components. The user interface 1003 may include a display screen and an input unit, such as a keyboard. Optionally, the user interface 1003 may also include a standard wired interface or a wireless interface. The network interface 1004 may optionally include a standard wired interface or a wireless interface (such as a Wi-Fi interface). The memory 1005 may be high-speed RAM or non-volatile memory, such as a disk drive. Optionally, the memory 1005 may also be a storage device independent of the aforementioned processor 1001.

[0076] Those skilled in the art will understand that Figure 8 The wireless BMS structure shown does not constitute a limitation on the wireless BMS and may include more or fewer components than shown, or combine certain components, or have different component arrangements.

[0077] like Figure 8 As shown, the memory 1005, which serves as a computer storage medium, may include an operating system, a network communication module, a user interface module, and computer programs.

[0078] exist Figure 8 In the wireless BMS shown, the network interface 1004 is mainly used to connect to the backend server and communicate with the backend server; the user interface 1003 is mainly used to connect to the client (user terminal) and communicate with the client; and the processor 1001 can be used to call the computer program stored in the memory 1005. When the computer program is called and executed by the processor 1001, it implements the steps of the wireless BMS networking method described above.

[0079] Based on the computer program proposed in the foregoing embodiments, the present invention also proposes a storage medium storing a computer program, which, when executed by a controller, implements the wireless BMS networking method described in the foregoing embodiments.

[0080] Since both the wireless BMS and the storage medium of the present invention can implement the steps of the above-described wireless BMS networking method, they at least have all the beneficial effects brought about by the technical solutions of the above-described wireless BMS networking method embodiments, which will not be elaborated here.

[0081] In the several embodiments provided in this application, it should be understood that the disclosed methods and apparatus can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative. For instance, the division of modules is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple modules or components may be combined or integrated into another device, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces, or indirect coupling or communication connection between devices or modules, and may be electrical, mechanical, or other forms.

[0082] The modules described as separate components may or may not be physically separate. The components shown as modules may or may not be physical modules; that is, they may be located in one place or distributed across multiple network modules. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs.

[0083] Furthermore, the functional modules in the various embodiments of the present invention can be integrated into one processing module, or each module can exist physically separately, or two or more modules can be integrated into one module. The integrated modules described above can be implemented in hardware or as software functional modules.

[0084] If the integrated module is implemented as a software functional module and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0085] The above description is only a part or preferred embodiment of the present invention. Neither the text nor the drawings should limit the scope of protection of the present invention. All equivalent structural transformations made using the content of the present invention specification and drawings under the overall concept of the present invention, or direct / indirect applications in other related technical fields, are included within the scope of protection of the present invention.

Claims

1. A networking method for a wireless BMS, wherein the wireless BMS includes a master node and multiple slave nodes that wirelessly communicate with the master node, characterized in that, The networking method of the wireless BMS includes: When the slave node receives a network invitation sent by the master node, it shortens the default wake-up period to a preset wake-up period and performs a wake-up operation and a network response operation within the preset wake-up period. The duration of the default wake-up period is longer than the duration of the preset wake-up period. The default wake-up period is the default period set when the slave node switches from a dormant state to a working state when it has not received a network invitation sent by the master node. The preset wake-up period is the period set in advance when the slave node switches from a dormant state to a working state when it receives a network invitation sent by the master node. The wake-up operation is to switch the slave node from a dormant state to a working state, and the network response operation is to form a network with the master node according to the network invitation. If network formation fails, the preset wake-up period will be maintained and network response operations will continue to be performed; If network formation fails continuously, the duration of the preset wake-up period will be extended. If the number of consecutive network failures reaches the preset number, then the wake-up operation and network response operation will be performed according to the default wake-up cycle. If the network is successfully established, the default wake-up cycle will be restored.

2. The networking method for a wireless BMS according to claim 1, characterized in that, The wake-up operation includes: When the master node receives a wake-up beacon broadcast by the master node, which instructs the slave node to switch from a dormant state to a working state and contains network time window information, the master node parses the wake-up beacon to obtain the network time window, which includes the start and end times of the network formation between the slave node and the master node. Each slave node synchronously performs a wake-up operation within the network time window.

3. The networking method for a wireless BMS according to claim 2, characterized in that, The network response operation includes: Within the network time window, each slave node competes to access the network channel of the master node.

4. The networking method for a wireless BMS according to claim 1, characterized in that, The network response operation includes: The network response operation is performed by selecting a preset fast channel, wherein the preset fast channel is the channel with the least communication latency; and / or The network response operation combines authentication and key exchange, where authentication verifies the slave node device ID, and key exchange negotiates the communication encryption key between the master node and the slave node; and / or Multiple slave nodes execute the network response operation in parallel.

5. The networking method for a wireless BMS according to claim 4, characterized in that, The network response operation also includes: Upon receiving a network invitation from the master node, the pre-shared key, which is a key used to authenticate the slave node, is extracted locally. The pre-shared key is fed back to the master node so that the master node can authenticate the identity of the slave node.

6. The networking method for a wireless BMS according to any one of claims 1 to 5, characterized in that, The network response operation includes: Receive polling network invitations from the master node on multiple channels; The network response operation is executed according to the preset frequency hopping sequence.

7. The networking method for a wireless BMS according to claim 6, characterized in that, Before the slave node receives the network invitation sent by the master node, the following steps are included: The master node generates a networking instruction data packet with a byte count less than a preset byte count, and adds forward error correction (FEC) redundancy to the networking instruction data packet. The networking instruction is used to instruct the slave node to form a network with the master node. The network configuration command data packet is sent to the slave node.

8. The networking method for a wireless BMS according to claim 7, characterized in that, After executing the step of sending the network configuration command data packet to the slave node, the following is included: Receive the network response operation results fed back from the node; The network is configured based on a priority strategy that prioritizes certain slave nodes, with the priority strategy used to indicate the network priority of each slave node.

9. The networking method for a wireless BMS according to claim 8, characterized in that, The execution of the priority strategy for networking with multiple core slave nodes includes: The slave node that prioritizes network formation is used as the subnet coordinator, and the network formation invitation beacon is forwarded to the slave nodes that have not yet joined the network through the subnet coordinator.

10. A wireless BMS, the wireless BMS comprising a master node and a plurality of slave nodes wirelessly communicating with the master node, characterized in that, The master node and the slave node are capable of executing the networking method of the wireless BMS according to any one of claims 1 to 9.

Images