Sensor-integrated IoT terminal access and data transmission method
By employing channel quality awareness and lightweight encryption caching technology, seamless data transmission for IoT terminals in complex environments is achieved, solving the problems of high reconnection latency and high resource consumption after link interruption, and improving the continuity and efficiency of data transmission.
Patent Information
- Application Number
- CN202611317594.8
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2026-08-28
- Publication Date
- 2026-11-17
AI Technical Summary
Traditional IoT terminals need to re-execute the entire authentication process and session reconstruction after the link is interrupted in complex communication environments, resulting in high data transmission latency, discontinuous transmission, and serious resource consumption, which cannot meet the needs of high-frequency real-time data acquisition.
A channel quality awareness and prediction mechanism is introduced to evaluate the link status in real time, cache the transmission context and skip the full authentication process when the link is restored, and lightweight encryption technology is adopted to achieve seamless breakpoint resumption.
It reduces link recovery latency, lowers resource consumption, and ensures the continuity and efficiency of data transmission, making it suitable for complex environments such as industrial IoT and smart security.
Smart Images

Figure CN123124055A_ABST
Abstract
Description
Technical Field
[0001] This invention relates to the field of IoT terminal communication interface related products, specifically to a method for IoT terminal access and data transmission that integrates sensing and communication. Background Technology
[0002] The sensor-integrated IoT terminal is a core terminal device that integrates sensing, communication, and data acquisition in the Internet of Things (IoT). It is widely used in complex scenarios such as industrial IoT, smart security, environmental monitoring, and smart agriculture, and features multi-dimensional sensor data acquisition, real-time data uploading, and adaptive network access. These terminals are typically deployed in complex environments such as outdoors, industrial workshops, and remote areas, where wireless communication links are susceptible to electromagnetic interference, obstructions, and signal attenuation, resulting in significant channel quality fluctuations and frequent short-term link interruptions.
[0003] Current traditional IoT terminal access and data transmission solutions have significant technical shortcomings: when a communication link is temporarily interrupted, the terminal must re-complete the entire access authentication process, including identity registration, certificate authentication, key negotiation, and session establishment, when reconnecting to the network. This authentication process is cumbersome and time-consuming. In scenarios with frequent intermittent transmissions, repeated full-process authentication consumes a significant amount of network bandwidth and platform computing resources, leading to problems such as high latency during data transmission interruption and restart, data packet loss, and discontinuous transmission. This severely impacts the high-frequency, real-time, and continuous data acquisition and transmission requirements of converged IoT terminals. Summary of the Invention
[0004] The purpose of this invention is to provide a method for accessing and transmitting data in a converged IoT terminal to solve the problems mentioned in the background art.
[0005] To achieve the above objectives, the present invention provides the following technical solution: a method for accessing and transmitting data from a converged IoT terminal, comprising the following steps:
[0006] S1. Terminal Initial Access: The sensor-connected IoT terminal completes the initial network registration, completes the full-process access authentication, key negotiation, and session link establishment with the cloud IoT platform, builds the initial communication link between the terminal and the platform, and simultaneously completes the two-way binding of terminal identity information, session key, and service transmission parameters.
[0007] S2. Real-time channel quality perception and assessment: The terminal and the IoT platform work together to collect channel status parameters of the communication link in real time. The channel status parameters include signal-to-noise ratio, link packet loss rate, transmission delay, delay jitter amplitude and link connectivity status. The real-time channel status is dynamically rated by a preset channel quality grading model to predict the risk of link degradation and interruption.
[0008] S3. Dynamic transmission context caching: When the channel quality rating is lower than the preset stability threshold, instantaneous fluctuations in the link are detected, or the link is completely interrupted, the terminal and the IoT platform synchronously perform a transmission context saving operation. The transmission context includes the terminal's unique identity identifier, valid authentication credentials, currently valid session key, session identifier, sequence number of transmitted data frames, queue of remaining data to be transmitted, and service transmission configuration parameters.
[0009] S4. Continuous Link Status Monitoring: The terminal interacts with the IoT platform in real time to continuously monitor the recovery status of the communication link. Once the link signal strength is detected to be up to standard and the channel parameters return to the normal range, it is determined that the link has recovered to a communicable state.
[0010] S5, No Full-Process Re-authentication and Resume Transmission: After the link is restored, the IoT platform directly retrieves the locally stored terminal transmission context, skipping the full-process access authentication steps of terminal identity verification, certificate verification, key negotiation, and session reconstruction. Based on the historical transmission context, it quickly activates the communication session and resumes the remaining data transmission from the last interrupted data frame position, achieving seamless resume transmission.
[0011] As a preferred embodiment of the present invention, the method for constructing the channel quality classification model in step S2 includes:
[0012] Historical channel data of IoT terminal communication links are collected in multiple scenarios. With signal-to-noise ratio, packet loss rate, and latency jitter as the core evaluation indicators, four quality levels are divided: high-quality channel, stable channel, degraded channel, and link interruption. The parameter threshold range corresponding to each level is set, and the collected channel parameters are substituted into the model in real time to complete the dynamic rating. When the channel parameters are lower than the stable threshold for N consecutive monitoring periods (N≥3), a link anomaly warning command is triggered.
[0013] As a preferred embodiment of the present invention, the transmission context in step S3 employs a lightweight encryption caching mechanism:
[0014] The transmission context data is subjected to lightweight AES encryption to remove redundant log data and retain only the core sessions and transmission parameters, which are stored in the local secure cache of the terminal and the edge cache node of the IoT platform, respectively. At the same time, a unique timestamp and terminal device fingerprint are bound to each transmission context to prevent context data from being tampered with, lost or illegally reused. The default retention time of cached data is the preset session validity period, and it is automatically cleared after expiration.
[0015] As a preferred embodiment of the present invention, the specific process for quickly activating the communication session in step S5 includes:
[0016] After the link is restored, the terminal sends a resume request to the platform, carrying the device fingerprint and historical session identifier. After receiving the request, the platform matches the corresponding transmission context cached locally, verifies the legality of the device fingerprint and session identifier, and directly reuses the original session key and communication link parameters without re-authentication. The platform also compares the historical data transmission frame sequence numbers of the terminal and the platform to locate the data interruption node and start the breakpoint resume task.
[0017] The sensing and communication convergence IoT terminal access and data transmission system based on channel quality awareness includes a terminal sensing cache module, a platform management and control module, a channel monitoring module, and a data retransmission module. The channel monitoring module and the terminal sensing cache module are deployed on the sensing and communication convergence IoT terminal side, while the platform management and control module and the data retransmission module are deployed on the cloud IoT platform side. The modules are interconnected and work together to form a closed-loop working system of channel awareness, context caching, link verification, and breakpoint retransmission.
[0018] The channel monitoring module is used to collect communication link channel parameters in real time, complete dynamic channel quality rating and link interruption prediction. The channel monitoring module establishes bidirectional data connection with the terminal perception cache module and the platform management module respectively, and pushes the real-time channel quality rating results and link anomaly warning signals to the terminal perception cache module and the platform management module in a synchronous manner, providing core data basis for context cache triggering and link status determination.
[0019] The terminal perception cache module is connected to the channel monitoring module. After receiving the link anomaly warning instruction, it completes the lightweight encryption cache of the terminal side transmission context. At the same time, it continuously monitors the link recovery status. After the link is restored, it sends a breakpoint resume request carrying the device fingerprint and historical session identifier to the platform management module, realizing the functions of terminal side status perception, data caching and request interaction.
[0020] The platform management module is connected to the channel monitoring module, the terminal perception cache module and the data continuation module respectively. It is used to synchronously store the transmission context data of the platform side, receive the terminal continuation request and complete the device fingerprint and session identifier legality verification. After the verification is passed, it skips the full process access authentication, activates the historical communication session, and sends the breakpoint continuation start command to the data continuation module. It synchronously transmits core context parameters such as historical transmission progress and data frame sequence number.
[0021] The data continuation module is connected to the platform management module. After receiving the continuation start command and transmission context data, it accurately matches the data transmission breakpoint and continues to complete the transmission, verification and retransmission of the remaining sensor fusion data. At the same time, it sends the continuation completion status and the latest transmission progress back to the platform management module, which then updates the transmission context cached on both sides synchronously to complete the single breakpoint continuation closed-loop process.
[0022] Compared with the prior art, the beneficial effects of the present invention are:
[0023] 1. This invention innovatively introduces a channel quality awareness and prediction mechanism, which can identify link degradation trends in advance and complete transmission context caching before the link is completely interrupted, avoiding the loss of context data caused by sudden link interruption and ensuring that the data at the breakpoint is traceable and can be resumed.
[0024] 2. This invention designs a bidirectional lightweight caching architecture for transmission context. The terminal and platform synchronously store encrypted core session and transmission data, eliminating redundant information and balancing caching efficiency and communication security. At the same time, it uses device fingerprints and timestamps to prevent counterfeiting and tampering, ensuring access and transmission security.
[0025] 3. The core breakthrough of this invention lies in the elimination of full-process access authentication after link recovery, which completely eliminates the cumbersome process of identity verification, certificate verification, key negotiation and session reconstruction in traditional solutions, greatly shortens the reconnection recovery latency, and reduces the computing power consumption and network resource occupation of terminals and platforms. Attached Figure Description
[0026] Figure 1 This is a schematic diagram of the structure of the sensing-fusion IoT terminal access and data transmission method of the present invention;
[0027] Figure 2 This is a framework diagram of the sensing and communication fusion IoT terminal access and data transmission system based on channel quality awareness of the present invention. Detailed Implementation
[0028] The technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings of the embodiments of the present invention. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments.
[0029] In the description of this invention, it should be noted that the terms "upper," "lower," "inner," "outer," "front end," "rear end," "both ends," "one end," and "the other end," etc., indicate the orientation or positional relationship based on the orientation or positional relationship shown in the accompanying drawings. They are used only for the convenience of describing this invention and for simplifying the description, and do not indicate or imply that the device or element referred to must have a specific orientation, or be constructed and operated in a specific orientation. Therefore, they should not be construed as limitations on this invention. Furthermore, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance.
[0030] In the description of this invention, it should be noted that, unless otherwise explicitly specified and limited, the terms "installed," "equipped with," "connected," etc., should be interpreted broadly. For example, "connection" can be a fixed connection, a detachable connection, or an integral connection; it can be a mechanical connection or an electrical connection; it can be a direct connection or an indirect connection through an intermediate medium; it can be a connection within two components. Those skilled in the art can understand the specific meaning of the above terms in this invention based on the specific circumstances.
[0031] Please see Figure 1-2 The present invention provides an embodiment of a converged IoT terminal access and data transmission method. This invention discloses a converged IoT terminal access and data transmission method and system based on channel quality awareness. The core aim is to solve the problems of high data transmission latency, low transmission efficiency, and significant resource consumption caused by the need to re-execute the full-process authentication and session reconstruction after channel fluctuations and link interruptions in traditional converged IoT terminals under complex communication scenarios. Through real-time channel quality awareness, lightweight encrypted caching of transmission context, and a mechanism for resuming transmission without full-process re-authentication breakpoints, the invention achieves continuity, stability, and efficiency in IoT terminal data transmission. It is applicable to converged data transmission scenarios in various scenarios such as industrial IoT, smart security, and smart buildings.
[0032] S1. The specific process for terminal initialization and access is as follows: When the converged IoT terminal powers on for the first time or restarts to access the network, it initiates the initial network access registration process, actively sending a network access registration request message to the cloud IoT platform. The message carries basic information such as the terminal's factory-fixed unique identifier, device model, and access protocol version. After receiving the registration request, the cloud IoT platform performs an initial compliance verification of the terminal's basic identity information. After confirming that the terminal is an authorized access device, it initiates the two-way key negotiation process.
[0033] In this embodiment, key negotiation employs a hybrid encryption mechanism combining asymmetric and symmetric encryption. The terminal and the cloud-based IoT platform use a preset encryption algorithm to generate and synchronously distribute the session key bidirectionally, ensuring that the key is only valid on both the terminal and the platform, thus eliminating the risk of key leakage. After key negotiation is completed, a dedicated encrypted session link is established on both sides, completing the initial setup of the communication link.
[0034] After the session link is established, the terminal and the cloud IoT platform perform a two-way parameter binding operation. The terminal synchronously reports its own identity information, hardware parameters, service transmission baud rate, data frame format, transmission heartbeat cycle and other service transmission parameters to the platform. The cloud IoT platform sends core parameters such as platform-side communication configuration, permission parameters and session validity period to the terminal. Finally, the two-way binding of terminal identity information, session key and service transmission parameters is realized, and the initial full-process access of the terminal is completed, providing a legal and stable basic communication link support for subsequent data transmission.
[0035] S2. Real-time channel quality perception and assessment is based on a preset channel quality classification model. It can monitor the operating status of the communication link in real time and predict the risk of link anomalies. The specific implementation process is as follows:
[0036] First, a channel quality classification model was constructed. During the model construction phase, historical communication channel data of IoT terminals in various typical application scenarios, such as industrial scenarios, outdoor scenarios, and indoor complex interference scenarios, were collected in batches. After removing abnormal interference data, four core evaluation indicators were selected: signal-to-noise ratio, link packet loss rate, transmission delay, and delay jitter amplitude. The communication link quality was then divided into four levels: excellent channel, stable channel, degraded channel, and link interruption.
[0037] In this embodiment, the parameter threshold ranges corresponding to each channel level are specifically set as follows: (1) High-quality channel: signal-to-noise ratio ≥ 35dB, link packet loss rate ≤ 0.5%, transmission delay ≤ 20ms, delay jitter amplitude ≤ 5ms; (2) Stable channel: 20dB ≤ signal-to-noise ratio < 35dB, 0.5% < link packet loss rate ≤ 2%, 20ms < transmission delay ≤ 50ms, 5ms < delay jitter amplitude ≤ 10ms; (3) Degraded channel: 10dB ≤ signal-to-noise ratio < 20dB, 2% < link packet loss rate ≤ 8%, 50ms < transmission delay ≤ 100ms, 10ms < delay jitter amplitude ≤ 20ms; (4) Link interruption: signal-to-noise ratio < 10dB, link packet loss rate > 8%, transmission delay > 100ms, delay jitter amplitude > 20ms or no data interaction on the link. At the same time, the channel stability threshold is set as the lower limit parameter of the channel stability level, and the preset monitoring period is 1 second. When the channel parameter is lower than the stability threshold for 3 or more consecutive monitoring periods, a link anomaly warning command is immediately triggered.
[0038] After the model is built, the terminal and the cloud IoT platform collaboratively initiate real-time channel parameter acquisition. The terminal acquires downlink channel parameters in real time, while the platform acquires uplink channel parameters in real time. Both sides synchronize the acquisition data every 1 second, integrating it to obtain complete bidirectional link channel status data. The real-time acquired signal-to-noise ratio, link packet loss rate, transmission delay, and delay jitter amplitude parameters are substituted into the channel quality grading model to complete dynamic quality rating. If the channel quality rating is detected to be lower than the stable threshold for N consecutive (N≥3) monitoring periods, a link degradation warning signal is immediately generated and simultaneously pushed to the cache control modules of the terminal and the platform, providing a trigger basis for subsequent transmission context caching.
[0039] S3. When the channel quality rating is lower than the preset stability threshold, instantaneous link fluctuations are detected, or the link is completely interrupted, the terminal and the IoT platform simultaneously perform a transmission context saving operation. This invention uses a lightweight encrypted caching mechanism to complete the context storage. The specific implementation process is as follows:
[0040] First, determine the core data content to be cached, accurately filter the core transmission context data, and remove redundant data such as redundant device operation logs, invalid interaction messages, and expired parameters. Only retain seven core data: the terminal's unique identity identifier, valid authentication credentials, the current valid session key, session identifier, the sequence number of transmitted data frames, the remaining data queue to be transmitted, and the service transmission configuration parameters. This minimizes the size of the cached data and achieves lightweight caching.
[0041] Secondly, lightweight encryption is performed, using the AES-128 lightweight encryption algorithm to encrypt the filtered transmission context data. This algorithm boasts high encryption efficiency and low computational consumption, adapting to the low-computing-power and low-storage hardware characteristics of IoT terminals. It can complete rapid encryption without affecting the normal operation of the terminal. After encryption, dual-sided distributed storage is implemented. On the terminal side, the encrypted transmission context is stored in a local dedicated secure cache with hardware-level access permissions set to prevent unauthorized external reading and tampering. The cloud-based IoT platform stores the corresponding context data on edge cache nodes, rather than the core business database, improving the response speed for subsequent data retrieval.
[0042] Simultaneously, a unique timestamp and terminal device fingerprint are bound to the transmission context of each cache group. The device fingerprint is generated by encrypting the terminal hardware MAC address and the device's unique code, ensuring uniqueness and non-copyability. The timestamp provides precise timing data for the cache operation, used to verify the timeliness and legality of the context data, thoroughly preventing context data tampering, loss, and unauthorized reuse. In this embodiment, the default retention period for cached data is set to be consistent with the current session's validity period. After the session expires, the corresponding context data in the terminal's local cache and the platform's edge node cache is automatically cleared to release storage space, avoiding cached data accumulation and resource consumption.
[0043] S4. Continuous monitoring of link status is achieved through a two-sided real-time heartbeat interaction mechanism. The specific implementation method is as follows: After the link deteriorates, fluctuates or is interrupted, the terminal and the cloud IoT platform continuously maintain a heartbeat interaction mechanism. The default heartbeat sending cycle is 2 seconds. The terminal sends heartbeat detection messages to the platform at regular intervals. After receiving the messages, the platform returns response messages to monitor the connectivity and signal quality of the communication link in real time.
[0044] During monitoring, link signal strength and channel parameters are collected in real time. The real-time data is compared with preset normal range parameters. When the link signal strength is detected to be up to standard, and the signal-to-noise ratio, packet loss rate, transmission delay, and delay jitter amplitude all return to the channel stability level or above, the link is determined to have recovered and is ready for normal communication. The link anomaly warning is immediately terminated, and a resume preparation command is triggered simultaneously to provide state support for subsequent no-re-authentication breakpoint resume transmission. If the link continues to fail to recover, the cached data is maintained in a valid state, and heartbeat monitoring continues until the link recovers.
[0045] S5. After the link is restored, a resume operation without full-process re-authentication is performed, skipping the entire process of identity verification, certificate verification, key negotiation, and session reconstruction of traditional access. The resume operation is based on the historical transmission context and proceeds quickly. The specific process is as follows:
[0046] Once the link recovery determination is completed, the terminal immediately sends a breakpoint resumption request message to the cloud IoT platform, which carries the unique device fingerprint and historical valid session identifier of the local device. The request message only contains core verification information, has a small message size, and a fast transmission speed, and does not need to carry redundant authentication data.
[0047] After receiving the resume request, the cloud-based IoT platform quickly matches the corresponding terminal transmission context data pre-stored in the local edge cache node based on the device fingerprint and session identifier in the message. It first verifies the uniqueness and legality of the device fingerprint, and then verifies the validity of the historical session identifier to confirm that the requesting terminal is a legitimate authorized device and that the historical session is real and valid.
[0048] After successful verification, the platform directly reuses the existing valid session keys and historical communication link parameters cached on both sides. This eliminates the need to re-execute the entire access authentication process, including certificate issuance, identity verification, key negotiation, and session creation, quickly activating the historical communication session and rapidly restoring the communication link. Subsequently, the platform retrieves the terminal's transmitted data frame sequence numbers from the cache and compares them bi-directionally with the terminal's locally recorded transmission progress. This allows for precise location of the exact frame where data transmission was interrupted, identifying the remaining data queue that was not fully transmitted.
[0049] Finally, based on the interruption node, the breakpoint resume transmission task is started. The terminal and the platform start from the next frame after the interrupted data frame and continue to complete the encrypted transmission, data verification, and missing data supplementation of the remaining sensor fusion data. There is no need to re-enter the network for authentication throughout the process, realizing seamless resume transmission after the link is interrupted, greatly shortening the transmission preparation time after the link is restored, and improving data transmission efficiency.
[0050] The present invention provides a channel quality-aware, converged IoT terminal access and data transmission system to fully implement the aforementioned data transmission method. The system adopts a terminal-cloud dual-side distributed architecture, including a channel monitoring module and a terminal perception caching module deployed on the converged IoT terminal side, and a platform management module and a data continuation module deployed on the cloud IoT platform side. These four modules are interconnected and work together to form a closed-loop working system of "channel awareness - context caching - link verification - breakpoint resumption". The specific functions and linkage methods of each module are as follows:
[0051] Channel monitoring module: This is the core sensing module of the system, with built-in channel parameter acquisition and quality rating calculation units. During operation, it continuously collects channel status parameters such as signal-to-noise ratio, packet loss rate, transmission delay, delay jitter, and link connectivity status of the bidirectional communication link between the terminal and the platform. Through a built-in channel quality rating model, it performs real-time dynamic channel quality rating, accurately predicting link degradation and outage risks. This module establishes a bidirectional data communication link with the terminal sensing cache module and the platform control module, and can synchronously push channel quality rating results and link anomaly warning signals to both control modules in real time, providing accurate data support for context cache triggering, link recovery status determination, and resuming transmission command issuance.
[0052] Terminal-Aware Caching Module: This is a core functional module on the terminal side. It connects to the channel monitoring module in real time. Upon receiving a link anomaly warning command, it immediately initiates a lightweight encrypted caching process. This process involves filtering the terminal-side transmission context, performing AES lightweight encryption, and securing local storage. It also binds the device fingerprint and timestamp to ensure the security of the cached data. Simultaneously, this module has link status monitoring and request interaction functions. After a link interruption, it continuously monitors the link recovery status using a heartbeat mechanism. Once link recovery is detected, it immediately sends a resume request carrying the device fingerprint and historical session identifier to the cloud platform management module, completing the entire process of terminal-side status response and interaction.
[0053] The platform management module serves as the core management hub of the cloud system, establishing communication connections with the channel monitoring module, terminal perception caching module, and data resumption module. On one hand, it synchronously stores encrypted context data of terminal transmissions on the platform side, and synchronizes terminal link status and channel quality status in real time. On the other hand, it receives breakpoint resumption requests initiated by terminals, retrieves context data from edge caching nodes, and completes the legality verification of device fingerprints and historical session identifiers. Upon successful verification, it automatically skips the full access authentication process, quickly activates historical communication sessions, and simultaneously issues a breakpoint resumption start command to the data resumption module, synchronously pushing core context parameters such as historical data frame sequence numbers, remaining transmission queues, and session keys, thus comprehensively managing the entire resumption process.
[0054] The data resumption module is the data retransmission execution module. It interfaces with the platform management module, receiving resumption start commands and core transmission context data in real time. By comparing transmission progress data from both sides, it accurately locates data transmission breakpoints and automatically generates a resumption task list. Following the original business transmission configuration parameters, it resumes the encrypted transmission of remaining integrated data, performs data integrity verification, and retransmits missing data. After the resumption task is completed, it automatically calculates the resumption status and the latest data transmission progress, and sends the results back to the platform management module. The platform management module then synchronously updates the transmission context data cached on both the terminal and the platform, completing a closed-loop workflow of single-link anomaly-caching-resumption.
[0055] It will be apparent to those skilled in the art that the present invention is not limited to the details of the exemplary embodiments described above, and that the invention can be implemented in other specific forms without departing from its spirit or essential characteristics. Therefore, the embodiments should be considered in all respects as exemplary and non-limiting, and the scope of the invention is defined by the appended claims rather than the foregoing description. Thus, all variations falling within the meaning and scope of equivalents of the claims are intended to be included within the present invention. No reference numerals in the claims should be construed as limiting the scope of the claims.
Claims
1. A method for accessing and transmitting data from a converged IoT terminal, comprising the following steps: S1. Terminal Initial Access: The sensor-connected IoT terminal completes the initial network registration, completes the full-process access authentication, key negotiation, and session link establishment with the cloud IoT platform, builds the initial communication link between the terminal and the platform, and simultaneously completes the two-way binding of terminal identity information, session key, and service transmission parameters. S2. Real-time channel quality perception and assessment: The terminal and the IoT platform work together to collect channel status parameters of the communication link in real time. The channel status parameters include signal-to-noise ratio, link packet loss rate, transmission delay, delay jitter amplitude and link connectivity status. The real-time channel status is dynamically rated by a preset channel quality grading model to predict the risk of link degradation and interruption. S3. Dynamic transmission context caching: When the channel quality rating is lower than the preset stability threshold, instantaneous fluctuations in the link are detected, or the link is completely interrupted, the terminal and the IoT platform synchronously perform a transmission context saving operation. The transmission context includes the terminal's unique identity identifier, valid authentication credentials, currently valid session key, session identifier, sequence number of transmitted data frames, queue of remaining data to be transmitted, and service transmission configuration parameters. S4. Continuous Link Status Monitoring: The terminal interacts with the IoT platform in real time to continuously monitor the recovery status of the communication link. Once the link signal strength is detected to be up to standard and the channel parameters return to the normal range, it is determined that the link has recovered to a communicable state. S5, No Full-Process Re-authentication and Resume Transmission: After the link is restored, the IoT platform directly retrieves the locally stored terminal transmission context, skipping the full-process access authentication steps of terminal identity verification, certificate verification, key negotiation, and session reconstruction. Based on the historical transmission context, it quickly activates the communication session and resumes the remaining data transmission from the last interrupted data frame position, achieving seamless resume transmission.
2. The sensing-integrated IoT terminal access and data transmission method according to claim 1, characterized in that, The method for constructing the channel quality classification model in step S2 includes: Historical channel data of IoT terminal communication links are collected in multiple scenarios. With signal-to-noise ratio, packet loss rate, and latency jitter as the core evaluation indicators, four quality levels are divided: high-quality channel, stable channel, degraded channel, and link interruption. The parameter threshold range corresponding to each level is set, and the collected channel parameters are substituted into the model in real time to complete the dynamic rating. When the channel parameters are lower than the stable threshold for N consecutive monitoring periods (N≥3), a link anomaly warning command is triggered.
3. The sensing-integrated IoT terminal access and data transmission method according to claim 1, characterized in that, The transmission context described in step S3 employs a lightweight encrypted caching mechanism: The transmission context data is subjected to lightweight AES encryption to remove redundant log data and retain only the core sessions and transmission parameters, which are stored in the local secure cache of the terminal and the edge cache node of the IoT platform, respectively. At the same time, a unique timestamp and terminal device fingerprint are bound to each transmission context to prevent context data from being tampered with, lost or illegally reused. The default retention time of cached data is the preset session validity period, and it is automatically cleared after expiration.
4. The sensing-integrated IoT terminal access and data transmission method according to claim 1, characterized in that, The specific process for quickly activating the communication session in step S5 includes: After the link is restored, the terminal sends a resume request to the platform, carrying the device fingerprint and historical session identifier. After receiving the request, the platform matches the corresponding transmission context cached locally, verifies the legality of the device fingerprint and session identifier, and directly reuses the original session key and communication link parameters without re-authentication. The platform also compares the historical data transmission frame sequence numbers of the terminal and the platform to locate the data interruption node and start the breakpoint resume task.
5. A channel quality-aware, converged IoT terminal access and data transmission system, characterized in that, The method for implementing any one of claims 1-5 includes a terminal sensing cache module, a platform management module, a channel monitoring module, and a data retransmission module; the channel monitoring module and the terminal sensing cache module are deployed on the sensing convergence IoT terminal side, and the platform management module and the data retransmission module are deployed on the cloud IoT platform side. The modules are interconnected and work together to form a closed-loop working system of channel sensing-context caching-link verification-breakpoint retransmission. The channel monitoring module is used to collect communication link channel parameters in real time, complete dynamic channel quality rating and link interruption prediction. The channel monitoring module establishes bidirectional data connection with the terminal perception cache module and the platform management module respectively, and pushes the real-time channel quality rating results and link anomaly warning signals to the terminal perception cache module and the platform management module in a synchronous manner, providing core data basis for context cache triggering and link status determination. The terminal perception cache module is connected to the channel monitoring module. After receiving the link anomaly warning instruction, it completes the lightweight encryption cache of the terminal side transmission context. At the same time, it continuously monitors the link recovery status. After the link is restored, it sends a breakpoint resume request carrying the device fingerprint and historical session identifier to the platform management module, realizing the functions of terminal side status perception, data caching and request interaction. The platform management module is connected to the channel monitoring module, the terminal perception cache module and the data continuation module respectively. It is used to synchronously store the transmission context data of the platform side, receive the terminal continuation request and complete the device fingerprint and session identifier legality verification. After the verification is passed, it skips the full process access authentication, activates the historical communication session, and sends the breakpoint continuation start command to the data continuation module. It synchronously transmits core context parameters such as historical transmission progress and data frame sequence number. The data continuation module is connected to the platform management module. After receiving the continuation start command and transmission context data, it accurately matches the data transmission breakpoint and continues to complete the transmission, verification and retransmission of the remaining sensor fusion data. At the same time, it sends the continuation completion status and the latest transmission progress back to the platform management module, which then updates the transmission context cached on both sides synchronously to complete the single breakpoint continuation closed-loop process.
