Low power wireless data acquisition system

Abstract

The application discloses a low-power wireless data collection system, and relates to the technical field of wireless communication, which comprises the following steps: a slave machine is woken up when reaching a preset wake-up moment, collects data and sends a current collection data packet to a host machine; the host machine is used for receiving the current collection data packet and returning a next wake-up moment to the slave machine based on the current collection data packet; the slave machine is also used for updating the wake-up setting of the slave machine according to the next wake-up moment if the next wake-up moment returned by the host machine is received, closing the working power supply of a wireless module and entering a sleep state, and woken up again at the next wake-up moment to repeatedly execute the operations of wake-up, data collection and current collection data packet sending; the slave machine is also used for closing the working power supply of the wireless module and entering the sleep state after executing an abnormal processing operation if the next wake-up moment is not received, and woken up again after the sleep is ended to repeatedly execute the operations of wake-up, data collection and current collection data packet sending. The application can effectively reduce power consumption.

Description

Technical Field

[0001] This application relates to the field of wireless communication technology, and in particular to a low-power wireless data acquisition system. Background Technology

[0002] With the development trend of refined management in industrial production, it is necessary to connect the data of intelligent devices that have been installed on site but not connected to the management system to the system. If wired communication is used, subsequent wiring construction and laying of communication cables are required. During the construction process, it is often necessary to shut down the intelligent devices running on site, which can easily cause production stoppages and economic losses.

[0003] To solve the construction challenges of wired cabling, wireless communication is used for data interaction between on-site intelligent devices and management systems, while battery power supply further solves the power supply problem of on-site wireless data acquisition devices, becoming the mainstream power supply method for such devices.

[0004] To improve standby time and reduce the cost and frequency of subsequent battery replacements, smart devices are designed with low power consumption. However, due to the limitations of existing low power consumption technology solutions, the actual power reduction effect is not good, and it is still impossible to effectively reduce the frequency of battery replacement and maintenance, making it difficult to meet the needs of long-term stable use in the field. Summary of the Invention

[0005] The purpose of this application is to provide a low-power wireless data acquisition system that can effectively reduce power consumption.

[0006] To achieve the above objectives, this application provides the following solution: In a first aspect, this application provides a low-power wireless data acquisition system, the system comprising: a slave device and a master device; The slave device is used to wake up when a preset wake-up time is reached, collect data, and send the currently collected data packet to the host. The host is configured to receive the currently collected data packet and, based on the currently collected data packet, return the next wake-up time to the slave device; The slave device is also configured to, if it receives the next wake-up time returned by the master device, update its own wake-up settings according to the next wake-up time, turn off the working power of the wireless module and enter a sleep state, and wake up again at the next wake-up time to repeat the operations of wake-up, data collection and sending the currently collected data packet; The slave device is also configured to, if it does not receive the next wake-up time, perform an exception handling operation, turn off the power supply of the wireless module and enter a sleep state, and wake up again after the sleep state ends to repeat the wake-up, data collection and sending of the currently collected data packet operations.

[0007] According to the specific embodiments provided in this application, the following technical effects are disclosed: This application provides a low-power wireless data acquisition system. The system utilizes a dynamic wake-up negotiation mechanism between the slave and master devices, enabling the slave device to flexibly adjust its sleep cycle based on the next wake-up time issued by the master device based on the currently acquired data. This mechanism breaks the limitations of traditional fixed-cycle wake-up, allowing the slave device to extend its sleep time according to the master device's instructions when there are no significant changes in data or no acquisition needs. This avoids ineffective power consumption caused by fixed high-frequency wake-ups, significantly improves the device's standby energy efficiency, and effectively extends the continuous working time after a single power supply. Attached Figure Description

[0008] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0009] Figure 1 This is a schematic diagram of a low-power wireless data acquisition system according to an exemplary embodiment; Figure 2 This is a flowchart illustrating a low-power wireless data acquisition method according to an exemplary embodiment. Figure 1 ; Figure 3 This is a flowchart illustrating a low-power wireless data acquisition method according to an exemplary embodiment. Figure 2 . Detailed Implementation

[0010] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0011] To make the above-mentioned objectives, features and advantages of this application more apparent and understandable, the application will be further described in detail below with reference to the accompanying drawings and specific embodiments.

[0012] Figure 1 This is a schematic diagram illustrating the structure of a low-power wireless data acquisition system according to an exemplary embodiment, such as... Figure 1 As shown, the system includes: a slave device and a master device; The slave device is used to wake up when a preset wake-up time is reached, collect data, and send the currently collected data packet to the host. The host is configured to receive the currently collected data packet and, based on the currently collected data packet, return the next wake-up time to the slave device; The slave device is also configured to, if it receives the next wake-up time returned by the master device, update its own wake-up settings according to the next wake-up time, turn off the working power of the wireless module and enter a sleep state, and wake up again at the next wake-up time to repeat the operations of wake-up, data collection and sending the currently collected data packet; The slave device is also configured to, if it does not receive the next wake-up time, perform an exception handling operation, turn off the power supply of the wireless module and enter a sleep state, and wake up again after the sleep state ends to repeat the wake-up, data collection and sending of the currently collected data packet operations.

[0013] The slave-side wireless data acquisition module, which is independently powered by a battery, is a terminal execution unit deployed in industrial sites. It requires no external power supply or on-site wiring. Its core functions include data acquisition, wireless data transmission and reception, wake-up / sleep control, and wireless module power management. It is a key carrier for achieving low-power, on-site data acquisition in the system.

[0014] The host is the core management device of the system, deployed on the side of the industrial production management system. It is the core of the entire wireless data acquisition system for command control and data reception, and has two core functions: receiving acquired data and dynamically calculating and issuing the next wake-up time.

[0015] Specifically, after the slave device reaches the preset wake-up time, it switches from sleep mode to working mode. First, it collects data from the field, generating and sending a current data packet (i.e., the field data within this wake-up cycle) to the master device. The master device receives the current data packet uploaded by the slave device in real time. Based on factors such as the field equipment status and production management requirements corresponding to this current data packet, it calculates and returns the next wake-up time to the slave device (i.e., the end time of the slave device's current sleep state, and also the start time of the next data collection). After successfully receiving the next wake-up time returned by the master device, the slave device immediately updates its wake-up settings (setting the next wake-up time to the new preset wake-up time), shuts down the power supply of the wireless module (completely cutting off the power consumption source of the wireless module, unlike the traditional sleep-only, standby listening mode), and then enters a deep sleep state. The slave device waits in deep sleep until the new preset wake-up time arrives, then wakes up again, repeating the process: "Collect data - Send data packet - Receive wake-up time - Update settings - Power off module and go into sleep". The operation forms a stable normal data acquisition closed loop. If the slave device fails to receive the next wake-up time from the host due to network interference, channel congestion, or other reasons after sending the current acquisition data packet, this disclosure also provides fault-tolerant processing logic to ensure that the system can maintain low power consumption during communication abnormalities and resume acquisition after the fault is cleared. The steps are as follows: After the slave device completes the field data acquisition and sends the current acquisition data packet to the host, if it does not receive the next wake-up time from the host within the preset response time, the system triggers the abnormal handling mechanism; the slave device performs abnormal handling operations according to preset rules; after the slave device completes the preset abnormal handling operations, if it still does not receive the next wake-up time from the host, it shuts down the power supply of the wireless module and enters a deep sleep state; the slave device automatically wakes up after the fixed sleep time ends, and after waking up, it directly repeats the operations of acquiring data and sending the current acquisition data packet, and tries to re-establish normal interaction with the host. If the interaction is restored, it enters the normal closed loop; if it is still not restored, the abnormal handling closed loop is triggered again.

[0016] Compared with related technologies, this disclosure utilizes a dynamic wake-up negotiation mechanism between the slave and master devices, enabling the slave device to flexibly adjust its sleep cycle based on the next wake-up time issued by the master based on the currently collected data. This mechanism breaks the limitations of traditional fixed-cycle wake-up, allowing the slave device to extend its sleep time according to the master's instructions when there are no significant changes in data or no collection needs. This avoids the ineffective power consumption caused by fixed high-frequency wake-ups, significantly improves the standby energy efficiency of the device, and effectively extends the continuous working time after a single power supply.

[0017] Meanwhile, this disclosure sets up an exception handling entry for the case where the next wake-up time is not received, ensuring that a low-power state can still be maintained by shutting down the wireless module and entering sleep mode when communication is abnormal.

[0018] In one embodiment, in the aspect where the wireless module's power is turned off and it enters a sleep state after the exception handling operation is performed, the slave device is specifically used for: The currently collected data packet is retransmitted. If the next wake-up time is not received after a first preset number of retransmissions, the power supply of the wireless module is turned off and the module goes into sleep mode for a first preset duration.

[0019] Specifically, when the slave device wakes up at the preset wake-up time and sends the currently collected data packet, if it fails to receive the next wake-up time from the master within the expected time, an exception handling procedure is triggered. The slave device first initiates a retransmission mechanism to retransmit the currently collected data packet. After each retransmission, the slave device waits for a preset receive window to listen for whether the master returns the next wake-up time.

[0020] Set an upper limit for the number of retransmissions, namely the first preset number (e.g., 3 times, 5 times, or other values ​​set according to the actual application scenario). In each retransmission attempt, the slave device keeps the wireless module in an active state to complete the transmission of data packets and subsequent listening.

[0021] If the slave device still does not receive the next wake-up time from the master device after the first preset number of retransmissions, the slave device will no longer perform unlimited retransmissions, but will instead perform the following operations: Immediately cut off the power supply to the wireless module to put it into a zero-power state, so as to avoid unnecessary power consumption caused by standby monitoring; The slave device enters sleep mode, and the main control unit and non-essential peripherals are powered off or enter low-power mode for a duration of the first preset time (e.g., 5 minutes, 10 minutes or other durations set according to the application scenario). After the first preset time period ends, the slave device will automatically wake up and re-execute the normal process of waking up, collecting data, and sending the currently collected data packet.

[0022] In scenarios of transient communication failures, this disclosure provides multiple transmission opportunities for data packets through a limited number of retransmissions, ensuring reliable data delivery as much as possible without excessive power consumption and avoiding data loss caused by abandoning reporting due to a single communication failure. In scenarios of persistent communication failures (such as network paralysis), by setting an upper limit on the number of retransmissions and promptly shutting down the wireless module to enter sleep mode, power consumption caused by invalid retransmissions is effectively avoided. By setting a first preset sleep period, a time window is provided for the autonomous recovery of the communication link. When the slave device wakes up again, the communication environment may have returned to normal (e.g., the interference source has disappeared), thus realizing the device's self-recovery capability.

[0023] In practical applications, the specific values ​​of the first preset number of times and the first preset duration can be configured according to the application scenario: For scenarios with high real-time requirements and frequent data changes, a smaller first preset number of times (e.g., 2-3 times) and a shorter first preset duration (e.g., 1-5 minutes) can be set to restore data acquisition as quickly as possible; For scenarios where data changes slowly and power consumption requirements are strict, a moderate first preset number of times (e.g., 3-5 times) and a longer first preset duration (e.g., 10-30 minutes) can be set to maximize energy saving. For applications deployed in remote areas and difficult to maintain, a larger initial preset number of times (e.g., 5-8 times) and a longer initial preset duration (e.g., 30-60 minutes) can be set to extend battery life as much as possible while ensuring data reliability.

[0024] All of the above parameters can be configured remotely by the host or preset in the firmware of the slave device, and can be dynamically adjusted according to the actual operating conditions on site.

[0025] In one embodiment, the slave device is further configured to send a power-on data packet to the master device after detecting power-on before waking up at a preset wake-up time; The host is also configured to receive the power-on data packet and return the initial wake-up time to the slave device based on the power-on data packet; The slave device is also used to set its own wake-up time according to the initial wake-up time after receiving the initial wake-up time, and to enter a sleep state after turning off the working power of the wireless module, and to wake up at the initial wake-up time to perform wake-up, data collection and sending the currently collected data packet. The slave device is also configured to retransmit the power-on data packet when it does not receive the initial wake-up time, and if it still does not receive the initial wake-up time after retransmission a second preset number of times, turn off the power supply of the wireless module and go into sleep for a second preset period of time, and wake up again after the sleep period ends to re-execute the step of sending the power-on data packet to the host.

[0026] When the slave device detects power-on (e.g., battery installation, hardware reset, watchdog restart), it first initializes the wireless module and related peripherals, but does not immediately begin periodic data acquisition. Instead, it sends a dedicated power-on data packet to the host. This power-on data packet reports to the host that the slave device is online and can carry information such as slave device identifier, device type, firmware version, and current battery level, allowing the host to register the device and configure its parameters.

[0027] After receiving the power-on data packet from the slave device, the master device allocates an initial wake-up time to the slave device according to the current overall system strategy. The master device returns the determined initial wake-up time to the slave device via a response data packet. The determination of this initial wake-up time can take into account various factors, such as: the current network load to avoid congestion caused by a large number of slave devices powering on simultaneously; the battery level information reported by the slave device, where a longer initial wake-up interval can be allocated when the battery level is low; and the slave device type and application scenario, as different initial wake-up times are allocated to devices with different sampling frequency requirements.

[0028] If the slave device successfully receives the initial wake-up time returned by the master device, then perform the following operations: Based on the received initial wake-up time, the slave device sets its own first wake-up time. For example, if the current time is T0 and the initial wake-up time is T0+Δt, then the slave device is set to wake up after Δt.

[0029] After the settings are completed, the slave device shuts down the power supply of the wireless module, cutting off its power supply circuit and putting the wireless module into a zero-power state; at the same time, the slave main control unit and non-essential peripherals enter a low-power sleep mode.

[0030] When the set initial wake-up time is reached, the slave device automatically wakes up. After waking up, it performs the normal workflow of waking up, collecting data, and sending the current data collection data packet. In each subsequent cycle, it continuously obtains the next wake-up time through a dynamic negotiation mechanism of waking up, collecting data, and sending the current data collection data packet.

[0031] If the slave device sends a power-on data packet but does not receive the initial wake-up time from the master device within the preset waiting window, an exception handling procedure is triggered: The slave device initiates a retransmission mechanism to resend the power-on data packets. After each retransmission, the slave device waits for a preset receive window, listening for whether the master device returns to the initial wake-up time.

[0032] Set an upper limit for the number of retransmissions, i.e., a second preset number of times (e.g., 3 times, 5 times, etc.). This number can be the same as the first preset number in regular communication, or it can be set to a different value depending on the importance of the power-on phase.

[0033] If the slave device still does not receive the initial wake-up time from the master device after the second preset number of retransmissions, it determines that the current network is unavailable or the master device is unresponsive. In this case, the slave device will no longer perform unlimited retransmissions, but will instead perform the following operations: Turn off the power supply of the wireless module; Enter sleep mode and continue for the second preset duration (e.g., 5 minutes, 10 minutes, etc.). After the second preset time period ends, the slave device will automatically wake up and re-execute the step of sending a power-on data packet to the master device.

[0034] This embodiment introduces a wake-up time negotiation mechanism with the host during the power-on initialization phase, enabling the slave device to obtain an initial wake-up time that matches the system requirements. This avoids invalid wake-ups and energy waste that may be caused by using a default fixed period. At the same time, in response to possible communication anomalies during the power-on phase, a backoff mechanism is set up for limited retransmissions and forced sleep for a preset duration after retransmission failure. This allows the slave device to autonomously enter sleep mode and wait when the network is unavailable. After the network is restored, it will retry registration, realizing the device's autonomous recovery capability and ensuring that the slave device can reliably access the system and enter a low-power operation mode.

[0035] In one embodiment, the slave device is further configured to measure the current wireless signal quality after waking up and before sending the current data acquisition packet; if the signal quality is lower than a first preset threshold, the current data acquisition packet is delayed, and a detection interval shorter than the current wake-up interval is set. After the detection interval, the slave device is woken up again to remeasure the signal quality until the signal quality meets the requirements before sending the current data acquisition packet. The slave device is also used to record the signal quality measurement value each time it is woken up, forming a signal quality history trajectory. If the signal quality measured multiple times in a row is lower than the first preset threshold, it actively sends a signal quality alarm message to the host. The signal quality alarm message includes the signal quality history trajectory. The host is also configured to receive the signal quality alarm, determine whether the signal quality is persistent based on the historical signal quality trajectory, and if so, adjust the next wake-up time of the slave device and return the adjusted next wake-up time to the slave device.

[0036] In wireless communication environments, signal quality is a key factor affecting communication success rate and power consumption. Traditional solutions often attempt communication directly when the signal is poor, and then retransmit after failure. This mode leads to multiple invalid transmissions and receptions when the signal continues to deteriorate, resulting in wasted power. This embodiment provides a proactive prediction mechanism that determines the signal before transmitting, specifically including the following steps: Upon each wake-up and before sending the currently collected data packet, the slave device first measures the current wireless signal quality. Measurement metrics may include parameters reflecting the communication link quality, such as received signal strength indication, signal-to-noise ratio, and bit error rate. The slave device then compares the measured values ​​with a preset first threshold.

[0037] If the measured value reaches or exceeds the first preset threshold, it indicates that the current communication conditions are good and the slave device is normally executing the data packet sending process.

[0038] If the measured value is lower than the first preset threshold, it indicates that the current communication conditions are poor. Forcing a transmission may result in communication failure and subsequent retransmissions. In this case, the slave device does not immediately send data packets, but instead performs the following operations: The data transmission task is temporarily suspended; Set a detection interval shorter than the current regular wake-up interval (for example, if the preset wake-up interval based on the next wake-up time is 10 minutes, the detection interval can be set to 30 seconds or 1 minute). After the wireless module is turned off, it enters sleep mode; The system is woken up again after the detection interval ends to remeasure the signal quality. Repeat the above measurement-judgment-delay-probe cycle until a measurement shows that the signal quality meets the requirements, at which point the slave device executes the transmission of data packets.

[0039] Each time the slave device wakes up to measure signal quality, it records the measurement value, forming a signal quality history. If the slave device detects that the signal quality is lower than a first preset threshold for multiple consecutive measurements (e.g., 3 or 5 consecutive measurements), it determines that there may be a persistent signal degradation problem in the current area. At this time, the slave device no longer waits passively, but actively sends a signal quality alarm message to the master device. This alarm message carries the signal quality history for the master device to make diagnostic decisions.

[0040] After receiving a signal quality alarm from the slave device, the master device determines whether the signal degradation is persistent based on the historical signal quality trajectory. The criteria for this determination may include: duration of degradation, degree of degradation, and whether there is a periodic pattern. If persistent signal degradation is determined, the master device adjusts the wake-up time, reallocating a time window for the slave device that may avoid the current interference source. The master device then sends the adjusted next wake-up time or other configuration parameters back to the slave device, which continues operating according to the new parameters.

[0041] This embodiment achieves proactive adaptation to complex wireless environments by constructing a closed-loop mechanism that combines slave-side signal quality prediction with master-side collaborative adjustment. The signal quality prediction mechanism avoids invalid transmissions on poor-quality channels from the source, reducing the probability of communication failures and retransmissions. The historical trajectory recording and alarm mechanism enables the slave to identify persistent signal degradation and seek master intervention. The master-side collaborative adjustment mechanism optimizes the slave's operating parameters at the system level, fundamentally improving communication conditions.

[0042] In one embodiment, the host is further configured to execute a power grading strategy based on the remaining power of the slave device to determine the next wake-up time, the power grading strategy including: A first power threshold and a second power threshold are preset, with the first power threshold being higher than the second power threshold; if the remaining power is higher than the first power threshold, the next wake-up time is determined and sent according to a first sampling frequency; if the remaining power is between the first power threshold and the second power threshold, the next wake-up time is determined and sent according to a second sampling frequency lower than the first sampling frequency; if the remaining power is lower than the second power threshold, a power warning command is sent to the slave device, and the completion wake-up time of the last data report of the slave device is determined and sent. The slave device is also used to receive the power warning command, and after completing the next data report at the wake-up time, it turns off the working power of the wireless module and enters deep sleep mode until it receives the active wake-up command issued by the host and then wakes up to work.

[0043] The system presets a first battery level threshold and a second battery level threshold, with the first threshold being higher than the second. For example, the first battery level threshold can be set to 70%, and the second threshold can be set to 20%. These two thresholds divide the battery status into three intervals: High battery range: Remaining battery level > first battery threshold; Medium battery level range: First battery level threshold ≥ Remaining battery level ≥ Second battery level threshold; Low battery range: Remaining battery level < second battery threshold; When the slave device's remaining battery power is higher than the first battery power threshold, it indicates that the battery has sufficient energy. The master device then determines and sends the next wake-up time according to the first acquisition frequency. The first acquisition frequency can be set to a relatively high frequency (e.g., wake-up once every 5 minutes) to ensure the density and real-time performance of data acquisition.

[0044] When the remaining battery power of the slave device is between the first and second battery power thresholds, it indicates that the battery has been partially depleted and power conservation is necessary. The master device determines and sends the next wake-up time at a second sampling frequency lower than the first sampling frequency. The second sampling frequency can be set to a lower frequency (e.g., wake-up every 15 minutes) to extend battery life while sacrificing some real-time performance.

[0045] When the slave device's remaining battery power falls below the second battery threshold, it indicates that the battery is about to run out and emergency measures are required. The master device will then perform the following actions: Send a power warning command to the slave device to inform it that the power level has entered a dangerous range; At the same time, the completion and wake-up time of the last data report of the slave device is determined and issued, that is, the slave device is allowed to perform one last routine data report.

[0046] After receiving the power warning command, the slave device completes its final data report according to the current wake-up completion time. After reporting, the slave device performs the following operations: Turn off the power supply of the wireless module; Enter deep sleep mode. In deep sleep mode, the slave device retains only extremely low-power wake-up reception capability (such as through an independent RTC or low-power wake-up circuit), while the master control unit and other peripherals are powered off; During deep sleep, the slave device will not perform any periodic wake-up operations until it receives an active wake-up command from the master device, at which point it will resume normal operation.

[0047] This embodiment achieves refined power consumption management throughout the entire lifecycle of the slave device's battery through a power level-based strategy: high-frequency data acquisition is maintained during high-battery periods to ensure data quality; automatic frequency reduction is implemented during medium-battery periods to extend battery life; and early warnings are sent and deep sleep mode is initiated during low-battery periods to prevent data loss and permanent device downtime due to sudden battery depletion. This mechanism allows maintenance personnel to plan battery replacements in advance based on early warnings, ensuring data continuity while reducing maintenance costs.

[0048] In one embodiment, The host is further configured to execute a congestion avoidance strategy based on the current network load state to adjust and determine the next wake-up time, the congestion avoidance strategy including: Monitor the current network channel occupancy rate; If the channel occupancy rate exceeds the preset channel congestion threshold, the host will randomly scatter the wake-up times of all slaves in the current period on the time axis, so that the wake-up times of at least two slaves that were originally woken up at the same time are staggered, and the adjusted wake-up times will be sent to the corresponding slaves respectively.

[0049] In industrial IoT scenarios with a large number of slave devices, if the wake-up times of all slave devices are too concentrated, it may lead to channel congestion, data collisions, and a surge in retransmissions, which not only reduces the communication success rate but also increases overall energy consumption. This embodiment provides a congestion avoidance strategy that achieves load balancing of wake-up times through dynamic scheduling of the master device.

[0050] The host continuously monitors the current network channel occupancy. Channel occupancy can be calculated by the ratio of idle time to total channel time, or indirectly assessed by counting the number of data packets per unit time. The host presets a channel congestion threshold (such as 60%, 70%, etc.) as a benchmark for judging whether the network is congested.

[0051] When a host detects that the channel occupancy rate exceeds the preset channel congestion threshold, it determines that the current network is in a congested state and needs to execute a congestion avoidance strategy.

[0052] The host obtains the current wake-up time configuration of all slave devices within the current period and identifies those slave devices with the same or very close wake-up times. Subsequently, the host randomly distributes the wake-up times of these slave devices along the timeline, staggering the working periods of slave devices that might otherwise wake up simultaneously and compete for the channel. For example, if 10 slave devices are originally set to wake up at the top of the hour, the host can randomly assign them to different time points within 0-5 minutes after the top of the hour.

[0053] The master unit sends the adjusted wake-up time to the corresponding slave units. After receiving the new wake-up time, each slave unit updates its own wake-up settings and then wakes up and works according to the new time.

[0054] This embodiment achieves adaptive load balancing in a large-scale slave network through a host-initiated congestion avoidance strategy: when the network load is too high, the host effectively reduces the probability of channel conflicts and data collisions caused by multiple concurrent devices by randomly scattering wake-up times; it reduces the number of retransmissions and backoff waiting time caused by congestion, thereby reducing the overall network energy consumption; at the same time, this strategy does not require coordination between slave devices and is completely controlled centrally by the host, making it simple to implement and highly effective.

[0055] In one embodiment, the host is further configured to determine the next wake-up time according to a self-learning adjustment step, the self-learning adjustment step including: Record the data change patterns of the slave device within the historical period; When the data reported by the slave device is within the preset fluctuation range for multiple consecutive times, the master device automatically extends the wake-up interval of the slave device; When the data fluctuation reported by the slave device exceeds a preset range, the master device automatically shortens the wake-up interval of the slave device.

[0056] Industrial field data often exhibits patterns: some periods show stable data with no change, while others see frequent fluctuations. Traditional fixed-period data collection methods cannot adapt to these dynamic changes, resulting in ineffective wake-ups during stable periods and potentially missing critical data during fluctuating periods. This embodiment provides a self-learning adjustment mechanism, enabling the host to dynamically optimize the wake-up interval based on the historical patterns of data reported by the slave devices.

[0057] The master records the data change patterns of each slave device within a historical period, including the data value reported each time, the magnitude of change, the frequency of change, and other information, forming a data feature profile for each slave device.

[0058] When the host detects that the data reported by a slave device multiple times consecutively is within a preset fluctuation range (e.g., the temperature value changes no more than ±0.5℃ for 10 consecutive times), it determines that the monitored object of the slave device is currently in a stable period. At this time, the host automatically lengthens the wake-up interval of the slave device, switching it from high-frequency acquisition mode to low-frequency monitoring mode, reducing the number of invalid wake-ups.

[0059] When the host detects that the data fluctuation reported by a slave device exceeds a preset range (for example, a sudden increase of 5°C in temperature), it determines that the monitored object has entered an active or abnormal period and needs to increase the monitoring density. At this time, the host automatically shortens the wake-up interval of the slave device, enabling it to report subsequent data more frequently and capture changing trends in a timely manner.

[0060] The above adjustment process continues. When the slave device enters a stable period, the interval is lengthened, and when it enters a fluctuating period, the interval is shortened. The master device continuously learns and optimizes the wake-up frequency of each slave device so that it always matches the data change pattern.

[0061] This embodiment achieves adaptive optimization of the wake-up interval based on data change patterns through a host self-learning mechanism: automatically reducing the frequency during periods of stable data to maximize energy conservation; and automatically increasing the frequency during periods of fluctuating data to ensure that critical data is not missed. This mechanism requires no manual intervention; the system automatically learns and adapts to the changing characteristics of the field data, achieving an intelligent balance between data acquisition quality and power consumption control.

[0062] In one embodiment, the slave device is further configured to compare the collected data with a preset emergency threshold after collecting the data; if the data exceeds the emergency threshold, it is determined to be emergency data and an emergency identifier is marked in the current collected data packet. The host is also used to receive the currently collected data packet, detect whether it contains an emergency identifier, and if it contains an emergency identifier, the host automatically shortens the wake-up interval of the slave device.

[0063] In industrial field data acquisition, different data have different levels of importance and timeliness requirements. In conventional periodic acquisition modes, regardless of data urgency, the slave device operates at a fixed wake-up interval. This one-size-fits-all approach has two problems: First, in the event of an emergency, if acquisition continues at the original interval, critical data changes may be missed due to the low sampling frequency, resulting in abnormal trends not being captured in time. Second, if high-frequency acquisition is consistently used to cope with potential emergencies, unnecessary energy waste occurs, shortening equipment battery life.

[0064] To address the aforementioned issues, this embodiment provides a dynamic wake-up interval adjustment mechanism based on data urgency. This mechanism enables the slave and master devices to work collaboratively, automatically increasing the data acquisition frequency when urgent data is detected, and then reverting to normal mode once the event subsides. Specifically, it includes the following steps: The slave device wakes up at each preset wake-up time and collects on-site data. After collection, the slave device compares the currently collected data with a preset emergency threshold. The emergency threshold can be preset according to different application scenarios, for example: Temperature monitoring scenario: Set a high temperature alarm threshold, such as 80℃; Pressure monitoring scenario: Set a pressure over-limit threshold, such as 1.2 times the rated pressure; Vibration monitoring scenario: Set a vibration amplitude threshold, such as 50% above the normal range.

[0065] If the collected data does not exceed the emergency threshold, it is considered normal data, and the slave device sends the data packet according to the normal procedure without adding a special identifier. If the collected data exceeds the emergency threshold, it is considered emergency data, and the slave device adds an emergency identifier to the current collected data packet. The emergency identifier can be a specific flag bit in the data packet header or a specific encoded value in the data field.

[0066] The slave device sends the currently acquired data packet with an emergency flag (or without a flag) to the master device. After sending, the slave device waits for the master device to return the next wake-up time.

[0067] After receiving the current data packet sent by the slave device, the host parses the data packet content and checks whether it contains an emergency flag.

[0068] If the data packet does not contain an emergency identifier: the current data is determined to be normal data, and the host determines the next wake-up time according to the normal strategy (such as based on factors such as power consumption and network load) and returns it to the slave.

[0069] If the data packet contains an emergency flag, it indicates an emergency has occurred in the slave's monitoring area, requiring increased monitoring density. In this case, the master automatically adjusts its strategy, shortening the wake-up interval for that slave. For example: The normal wake-up interval is 15 minutes. After an emergency occurs, the host will adjust the next wake-up time to 5 minutes. If the urgency level is further classified, different reduction ranges can be set according to different urgency levels.

[0070] The master will send the adjusted next wake-up time (i.e., a shorter interval) back to the slave.

[0071] After receiving the next wake-up time from the master, the slave device enters sleep mode according to the new wake-up settings and wakes up again at the specified time to continue data acquisition and reporting. As long as the data continuously reported by the slave device is still determined to be urgent (i.e., still exceeds the urgent threshold), the master device can continue to maintain the short interval mode.

[0072] Once the data subsequently reported by the slave device returns to normal (i.e., below the emergency threshold), the slave device will no longer add an emergency flag. After the master device detects that there is no emergency flag in the data packet, it determines that the emergency has subsided and gradually or immediately restores the wake-up interval to the normal value, so that the system returns to the energy-saving operation mode.

[0073] In practical applications, parameters such as emergency threshold, regular wake-up interval, and emergency wake-up interval can be flexibly configured according to specific scenarios: For monitoring high-risk equipment, a lower emergency threshold can be set to make the system more sensitive to anomalies; For rapidly changing process parameters, a shorter emergency interval (such as 1 minute) can be set to ensure that the change trajectory is completely recorded; For parameters that change slowly, the regular interval can be set to a longer interval (e.g., 30 minutes), while the emergency interval can be set to a moderate interval (e.g., 10 minutes), taking into account both response speed and energy consumption.

[0074] The above parameters can be configured remotely by the host or preset in the slave device and dynamically optimized according to the on-site operating conditions.

[0075] This embodiment introduces a dynamic wake-up interval adjustment mechanism based on data urgency, achieving rapid response to emergency events and adaptive monitoring density enhancement. When emergency data is detected, the host automatically shortens the slave wake-up interval, enabling the system to collect data at a higher frequency during critical windows, closely tracking anomaly trends and avoiding the loss of critical information due to insufficient sampling frequency. Once the emergency subsides, the system automatically returns to the normal interval and continues operating in low-power mode. This mechanism ensures the reliability of emergency event monitoring while maximizing daily operating power savings, achieving an intelligent balance between monitoring quality and energy consumption control.

[0076] In one embodiment, the slave device is further configured to record the received signal strength indication value and signal-to-noise ratio of the current communication after each successful reception of the next wake-up time, and to statistically analyze the communication success rate within a preset period to form a communication quality profile. The slave device is also used to actively send a communication quality abnormality alarm to the host when the communication success rate is lower than a preset success rate threshold, and the communication quality abnormality alarm carries the communication quality file. The host is also used to receive the communication quality abnormality alarm and determine the communication environment level of the area where the slave is located based on the communication quality profile. When it is determined to be a low-quality communication area, the host configures an enhanced communication mode for the slave. The enhanced communication mode includes at least one of the following: extending the duration of the radio frequency preamble after a single wake-up, increasing the retransmission redundancy of data packets, and shortening the wake-up interval to increase communication opportunities. The host is also configured to continuously monitor the communication quality feedback of the slave device after configuring the enhanced communication mode, and automatically switch the slave device back to the normal communication mode when the communication quality returns to the normal level and remains stable for a preset period.

[0077] In industrial settings, some areas may experience long-term signal coverage blind spots or persistent interference. Relying solely on a single signal quality test is insufficient to comprehensively reflect the overall communication environment of that area. This embodiment constructs a communication quality profile to statistically assess the communication environment of the area where the slave device is located and provides differentiated communication mode configurations.

[0078] After each successful reception of the master's next wake-up time, the slave device records the key quality indicators of this communication, including but not limited to: received signal strength indication value, signal-to-noise ratio, number of retransmissions (if any), and communication time.

[0079] The slave device accumulates and statistically analyzes the above indicators to form the communication success rate within a preset period (e.g., 1 hour, 24 hours, 7 days). The communication success rate can be defined as the ratio of the number of times a host response is successfully received to the total number of wake-ups. These data together constitute the slave device's communication quality profile.

[0080] The slave device has a preset success rate threshold (e.g., 90% or 95%). When the communication success rate within a statistical period falls below this preset threshold, it is determined that there is a persistent communication quality problem in the area where the slave device is located. At this time, the slave device proactively sends a communication quality anomaly alarm to the master device, and the alarm message carries a complete communication quality profile for the master device to make a comprehensive judgment.

[0081] After receiving an alarm, the host determines the communication environment level of the area where the slave device is located based on the communication quality profile. The determination criteria may include: Average received signal strength and fluctuation; Average signal-to-noise ratio; Long-term trend of communication success rate; Is there a periodic degradation (such as signal deterioration at specific times of the day)? Based on the above analysis, the host and slave areas are divided into different levels, such as "normal area", "slightly degraded area" and "severely degraded area".

[0082] When the master determines that the slave device is located in a low-quality communication area (such as a severely degraded area), it configures an enhanced communication mode for the slave device. The enhanced communication mode includes at least one of the following measures: Extending the duration of the radio frequency preamble allows the receiver more time to synchronously acquire the signal, thus improving the demodulation success rate in weak signal environments. Increase the retransmission redundancy of data packets, such as by increasing forward error correction coding redundancy, adopting more robust modulation methods, or allowing more retransmissions when communication fails. Shorten the wake-up interval to increase communication opportunities. By increasing the frequency of communication, the impact of low success rate of single communication can be offset, ensuring that data can be successfully reported within a certain period of time.

[0083] The host sends the configuration parameters for the enhanced communication mode to the slave via a response data packet.

[0084] After the slave device operates in enhanced communication mode, the host continuously monitors its communication quality feedback. When the slave device's communication quality recovers to a normal level (e.g., the communication success rate is higher than a preset threshold for several consecutive cycles) and remains stable for a preset period (e.g., it remains normal for 24 consecutive hours), the host automatically switches the slave device back to normal communication mode to restore standard power consumption levels.

[0085] This embodiment achieves long-term, statistical evaluation of the slave device's communication environment by constructing a communication quality profile, solving the problem that a single test cannot reflect the overall environment. Through a communication quality anomaly alarm mechanism, the slave device can proactively seek host intervention when its quality continuously deteriorates. Enhanced communication modes provide more robust communication guarantees for slave devices in harsh environments. Continuous monitoring and automatic recovery enable dynamic optimization of the communication mode, ensuring data reliability in harsh environments and timely recovery to a low-power mode after environmental improvement. This mechanism gives the system self-diagnosis, self-repair, and adaptive optimization capabilities, significantly improving long-term operational stability in complex industrial environments.

[0086] In one embodiment, the slave device is further configured to carry disturbance information at the time of failure in the data packets subsequently sent successfully each time communication fails. The disturbance information includes the time of failure and the communication activities of other slave devices in the vicinity that were monitored at the time of failure. The host is also used to receive interference information reported by multiple slave devices, identify slave device combinations that interfere with each other through cross-analysis, and establish an interference relationship map. The host is also configured to perform at least one of the following avoidance strategies on slave devices that are interfering with each other, based on the interference relationship map: assigning different operating frequencies to different slave devices, further spacing the wake-up times of interfering slave devices on the time axis, and adjusting the transmit power of the slave devices.

[0087] In battery-powered wireless data acquisition systems, existing low-power designs primarily focus on the communication link quality between individual slave and master devices, as well as the power consumption control of the slave devices themselves. However, in large-scale industrial deployments, a commonly overlooked issue is the mutual interference between slave devices.

[0088] This interference is not traditional channel congestion (i.e., multiple devices simultaneously vying for the same channel), but rather a more insidious electromagnetic interference phenomenon, including: Adjacent channel interference: Slave devices operating on adjacent frequencies affect each other due to leakage of the transmitted spectrum; Intermodulation interference: The transmitted signals from multiple slave devices mix on nonlinear devices, generating new frequency components that fall into the receiving frequency band; Receiver blockage: Strong signals from nearby slave devices saturate the receiver front end, making it impossible to demodulate weak signals.

[0089] Even if the wake-up time of the slave device is staggered by the master device, these interferences can still affect each other as long as they are close in time and adjacent in frequency, leading to communication failures, increased retransmissions, and increased power consumption. In existing technical solutions, when communication fails, the slave device only knows that it has failed, but does not know who is interfering with it; the master device also only sees the failure result, but cannot identify the cause of the failure, let alone eliminate the interference at its root.

[0090] To address the aforementioned issues, this embodiment provides a cooperative avoidance mechanism based on inter-slave interference identification, enabling the system to detect mutually interfering slave combinations and proactively take avoidance measures. Specifically, it includes the following steps: When a slave device sends the current data packet after a wake-up but fails to receive the next wake-up time from the master (i.e., communication failure), the slave device does not immediately discard the experience of this failure. Instead, it reports the disturbance information of this failure when it successfully communicates in the future. The disturbance information specifically includes: (1) the time of failure, the time when the communication failure occurred; (2) the surrounding communication activities, the communication activities of other slave devices around the slave device that the slave device listens to at the time of failure, including but not limited to: the signal strength of other slave devices detected; the frequency information of other slave devices detected; the communication duration of other slave devices detected; and, if demodulation is possible, the device identifier of other slave devices. It should be noted that the slave device does not need to wake up for this or increase the listening time. It simply listens to the surrounding environment during the time when the receiver is waiting for the master response within the original wake-up window. This passive listening method does not increase any additional power consumption.

[0091] When the slave device successfully receives the next wake-up message from the master, it includes the previously recorded interference information in the current data packet and sends it to the master. This method of reporting failure experiences after the fact avoids the energy consumption of repeated retransmissions at the moment of failure and ensures that the master can obtain valuable information about the interference situation.

[0092] After receiving interference reports from multiple slave devices, the host does not treat each record in isolation, but performs cross-analysis to identify combinations of slave devices that are interfering with each other. Cross-analysis methods include: Time correlation analysis: If slave A reports interference at a certain moment, while slave B's communication record shows that it sent data at the exact same moment, then A and B are suspected of interference. Frequency correlation analysis: If A reports the detection of a strong signal at a certain frequency, and B happens to be operating at that frequency, then A and B are suspected of interference. Spatial correlation analysis: If multiple slave devices repeatedly report interference from the same group of devices, it can be inferred that these devices are physically close and easily affect each other; Each slave device is treated as a node, and edges are connected between slave devices suspected of having interference relationships. The weight of each edge can be set to the frequency or intensity of the interference. After multiple rounds of data accumulation, the host gradually constructs a complete interference relationship graph, clearly showing which combinations of slave devices will cause interference when placed together.

[0093] Based on the interference relationship map, the host executes at least one of the following avoidance strategies for combinations of slaves that interfere with each other: 1. Assign different operating frequencies: For slave unit combinations that experience severe mutual interference, the host assigns them to different operating frequencies. If the system supports multi-frequency communication (such as multi-channel LoRa, multi-band Wi-SUN, etc.), this strategy can fundamentally eliminate adjacent-channel interference and intermodulation interference. For example, the originally adjacent frequencies of slave units A and B can be staggered to ensure a sufficiently large frequency gap, preventing spectrum leakage from affecting each other.

[0094] 2. Further extend the wake-up time: If frequency resources are limited or frequency switching is not possible, the master can further stagger the wake-up times of interfering slave devices on the timeline. The congestion avoidance strategy in claim 6 primarily aims to avoid channel contention caused by simultaneous wake-ups, while this step requires that "even if they don't wake up simultaneously, a sufficiently large time interval must be maintained" to avoid receiver blocking and other effects. For example, two slave devices originally staggered by 1 second can be staggered by 5 seconds if mutual interference is detected.

[0095] 3. Adjust the slave device's transmit power: In cases where receiver congestion is caused by excessively strong signals, the host can appropriately reduce the transmission power of the interfering source to a level where its signal strength is not enough to block neighboring receivers. Of course, this must be done without affecting the communication quality of the slave receiver itself; a balance can be found by gradually reducing the power and monitoring feedback.

[0096] However, interference relationships are not static; changes in the field environment, the addition or removal of equipment, and frequency adjustments can all alter the interference pattern. Therefore, the host continuously collects interference information reported by the slave devices, dynamically updates the interference relationship map, and continuously optimizes avoidance strategies based on the new map, forming a closed-loop adaptive adjustment mechanism.

[0097] Taking the equipment monitoring system of a large factory as an example, hundreds of temperature and vibration sensors were deployed on-site. After the system had been running for a period of time, the master unit discovered that three slave units, A, B, and C, located in the same workshop, frequently reported communication failures, and the failure times were correlated. Through cross-analysis of the interference information, the master unit identified intermodulation interference between A, B, and C. When A and B worked simultaneously (or at similar times), an intermodulation component was generated that fell exactly on the receiving frequency band of C, causing C to be unable to receive a response from the master unit.

[0098] Based on the interference relationship diagram, the host implemented the following avoidance strategy: adjusting the operating frequencies of A and B to bands far away from C, and further spacing out the wake-up times of the three to ensure they do not overlap. After the adjustment, the communication success rate of the three was significantly improved, the number of retransmissions was significantly reduced, and the battery life was effectively extended.

[0099] Figure 2 This is a flowchart illustrating a low-power wireless data acquisition method according to an exemplary embodiment, such as... Figure 2 As shown, the method is applied to the low-power wireless data acquisition system in the above embodiments, and the method includes the following steps S101-S104: In step S101, the slave device wakes up when the preset wake-up time is reached and collects data; In step S102, the current data packet is sent to the host; In step S103, the host receives the currently collected data packet and returns the next wake-up time to the slave based on the currently collected data packet; In step S104, if the slave device receives the next wake-up time returned by the master device, it updates its own wake-up settings according to the next wake-up time, turns off the power of the wireless module and enters a sleep state, and wakes up again at the next wake-up time to repeat the wake-up, data acquisition and sending of the currently acquired data packet operations; if the next wake-up time is not received, it performs an exception handling operation, turns off the power of the wireless module and enters a sleep state, and wakes up again after the sleep state ends to repeat the wake-up, data acquisition and sending of the currently acquired data packet operations.

[0100] In one embodiment, after the slave device performs an exception handling operation, it shuts down the power supply of the wireless module and enters a sleep state, including: The slave device retransmits the currently collected data packet. If the next wake-up time is not received after the first preset number of retransmissions, the power supply of the wireless module is turned off and the device goes into sleep mode for a first preset duration.

[0101] In one embodiment, the method further includes: Before waking up at the preset wake-up time, the slave device sends a power-on data packet to the master device after detecting power-on. The master receives the power-on data packet and returns the initial wake-up time to the slave based on the power-on data packet; After receiving the initial wake-up time, the slave device sets its own wake-up settings according to the initial wake-up time, and enters a sleep state after turning off the power of the wireless module. It wakes up at the initial wake-up time to perform wake-up, data acquisition, and sending the currently acquired data packet. If the initial wake-up time is not received, the power-on data packet is retransmitted. If the initial wake-up time is still not received after the second preset number of retransmissions, the power of the wireless module is turned off and the device goes into sleep for a second preset duration. After the sleep period ends, the device wakes up again to re-execute the step of sending the power-on data packet to the host.

[0102] In one embodiment, the method further includes: After being woken up, the slave device measures the current wireless signal quality before sending the current data acquisition packet. If the signal quality is lower than the first preset threshold, the current data acquisition packet is delayed, and a detection interval shorter than the current wake-up interval is set. After the detection interval, the slave device is woken up again to remeasure the signal quality until the signal quality meets the requirements before sending the current data acquisition packet. The slave device records the signal quality measurement value at each wake-up and forms a signal quality history trajectory. If the signal quality is lower than the first preset threshold for multiple consecutive measurements, it actively sends a signal quality alarm message to the host. The signal quality alarm message includes the signal quality history trajectory. The master receives a signal quality alarm. Based on the historical signal quality trajectory, it determines whether the signal degradation is continuous. If so, it adjusts the next wake-up time of the slave and returns the adjusted next wake-up time to the slave.

[0103] In one embodiment, the method further includes: The master unit executes a power grading strategy based on the remaining power of the slave unit to determine the next wake-up time. The power grading strategy includes: A first power threshold and a second power threshold are preset, with the first power threshold being higher than the second power threshold. If the remaining power is higher than the first power threshold, the next wake-up time is determined and sent according to the first collection frequency. If the remaining power is between the first power threshold and the second power threshold, the next wake-up time is determined and sent according to the second collection frequency, which is lower than the first collection frequency. If the remaining power is lower than the second power threshold, a power warning command is sent to the slave device, and the completion wake-up time of the last data report of the slave device is determined and sent. The slave device receives the power warning command and, after completing the next data report at the wake-up time, shuts down the power supply of the wireless module and enters deep sleep mode until it receives the active wake-up command from the host before waking up to work.

[0104] In one embodiment, the method further includes: The host is also used to execute congestion avoidance strategies based on the current network load status to adjust and determine the next wake-up time. These congestion avoidance strategies include: Monitor the current network channel occupancy rate; If the channel occupancy rate exceeds the preset channel congestion threshold, the host will randomly scatter the wake-up times of all slaves in the current period on the time axis, so that the wake-up times of at least two slaves that were originally woken up at the same time are staggered, and the adjusted wake-up times will be sent to the corresponding slaves respectively.

[0105] In one embodiment, such as Figure 3 As shown, the method further includes: The host determines the next wake-up time according to the self-learning adjustment steps, which include the following steps A1-A3: A1. Record the data change patterns of the slave device within the historical period; A2. When the data reported by the slave device is within the preset fluctuation range for multiple consecutive times, the master device automatically extends the wake-up interval of the slave device. A3. When the data fluctuation reported by the slave device exceeds the preset range, the master device automatically shortens the wake-up interval of the slave device.

[0106] In one embodiment, the method further includes: After collecting data, the slave device compares the collected data with a preset emergency threshold. If the data exceeds the emergency threshold, it is determined to be emergency data and an emergency label is marked in the current data packet. The host receives the currently collected data packet and checks whether it contains an emergency flag. If it does, the host automatically shortens the wake-up interval of the slave device.

[0107] In one embodiment, the method further includes: After each successful reception of the next wake-up time, the slave device records the received signal strength indicator value and signal-to-noise ratio of this communication, and calculates the communication success rate within a preset period to form a communication quality profile. When the communication success rate is lower than the preset success rate threshold, the slave device actively sends a communication quality abnormality alarm to the master device, and the communication quality abnormality alarm carries a communication quality file. The host receives communication quality abnormality alarms and determines the communication environment level of the slave's area based on the communication quality profile. When it is determined to be a low-quality communication area, the host configures an enhanced communication mode for the slave. The enhanced communication mode includes at least one of the following: extending the duration of the radio frequency preamble after a single wake-up, increasing the retransmission redundancy of data packets, and shortening the wake-up interval to increase communication opportunities. After configuring the enhanced communication mode, the host continuously monitors the communication quality feedback of the slave. When the communication quality returns to a normal level and remains stable for a preset period, the host automatically switches the slave back to the normal communication mode.

[0108] In one embodiment, the method further includes: When a communication fails, the slave device carries the disturbance information at the time of failure in the data packets that are subsequently successfully sent. The disturbance information includes the time of failure and the communication activities of other slave devices in the vicinity that were monitored at the time of failure. The host receives interference information reported by multiple slave devices, identifies combinations of slave devices that interfere with each other through cross-analysis, and establishes an interference relationship map. Based on the interference relationship map, the host executes at least one of the following avoidance strategies for slave devices that are interfering with each other: assigning different operating frequencies to different slave devices, further spacing the wake-up times of interfering slave devices on the time axis, or adjusting the transmit power of the slave devices.

[0109] The following details the scheme disclosed herein: Step 1: The wireless data acquisition module (slave, battery powered) starts working for the first time, establishes wireless communication with the host unit, and sends a power-on start data packet to the host device. After successfully receiving the data packet, the host device responds with the time required for the next wake-up. After the slave successfully receives the response, the wireless data acquisition module (slave, battery powered) sets the time required for the next wake-up according to the received time. Then proceed to Step 4. If the slave does not receive a response from the host after sending the data packet, proceed to Step 2.

[0110] Step 2: The wireless data acquisition module (slave, battery powered) retransmits the start-up data packet to the host device. The retransmission count is 3 times. After successfully acquiring the data packet, the host device responds with the time required for the next wake-up. After the slave successfully receives the response, the wireless data acquisition module (slave, battery powered) sets the time required for the next wake-up according to the received time. Then proceed to Step 4. If no response is received from the host after the slave sends the data packet 3 times, proceed to Step 3.

[0111] Step 3: After the wireless data acquisition module (slave, battery powered) is turned off, it enters sleep mode and automatically wakes up after a fixed period of time, proceeding to step 1.

[0112] Step 4: After the wireless data acquisition module (slave, battery powered) is powered off, it enters sleep mode and automatically wakes up after a specified timeout to collect data and upload the collected data to the host device. After successfully acquiring the data packet, the host device responds with the time required for the next wake-up. After the slave device successfully receives the response, it proceeds to step 5. If the slave device does not receive a response from the host after sending the data packet, it proceeds to step 6.

[0113] Step 5: The wireless data acquisition module (slave, battery powered) sets the duration required for the next wake-up based on the received current time, and proceeds to step 4.

[0114] Step 6: The wireless data acquisition module (slave, battery powered) retransmits the data packet 3 times. After the master device successfully acquires the data packet, it responds with the time required for the next wake-up. After the slave device successfully receives the response, the wireless data acquisition module (slave, battery powered) sets the time required for the next wake-up according to the received time. Then proceed to step 4. If no response is received from the master device after the slave device sends the data packet 3 times, proceed to step 3.

[0115] In one embodiment, to further reduce standby power consumption, as shown in steps 3 and 4, after the wireless data acquisition module (slave, battery powered) completes a data interaction communication, it first shuts down the wireless communication module and then enters a sleep state. It does not monitor in real time whether the wireless communication module receives a host command message and can resume from the sleep state to the working state at any time, thereby further reducing power consumption and increasing standby time.

[0116] In one embodiment, the data acquisition frequency can be dynamically adjusted, as shown in steps 1, 2, 4, 5, and 6. After each data interaction communication is completed, the wireless data acquisition module (slave or battery powered) receives the next wake-up duration from the host, starting from the current time, and then sets the next wake-up parameters to achieve on-demand dynamic adjustment of the communication frequency, overcoming the drawbacks of fixed intervals.

[0117] Standby time can be extended by increasing battery capacity, or by selecting a lower-power wireless communication scheme. Alternatively, a fixed frequency can be used for wireless communication, ensuring that the frequency meets the maximum communication frequency requirement. The host then filters and selects the data at the desired frequency after receiving the data.

[0118] In this disclosure, the wireless data acquisition module (slave, battery powered) does not need to be constantly in a command receiving and listening state waiting to be woken up. The power supply to the wireless receiving module can be turned off, further reducing standby power consumption and increasing the standby operating time of the wireless module (slave, battery powered) after a single charge, thus reducing the maintenance cycle of the wireless data acquisition module. The interval between two data acquisition transmissions of the wireless data acquisition module (slave, battery powered) is dynamically adjustable, enabling wireless data communication with varying intervals, improving transmission flexibility, and eliminating the need for maintenance of the wireless data acquisition module when data acquisition frequency requirements change.

[0119] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0120] This document uses specific examples to illustrate the principles and implementation methods of this application. The descriptions of the above embodiments are only intended to help understand the methods and core ideas of this application. Furthermore, those skilled in the art will recognize that, based on the ideas of this application, there will be changes in the specific implementation methods and application scope. Therefore, the content of this specification should not be construed as a limitation of this application.

Claims

1. A low-power wireless data acquisition system, characterized in that, The system includes: a slave device and a master device; The slave device is used to wake up when a preset wake-up time is reached, collect data, and send the currently collected data packet to the host. The host is configured to receive the currently collected data packet and, based on the currently collected data packet, return the next wake-up time to the slave device; The slave device is also configured to, if it receives the next wake-up time returned by the master device, update its own wake-up settings according to the next wake-up time, turn off the working power of the wireless module and enter a sleep state, and wake up again at the next wake-up time to repeat the operations of wake-up, data collection and sending the currently collected data packet; The slave device is also configured to, if it does not receive the next wake-up time, perform an exception handling operation, turn off the power supply of the wireless module and enter a sleep state, and wake up again after the sleep state ends to repeat the wake-up, data collection and sending of the currently collected data packet operations.

2. The system according to claim 1, characterized in that, In the aspect of shutting down the power supply of the wireless module and entering a sleep state after performing the exception handling operation, the slave device is specifically used for: The currently collected data packet is retransmitted. If the next wake-up time is not received after a first preset number of retransmissions, the power supply of the wireless module is turned off and the module goes into sleep mode for a first preset duration.

3. The system according to claim 2, characterized in that, The slave device is also used to send a power-on data packet to the master device after detecting power-on before waking up at a preset wake-up time; The host is also configured to receive the power-on data packet and return the initial wake-up time to the slave device based on the power-on data packet; The slave device is also used to set its own wake-up time according to the initial wake-up time after receiving the initial wake-up time, and to enter a sleep state after turning off the working power of the wireless module, and to wake up at the initial wake-up time to perform wake-up, data collection and sending the currently collected data packet. The slave device is also configured to retransmit the power-on data packet when it does not receive the initial wake-up time, and if it still does not receive the initial wake-up time after retransmission a second preset number of times, turn off the power supply of the wireless module and go into sleep for a second preset period of time, and wake up again after the sleep period ends to re-execute the step of sending the power-on data packet to the host.

4. The system according to claim 3, characterized in that, The slave device is also used to measure the current wireless signal quality after waking up and before sending the current data acquisition data packet; if the signal quality is lower than a first preset threshold, the current data acquisition data packet is delayed, and a detection interval shorter than the current wake-up interval is set. After the detection interval, the device is woken up again to remeasure the signal quality until the signal quality meets the requirements before sending the current data acquisition data packet. The slave device is also used to record the signal quality measurement value each time it is woken up, forming a signal quality history trajectory. If the signal quality measured multiple times in a row is lower than the first preset threshold, it actively sends a signal quality alarm message to the host. The signal quality alarm message includes the signal quality history trajectory. The host is also configured to receive the signal quality alarm, determine whether the signal quality is persistent based on the historical signal quality trajectory, and if so, adjust the next wake-up time of the slave device and return the adjusted next wake-up time to the slave device.

5. The system according to claim 3, characterized in that, The host is further configured to execute a power grading strategy based on the remaining power of the slave device to determine the next wake-up time, the power grading strategy including: A first power threshold and a second power threshold are preset, with the first power threshold being higher than the second power threshold; if the remaining power is higher than the first power threshold, the next wake-up time is determined and sent according to a first sampling frequency; if the remaining power is between the first power threshold and the second power threshold, the next wake-up time is determined and sent according to a second sampling frequency lower than the first sampling frequency; if the remaining power is lower than the second power threshold, a power warning command is sent to the slave device, and the completion wake-up time of the last data report of the slave device is determined and sent. The slave device is also used to receive the power warning command, and after completing the next data report at the wake-up time, it turns off the working power of the wireless module and enters deep sleep mode until it receives the active wake-up command issued by the host and then wakes up to work.

6. The system according to claim 3, characterized in that, The host is further configured to execute a congestion avoidance strategy based on the current network load state to adjust and determine the next wake-up time, the congestion avoidance strategy including: Monitor the current network channel occupancy rate; If the channel occupancy rate exceeds the preset channel congestion threshold, the host will randomly scatter the wake-up times of all slaves in the current period on the time axis, so that the wake-up times of at least two slaves that were originally woken up at the same time are staggered, and the adjusted wake-up times will be sent to the corresponding slaves respectively.

7. The system according to claim 3, characterized in that, The host is further configured to determine the next wake-up time according to a self-learning adjustment step, the self-learning adjustment step including: Record the data change patterns of the slave device within the historical period; When the data reported by the slave device is within the preset fluctuation range for multiple consecutive times, the master device automatically extends the wake-up interval of the slave device; When the data fluctuation reported by the slave device exceeds a preset range, the master device automatically shortens the wake-up interval of the slave device.

8. The system according to claim 3, characterized in that, The slave device is also used to compare the collected data with a preset emergency threshold after collecting the data. If the data exceeds the emergency threshold, it is determined to be emergency data and an emergency identifier is marked in the current data collection data. The host is also used to receive the currently collected data packet, detect whether it contains an emergency identifier, and if it contains an emergency identifier, the host automatically shortens the wake-up interval of the slave device.

9. The system according to claim 3, characterized in that, The slave device is also used to record the received signal strength indication value and signal-to-noise ratio of the current communication after each successful reception of the next wake-up time, and to calculate the communication success rate within a preset period to form a communication quality profile. The slave device is also used to actively send a communication quality abnormality alarm to the host when the communication success rate is lower than a preset success rate threshold, and the communication quality abnormality alarm carries the communication quality file. The host is also used to receive the communication quality abnormality alarm and determine the communication environment level of the area where the slave is located based on the communication quality profile. When it is determined to be a low-quality communication area, the host configures an enhanced communication mode for the slave. The enhanced communication mode includes at least one of the following: extending the duration of the radio frequency preamble after a single wake-up, increasing the retransmission redundancy of data packets, and shortening the wake-up interval to increase communication opportunities. The host is also configured to continuously monitor the communication quality feedback of the slave device after configuring the enhanced communication mode, and automatically switch the slave device back to the normal communication mode when the communication quality returns to the normal level and remains stable for a preset period.

10. The system according to claim 1, characterized in that, The slave device is also used to carry the disturbance information at the time of failure in the data packets that are subsequently successfully sent when each communication fails. The disturbance information includes the time of failure and the communication activities of other slave devices in the vicinity that were monitored at the time of failure. The host is also used to receive interference information reported by multiple slave devices, identify slave device combinations that interfere with each other through cross-analysis, and establish an interference relationship map. The host is also configured to perform at least one of the following avoidance strategies on slave devices that are interfering with each other, based on the interference relationship map: assigning different operating frequencies to different slave devices, further spacing the wake-up times of interfering slave devices on the time axis, or adjusting the transmit power of the slave devices.

Images