A low-power consumption short-distance communication scheduling method for an internet of things terminal

Abstract

The application discloses a low-power near-distance communication scheduling method for an Internet of Things terminal, and specifically comprises the following steps: step one, terminal hierarchical reporting; step two, dynamic time slot resource pre-allocation; step three, mode-based start-stop communication scheduling; step four, link state dynamic correction scheduling; and step five, idle time slot recycling and reuse. The application has the beneficial effects that high-priority terminals preferentially occupy communication time slots, and the resource mismatch problem caused by the same occupation of time slots by various terminals is solved from the resource allocation level; the terminal only reports parameters when being powered on or when the state of the terminal changes, thereby eliminating the invalid power consumption caused by the fixed-period repeated reporting, effectively reducing the useless communication power consumption of the terminal, directly cutting off the power supply of the communication module in deep sleep, flexibly controlling the start and stop of the module according to the business demand, and further reducing the idle power consumption of the terminal.

Description

Technical Field

[0001] This invention relates to the field of Internet of Things (IoT) terminal technology, specifically to a low-power short-range communication scheduling method for IoT terminals. Background Technology

[0002] The Internet of Things (IoT) connects various physical devices equipped with sensors and communication modules through networks. These devices can automatically collect environmental and operational data and complete information exchange and remote control through short-range or wireless networks, enabling intelligent monitoring, automatic scheduling, and autonomous operation of goods.

[0003] IoT terminals are hardware devices that integrate communication, sensing, and control components. They can collect field data, rely on communication methods such as NFC, BLE, and Zigbee, and form a network with gateways. They can complete data uploading, start-up, and shutdown control according to scheduling instructions. They are the end carriers for IoT to realize data collection and device management.

[0004] However, the shortcomings of existing short-range IoT communication scheduling methods are that most of them adopt a unified time slot allocation mechanism, in which all terminals occupy communication time slot resources uniformly regardless of the importance of their services, and the terminal reporting mechanism reports at fixed intervals, sending data periodically regardless of whether its own status changes, resulting in a large amount of invalid reporting power consumption.

[0005] To address this, we propose a low-power, short-range communication scheduling method for IoT terminals. Summary of the Invention

[0006] In view of the problems existing in the above and / or existing low-power short-range communication scheduling methods for IoT terminals, the present invention is proposed.

[0007] Therefore, the purpose of this invention is to provide a low-power short-range communication scheduling method for IoT terminals. By improving the existing short-range IoT communication scheduling methods, this invention can solve the shortcomings of the existing short-range IoT communication scheduling methods mentioned above. These methods mostly adopt a unified time slot allocation mechanism, in which all terminals occupy communication time slot resources uniformly regardless of the importance of their services. The terminal reporting mechanism reports at fixed intervals, periodically sending data regardless of whether its own state changes, resulting in a large amount of invalid reporting power consumption.

[0008] To address the aforementioned technical problems, according to one aspect of the present invention, the present invention provides the following technical solution:

[0009] A low-power short-range communication scheduling method for IoT terminals is provided. The scheduling method operates in a short-range IoT networking system consisting of a gateway node and several IoT terminals equipped with NFC / BLE / Zigbee short-range communication modules. The gateway node performs terminal access control, time slot resource allocation, and communication task scheduling. Each IoT terminal is configured with a sleep-wake time-sharing power management unit.

[0010] The scheduling method specifically includes the following steps:

[0011] Step 1: Terminal hierarchical reporting, terminal status changes and power-on reporting of power consumption, data volume, and channel quality, gateway classifies terminals into three levels;

[0012] Step 2: Dynamic time slot resource pre-allocation, allocating dedicated time slots according to priority, and terminals with inferior channels can only use scattered idle time slots;

[0013] Step 3: Start and stop communication scheduling in different modes, and control the start and stop of modules in a hierarchical manner. High priority modules are always on, medium priority modules are woken up on a timed basis, low priority modules are woken up in fragmented time slots, and modules are put into hibernation and powered off during other periods.

[0014] Step 4: Dynamically adjust and schedule the link status, dynamically expand and contract the time slots based on packet loss and battery level, and delay non-urgent data when the battery level is low.

[0015] Step 5: Reclaim and reuse idle time slots. Periodically reclaim idle time slots and redistribute them to data backlog terminals to form a scheduling closed loop.

[0016] As a preferred embodiment of the low-power short-range communication scheduling method for IoT terminals described in this invention, in step one, the terminals report hierarchically, and each IoT terminal reports its real-time remaining power, the amount of business data to be transmitted, and the channel quality of the short-range communication link to the nearest gateway when it is powered on and its status changes. The gateway divides all terminals into three terminal levels: high-priority real-time terminals, medium-priority periodic terminals, and low-priority sleep terminals based on the reported information.

[0017] In step two, the gateway pre-allocates dynamic time slot resources based on the hierarchical results and according to the priority order of terminal level from high to low. It splits the total time slot resources for near-field communication, allocates dedicated communication time slot segments for terminals of different levels, reserves fragmented idle time slots for low-priority dormant terminals, and cancels the continuous time slot configuration for terminals with channel quality below a preset threshold, allowing only fragmented idle time slots to be reused.

[0018] In step three, the communication scheduling is divided into different modes. High-priority terminals keep their short-range communication modules constantly running and sending and receiving data in their dedicated time slots. Medium-priority terminals only wake up their communication modules in their allocated time slots to complete batch data aggregation and uploading, and enter a shallow sleep state in non-allocated time slots. Low-priority terminals are only woken up by the gateway in fragmented idle time slots, and enter a deep sleep state for the remaining time slots, cutting off the power supply to the short-range communication modules.

[0019] The working mode of the IoT terminal is adjusted by the multi-mode start-stop communication scheduling. While ensuring the work content, the power consumption of the IoT terminal is reasonably adjusted. During the operation of the IoT terminal, the work content and power consumption of the IoT terminal are recorded in real time. By comparing the real-time work content and power consumption of the IoT terminal, as well as the changes in work content and power consumption of the IoT terminal within a certain time limit, the staff can analyze whether the work content and power consumption of the IoT terminal are proportional, so that the staff can make manual intervention adjustments. Based on the power consumption and work content recorded data of the IoT terminal, the staff can adjust the gateway time slot allocation rules and the terminal sleep management method as needed.

[0020] The link status dynamic correction scheduling described in step four involves the gateway collecting real-time data on packet loss rate and power consumption of each terminal. When a terminal continuously loses more packets than the limit, the terminal's time slot is temporarily expanded. When the remaining power of a terminal is lower than the warning threshold, its communication time slot is reduced and non-urgent data is postponed to subsequent idle time slots for unified transmission.

[0021] In step five, idle time slots are reclaimed and reused. After each scheduling cycle, the gateway reclaims all idle time slots that have not been occupied throughout the entire time period and re-integrates and allocates them to terminals with backlogged data to be transmitted in the next cycle, thus completing closed-loop dynamic scheduling.

[0022] As a preferred embodiment of the low-power short-range communication scheduling method for IoT terminals described in this invention, the terminal reporting operation is initiated only when the terminal is powered on and its state changes. When there is no state change, the terminal remains silent and does not report data, thus avoiding unnecessary power consumption caused by frequent reporting.

[0023] As a preferred embodiment of the low-power short-range communication scheduling method for IoT terminals described in this invention, the gateway synchronously records the classification results of each terminal when classifying terminal levels. The classification results are updated in real time with the next data reported by the terminal, and the classification status is not fixed for a long period of time.

[0024] As a preferred embodiment of the low-power short-range communication scheduling method for IoT terminals described in this invention, the gateway distinguishes between continuous time slots and fragmented idle time slots. The fragmented idle time slots are taken from the remaining scattered idle communication resources after allocation by terminals at all levels, and do not occupy the main communication time slots of the system separately.

[0025] As a preferred embodiment of the low-power short-range communication scheduling method for IoT terminals described in this invention, a low-quality channel terminal whose continuous time slots are cancelled can only access the channel to transmit data when fragmented idle time slots arrive, and cannot occupy any continuous dedicated time slots.

[0026] As a preferred embodiment of the low-power short-range communication scheduling method for IoT terminals described in this invention, in the shallow sleep state, the terminal only retains the gateway signaling monitoring function, and the short-range communication module does not perform data transmission and reception; in the deep sleep state, the power supply to the communication module is directly cut off, and the channel signal is no longer continuously monitored.

[0027] As a preferred embodiment of the low-power short-range communication scheduling method for IoT terminals described in this invention, the gateway wakes up low-priority terminals in batches, staggering the access times of different terminals to prevent channel conflicts caused by multiple terminals accessing simultaneously.

[0028] As a preferred embodiment of the low-power short-range communication scheduling method for IoT terminals described in this invention, the non-urgent data that the gateway delays storing is uniformly stored in the gateway's local cache, and is prioritized for transmission after a subsequent idle time slot appears.

[0029] As a preferred embodiment of the low-power short-range communication scheduling method for IoT terminals described in this invention, the idle time slots recovered by the gateway are preferentially allocated to terminals with a large backlog of data to be transmitted, and the remaining time slots are then allocated to other terminals as needed.

[0030] Compared with the prior art, the beneficial effects achieved by the present invention are:

[0031] 1. In this invention, by abandoning the unified scheduling mode of all terminals, hierarchical management is completed based on terminal power, amount of data to be sent, and channel quality. High-priority terminals occupy communication time slots first to ensure timely transmission of emergency data. This solves the resource mismatch problem caused by various terminals occupying time slots equally from the resource allocation level. Terminals only report parameters when powered on or when their own state changes, and remain silent when there are no state fluctuations. This effectively reduces the power consumption of useless communication of terminals. Deep sleep directly cuts off the power supply of the communication module. The module start and stop can be flexibly controlled according to business needs, further reducing the idle power consumption of terminals.

[0032] 2. In this invention, dedicated time slots and fragmented time slots are divided according to the terminal level. Terminals with poor channel quality can only reuse fragmented time slots, avoiding the long-term occupation of complete time slots by inferior links and improving the overall utilization rate of time slots. The gateway dynamically adjusts time slot resources based on packet loss and remaining power. Terminals with low power temporarily suspend non-urgent data transmission. At the same time, idle time slots are recycled and re-allocated throughout the entire cycle, realizing closed-loop utilization of communication resources. Under the premise of ensuring basic communication capabilities, the overall power consumption of terminals in the network is reduced in all aspects.

[0033] 3. In this invention, a three-level classification is completed based on the power consumption, amount of data to be transmitted, and channel quality reported by the terminal, breaking the one-size-fits-all scheduling mode. Emergency business terminal resources are given priority to avoid alarm information delays. Ordinary terminals reduce communication frequency as needed, reducing ineffective power consumption from the source. Idle time slots in the scheduling cycle are uniformly recycled and redistributed, and idle resources flow to terminals with data backlog, realizing time slot closed-loop reuse, further optimizing resource allocation. The terminal's working content and power consumption data are recorded throughout the process. Staff can use the records to reverse optimize time slots and sleep rules, facilitating subsequent iterative optimization of scheduling strategies. Attached Figure Description

[0034] Figure 1 This is a schematic diagram of the steps of the present invention;

[0035] Figure 2 This is a detailed flowchart of the present invention;

[0036] Figure 3 This is a schematic diagram of the terminal hierarchical reporting method of the present invention;

[0037] Figure 4 This is a schematic diagram of the dynamic time slot resource pre-allocation of the present invention. Detailed Implementation

[0038] To make the objectives, technical solutions, and advantages of the present invention clearer, the embodiments of the present invention will be described in further detail below with reference to the accompanying drawings.

[0039] This invention provides a low-power short-range communication scheduling method for IoT terminals. It has the advantages of abandoning the unified scheduling mode for all terminals, and completing hierarchical management based on terminal power, amount of data to be transmitted, and channel quality. High-priority terminals occupy communication time slots first to ensure timely transmission of emergency data. It solves the resource mismatch problem caused by various terminals occupying the same time slots from the resource allocation level. The terminal only reports parameters when it is powered on or when its own state changes. It remains silent when there is no state fluctuation, effectively reducing the power consumption of the terminal in useless communication. Deep sleep directly cuts off the power supply of the communication module. The module start and stop can be flexibly controlled according to business needs, further reducing the idle power consumption of the terminal.

[0040] Please see Figure 1-4A low-power short-range communication scheduling method for IoT terminals is disclosed. The method operates in a short-range IoT network system consisting of a gateway node and several IoT terminals equipped with NFC / BLE / Zigbee short-range communication modules. The gateway node performs terminal access control, time slot resource allocation, and communication task scheduling. Each IoT terminal is configured with a sleep-wake time-sharing power management unit. The scheduling method specifically includes the following steps: Step 1: Terminal hierarchical reporting. Terminals report power consumption, data volume, and channel quality upon status changes and power-on. The gateway classifies terminals into three levels. Step 2: Dynamic time slot resource pre-allocation. Dedicated time slots are allocated according to priority. Terminals with poor channel quality can only use scattered idle time slots. Step 3: Mode-based start / stop communication scheduling. Module start / stop is hierarchically controlled. High-priority terminals are always on, medium-priority terminals are woken up periodically, and low-priority terminals are woken up in fragmented time slots. Terminals are put into sleep mode and powered off during other periods. Step 4: Dynamic link status correction scheduling. Time slots are dynamically expanded or contracted based on packet loss and power consumption. Non-urgent data is delayed when power is low.

[0041] Step 5: Reclaim and reuse idle time slots. Periodically reclaim idle time slots and redistribute them to terminals with data backlog, forming a scheduling closed loop. By abandoning the unified scheduling mode for all terminals, hierarchical management is achieved based on terminal power, amount of data to be transmitted, and channel quality. High-priority terminals occupy communication time slots first, ensuring timely transmission of emergency data. This solves the resource mismatch problem caused by various terminals occupying the same time slots from the resource allocation level. Terminals only report parameters when powered on or when their own state changes, and remain silent when there are no state fluctuations, effectively reducing the power consumption of useless communication of terminals. Deep sleep directly cuts off the power supply of the communication module, and the start and stop of the module can be flexibly controlled according to business needs, further reducing the idle power consumption of terminals.

[0042] In step one, terminals report in a hierarchical manner. When each IoT terminal powers on or changes its status, it reports its real-time remaining power, the amount of business data to be transmitted, and the channel quality of the short-range communication link to the nearest gateway. Based on the reported information, the gateway classifies all terminals into three levels: high-priority real-time terminals, medium-priority periodic terminals, and low-priority dormant terminals. In step two, dynamic time slot resource pre-allocation is carried out. Based on the hierarchical results, the gateway splits the total short-range communication time slot resources according to the priority order of terminal level from high to low, allocates dedicated communication time slot segments for terminals of different levels, reserves fragmented idle time slots for low-priority dormant terminals, and cancels the continuous time slot configuration for terminals with channel quality lower than a preset threshold, allowing only fragmented idle time slots to be reused.

[0043] In step three, communication scheduling is implemented in a mode-based manner. High-priority terminals maintain their near-field communication modules constantly active and transmit / receive data within their dedicated time slots. Medium-priority terminals only wake up their communication modules during their allocated time slots to complete batch data aggregation and uploading, and enter a shallow sleep state during unallocated time slots. Low-priority terminals are only woken up by the gateway during fragmented idle time slots, and remain in deep sleep for the remaining time, cutting off power to their near-field communication modules. By adjusting the working mode of IoT terminals through this mode-based communication scheduling, the power consumption of IoT terminals is reasonably adjusted while ensuring the functionality of the terminals. During the operation of IoT terminals, the functionality and power consumption of the terminals are recorded in real time. By comparing the real-time functionality and power consumption of IoT terminals, as well as the changes in functionality and power consumption within a certain time limit, staff can analyze whether the functionality and power consumption of IoT terminals are proportional, allowing for manual intervention. Based on the power consumption and functionality data recorded by IoT terminals, staff can adjust the gateway time slot allocation rules and terminal sleep control methods as needed.

[0044] In step four, the link status is dynamically corrected and scheduled. The gateway collects the packet loss rate and power consumption data of each terminal in real time. When the terminal continuously loses more packets than the limit, the time slot of the terminal is temporarily expanded. When the remaining power of the terminal is lower than the warning threshold, its communication time slot is reduced and non-urgent data is postponed to the subsequent idle time slot for unified transmission. In step five, the idle time slot is recycled and reused. After each scheduling cycle, the gateway reclaims the idle time slots that have not been occupied throughout the time period and re-integrates and allocates them to the terminals with backlog of data to be transmitted in the next cycle, thus completing the closed-loop dynamic scheduling.

[0045] Terminal reporting is initiated proactively only when the terminal is powered on or its state changes. When there is no state change, the terminal remains silent and does not report data to avoid unnecessary power consumption caused by frequent reporting. When the gateway classifies terminals, it records the classification results of each terminal simultaneously. The classification results are updated in real time with the next data report from the terminal, and the classification status is not fixed for a long time. The gateway distinguishes between continuous time slots and fragmented idle time slots. Fragmented idle time slots are taken from the remaining scattered idle communication resources after the allocation of terminals at each level and do not occupy the main communication time slot of the system. Inferior channel terminals whose continuous time slots have been canceled can only access the channel to transmit data when fragmented idle time slots arrive and cannot occupy any continuous dedicated time slots.

[0046] In shallow sleep mode, the terminal only retains the gateway signaling listening function, and the near-field communication module does not transmit or receive data; in deep sleep mode, the power supply to the communication module is directly cut off, and the continuous listening to the channel signal is no longer performed; when the gateway wakes up low-priority terminals, it wakes them up in batches in sequence, and different terminals access at different times to prevent multiple terminals from accessing at the same time and causing channel conflicts; non-urgent data that the gateway delays is uniformly stored in the gateway's local cache, and is given priority for transmission when a subsequent idle time slot appears; the idle time slots reclaimed by the gateway are given priority to terminals with a large amount of backlogged data to be transmitted, and the remaining time slots are then allocated to other terminals as needed.

[0047] The workflow of this invention is as follows: First, in the terminal hierarchical reporting stage, the IoT terminal does not report data frequently at fixed intervals. It only actively uploads three key parameters to the nearest gateway when the device is powered on or when its own power level, the amount of data to be transmitted, or the channel quality changes. If the terminal's operating status does not change, it will remain silent and stop reporting indefinitely, reducing power consumption caused by sending useless data. After receiving the terminal's reported information, the gateway combines the reported remaining power level, the amount of data to be transmitted, and the link channel quality to classify all access terminals into three categories: high-priority real-time terminals, medium-priority periodic terminals, and low-priority dormant terminals. The gateway synchronously stores the hierarchical results of each terminal. When a terminal reports new data again, the gateway refreshes the corresponding terminal level in real time. The hierarchical results change dynamically and are not permanently locked.

[0048] After completing the terminal classification, step two, dynamic time slot resource pre-allocation, is executed. The gateway splits the overall system communication time slots in order from high priority to low priority, allocating dedicated continuous communication time slots for high-priority and medium-priority terminals respectively. At the same time, fragmented idle time slots are collected from the remaining resources allocated at each level of time slots and reserved specifically for low-priority dormant terminals. The fragmented time slots are taken from the remaining scattered resources and do not occupy the main system time slots. For inferior channel terminals whose channel quality does not meet the usage standards, the gateway directly cancels the permission of such devices to use continuous time slots. Inferior channel terminals can only rely on fragmented idle time slots for data transmission and cannot occupy any dedicated continuous time slots, thus avoiding the waste of high-quality spectrum resources by inferior links.

[0049] The process then proceeds to a three-step communication scheduling mechanism, which differentiates the start and stop of communication modules based on terminal priority. High-priority terminals maintain their communication modules throughout their dedicated time slots, ready to receive and send emergency business data at any time. Medium-priority terminals are only awakened during their allocated time slots, where they aggregate and upload multiple sets of data in batches. When outside their allocated time slots, they enter a shallow sleep state, where they only retain gateway signaling listening while the communication modules cease data transmission and reception. Low-priority terminals are only awakened by the gateway in staggered batches during fragmented idle time slots to avoid channel conflicts caused by multiple terminals accessing simultaneously. During other times, they enter deep sleep and have their communication modules powered off. Terminals record their work content and real-time power consumption throughout the process. Staff retrieve these records, compare the patterns of work changes and power consumption changes, and manually adjust the gateway time slot allocation rules and terminal sleep control strategies based on the analysis results.

[0050] The next step is to execute step four, which involves dynamic adjustment and scheduling of the link status. The gateway collects packet loss data and power consumption information of all terminals in the network in real time. When a terminal continuously loses packets beyond the normal range, the gateway temporarily expands the time slot of that terminal to ensure communication stability. When the remaining power of the terminal drops to the warning value, the gateway compresses the available time slot of that terminal and caches non-urgent data inside the device to the local gateway, waiting for subsequent idle time slots to appear before prioritizing transmission.

[0051] Finally, step five, idle time slot recycling and reuse, is performed. After a single scheduling cycle ends, the gateway collects all idle and unused time slots within the cycle and integrates them before the next round of scheduling begins. These slots are then prioritized for allocation to terminals with a large amount of pending data or severe data backlog. The remaining idle time slots are then allocated to other devices as needed. Once this round of scheduling is completed, the system immediately starts a new round of full-process cyclic scheduling.

[0052] Although the present invention has been described above with reference to embodiments, various modifications can be made and components can be replaced with equivalents without departing from the scope of the invention. In particular, as long as there is no structural conflict, the features in the disclosed embodiments can be combined with each other in any manner. The lack of an exhaustive description of these combinations in this specification is merely for the sake of brevity and resource conservation. Therefore, the present invention is not limited to the specific embodiments disclosed herein, but includes all technical solutions falling within the scope of the claims.

Claims

1. A low-power short-range communication scheduling method for Internet of Things (IoT) terminals, characterized in that, The scheduling method operates in a near-field IoT network system consisting of a gateway node and several IoT terminals equipped with NFC / BLE / Zigbee near-field communication modules. The gateway node performs terminal access control, time slot resource allocation, and communication task scheduling. Each IoT terminal is configured with a sleep-wake time-sharing power management unit. The scheduling method specifically includes the following steps: Step 1: Terminal hierarchical reporting, terminal status changes and power-on reporting of power consumption, data volume, and channel quality, gateway classifies terminals into three levels; Step 2: Dynamic time slot resource pre-allocation, allocating dedicated time slots according to priority, and terminals with inferior channels can only use scattered idle time slots; Step 3: Start and stop communication scheduling in different modes, and control the start and stop of modules in a hierarchical manner. High priority modules are always on, medium priority modules are woken up on a timed basis, low priority modules are woken up in fragmented time slots, and modules are put into hibernation and powered off during other periods. Step 4: Dynamically adjust and schedule the link status, dynamically expand and contract the time slots based on packet loss and battery level, and delay non-urgent data when the battery level is low. Step 5: Reclaim and reuse idle time slots. Periodically reclaim idle time slots and redistribute them to data backlog terminals to form a scheduling closed loop.

2. The low-power short-range communication scheduling method for IoT terminals according to claim 1, characterized in that, The terminal hierarchical reporting described in step one involves each IoT terminal reporting its real-time remaining power, the amount of business data to be transmitted, and the channel quality of the short-range communication link to the nearest gateway when it is powered on and its status changes. The gateway then divides all terminals into three levels based on the reported information: high-priority real-time terminals, medium-priority periodic terminals, and low-priority sleep terminals. In step two, the gateway pre-allocates dynamic time slot resources based on the hierarchical results and according to the priority order of terminal level from high to low. It splits the total time slot resources for near-field communication, allocates dedicated communication time slot segments for terminals of different levels, reserves fragmented idle time slots for low-priority dormant terminals, and cancels the continuous time slot configuration for terminals with channel quality below a preset threshold, allowing only fragmented idle time slots to be reused. In step three, the communication scheduling is divided into different modes. High-priority terminals keep their short-range communication modules constantly running and sending and receiving data in their dedicated time slots. Medium-priority terminals only wake up their communication modules in their allocated time slots to complete batch data aggregation and uploading, and enter a shallow sleep state in non-allocated time slots. Low-priority terminals are only woken up by the gateway in fragmented idle time slots, and enter a deep sleep state for the remaining time slots, cutting off the power supply to the short-range communication modules. The working mode of the IoT terminal is adjusted by the multi-mode start-stop communication scheduling. While ensuring the work content, the power consumption of the IoT terminal is reasonably adjusted. During the operation of the IoT terminal, the work content and power consumption of the IoT terminal are recorded in real time. By comparing the real-time work content and power consumption of the IoT terminal, as well as the changes in work content and power consumption of the IoT terminal within a certain time limit, the staff can analyze whether the work content and power consumption of the IoT terminal are proportional, so that the staff can make manual intervention adjustments. Based on the power consumption and work content recorded data of the IoT terminal, the staff can adjust the gateway time slot allocation rules and the terminal sleep management method as needed. The link status dynamic correction scheduling described in step four involves the gateway collecting real-time data on packet loss rate and power consumption of each terminal. When a terminal continuously loses more packets than the limit, the terminal's time slot is temporarily expanded. When the remaining power of a terminal is lower than the warning threshold, its communication time slot is reduced and non-urgent data is postponed to subsequent idle time slots for unified transmission. In step five, idle time slots are reclaimed and reused. After each scheduling cycle, the gateway reclaims all idle time slots that have not been occupied throughout the entire time period and re-integrates and allocates them to terminals with backlogged data to be transmitted in the next cycle, thus completing closed-loop dynamic scheduling.

3. The low-power short-range communication scheduling method for IoT terminals according to claim 2, characterized in that, The terminal reporting operation is initiated only when the terminal is powered on or when its state changes. When there is no state change, the terminal remains silent and does not report data, thus avoiding unnecessary power consumption caused by frequent reporting.

4. The low-power short-range communication scheduling method for IoT terminals according to claim 3, characterized in that, When the gateway classifies terminals, it synchronously records the classification results of each terminal. The classification results are updated in real time with the next data reported by the terminal, and the classification status is not fixed for a long time.

5. The low-power short-range communication scheduling method for IoT terminals according to claim 4, characterized in that, The gateway distinguishes between continuous time slots and fragmented idle time slots. Fragmented idle time slots are taken from the remaining scattered idle communication resources after allocation by terminals at all levels, and do not occupy the main communication time slots of the system separately.

6. The low-power short-range communication scheduling method for IoT terminals according to claim 5, characterized in that, A low-quality channel terminal whose continuous time slots have been cancelled can only access the channel to transmit data when fragmented idle time slots arrive, and cannot occupy any continuous dedicated time slots.

7. A low-power short-range communication scheduling method for IoT terminals according to claim 6, characterized in that, In the shallow sleep state, the terminal only retains the gateway signaling monitoring function, and the near-field communication module does not perform data transmission and reception; in the deep sleep state, the power supply to the communication module is directly cut off, and the channel signal is no longer continuously monitored.

8. A low-power short-range communication scheduling method for IoT terminals according to claim 7, characterized in that, When the gateway wakes up low-priority terminals, it wakes them up in batches and staggers the access times of different terminals to prevent multiple terminals from accessing at the same time and causing channel conflicts.

9. A low-power short-range communication scheduling method for IoT terminals according to claim 8, characterized in that, Non-urgent data that is delayed by the gateway is uniformly stored in the gateway's local cache and will be prioritized for transmission once a subsequent idle time slot becomes available.

10. A low-power short-range communication scheduling method for IoT terminals according to claim 9, characterized in that, The idle time slots recovered by the gateway are first allocated to terminals with a large backlog of data to be transmitted, and the remaining time slots are then allocated to other terminals as needed.

Images