Internet of Things (IoT) devices and their network control methods, apparatuses, storage media and products

Abstract

This application discloses an Internet of Things (IoT) device and its network control method, apparatus, storage medium, and product. The method includes: the IoT device sending a domain name resolution request from a cloud server to a DNS server; if the resolution response is determined to be a resolution failure, obtaining the access address of the target device and establishing a communication connection with the target device based on the access address; wherein the target device is a device managed by the cloud server and located on the same local area network or under the same management account as the IoT device; obtaining the IP address of the cloud server to which the target device is currently connected; and establishing a communication connection with the cloud server based on the IP address. This method allows for the establishment of a communication connection with the cloud server even when DNS server resolution fails, effectively ensuring the network status of the IoT device and thus improving the reliability of intelligent control and the human-computer interaction experience.

Description

Technical Field

[0001] This application relates to the field of intelligent control, and more particularly to an Internet of Things (IoT) device and its network control method, apparatus, storage medium, and product. Background Technology

[0002] With the improvement of people's living standards and the development of science and technology, the Internet of Things (IoT) has emerged. The IoT is essentially an internet connecting all things, and smart homes are a part of it. Smart homes excel in home entertainment and appliance control, making people's home life safer, simpler, and more comfortable in every aspect.

[0003] Smart home technology utilizes advanced computer technology, network communication technology, intelligent cloud control, and integrated wiring technology, while incorporating personalized needs. It organically combines various subsystems related to home life, such as security, lighting control, curtain control, gas valve control, smart appliances, scene linkage, underfloor heating, health care, hygiene and epidemic prevention, and security, to achieve a brand-new home living experience through networked integrated intelligent control and management.

[0004] To facilitate convenient remote control by users, IoT devices need to be kept online and accessible. This means the IoT devices should establish a network connection with the smart control server, allowing users to access the server for related smart control via a client app (application software). However, in related technologies, if DNS (Domain Name System) resolution fails during the connection process, the IoT device, although able to connect to the network, will be unable to access the server. This results in the IoT device being in a "false online, true offline" state, affecting the reliability of smart control. Summary of the Invention

[0005] In view of this, embodiments of this application provide an Internet of Things (IoT) device and its network control method, apparatus, storage medium, and product, aiming to ensure the network status of IoT devices and effectively improve the reliability of intelligent control and human-computer interaction experience.

[0006] The technical solution of this application embodiment is implemented as follows:

[0007] In a first aspect, embodiments of this application provide a method for controlling the network connectivity of an Internet of Things (IoT) device, including:

[0008] Send a domain name resolution request from the cloud server to the DNS server;

[0009] If the parsing response is determined to be a parsing failure, the access address of the target device is obtained, and a communication connection is established with the target device based on the access address of the target device; wherein, the target device is a device under the management of the cloud server and located on the same local area network or under the same management account as the IoT device;

[0010] Obtain the IP (Internet Protocol) address of the cloud server that the target device is currently connecting to;

[0011] A communication connection is established with the cloud server based on the IP address.

[0012] In some implementations, obtaining the access address of the target device includes:

[0013] Obtain the access address of the target device based on pre-stored whitelist information and set policies;

[0014] The whitelist information is used to maintain the access addresses of devices that support access by the IoT devices.

[0015] In some implementations, the method further includes:

[0016] After the IoT device connects to a local area network gateway or router and is bound to a management account, it obtains the MAC (Media Access Control Address) of other devices under the management account and adds the MAC addresses of the other devices to the whitelist information; and / or,

[0017] The IoT device obtains the MAC addresses of other devices located in the same local area network and adds the MAC addresses of the other devices to the whitelist information.

[0018] In some implementations, obtaining the access address of the target device based on pre-stored whitelist information and set policies includes:

[0019] Devices that support short-range wireless communication are selected as candidate devices based on pre-stored whitelist information;

[0020] Select any device from the candidate devices that is communicating normally with the cloud server as the target device, and obtain the access address of the target device.

[0021] In some implementations, establishing a communication connection with the target device based on the access address of the target device includes:

[0022] Based on the access address of the target device, a short-range wireless communication connection is established with the target device.

[0023] In some implementations, selecting any device that can communicate normally with the cloud server from the candidate devices as the target device includes:

[0024] Obtain the status parameters of the communication status between each candidate device and the cloud server;

[0025] Based on the status parameters, the device closest to the IoT device is selected from the candidate devices that are communicating normally with the cloud server.

[0026] In some implementations, sending the domain name resolution request from the cloud server to the DNS server includes:

[0027] In response to the detection results of the IoT device being powered on, restarted, or disconnected from the cloud server, a domain name resolution request from the cloud server is sent to the DNS server.

[0028] Secondly, embodiments of this application provide a network control device for an Internet of Things (IoT) device, comprising:

[0029] The sending module is used to send domain name resolution requests from the cloud server to the DNS server;

[0030] The first connection module is used to obtain the access address of the target device and establish a communication connection with the target device based on the access address of the target device if it is determined that the parsing response is a parsing failure result; wherein, the target device is a device under the management of the cloud server and located on the same local area network or under the same management account as the IoT device;

[0031] The acquisition module is used to acquire the IP address of the cloud server that the target device is connecting to;

[0032] The second connection module is used to establish a communication connection with the cloud server based on the IP address.

[0033] Thirdly, embodiments of this application provide an Internet of Things (IoT) device, including: a processor and a memory for storing a computer program capable of running on the processor, wherein, when the processor is used to run the computer program, it executes the steps of the method described in the first aspect of embodiments of this application.

[0034] In some implementations, the IoT device is an IoT wired controller.

[0035] Fourthly, embodiments of this application also provide a storage medium storing a computer program, which, when executed by a processor, implements the steps of the method described in the first aspect of embodiments of this application.

[0036] Fifthly, embodiments of this application also provide a computer program product, including a computer program that, when executed by a processor, implements the steps of the method described in the first aspect of embodiments of this application.

[0037] The technical solution provided in this application embodiment involves an IoT device sending a domain name resolution request from a cloud server to a DNS server. If the resolution response indicates a resolution failure, the access address of the target device is obtained, and a communication connection is established with the target device based on that access address. The target device is a device managed by the cloud server and located on the same local area network or under the same management account as the IoT device. The IP address of the cloud server to which the target device is currently connected is obtained. Based on the IP address, a communication connection is established with the cloud server. Thus, even when DNS server resolution fails, a communication connection can be established with the target device, which is managed by the cloud server and located on the same local area network or under the same management account as the IoT device, to obtain the IP address of the cloud server on that target device. A communication connection is then established with the cloud server based on this IP address. This ensures that a communication connection can still be established with the cloud server even when DNS server resolution fails, effectively protecting the network connectivity of the IoT device and improving the reliability of intelligent control and the human-computer interaction experience. Attached Figure Description

[0038] Figure 1 This is a flowchart illustrating the network control method for IoT devices according to an embodiment of this application;

[0039] Figure 2 This is a flowchart illustrating the network control method for an IoT device as an application embodiment of this application;

[0040] Figure 3 This is a schematic diagram of the network control device for an IoT device according to an embodiment of this application;

[0041] Figure 4 This is a schematic diagram of the structure of an IoT device according to an embodiment of this application. Detailed Implementation

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

[0043] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs. The terminology used herein in the specification of this application is for the purpose of describing particular embodiments only and is not intended to be limiting of this application.

[0044] This application provides a method for controlling an Internet of Things (IoT) device. The IoT device can be understood as various smart devices that support connection and interaction via the Internet. For example, in a smart home scenario, it may include, but is not limited to, smart lights, smart sockets, smart door locks, and smart wired controllers for electronic devices. Figure 1 As shown, the method includes:

[0045] Step 101: Send a domain name resolution request from the cloud server to the DNS server.

[0046] Here, in order to achieve the effect of online intelligent control, IoT devices need to establish a connection with the cloud server, that is, to achieve a network connection with the cloud server. Since IoT devices often only have the cloud server's domain name configured or require the user to manually enter the cloud server's domain name, the IoT device needs to send the cloud server's domain name resolution request to the DNS server to obtain the cloud server's IP address, and then establish a connection with the cloud server based on the IP address.

[0047] Step 102: If the parsing response is determined to be a parsing failure, then obtain the access address of the target device and establish a communication connection with the target device based on the access address of the target device; wherein, the target device is a device under the management of the cloud server and located on the same local area network or under the same management account as the IoT device.

[0048] If the DNS server returns a resolution response containing the cloud server's IP address, the IoT device can directly establish a connection with the cloud server based on that IP address. If the DNS server returns a resolution failure result, the IoT device will be unable to successfully connect to the cloud server, thus causing the IoT device to go offline.

[0049] It should be noted that there may be various reasons for DNS server resolution failure, including but not limited to: network connection problems, DNS server malfunctions, domain name spelling errors, DNS caching problems, domain name registration problems, domain name server configuration problems, and DNS hijacking. This application embodiment does not limit these reasons. Specifically, network connection problems refer to DNS resolution failure caused by network connectivity issues; DNS server malfunctions refer to problems with or unavailability of the DNS server, leading to DNS resolution failure; domain name spelling errors refer to DNS resolution failure if the entered domain name is misspelled, requiring ensuring the correct spelling; DNS caching problems refer to issues with the DNS cache on the local computer or router, causing resolution failure, requiring attempts to clear the local DNS cache or restart the router; domain name registration problems refer to DNS resolution failure if the domain name is not correctly registered or the domain name registration information is incorrect; domain name server configuration problems refer to DNS resolution failure if the domain name server record is incorrect or the domain name server is configured incorrectly; and DNS hijacking refers to the possibility of DNS hijacking by ISPs or other network providers, redirecting the user's DNS resolution request to an incorrect server, thus causing resolution failure.

[0050] In this embodiment, regardless of the reason for the domain name resolution failure, if the resolution response is determined to be a resolution failure, the IoT device obtains the access address of the target device and establishes a communication connection with the target device based on the access address to obtain the IP address of the cloud server on the target device side. It should be noted that the target device and the IoT device share the same cloud server.

[0051] Step 103: Obtain the IP address of the cloud server that the target device is connecting to.

[0052] Here, after an IoT device establishes a communication connection with a target device, it can obtain the IP address of the cloud server that the target device is connecting to.

[0053] Step 104: Establish a communication connection with the cloud server based on the IP address.

[0054] Here, after obtaining the IP address of the cloud server, the IoT device can access the cloud server based on the IP address, and thus establish a communication connection with the cloud server.

[0055] It is understood that the network control method of this application embodiment can establish a communication connection with the target device under the management of the cloud server and located on the same local area network or under the same management account as the IoT device when the DNS server resolution fails, and obtain the IP address of the cloud server on the target device side. Based on the IP address, a communication connection with the cloud server can be established, so that a communication connection can be established with the cloud server even when the DNS server resolution fails, effectively ensuring the network status of the IoT device, thereby improving the reliability of intelligent control and the human-computer interaction experience.

[0056] For example, obtaining the access address of the target device includes:

[0057] Obtain the access address of the target device based on pre-stored whitelist information and set policies;

[0058] The whitelist information is used to maintain the access addresses of devices that support access by the IoT devices.

[0059] Here, IoT devices can store and maintain whitelist information locally. This whitelist information can include the access addresses of other devices that the IoT device can access, such as other IoT devices in a home environment that are managed by the same cloud server. In this way, the IoT device can determine the target device from the whitelist information and obtain the access address of the target device based on a set policy. The set policy can be set according to requirements. For example, it can be a policy that supports setting a communication method or a policy that is selected based on communication distance. This application embodiment does not limit this.

[0060] Exemplarily, the method further includes:

[0061] After the IoT device connects to the local area network gateway or router and is bound to a management account, it obtains the MAC addresses of other devices under the management account and adds the MAC addresses of the other devices to the whitelist information; and / or,

[0062] The IoT device obtains the MAC addresses of other devices located in the same local area network and adds the MAC addresses of the other devices to the whitelist information.

[0063] In one application example, after an IoT device connects to a local area network gateway or router and is bound to a management account, it can obtain the MAC addresses of other devices under that management account. This management account is the user-registered account used to log in to the cloud server. If the user manages multiple IoT devices in a home environment based on this cloud server, the current IoT device, after binding to the management account, can obtain the MAC addresses of other IoT devices under that management account and add their MAC addresses to a whitelist.

[0064] In another application example, IoT devices can also obtain the MAC addresses of other devices located on the same local area network (LAN) and add these MAC addresses to a whitelist. For instance, if multiple IoT devices are connected via a LAN in a home environment, any one of these devices can obtain the MAC addresses of other IoT devices on the LAN and add them to its local whitelist. For example, in a multi-split air conditioner, where multiple indoor units are connected via a LAN, the smart control board of each indoor unit can obtain the MAC addresses of the smart control boards of other indoor units based on the LAN and add these MAC addresses to its local whitelist.

[0065] For example, obtaining the access address of the target device based on pre-stored whitelist information and set policies includes:

[0066] Devices that support short-range wireless communication are selected as candidate devices based on pre-stored whitelist information;

[0067] Select any device from the candidate devices that is communicating normally with the cloud server as the target device, and obtain the access address of the target device.

[0068] Here, IoT devices can select devices that support short-range wireless communication from a pre-stored whitelist as candidate devices, and select any device that can communicate normally with the cloud server as the target device from the candidate devices. After establishing a short-range wireless communication connection with the target device, the device can obtain the IP address of the cloud server on the target device side.

[0069] For example, the short-range wireless communication can be Bluetooth communication or Near Link communication, and this application embodiment does not limit this. Near Link communication is a new type of wireless communication technology specifically designed for short-range data transmission. Compared to traditional technologies such as Bluetooth and Wi-Fi, it has undergone numerous innovative upgrades (and also introduced some key 5G technologies), achieving comprehensive improvements in speed, latency, transmission distance, security, and reliability. In other words, Near Link communication is essentially an enhanced version of a "Wi-Fi + Bluetooth" hybrid.

[0070] Understandably, the whitelist information also includes parameters such as whether the device supports short-range wireless communication and the type of short-range wireless communication it supports. Based on this, IoT devices can select candidate devices from the whitelist information. The IoT devices then further select target devices based on the communication status between the candidate devices and the cloud server, and obtain the access address of the target devices from the whitelist information.

[0071] For example, establishing a communication connection with the target device based on the access address of the target device includes:

[0072] Based on the access address of the target device, a short-range wireless communication connection is established with the target device.

[0073] Understandably, connecting IoT devices and target devices via short-range wireless communication can overcome the limitations of wired local area networks and allow access to the IP addresses of cloud servers on other devices in a home environment.

[0074] For example, selecting any device that can communicate normally with the cloud server from the candidate devices as the target device includes:

[0075] Obtain the status parameters of the communication status between each candidate device and the cloud server;

[0076] Based on the status parameters, the device closest to the IoT device is selected from the candidate devices that are communicating normally with the cloud server.

[0077] In one application example, devices in a home scenario can generate communication status detection results between themselves and the cloud server based on heartbeat packets. Thus, IoT devices can obtain communication status parameters between each candidate device and the cloud server based on the detection results of the communication status of each candidate device. Preferably, to enhance the reliability of short-range wireless communication, the device closest to the IoT device can be selected from the candidate devices that are communicating normally with the cloud server based on the status parameters. This effectively ensures that the IoT device successfully establishes a short-range wireless communication connection with the target device and obtains the IP address of the cloud server.

[0078] For example, sending the domain name resolution request from the cloud server to the DNS server includes:

[0079] In response to the detection results of the IoT device being powered on, restarted, or disconnected from the cloud server, a domain name resolution request from the cloud server is sent to the DNS server.

[0080] Here, in response to a user's power-on or restart operation, when the IoT device needs to re-establish a connection with the cloud server, it can send a domain name resolution request from the cloud server to the DNS server. Alternatively, the IoT device can also send a domain name resolution request from the cloud server to the DNS server after detecting a disconnection from the cloud server based on a heartbeat packet.

[0081] The following example illustrates the network control method for IoT devices.

[0082] Reference Figure 2 In this application embodiment, when device A cannot connect to the cloud server due to DNS resolution failure, device A can communicate with device B via Bluetooth or StarFlash to obtain the IP address of the cloud server and then establish a connection with the cloud server. Specifically, this includes the following steps:

[0083] Step 201: Device A connects to Wi-Fi.

[0084] Here, device A can automatically connect to Wi-Fi devices in home or office settings after being powered on.

[0085] Step 202: Bind the account to device A.

[0086] Here, device A can be pre-linked with the user's account for logging into the cloud server.

[0087] Step 203: Obtain the MAC addresses of other devices under the same account via the cloud.

[0088] Here, the Wi-Fi device can store the MAC addresses of all devices under the user's account on the cloud server. Device A can obtain the MAC addresses of other devices under the same account after connecting to the Wi-Fi device.

[0089] Step 204: If device A is directly connected to the air conditioner, obtain the MAC addresses of other screen devices of the unit through the non-polar serial port.

[0090] Here, if device A is connected to the local area network of a multi-split air conditioner, the MAC address of other screen-end devices (i.e., wired controllers) of the unit can be obtained through a non-polar serial port.

[0091] Step 205: Add the obtained MAC address to the whitelist.

[0092] Here, device A can add the MAC address obtained in step 203 and / or step 204 to the local whitelist information for subsequent access connections in the event of DNS resolution failure.

[0093] Step 206: Device A attempts to establish communication with the cloud server.

[0094] Here, device A attempts to establish communication with the cloud server. Device A's domain name resolver can send the cloud server's domain name resolution request to the DNS server.

[0095] Step 207: Determine if device A failed to resolve the cloud server IP address via DNS. If so, proceed to step 208.

[0096] Here, device A, based on the DNS server's resolution response received by the domain name resolver, if it determines that the resolution has failed, proceeds to step 208; if it can obtain the cloud server's IP address based on the resolution response, it can establish a connection with the cloud server based on that IP address.

[0097] Step 208: Determine if there is a device B near device A that is in the whitelist and supports both Wi-Fi and Bluetooth / StarFlash. If so, proceed to step 209.

[0098] Here, device A determines that there is a device B in the whitelist that supports Bluetooth or StarFlash communication nearby based on the connected Wi-Fi device. Then it determines that device A can obtain the IP address of the cloud server based on the short-range wireless communication with device B, and executes step 209.

[0099] Step 209: Device A establishes a Bluetooth / StarFlash connection with Device B.

[0100] Device A establishes a Bluetooth or StarFlash connection with Device B based on Device B's MAC address.

[0101] Step 210: Determine whether device B is communicating normally with the cloud server. If so, proceed to steps 211 and 212.

[0102] Here, each device in the whitelist can generate a detection result of the communication status between the generator and the cloud server based on the heartbeat packets between the generator and the cloud server. Device A obtains the detection result of the communication status of device B. If it is determined that device B is communicating normally with the cloud server, then steps 211 and 212 are executed. Otherwise, after establishing a communication connection with other devices that are communicating normally with the cloud server (i.e., the new device B), the subsequent steps 211 and 212 are executed.

[0103] Step 211: Device A obtains the IP address of the cloud server that Device B is currently connecting to.

[0104] Step 212: Device A successfully connects to the cloud server.

[0105] It is understood that in this application embodiment, when DNS resolution fails and the device cannot connect to the cloud server, device A can obtain the IP address of the cloud server by establishing Bluetooth or StarFlash communication with device B. Thus, even when DNS server resolution fails, it can still establish a communication connection with the cloud server, effectively ensuring the network status of IoT devices and thereby improving the reliability of intelligent control and the human-computer interaction experience.

[0106] To implement the method of the embodiments of this application, the embodiments of this application also provide a network control device for an Internet of Things (IoT) device. This network control device for an IoT device corresponds to the network control method for an IoT device described above, and the steps in the embodiments of the network control method for an IoT device described above are also fully applicable to the embodiments of the network control device for an IoT device described above.

[0107] like Figure 3 As shown, the network control device for this IoT device includes: a sending module 301, a first connection module 302, an acquisition module 303, and a second connection module 304. The sending module 301 sends a domain name resolution request from the cloud server to the DNS server; the first connection module 302, if the resolution response is determined to be a resolution failure, acquires the access address of the target device and establishes a communication connection with the target device based on the access address; wherein, the target device is a device managed by the cloud server and located on the same local area network or under the same management account as the IoT device; the acquisition module 303 acquires the IP address of the cloud server to which the target device is connecting; the second connection module 304 establishes a communication connection with the cloud server based on the IP address.

[0108] In some embodiments, the first connection module 302 obtains the access address of the target device, including:

[0109] Obtain the access address of the target device based on pre-stored whitelist information and set policies;

[0110] The whitelist information is used to maintain the access addresses of devices that support access by the IoT devices.

[0111] In some embodiments, the first connection module 302 is further configured to:

[0112] After the IoT device connects to the local area network gateway or router and is bound to a management account, it obtains the MAC addresses of other devices under the management account and adds the MAC addresses of the other devices to the whitelist information; and / or,

[0113] Obtain the MAC addresses of other devices located on the same local area network, and add the MAC addresses of the other devices to the whitelist information.

[0114] In some embodiments, the first connection module 302 obtains the access address of the target device based on pre-stored whitelist information and set policies, including:

[0115] Devices that support short-range wireless communication are selected as candidate devices based on pre-stored whitelist information;

[0116] Select any device from the candidate devices that is communicating normally with the cloud server as the target device, and obtain the access address of the target device.

[0117] In some embodiments, the first connection module 302 establishes a communication connection with the target device based on the access address of the target device, including:

[0118] Based on the access address of the target device, a short-range wireless communication connection is established with the target device.

[0119] In some embodiments, the first connection module 302 selects any device that is normally communicating with the cloud server from the candidate devices as the target device, including:

[0120] Obtain the status parameters of the communication status between each candidate device and the cloud server;

[0121] Based on the status parameters, the device closest to the IoT device is selected from the candidate devices that are communicating normally with the cloud server.

[0122] In some embodiments, the sending module 301 is specifically used for:

[0123] In response to the detection results of the IoT device being powered on, restarted, or disconnected from the cloud server, a domain name resolution request from the cloud server is sent to the DNS server.

[0124] In practical applications, the sending module 301, the first connection module 302, the acquisition module 303, and the second connection module 304 can be implemented by the processor of the IoT device. Of course, the processor needs to run the computer program in the memory to implement its functions.

[0125] It should be noted that the network control device for IoT devices provided in the above embodiments is only illustrated by the division of the above program modules. In practical applications, the above processing can be assigned to different program modules as needed, that is, the internal structure of the device can be divided into different program modules to complete all or part of the processing described above. In addition, the network control device for IoT devices provided in the above embodiments and the network control method embodiments for IoT devices belong to the same concept, and the specific implementation process can be found in the method embodiments, which will not be repeated here.

[0126] Based on the hardware implementation of the above program modules, and in order to implement the method of the embodiments of this application, the embodiments of this application also provide an Internet of Things device. Figure 4 This is only an exemplary structure of the IoT device, not the entire structure; it can be implemented as needed. Figure 4 The structure shown may be part or all of the structure.

[0127] like Figure 4 As shown, the IoT device 400 provided in this embodiment includes at least one processor 401, a memory 402, a user interface 403, and at least one network interface 404. The various components in the IoT device 400 are coupled together via a bus system 405. It can be understood that the bus system 405 is used to implement communication between these components. In addition to a data bus, the bus system 405 also includes a power bus, a control bus, and a status signal bus. However, for clarity, in… Figure 4 The general designated all buses as Bus System 405.

[0128] The user interface 403 may include a monitor, keyboard, mouse, trackball, click wheel, buttons, touchpad, or touch screen.

[0129] The network interface 404 may include a Wi-Fi communication module for connecting Wi-Fi devices, and may also include a Bluetooth module and / or a StarScan module for short-range wireless communication. This application embodiment does not limit this.

[0130] The memory 402 in this embodiment is used to store various types of data to support the operation of IoT devices. Examples of such data include any computer programs used to operate on IoT devices.

[0131] The IoT device network control method disclosed in this application can be applied to or implemented by the processor 401. The processor 401 may be an integrated circuit chip with signal processing capabilities. During implementation, each step of the IoT device network control method can be completed by the integrated logic circuits in the processor 401 or by software instructions. The processor 401 can be a general-purpose processor, a digital signal processor (DSP), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The processor 401 can implement or execute the methods, steps, and logic block diagrams disclosed in this application. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the method disclosed in this application can be directly manifested as execution by a hardware decoding processor, or execution by a combination of hardware and software modules in the decoding processor. The software modules can be located in a storage medium, specifically memory 402. The processor 401 reads information from memory 402 and, in conjunction with its hardware, completes the steps of the IoT device network control method provided in this application.

[0132] In an exemplary embodiment, the Internet of Things (IoT) device may be implemented by one or more application-specific integrated circuits (ASICs), DSPs, programmable logic devices (PLDs), complex programmable logic devices (CPLDs), field-programmable gate arrays (FPGAs), general-purpose processors, controllers, microcontrollers (MCUs), microprocessors, or other electronic components to perform the aforementioned methods.

[0133] For example, an IoT device can be an IoT wired controller.

[0134] It is understood that memory 402 can be volatile memory or non-volatile memory, or both. Non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), ferromagnetic random access memory (FRAM), flash memory, magnetic surface memory, optical disc, or compact disc read-only memory (CD-ROM); magnetic surface memory can be disk storage or magnetic tape storage. Volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as Static Random Access Memory (SRAM), Synchronous Static Random Access Memory (SSRAM), Dynamic Random Access Memory (DRAM), Synchronous Dynamic Random Access Memory (SDRAM), Double Data Rate Synchronous Dynamic Random Access Memory (DDRSDRAM), Enhanced Synchronous Dynamic Random Access Memory (ESDRAM), Sync Link Dynamic Random Access Memory (SLDRAM), and Direct Rambus Random Access Memory (DRRAM).The memories described in the embodiments of this application are intended to include, but are not limited to, these and any other suitable types of memories.

[0135] In an exemplary embodiment, this application also provides a storage medium, namely a computer storage medium, specifically a computer-readable storage medium, such as a memory 402 that stores a computer program. This computer program can be executed by the processor 401 of an Internet of Things (IoT) device to complete the steps described in the method of this application embodiment. The computer-readable storage medium can be a ROM, PROM, EPROM, EEPROM, Flash Memory, magnetic surface memory, optical disc, or CD-ROM, etc.

[0136] In an exemplary embodiment, this application also provides a computer program product, including a computer program that can be executed by the processor 401 of an Internet of Things device 400 to complete the steps described in the method of this application embodiment.

[0137] It should be noted that terms such as "first" and "second" are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence.

[0138] Furthermore, the technical solutions described in the embodiments of this application can be combined arbitrarily without conflict.

[0139] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A method for controlling the network of an Internet of Things (IoT) device, characterized in that, include: Send a domain name resolution request from the cloud server to the DNS server; If the parsing response is determined to be a parsing failure, the access address of the target device is obtained, and a communication connection is established with the target device based on the access address of the target device; wherein, the target device is a device under the management of the cloud server and located on the same local area network or under the same management account as the IoT device; Obtain the IP address of the cloud server that the target device is currently connecting to; A communication connection is established with the cloud server based on the IP address.

2. The method according to claim 1, characterized in that, The step of obtaining the access address of the target device includes: Obtain the access address of the target device based on pre-stored whitelist information and set policies; The whitelist information is used to maintain the access addresses of devices that support access by the IoT devices.

3. The method according to claim 2, characterized in that, The method further includes: After the IoT device connects to the local area network gateway or router and is bound to a management account, it obtains the MAC addresses of other devices under the management account and adds the MAC addresses of the other devices to the whitelist information; and / or, The IoT device obtains the MAC addresses of other devices located in the same local area network and adds the MAC addresses of the other devices to the whitelist information.

4. The method according to claim 2, characterized in that, The process of obtaining the access address of the target device based on pre-stored whitelist information and set policies includes: Devices that support short-range wireless communication are selected as candidate devices based on pre-stored whitelist information; Select any device from the candidate devices that is communicating normally with the cloud server as the target device, and obtain the access address of the target device.

5. The method according to claim 4, characterized in that, The step of establishing a communication connection with the target device based on the access address of the target device includes: Based on the access address of the target device, a short-range wireless communication connection is established with the target device.

6. The method according to claim 4, characterized in that, Selecting any device from the candidate devices that can communicate normally with the cloud server as the target device includes: Obtain the status parameters of the communication status between each candidate device and the cloud server; Based on the status parameters, the device closest to the IoT device is selected from the candidate devices that are communicating normally with the cloud server.

7. The method according to claim 1, characterized in that, Sending the domain name resolution request from the cloud server to the DNS server includes: In response to the detection results of the IoT device being powered on, restarted, or disconnected from the cloud server, a domain name resolution request from the cloud server is sent to the DNS server.

8. A network control device for an Internet of Things (IoT) device, characterized in that, include: The sending module is used to send domain name resolution requests from the cloud server to the DNS server; The first connection module is used to obtain the access address of the target device and establish a communication connection with the target device based on the access address of the target device if it is determined that the parsing response is a parsing failure result; wherein, the target device is a device under the management of the cloud server and located on the same local area network or under the same management account as the IoT device; The acquisition module is used to acquire the IP address of the cloud server that the target device is connecting to; The second connection module is used to establish a communication connection with the cloud server based on the IP address.

9. An Internet of Things (IoT) device, characterized in that, include: The processor and memory for storing computer programs that can run on the processor, wherein, The processor, when running a computer program, performs the steps of the method according to any one of claims 1 to 7.

10. The Internet of Things device according to claim 9, characterized in that, The IoT device is an IoT wired controller.

11. A storage medium storing a computer program, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 7.

12. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 7.

Images