A low-power internet of things terminal access method

Abstract

The application relates to a low-power-consumption Internet of Things terminal access method, relates to the field of low-power-consumption Internet of Things, and comprises the following steps: receiving a time period and a connection device in response to a received signal; dividing the time period into a sleep period and an active period based on a preset distribution ratio, wherein the sleep period and the active period appear alternately in cycles; entering a preset deep sleep state in the sleep period; and entering a preset active access state in the active period. The application has the effect of reducing additional energy consumption caused by invalid wake-up and invalid monitoring.

Description

Technical Field

[0001] This invention relates to the field of low-power Internet of Things (IoT), and more particularly to a low-power IoT terminal access method. Background Technology

[0002] Currently, the Internet of Things (IoT) technology, with its ubiquitous sensing, efficient interconnection, and intelligent processing characteristics, has deeply penetrated all aspects of social production and life, demonstrating significant technological advantages and application value. The IoT relies on diverse sensing terminals to achieve comprehensive monitoring of environmental parameters, equipment status, user behavior, and other aspects. Compared to traditional single-point data collection methods, the IoT, through large-scale heterogeneous device networking, can cover multi-dimensional data such as time, space, and environment, providing a high-granularity and timely information foundation for subsequent analysis.

[0003] To extend the battery life of IoT terminal devices, the IoT field has developed multi-layered low-power solutions. At the hardware level, ultra-low-power chips and energy harvesting technologies are employed; at the communication protocol level, narrowband technologies such as LoRaWAN and NB-IoT reduce radio frequency power consumption through spread spectrum technology and low duty cycle design. Dynamic reception mechanisms have become a key optimization method, where the device only activates the radio frequency module within a preset time window or when specific triggering conditions are detected, such as vibration or changes in lighting, while remaining in deep sleep mode the rest of the time.

[0004] Regarding the aforementioned technologies, while dynamic reception strategies effectively save energy, they suffer from issues such as ineffective wake-up and ineffective listening. When the device is in a noisy environment or experiencing network interference, it may frequently receive incomplete data packets or non-target information, leading to repeated wake-up-sleep cycles and causing additional energy consumption. Summary of the Invention

[0005] To reduce the additional energy consumption caused by invalid wake-ups and invalid listening, this invention provides a low-power IoT terminal access method.

[0006] This invention provides a low-power IoT terminal access method, which adopts the following technical solution: A low-power IoT terminal access method, characterized by comprising: Step 1: In response to the received signal, the reception time period and the connected device; Step 2: Divide the time period into a dormant period and an active period based on a preset allocation ratio, wherein the dormant period and the active period alternate in a cycle; Step 3: During the dormancy period, enter a preset deep dormancy state; Step 4: During the activation period, enter the preset activation access state.

[0007] By adopting the above technical solution, this method achieves periodic sleep and activation of IoT terminals through dynamic time period division, significantly reducing energy consumption when the device is idle. This design solves the high power consumption problem caused by traditional IoT terminals residing in the communication channel for extended periods, while avoiding the signal collision risk caused by frequent wake-ups. Its core advantage lies in reducing the overall energy consumption of the device to near the theoretical limit of the hardware while maintaining basic connectivity through refined resource allocation in the time dimension. This effectively extends the terminal's battery life and reduces the operation and maintenance costs of large-scale deployments.

[0008] Optionally, during the activation period, the specific method for entering the activated access state includes: Step 40: Obtain the initial reference time, which is the time stamp of the terminal device when it first pairs with the connected device after receiving the time period; Step 41: Receive a unified timeline, which is independently calculated by the connected device based on the initial reference time, the sleep period, and the activation period; Step 42: Based on the unified timeline, obtain the start time, end time, and re-verification time of all activation periods within the preset running time. Define the start time of a single activation period as the activation start time and the end time of a single activation period as the activation end time. The re-verification time is the time when the unified timeline needs to be recalibrated. Step 43: Based on the connected device, find the connected device collaboration strategy scheme from the preset connected device collaboration strategy library; Step 44: Based on the connection device collaboration strategy, the activation period is divided into multiple data exchange time windows, and each data exchange time window is the time for the terminal device to exchange data with the corresponding connection device; Step 45: If the preset radio frequency module is turned on at the activation start time; Step 46: Exchange data with the connected device within the data exchange time window; Step 47: At the activation deadline, turn off the radio frequency module; Step 48: When re-verifying the time, obtain the initial reference time again and re-execute step 41.

[0009] By adopting the above technical solution, this method achieves periodic low-power operation and efficient time coordination of IoT terminals. Its core lies in constructing a unified timeline based on an initial reference time, dynamically dividing the sleep period and the active period, and solving the high energy consumption problem caused by continuous monitoring in traditional IoT devices by splitting the active period into multiple data exchange windows through a connected device coordination strategy. Simultaneously, the unified timeline ensures clock alignment between devices, reducing the time for terminal data exchange, which helps extend battery life and reduce power consumption.

[0010] Optionally, the method for exchanging data with the connected device within the data exchange time window includes: Step 460: Determine the data reception time period and data transmission time period of the data exchange time window according to the preset data exchange scheme; Step 461: Receive the data reception start time, data transmission start time, and data reception signal, and generate a data transmission signal; Step 462: If both the data receiving signal and the data transmitting signal exist simultaneously at the data receiving start time, receive data from the connected device and accumulate the receiving time; Step 4620: When the receiving time exceeds the data receiving time period, stop receiving data from the connected device, start outputting data, and accumulate the transmission time; Step 4621: When the transmission time exceeds the data transmission time period, stop the data output; Step 463: When the data receiving signal is not present, directly output the data; Step 464: When the data transmission signal is not present, directly receive the data; Step 465: No operation is performed when neither the data receiving signal nor the data transmitting signal is present.

[0011] By adopting the above technical solution, the data exchange time window is divided into receiving and sending periods, reducing the risk of data receiving and sending conflicts during data exchange between terminals. Its core solution addresses the resource contention and optimization conflicts caused by send-receive conflicts in communication, and reduces the risk of conflicts during data interaction through time accumulation and timeout forced handover mechanisms.

[0012] Optionally, it also includes a method for stopping data reception by the connected device and starting data output when the reception time exceeds the data reception period, the method comprising: Step 46210: Obtain the output data; Step 46211: Based on preset priority rules, classify the output data into high-priority data and ordinary-priority data; Step 46212: The output data to be sent is classified and stored in a priority storage area and a normal storage area. The priority storage area is dedicated to storing the high-priority data, and the normal storage area is dedicated to storing the normal-priority data. Step 46213: Send all the high-priority data in the priority storage area when the sending time just falls into the data sending time period; Step 46214: When the transmission time falls within the data transmission time period and a preset priority output empty state signal is received, send the normal priority data to the connected device; Step 46215: When the transmission time exceeds the data transmission time period and the priority output empty state signal is not received, a preset data transmission abnormality signal is issued.

[0013] By adopting the above technical solution, the system intelligently switches to data output mode after data reception timeout and optimizes transmission resource allocation through a priority classification strategy. Its core solution addresses the conflict between high-priority data and ordinary data within a limited transmission window under unclassified conditions, ensuring that critical information is sent first. Simultaneously, it triggers ordinary data transmission through status signals, reducing wasted transmission time. This design improves the real-time performance and reliability of data transmission and avoids blocking of high-priority tasks.

[0014] Optional, also includes: Step 46216: When the transmission time exceeds the data transmission time period and no preset normal output empty state signal is received, the normal priority data that has not been transmitted is defined as data to be continued, and the number of survival cycles is accumulated at the next activation start time. Step 462160: When the transmission time falls within the data transmission time period and the normal output empty state signal is received, if the number of survival cycles is less than the preset maximum number of survival cycles threshold, the data to be transmitted corresponding to the number of survival cycles will be output. Step 462161: When the number of survival cycles is equal to the maximum number of survival cycles threshold, delete the corresponding pending transmission data.

[0015] By adopting the above technical solution, intelligent transmission and lifecycle management of ordinary priority data are achieved. The core solution addresses the problem of incomplete transmission of ordinary data due to insufficient activation period. By marking data to be retransmitted and tracking its lifespan, it ensures that incomplete transmissions can be retransmitted in an orderly manner in subsequent cycles, while preventing expired data from occupying system resources for extended periods. This solution improves the reliability of data transmission, reduces data loss caused by single transmission failures, and optimizes storage resource utilization by dynamically cleaning up redundant data through a maximum lifespan threshold.

[0016] Optionally, it further includes a method for not issuing the data transmission error signal when the transmission time exceeds the data transmission time period and the priority output empty state signal is not received, the method comprising: Step 46217: When the transmission time exceeds the data transmission time period and the priority output empty state signal is not received, the radio frequency module is not turned off and the data output to the connected device continues and the duration is extended cumulatively; Step 462170: Upon receiving the priority output empty state signal, define the extension duration at this time as the completion extension time; Step 462171: When the completion extension time exceeds the preset extension time threshold, the data transmission abnormality signal is still issued; Step 4621710: When the completion extension time does not exceed the extension time threshold, a preset pairing signal is sent to the connected device at the next activation start time; Step 4621711: Receive the corrected reference time and output it as the initial reference time. The corrected reference time is the time stamp when the connecting device re-pairs with the terminal device after receiving the pairing signal.

[0017] By adopting the above technical solution, when data reception times out and no priority signal is detected, the RF module's on-time is dynamically extended and the extension duration is tracked, avoiding misjudgments caused by brief signal delays. Its core solution addresses the problem of missed data transmission detection or frequent abnormal alarms caused by fixed timeout mechanisms. It reduces unnecessary abnormal reporting and ensures clock consistency between devices through pairing signal resynchronization.

[0018] Optional, also includes: Step 462172: If the completion extension time does not exceed the extension time threshold, accumulate the number of faults; Step 4621720: If the number of faults exceeds a preset fault count threshold, adjust the length of the dormant period and the activation period based on all the completion extension times corresponding to the number of faults, obtain the adjusted dormant period and the adjusted activation period, and update them to the dormant period and the activation period.

[0019] By adopting the above technical solution, dynamic optimization of the sleep and activation cycles of IoT terminals is achieved. Its core lies in adaptively adjusting cycle parameters through data analysis of accumulated fault counts and extended durations, thus solving the problem of insufficient adaptability of fixed-cycle strategies in complex environments. This improves the stability of data acquisition while ensuring low power consumption, enhancing the long-term stable operation capability of terminals in changing scenarios.

[0020] Optionally, it also includes a data exchange method when the priority output empty state signal is not received after the completion extension time exceeds the duration of the sleep period, the method comprising: Step 462173: When the extended duration exceeds the duration of the sleep period and the priority output empty state signal is not received, immediately interrupt the current data exchange operation; Step 4621730: Define the remaining high-priority data as priority data to be transmitted; Step 4621731: Send the preset key demand data signal; Step 4621732: Receive the required key data signal at the next activation start time, the required key data signal being a signal containing the data type required by the connected device to maintain its own operation; Step 4621733: Output the corresponding priority data to be transmitted based on the required key data signal, and delete the remaining priority data to be transmitted.

[0021] By adopting the above technical solution, when critical data interaction cannot be completed even with an extremely long extension, the operation is forcibly interrupted, and core data transmission is prioritized. Its core solution addresses the reliable delivery of high-priority data in extreme scenarios. By marking remaining data and triggering critical data signals, it ensures that the minimum dataset required for the connected device to maintain operation is transmitted first, while redundant data is cleaned up to avoid resource waste. This design enhances the system's fault tolerance under harsh communication conditions.

[0022] Optionally, it also includes a method for transmitting data even during the deep sleep state, the method comprising: Step 5: In response to a preset emergency interaction signal, determine the terminal device status and emergency connection device; Step 6: When the terminal device is in the deep sleep state, turn on the radio frequency module and exchange data with the emergency connection device; Step 7: When the terminal device is in the active access state, define the currently data-exchanging connection device as the lagging connection device, disconnect the data exchange with the lagging connection device, and switch to data exchange with the emergency connection device.

[0023] By adopting the above technical solution, priority transmission of emergency data and dynamic connection management in deep sleep mode are achieved. Its core solution addresses the problem of delayed response to critical tasks caused by deep sleep in IoT devices, rapidly waking the radio frequency module through a preset signal trigger, ensuring real-time interaction of emergency data.

[0024] Optional, also includes: Step 8: When the emergency interaction signal disappears, if the terminal device is in the activation period, then continue to execute step 46; Step 9: When the emergency interaction signal disappears, if the terminal device is in the sleep period, it sends a preset emergency pairing signal to the connected device at the next activation start time, and continues to execute steps 40-41.

[0025] By adopting the above technical solution, an adaptive recovery mechanism is implemented after the emergency interaction ends. Its core solution addresses the issue of discrepancies between the device's sleep and activation periods and the predetermined times caused by emergency signals. By distinguishing between activation and sleep scenarios, it dynamically selects either to directly continue data transmission or to resynchronize via an emergency pairing signal, ensuring a smooth transition of the communication link.

[0026] In summary, this application includes at least one of the following beneficial technical effects: By dividing the time cycle into a sleep period and an activation period, and achieving clock synchronization between devices based on an initial reference time and a unified time axis, the terminal device only turns on the radio frequency module to perform data interaction during the activation period, and enters deep sleep during the rest of the time, which significantly reduces ineffective power consumption and extends battery life.

[0027] Within the data exchange window, output data is divided into high priority and normal priority according to preset priority rules. High priority data is stored first and sent quickly, while normal data is retransmitted as needed, ensuring that key information is transmitted first and improving the utilization rate of limited communication resources.

[0028] When responding to an emergency signal, the terminal can be forcibly woken up and switched to the emergency connection device, interrupting the interaction of the lagging connection device to ensure the real-time nature of the emergency task; after the emergency is lifted, normal communication is restored by resetting the base time or sending a pairing signal, taking into account both low power consumption and high reliability requirements. Attached Figure Description

[0029] Figure 1This is a flowchart of a low-power IoT terminal access method according to an embodiment of this application; Figure 2 This is a flowchart of a data exchange method based on the same time axis in an embodiment of this application; Figure 3 This is a flowchart of a method for exchanging data after responding to an emergency interaction signal, as described in this application embodiment. Detailed Implementation

[0030] The present invention will now be described in further detail with reference to the accompanying drawings and embodiments.

[0031] This application discloses a low-power IoT terminal access method. (Refer to...) Figure 1 A low-power IoT terminal access method includes: Step 1: Response to received signal, reception time period and connected device.

[0032] Received signals refer to information carriers in the form of electromagnetic, optical, or acoustic signals that a device obtains from the external environment or other devices, which are used to trigger the terminal to perform subsequent operations.

[0033] The time cycle is the time interval between the execution of periodic tasks by the equipment, which defines the rhythm of the equipment's operating state switching.

[0034] Connecting devices are other hardware or software entities that establish a communication connection with the current terminal and exchange data.

[0035] When the terminal detects a received signal that conforms to a preset protocol or feature, it parses the data fields in the signal, extracts the numerical parameters of the time period and the identification information or network address of the connected device, and then establishes a communication link with the connected device based on this information, and performs subsequent sleep and activation period division and state switching operations according to the time period.

[0036] Step 2: Divide the time period into a dormant period and an active period based on a preset allocation ratio, with the dormant period and the active period alternating in a cycle.

[0037] The hibernation period refers to the time period during which a device operates in a low-power state, maintaining only basic functions or suspending most operations to reduce energy consumption.

[0038] The activation period is the time during which the device resumes normal operation, performs its main tasks, or interacts with external data.

[0039] The allocation ratio refers to the ratio of the dormant period to the active period within a complete time cycle, usually expressed as a percentage or fraction. The allocation ratio is set by the staff, calculated by the terminal connection device, and sent to the terminal. The terminal receives and stores the calculated ratio in its non-volatile memory.

[0040] The significance of alternating dormancy and activation periods lies in the fact that it can ensure that the device completes necessary tasks and maintains normal system operation during the activation period, while significantly reducing energy consumption during the dormancy period, extending the device's battery life or reducing energy consumption. This is especially suitable for power-sensitive scenarios, such as IoT devices and mobile terminals, and achieves an optimized balance between performance and energy consumption through this periodic state switching.

[0041] Step 3: During the hibernation period, enter the preset deep hibernation state.

[0042] Deep sleep refers to a state in which a device shuts down or puts non-essential hardware components, such as the processor core, communication modules, and display drivers, into an extremely low-power mode during its sleep period. Only a small number of necessary monitoring circuits and a minimal system are maintained to achieve the lowest possible power consumption. In this state, the device hardly processes user data or responds to external requests. It only gradually restores hardware power and system operation upon detecting specific wake-up signals, such as timer expiration or emergency interaction signals.

[0043] Step 4: During the activation period, enter the preset activation access state.

[0044] Activated access state refers to the state in which all functional modules (such as processors, communication modules, sensors, etc.) of the device are fully or as needed during the activation period. When the terminal enters normal working mode, it can actively establish communication connections with external devices, receive and process various data requests, and execute predetermined tasks, such as data acquisition, transmission, calculation, and response to external control commands, thereby realizing the complete functions of the device.

[0045] Reference Figure 2 During the activation period, the specific methods for entering the preset activated access state include: Step 40: Obtain the initial reference time.

[0046] The initial reference time is a timestamp recorded when a terminal device first pairs with a connected device after receiving a time cycle. It serves as the starting reference standard for subsequent time calculations and synchronization, providing a time base for data exchange and state switching between devices.

[0047] Step 41: Receive the unified timeline.

[0048] The unified timeline is calculated independently for each connected device based on its initial reference time, dormancy period, and activation period.

[0049] A unified timeline is a timeline established by connected devices based on an initial reference time, with time as the scale. Data interactions between the terminal and connected devices are kept highly synchronized along this timeline. The unified timeline provides a consistent time reference for state switching and data interaction between different devices, ensuring that all devices work collaboratively in the time dimension.

[0050] The unified timeline is obtained as follows: The connected device uses the initial reference time as the origin of the timeline coordinates, and then, based on the known durations of the sleep and active periods, arranges and combines these two time periods sequentially according to time order. For example, the initial reference time is denoted as T0, and the sleep period duration is T... sleep The activation period lasts for T. active Therefore, the initial activation period begins at time T. A =T0, the start time of the dormancy period is T. S =T0+T active After that, the cycle of "dormant period - activation period" is repeated continuously.

[0051] T A,i =T0+(i-1)×(T sleep +T active ); T S,j =T0+T active +(j-1)×(T sleep +T active ); T A,i T represents the start time of the i-th activation period. S,j This indicates the start time of the j-th dormancy period.

[0052] For example, in everyday use, after the fitness tracker and phone are paired and connected, they will interact with each other according to a set time period. At 10:05 AM, precisely within the preset activation period, the fitness tracker and phone enter the data exchange phase. At this time, the fitness tracker transmits collected exercise data, heart rate information, etc., to the phone in real time, while the phone also sends new setting commands, detection condition changes, and other signals to the fitness tracker. At 10:06 AM, the activation period ends, and the fitness tracker stops receiving and sending data to the phone; the phone also simultaneously stops receiving and sending data signals to the fitness tracker, and the fitness tracker enters a sleep phase to reduce power consumption until the next activation period arrives and data interaction resumes.

[0053] Step 42: Based on the unified timeline, obtain the start time, end time and re-verification time of all activation periods within the preset running time. Define the start time of a single activation period as the activation start time, define the end time of a single activation period as the activation end time, and define the re-verification time as the time when the unified timeline needs to be recalibrated.

[0054] Running time refers to the total time period during which the connected device needs to calculate the start time, end time, and re-verification time of all activation periods for both the terminal and the connected device under a unified time axis.

[0055] The runtime is determined by staff through analysis of a large number of IoT terminal devices. Staff continuously refine the runtime through experimentation to ensure it is not too long, as this would cause time shifts in the calculated start and end times of the activation period, affecting the accuracy of the activation period. Conversely, it shouldn't be too short, as this would require terminals to frequently receive new timelines calculated by connected devices, increasing energy consumption.

[0056] The start time of the activation period refers to the moment on a unified timeline when the device switches from a dormant state to a normal working state and begins to perform operations such as data interaction and task processing.

[0057] The activation period ends when the device ends its normal operation and is about to enter a dormant state within an activation period defined by a unified timeline.

[0058] The start and end times of the activation period can be obtained directly from a unified timeline. The specific method for obtaining this information has been explained in step 41 and will not be repeated here.

[0059] Step 43: Based on the connected device, find the connected device collaboration strategy scheme from the preset connected device collaboration strategy library.

[0060] The connectivity device collaboration strategy library is a collection of preset strategies built into connectivity devices, which includes different connectivity device collaboration strategy schemes between terminal devices and connectivity devices.

[0061] The connectivity device collaboration strategy scheme is used to guide the data exchange rules between terminal devices and different types of connectivity devices, including parameters such as connection duration, communication frequency, data exchange mode, and priority allocation.

[0062] The connectivity device collaboration strategy library was developed by researchers who studied numerous parameters required for data exchange between terminal devices and connecting devices, including connection duration, communication frequency, and data priority. The library stores the most typical connection methods for each type of terminal device and connecting device as connectivity strategy schemes. With terminal confirmation, simply inputting the connecting device model allows the system to retrieve the required connectivity device collaboration strategy scheme from the library, specifying the connection duration, communication frequency, and data priority parameters for data interaction with the terminal.

[0063] Step 44: Based on the connected device collaboration strategy, the activation period will be divided into multiple data exchange time windows.

[0064] Each data exchange time window is the time during which a terminal device exchanges data with its corresponding connected device. Each window includes a fixed start time, end time, and communication resources to ensure that data transmission and reception between devices can be completed without conflicts. The number of connected devices waiting to connect is determined through a connection device coordination strategy. Then, based on the size and priority of the data to be exchanged by the connected devices, the activation period is divided into multiple data exchange time windows according to time.

[0065] Step 45: If the preset radio frequency module is turned on at the activation start time.

[0066] A radio frequency (RF) module is a hardware component used for wireless communication. It is responsible for signal transmission and reception and serves as the physical layer interface for interaction between the device and connected devices. Enabling the RF module aims to establish a communication link with the connected device during its activation period, enabling data transmission such as sensor reporting and control command exchange.

[0067] The terminal device sends a startup command to the RF chip through a preset driver or hardware control interface, and simultaneously supplies power to the RF module and starts the communication function.

[0068] Step 46: Exchange data with the connected device within the data exchange time window.

[0069] Step 47: Turn off the RF module at the activation deadline.

[0070] When the activation deadline is reached, the terminal immediately shuts down the radio frequency module to reduce power consumption.

[0071] Step 48: When re-verifying the time, obtain the initial baseline time again and repeat step 41.

[0072] At the reverification point, the system clock reference is updated through the time synchronization mechanism, and periodic tasks, such as the activation-sleep cycle, are restarted. Reacquiring the initial reference time at the reverification point ensures the time synchronization accuracy between the terminal device and the connected device, preventing subsequent periodic disruptions caused by clock drift or accumulated errors, which could lead to a shift in the consistency of the terminal and connected devices on the timeline. The method for obtaining the reference time is described in step 40 and will not be repeated here.

[0073] Methods for exchanging data with connected devices within a data exchange time window include: Step 460: Determine the data reception time period and data transmission time period of the data exchange time window according to the preset data exchange scheme.

[0074] A data exchange scheme is a predefined set of rules used to define the timing, resource allocation, and priority strategies for data interaction between devices. It is a scheme developed by staff through analyzing numerous data interaction processes between terminals and connected devices, enabling them to select different data interaction methods for different connected devices.

[0075] The data reception time period refers to the length of time within the data exchange time window that the terminal device is dedicated to receiving data from the connected device.

[0076] The data transmission time period refers to the length of time within the data exchange time window that the terminal device is specifically dedicated to sending data to the connected device.

[0077] Step 461: Receive the data reception start time, data transmission start time, and data reception signal, and generate the data transmission signal.

[0078] The data reception start time refers to the starting moment when the connected device begins sending data to the terminal. It is calculated by the connected device and sent to the terminal. The terminal device receives the data at the corresponding time to ensure that it is aligned with the sending time of the connected device.

[0079] The data transmission start time refers to the starting moment when the terminal begins sending data to the connected device. It is calculated by the connected device and sent to the terminal to ensure that it does not conflict with the data reception time.

[0080] The data reception signal is a signal sent by the connected device indicating that the terminal has data to receive.

[0081] Data transmission signals are control signals generated by terminal devices during the data transmission period within the activation period, used to indicate their requests or statuses for sending data to connected devices.

[0082] Step 462: If both a data reception signal and a data transmission signal exist at the start time of data reception, receive data from the connected device and accumulate the reception time.

[0083] Reception time refers to the cumulative duration during which a terminal device actually performs data reception operations within the activation period.

[0084] If both data reception and data transmission signals are present at the start of data reception, it indicates that the device faces a conflict between receiving and transmitting during the initial stage of activation. A collaborative strategy is needed to resolve this resource contention. Since receiving operations take precedence over transmitting operations to ensure timely acquisition of critical data, data reception is processed first.

[0085] Step 4620: When the receiving time exceeds the data receiving period, stop receiving data from the connected device, start outputting data, and accumulate the transmission time.

[0086] The transmission time refers to the actual duration during which the terminal device performs data transmission operations within the activation period. These durations are accumulated to determine whether it is time to stop receiving data.

[0087] Step 4621: Stop outputting data when the transmission time exceeds the data transmission period.

[0088] If the transmission time exceeds the data transmission period, it indicates that the device has used up the time within the allocated data transmission period, and therefore it is necessary to stop acquiring data.

[0089] Step 463: Output data directly when the data receiving signal is not available.

[0090] When the data receiving signal is absent, it indicates that the device has not detected the data or instructions that need to be received during the activation period, and then directly enters the data output stage.

[0091] Step 464: If the data transmission signal is not present, directly receive the data.

[0092] When the data transmission signal is absent, it indicates that the device has not detected any data or instructions to be sent during the activation period, and it directly enters the data reception stage.

[0093] Step 465: No operation is performed when neither the data receiving signal nor the data transmitting signal is present.

[0094] When neither the data receiving signal nor the data transmitting signal is present, it indicates that the device has neither a receiving task nor a sending task during the activation period. At this time, the system enters an idle state and does not perform any operation.

[0095] It also includes a method for stopping data reception from the connected device and starting data output when the reception time exceeds the data reception period, the method comprising: Step 46210: Obtain the output data.

[0096] Output data refers to the data to be sent generated by the terminal device during the activation period, including sensor acquisition results, processed status information, or response commands.

[0097] Step 46211: Based on the preset priority rules, classify the output data into high-priority data and ordinary-priority data.

[0098] High-priority data refers to output data that has been marked as urgent or critical based on preset rules and must be sent first to ensure real-time performance. These preset rules are set by staff. Regular-priority data refers to non-urgent, routine data and is allowed to be sent after high-priority data.

[0099] Step 46212: Classify and store the output data to be sent into a priority storage area and a normal storage area. The priority storage area is dedicated to storing high-priority data, and the normal storage area is dedicated to storing normal-priority data.

[0100] Priority storage area refers to a dedicated storage area in the terminal device's memory used to cache high-priority data, ensuring fast access and transmission. Normal storage area refers to a storage area used to cache normal-priority data, which is transmitted after priority storage area data.

[0101] Step 46213: Send all high-priority data in the priority storage area when the sending time just falls into the data sending time period.

[0102] When the transmission time falls within the data transmission period, it indicates that the terminal device's transmission operation has entered the preset data transmission period. At this time, the system will immediately trigger the forced transmission of high-priority data.

[0103] Step 46214: When the transmission time falls within the data transmission time period and a preset priority output empty state signal is received, send normal priority data to the connected device.

[0104] The priority output empty status signal is a feedback signal sent by the connected device to the terminal device after successfully receiving and processing all high-priority data from the terminal device. This signal indicates that the priority storage area has been cleared and the next data interaction can proceed.

[0105] When the sending time falls within the data sending time period, it indicates that if high-priority data has been processed within the data sending time period and the remaining available sending time has not been exhausted, the system can flexibly execute the sending of ordinary priority data.

[0106] Step 46215: When the transmission time exceeds the data transmission period and no priority output empty state signal is received, a preset data transmission abnormality signal is issued.

[0107] If the transmission time exceeds the data transmission period, it indicates that the terminal device has exceeded the preset data transmission period and cannot continue to perform the receiving operation. If no priority output empty status signal is received at this time, it means that there is still high-priority data that has not been completely output, so the system will trigger a data transmission error signal.

[0108] This is an alarm signal automatically triggered by the system when the terminal device's transmission time exceeds the set data transmission time and no priority output empty status signal is received from the connected device. This signal indicates that high-priority data failed to be transmitted within the specified time, which may be due to link failure, device malfunction, or protocol conflict.

[0109] Also includes: Step 46216: When the transmission time exceeds the data transmission period and no preset normal output empty state signal is received, the normal priority data that has not been transmitted is defined as data to be continued, and the number of survival cycles is accumulated at the next activation start time.

[0110] Data to be transmitted refers to ordinary priority data that has not yet been transmitted when the terminal device's transmission time exceeds the end time of the preset data transmission period and no ordinary output empty status signal is received from the connected device.

[0111] The normal output empty state signal is the state signal received by the terminal device after all normal priority data has been output. Its specific generation and reception methods are the same as those of the priority output empty state signal in step 46214, and will not be repeated here.

[0112] The lifetime count refers to the maximum number of time periods that a terminal can allow data awaiting retransmission to remain on the terminal. At the start of each activation period, the system checks and updates the lifetime count of the data awaiting retransmission.

[0113] If the transmission time exceeds the data transmission period and no preset normal output empty status signal is received, it indicates that the normal priority data transmission operation allocated during the current active period failed to complete due to time exhaustion. Therefore, the untransmitted normal priority data must be processed separately.

[0114] Step 462160: When the transmission time falls within the data transmission time period and a normal output empty state signal is received, if the number of survival cycles is less than the preset maximum survival cycle threshold, the data to be transmitted corresponding to the number of survival cycles will be output.

[0115] If the transmission time falls within the data transmission period, it indicates that the ordinary priority data has been successfully received, and the data to be resumed can be output. The maximum lifespan threshold is a preset integer threshold used to limit the maximum number of lifespans of data to be resumed in the retransmission queue. When the lifespan of data to be resumed reaches this threshold, the system will permanently delete the data and stop retransmission. This value is set by the staff.

[0116] When the transmission time falls within the data transmission period, data awaiting transmission with a lifespan count less than the preset maximum lifespan count threshold is considered to still have transmission value. At the same time, there is currently an idle window for data transmission, so the corresponding data awaiting transmission can be output to improve the integrity of data transmission from the terminal device.

[0117] Step 462161: When the number of survival cycles equals the maximum number of survival cycles threshold, delete the corresponding pending data.

[0118] When the number of lifecycles of data to be resumed reaches the preset maximum lifecycle threshold, it means that the corresponding data to be resumed has been stored on the terminal for too long. Since it has not had a transmission opportunity for a long time, the system will determine it as outdated data and perform a deletion operation.

[0119] It also includes a method for not issuing a data transmission error signal when the transmission time exceeds the data transmission period and no priority output empty state signal is received, the method comprising: Step 46217: If the transmission time exceeds the data transmission period and no priority output empty state signal is received, the RF module is not turned off and data output to the connected device continues, and the duration is extended cumulatively.

[0120] When the transmission time exceeds the data transmission period, the system allows the transmission operation to continue instead of immediately shutting down the RF module because the data transmission period is a preset validity period, but the actual transmission may not be completed by the window threshold due to factors such as data volume and network fluctuations. Directly shutting down the RF module at this time may lead to transmission interruption and failure. The system provides a short grace period through an "extended duration" mechanism, allowing the transmission to complete naturally and avoiding resource waste or service failure due to instantaneous timeouts.

[0121] The extension duration refers to the time during which the system continues to perform transmission operations from the moment the data transmission period ends to the moment the priority output empty state signal is received. This extended duration is accumulated to determine whether the extension is short-term or long-term.

[0122] Step 462170: When the priority output empty state signal is received, the extension duration at this time is defined as the completion extension time.

[0123] The receipt of a priority output empty status signal indicates that the high-priority data transmission task has been completed normally.

[0124] The completion delay time is the total delay time from the end of the originally scheduled data transmission period to the receipt of the priority output empty state signal. It is used to measure whether the transmission is completed within the tolerable range.

[0125] Step 462171: If the completion extension time exceeds the preset extension time threshold, a data transmission abnormality signal will still be issued.

[0126] The extension time threshold is used to determine whether the extended time is acceptable. The extension time threshold is set by staff.

[0127] A completion time exceeding the preset extension time threshold indicates that the actual data transmission time has exceeded the system's maximum tolerance range. This could be due to factors such as excessive data volume, transmission interference, equipment failure, or clock asynchrony, leading to low transmission efficiency. The system determines this transmission as abnormal and therefore still issues a data transmission abnormality signal.

[0128] Step 4621710: If the completion extension time does not exceed the extension time threshold, a preset pairing signal is sent to the connected device at the next activation start time.

[0129] If the extension time does not exceed the extension time threshold, it indicates that the data transmission was completed within the system's normal fault tolerance range. Although the total data transmission time exceeded the activation period, it was still within an acceptable range. Therefore, this transmission can be considered successful, and a pairing signal can be sent at the start of the next activation to maintain the connection and synchronization time base between devices.

[0130] The pairing signal is a preset communication identifier sent by the system to the connected device. When the connected device receives the pairing signal, it will re-pair with the terminal and reconfirm the initial reference time.

[0131] Step 4621711: Receive the corrected reference time and output it as the initial reference time. The corrected reference time is the time stamp used when the connected device re-pairs with the terminal device after receiving the pairing signal.

[0132] The corrected reference time is a timestamp used when a connected device and a terminal device re-pair. Its function is to correct the initial reference time of the terminal device through pairing signal interaction, ensuring that the timelines of both parties are synchronized. Even if the completion extension time does not exceed the preset extension time threshold, which is within an acceptable range, the timelines of the terminal's sleep and activation periods will be pushed back due to the completion of the extension time, resulting in a mismatch between the timelines of the terminal and the connected device. Therefore, re-pairing is required.

[0133] Also includes: Step 462172: If the extended time does not exceed the extended time threshold, the cumulative number of faults is recorded.

[0134] The fault count refers to the cumulative number of fault records during system operation due to extended time not exceeding the preset extended time threshold. Each time an extended time occurs (such as data transmission timeout, task execution delay, etc.) and the extended time does not exceed the preset extended time threshold, the fault count is incremented by 1.

[0135] The extension time threshold is a preset upper limit value for the system, used to determine whether a certain extension belongs to a "tolerable fault". This value is set by the staff.

[0136] Step 4621720: If the number of faults exceeds the preset fault count threshold, adjust the length of the dormant period and the activation period based on the completion extension time corresponding to the number of faults, obtain the corrected dormant period and the corrected activation period, and update them as dormant period and activation period.

[0137] The corrected hibernation period refers to the new hibernation duration after the number of failures exceeds a threshold, which is adjusted by the system based on the mode of historical extended periods.

[0138] The revised activation period refers to the new activation duration after the number of failures exceeds a threshold, when the system adjusts the original activation period based on the mode of historical extension times.

[0139] If the number of failures exceeds the preset failure count threshold, it indicates that the current activation period is set too short, causing tasks to frequently approach but not exceed the extended time threshold. The system determines that the number of "tolerable failures" has accumulated too high. Therefore, the cycle configuration needs to be optimized by extending the activation period. The specific method is as follows: extend the activation period based on the mode of the completion extension times for all failures, i.e., the most frequently occurring extension time. For example, if the mode is 5 seconds, extend the activation period by 5 seconds and shorten the dormancy period accordingly. If there are completion extension times with the same number of occurrences, the longest one will be used.

[0140] It also includes a data exchange method when no priority output empty state signal is received after the completion extension time exceeds the sleep period duration, the method including: Step 462173: If the extended duration exceeds the sleep period and no priority output empty state signal is received, immediately interrupt the current data exchange operation.

[0141] If the extended time exceeds the sleep period and no priority output empty state signal is received, it indicates that data transmission has been delayed to the next cycle, seriously consuming system resources and threatening the execution of subsequent tasks. The current operation must be interrupted immediately.

[0142] Step 4621730: Define the remaining high-priority data as priority data to be transmitted.

[0143] Priority pending transmission data refers to portions of high-priority data that have not yet been fully transmitted. The system marks this type of data to ensure that it can continue to be transmitted when resources allow, rather than being mixed with ordinary data.

[0144] Step 4621731: Send a preset key data signal for demand.

[0145] The critical data request signal is a high-priority request signal actively sent by the system after a transmission interruption. It explicitly requests core data from connected devices, such as device status and configuration parameters, to maintain basic functionality. The purpose of this signal is to quickly obtain critical information and transmit the most important data within a limited transmission time.

[0146] Step 4621732: Receive the required critical data signals at the next activation start time. The required critical data signals are signals containing the data types required for the connected device to maintain its operation.

[0147] The required key data signals are the specific data content fed back by the connected device after responding to the required key data signals. They include the minimum necessary information to maintain device operation, such as heartbeat packets and synchronization signals. Their function is to provide the system with a basis for judgment and to filter out the priority data that must be transmitted in the current cycle.

[0148] Step 4621733: Output the corresponding priority data to be transmitted based on the required key data signals, and delete the remaining priority data to be transmitted.

[0149] The system optimizes resources and dynamically adjusts priorities by outputting priority data to be transmitted based on the required key data signals and deleting remaining data. The required key data signals define the minimum operating requirements of the connected devices. Based on this, the system selects high-priority data that is strongly correlated with these requirements, ensuring their priority transmission. Remaining priority data that matches the key data requirements may be outdated or less important, and continuing to transmit it would waste resources. Deleting this data frees up storage space and reduces the transmission load.

[0150] Reference Figure 3 It also includes a method for data transmission that is still required during deep sleep, the method comprising: Step 5: In response to the preset emergency interaction signal, determine the terminal device status and emergency connection device.

[0151] Emergency interaction signals are system-preset signals used to trigger emergency interactions, instructing terminal devices to immediately perform specific operations.

[0152] Terminal device status refers to the type of state a terminal device is in, including deep sleep state and active access state. Emergency connection devices are those marked as the highest priority communication objects by the system when an emergency interaction signal is triggered.

[0153] Step 6: When the terminal device is in deep sleep mode, turn on the radio frequency module and exchange data with the emergency connection device.

[0154] When a terminal device is in deep sleep mode, its default strategy is to shut down the radio frequency module to save power and it cannot respond to ordinary communication requests. However, the appearance of an emergency interaction signal indicates that the current task has the highest priority and the low-power strategy must be broken immediately to perform necessary and urgent data exchange operations.

[0155] Step 7: When the terminal device is in the active access state, define the currently data-exchanging connection device as the lagging connection device, disconnect the data exchange with the lagging connection device, and switch to data exchange with the emergency connection device.

[0156] Lagging connection devices refer to ordinary connection devices that are originally exchanging data when the terminal device is in an active access state. When the system detects an emergency interaction signal, these devices are marked as "lagging" because they have a lower priority than emergency connection devices, and their data exchange needs to be temporarily interrupted to ensure that the emergency task is handled with priority.

[0157] Also includes: Step 8: When the emergency interaction signal disappears, if the terminal device is in the active period, continue to step 46.

[0158] During the activation period, the terminal device's RF module is already in normal working order, and the system time still conforms to the preset activation period time window. At this time, the emergency interaction signal disappears, indicating that the external emergency has been resolved, but the terminal device is still within the normal activation period cycle, requiring no timeline adjustment or resynchronization. Therefore, the system can directly continue the data interaction process.

[0159] Step 9: When the emergency interaction signal disappears, if the terminal device is in a sleep period, it will send a preset emergency pairing signal to the connected device at the next activation start time and continue to execute steps 40-41.

[0160] During the sleep period, the terminal device's radio frequency module is typically off or in a low-power state, and the system time may be offset due to the processing of emergency interaction signals, such as extending the activation period or shortening the sleep period. When the emergency signal disappears, the clock synchronization between the terminal device and connected devices may have been disrupted, and the originally planned activation start time and sleep period length cannot be directly restored.

[0161] Therefore, by sending an emergency pairing signal, the terminal device can renegotiate the time base with the connected device, correcting the cycle disruptions caused by the emergency handling, and ensuring that the scheduling of subsequent activation and sleep periods is consistent with the connected device. The emergency pairing signal is a signal sent by the terminal device to the connected device after the emergency interaction signal disappears during the sleep period, used to quickly restore synchronization and connection between devices.

Claims

1. A low-power IoT terminal access method, characterized in that, include: Step 1: In response to the received signal, the reception time period and the connected device; Step 2: Divide the time period into a dormant period and an active period based on a preset allocation ratio, wherein the dormant period and the active period alternate in a cycle; Step 3: During the dormancy period, enter a preset deep dormancy state; Step 4: During the activation period, enter the preset activation access state; The specific methods for entering the activated access state during the activation period include: Step 40: Obtain the initial reference time, which is the time stamp of the terminal device when it first pairs with the connected device after receiving the time period; Step 41: Receive a unified timeline, which is independently calculated by the connected device based on the initial reference time, the sleep period, and the activation period; Step 42: Based on the unified timeline, obtain the start time, end time, and re-verification time of all activation periods within the preset running time. Define the start time of a single activation period as the activation start time and the end time of a single activation period as the activation end time. The re-verification time is the time when the unified timeline needs to be recalibrated. Step 43: Based on the connected device, find the connected device collaboration strategy scheme from the preset connected device collaboration strategy library. The connected device collaboration strategy scheme is used to guide the data exchange rules between the terminal device and different types of connected devices, including connection duration, communication frequency, data exchange mode, and priority allocation. Step 44: Based on the connection device collaboration strategy, the activation period is divided into multiple data exchange time windows, and each data exchange time window is the time for the terminal device to exchange data with the corresponding connection device; Step 45: If the preset radio frequency module is turned on at the activation start time; Step 46: Exchange data with the connected device within the data exchange time window; Step 47: At the activation deadline, turn off the radio frequency module; Step 48: When the re-verification time is reached, the initial reference time is obtained again and step 41 is executed again; The method for exchanging data with the connected device within the data exchange time window includes: Step 460: Determine the data reception time period and data transmission time period of the data exchange time window according to the preset data exchange scheme; Step 461: Receive the data reception start time, data transmission start time, and data reception signal, and generate a data transmission signal; Step 462: If both the data receiving signal and the data transmitting signal exist simultaneously at the data receiving start time, receive data from the connected device and accumulate the receiving time; Step 4620: When the receiving time exceeds the data receiving time period, stop receiving data from the connected device, start outputting data, and accumulate the transmission time; Step 4621: When the transmission time exceeds the data transmission time period, stop the data output; Step 463: When the data receiving signal is not present, directly output the data; Step 464: When the data transmission signal is not present, directly receive the data; Step 465: No operation is performed when neither the data receiving signal nor the data transmitting signal is present; This also includes a method for stopping data reception from the connected device and starting data output when the reception time exceeds the data reception period, the method comprising: Step 46210: Obtain the output data; Step 46211: Based on preset priority rules, classify the output data into high-priority data and ordinary-priority data; Step 46212: The output data to be sent is classified and stored in a priority storage area and a normal storage area. The priority storage area is dedicated to storing the high-priority data, and the normal storage area is dedicated to storing the normal-priority data. Step 46213: Send all the high-priority data in the priority storage area when the sending time just falls into the data sending time period; Step 46214: When the transmission time falls within the data transmission time period and a preset priority output empty state signal is received, send the normal priority data to the connected device; Step 46215: When the transmission time exceeds the data transmission time period and the priority output empty state signal is not received, a preset data transmission abnormality signal is issued; This also includes: Step 46216: When the transmission time exceeds the data transmission time period and no preset normal output empty state signal is received, the normal priority data that has not been transmitted is defined as data to be continued, and the number of survival cycles is accumulated at the next activation start time. Step 462160: When the transmission time falls within the data transmission time period and the normal output empty state signal is received, if the number of survival cycles is less than the preset maximum number of survival cycles threshold, the data to be transmitted corresponding to the number of survival cycles will be output. Step 462161: When the number of survival cycles is equal to the maximum number of survival cycles threshold, delete the corresponding data to be transmitted. The method further includes a method for not issuing the data transmission error signal when the transmission time exceeds the data transmission time period and the priority output empty state signal is not received. This method includes: Step 46217: When the transmission time exceeds the data transmission time period and the priority output empty state signal is not received, the radio frequency module is not turned off and the data output to the connected device continues and the duration is extended cumulatively; Step 462170: Upon receiving the priority output empty state signal, define the extension duration at this time as the completion extension time; Step 462171: When the completion extension time exceeds the preset extension time threshold, the data transmission abnormality signal is still issued; Step 4621710: When the completion extension time does not exceed the extension time threshold, a preset pairing signal is sent to the connected device at the next activation start time; Step 4621711: Receive the corrected reference time and output it as the initial reference time. The corrected reference time is the time stamp when the connecting device re-pairs with the terminal device after receiving the pairing signal. This also includes a data exchange method when the priority output empty state signal is not received after the completion extension time exceeds the duration of the sleep period, the method comprising: Step 462173: When the extended duration exceeds the duration of the sleep period and the priority output empty state signal is not received, immediately interrupt the current data exchange operation; Step 4621730: Define the remaining high-priority data as priority data to be transmitted; Step 4621731: Send a preset key demand data signal; Step 4621732: Receive the required key data signal at the next activation start time, the required key data signal being a signal containing the data type required by the connected device to maintain its own operation; Step 4621733: Output the corresponding priority data to be transmitted based on the required key data signal, and delete the remaining priority data to be transmitted.

2. The low-power IoT terminal access method according to claim 1, characterized in that, Also includes: Step 462172: If the completion extension time does not exceed the extension time threshold, accumulate the number of faults; Step 4621720: If the number of faults exceeds a preset fault count threshold, adjust the length of the dormant period and the activation period based on all the completion extension times corresponding to the number of faults, obtain the adjusted dormant period and the adjusted activation period, and update them to the dormant period and the activation period.

3. The low-power IoT terminal access method according to claim 1, characterized in that, It also includes a method for transmitting data even during the deep sleep state, the method comprising: Step 5: In response to a preset emergency interaction signal, determine the terminal device status and emergency connection device; Step 6: When the terminal device is in the deep sleep state, turn on the radio frequency module and exchange data with the emergency connection device; Step 7: When the terminal device is in the active access state, define the currently data-exchanging connection device as the lagging connection device, disconnect the data exchange with the lagging connection device, and switch to data exchange with the emergency connection device.

4. The low-power IoT terminal access method according to claim 3, characterized in that, Also includes: Step 8: When the emergency interaction signal disappears, if the terminal device is in the activation period, then continue to execute step 46; Step 9: When the emergency interaction signal disappears, if the terminal device is in the sleep period, it sends a preset emergency pairing signal to the connected device at the next activation start time, and continues to execute steps 40-41.

Images