A cable monitoring terminal hierarchical power consumption management and hibernation wake-up control system

Abstract

This invention discloses a hierarchical power consumption management and sleep / wake-up control system for cable monitoring terminals, belonging to the field of data acquisition and control technology. It includes: a startup and strategy generation module, a hierarchical sleep and monitoring configuration module, a candidate wake-up detection module, a rapid confirmation module, a working state acquisition and session reporting module, and a closed-loop statistics and collaborative update module. By constructing an interference risk assessment, candidate wake-up and rapid confirmation collaborative control, and a terminal-gateway linkage scheduling mechanism, this invention achieves the technical effects of stable identification of real wake-up signals, collaborative suppression of false and missed wake-ups, and maintaining stable establishment of the main communication link under low power consumption. It solves the problems in existing technologies where the wake-up wireless receiver and main communication module have insufficient anti-interference capability when operating on the same frequency, making it difficult to balance wake-up sensitivity and link stability, and easily causing increased system power consumption.

Description

Technical Field

[0001] This invention relates to the field of data acquisition and control technology, and in particular to a hierarchical power consumption management and sleep / wake-up control system for a cable monitoring terminal. Background Technology

[0002] With technological advancements, power systems are expanding in scale and operating environments are becoming increasingly complex. This makes cables more susceptible to hazards due to factors such as temperature, current, and external environmental conditions during long-term operation. Therefore, technicians utilize cable monitoring terminals for real-time online monitoring and anomaly warnings. In online operation and maintenance scenarios for distribution network cables, cable monitoring terminals need to be online continuously and operate under tiered modes of normal low power consumption and abnormal high power consumption, balancing endurance and responsiveness. Therefore, tiered power management and sleep / wake-up control have become key technological directions.

[0003] Existing cable monitoring terminal systems achieve hierarchical management by dividing sub-modules such as sensing, communication, and main control into different power supply domains and employing power gating and clock gating to enable on-demand power switching and sleep state transitions to reduce overall power consumption. This is achieved by putting the MCU (Microcontroller Unit) into deep sleep during non-data acquisition / non-communication periods and using an RTC (Real-Time Clock), external events, or low-power wake-up wireless signals as wake-up sources, in conjunction with a firmware power management module to implement wake-up strategies and achieve low-power operation. Furthermore, existing systems introduce a low-power wake-up signal channel between the gateway and the terminal. The terminal-side WuR (Wake-Up Receiver) continuously listens for wake-up commands at low power, and only wakes up the main communication module upon receiving a valid wake-up signal to establish a complete data session, enabling on-demand communication. At the software level, the system calculates strategies and schedules events by switching sleep duration, wake-up time, and power levels, and can combine predictive mechanisms to optimize sleep strategies for energy consumption control.

[0004] The above-mentioned technology has at least the following technical problems: In existing technologies, the wake-up wireless receiver of cable monitoring terminals typically shares the same channel or frequency band with the main communication module, and the wake-up signal often employs a simple incoherent detection method to reduce power consumption. While this method contributes to power consumption reduction, it also results in poor anti-interference capability of the wake-up wireless receiver. During system operation, the shared channel between the main communication signal and the wake-up signal is highly susceptible to interference, leading to false wake-ups, missed wake-ups, or signal conflicts. Especially in high-interference environments, the wake-up signal often fails to trigger accurately, causing the system to malfunction and affecting the execution of monitoring tasks. When the main communication signal is strong, it may affect the accuracy of the wake-up signal, causing the receiver to incorrectly determine whether it has entered the wake-up state, or even completely miss some wake-up requests. This phenomenon is particularly pronounced in complex power network and distribution network environments, potentially causing delays in cable fault diagnosis and further increasing risks.

[0005] Furthermore, existing technologies cannot effectively distinguish between interference between wake-up signals and main communication signals in monitoring terminals that utilize wireless wake-up receivers deployed on the same or adjacent frequency bands as the main communication module. Even when the wake-up receiving link and the main communication link share the same frequency, are adjacent to each other, or have limited isolation, some mutual interference may still occur. This is especially true when the main communication module uses high transmit power for burst communication, while the wake-up receiver employs a lower-complexity detection method to reduce power consumption. If the RF front-end has insufficient selectivity or limited spatial isolation, wake-up decision interference is more likely to occur. Systems relying on simple threshold and duty cycle adjustments often struggle to maintain low power consumption while ensuring high accuracy, and the challenge of balancing wake-up signal sensitivity and anti-interference capability with the stability of the main communication link remains. In practical applications, frequent retries after false wake-ups increase unnecessary power consumption and response time, making the system difficult to adapt to various complex environments, particularly in low-power and high-interference scenarios, where system stability and reliability are difficult to guarantee. Summary of the Invention

[0006] To address the technical problem of mutual interference between wake-up signals and main communication signals in existing technologies, leading to increased power consumption and decreased stability, this invention provides a hierarchical power management and sleep / wake-up control system for cable monitoring terminals. The technical solution is as follows: A hierarchical power consumption management and sleep / wake-up control system for cable monitoring terminals is provided. The system includes: The startup and policy generation module is used to perform initialization and policy synchronization processing after the terminal is powered on, obtain the current policy parameters and historical statistics, determine the target power consumption state based on task information, terminal status information and historical operation information, and generate wake-up listening parameters and confirmation parameters based on historical statistics.

[0007] The hierarchical sleep and monitoring configuration module is used to control the terminal to enter the target power state and retain preset low-power monitoring resources.

[0008] The candidate wake-up detection module is used to perform candidate wake-up detection on the received signal within the listening window to obtain candidate wake-up events.

[0009] The quick confirmation module is used to respond to candidate wake-up events, perform a short confirmation process, and obtain a confirmation result.

[0010] The working state acquisition and session reporting module is used to establish a working state and perform data acquisition, session communication and policy interaction when the confirmation result meets the working state switching conditions.

[0011] The closed-loop statistics and collaborative update module is used to write back the statistical results generated during the current cycle and, based on the updated scheduling parameters, to coordinate with the gateway to control the terminal to enter the sleep state of the next cycle.

[0012] The beneficial effects of the technical solutions provided by the embodiments of the present invention include at least the following: 1. The cable monitoring terminal hierarchical power consumption management and sleep / wake-up control system provided by this invention constructs an interference risk assessment mechanism and dynamically adjusts the wake-up monitoring duty cycle, matching strength, and fast confirmation window parameters based on false wake-up statistics, channel busyness, and energy fluctuation information. This introduces a dual closed-loop mechanism of candidate detection and fast confirmation during the wake-up phase, thereby achieving accurate identification of real wake-up signals and effective suppression of false wake-ups in high-interference environments. This effectively solves the problem in existing technologies where the wake-up wireless receiver and main communication module operate on the same frequency, leading to insufficient anti-interference capability, easy false wake-ups and missed wake-ups, and increased system power consumption. Specifically, by periodically updating the interference risk index and driving adaptive adjustment of the monitoring strategy, the wake-up link no longer uses a static strategy with a fixed threshold or fixed duty cycle, but dynamically converges to the optimal monitoring parameter range based on the environmental state. This mechanism reduces the probability of false triggering and avoids missed detections due to excessively high thresholds. Furthermore, the system only briefly powers on the main communication transceiver for fast confirmation after a candidate wake-up, rather than directly entering the full working state, effectively reducing the instantaneous power consumption impact caused by false wake-ups and achieving synergistic optimization of power consumption control and identification accuracy.

[0013] 2. This invention writes back statistical data such as the number of false wake-ups, the reasons for failures, and link busyness at the end of each working cycle. When the interference risk continues to rise, it requests the gateway to issue minimum silence protection window parameters. This allows the terminal to adaptively optimize the monitoring strategy and the network to provide collaborative protection, thereby achieving the technical effect of maintaining low power consumption while ensuring stable establishment of the main communication link and reliable data reporting. This effectively solves the problem in existing technologies of balancing wake-up signal sensitivity and anti-interference capability, while failing to guarantee the stability of the main communication link. Furthermore, by introducing a collaborative scheduling mechanism between the monitoring terminal and the gateway, the wake-up phase no longer relies entirely on passive anti-interference on the terminal side. Instead, the network side provides a time-domain or time-slot-level silence protection window when necessary, reducing collision probability and channel occupancy conflicts at the system level. This achieves linkage optimization between terminal strategy and network scheduling, allowing the system to gradually converge to a stable working state when the interference environment changes, avoiding long-term unstable intervals with high false wake-ups or high missed wake-ups, thus significantly improving the overall reliability and energy efficiency. Attached Figure Description

[0014] To more clearly illustrate the technical solutions in the embodiments of the present invention, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0015] Figure 1 A schematic diagram of a hierarchical power consumption management and sleep / wake-up control system for a cable monitoring terminal provided in this application embodiment; Figure 2 A flowchart illustrating a hierarchical power consumption management and sleep / wake-up control system for a cable monitoring terminal, provided in an embodiment of this application; Figure 3 This is a schematic diagram of the operation of the hierarchical power consumption state machine provided in the embodiments of this application; Figure 4 This is a schematic diagram illustrating the operation of the gateway silent protection window provided in the embodiments of this application. Detailed Implementation

[0016] Embodiments of the present disclosure will now be described in more detail with reference to the accompanying drawings. While some embodiments of the present disclosure are shown in the drawings, it should be understood that embodiments of the present disclosure may be implemented in various forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided to provide a more thorough and complete understanding of the present disclosure.

[0017] It should be understood that the accompanying drawings and embodiments of this disclosure are for illustrative purposes only and are not intended to limit the scope of protection of this disclosure. In the description of the embodiments of this disclosure, the term "comprising" and similar terms should be understood as open-ended inclusion, i.e., "including but not limited to". The term "based on" should be understood as "at least partially based on". The term "one embodiment" or "this embodiment" should be understood as "at least one embodiment". The terms "first", "second", etc., may refer to different or the same objects.

[0018] To make the technical problems, technical solutions and advantages of the present invention clearer, a detailed description will be given below in conjunction with the accompanying drawings and specific embodiments.

[0019] like Figure 1 The diagram shown is a schematic representation of a hierarchical power consumption management and sleep / wake-up control system for a cable monitoring terminal provided in an embodiment of this application. Figure 2 The diagram shown is a flowchart of a hierarchical power consumption management and sleep / wake-up control system for a cable monitoring terminal, provided in an embodiment of this application. The system structure and the business methods of each system are as follows: The startup and strategy generation module is used to complete terminal power-on initialization and lightweight synchronization, select the target power level based on monitoring task information, calculate the interference risk index based on statistics, and generate wake-up monitoring strategy confirmation parameters. First, the terminal performs a local recovery operation, enabling the system to have basic operational capabilities without relying on complete external interaction. After power-on, the terminal enters the initialization state, configures the power state machine, and loads the switching conditions for each state. The power state machine includes four power states: deep sleep, light sleep, enhanced monitoring, and working. Simultaneously, wake-up sources are registered, including a real-time clock wake-up source, a wake-up receiver candidate interrupt source, and an optional hardware over-limit interrupt source, providing a trigger basis for subsequent sleep cycles. Subsequently, the terminal reads threshold parameters and historical statistics from local memory. Threshold parameters include basic strategy parameters such as the power threshold corresponding to the power state selection, the wake-up receiver duty cycle range, and the signature matching strength level. Historical statistics include false wake-up statistics, channel busyness statistics, received signal strength fluctuation statistics, missed wake-up indication statistics, and sliding window count information used for smoothing calculations. Upon first power-on or when the record is invalid, the factory default policy is loaded and all historical statistics are set to zero or default values ​​to ensure the system can operate.

[0020] After local recovery is complete, the terminal and gateway perform a lightweight synchronization. The terminal briefly activates the main communication link and sends local time information, local policy version number, and terminal status summary information. The local policy version number is a policy configuration version identifier associated with the current monitoring parameter set, acknowledgment parameter set, silent window rule set, and power control configuration set, used to identify the version status of the locally stored policy parameter set. The time information is used for time synchronization, the policy version number for version comparison, and the status summary information may include the power level and the result of the last session. The gateway returns time synchronization information, the current policy version number, and silent window rule information. The current policy version number is the version identifier of the gateway-side policy parameter set, used for consistency verification with the terminal's local policy version number. The terminal corrects its real-time clock or records deviations based on the returned information. If the policy versions are inconsistent, an update mark is recorded, and large parameter updates are completed in subsequent normal sessions. The silent window rule information is saved for subsequent wake-up determination and silent protection execution. By executing the above steps, the terminal system can form an executable basic parameter set and policy version number during the initialization phase.

[0021] Next, the system determines the target power consumption state based on task information, terminal status information, and historical operation information. The terminal first discretizes the decision input. On the task side, trigger sources are divided into alarm tasks, inspection tasks, periodic sampling tasks, and no-task states, and task information is assigned to each. For example, alarm tasks correspond to high priority, inspection tasks to medium-high priority, periodic sampling tasks to medium priority, and no-task states to low priority. On the power side, terminal status information, i.e., battery power levels, is divided into high, medium, low, and critically low levels to avoid boundary jitter. On the link side, historical operation information, including success, failure, timeout, or no-record states, is used, and the number of consecutive failures is recorded as an auxiliary basis. It should be noted that the above division of task information, terminal status information, and communication results is only an example; technicians can freely define the states according to actual conditions, and this embodiment does not impose constraints on this. This embodiment adopts a hierarchical sequential decision-making mechanism and maintains consistency with the execution logic of subsequent power consumption state control. The decision-making process executes mandatory condition determination, task information determination, task information constraint correction, communication result correction, and hysteresis hold constraint in a preset order to ensure that any combination of inputs yields a uniquely determined target power consumption state. The hysteresis hold constraint maintains the original power consumption state when the current power consumption state is already determined and the decision input does not meet the preset state switching conditions.

[0022] Based on this, the target power consumption state is determined according to preset rules. This embodiment sets four power consumption states, from low to high: deep sleep, light sleep, enhanced monitoring, and working state. Deep sleep corresponds to the lowest power consumption state, retaining only the necessary always-on power domains; light sleep is one level above deep sleep, maintaining low power consumption while retaining some monitoring capabilities; enhanced monitoring is above light sleep, operating under the premise of increasing monitoring frequency or shortening the wake-up cycle; and working state is the highest power consumption state, corresponding to the full functional domain being enabled and the session running state. For example... Figure 3 The diagram shows the operation of the hierarchical power consumption state machine provided in this embodiment. First, a mandatory operating condition determination phase is entered. A mandatory operating condition is triggered when any of the following conditions are met: there is an incomplete alarm confirmation or real-time alarm task; the main communication session is currently in the establishment phase and the session has not ended normally; the number of consecutive communication failures reaches a preset upper limit N1 and the power consumption is not at a critical low level; or a mandatory scheduling or remote control command is received from the gateway. This directly determines the target power consumption state as the operating state, and the subsequent correction process is not initiated. These conditions are overriding conditions, and their priority is higher than task information constraints and terminal state information constraints. When an alarm task exists or the alarm risk is high, if the battery level is high or medium, the system will be prioritized to enter enhanced monitoring mode or have its timed wake-up cycle shortened. Alarm risk is determined by comparing sensor data with preset thresholds. For example, if the temperature exceeds 120% of the alarm threshold or the abnormal current lasts for more than 5 minutes, the system will be directly set to enhanced monitoring mode. If the alarm risk is at the warning level but not at the mandatory alarm level, the timed wake-up cycle will be shortened, for example, from 30 minutes to 5 minutes. If the battery level is low, the system will be set to a light sleep mode while retaining controlled monitoring capabilities. If no mandatory operating conditions are triggered, the initial target state will be determined based on the task information. Alarm tasks correspond to enhanced monitoring mode, inspection tasks correspond to light sleep mode, and periodic sampling tasks and no-task states correspond to deep sleep mode by default. The state obtained at this stage is the task-driven initial target state. When only periodic sampling tasks exist and the environment is stable, if the battery is low, the system enters deep sleep mode to extend its hibernation time. If the battery is high or medium, it selects between light sleep and deep sleep based on the sampling urgency, which is determined by the ratio of the remaining allowable delay time to the standard sampling period. For example, if the current time until the next mandatory sampling deadline is less than 50% of the standard sampling period, it is considered high urgency; if the remaining time is greater than 80% of the standard period, it is considered low urgency. In high urgency situations, even with medium battery levels, light sleep mode is preferred; in low urgency situations, deep sleep mode can be entered to extend the hibernation time.

[0023] Subsequently, task information constraint corrections are performed. If the battery level is high or medium, the current target state is not restricted; if the battery level is low, entering the working state is prohibited; if the battery level is critically low, only deep sleep or light sleep states are allowed. If the current target state exceeds the battery allowable limit, it is automatically downgraded to the highest battery allowable state. When a previous communication failure is detected, enhanced listening or a shortened wake-up cycle is prioritized to increase the probability of successful wake-up and confirmation on the next attempt, rather than directly entering the full working state. Afterwards, state corrections are performed based on historical operating information. If the previous communication cycle failed or timed out, the target state is upgraded by one level within the battery allowable range; if the number of consecutive successful attempts reaches a preset threshold N², the power consumption state is downgraded by one level without violating the task information lower limit; if communication is successful but the consecutive success threshold is not reached, the current state remains unchanged. To prevent frequent switching of power consumption states, the system introduces a hysteresis mechanism and a minimum hold duration mechanism. Different threshold settings are used for entering and exiting a power consumption state, and the minimum hold period for each power consumption state is limited, thereby reducing the additional power consumption and system instability risks caused by switching. Before switching execution states, the system determines whether the current running state has reached the minimum hold period T. min If the target state is not reached, the original state remains unchanged; if the target state is reached and it differs from the current state, a state switch is executed. In this embodiment, the maximum threshold for continuous communication failures, N1, is 3 times. That is, when the main communication establishment fails or the acknowledgment times out for 3 consecutive cycles, a forced working state is triggered to avoid long-term missed reports. The maximum threshold for consecutive successes, N2, is 5 times. That is, when 5 consecutive communication cycles are successful without retransmission, the current power consumption state is allowed to be reduced by one level to reduce unnecessary listening overhead. The minimum hold period, T... min The minimum hold period can be set according to different power consumption states. For example, the minimum hold period for deep sleep state can be set to 3 sampling periods, for light sleep state to 2 periods, and for enhanced monitoring state to 1 period. The above values ​​are only examples, and technicians can adjust them according to actual conditions. This embodiment does not impose any restrictions on this.

[0024] Finally, the interference risk index I is calculated, and I is used to determine the monitoring and acknowledgment parameters of the terminal-side WuR. The specific implementation steps are as follows: The terminal reads local statistics, including false wake-up statistics F, channel busyness statistics B, received signal strength fluctuation statistics R, and missed wake-up indication statistics L. The above statistics are continuously updated by the preceding monitoring and acknowledgment process. That is, at the end of each monitoring cycle, the corresponding statistics are incrementally updated based on the event count or observation results generated in this cycle. Among them, F is used to characterize the false wake-up situation. Specifically, when a candidate wake-up is triggered, if no valid acknowledgment frame is received or the address matching fails within a short acknowledgment window, the event is recorded as a false wake-up, and F is accumulated. To improve stability, the false wake-up rate of the most recent K monitoring windows can be used as the effective statistical value of the false wake-up statistics, where K can be set to 10 monitoring windows, and the false wake-up rate can be defined as the proportion of the number of false wake-ups to the total number of candidate wake-ups. B is used to characterize the channel busyness level. It can be obtained by the energy detection ratio on the wake-up receiver side, that is, the proportion of time the energy continuously exceeds the noise threshold within the listening window, forming a busyness index between 0 and 1. The listening window is the WuR activation period triggered by RTC timing or duty cycle strategy when the terminal is in hierarchical sleep state, for example, it is activated once every 60 seconds, and each time it lasts for 20~100 milliseconds. The start time of the listening window is generated by RTC timer or other low-power timing unit, and the duration is determined by the current power consumption state and the interference risk index I calculated by the previous statistical period, and is implemented by WuR control register or MCU low-power scheduling instructions. The noise threshold can be measured based on the ambient noise floor during factory calibration, for example, taking the average ambient noise floor plus 3dB as the initial threshold, and can be adaptively fine-tuned according to the sliding window average during operation. R is used to reflect the fluctuation of the received signal strength during the listening period. Specifically, it refers to the variance calculation of the energy detection value within the listening window. The larger the variance, the more environmental interference sources or the more drastic the multipath changes. The energy detection value is a discrete sample value formed after amplitude sampling or power sampling of the received signal within the listening window. L is used to characterize missed wake-up events. Its calculation is based on the difference between the expected wake-up events (the number of wake-up triggers theoretically expected within a statistical period according to a preset monitoring period or scheduling plan) and the actual number of confirmed wake-up triggers (the number of confirmed wake-up events). To avoid misjudgment due to occasional packet loss, the average of the cumulative differences over M consecutive periods can be used as the effective statistic. In this embodiment, M=3 or 5 is used as an example. L can also be accumulated when multiple expected wake-ups fail to receive confirmation frames, or when the gateway provides a warning in subsequent sessions indicating that a link was not established as planned.

[0025] After obtaining the above statistics, the terminal first normalizes each statistic to map it to a uniform scale range. Specifically, scaling and upper / lower limit pruning can be used to convert the false wake-up statistic F, channel busyness statistic B, received signal strength fluctuation statistic R, and missed wake-up indication statistic L into standardized values ​​between 0 and 1. Then, the terminal performs a weighted summation of the normalized indicators according to preset weights to obtain the interference risk index I, as shown in the following formula: ; In this implementation, w1 represents the weight of the false wake-up statistic F, w2 represents the weight of the channel busyness statistic B, w3 represents the weight of the received signal strength fluctuation statistic R, and w4 represents the weight of the missed wake-up indication statistic L. It should be noted that this embodiment does not explicitly specify the exact numbers for the weights; it only requires that the sum of all weights equals 1. In this embodiment, the weight values ​​are set between 0.2 and 0.4 to prevent the system from becoming overly sensitive to a particular indicator or for that indicator's statistical dimension to become invalid. Furthermore, the weight allocation can be set according to the system's emphasis on the energy consumption risk of false wake-ups versus the service risk of missed wake-ups, thereby achieving different strategy preferences. For example, if more concern is given to the power consumption impact of false wake-ups, the values ​​of w1 and w2 can be appropriately increased; if more concern is given to the impact of missed wake-ups on services, the value of w4 can be appropriately increased.

[0026] Based on the calculated interference risk index I, the terminal generates corresponding wake-up monitoring parameters and acknowledgment parameters. First, the terminal adjusts the wake-up receiver's wake-up monitoring duty cycle according to I. The monitoring duty cycle is represented by the ratio of the monitoring period to the monitoring window duration, where the monitoring period T... cycle This can be determined by a hierarchical power state machine, for example, in deep sleep, T cycle The duration can be set to 60-300 seconds, 20-60 seconds in light sleep mode, and 5-20 seconds in enhanced monitoring mode. Monitoring window duration T. winThe duration of a single WUR activation can be set from 10 to 100 milliseconds. The wake-up monitoring duty cycle is defined as the ratio of the monitoring window duration to the monitoring period. These parameters can be provided in a default table at the factory or adjusted based on the power level. When I increases, and the false wake-up statistic F or channel busyness statistic B dominates, reduce the wake-up monitoring duty cycle or shorten the single monitoring duration to reduce false triggers and control power consumption. Specifically, when I is in the medium-to-high risk range, such as 0.5 ≤ I < 0.75, the wake-up monitoring duty cycle can be reduced proportionally by 10% to 30%, for example, from 0.5% to 0.35%. When I ≥ 0.75 and F or B accounts for more than 50% of I, the single monitoring window duration can be further shortened, for example, from 50ms to 30ms. The criteria for a low false wake-up count or channel busyness count are when they exceed a preset threshold, such as F>0.3 or B>0.6. When I increases but the missed wake-up count L dominates, the wake-up monitoring duty cycle should be maintained or moderately increased to avoid affecting the wake-up capability due to excessive tightening. For example, when L≥0.2 and increases for two consecutive cycles, the wake-up monitoring duty cycle can be increased by 10%~20%, or the monitoring cycle can be shortened by one level, such as from 60 seconds to 30 seconds, but the single monitoring window should not exceed the upper limit of 100ms to prevent a surge in energy consumption.

[0027] Next, the terminal adjusts the candidate wake-up threshold and signature matching strength based on I. When I is high, the candidate wake-up energy threshold or related peak threshold is increased to improve the matching correlation requirements. The length of the short identifier or rhythm sequence participating in signature matching can also be increased to enhance anti-interference capabilities. For example, when I ≥ 0.75, the energy detection threshold can be increased by 3~6dB, or the correlation matching threshold can be increased from 0.6 to 0.8, while the matching byte length can be extended from 8 bits to 16 bits. The basis for the increase is a significant increase in channel busyness statistics or false wake-up statistics. When I is low, the signature matching conditions are appropriately relaxed to reduce wake-up latency and power consumption. For example, when I ≤ 0.3, the energy threshold can be reduced by 2~3dB, or the correlation matching threshold can be lowered from 0.8 to 0.6, while the matching sequence length can be shortened. The basis for the relaxation is that the number of consecutive successful communications reaches N2.

[0028] In addition, the terminal needs to configure the two-stage acknowledgment duration and acknowledgment conditions based on I. When I is high, the acknowledgment window time is extended, allowing repeated reception and multiple verifications, and the strength of the acknowledgment conditions is increased. For example, the acknowledgment identifier, address, and integrity fields are verified simultaneously. For instance, when I ≥ 0.75, the acknowledgment window can be extended from the default 20ms to 50~80ms, and at least two consecutive valid acknowledgment frames or a CRC (Cyclic Redundancy Check) verification is required before success is determined. The extension is based on the insufficient reliability of acknowledgment under high interference environments. When I is low, the acknowledgment window is shortened to reduce the additional power consumption caused by the short-term startup of the main communication module. For instance, when I ≤ 0.3, the acknowledgment window can be shortened to 10~20ms, and only a single valid acknowledgment frame is required for success. When I exceeds a preset high threshold I... th For example, when the threshold is 0.75, or when both channel busyness and missed wake-up signs increase simultaneously, the terminal generates a silence protection window request flag and sends a request to the gateway in the next normal communication session. After the gateway returns the silence protection window parameters, the terminal saves them and uses them for subsequent monitoring and scheduling strategy generation, realizing collaborative anti-interference control between the terminal and the gateway. Among these, the high threshold I... th This can be determined by statistically analyzing historical operating data. For example, the average of the interference risk index over the most recent 100 cycles can be added to one standard deviation, or a fixed value within the range of 0.7 to 0.8 can be set directly. In this embodiment, it is set to 0.75. When I exceeds I for two consecutive cycles... th The request is triggered only when the time is right to avoid accidental triggering due to occasional fluctuations. This threshold can also be updated remotely by the gateway.

[0029] A tiered sleep and monitoring configuration module is used to perform domain-based control of the terminal, thereby achieving tiered sleep. The terminal power supply is divided into three power domains: normally open domain, main communication domain, and high-power sensor domain. The normally open domain is the power domain that must be continuously powered during sleep, and in this embodiment, it includes a wake-up receiver, a real-time clock, and an optional low-power over-limit detection circuit. The main communication domain includes the main communication transceiver and its RF front-end, power amplifier, low-noise amplifier, and other high-power communication components. The high-power sensor domain includes sensors that require continuous power or have high current draw, sampling front-ends, electrically excited devices, or image acquisition modules. Each power domain is uniformly managed by a power management chip, load switch, or control GPIO (General Purpose Input / Output) with preset power-on and power-off sequences. It should be noted that the division of the terminal power supply into three power domains in this embodiment is merely an example; those skilled in the art can freely adjust the classification according to actual conditions, and this embodiment does not impose any restrictions on this.

[0030] Before entering hibernation, the terminal first performs hibernation preparation operations. First, it saves necessary context information, including the current power state machine state, the next monitoring plan, and statistical cache data, and writes this information to a reserved area or backup register to ensure resumption of operation after hibernation. Next, it configures the wake-up source. The wake-up source includes at least a wake-up receiver candidate wake-up interrupt and a real-time clock timed wake-up. In addition, a low-power over-limit hardware interrupt can be configured to directly wake the processor when the detected quantity exceeds a threshold. Finally, the hibernation monitoring parameters are written to the wake-up receiver register, including the wake-up monitoring duty cycle, monitoring window duration, and threshold settings, so that the wake-up receiver operates according to a predetermined strategy during hibernation.

[0031] After completing the above preparations, the terminal shuts down the main communication domain and the high-power sensor domain according to the power domain strategy. In this embodiment, the shutdown process mainly adopts a logical power-down followed by a physical power-off. For the main communication domain, the transceiver is first put into sleep or standby mode, the transmit link and related clocks are shut down, and then the power supply to this domain is cut off through the power management chip or load switch. The relevant interface signals are processed with high impedance or fixed level to avoid reverse power supply. For the high-power sensor domain, sampling and related bus clocks are first stopped to put the sensor into low-power mode, and then the power supply is cut off, while only the necessary low-power over-limit interrupt path is retained. When both the main communication domain and the high-power sensor domain are shut down, the system is maintained by the normally open domain only during sleep. The wake-up receiver is continuously powered and performs candidate wake-up detection according to the configuration. The real-time clock continues to count and provides a timing wake-up reference. The low-power detection circuit can trigger an interrupt wake-up when the limit is exceeded.

[0032] After the power domain configuration is completed, the processor enters the corresponding hierarchical sleep state according to the hierarchical power state machine. In deep sleep state, the system shuts down most of the internal clocks and logic modules, retaining only the minimum wake-up unit; in light sleep state, more context is retained to speed up wake-up; in enhanced listening state, the wake-up receiver listening frequency or duty cycle is increased, but the main communication domain remains off, and the main communication transceiver is only briefly powered on during the subsequent confirmation phase. If the confirmation fails, it immediately returns to the sleep configuration state.

[0033] The candidate wake-up detection module is used to perform candidate wake-up detection based on the monitoring parameter configuration generated in the hierarchical sleep and monitoring configuration module, combined with the candidate wake-up judgment conditions. The terminal first downloads the wake-up monitoring parameters generated in the previous stage to the wake-up receiver or its low-power detection logic unit to form a configuration parameter set. The configuration parameters include the monitoring period T. cycle Listening window duration T listen Energy threshold E, rhythm matching rule R rule Short ID length ID len Short ID Expected Value ID valueMatching threshold (Match) and matching timeout (T) out The above parameters serve as direct inputs for candidate wake-up detection and are automatically executed by the wake-up receiver according to a predetermined strategy during sleep. Among them, the matching timeout T... out This is used to limit the maximum allowed time from the detection of energy exceeding the threshold E to the completion of a rhythm match or short ID match. If in T... out If a valid match is not completed within the specified time, it is considered a match failure and the matching state machine is immediately reset to avoid prolonged occupation of the listening window due to continuous noise or erroneous segments. Generally, T out The time limit must not exceed 80% of the listening window duration to ensure that there is still time to complete the next detection cycle or enter a sleep state after a match fails. The candidate wake-up determination criteria include the energy detection threshold and the feature detection matching threshold.

[0034] To achieve low-power detection, the wake-up receiver preferably employs a two-stage screening structure, including analog coarse screening and lightweight digital fine screening. Its front-end operates continuously under normally open-domain power supply. The signal, after passing through the antenna and filtering, enters the low-power RF or baseband front-end, where an energy signal is output through an envelope or energy detection circuit. A comparator or low-speed sampling circuit then determines the energy threshold. Its back-end is configured with simple matching logic or a small state machine to perform rhythm matching and short ID matching operations. Upon successful matching, a candidate wake-up interrupt signal is output to the processor. During operation, the wake-up receiver operates according to the listening period T. cycle The system automatically enters the listening window. Upon reaching the listening trigger time, it wakes up the receiver, enters the listening state, and continues for a period of time T. listen Time; if the test fails within this time, the system will automatically exit the listening window and enter sleep mode to wait for the next cycle.

[0035] Within the monitoring window, energy detection, i.e., the first-level energy threshold judgment, is performed first. The receiver is woken up to sample the envelope energy at a low speed, and the sampled value is compared with the energy threshold E to generate a single energy judgment result. When the sampled value is greater than or equal to the energy threshold, it is marked as a valid sample; otherwise, it is marked as an invalid sample. To suppress transient noise interference, it can be set that multiple consecutive samples exceeding the threshold or exceeding the threshold a predetermined number of times within a certain number of samples are considered acceptable. A threshold hysteresis interval can also be set to avoid critical jitter. If the energy detection fails, it is determined that there is no candidate signal and the window is exited.

[0036] Once the energy threshold is passed, the second-level feature detection begins: rhythm and short ID matching. Rhythm matching determines whether the signal conforms to a preset pulse interval rule. The wake-up receiver records multiple energy rising edge timestamps and calculates adjacent interval values, comparing them with R... rule Perform a tolerance comparison; if a match is found, continue with short ID matching. Where R... ruleA set of preset pulse time interval rules, including, for example, the ideal interval value T. ref The allowable offset range ΔT is defined as the allowable time deviation range, i.e., when the actual interval T... actual Satisfy | T actual -T ref When |≤ΔT, the interval is considered a successful match. In this embodiment, ΔT can be set to T. ref The tolerance range is 5% to 15%. For example, when the ideal pulse interval is 10ms, the tolerance range can be set to ±1ms. When the interference risk index I ≥ 0.75, the tolerance can be reduced to ±0.5ms to enhance anti-interference capability. When I ≤ 0.3, it can be relaxed to ±1.5ms to improve the matching success rate under weak signal conditions. If the rule is not met, it is judged as a failure and exits the window. Short ID matching is used to quickly decide on the received simplified bit sequence, and performs correlation or Hamming distance judgment according to the configured matching strength parameter. When the interference risk is high, the matching threshold Match can be increased or the matching sequence length can be extended, where the matching threshold Match represents the lower limit of the correlation score. For example, when using correlation matching, the received sequence and the expected ID can be calculated. value The normalized correlation coefficient Cor between them is used to determine a successful match when Cor ≥ Match. In this embodiment, when ID len When the bit depth is 16 bits, the matching threshold (Match) can be set to 0.7~0.9. When the interference risk index I ≥ 0.75, Match can be increased to 0.85 or higher; when I ≤ 0.3, Match can be decreased to 0.7 to improve wake-up sensitivity. Within the specified T... out If a match is not completed or fails to be matched within the time limit, the window will be closed.

[0037] Once the energy, rhythm, and short ID match are successful, the wake-up receiver generates a candidate wake-up event and wakes the processor via a hardware interrupt line. Simultaneously, relevant information, including peak energy, matching score, hit short ID, and timestamp, is latched in internal system registers or buffers for the processor to read during subsequent confirmation. To avoid jitter-induced false triggers, a minimum interrupt hold time can be set or the processor can be required to write back confirmation to clear the latch flag. If the match fails, the wake-up receiver immediately shuts down or reduces its front-end operating current, clears the temporary state of the current window, and returns to sleep mode to await the next listening cycle. Simultaneously, coarse-grained environmental observation data is generated, recording interference intensity, false trigger counts, and noise statistics obtained during the listening process, such as the percentage of energy exceeding the threshold or signal strength fluctuation statistics within the window, for subsequent interference risk assessment and adaptive strategy updates. Based on the above matching, candidate wake-up events can be obtained.

[0038] The rapid confirmation module is used to verify the legitimacy of a wake-up event after the microcontroller unit is awakened by a candidate wake-up. This verifies whether the wake-up originates from a genuine wake-up process initiated by the gateway, or is a false trigger caused by environmental interference, co-channel communication, or a collision. After the processor is awakened, the wake-up source is first identified to confirm whether it was triggered by a candidate wake-up event from the wake-up receiver, rather than by a real-time clock or an out-of-limit interrupt. Optionally, the digest information latched by the wake-up receiver, including the matching short ID, peak energy, and matching score, is read for subsequent statistics and strategy optimization.

[0039] Subsequently, the processor powers on the main communication domain, but only enters the acknowledgment mode. Specifically, the main communication domain is powered on via the power management unit or load switch, the main communication transceiver is initialized to listen or acknowledgment mode, and only the fixed channel, rate, and acknowledgment-specific parameter set are configured, without loading the complete protocol stack or starting the high-power sensor domain, thus achieving the minimum power-on path. During this stage, the processor preferably only enables the transceiver's receive link, disables the transmit link and power amplifier module, and masks unnecessary interrupt sources to reduce instantaneous current peaks. The acknowledgment-specific parameter set can be a lightweight configuration file pre-loaded in memory, avoiding the time and power consumption overhead of dynamically loading the complete communication stack.

[0040] Based on this, the processor starts a confirmation window timer, which is set to run within a preset confirmation window T. confirm The system performs rapid listening and judgment. The confirmation window duration can be generated by a pre-adaptive strategy and appropriately extended when the interference risk is high. The confirmation judgment logic is only used to determine whether a valid confirmation frame exists and does not perform complete business processing. Confirmation conditions may include detecting a specific frame type identifier, the destination address matching the local terminal address, passing the verification field, and optional session tag matching. To improve confirmation reliability, the confirmation logic can adopt a hierarchical judgment mechanism, such as first performing rapid frame type filtering, then address field comparison, and finally performing CRC or integrity verification, thereby controlling processing delay while ensuring confirmation accuracy. If the above conditions are met within the confirmation window, the confirmation is considered successful.

[0041] If the confirmation condition is not met by the end of the confirmation window, the confirmation is deemed to have failed. The reasons for failure can be categorized as no valid frame within the window, address mismatch, or verification failure, and the corresponding reason code is recorded. This reason code can be written into the statistics area using bit-encoded methods for subsequent analysis of the proportion of different interference types. The processor then shuts down the main communication transceiver and cuts off the power supply to the main communication domain, returning to the hierarchical sleep process, retaining only the normally open domain for operation. During the shutdown process, it is preferable to first put the transceiver into a low-power or standby state before cutting off the power supply to avoid sudden current changes or reverse power supply issues at the interface. Simultaneously, the false wake-up statistics are updated, and interference-related observation data, including signal strength fluctuations or channel busy status, are recorded as input for subsequent interference risk assessment and monitoring strategy adjustments, thus forming a statistical write-back closed loop. It should be noted that the above statistical updates can be smoothed using a sliding window or exponential weighting method to avoid excessive impact of a single abnormal event on the overall strategy. This embodiment is merely an example; in actual implementation, technicians can freely choose the specific smoothing method according to the actual situation, and this embodiment does not impose any constraints on this.

[0042] Upon successful confirmation, a confirmation pass flag is recorded, and the process switches from confirmation mode to working state to establish a workflow. The main communication domain and related functional modules are then activated according to the predetermined power-on sequence, entering the formal session or task processing state. During the switching process, communication parameters can be reinitialized to the complete service configuration, and the sensor domain or storage domain can be activated simultaneously depending on the current task type, thus achieving a smooth transition from the minimum confirmation path to the complete service path.

[0043] The operating state acquisition and session reporting module is used to establish the system's operating state, collect and report key data, and update the interference risk index and power consumption statistics. First, after successful confirmation in the quick confirmation module, the terminal begins to activate the necessary power domains and establish a session context in a predetermined order.

[0044] To avoid anomalies caused by power surges and peripheral instability, the system performs a power-on operation in the power domain, following a sequence from the storage domain to the sensor domain, and then to full communication functionality. The main communication domain is already in a minimal power-on state during the confirmation phase; it is powered on but the full protocol stack is not loaded yet. The storage domain is then enabled for session recording, data caching, and statistical writing. Next, the required sensor subdomains are enabled based on the task type, not all sensor domains. Simultaneously, only the bus and peripheral clocks relevant to this task are enabled. When enabling each power domain, a power-on stabilization delay or polling ready flag can be set to ensure voltage stability and successful peripheral self-tests before proceeding to the next stage, avoiding abnormal sampling or communication errors due to power instability. After necessary initialization, the working state ready flag is set, and the system enters the session handshake phase. If an anomaly is detected at any stage, the enabled power domains are shut down according to a predetermined fallback path, and the system returns to sleep mode, preventing the system from remaining in an abnormally high-power state for an extended period.

[0045] The main transceiver is switched from acknowledgment mode to session mode. Specifically, this involves loading complete session communication parameters, including channel, rate, network identifier, and retransmission policy, and establishing a session context. The session context includes the terminal address, session sequence number, policy version number, statistical summary information, wake-up source identifier, current power consumption status, and brief historical link quality indicators. These are used for subsequent data interaction and more refined scheduling decisions by the gateway. Following this, the handshake process for entering the session is executed. The terminal sends a joining request message to the gateway, carrying information such as the local policy version number, power level, current power consumption status, and wake-up type. The gateway returns a joining confirmation message, carrying a joining permission flag, a task or parameter update summary, and the gateway policy version number. If the versions of both parties are inconsistent, the update flag is recorded. The handshake process can be configured with a maximum number of retries and a timeout determination mechanism. If the handshake fails, the reason for the failure is analyzed, and the system reverts to a sleep state to avoid prolonged waste of communication energy. After the handshake is completed, the data phase begins.

[0046] After the session is established, the terminal drives the sensor domain to operate according to the sampling instructions. The sampling instructions specify the sampling object, the number of samples, and whether to execute an alarm determination. Collected data is preferentially written to the buffer to avoid data loss due to communication jitter. The buffer can adopt a ring buffer structure or a double buffer structure to support parallel operation of sampling and communication, thereby improving system real-time performance. During data processing, only necessary edge preprocessing is performed, including filtering and noise reduction, threshold determination, and data compression or packaging, to generate reported data, denoted as D. reportIf an out-of-limit event is detected, an alarm flag is generated. The preprocessing algorithms typically employ low-computation filtering or feature extraction methods to control processor time and avoid significant impact on power consumption. It should be noted that this embodiment only illustrates a feature extraction algorithm; technicians can freely choose the preprocessing algorithm according to actual needs, and this embodiment does not impose any constraints on this. Uplink and downlink interactions are completed within the same session. The terminal sends D... report The system also uses a confirmation mechanism to count retransmissions. Simultaneously, it receives task updates, silent window rule updates, or policy version updates from the gateway. Uplink data packets can include current statistical summaries and link quality indicators for centralized analysis on the gateway side. Received parameters are distributed to the corresponding internal modules to provide a basis for subsequent decision-making. Parameter updates preferably employ a version number verification mechanism to avoid duplicate loading or erroneous overwriting.

[0047] Finally, interference and power consumption statistics are updated. A statistical update operation is performed before the session ends, updating the acknowledgment result, session establishment time, retransmission count, and channel busyness estimate. The connection establishment time can be obtained from the time difference between session mode initiation and handshake completion. The retransmission count comes from communication process statistics, and the busyness can be obtained from carrier sensing or backoff statistics. These statistics can be stored by field category and smoothed using a sliding window or exponential weighting method to avoid a single anomaly excessively affecting the overall trend. Simultaneously, the terminal performs energy consumption estimation, recording the duration of the working state and the duration of the communication phase, and converting this into an estimated energy consumption value using a preset power consumption coefficient. These statistics can be implemented based on a state timer. The power consumption estimation result can be divided into communication energy consumption and sampling energy consumption, used for subsequent power status decisions and interference risk assessment inputs, respectively.

[0048] The above statistical results are written into the statistical area to form the input data for calculating the interference risk index and selecting the power consumption state in the next cycle. This statistical write-back operation does not immediately adjust the parameters, but serves as the basis for the next round of adaptive evaluation, thus forming a closed-loop convergence mechanism.

[0049] The closed-loop statistics and collaborative update module is used by the terminal system to complete statistical write-back, gateway collaborative silent window update and fallback hibernation operations, and optimize the next wake-up environment through gateway collaboration when necessary.

[0050] First, a statistical write-back operation is performed. The terminal writes the candidate wake-up results, acknowledgment results, acknowledgment failure reasons, link establishment time, retransmission information, false wake-up statistics, channel busyness, missed wake-up indicator statistics, energy consumption information, and environmental observation information generated in the current cycle into the local statistical area for storage. The statistical data serves as input for the interference risk index calculation and power consumption status decision in the next cycle. Parameters are not immediately adjusted in the current cycle; instead, a closed-loop data foundation is formed, and the interference risk index is updated based on the false wake-up statistics, channel busyness statistics, received signal fluctuation statistics, and missed wake-up indicator statistics. When the interference risk index I is detected to be consistently high, and the missed wake-up indicator shows an upward trend (i.e., the missed wake-up statistics within the sliding window monotonically increase or the slope exceeds a preset threshold), the terminal triggers the gateway-coordinated silent window update mechanism. The standard for consistently high levels can be determined by setting a statistical window; for example, if I exceeds a preset first threshold I for multiple consecutive cycles. th Among them, multiple consecutive cycles can be set to two consecutive power management cycles, when I ≥ I in two consecutive cycles. th If the value is consistently high, it can be further required that, to avoid misjudgment due to occasional spikes, there are at least 3 instances where I ≥ I in the most recent 5 cycles. th The value of L is considered to be consistently high; an increase in missed wake-up rate can be judged by the increment of L within the sliding window or the increase in the proportion of invalid frames in the failed confirmations. Specifically, a sliding window of length N can be set, for example, N=3, and the difference in missed wake-up rate within adjacent time windows can be calculated. When the difference is positive for K consecutive times, for example, K=2, or the overall linear fitting slope of the window is greater than a preset threshold S, the missed wake-up rate is considered to be high. th For example, S th When the value is 0.05 / cycle, it is determined that the missed wake-up indicator is increasing. In this embodiment, the terminal continuously records the above statistics in each power management cycle, and uses the increment of the missed wake-up statistics within the sliding window as the basis for determining the upward trend of the missed wake-up indicator. It should be noted that the above statistics are all from the statistical write-back results of the previous steps. When the terminal is currently in a working state and the main communication link has been established, the terminal sends a silent window cooperation request to the gateway in this session. If the terminal has not yet established a main communication link or is in a sleep cycle, the terminal only saves the request flag and associated statistical summary locally, and sends the request again when the session is successfully established next time, so as to avoid additionally waking up the main communication resources to send the request.

[0051] like Figure 4The diagram illustrates the operation of the gateway silent protection window provided in this embodiment. When the triggering conditions are met, the terminal sends a silent window request message to the gateway in the current session. This message includes a request type identifier, a summary of the current interference risk, duration information, missed wake-up trend indicators, and relevant service or node range identifiers. The terminal can also specify the next planned wake-up time or a predetermined time slot number, and provide the desired minimum silent window length or level. The terminal only requests the minimum silent window; the specific scheduling arrangement is decided uniformly by the gateway. The gateway returns a protection plan based on the overall network load and scheduling situation, including silent window parameters, alternative time slots, and temporary rerouting strategies. The gateway can generate and return silent window parameters by combining network-side resource occupancy and scheduling status. These parameters include the silent window start time and duration, and can further carry applicable scope information and strategy version information. Furthermore, the gateway can simultaneously return alternative time slot parameters and link scheduling parameters. It should be noted that the silence window parameter is used to limit the start time, duration, scope of application, number of valid times, or effective time period of the silence protection window. The alternative time slot parameter is used to instruct the terminal to replace the target time slot information of the originally planned listening / acknowledgment time slot. The link scheduling parameter is used to instruct the temporary scheduling constraint information of relevant nodes, services, channels, or routes. The silence window parameter includes the silence duration before and after wake-up, the scope of application, and the number of valid times or effective time period. If the originally planned wake-up time period is congested, the gateway can issue alternative time slot information. In addition, in complex scenarios, the service time slots or channels of relevant nodes can be temporarily adjusted to provide the target terminal with acknowledgment clearance time. When the silence window parameter received by the terminal conflicts with the alternative time slot parameter, the terminal prioritizes the constraint of the silence window and remaps or postpones the alternative time slot. In this embodiment, when the gateway returns parameters carrying a forced scheduling priority identifier or a higher priority identifier, the terminal can execute the alternative time slot first according to the priority identifier and downgrade the silence window to only be effective for non-critical services or non-acknowledgment stages. After receiving the returned content, the terminal writes the policy version number and the silent window parameter to the local storage area and sets a validity flag. To improve reliability, verification information can be attached to the stored content. The silent window parameter will be read and used when the next cycle of listening and acknowledgment plan is generated.

[0052] After completing the statistical write-back and collaborative update, the terminal generates the next cycle's operating plan. The plan's inputs include current terminal status information, task information and timing information, the interference risk index for this cycle, and the silent window or alternative time slot parameters issued by the gateway. Outputs include the next cycle's power consumption state selection, the monitoring window time arrangement, and the next cycle's wake-up parameter configuration. Specifically, the terminal determines whether to enter deep sleep, light sleep, or enhanced monitoring state based on the next cycle's operating plan, and adjusts the next monitoring window time, such as aligning with alternative time slots or avoiding congested periods outside the silent window. Simultaneously, it updates the next cycle's wake-up receiver configuration parameters. The terminal saves the policy version information corresponding to the received parameters and determines the monitoring and sleep scheduling arrangements for the next cycle based on the received parameters. The silent window becomes invalid when: the silent window expires or exceeds the preset maximum valid duration; a higher version silent window or scheduling policy parameter is received and replaced; interference risk-related indicators fall below the low-risk threshold for multiple consecutive power management cycles and the terminal clears the request flag; or there is an irreconcilable conflict between the silent window and the forced link scheduling parameters, and the gateway indicates that forced scheduling takes priority.

[0053] Subsequently, the system performs a fallback operation. The terminal exits the session mode in the order of logical power-down followed by physical power-off, shuts down the power to the sensor domain and storage domain, and retains power to the normally open domain only for necessary low-power detection. The main communication transceiver exits the session mode and cuts off its power supply. Finally, the processor enters the selected hierarchical sleep state, waiting for the next round of listening or task triggering.

[0054] Through the above description of the implementation methods, those skilled in the art can clearly understand that, for the sake of convenience and brevity, only the division of the above functional modules is used as an example. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the above functions can be divided into different functional modules to complete all or part of the functions described above.

[0055] In the embodiments provided in this application, it should be understood that the disclosed systems and methods can be implemented in other ways. For example, the embodiments described above are merely illustrative; for instance, the division of modules or units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units 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 units, and may be electrical, mechanical, or other forms.

[0056] The units described as separate components may or may not be physically separate. A component shown as a unit can be one or more physical units, located in one place or distributed in multiple different locations. Some or all of the units can be selected to achieve the purpose of this embodiment, depending on actual needs.

[0057] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0058] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a readable storage medium. Based on this understanding, the technical solutions of the embodiments of this application, or the parts that contribute to the solution, or all or part of the technical solution, can be embodied in the form of a software product. This software product is stored in a storage medium and includes several instructions to cause a device (which may be a microcontroller, chip, etc.) or processor to execute all or part of the steps of the methods of the various embodiments of this application. 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.

[0059] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions within the technical scope disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A hierarchical power consumption management and sleep / wake-up control system for cable monitoring terminals, characterized in that, include: The startup and policy generation module is used to perform initialization and policy synchronization processing after the terminal is powered on, obtain the current policy parameters and historical statistics, determine the target power consumption state based on task information, terminal status information and historical running information, and generate wake-up listening parameters and confirmation parameters based on historical statistics. The hierarchical sleep and monitoring configuration module is used to control the terminal to enter and target power states, and to retain preset low-power monitoring resources; The candidate wake-up detection module is used to perform candidate wake-up detection on the received signal within the listening window to obtain candidate wake-up events; A quick confirmation module is used to respond to the candidate wake-up event, perform a short confirmation process, and obtain a confirmation result; The working state acquisition and session reporting module is used to establish a working state and perform data acquisition, session communication and policy interaction when the confirmation result meets the working state switching conditions; The closed-loop statistics and collaborative update module is used to write back the statistical results generated during the current cycle and, based on the updated scheduling parameters, to coordinate with the gateway to control the terminal to enter the sleep state of the next cycle.

2. The cable monitoring terminal hierarchical power consumption management and sleep / wake-up control system as described in claim 1, characterized in that: The initialization and policy synchronization processing includes: Load locally stored threshold parameters, historical statistics, and policy version information. The threshold parameters include one or more of the following: power threshold corresponding to power consumption state selection, wake-up receiver duty cycle range, and signature matching strength level. The historical statistics include one or more of the following: false wake-up statistics, channel busyness statistics, received signal strength fluctuation statistics, missed wake-up sign statistics, and sliding window count information used for smoothing calculation. Synchronous interaction with the gateway to obtain time base information, current policy version information, and silent window rule information; A basic parameter set is generated based on the threshold parameters, historical statistics, policy version information, and synchronization interaction information stored locally.

3. The cable monitoring terminal hierarchical power consumption management and sleep / wake-up control system as described in claim 1, characterized in that: The determination of the target power consumption state based on task information, terminal status information, and historical operation information includes: Acquire task information, terminal status information, and historical operation information, wherein the task information includes one or more of high priority, medium-high priority, medium priority, and low priority; the terminal status information includes one or more of high, medium, low, and critical low battery levels; and the historical operation information includes one or more of success, failure, timeout, and / or no record. Based on the task information, terminal status information, and historical operation information, a target power consumption state is selected from multiple preset power consumption states. The target power consumption state includes at least one of the following: deep sleep state, light sleep state, enhanced listening state, and working state.

4. The cable monitoring terminal hierarchical power consumption management and sleep / wake-up control system as described in claim 1, characterized in that: The generation of wake-up monitoring parameters and acknowledgment parameters based on historical statistical information includes: Read locally stored historical statistical information and calculate the interference risk index based on the historical statistical information. The historical statistical information includes one or more of the following: false wake-up statistics, channel busyness statistics, received signal fluctuation statistics, and missed wake-up sign statistics. The interference risk index is used to perform segmented mapping between multiple risk intervals to generate monitoring parameter and confirmation parameter sets with different combinations. A set of wake-up monitoring parameters and confirmation parameters are generated based on the interference risk index. The wake-up monitoring parameters include at least one or more of wake-up monitoring duty cycle and candidate wake-up threshold, and the confirmation parameters include at least one or more of signature matching strength, confirmation window parameters, and gateway collaboration request parameters.

5. The cable monitoring terminal hierarchical power consumption management and sleep / wake-up control system as described in claim 1, characterized in that: The control terminal enters the target power consumption state, including: According to the target power consumption state, set the power-on or power-on state for the normally open domain, the main communication domain, and the high-power sensing domain respectively; In the normally open domain, the operating parameters for the wake-up listening time window and the periodic wake-up timer are set; The terminal maintains the working state of the functional units in the normally open domain only during the period when the terminal is in a sleep state. The functional units include at least one of a wake-up receiving unit, a time base timing unit, and a low power detection unit.

6. The cable monitoring terminal hierarchical power consumption management and sleep / wake-up control system as described in claim 1, characterized in that: The step of performing candidate wake-up detection on the received signal within the monitoring window includes: Within the monitoring window, energy detection and / or feature detection are performed on the received wake-up signal. The energy detection results and / or feature detection results are compared with preset candidate wake-up judgment conditions. The energy detection results include numerical detection quantities formed after amplitude statistics, power statistics, or energy integration of the received signal within the monitoring window. The feature detection results include feature matching quantities or matching judgment flags generated based on the rhythm characteristics, timing characteristics, identification characteristics, or matching characteristics of the received signal. When the detection result meets the candidate wake-up determination condition, a candidate wake-up event is generated; when the detection result does not meet the candidate wake-up determination condition, the terminal remains in a sleep cycle. Record at least one of the following during the monitoring process: interference intensity, number of false triggers, or noise statistics, to form corresponding environmental observation data.

7. The cable monitoring terminal hierarchical power consumption management and sleep / wake-up control system as described in claim 1, characterized in that: The short-term acknowledgment process in response to the candidate wake-up event includes: The wake-up control processing unit briefly activates the main communication transmit and receive resources and enters the confirmation mode; Within a preset confirmation window, a confirmation signal is received. Based on at least one of the confirmation frame, address information, and / or identification information, it is determined whether the confirmation signal meets a preset confirmation condition. The preset confirmation condition requires that the confirmation signal at least matches the target confirmation information pre-stored in the terminal. If the verification result does not meet the confirmation conditions, a failure result is generated and the confirmation mode is exited, and the terminal returns to the sleep loop. When the verification result meets the confirmation conditions, a pass result is generated and the process enters the working state to establish the workflow.

8. The cable monitoring terminal hierarchical power consumption management and sleep / wake-up control system as described in claim 1, characterized in that: The establishment of the working state and the execution of data acquisition, session communication, and policy interaction include: The high-power sensing domain, storage domain, and main communication domain enter the working state in a predetermined order, wherein the predetermined order ensures that the storage domain enters a writable state before the main communication domain establishes a session. Establish a session context, which includes one or more of the following: a session identifier associated with the current session, buffer information, and policy parameter references; According to the sampling instruction, the monitoring data is acquired, and edge preprocessing is performed on the monitoring data to generate the reporting data. The edge preprocessing includes at least one of the following operations: filtering and noise reduction, threshold determination, data compression or packaging. The main communication domain sends the reported data based on the session context and receives one or more of the following from the gateway: task parameters, policy parameters, and version parameters. The task parameters include one or more of the following: sampling frequency, sampling period, sampling triggering conditions, and task information. The policy parameters include one or more of the following: wake-up listening configuration, acknowledgment rule configuration, power consumption status configuration, and silent window configuration. The version parameters include one or more of the following: version identification information used to identify the current task parameter or policy parameter configuration version.

9. The cable monitoring terminal hierarchical power consumption management and sleep / wake-up control system as described in claim 1, characterized in that: The process of writing back the statistical results generated during the current cycle includes: Record one or more of the following: candidate wake-up result, confirmation result, confirmation failure reason, link establishment time, retransmission information, channel busyness information, energy consumption information, and environmental observation information, and write the recorded results to local statistical storage; The update results in the local statistical storage are used as the data input for generating parameters in the next cycle.

10. The cable monitoring terminal hierarchical power consumption management and sleep / wake-up control system as described in claim 1, characterized in that: The gateway collaborative scheduling process includes: When the interference risk-related indicators are continuously higher than the first threshold within a preset time period and the missed wake-up signs show an upward trend, the terminal sends a silent window cooperation request to the gateway. The upward trend is determined by the increment of the missed wake-up statistics within the sliding window. Receive at least one of the following parameters returned by the gateway: silent window parameter, alternative time slot parameter, and link scheduling parameter; Save the policy version information corresponding to the received parameters; The listening and hibernation schedules for the next cycle are determined based on the received parameters.

Images