Wireless communication system in the internet of things

Abstract

The application provides a wireless communication system in an Internet of Things, the system comprising a distributed Internet of Things device, a cloud platform maintaining wireless communication with the Internet of Things device, the Internet of Things device being configured to collect log data of a position acted on by a pre-added burying point in a wireless communication module of the Internet of Things device and upload the log data to the cloud platform; the cloud platform being configured to capture an abnormal event of the wireless communication module according to the log data and respond to the abnormal event. The embodiment of the application can capture the abnormal event of the wireless communication module in time, and then respond in time, thereby avoiding a security problem caused by the abnormal event of the wireless communication module of the Internet of Things device existing for a long time.

Description

Technical Field

[0001] This application relates to the field of the Internet of Things (IoT), specifically to a wireless communication system in the IoT. Background Technology

[0002] In the field of the Internet of Things (IoT), wireless communication technology is a crucial component. The level of intelligence in the IoT largely depends on the extent to which wireless communication technology is applied. However, with the dramatic increase in the number of IoT devices, their wireless communication modules often experience problems after being put into practical use. In related technologies, problems with the wireless communication modules of IoT devices are often difficult to detect, thus hindering the normal operation of the IoT. In some cases, if these problems persist for an extended period, they can even lead to security issues and cause personal injury or property damage. Summary of the Invention

[0003] One objective of this application is to propose a wireless communication system in the Internet of Things (IoT) that can promptly capture abnormal events of the wireless communication module and respond accordingly, thereby avoiding security problems caused by prolonged abnormalities in the wireless communication module of IoT devices.

[0004] According to one aspect of the embodiments of this application, a wireless communication system in the Internet of Things (IoT) is disclosed, the system comprising distributed IoT devices and a cloud platform maintaining wireless communication with the IoT devices.

[0005] The IoT device is configured to: collect log data at the location where the embedded points are located, based on the embedded points pre-added in the wireless communication module of the IoT device, and upload the log data to the cloud platform;

[0006] The cloud platform is configured to: capture abnormal events of the wireless communication module based on the log data, and respond to the abnormal events.

[0007] In some embodiments of this application, the WIFI module in the wireless communication module maintains wireless communication with the cloud platform by establishing a long connection with the cloud platform using a first communication protocol, and uploads the log data to the cloud platform by establishing a short connection with the cloud platform using a second communication protocol.

[0008] In some embodiments of this application, the first communication protocol includes the MQTT protocol or the COAP protocol; the second communication protocol includes the HTTP protocol.

[0009] In some embodiments of this application, the cloud platform is configured to respond to the abnormal event by generating an early warning message for the abnormal event and sending the early warning message to the management terminal of the Internet of Things.

[0010] In some embodiments of this application, the cloud platform is configured to respond to the abnormal event by sending a restart command to the IoT device.

[0011] In some embodiments of this application, the cloud platform is configured to respond to the abnormal event by sending a shutdown command to the IoT device.

[0012] In some embodiments of this application, the IoT device is configured to: collect first log data describing the remaining memory size based on a first embedded point pre-added in the dynamic memory of the wireless communication module, and upload the first log data to the cloud platform;

[0013] The cloud platform is configured to: capture memory anomaly events of the wireless communication module based on the first log data, and respond to the memory anomaly events.

[0014] In some embodiments of this application, the IoT device is configured to: collect second log data describing the thread's call process based on a second embedded point pre-added in the thread of the wireless communication module, and upload the second log data to the cloud platform;

[0015] The cloud platform is configured to: capture thread exception events of the wireless communication module based on the second log data, and respond to the thread exception events.

[0016] In some embodiments of this application, the second embedding point is pre-added to the lowest priority thread of the wireless communication module, and the second log data is used to describe the calling process of the lowest priority thread;

[0017] The cloud platform is configured to: if the second log data is not received for a continuously preset time threshold, capture the thread blocking event of the wireless communication module and respond to the thread blocking event.

[0018] In some embodiments of this application, the IoT device is configured as follows:

[0019] The system maintains a long-term connection with the cloud platform by periodically sending heartbeat packets to the cloud platform via the wireless communication module.

[0020] Based on the second embedded point pre-added in the lowest priority thread of the wireless communication module, the call signal of the lowest priority thread is collected, and after the call signal is collected, a preset flag bit is added to the next heartbeat packet;

[0021] The cloud platform is configured to: if it continuously receives a preset number of heartbeat packets without the flag bit, it will capture the thread blocking event of the wireless communication module and respond to the thread blocking event.

[0022] The wireless communication system in the Internet of Things provided in this application embodiment, by pre-adding embedded points to the wireless communication module of the Internet of Things device, enables the cloud platform to promptly capture abnormal events of the wireless communication module based on the log data of the location where the embedded points are located, and thus respond in a timely manner, avoiding security problems caused by the long-term existence of abnormalities in the wireless communication module of the Internet of Things device.

[0023] Other features and advantages of this application will become apparent from the following detailed description, or may be learned in part from practice of this application.

[0024] It should be understood that the above general description and the following detailed description are merely exemplary and do not limit this application. Attached Figure Description

[0025] The above and other objectives, features and advantages of this application will become more apparent from a detailed description of exemplary embodiments thereof with reference to the accompanying drawings.

[0026] Figure 1 A schematic diagram illustrating the architectural composition of a wireless communication system in the Internet of Things according to some embodiments of this application is shown.

[0027] Figure 2 A schematic diagram illustrating the architectural composition of a wireless communication system in the Internet of Things according to some embodiments of this application is shown.

[0028] Figure 3 A schematic diagram illustrating the architectural composition of a wireless communication system in the Internet of Things according to some embodiments of this application is shown.

[0029] Figure 4 A schematic diagram illustrating the interaction flow between terminals in an Internet of Things (IoT) according to some embodiments of this application is shown.

[0030] Figure 5 A schematic diagram illustrating the communication between the WIFI module of an IoT device and a cloud platform, according to some embodiments of this application, is shown.

[0031] Figure 6 A schematic diagram illustrating the communication between the WIFI module of an IoT device and a cloud platform, according to some embodiments of this application, is shown. Detailed Implementation

[0032] Exemplary embodiments will now be described more fully with reference to the accompanying drawings. However, these exemplary embodiments can be implemented in many forms and should not be construed as limited to the examples set forth herein; rather, they are provided to make the description of this application more comprehensive and complete, and to fully convey the concept of the exemplary embodiments to those skilled in the art. The drawings are merely illustrative of this application and are not necessarily drawn to scale. The same reference numerals in the drawings denote the same or similar parts, and therefore repeated descriptions of them will be omitted.

[0033] Furthermore, the described features, structures, or characteristics can be combined in any suitable manner in one or more exemplary embodiments. Numerous specific details are provided in the following description to give a full understanding of exemplary embodiments of this application. However, those skilled in the art will recognize that the technical solutions of this application can be practiced with one or more of the specific details omitted, or other methods, components, steps, etc., can be employed. In other instances, well-known structures, methods, implementations, or operations are not shown or described in detail to avoid obscuring various aspects of this application.

[0034] Some of the block diagrams shown in the accompanying drawings are functional entities and do not necessarily correspond to physically or logically independent entities. These functional entities can be implemented in software, in one or more hardware modules or integrated circuits, or in different network and / or processor devices and / or microcontroller devices.

[0035] Figure 1 A schematic diagram illustrating the architectural composition of a wireless communication system in the Internet of Things (IoT) according to some embodiments of this application is shown.

[0036] refer to Figure 1 As shown in some embodiments of this application, the wireless communication system in the Internet of Things (IoT) mainly consists of two parts: distributed IoT devices and a cloud platform that maintains wireless communication with the IoT devices. The IoT devices are physically distributed and interconnected to a certain extent under the unified management of the cloud platform.

[0037] In this embodiment, the IoT device is configured to: collect log data at the locations where the embedded points are located, based on pre-added embedded points in the IoT device's wireless communication module, and upload the log data to the cloud platform. The cloud platform is configured to: capture abnormal events of the wireless communication module based on the log data and respond to the abnormal events.

[0038] Specifically, before IoT devices leave the factory, low-level code for data tracking is written into the wireless communication module of the IoT device, thereby adding data tracking points to the wireless communication module. The location of the data tracking points is set according to the application requirements of the IoT.

[0039] After IoT devices are put into use, they automatically collect log data at the locations where the embedded points in their wireless communication modules operate, and upload the log data to the cloud platform. The cloud platform then parses the log data received from the IoT devices to detect abnormal events in the wireless communication modules of the IoT devices and responds to these abnormal events.

[0040] Therefore, the wireless communication system in the Internet of Things provided in this application embodiment, by pre-adding embedded points to the wireless communication module of the Internet of Things device, enables the cloud platform to promptly capture abnormal events of the wireless communication module based on the log data of the location where the embedded points are located, and thus respond in a timely manner, avoiding security problems caused by the long-term existence of abnormalities in the wireless communication module of the Internet of Things device.

[0041] In some embodiments, distributed IoT devices include: televisions, refrigerators, air conditioners, washing machines, lamps, smart door locks, etc.

[0042] In some embodiments, the cloud platform is configured to respond to the abnormal event by generating an early warning message for the abnormal event and sending the early warning message to the management terminal of the Internet of Things.

[0043] In this embodiment, the Internet of Things (IoT) also includes a management terminal, which typically has higher control authority over IoT devices. After capturing abnormal events from the log data of the IoT devices, the cloud platform generates an early warning message and sends it to the IoT management terminal. In this way, when the wireless communication module of an IoT device malfunctions, the cloud platform promptly alerts the management terminal, enabling the management terminal to take appropriate control measures and respond to the abnormal event in a timely manner.

[0044] Figure 2 A schematic diagram illustrating the architectural composition of a wireless communication system in the Internet of Things (IoT) according to some embodiments of this application is shown.

[0045] refer to Figure 2 As shown in some embodiments of this application, the cloud platform in the Internet of Things (IoT) also establishes communication with the IoT management terminal. Specifically, after the cloud platform captures an abnormal event from the log data of the IoT device, it sends an alarm message to the management terminal to notify the management terminal that the IoT device has malfunctioned.

[0046] If the management terminal is used by IoT maintenance personnel, the cloud platform can send the log data and alarm information to the maintenance personnel's terminal so that they can further analyze the log data and take timely maintenance measures for IoT devices with abnormal wireless communication modules.

[0047] If the management terminal is the terminal used by the service user of the IoT device, the cloud platform can send alarm information to the terminal used by the service user to remind the service user to shut down or restart the IoT device, so that the service user can respond in a timely manner to IoT devices with abnormal wireless communication modules and avoid security problems.

[0048] In some embodiments, the cloud platform is configured to respond to abnormal events by sending a restart command to the IoT device.

[0049] In this embodiment, after the cloud platform captures an abnormal event from the log data of the IoT device, it sends a restart command to the IoT device, causing the IoT device to restart upon receiving the restart command. The restarted IoT device will, to a certain extent, eliminate the abnormal event. In this way, the cloud platform can respond promptly to abnormal events when the wireless communication module of the IoT device malfunctions, reducing the adverse effects of such events.

[0050] In some embodiments, the cloud platform is configured to respond to abnormal events by sending a shutdown command to the IoT device.

[0051] In this embodiment, after the cloud platform captures an abnormal event from the log data of the IoT device, it sends a shutdown command to the IoT device, causing the IoT device to shut down upon receiving the command. The shutdown of the IoT device at least does not pose a security risk. In this way, the cloud platform responds promptly to abnormal events when the wireless communication module of the IoT device malfunctions, preventing security issues from occurring.

[0052] In some embodiments, the wireless communication module where the embedded point is located is the WIFI module of the IoT device.

[0053] In this embodiment, the IoT device maintains wireless communication with the cloud platform through the WIFI module, and can also form a network with other IoT devices in nearby physical locations through the WIFI module to directly establish wireless communication with other IoT devices and realize direct interoperability of some information.

[0054] By pre-installing data points on the Wi-Fi module of IoT devices, the IoT devices upload log data from the locations where these data points are located to the cloud platform. This enables the cloud platform to capture abnormal events in the Wi-Fi module of the IoT devices and respond accordingly.

[0055] Figure 3 A schematic diagram illustrating the architectural composition of a wireless communication system in the Internet of Things (IoT) according to some embodiments of this application is shown.

[0056] refer to Figure 3 As shown, in some embodiments of this application, the wireless communication module where the embedded point is located is the WIFI module and Bluetooth module of the IoT device.

[0057] In this embodiment, the wireless communication module in the IoT device includes a Wi-Fi module and a Bluetooth module. The Wi-Fi module is mainly used to maintain wireless communication with the cloud platform, acting as a gateway. The Bluetooth module is mainly used to network with other IoT devices in nearby physical locations, forming a Bluetooth mesh network. IoT devices in the same Bluetooth mesh network can directly establish wireless communication with other IoT devices through the Bluetooth module, enabling direct exchange of some information.

[0058] By pre-installing tracking points on the Wi-Fi and Bluetooth modules of IoT devices, the devices upload log data from these points to a cloud platform. This allows the cloud platform to capture and respond to abnormal events in both the Wi-Fi and Bluetooth modules. Based on this, the cloud platform can first generate warning messages that differentiate between the Wi-Fi and Bluetooth modules, and then send these warnings to the management terminal. This enables maintenance personnel or service users at the management terminal to not only determine whether the problem lies with the IoT device's wireless communication module, but also to accurately pinpoint whether the problem is caused by the Wi-Fi or Bluetooth module.

[0059] In some embodiments, the WIFI module in the wireless communication module maintains wireless communication with the cloud platform by establishing a long connection with the cloud platform using a first communication protocol, and uploads the log data to the cloud platform by establishing a short connection with the cloud platform using a second communication protocol.

[0060] In this embodiment, the WIFI module in the wireless communication module uses two communication protocols to communicate with the cloud platform. Specifically, the WIFI module in the IoT device continuously uses the first communication protocol to establish a long connection with the cloud platform, thereby maintaining continuous wireless communication with the cloud platform; and when it is necessary to upload log data of the location where the embedded point is located to the cloud platform, it uses the second communication protocol to establish a short connection with the cloud platform, uploads the log data to the cloud platform during the short connection period, and disconnects the short connection with the cloud platform after the log data transmission is completed.

[0061] The advantage of this embodiment is that by using two communication protocols to establish long and short connections with the cloud platform respectively, the communication process of the data entry point is separated from the conventional communication process.

[0062] In some embodiments, the first communication protocol includes the MQTT protocol or the COAP protocol; the second communication protocol includes the HTTP protocol.

[0063] In this embodiment, the WIFI module in the wireless communication module establishes a long connection with the cloud platform using IoT communication protocols such as MQTT (Message Queuing Telemetry Transport) or COAP (The Constrained Application Protocol); and establishes a short TCP (Transmission Control Protocol) connection with the cloud platform using HTTP (Hypertext Transfer Protocol).

[0064] Figure 4 The diagram illustrates the interaction flow between terminals in an Internet of Things (IoT) according to some embodiments of this application.

[0065] refer to Figure 4 As shown, in some embodiments, the distributed IoT devices in the Internet of Things (IoT) are smart home devices (e.g., televisions, washing machines, air conditioners, etc.) located in the home environment, and the management terminal of the IoT is the mobile phone of the user served by the smart home devices.

[0066] In this embodiment, after the smart home device performs a series of initialization operations such as registering, requesting encryption, and requesting system parameters with the cloud platform through the WIFI module, the smart home device authenticated by the cloud platform reports its device status to the cloud platform through the WIFI module. Then, the cloud platform pushes the device status to the user's mobile phone, so that the user can view the device status of the smart home device through the mobile phone.

[0067] Smart home devices establish a persistent connection with the cloud platform via a Wi-Fi module and a heartbeat mechanism, using either the MQTT or COAP protocol. A heartbeat is a pre-agreed command field sent at regular intervals between the communicating parties. If a heartbeat is not received within this interval, it indicates that the other party has gone offline.

[0068] With the log tracking mechanism in place, the Wi-Fi module establishes a short TCP connection with the cloud platform using the HTTP protocol and reports the log data collected by the tracking points to the cloud platform. Therefore, when an anomaly occurs at a tracking point in the Wi-Fi module, the cloud platform can capture the corresponding abnormal event by parsing the log data, generate an alert, and push the alert to the user's mobile phone to notify the user that the smart home device has malfunctioned and requires handling.

[0069] Furthermore, when the WIFI module itself malfunctions and is about to crash, the WIFI module will send a will message to the cloud platform via the HTTP protocol to notify the cloud platform that the WIFI module is about to crash, and the cloud platform will parse the will message to respond to the WIFI module crash event.

[0070] Figure 5 This paper illustrates a communication diagram showing the establishment of a long-term connection between the WIFI module of an IoT device and a cloud platform according to some embodiments of this application.

[0071] refer to Figure 5 As shown in this embodiment, the Wi-Fi module of the IoT device sends a synchronization sequence number to the cloud platform and enters the sending state, waiting for confirmation from the cloud platform. After receiving the synchronization sequence number, the cloud platform confirms it and also sends a number and confirmation identifier to the Wi-Fi module, then enters the receiving state. After receiving the number and confirmation identifier sent by the cloud platform, the Wi-Fi module also sends a confirmation identifier to the cloud platform. The three-way handshake is completed, and the Wi-Fi module successfully connects to the cloud platform; then, combined with the heartbeat mechanism, the Wi-Fi module and the cloud platform establish a long-term connection.

[0072] Figure 6 This paper illustrates a communication diagram showing the establishment of a short connection between the WIFI module of an IoT device and a cloud platform according to some embodiments of this application.

[0073] refer to Figure 6 As shown, in this embodiment, the Wi-Fi module of the IoT device initiates a three-way handshake with the cloud platform using the HTTP protocol. After the three-way handshake is successful, the Wi-Fi module transmits the log data collected by the embedded points to the cloud platform. After the log data transmission is complete, the Wi-Fi module sends a message with an end marker to the cloud platform; upon receiving this message, the cloud platform sends an acknowledgment number to the Wi-Fi module and simultaneously notifies its application that the Wi-Fi module requests to terminate the communication; the cloud platform then sends another message with an end marker to the Wi-Fi module; upon receiving this message, the Wi-Fi module sends an acknowledgment number to the cloud platform. With the four-way handshake completed, the Wi-Fi module and the cloud platform terminate communication, disconnecting the short connection.

[0074] In some embodiments, the IoT device is configured to: collect first log data describing the remaining memory size based on first embedded points pre-added in the dynamic memory of the wireless communication module, and upload the first log data to a cloud platform. The cloud platform is configured to: capture memory anomaly events of the wireless communication module based on the first log data, and respond to the memory anomaly events.

[0075] In this embodiment, a first embedded point is pre-added to the wireless communication module of the IoT device. The location of the first embedded point is the dynamic memory of the wireless communication module. As the dynamic memory of the wireless communication module is used, the remaining memory size of the wireless communication module will also change accordingly. The first embedded point can collect first log data describing the remaining memory size of the wireless communication module. Therefore, through this first log data, the cloud platform can monitor the remaining memory size of the wireless communication module in real time, and then capture and respond to memory anomaly events of the wireless communication module. For example, if the remaining memory size of the wireless communication module decreases rapidly within a certain period of time at a rate greater than a preset threshold, it indicates that a memory leak event has occurred in the wireless communication module, and the memory leak event can be captured and responded to.

[0076] In some embodiments, the IoT device is configured to: collect second log data describing the thread's call process based on second embedded points pre-added in the thread of the wireless communication module, and upload the second log data to a cloud platform. The cloud platform is configured to: capture thread exception events of the wireless communication module based on the second log data, and respond to the thread exception events.

[0077] In this embodiment, a second data entry point is pre-added within the wireless communication module of the IoT device. This second data entry point operates on the thread of the wireless communication module. As the thread of the wireless communication module is invoked, second log data describing the invocation process of the thread can be collected through the second data entry point. Therefore, using this second log data, the cloud platform can monitor the invocation process of the thread of the wireless communication module in real time, and further capture and respond to abnormal events in the thread of the wireless communication module.

[0078] In some embodiments, the second data point is pre-added to the lowest priority thread of the wireless communication module, and the second log data is used to describe the calling process of the lowest priority thread. The cloud platform is configured to: if the second log data is not received for a preset time threshold, capture the thread blocking event of the wireless communication module and respond to the thread blocking event.

[0079] In this embodiment, the second tracking point is added to the lowest priority thread of the wireless communication module. Through the second log data collected by this second tracking point, the cloud platform can monitor the call process of the lowest priority thread of the wireless communication module in real time. If the cloud platform does not receive the second log data within a preset time threshold, it indicates that the wireless communication module has not called the lowest priority thread within that time threshold. This means that some non-lowest priority threads of the wireless communication module are stuck or trapped in an infinite loop within that time threshold, indicating that thread blocking has occurred in the wireless communication module. Based on this, the cloud platform captures the thread blocking event of the wireless communication module and responds to the captured thread blocking event.

[0080] In some embodiments, the IoT device is configured to: maintain a long-term connection with the cloud platform by periodically sending heartbeat packets to the cloud platform via the wireless communication module; collect the call signal of the lowest priority thread based on a second embedded point pre-added in the lowest priority thread of the wireless communication module, and add a preset flag bit to the next heartbeat packet after collecting the call signal. The cloud platform is configured to: if it receives a preset number of heartbeat packets without the added flag bit consecutively, capture the thread blocking event of the wireless communication module and respond to the thread blocking event.

[0081] In this embodiment, thread blocking events are captured and responded to by reusing heartbeat packets based on the data entry points.

[0082] Specifically, the wireless communication module of the IoT device periodically sends heartbeat packets to the cloud platform to maintain a persistent connection. Furthermore, a second tracking point is added to the lowest priority thread of this wireless communication module. Each time this lowest priority thread is invoked, the wireless communication module can collect a call signal through this second tracking point; and each time the wireless communication module collects a call signal, it adds a preset flag to the next heartbeat packet to be sent to the cloud platform. Thus, each time the cloud platform receives a heartbeat packet with the added flag, it can determine that the lowest priority thread was invoked by the wireless communication module between this heartbeat packet and the previous heartbeat packet.

[0083] If the cloud platform receives a preset number of heartbeat packets without added flags, it indicates that the lowest priority thread has not been called by the wireless communication module during that preset number of heartbeat packets. This means that some non-lowest priority threads of the wireless communication module are stuck or trapped in an infinite loop during that preset number of heartbeat packets, resulting in thread blocking in the wireless communication module. Based on this, the cloud platform captures the thread blocking event of the wireless communication module and responds to the captured thread blocking event.

[0084] The advantage of this embodiment is that by reusing heartbeat packets on the basis of data entry points to capture and respond to thread blocking events, it ensures timely response to thread blocking events of the wireless communication module while reducing the signaling cost of communication between IoT devices and the cloud platform.

[0085] Other embodiments of this application will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of this application that follow the general principles of this application and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of this application are indicated by the appended claims.

Claims

1. A wireless communication system for the Internet of Things, characterized in that, The system includes distributed Internet of Things (IoT) devices and a cloud platform that maintains wireless communication with the IoT devices. The IoT device is configured to: collect log data at the location where the embedded points are located, based on the embedded points pre-added in the wireless communication module of the IoT device, and upload the log data to the cloud platform; The system maintains a long-term connection with the cloud platform by periodically sending heartbeat packets to the cloud platform via the wireless communication module. Based on the second embedded point pre-added in the lowest priority thread of the wireless communication module, the call signal of the lowest priority thread is collected, and after the call signal is collected, a preset flag bit is added to the next heartbeat packet; The cloud platform is configured to: capture abnormal events of the wireless communication module based on the log data, and respond to the abnormal events; If a preset number of heartbeat packets without the flag bit are received consecutively, the thread blocking event of the wireless communication module is captured, and the thread blocking event is responded to.

2. The system according to claim 1, characterized in that, The WIFI module in the wireless communication module maintains wireless communication with the cloud platform by establishing a long connection using a first communication protocol, and uploads the log data to the cloud platform by establishing a short connection using a second communication protocol.

3. The system according to claim 2, characterized in that, The first communication protocol includes the MQTT protocol or the COAP protocol; the second communication protocol includes the HTTP protocol.

4. The system according to claim 1, characterized in that, The cloud platform is configured to respond to the abnormal event by generating an early warning message for the abnormal event and sending the early warning message to the management terminal of the Internet of Things.

5. The system according to claim 1, characterized in that, The cloud platform is configured to respond to the abnormal event by sending a restart command to the IoT device.

6. The system according to claim 1, characterized in that, The cloud platform is configured to respond to the abnormal event by sending a shutdown command to the IoT device.

7. The system according to claim 1, characterized in that, The IoT device is configured to: collect first log data describing the remaining memory size based on a first embedded point pre-added in the dynamic memory of the wireless communication module, and upload the first log data to the cloud platform; The cloud platform is configured to: capture memory anomaly events of the wireless communication module based on the first log data, and respond to the memory anomaly events.

8. The system according to claim 1, characterized in that, The IoT device is configured to: collect second log data describing the thread's call process based on a second embedded point pre-added in the thread of the wireless communication module, and upload the second log data to the cloud platform; The cloud platform is configured to: capture thread exception events of the wireless communication module based on the second log data, and respond to the thread exception events.

9. The system according to claim 8, characterized in that, The second data entry point is pre-added to the lowest priority thread of the wireless communication module, and the second log data is used to describe the calling process of the lowest priority thread. The cloud platform is configured to: if the second log data is not received for a continuously preset time threshold, capture the thread blocking event of the wireless communication module and respond to the thread blocking event.

Images