Device binding method, server and internet-of-things device

Abstract

Provided in the present disclosure are a device binding method, a server and an Internet-of-Things device. The method comprises: in response to an activation request from an Internet-of-Things device having been received, on the basis of device information of the Internet-of-Things device and account information of a user account in the activation request, storing binding information between the Internet-of-Things device and the user account; sending a network access permission to the Internet-of-Things device, wherein the network access permission is used for the Internet-of-Things device to access a first communication channel, and the first communication channel is used for receiving and sending service data between the Internet-of-Things device and a server; and when it is detected that the Internet-of-Things device accesses the first communication channel, binding the Internet-of-Things device to the user account on the basis of the binding information. According to the solutions in the present disclosure, it is ensured that user experience after a user is bound to an Internet-of-Things device is not affected by network conditions of the Internet-of-Things device during binding.

Description

Device binding methods, servers and IoT devices

[0001] This application claims priority to Chinese Patent Application No. 202510090565.1, filed on January 20, 2025, entitled "Device Binding Method, Server and Internet of Things Device", the entire contents of which are incorporated herein by reference. Technical Field

[0002] This disclosure relates to the field of Internet of Things (IoT) device management, and in particular to device binding methods, servers, and IoT devices. Background Technology

[0003] With the rapid development of IoT technology, IoT devices are being used more and more widely in daily life and industrial fields. However, during the device binding process, the server may have successfully bound the IoT device to the user account, but because the IoT device is in a weak network or no network state, it has failed to successfully connect to the server's communication channel. As a result, although the server has completed the binding, the IoT device cannot be used or communicate normally. Summary of the Invention

[0004] This disclosure provides a device binding method, a server, and an Internet of Things (IoT) device to solve or mitigate one or more technical problems in the prior art.

[0005] Firstly, this disclosure provides a device binding method applied to a server, including:

[0006] In response to receiving an activation request from an IoT device, based on the device information of the IoT device and the account information of the user account in the activation request, the binding information between the IoT device and the user account is stored.

[0007] Sending network access licenses to IoT devices; wherein, the network access license is used for IoT devices to access the first communication channel; the first communication channel is used for the transmission and reception of business data between IoT devices and servers;

[0008] When an IoT device is detected to be accessing the primary communication channel, the IoT device and the user account are bound together based on the binding information.

[0009] Secondly, this disclosure provides a device binding method for use with Internet of Things (IoT) devices, including:

[0010] Send an activation request to the server; the activation request includes the device information of the IoT device and the account information of the user account; the device information of the IoT device and the account information of the user account are used by the server to determine the binding information between the IoT device and the user account;

[0011] The system receives network access permission from the server and accesses the first communication channel based on the network access permission to trigger the server to bind the IoT device and the user account based on the binding information; wherein, the first communication channel is used for the transmission and reception of business data between the IoT device and the server.

[0012] Thirdly, this disclosure provides a server, including:

[0013] The storage module is used to respond to an activation request received from an IoT device, and store the binding information between the IoT device and the user account based on the device information of the IoT device and the account information of the user account in the activation request.

[0014] The network access license sending module is used to send network access licenses to IoT devices; wherein, the network access license is used for IoT devices to access the first communication channel; the first communication channel is used for the transmission and reception of business data between IoT devices and servers;

[0015] The binding module is used to bind the IoT device and the user account based on the binding information when the IoT device is detected to be accessing the first communication channel.

[0016] Fourthly, this disclosure provides an Internet of Things (IoT) device, including:

[0017] The activation request sending module is used to send an activation request to the server. The activation request includes the device information of the IoT device and the account information of the user account. The device information of the IoT device and the account information of the user account are used by the server to determine the binding information between the IoT device and the user account.

[0018] The binding trigger module is used to receive network access permission from the server, access the first communication channel based on the network access permission, and trigger the server to bind the IoT device and user account based on the binding information; wherein, the first communication channel is used for business data transmission and reception between the IoT device and the server.

[0019] Fifthly, a server is provided, comprising:

[0020] At least one processor; and

[0021] The memory is communicatively connected to the at least one processor; wherein,

[0022] The memory stores instructions that can be executed by the at least one processor to enable the at least one processor to perform any of the methods described in the present disclosure.

[0023] Sixthly, an Internet of Things (IoT) device is provided, comprising:

[0024] At least one processor; and

[0025] The memory is communicatively connected to the at least one processor; wherein,

[0026] The memory stores instructions that can be executed by the at least one processor to enable the at least one processor to perform any of the methods described in the present disclosure.

[0027] In a seventh aspect, a non-transitory computer-readable storage medium is provided storing computer instructions, wherein the computer instructions are used to cause the computer to perform any of the methods according to embodiments of the present disclosure.

[0028] Eighthly, a computer program product is provided, including a computer program that, when executed by a processor, implements any of the methods according to embodiments of the present disclosure.

[0029] The beneficial effects of the technical solution provided in this disclosure include at least the following: the binding process of IoT devices can be divided into two parts: First, when the server receives an activation request from the IoT device, the server can return a network access license, allowing the IoT device to communicate with the server using the network access license. Second, the server monitors the first communication channel used by the IoT device, and only performs the binding operation after the IoT device successfully connects to the first communication channel. This asynchronous device binding method synchronizes the usability status of the IoT device and the user device with the binding status in the server, improving the stability and reliability of device binding, effectively distributing system load, reducing system performance bottlenecks in high-concurrency environments, and ensuring that the user experience after binding the IoT device is not affected by the network status of the IoT device at the time of binding.

[0030] It should be understood that the description in this section is not intended to identify key or essential features of the embodiments of this disclosure, nor is it intended to limit the scope of this disclosure. Other features of this disclosure will become readily apparent from the following description. Attached Figure Description

[0031] In the accompanying drawings, unless otherwise specified, the same reference numerals throughout the various drawings denote the same or similar parts or elements. These drawings are not necessarily drawn to scale. It should be understood that these drawings depict only some embodiments provided according to this disclosure and should not be construed as limiting the scope of this disclosure.

[0032] Figure 1 is a schematic diagram of a device binding method provided in an embodiment of this disclosure;

[0033] Figure 2 is a schematic diagram of a device binding method provided in another embodiment of this disclosure;

[0034] Figure 3 is a schematic diagram of an application example of the device binding method provided in the embodiments of this disclosure;

[0035] Figure 4 is a schematic block diagram of a server provided in an embodiment of this disclosure;

[0036] Figure 5 is a schematic block diagram of a server provided in another embodiment of this disclosure;

[0037] Figure 6 is a schematic block diagram of an Internet of Things (IoT) device provided in an embodiment of this disclosure;

[0038] Figure 7 is a block diagram of an electronic device used to implement the device binding method of the embodiments of the present disclosure. Detailed Implementation

[0039] The present disclosure will now be described in further detail with reference to the accompanying drawings. The same reference numerals in the drawings denote elements that have the same or similar functions. Although various aspects of embodiments are shown in the drawings, they are not necessarily drawn to scale unless specifically indicated otherwise.

[0040] Furthermore, to better illustrate this disclosure, numerous specific details are set forth in the following detailed description. Those skilled in the art will understand that this disclosure can be practiced without certain specific details. In some instances, methods, means, components, and circuits well known to those skilled in the art have not been described in detail in order to highlight the main points of this disclosure.

[0041] To facilitate understanding of the device binding method provided in the embodiments of this disclosure, the relevant technologies of the embodiments of this disclosure are described below. The following relevant technologies are optional solutions and can be arbitrarily combined with the technical solutions of the embodiments of this disclosure, and they all fall within the protection scope of the embodiments of this disclosure.

[0042] In related technologies, IoT device binding typically relies on synchronous requests. That is, the server binds the IoT device and user account simultaneously upon receiving the binding request. However, in high-concurrency environments, this can lead to system performance bottlenecks. Due to the strong coupling between systems, consistency issues can easily arise, causing the binding status of the IoT device and the server to be out of sync, potentially resulting in delays. Furthermore, the operation is complex, system maintenance is difficult, and user experience is negatively impacted. In addition, if the IoT device is in a weak or no-network state during the binding process, it may fail to connect to the server's communication channel, rendering the IoT device unusable and unable to communicate normally.

[0043] The device binding method provided in this disclosure divides the binding process of IoT devices into two parts: First, when the server receives an activation request from the IoT device, the server can return a network access license, allowing the IoT device to communicate with the server using the license. Second, the server can monitor the first communication channel used by the IoT device, and only performs the binding operation after the IoT device successfully connects to the first communication channel. This asynchronous device binding method synchronizes the usability status of the IoT device and the user device with the binding status on the server, improving the stability and reliability of device binding, effectively distributing system load, reducing system performance bottlenecks in high-concurrency environments, and ensuring that the user experience after binding the IoT device is not affected by the network status of the IoT device at the time of binding.

[0044] The device binding method provided in this disclosure is applicable to the management of various IoT devices and has strong versatility and scalability. For example, IoT devices may include, for instance, IPCs (Internet Protocol Cameras), wearable devices, electricity meters, and home appliances. In practical applications, the binding strategy can be flexibly adjusted according to specific application scenarios to adapt to the needs of different types of IoT devices and network environments.

[0045] Figure 1 illustrates a schematic diagram of a device binding method provided in an embodiment of this disclosure. This method can be applied to a server. As shown in Figure 1, the method may include the following steps S110 to S130.

[0046] Step S110: In response to receiving an activation request from an IoT device, based on the device information of the IoT device and the account information of the user account in the activation request, store the binding information between the IoT device and the user account.

[0047] Optionally, users can use an app to bind and associate IoT devices with their accounts. The app can obtain device information from the IoT device or user input, thereby confirming the IoT device to be bound and sending the user's account information to that device. Optionally, it can also send the IoT device's device information. After obtaining the device and account information, the IoT device can send an activation request to the server. Optionally, the activation request can be sent to the server via HTTP (Hypertext Transfer Protocol).

[0048] Alternatively, the aforementioned server can be a remote server, a cloud server, etc. In some descriptions, a cloud server may also be referred to as the cloud platform.

[0049] In this embodiment of the disclosure, when the server receives an activation request from an IoT device, it can determine the binding information between the IoT device and the user account based on the device information of the IoT device and the account information of the user account, and store the binding information without binding the IoT device first.

[0050] Optionally, the IoT device can decode the activation request to determine the device information of the IoT device and the account information of the user account in the activation request.

[0051] In this embodiment of the disclosure, the activation request may include device information of the IoT device and account information of the user account. Optionally, the device information of the IoT device may include the device ID (identification), and the account information of the user account may include the user ID. The server can associate the device ID and the user ID to determine the stored binding information.

[0052] Among these methods, users can obtain IoT device information by scanning the QR code of the IoT device through the APP (Application) on their device, or by manually entering the device information. Users can also obtain user account information by logging in through the APP on their device.

[0053] Optionally, the device information of an IoT device may include information that can identify the IoT device, such as the IoT device's serial number, unique identifier (UID), device version, and device type.

[0054] Optionally, the user account information may include the user account's account code (e.g., a string), username, UID, and other information that can identify the user account.

[0055] Step S120: Send a network access license to the IoT device; wherein, the network access license is used for the IoT device to access the first communication channel; the first communication channel is used for the transmission and reception of business data between the IoT device and the server.

[0056] In this embodiment of the disclosure, the server can generate a network access license based on the device information of the IoT device, and then send the network access license to the IoT device. Optionally, the server can send the network access license to the IoT device via HTTP.

[0057] Correspondingly, IoT devices can receive network access licenses. When the network status of the IoT device is normal, the IoT device can use the network access license to establish a first communication channel with the server, that is, the IoT device accesses the first communication channel.

[0058] Optionally, the IoT device can send an online notification to the server based on the first communication channel. When the server receives the online notification, it can be regarded as the server detecting that the IoT device has accessed the first communication channel.

[0059] In practical applications, after binding, business data can be sent and received between IoT devices and servers through the primary communication channel, enabling IoT devices to function and communicate normally. For example, business data can include instructions issued by the server to the IoT device, or information reported by the IoT device to the server.

[0060] Step S130: When an IoT device is detected to be accessing the first communication channel, the IoT device and the user account are bound together based on the binding information.

[0061] In this embodiment, the server can monitor in real time whether the IoT device is connected to the first communication channel. When the server detects that the IoT device is not connected to the first communication channel, it indicates that the IoT device's network status is poor or there is no network, and the server does not bind the IoT device to the user account. Only when the server detects that the IoT device is connected to the first communication channel does it indicate that the IoT device's network status is normal, and the IoT device can communicate through the first communication channel. The server can then read the previously stored binding information and bind the IoT device to the user account.

[0062] Optionally, after the server successfully binds the IoT device and the user account, the server can notify the user that the binding with the IoT device is successful.

[0063] The device binding method provided in this disclosure divides the IoT device binding process into two parts: First, when the server receives an activation request from the IoT device, the server can return a network access license, allowing the IoT device to communicate with the server using the license. Second, the server monitors the first communication channel used by the IoT device, and only performs the binding operation after the IoT device successfully connects to the first communication channel. This asynchronous device binding method synchronizes the usability status of the IoT device and the user device with the binding status on the server, improving the stability and reliability of device binding, effectively distributing system load, reducing system performance bottlenecks in high-concurrency environments, and ensuring that the user experience after binding the IoT device is not affected by the network status of the IoT device at the time of binding.

[0064] In some embodiments, step S110, in response to receiving an activation request from an IoT device, stores binding information between the IoT device and the user account based on the device information of the IoT device and the account information of the user account in the activation request, including:

[0065] In response to receiving an activation request from an IoT device, the legitimacy of the IoT device is determined based on the device information in the activation request.

[0066] If the legitimacy of the IoT device is confirmed, the binding information between the IoT device and the user account is stored based on the device information of the IoT device and the account information of the user account in the activation request.

[0067] In this embodiment of the disclosure, the legality of the Internet of Things (IoT) device may include whether the IoT device is an authorized device, that is, whether the IoT device is in the manufacturer's or server's authorized list. When the IoT device is in the manufacturer's or server's authorized list, the legality of the IoT device can be determined as positive information, and when the IoT device is not in the manufacturer's or server's authorized list, the legality of the IoT device can be determined as negative information.

[0068] Optionally, the device information may include the IoT device's serial number, UID, device version, device type, etc. The server can determine the legitimacy of the IoT device based on any one or more of the above device information.

[0069] According to the above embodiments, by verifying the legitimacy of IoT devices, it is possible to effectively prevent the binding of illegitimate IoT devices, thereby further improving the reliability of binding IoT devices.

[0070] In some embodiments, the device binding method further includes:

[0071] Once the IoT device and user account are successfully bound, a successful binding notification is sent to the user device based on the user account.

[0072] In this embodiment of the disclosure, when the server successfully binds the IoT device and the user account, the user can view the successful binding notification displayed in the user account through the user device, so that the user can subsequently control the IoT device through the user account.

[0073] According to the above embodiments, the server can notify the user that the binding is successful, so that after the binding is successful, the user can manage and control the IoT device through the user account, which further improves the user experience.

[0074] In some embodiments, when an IoT device and a user account are successfully bound, the server can first send a successful binding notification to the IoT device. When the server detects that the IoT device has received the successful binding notification through a first communication channel, such as when it receives binding confirmation information sent by the IoT device, it sends a successful binding notification to the user device based on the user account. This ensures that the usability status of the IoT device is synchronized with the binding status in the server, further improving the user experience.

[0075] In some embodiments, the first communication channel is a communication channel based on the MQTT (Message Queuing Telemetry Transport) protocol or the WebSocket protocol.

[0076] In this embodiment of the disclosure, the MQTT and WebSocket protocols use smaller data packets. The MQTT or WebSocket protocols can be used to send and receive business data between IoT devices and servers, which can reduce network overhead, thereby reducing the data transmission load and improving data transmission efficiency.

[0077] Figure 2 illustrates a schematic diagram of a device binding method provided in another embodiment of this disclosure. This method can be applied to Internet of Things (IoT) devices. As shown in Figure 2, the method may include the following steps S210 to S220.

[0078] Step S210: Send an activation request to the server; wherein, the activation request includes the device information of the IoT device and the account information of the user account; the device information of the IoT device and the account information of the user account are used by the server to determine the binding information between the IoT device and the user account;

[0079] Prior to this disclosure, users could use an app to bind and associate IoT devices with their user accounts. Optionally, users could obtain IoT device information by scanning a QR code on their device or manually entering device information, and obtain user account information by logging into the app on their device.

[0080] In this embodiment of the disclosure, after receiving device information and account information sent by the APP, the IoT device can send an activation request to the server. The activation request may include the device information of the IoT device and the account information of the user account.

[0081] Correspondingly, when the server receives an activation request from an IoT device, the server can store the binding information between the IoT device and the user account based on the device information of the IoT device and the account information of the user account in the activation request, and send a network access license to the IoT device.

[0082] Step S220: Receive network access permission from the server, access the first communication channel based on the network access permission, so as to trigger the server to bind the IoT device and the user account based on the binding information; wherein, the first communication channel is used for business data transmission and reception between the IoT device and the server.

[0083] In this embodiment of the disclosure, the IoT device can receive a network access license. When the IoT device's network status is normal, the IoT device can use the network access license to establish a first communication channel with the server; that is, the IoT device accesses the first communication channel based on the network access license. Optionally, the IoT device can receive the network access license sent by the IoT device via HTTP.

[0084] Accordingly, when the server detects that an IoT device has accessed the first communication channel, the server can bind the IoT device and the user account based on the binding information.

[0085] The device binding method provided in this disclosure allows an IoT device to send an activation request to a server, which then returns a network access license. The IoT device can then use this license to communicate with the server. This allows the server to perform the binding operation only after the IoT device has successfully connected to the first communication channel. This asynchronous device binding method synchronizes the usability of the IoT device and the user device with the binding status on the server, improving the stability and reliability of device binding, effectively distributing system load, reducing system performance bottlenecks in high-concurrency environments, and ensuring that the user experience after binding the IoT device is not affected by the network status of the IoT device at the time of binding.

[0086] In some embodiments, step S210, sending an activation request to the server, includes:

[0087] Access to a second communication channel is established based on the connection between the user device and the user account;

[0088] An activation request is sent to the server via a second communication channel.

[0089] In this embodiment of the disclosure, when a user begins the binding process (e.g., scanning a QR code on an IoT device or manually entering device information), the user device can connect to the IoT device based on the device information, and the IoT device can access a second communication channel. The second communication channel and the first communication channel can be built based on different communication protocols. Binding the IoT device and the user account is only possible when the IoT device can access both the second and first communication channels.

[0090] Optionally, the APP can notify the IoT device via push notification or Short Messaging Service (SMS). If the IoT device receives the above notification, it can be considered that the IoT device is connected to the user device. Then the IoT device can access the second communication channel and send an activation request to the server based on the second communication channel.

[0091] According to the above embodiments, IoT devices can respond to the user's binding process by accessing a second communication channel and sending an activation request to the server, further improving data transmission efficiency.

[0092] In some embodiments, the second communication channel is a communication channel based on the HTTP protocol.

[0093] In this embodiment of the disclosure, the IoT device can send an activation request to the server via the HTTP protocol, thereby achieving cross-platform data transmission and improving data transmission efficiency and security.

[0094] In some embodiments, the first communication channel is a communication channel based on the MQTT protocol or the WebSocket protocol.

[0095] In this embodiment of the disclosure, the MQTT and WebSocket protocols use smaller data packets. The MQTT or WebSocket protocols can be used to send and receive business data between IoT devices and servers, which can reduce network overhead, thereby reducing the data transmission load and improving data transmission efficiency.

[0096] To better understand the technical solutions of the embodiments of this disclosure, a specific application example is provided below. Figure 3 shows a flowchart of the device binding method. As shown in Figure 3, the device binding method may include the following steps S310-S390:

[0097] Step S310: The user uses the APP to bind and associate the IoT device with the user account;

[0098] Step S320: The APP notifies the IoT device user to prepare to begin the binding process;

[0099] Step S330: The IoT device requests the server to activate and bind the device via the HTTP protocol;

[0100] Step S340: The server's logic may include: the server only activates the device, does not bind the device, and temporarily stores the binding relationship;

[0101] Step S350: The server issues a network access license to the IoT device, allowing the IoT device to access the network and communicate.

[0102] Step S360: The IoT device uses the network access license to communicate with the first communication channel;

[0103] Step S370: The server detects that the IoT device is communicating normally, obtains the previously stored binding information, and binds the user account to the IoT device.

[0104] Step S380: The server informs the IoT device that the binding was successful;

[0105] Step S390: The server informs the user that the binding is successful; the user can be notified of the successful binding through the APP, and the user can confirm the successful device binding in the APP.

[0106] According to the above embodiments, the device's usability status and the server's binding status can be synchronized, avoiding inconsistencies between the two sides, improving user experience, and reducing customer complaint rates. Simultaneously, by separating the device activation and binding processes, system performance bottlenecks in high-concurrency environments are reduced, ensuring system stability and reliability.

[0107] To describe in detail the device binding method provided in this disclosure, two application examples are provided below. The two application examples use a similar method, but have been adjusted in some parameters and details to adapt to different application scenarios.

[0108] Application Example 1:

[0109] Step 1: The user uses the app to begin binding and associating the IoT device with their user account. First, the user opens the app on their mobile phone and binds the IoT device to their user account by scanning a QR code or manually entering the device's serial number.

[0110] Step 2: The app notifies the IoT device user to prepare for the binding process. Specifically, after the user completes the initial binding, the app sends a binding preparation notification to the IoT device. Upon receiving the notification, the IoT device enters the binding preparation state.

[0111] Step 3: The IoT device requests device activation and binding from the server via the HTTP protocol. Specifically, after receiving the binding preparation notification, the IoT device sends a device activation request to the server. This activation request may include necessary information such as the device serial number, device model, and account information.

[0112] Step 4, server logic may include:

[0113] 4.1 The server only activates IoT devices and does not bind them. After receiving a device activation request, the server first verifies the legitimacy of the IoT device. If the legitimacy of the IoT device is confirmed, the server confirms the activation status of the IoT device.

[0114] 4.2 The server temporarily stores the binding information between IoT devices and user accounts. That is, the server temporarily stores the user ID and device ID in the database.

[0115] Step 5: The server issues a network access license to the IoT device. The server returns the generated network access license to the IoT device via HTTP protocol, and the IoT device parses and stores it upon receipt.

[0116] Step 6: The IoT device uses its network access license to communicate with the server via the first communication channel. Specifically, the IoT device uses its network access license to establish a connection with the first communication channel via the MQTT protocol or other applicable communication protocols, and sends a communication request.

[0117] Step 7: The server detects that the IoT device is communicating normally, retrieves the previously stored binding relationship, and binds the IoT device and the user account. Specifically, the server monitors the communication status of the IoT device, and after confirming that the IoT device is communicating normally, it retrieves the binding information from temporary storage and completes the binding of the IoT device and the user account.

[0118] Step 8: The server notifies the user and IoT device of successful binding. Specifically, after completing the binding operation, the server sends a binding success notification to the IoT device and the corresponding app for the user account. Upon receiving the notification, the IoT device can then send a successful binding notification to the user via the app. The user can then confirm the successful device binding in the app, completing the entire binding process.

[0119] Application Example 2:

[0120] Step 1: Users use the app to begin binding and associating IoT devices with their user accounts. Specifically, users can enter the IoT device's unique identifier and account information in the app to initiate the initial binding and association.

[0121] Step 2: The app notifies the IoT device user to prepare for the binding process. Specifically, the app can notify the IoT device to enter the binding preparation state via push notification or SMS service.

[0122] Step 3: The IoT device requests activation and binding from the server via the HTTP protocol. Specifically, after receiving the binding preparation notification, the IoT device sends an activation request to the server containing information such as the device UID, device version, device type, and account information.

[0123] Step 4, server logic may include:

[0124] 4.1 The server only activates IoT devices and does not bind them. After verifying the device information, the server only activates the IoT device and does not perform any binding operations.

[0125] 4.2 The server temporarily stores the binding information between IoT devices and user accounts. That is, the server stores the binding information in a temporary database, awaiting subsequent processing.

[0126] Step 5: The server issues a network access license to the IoT device. Specifically, after receiving the network access license from the server, the IoT device stores it in its memory.

[0127] Step 6: The IoT device uses its network access license to communicate with the first communication channel. Specifically, the IoT device uses its network access license to establish a connection with the first communication channel via the WebSocket protocol and sends a communication request.

[0128] Step 7: The server detects that the IoT device is communicating normally, retrieves the previously stored binding information, and binds the IoT device and the user account. Specifically, the server monitors the connection status of the IoT device in real time. After confirming that the IoT device is communicating normally, it reads the binding information from the temporary database and completes the binding of the IoT device and the user account.

[0129] Step 8: The server notifies the user and IoT device of successful binding. Specifically, after completing the binding operation, the server sends a binding success notification to the IoT device and the corresponding APP of the user account. After receiving the notification, the IoT device can display the binding success notification to the user through the APP. The user can confirm the successful device binding in the APP, completing the entire binding process.

[0130] As can be seen, the device binding method provided in this disclosure can have the following beneficial effects:

[0131] 1. Improved System Performance: This disclosure divides the IoT device binding process into two parts. First, the IoT device requests device activation via HTTP, and the server returns a network access license. The IoT device then communicates with the server using this license. Next, the server monitors the first communication channel used by the IoT device. When communication is detected, the server retrieves the binding information stored on the server and associates the IoT device with the user account. This asynchronous binding method effectively distributes the system load and reduces system performance bottlenecks under high concurrency environments.

[0132] 2. Reduced consistency issues: By separating IoT device activation and binding, the server only performs the binding operation after the IoT device has successfully connected to the communication channel, avoiding inconsistencies in binding states caused by strong coupling between systems. This ensures that the usable state on the device side is consistent with the binding state on the server, improving system stability and reliability.

[0133] 3. Improved user experience: Through asynchronous binding, IoT devices can still be used and communicate normally after activation, even in weak or no network conditions. That is, the binding operation is performed only after the IoT device successfully connects to the first communication channel, ensuring that the user experience after device activation is not affected by network conditions, reducing user waiting time and operation complexity.

[0134] 4. Reduced maintenance complexity: Asynchronous binding simplifies the device binding process and reduces system maintenance complexity. The server only needs to monitor the communication status of IoT devices and complete the binding operation at the appropriate time, improving the system's automation level and reducing the workload of maintenance personnel.

[0135] 5. Reduce customer complaint rate: By improving the success rate and stability of device binding, we ensure that users will not encounter problems due to inconsistent binding status between the device and the server, thereby reducing the customer complaint rate and improving overall user satisfaction.

[0136] 6. Enhanced System Scalability: The device binding method disclosed herein is applicable to the management of various IoT devices, exhibiting strong versatility and scalability. Binding strategies can be flexibly adjusted according to specific application scenarios to adapt to the needs of different types of IoT devices and network environments.

[0137] According to embodiments of this disclosure, this disclosure also provides a server. FIG4 shows a schematic block diagram of a server provided in an embodiment of this disclosure. As shown in FIG4, the server includes:

[0138] Storage module 410 is used to respond to receiving an activation request from an IoT device, and store the binding information between the IoT device and the user account based on the device information of the IoT device and the account information of the user account in the activation request;

[0139] The network access license sending module 420 is used to send network access licenses to IoT devices; wherein, the network access license is used for IoT devices to access the first communication channel; the first communication channel is used for the transmission and reception of business data between IoT devices and servers;

[0140] The binding module 430 is used to bind the IoT device and the user account based on the binding information when the IoT device is detected to be accessing the first communication channel.

[0141] In some embodiments, the storage module 410 is specifically used for:

[0142] In response to receiving an activation request from an IoT device, the legitimacy of the IoT device is determined based on the device information in the activation request.

[0143] If the legitimacy of the IoT device is confirmed, the binding information between the IoT device and the user account is stored based on the device information of the IoT device and the account information of the user account in the activation request.

[0144] In some embodiments, as shown in FIG5, the server further includes a binding notification module 510:

[0145] The binding notification module 510 is used to send a successful binding notification to the user device based on the user account when the IoT device and the user account are successfully bound.

[0146] In some embodiments, the first communication channel is a communication channel based on the MQTT protocol or the WebSocket protocol.

[0147] The specific functions and examples of each module and submodule of the server in this embodiment can be found in the relevant descriptions of the corresponding steps in the above method embodiments, and will not be repeated here.

[0148] According to embodiments of this disclosure, this disclosure also provides an Internet of Things (IoT) device. FIG6 shows a schematic block diagram of an IoT device provided according to an embodiment of this disclosure. As shown in FIG6, the IoT device includes:

[0149] The activation request sending module 610 is used to send an activation request to the server; wherein, the activation request includes the device information of the IoT device and the account information of the user account; the device information of the IoT device and the account information of the user account are used by the server to determine the binding information between the IoT device and the user account;

[0150] The binding trigger module 620 is used to receive network access permission from the server, access the first communication channel based on the network access permission, and trigger the server to bind the IoT device and the user account based on the binding information; wherein, the first communication channel is used for business data transmission and reception between the IoT device and the server.

[0151] In some embodiments, the activation request sending module 610 is specifically used for:

[0152] Access to a second communication channel is established based on the connection between the user device and the user account;

[0153] An activation request is sent to the server via a second communication channel.

[0154] In some embodiments, the second communication channel is a communication channel based on the HTTP protocol.

[0155] In some embodiments, the first communication channel is a communication channel based on the MQTT or WebSocket protocol.

[0156] The specific functions and examples of each module and sub-module of the IoT device in this disclosure embodiment can be found in the relevant descriptions of the corresponding steps in the above method embodiments, and will not be repeated here.

[0157] The acquisition, storage, and application of user personal information involved in the technical solution disclosed herein comply with the provisions of relevant laws and regulations and do not violate public order and good morals.

[0158] Figure 7 is a structural block diagram of an electronic device according to an embodiment of the present disclosure. As shown in Figure 7, the electronic device includes a memory 710 and a processor 720. The memory 710 stores a computer program that can run on the processor 720. The number of memories 710 and processors 720 can be one or more. The memory 710 can store one or more computer programs, which, when executed by the electronic device, cause the electronic device to perform the methods provided in the above-described method embodiments. The electronic device may further include a communication interface 730 for communicating with external devices and performing data exchange and transmission.

[0159] If the memory 710, processor 720, and communication interface 730 are implemented independently, they can be interconnected via a bus to communicate with each other. This bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. This bus can be categorized as an address bus, data bus, control bus, etc. For ease of illustration, only one thick line is used in Figure 7, but this does not indicate that there is only one bus or one type of bus.

[0160] Optionally, in a specific implementation, if the memory 710, processor 720, and communication interface 730 are integrated on a single chip, then the memory 710, processor 720, and communication interface 730 can communicate with each other through an internal interface.

[0161] In one embodiment, the electronic device may be a server in the embodiments of this application, and the electronic device may implement the corresponding processes implemented by the server in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0162] In one embodiment, the electronic device may be an Internet of Things (IoT) device according to the embodiments of this application, and the electronic device may implement the corresponding processes implemented by the IoT device in the various methods of the embodiments of this application. For the sake of brevity, these will not be described in detail here.

[0163] It should be understood that the aforementioned processor can be a Central Processing Unit (CPU), or other general-purpose processors, Digital Signal Processors (DSPs), Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. General-purpose processors can be microprocessors or any conventional processor. It is worth noting that the processor can be a processor supporting Advanced Reduced Instruction Set Machines (ARM) architecture.

[0164] Further, optionally, the aforementioned memory may include read-only memory and random access memory, and may also include non-volatile random access memory. The memory may be volatile or non-volatile, or may include both. Non-volatile memory may include read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory may include random access memory (RAM), which serves as an external cache. Many forms of RAM are available by way of example, but not limitation. Examples include Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), Synchronous DRAM (SDRAM), Double Data Rate Synchronous DRAM (DDR SDRAM), Enhanced Synchronous DRAM (ESDRAM), Synchlink DRAM (SLDRAM), and Direct RAMBUS RAM (DR RAM).

[0165] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented in software, it can be implemented, in whole or in part, as a computer program product. The computer program product includes one or more computer instructions. When the computer instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this disclosure are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another via wired (e.g., coaxial cable, fiber optic, Digital Subscriber Line, DSL) or wireless (e.g., infrared, Bluetooth, microwave, etc.) means. The computer-readable storage medium can be any available medium accessible to a computer, or a data storage device such as a server or data center that integrates one or more available media. The available media can be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., Digital Versatile Discs (DVDs)), or semiconductor media (e.g., Solid State Disks (SSDs)). It is worth noting that the computer-readable storage media mentioned in this disclosure can be non-volatile storage media; in other words, it can be non-transient storage media.

[0166] Those skilled in the art will understand that all or part of the steps of the above embodiments can be implemented by hardware or by a program instructing related hardware. The program can be stored in a computer-readable storage medium, such as a read-only memory, a disk, or an optical disk.

[0167] In the description of the embodiments of this disclosure, references to terms such as "one embodiment," "some embodiments," "example," "specific example," or "some examples," etc., indicate that a specific feature, structure, material, or characteristic described in connection with that embodiment or example is included in at least one embodiment or example of this disclosure. Furthermore, the specific features, structures, materials, or characteristics described may be combined in any suitable manner in one or more embodiments or examples. Moreover, without contradiction, those skilled in the art can combine and integrate the different embodiments or examples described in this specification, as well as the features of those different embodiments or examples.

[0168] In the description of the embodiments disclosed herein, unless otherwise stated, " / " means "or". For example, A / B can mean A or B. The "and / or" in this document is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, and B existing alone.

[0169] In the description of embodiments of this disclosure, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of indicated technical features. Therefore, a feature defined as "first" or "second" may explicitly or implicitly include one or more of that feature. In the description of embodiments of this disclosure, unless otherwise stated, "a plurality of" means two or more.

[0170] The above description is merely an exemplary embodiment of this disclosure and is not intended to limit this disclosure. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this disclosure should be included within the protection scope of this disclosure.

Claims

1. A device binding method, applied to a server, characterized in that, include: In response to receiving an activation request from an IoT device, based on the device information of the IoT device and the account information of the user account in the activation request, the binding information between the IoT device and the user account is stored; Send a network access license to the IoT device; wherein the network access license is used for the IoT device to access a first communication channel; the first communication channel is used for the transmission and reception of business data between the IoT device and the server; When the IoT device is detected to be connected to the first communication channel, the IoT device and the user account are bound together based on the binding information.

2. The method according to claim 1, characterized in that, In response to receiving an activation request from an IoT device, based on the device information of the IoT device and the account information of the user account in the activation request, the binding information between the IoT device and the user account is stored, including: In response to receiving an activation request from an IoT device, the legitimacy of the IoT device is determined based on the device information of the IoT device in the activation request; If the legitimacy of the IoT device is confirmed, the binding information between the IoT device and the user account is stored based on the device information of the IoT device and the account information of the user account in the activation request.

3. The method according to claim 1, characterized in that, Also includes: When the IoT device and the user account are successfully bound, a successful binding notification is sent to the user device based on the user account.

4. The method according to any one of claims 1-3, characterized in that, The first communication channel is a communication channel based on the Message Queue Telemetry Transmission (MQTT) protocol or the WebSocket protocol.

5. A device binding method applied to Internet of Things (IoT) devices, characterized in that, include: An activation request is sent to the server; wherein, the activation request includes device information of the IoT device and account information of the user account; the device information of the IoT device and the account information of the user account are used by the server to determine the binding information between the IoT device and the user account; The system receives a network access permission from the server, accesses a first communication channel based on the network access permission, and triggers the server to bind the IoT device and the user account based on the binding information; wherein, the first communication channel is used for the transmission and reception of business data between the IoT device and the server.

6. The method according to claim 5, characterized in that, Sending the activation request to the server includes: Based on the connection between the user device corresponding to the user account, access is made to the second communication channel; An activation request is sent to the server via the second communication channel.

7. The method according to claim 6, characterized in that, The second communication channel is a communication channel based on the Hypertext Transfer Protocol (HTTP).

8. The method according to any one of claims 5-7, characterized in that, The first communication channel is a communication channel based on the MQTT protocol or the WebSocket protocol.

9. A server, characterized in that, include: A storage module is configured to, in response to receiving an activation request from an IoT device, store binding information between the IoT device and the user account based on the device information of the IoT device and the account information of the user account in the activation request; A network access license sending module is used to send a network access license to the IoT device; wherein, the network access license is used for the IoT device to access a first communication channel; the first communication channel is used for the transmission and reception of business data between the IoT device and the server; The binding module is used to bind the IoT device and the user account based on the binding information when the IoT device is detected to be accessing the first communication channel.

10. An Internet of Things (IoT) device, characterized in that, include: An activation request sending module is used to send an activation request to the server; wherein, the activation request includes device information of the IoT device and account information of the user account; the device information of the IoT device and the account information of the user account are used by the server to determine the binding information between the IoT device and the user account; The binding trigger module is used to receive network access permission from the server, access the first communication channel based on the network access permission, and trigger the server to bind the IoT device and the user account based on the binding information; wherein, the first communication channel is used for business data transmission and reception between the IoT device and the server.

11. A server, comprising: At least one processor; as well as A memory communicatively connected to the at least one processor; wherein, The memory stores instructions that can be executed by the at least one processor to enable the at least one processor to perform the method of any one of claims 1-4.

12. An Internet of Things (IoT) device, comprising: At least one processor; as well as A memory communicatively connected to the at least one processor; wherein, The memory stores instructions that can be executed by the at least one processor to enable the at least one processor to perform the method of any one of claims 5-8.

Images