Batch network configuration method and system for internet of things device

Abstract

The application relates to a batch network configuration method and system of an Internet of Things device, and belongs to the technical field of the Internet of Things. The method comprises the following steps: configuring a gateway host access server; based on unique code information of the gateway host, the gateway host obtains a device installation list of a to-be-assembled project corresponding to the unique code information from the server; and the gateway host binds an installed device based on the device installation list, and the installed device is automatically configured with a network through the gateway host. When the gateway host searches for a sub-device, whether the sub-device is bound can be confirmed through the device installation list, and after the binding is completed, the gateway host calls an interface provided by an SDK to inform an Internet of Things platform to proxy the sub-device, so that manual intervention is reduced, and network configuration operation of the sub-device is simplified.

Description

Technical Field

[0001] This application relates to the technical field of the Internet of Things (IoT), and in particular to a method and system for batch network configuration of IoT devices. Background Technology

[0002] The Internet of Things (IoT) refers to the intelligent sensing, identification, and management of objects by collecting various information sensors in real time and connecting them to various networks to achieve connectivity between things and between things and people. Among the many IoT devices, there are many sub-devices that do not integrate the Link SDK. These sub-devices typically lack IP addresses and cannot directly connect to the IoT platform; examples include Zigbee devices and KNX devices.

[0003] Currently, users can select a gateway device through their client, and then add the gateway device via LAN or Bluetooth. After the gateway device is added, related sub-devices under the gateway device can be added. After selecting the device type of the sub-device, the sub-device can be bound to the gateway device via LAN or Bluetooth, thereby establishing a connection between the sub-device and the IoT platform.

[0004] However, with the upgrading of IoT technology and the proposal of whole-house intelligence, more and more sub-devices need to be connected to the IoT platform. The traditional solution of configuring each sub-device individually has the drawback of being cumbersome to operate. Summary of the Invention

[0005] To simplify the network configuration of sub-devices, this application provides a method and system for batch network configuration of IoT devices.

[0006] Firstly, this application provides a method for batch network configuration of IoT devices, employing the following technical solution:

[0007] A method for batch network configuration of IoT devices, comprising:

[0008] Configure the gateway host to access the server;

[0009] Based on the unique coding information of the gateway host, the gateway host obtains from the server the equipment installation list of the items to be assembled corresponding to the unique coding information;

[0010] The gateway host binds the installed devices based on the device installation list, and the installed devices are automatically configured to the network through the gateway host.

[0011] By adopting the above technical solution, the unique coding information of the gateway host can identify which project it belongs to. When the gateway host connects to the server, it retrieves the device installation list corresponding to the unique coding information from the server. This list includes the sub-device's model, device identifier, and corresponding authentication information. When the gateway host finds a sub-device, it can confirm whether to bind it using the device installation list. After binding, the gateway host calls the interface provided by the SDK to inform the IoT platform to proxy the sub-device. This application reduces manual intervention by obtaining the device installation list from the server to complete batch network configuration of sub-devices, simplifying the network configuration operation.

[0012] Optionally, the configuration of the gateway host access server may further include:

[0013] Create project information for the items to be assembled;

[0014] Based on the project information, configure the first proposed equipment for the project to be assembled;

[0015] Generate an equipment installation list based on the first proposed equipment;

[0016] The equipment installation list is stored on the server.

[0017] By adopting the above technical solution, the project name, unit type, and space (house organization structure) information are first created based on the actual situation of the project to be installed. Before the project enters the site, the configuration of the first proposed equipment (including gateway host, various sub-device types, sub-device names, sub-device scenarios, and related interactions) can be completed on the IoT cloud server based on the relevant project information; then, an equipment installation list is generated based on the first proposed equipment and saved on the server.

[0018] Optionally, the configuration of the gateway host access server may further include:

[0019] Create project information for the items to be assembled;

[0020] In response to the assembly request of the item to be assembled, the project information is sent to the engineering client;

[0021] Receive the unique device identifier uploaded by the engineering client based on the project information;

[0022] The second proposed equipment for the project to be assembled is identified based on the unique identifier of the equipment.

[0023] Generate an equipment installation list based on the second proposed equipment;

[0024] The equipment installation list is stored on the server.

[0025] By adopting the above technical solution, the project name, unit type, and space (building structure) information are first created based on the actual situation of the project to be installed. When the construction personnel arrive at the project site to install the equipment, the engineering client obtains the project information and uploads the unique device identifier (MAC address, serial number, etc.) of the IoT device actually used in the project by scanning the code. The IoT cloud server identifies the second proposed device based on the unique device identifier; then, an equipment installation list is generated based on the first proposed device and saved on the server.

[0026] Optionally, the configuration of the gateway host access server may further include:

[0027] Create project information for the items to be assembled;

[0028] Based on the project information, configure the first proposed equipment for the project to be assembled;

[0029] In response to the assembly request of the item to be assembled, the project information is sent to the engineering client;

[0030] Receive the unique device identifier uploaded by the engineering client based on the project information;

[0031] Based on the unique identifier of the equipment, the second proposed equipment for the project to be assembled is identified, and the first proposed equipment and the second proposed equipment are bound to each other in a one-to-one correspondence.

[0032] A list of equipment to be installed is generated based on the first and second proposed equipment.

[0033] The equipment installation list is stored on the server.

[0034] By adopting the above technical solution, some "virtual sub-devices" exist in the first proposed equipment, which only have sub-device type, sub-device name, and room to which they belong, but no relevant sub-device information (model, identification, and corresponding identity authentication information). Therefore, by binding the first proposed equipment and the second proposed equipment one-to-one, the "virtual sub-devices" in the first proposed equipment correspond to the "actual sub-devices" in the second proposed equipment, thereby enabling the subsequent network distribution to proceed smoothly.

[0035] Optionally, the gateway host binds the installed devices based on the device installation list, specifically including:

[0036] Determine whether the installed device is in the device installation list; if so, bind the gateway host to the installed device.

[0037] If not, the gateway host pushes the new device confirmation information to the engineering client through the server; in response to the engineering client confirming the new device within a preset time, the installed device is added to the device installation list.

[0038] By adopting the above technical solution, when the sub-device is powered on for the first time, the sub-devices in the device installation list can be bound to the gateway host in batches. Sub-devices not in the device installation list can be added to the device installation list and bound to the gateway host after confirmation by the commissioning personnel, reducing manual intervention.

[0039] Optionally, the server may include an IoT cloud server, a local server, or a debugging server.

[0040] By adopting the above technical solution, when the local machine can temporarily connect to the external network, it obtains the equipment installation list of the project to be assembled corresponding to the unique coding information from the IoT cloud server; when the local machine cannot temporarily connect to the external network, it downloads the equipment installation list of the project to be assembled from the IoT cloud server to the local machine, and then uploads the downloaded data to the local server or the debugging server. By connecting to the local server or the debugging server, it obtains the equipment installation list of the project to be assembled corresponding to the unique coding information from the local server or the debugging server.

[0041] Optional, also includes:

[0042] Receive acceptance information uploaded by the project client;

[0043] Based on the acceptance information and the equipment installation list, determine whether the project to be assembled has passed acceptance; if it has, change the project to be assembled to a completed project.

[0044] Secondly, this application provides an IoT batch distribution network system, which adopts the following technical solution:

[0045] An IoT batch distribution system includes:

[0046] Gateway host, used to connect to the server;

[0047] The server is used to send an equipment installation list of the items to be installed corresponding to the unique coding information to the gateway host based on the unique coding information of the gateway host.

[0048] The gateway host binds the installed devices based on the device installation list, and all the installed devices are automatically configured to the network through the gateway host.

[0049] Thirdly, this application provides a computer device that adopts the following technical solution:

[0050] A computer device includes a memory and a processor, wherein the memory stores a computer program that can be loaded by the processor and executed as in any of the methods described in the first aspect above.

[0051] Fourthly, this application provides a computationally readable storage medium, employing the following technical solution:

[0052] A computer-readable storage medium includes a computer program stored thereon that can be loaded by a processor and executed as in any of the methods described in the first aspect above.

[0053] In summary, this application includes at least the following beneficial effects:

[0054] Once the gateway host connects to the server, it retrieves a device installation list from the server corresponding to the unique code information of the sub-devices. This list includes the sub-device's model number, device identifier, and corresponding authentication information. When the gateway host finds a sub-device, it can confirm whether to bind it using the device installation list. After binding, the gateway host calls the interface provided by the SDK to inform the IoT platform to act as a proxy for the sub-device. This application completes batch network configuration of sub-devices by retrieving the device installation list from the server, reducing manual intervention and simplifying the network configuration operation. Attached Figure Description

[0055] Figure 1 This is a flowchart illustrating the method for batch network configuration of IoT devices in this application;

[0056] Figure 2 This is a flowchart illustrating one implementation method prior to step S201 of the IoT device batch network configuration method in this application;

[0057] Figure 3 This is a flowchart illustrating another implementation method prior to step S201 of the IoT device batch network configuration method in this application;

[0058] Figure 4 This is a flowchart illustrating another implementation method prior to step S201 of the method for batch network configuration of IoT devices in this application.

[0059] Figure 5 This is a flowchart illustrating a further implementation method following step S203 of the method for batch network configuration of IoT devices in this application.

[0060] Figure 6 This is a structural block diagram of the IoT device batch distribution network system of this application;

[0061] Explanation of the attached diagram labels: 1. Gateway host; 2. Server; 21. IoT cloud server; 3. Installed device; 4. Engineering client. Detailed Implementation

[0062] To make the purpose, technical solution, and advantages of this application clearer, the following description is provided in conjunction with the appendix. Figure 1-6 The present application will be further described in detail below with reference to embodiments. It should be understood that the specific embodiments described herein are only for explaining the present application and are not intended to limit the present application. All other embodiments obtained by those skilled in the art based on the embodiments in this application without inventive effort are within the scope of protection of this application.

[0063] This application provides a method for batch network configuration of IoT devices.

[0064] As attached Figure 1 As shown, a method for batch network configuration of IoT devices includes:

[0065] S201. Configure gateway host 1 to access server 2;

[0066] Specifically, server 2 can be IoT cloud server 21, local server 2, or debugging server 2. When connected to the external network, it obtains the device installation list of the project to be assembled corresponding to the unique coding information from IoT cloud server 21; when unable to connect to the external network, it downloads the device installation list of the project to be assembled from IoT cloud server 21 to the local machine, and then uploads the downloaded data to local server 2 or debugging server 2. By connecting to local server 2 or debugging server 2, it obtains the device installation list of the project to be assembled corresponding to the unique coding information from local server 2 or debugging server 2.

[0067] S202. Based on the unique coding information of gateway host 1, gateway host 1 obtains the equipment installation list of the items to be assembled from server 2, which corresponds to the unique coding information.

[0068] Specifically, the unique coding information of gateway host 1 can identify which project to be installed belongs to gateway host 1. After gateway host 1 connects to server 2, it obtains the equipment installation list of the project to be installed corresponding to the unique coding information from server 2 through the unique coding information of gateway host 1. The equipment installation list includes the model of the sub-device, the device identifier, and the corresponding identity authentication information.

[0069] S203, Gateway host 1 binds the installed device 3 based on the device installation list, and the installed device 3 is automatically configured to the network through gateway host 1.

[0070] Specifically, when gateway host 1 detects a powered-on sub-device, it can confirm whether to bind the sub-device through the device installation list. This includes: determining whether the installed device 3 is in the device installation list; if so, gateway host 1 binds with the installed device 3; if not, gateway host 1 pushes a confirmation message for the new device to engineering client 4 through server 2; in response to engineering client 4 confirming the new device within a preset time, the installed device 3 is added to the device installation list. After gateway host 1 and the sub-device are bound, gateway host 1 calls the interface provided by the SDK to inform the IoT platform to act as a proxy for the sub-device.

[0071] In this embodiment, the batch network configuration of sub-devices is completed by obtaining the equipment installation list from server 2, which reduces manual intervention and simplifies the network configuration operation of sub-devices.

[0072] As attached Figure 2 As shown, in one implementation of the method for batch network configuration of IoT devices, steps S101-S104 are included before step S201:

[0073] S101. Create project information for the project to be assembled;

[0074] Specifically, first create the project name, unit type, and space (house organization structure) information based on the actual situation of the project to be assembled.

[0075] S102. Based on project information, configure the first equipment to be installed for the project to be assembled.

[0076] Specifically, after determining the relevant project information, the configuration of the first proposed device (including gateway host 1, various sub-device types, sub-device names, sub-device scenarios, related interactions, etc.) can be completed on the IOT cloud server 21. The first proposed device can be manually configured by engineering technicians based on the project's apartment type and requirements, combined with their experience; or it can be automatically configured using preset templates. The IOT cloud server 21 stores templates corresponding to various apartment types. Once the apartment type of the project to be installed is known, the first proposed device required for that apartment type can be automatically generated based on the template. The same apartment type in the same project can achieve batch and rapid completion of device installation and debugging through this technology.

[0077] S103. Generate an equipment installation list based on the first proposed equipment;

[0078] S104. Save the equipment installation list in server 2.

[0079] As attached Figure 3 As shown, as another implementation of the method for batch network configuration of IoT devices, steps S111-S115 are included before step S201:

[0080] S111, Create project information for the project to be assembled;

[0081] S112. In response to the assembly request of the project to be assembled, send project information to the engineering client 4;

[0082] Specifically, when construction workers arrive at the site of the project to be assembled to install the equipment, they obtain the project information of the project to be assembled from the IoT cloud server 21 through the engineering client 4, and then upload the unique device identifier (MAC address, serial number, etc.) of the IoT device actually used in the project by scanning the code.

[0083] S113. Receive the unique device identifier uploaded by the engineering client 4 based on project information;

[0084] Specifically, the engineering client 4 scans the QR code on the IoT device to obtain the device's unique identifier and uploads it to the IoT cloud server 21.

[0085] S114. Identify the second equipment to be installed for the project to be assembled based on the unique equipment identifier;

[0086] Specifically, the IoT cloud server 21 stores the unique device identifiers of each IoT device, which enables the identification of the second device to be installed.

[0087] S115. Generate an equipment installation list based on the second proposed equipment;

[0088] S116. Save the equipment installation list in server 2.

[0089] As attached Figure 4 As shown, in another implementation of the method for batch network configuration of IoT devices, steps S121-S127 are included before step S201:

[0090] S121. Create project information for the project to be assembled;

[0091] S122. Based on project information, configure the first proposed equipment for the project to be assembled;

[0092] S123. In response to the assembly request of the item to be assembled, send the project information to the engineering client 4.

[0093] S124. Receive the unique device identifier uploaded by the engineering client 4 based on project information;

[0094] S125. Identify the second proposed equipment for the project to be assembled based on the unique equipment identifier, and bind the first proposed equipment and the second proposed equipment to each other in a one-to-one correspondence.

[0095] S126. Generate an equipment installation list based on the first proposed equipment and the second proposed equipment;

[0096] S127. Save the equipment installation list in server 2.

[0097] In this embodiment, some of the first proposed equipment consists of "virtual sub-devices" that only have sub-device type, sub-device name, and room to which they belong, but lack relevant sub-device information (model, identifier, and corresponding identity authentication information). Therefore, by binding the first proposed equipment to the second proposed equipment one-to-one, the "virtual sub-devices" in the first proposed equipment correspond to the "actual sub-devices" in the second proposed equipment, thereby enabling the subsequent network distribution to proceed smoothly.

[0098] In this embodiment, when a sub-device is powered on for the first time, sub-devices in the device installation list can be bound to the gateway host 1 in batches. Sub-devices not in the device installation list can be added to the device installation list and bound to the gateway host 1 after confirmation by the commissioning personnel, reducing manual intervention.

[0099] As attached Figure 5 As shown, a further implementation of the method for batch network configuration of IoT devices also includes:

[0100] S301, Receive acceptance information uploaded by engineering client 4;

[0101] Specifically, after the sub-devices are added to the network, the commissioning personnel verify and check each function according to the equipment installation list to ensure that it is normal. After confirming that there are no problems, they take photos through the engineering client 4 and upload them to the IoT cloud server 21.

[0102] S302. Based on the acceptance information and equipment installation list, determine whether the project to be assembled has passed the acceptance test; if it has, change the project to be assembled to a completed project.

[0103] Specifically, when all IoT devices in the equipment installation list have corresponding acceptance information, the project to be installed is considered to have passed acceptance. The IOT cloud server 21 will then change the project to be installed to a completed project. When the owner moves in, they can register an account through the user client and scan the QR code on the smart gateway to complete the binding process.

[0104] As shown in the attached figure, this application provides an IoT batch distribution system.

[0105] As attached Figure 6 As shown, an IoT batch distribution network system includes:

[0106] Gateway host 1 is used to connect to server 2;

[0107] Server 2 is used to send a list of equipment to be installed for the items corresponding to the unique coding information to gateway host 1, based on the unique coding information of gateway host 1.

[0108] Gateway host 1 binds to the installed device 3 based on the device installation list, and all installed devices 3 are automatically configured to the network through gateway host 1.

[0109] Also includes:

[0110] IoT cloud server 21 is used to generate a device installation list;

[0111] Engineering Client 4 is used for the unique device identifier of IoT devices and for uploading acceptance information.

[0112] This application provides a computer device.

[0113] A computer device includes a memory and a processor, wherein the memory stores a computer program that can be loaded by the processor and executed as in any of the methods described in the first aspect above.

[0114] This application provides a computationally readable storage medium.

[0115] A computer-readable storage medium includes a computer program stored thereon that can be loaded by a processor and executed as in any of the methods described in the first aspect above.

[0116] It should be noted that the descriptions of each embodiment in the above embodiments have different focuses. For parts not described in detail in a certain embodiment, please refer to the relevant descriptions in other embodiments.

[0117] It should be understood that, for the sake of convenience and brevity, the above division of functional units and modules is used as an example. In actual applications, the above functions can be assigned to different functional units and modules as needed, that is, the internal structure of the system can be divided into different functional units or modules to complete all or part of the functions described above.

[0118] The above are all preferred embodiments of this application, and are not intended to limit the scope of protection of this application. Therefore, all equivalent changes made in accordance with the structure, shape and principle of this application should be covered within the scope of protection of this application.

Claims

1. A method for batch network configuration of Internet of Things (IoT) devices, characterized in that, include: Configure the gateway host (1) to access the server (2); Based on the unique coding information of the gateway host (1), the gateway host (1) obtains from the server (2) the equipment installation list of the items to be assembled corresponding to the unique coding information; The gateway host (1) binds the installed devices (3) based on the device installation list, and all the installed devices (3) are automatically configured through the gateway host (1); The gateway host (1) binds the installed device (3) based on the device installation list, specifically including: Determine whether the installed device (3) is in the device installation list; if so, the gateway host (1) is bound to the installed device (3); If not, the gateway host (1) pushes the new device confirmation information to the engineering client (4) through the server (2); in response to the engineering client (4) confirming the new device within a preset time, the installed device (3) is added to the device installation list. After the gateway host (1) and the sub-device are bound, the gateway host (1) calls the interface provided by the SDK to inform the IoT platform to proxy the sub-device.

2. The method for batch network configuration of IoT devices according to claim 1, characterized in that, The configuration of the gateway host (1) accessing the server (2) also includes, prior to: Create project information for the items to be assembled; Based on the project information, configure the first proposed equipment for the project to be assembled; Generate an equipment installation list based on the first proposed equipment; The equipment installation list is stored in the server (2).

3. The method for batch network configuration of IoT devices according to claim 1, characterized in that, The configuration of the gateway host (1) accessing the server (2) also includes, prior to: Create project information for the items to be assembled; In response to the assembly request of the item to be assembled, the project information is sent to the engineering client (4); Receive the unique device identifier uploaded by the engineering client (4) based on the project information; The second proposed equipment for the project to be assembled is identified based on the unique identifier of the equipment. Generate an equipment installation list based on the second proposed equipment; The equipment installation list is stored in the server (2).

4. The method for batch network configuration of IoT devices according to claim 1, characterized in that, The configuration of the gateway host (1) accessing the server (2) also includes, prior to: Create project information for the items to be assembled; Based on the project information, configure the first proposed equipment for the project to be assembled; In response to the assembly request of the item to be assembled, the project information is sent to the engineering client (4); Receive the unique device identifier uploaded by the engineering client (4) based on the project information; Based on the unique identifier of the equipment, the second proposed equipment for the project to be assembled is identified, and the first proposed equipment and the second proposed equipment are bound to each other in a one-to-one correspondence. A list of equipment to be installed is generated based on the first and second proposed equipment. The equipment installation list is stored in the server (2).

5. A method for batch network configuration of IoT devices according to any one of claims 1-4, characterized in that: The server (2) includes an IoT cloud server (21), a local server (2), or a debugging server (2).

6. The method for batch network configuration of IoT devices according to claim 1, characterized in that, Also includes: Receive acceptance information uploaded by the engineering client (4); Based on the acceptance information and the equipment installation list, determine whether the project to be assembled has passed acceptance; If approved, the item to be assembled will be changed to a completed item.

7. An IoT batch distribution network system, characterized in that, A method for batch network configuration of IoT devices according to any one of claims 1 to 6 includes: Gateway host (1) is used to connect to server (2); The server (2) is used to send a list of equipment to be installed for the project corresponding to the unique coding information to the gateway host (1) based on the unique coding information of the gateway host (1); The gateway host (1) binds the installed devices (3) based on the device installation list, and all the installed devices (3) are automatically configured through the gateway host (1).

8. A computer device, characterized in that: It includes a memory and a processor, wherein the memory stores a computer program that can be loaded by the processor and executed as in any one of claims 1-6 above.

9. A computer-readable storage medium, characterized in that: This includes storing a computer program that can be loaded by a processor and executed using any one of the methods described in claims 1-6.

Images