Device network configuration system, method, related device and storage medium

Through scanning of terminal devices and Bluetooth Mesh gateways, unallocated devices were found, distribution information tables were generated, and cloud servers were used to coordinate various Provisioners for batch distribution networking, solving the problem of long distribution time when large-scale Bluetooth Mesh devices are powered on at the same time, and improving distribution network efficiency.

CN115442872BActive Publication Date: 2025-08-05ZHEJIANG MAOJING ARTIFICIAL INTELLIGENCE TECH CO LTD
View PDF 1 Cites 0 Cited by

Patent Information

Application Number
CN202210977304.8
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2022-08-15
Publication Date
2025-08-05
Estimated Expiration
2042-08-15

AI Technical Summary

Technical Problem

In the prior art, when large-scale Bluetooth Mesh devices are powered on at the same time, the distribution network time is longer, and the distribution network efficiency needs to be improved.

Method used

Scan the terminal device and Bluetooth Mesh gateway to find unconfigured devices, generate distribution information tables, and use cloud servers to coordinate various Provisioners for batch distribution networking.

Benefits of technology

The batch distribution network of undistributed equipment has been realized, effectively reducing the distribution network time and improving the efficiency of equipment distribution network.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN115442872B_ABST
    Figure CN115442872B_ABST
Patent Text Reader

Abstract

The embodiment of the present application provides a device network configuration system, method, related equipment and storage medium, wherein the system includes: a terminal device, a Bluetooth Mesh gateway and a cloud server. The terminal device is used to execute the device discovery instruction to scan and discover unconfigured devices, and send the scan results to the cloud server; obtain the network configuration information table fed back by the cloud server, and schedule each Provisioner to perform network configuration for the corresponding unconfigured devices according to the network configuration information table. The Bluetooth Mesh gateway is used to obtain the device discovery instruction conveyed by the cloud server to scan and discover unconfigured devices, and send the scan results to the cloud server; and when the Bluetooth Mesh gateway is the Provisioner that performs network configuration, it is scheduled by the terminal device to perform network configuration for the corresponding unconfigured devices. The cloud server is used to generate a network configuration information table based on the scan results of the terminal device and the Bluetooth Mesh gateway and send it to the terminal device. The embodiment of the present application can realize batch network configuration of devices, shorten the network configuration time, and improve network configuration efficiency.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The embodiments of the present application relate to the field of communication technology, and specifically to a device network configuration system, method, related devices, and storage medium. Background Art

[0002] Bluetooth Mesh (wireless mesh) networks are mesh networks that establish inter-device communication based on Bluetooth Low Energy (BLE). They are widely used in intelligent connected scenarios such as smart homes and smart offices. After powering on, if Bluetooth Mesh devices are not in the provisioned state, provisioning is required to join the Bluetooth Mesh network. In this context, batch provisioning of unprovisioned Bluetooth Mesh devices is crucial to shorten provisioning time and improve provisioning efficiency. Summary of the Invention

[0003] In view of this, the embodiments of the present application provide a device configuration system, method, related equipment and storage medium to implement batch configuration of unconfigured Bluetooth Mesh devices, shorten the configuration time of Bluetooth Mesh devices, and improve configuration efficiency.

[0004] To achieve the above objectives, the embodiments of the present application provide the following technical solutions.

[0005] In a first aspect, an embodiment of the present application provides a device network configuration system, comprising: a terminal device, a Bluetooth Mesh gateway, and a cloud server;

[0006] The terminal device is configured to execute a device discovery instruction to scan and discover unprovisioned devices; send the scan results to the cloud server; obtain a network configuration information table fed back by the cloud server, the network configuration information table being used to indicate a correspondence between provisioners and unprovisioned devices, wherein a provisioner performs network configuration for the corresponding unprovisioned device, and one provisioner corresponds to at least one unprovisioned device, the provisioner including a terminal device and / or a Bluetooth Mesh gateway; and, based on the network configuration information table, schedule each provisioner to perform network configuration for the corresponding unprovisioned device;

[0007] The Bluetooth Mesh gateway is configured to obtain a device discovery instruction from the terminal device conveyed by the cloud server to scan and discover unprovisioned devices; send the scan results to the cloud server; and, when the Bluetooth Mesh gateway is the provisioner performing network provisioning, be dispatched by the terminal device to perform network provisioning for the corresponding unprovisioned device;

[0008] The cloud server is used to obtain the scanning results of the terminal device and the scanning results of the Bluetooth Mesh gateway; generate a network configuration information table based on the scanning results of the terminal device and the scanning results of the Bluetooth Mesh gateway; and send the network configuration information table to the terminal device.

[0009] In a second aspect, an embodiment of the present application provides a device network configuration method, which is applied to a terminal device, including:

[0010] Execute device discovery commands to scan and discover unconfigured devices;

[0011] Sending the scanning result of the terminal device to the cloud server;

[0012] Obtaining a network configuration information table sent by the cloud server; the network configuration information table is used to indicate the correspondence between the Provisioner and the unprovisioned device, wherein the Provisioner performs network configuration for the corresponding unprovisioned device, and one Provisioner corresponds to at least one unprovisioned device, and the Provisioner includes a terminal device and / or a Bluetooth Mesh gateway;

[0013] According to the network configuration information table, each Provisioner is scheduled to perform network configuration for the corresponding unconfigured device.

[0014] In a third aspect, an embodiment of the present application provides a device network configuration method, which is applied to a cloud server, comprising:

[0015] Obtain the scan results of the terminal device scanning for unprovisioned devices, and the scan results of the Bluetooth Mesh gateway scanning for unprovisioned devices;

[0016] Generate a network configuration information table based on the scan results of the terminal device and the scan results of the Bluetooth Mesh gateway; the network configuration information table is used to indicate the correspondence between the Provisioner and the unprovisioned device, wherein the Provisioner performs network configuration for the corresponding unprovisioned device, and one Provisioner corresponds to at least one unprovisioned device, and the Provisioner includes the terminal device and / or the Bluetooth Mesh gateway;

[0017] Send the network configuration information table to the terminal device.

[0018] In a fourth aspect, an embodiment of the present application provides a terminal device comprising at least one memory and at least one processor, wherein the memory stores one or more computer-executable instructions, and the processor calls the one or more computer-executable instructions to execute the device network configuration method described in the second aspect above.

[0019] In a fifth aspect, an embodiment of the present application provides a cloud server comprising at least one memory and at least one processor, wherein the memory stores one or more computer-executable instructions, and the processor calls the one or more computer-executable instructions to execute the device network configuration method as described in the third aspect above.

[0020] In a sixth aspect, an embodiment of the present application provides a storage medium, which stores one or more computer-executable instructions. When the one or more computer-executable instructions are executed, the device network configuration method as described in the second aspect above, or the device network configuration method as described in the third aspect above, is implemented.

[0021] In a seventh aspect, an embodiment of the present application provides a computer program, which, when executed, implements the device network configuration method as described in the second aspect above, or the device network configuration method as described in the third aspect above.

[0022] The device network configuration system provided in the embodiment of the present application can execute a device discovery instruction through a terminal device to scan and discover unprovisioned devices and send the scan results to the cloud server; at the same time, the Bluetooth Mesh gateway can obtain the device discovery instruction of the terminal device conveyed by the cloud server to scan and discover unprovisioned devices and send the scan results to the cloud server; further, the cloud server can obtain the scan results of the terminal device and the scan results of the Bluetooth Mesh gateway, generate a network configuration information table based on the scan results of the terminal device and the scan results of the Bluetooth Mesh gateway, and send the network configuration information table to the terminal device. In the embodiment of the present application, the network configuration information table is used to indicate the correspondence between the provisioner and the unprovisioned device, wherein the provisioner performs network configuration for the corresponding unprovisioned device, and one provisioner corresponds to at least one unprovisioned device, and the provisioner includes the terminal device and / or the Bluetooth Mesh gateway. Based on the indication content of the network configuration information table, after obtaining the network configuration information table, the terminal device can schedule each provisioner to perform network configuration for the corresponding unprovisioned device according to the network configuration information table, thereby realizing batch configuration of unprovisioned devices.

[0023] It can be seen that in the device discovery phase, the embodiment of the present application can scan and discover unprovisioned devices through the terminal device and the Bluetooth Mesh gateway, and send the scan results to the cloud server. Then, the cloud server can generate a network configuration information table based on the scan results of the terminal device and the Bluetooth Mesh gateway, and send the network configuration information table to the terminal device. Then, in the network configuration execution phase, the terminal device can schedule each Provisioner to perform network configuration for the corresponding unprovisioned device based on the network configuration information table. It can be seen that the embodiment of the present application can use each Provisioner in the Bluetooth Mesh network to perform parallel network configuration, thereby realizing batch network configuration of unprovisioned devices, which can effectively reduce network configuration time and improve device network configuration efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0024] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are merely embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on the provided drawings without any creative work.

[0025] Figure 1A This is an example diagram of a Bluetooth Mesh network.

[0026] Figure 1B This is an example diagram of the stages of the device network configuration process.

[0027] Figure 1C This is an example diagram of an optional distribution network.

[0028] Figure 2 This is a schematic diagram of an optional architecture of the device distribution network system provided in an embodiment of the present application.

[0029] Figure 3 This is an optional signaling flow chart of the device network configuration method provided in an embodiment of the present application.

[0030] Figure 4 This is an optional example diagram of the device discovery page provided in an embodiment of the present application.

[0031] Figure 5 This is an optional flowchart of the device network configuration method provided in an embodiment of the present application.

[0032] Figure 6 This is another optional flowchart of the device network configuration method provided in the embodiment of the present application.

[0033] Figure 7 This is another optional flowchart of the device network configuration method provided in the embodiment of the present application.

[0034] Figure 8This is an optional example diagram of each Provisioner discovering an unprovisioned device provided in an embodiment of the present application.

[0035] Figure 9 This is an optional block diagram of the equipment network distribution device provided in an embodiment of the present application.

[0036] Figure 10 It is an optional block diagram of the terminal equipment.

[0037] Figure 11 This is another optional block diagram of the equipment network distribution device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0038] The following will be combined with the drawings in the embodiments of this application to clearly and completely describe the technical solutions in the embodiments of this application. Obviously, the embodiments described are only part of the embodiments of this application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.

[0039] Figure 1A An example diagram of a Bluetooth Mesh network is shown as follows: Figure 1A As shown, the Bluetooth Mesh network may include: multiple node devices 101 that have been configured. Figure 1A In the figure, the Provisioner (provisioning device) 102 acts as a control device, connecting an unprovisioned device 103 to the Bluetooth Mesh network through the device provisioning process. It will be appreciated that once the unprovisioned device 103 is connected to the Bluetooth Mesh network, it becomes a node in the Bluetooth Mesh network, allowing users to securely control the node devices in the Bluetooth Mesh network. In a possible implementation, the Provisioner can be, for example, a Bluetooth Mesh gateway or terminal device.

[0040] Figure 1B The diagram shows an example of the stages of the device network configuration process. Provisioner can Figure 1B In the example stage, unprovisioned devices are connected to the Bluetooth Mesh network. Figure 1B As shown, the device network configuration process may include the following stages: a device discovery stage 111 and a network configuration execution stage 112 .

[0041] In the device discovery phase 111, after the unprovisioned device is powered on, it can periodically broadcast an unprovisioned broadcast packet for the Provisioner to discover the unprovisioned device. In some embodiments, after the unprovisioned device is powered on, it can broadcast an Unprovisioned Device Beacon (unprovisioned device broadcast beacon) broadcast packet and a PB (Provisioning Bearer, provisioning bearer mode)-GATT (Generic Attribute Profile) broadcast packet. In one example, if the Provisioner selects a terminal device, the terminal device can obtain the PB-GATT broadcast packet broadcast by the unprovisioned device after the unprovisioned device is powered on, that is, scan the PB-GATT broadcast packet broadcast by the unprovisioned device; if the Provisioner selects a Bluetooth Mesh gateway, the Bluetooth Mesh gateway can obtain the Unprovisioned Device Beacon broadcast packet broadcast by the unprovisioned device after the unprovisioned device is powered on, that is, scan the Unprovisioned Device Beacon broadcast packet broadcast by the unprovisioned device.

[0042] In the network configuration execution phase 112, the Provisioner may perform device authentication, network configuration, and other processes on the discovered unprovisioned devices, thereby connecting the unprovisioned devices to the Bluetooth Mesh network. For example, after discovering the unprovisioned devices, the Provisioner may interact with the cloud server and perform device authentication, network configuration, and other processes on the unprovisioned devices based on the scanned broadcast packet information, thereby connecting the unprovisioned devices to the Bluetooth Mesh network. The cloud server referred to in the embodiments of the present application may be a cloud service platform that provides Bluetooth Mesh management services, such as a cloud computing platform that provides intelligent interconnection services for devices such as smart homes and smart offices, an IoT (Internet of Things) cloud platform, and the like.

[0043] However, the number of Bluetooth Mesh devices in a large-scale Bluetooth Mesh network can be hundreds. After the Bluetooth Mesh devices are powered on at the same time, network provisioning operations need to be performed on a large number of unprovisioned devices.

[0044] In one example, ZigBee communication technology is used to reuse the network connection architecture of the ZigBee gateway and sub-devices, so that all devices in the Bluetooth Mesh network can communicate with other devices in the same network. Based on the topological binding relationship between the Bluetooth Mesh node and the Bluetooth Mesh gateway, the Bluetooth Mesh node can be used as a proxy node, wherein unprovisioned devices can be provisioned only by the terminal device or only by the Bluetooth Mesh gateway. When the terminal device configures the unprovisioned device, the terminal device only establishes a GATT connection with one of the multiple unprovisioned devices. The device that establishes the GATT connection acts as a proxy node to forward the network invitation PDU (Protocol Data Unit) to other devices to implement network configuration for the device. Although this method can achieve network provisioning for multiple unprovisioned devices, in essence, it is still a provisioner (terminal device or Bluetooth Mesh gateway) that configures all unprovisioned devices. The average batch provisioning time for a single device is 2.8 seconds to 3 seconds. For the situation where a large number of Bluetooth Mesh devices are powered on at the same time, the provisioning time is long and the provisioning efficiency needs to be improved.

[0045] In another example, each network-provisioned device is used as a temporary provisioner, and the unicast address segments sent by the cloud server are assigned to the temporary provisioner, and the temporary provisioner configures the network for other unprovisioned devices, such as Figure 1C An example diagram of an optional network configuration is shown, in which the central network configuration device is a provisioner (terminal device or Bluetooth Mesh gateway). After the central network configuration device configures devices A and B, devices A and B can act as first-level temporary provisioners to configure devices A1, A2, ..., Ax and B1, B2, ..., Bx respectively. Thus, devices A1, A2, ..., Ax and B1, B2, ..., Bx can act as second-level temporary provisioners to configure lower-level devices, and so on. Although this method can proxy network provisioning layer by layer, using multiple provisioned devices as temporary provisioners to perform parallel provisioning on multiple unprovisioned devices, effectively shortening the network provisioning time, the temporary provisioner cannot complete the network provisioning independently. For example, the temporary provisioner needs to authenticate the unprovisioned devices with the cloud server through the provisioner (such as the Bluetooth Mesh gateway). However, if the temporary provisioner authenticates the unprovisioned devices with the cloud server through the provisioner (such as the Bluetooth Mesh gateway), the network provisioning time will be significantly increased, and the effect of shortening the network provisioning time will not be achieved.

[0046] It can be seen that when unprovisioned devices in a large-scale Bluetooth Mesh network are powered on at the same time, it is particularly important to realize batch configuration of unprovisioned devices and shorten the configuration time of unprovisioned devices. Based on this, the embodiment of the present application uses an improved technical solution. In the device discovery phase, the terminal device and the Bluetooth Mesh gateway are used to scan and discover unprovisioned devices, and the scan results are sent to the cloud server; thereby, the cloud server can generate a configuration information table based on the scan results of the terminal device and the Bluetooth Mesh gateway, and send the configuration information table to the terminal device; and then in the configuration execution phase, the terminal device can schedule each Provisioner (such as multiple Bluetooth Mesh gateways and terminal devices) according to the configuration information table to execute configuration for the unprovisioned devices corresponding to each Provisioner, so as to realize batch configuration of unprovisioned devices, effectively reduce the configuration time, and improve the efficiency of device configuration.

[0047] Based on the above ideas, Figure 2 The schematic diagram of the architecture of the device distribution network system provided by the embodiment of the present application is shown as an example. Figure 2 As shown, the device network configuration system may include: a terminal device 20, a Bluetooth Mesh gateway 21 and a cloud server 22.

[0048] The terminal device 20 can directly interact with the cloud server 22 and act as a provisioner to perform network provisioning for unprovisioned devices. The Bluetooth Mesh gateway 21 can directly interact with the cloud server 22 and act as a provisioner to perform network provisioning for unprovisioned devices.

[0049] As a cloud service platform for Bluetooth Mesh management services, the cloud server 22 can aggregate and process the information of Bluetooth Mesh devices (including information of network-connected devices and information of unconnected devices).

[0050] As an optional implementation, terminal devices may include, but are not limited to, user devices such as mobile phones, tablets, or computers, which can provide interactive interfaces such as a device discovery page and a page for adding and binding devices. As user-operated devices, terminal devices can scan for and discover unprovisioned devices and perform network provisioning on them. Optionally, terminal devices can interact with cloud servers via an app. This app can be an application for Bluetooth Mesh management, such as an app that provides intelligent device connectivity services for smart homes and smart offices.

[0051] As an optional implementation, the Bluetooth Mesh gateway can be, for example, a smart speaker or multi-mode gateway with Bluetooth communication capabilities and Internet connection capabilities. In addition to the configuration and control functions of node devices, the Bluetooth Mesh gateway can also serve as a springboard for connecting node devices to the Internet to achieve remote control of node devices.

[0052] In the process of adding an unprovisioned device to a Bluetooth Mesh network, the Bluetooth Mesh gateway or terminal device that performs provisioning can be called a provisioner.

[0053] The following describes in detail the device network configuration scheme of the embodiment of the present application based on the device network configuration system architecture described above.

[0054] Figure 3 The following is an exemplary diagram of an optional signaling flow chart of a device network configuration method provided by an embodiment of the present application. The method flow can be as follows: Figure 2 The terminal devices, cloud servers, and Bluetooth Mesh gateways in the device distribution network system are implemented as shown. Figure 3 As shown, the method flow may include the following steps.

[0055] Step S30: The terminal device executes a device discovery instruction to scan and discover unconfigured devices.

[0056] A Bluetooth Mesh device can be in a state where it is waiting to be provisioned. For example, after a newly manufactured Bluetooth Mesh device is powered on, it can periodically send unprovisioned advertising packets to allow the Provisioner to discover the unprovisioned device.

[0057] As a user-operated device, the terminal device can initiate the device discovery process under user operation. For example, the user can perform the device discovery operation through the device scanning page provided by the terminal device, thereby scanning for unprovisioned devices in the Bluetooth Mesh network.

[0058] In step S31, the terminal device sends the scanning result to the cloud server.

[0059] When the terminal device scans and finds an unconnected device, it can obtain the corresponding scan result and send the scan result to the cloud server so that the cloud server can obtain the scan result of the terminal device.

[0060] In step S32, the Bluetooth Mesh gateway obtains the device discovery instruction of the terminal device conveyed by the cloud server to scan and discover unconnected devices.

[0061] The terminal device has a certain signal range and cannot scan and discover unprovisioned devices outside its signal range. Therefore, in order to discover as many unprovisioned devices as possible in the surrounding area that have not yet joined the Bluetooth Mesh network, when the terminal device executes the device discovery instruction and scans and discovers unprovisioned devices, the terminal device can convey the device discovery instruction to the Bluetooth Mesh gateway through the cloud server; then, the Bluetooth Mesh gateway can obtain the device discovery instruction of the terminal device conveyed by the cloud server and execute the device discovery instruction to scan and discover unprovisioned devices. Based on the scanning results of the terminal device and the scanning results of the Bluetooth Mesh gateway, the embodiment of the present application can discover as many unprovisioned devices as possible in the surrounding area.

[0062] In step S33, the Bluetooth Mesh gateway sends the scanning result to the cloud server.

[0063] In step S34, the cloud server obtains the scanning result of the terminal device and the scanning result of the Bluetooth Mesh gateway.

[0064] As an optional implementation, during the device discovery phase, the terminal device may poll the cloud server for the discovery results of unconfigured devices. The discovery results may be the results of combining the scan results of the terminal device and the Bluetooth Mesh gateway, such as the number of unconfigured devices after combining the scan results of the terminal device and the Bluetooth Mesh gateway. In an implementation example, the cloud server may summarize the number of unconfigured devices scanned by the terminal device and the Bluetooth Mesh gateway based on the scan results of the terminal device and the scan results of the Bluetooth Mesh gateway, and send it to the terminal device, so that the terminal device can display the number of unconfigured devices (an example of the discovery results) in real time on the device discovery page. Thus, the user can understand the current situation of unconfigured devices from the content displayed on the page.

[0065] In a specific example, the broadcast packet sent by the unprovisioned device will carry the device unique identifier such as DeviceUUID, so that when the terminal device and the Bluetooth Mesh gateway find the unprovisioned device, they can carry the device unique identifier of the unprovisioned device in the scanning result based on the device unique identifier in the broadcast packet of the unprovisioned device; after the cloud server obtains the scanning results of the terminal device and the unprovisioned device, it can determine the number of unprovisioned devices based on the device unique identifier of the unprovisioned device carried in the obtained scanning results. As an example, Figure 4 The following is an exemplary diagram showing an optional example of a device discovery page in an embodiment of the present application, such as Figure 4 As shown, the device discovery page can display the scanned unconfigured devices and the number of unconfigured devices (for example, 200 unconfigured smart lights).

[0066] In step S35, the cloud server generates a network configuration information table according to the scanning result of the terminal device and the scanning result of the Bluetooth Mesh gateway.

[0067] As a Bluetooth Mesh management platform, the cloud server can determine the network configuration capabilities of each Provisioner based on the scan results of the terminal device and the scan results of the Bluetooth Mesh gateway, thereby allocating corresponding unconfigured devices to each Provisioner. As an optional implementation, after obtaining the scan results of the terminal device and the scan results of the Bluetooth Mesh gateway, the cloud server can determine the network configuration capabilities of each Provisioner based on the scan results of the terminal device and the scan results of the Bluetooth Mesh gateway, and allocate unconfigured devices to each Provisioner when the terminal device and the Bluetooth Mesh device are the Provisioners performing network configuration, thereby generating a network configuration information table. The network configuration information table can indicate the corresponding relationship between the Provisioner and the unconfigured device. Among them, the Provisioner can perform network configuration for the corresponding unconfigured device, and one Provisioner corresponds to at least one unconfigured device. The Provisioner can include a terminal device and / or a Bluetooth Mesh gateway.

[0068] As an optional implementation, for any unprovisioned device, if the unprovisioned device is scanned and found within the signal range of the terminal device, but no unprovisioned device is scanned and found within the signal range of the Bluetooth Mesh gateway, the cloud server determines that the Provisioner that performs network provisioning for the unprovisioned device is the terminal device based on the scan results of the terminal device and the scan results of the Bluetooth Mesh gateway, and records it in the network provisioning information table;

[0069] As another optional implementation, for any unprovisioned device, if no unprovisioned device is scanned and found within the signal range of the terminal device, and no unprovisioned device is scanned and found within the signal range of the Bluetooth Mesh gateway, the cloud server determines that the provisioner performing network provisioning for the unprovisioned device is the Bluetooth Mesh gateway based on the scan results of the terminal device and the scan results of the Bluetooth Mesh gateway, and records it in the network provisioning information table;

[0070] As another optional implementation, for any unprovisioned device, if the unprovisioned device is scanned and found within the signal range of the terminal device, and the unprovisioned device is also scanned and found within the signal range of the Bluetooth Mesh gateway, the cloud server determines the Provisioner that performs network provisioning for the unprovisioned device based on the scan results of the terminal device and the scan results of the Bluetooth Mesh gateway, and records the result in the network provisioning information table. For example, if the scan results include the signal strength of the node device, and the signal strength corresponding to the unprovisioned device in the scan result of the terminal device is 1, and the signal strength corresponding to the unprovisioned device in the scan result of the Bluetooth Mesh gateway is 2, then the Provisioner that performs network provisioning for the unprovisioned device is determined to be the Bluetooth Mesh gateway, and the result is recorded in the network provisioning information table. If the signal strengths of the node device in the scan results are the same, the node device can be assigned to the terminal device and the Bluetooth Mesh gateway based on the number of devices to be provisioned already allocated in the network provisioning information table. The node device is then assigned to the party with the fewer devices to be provisioned, and the result is recorded in the network provisioning information table.

[0071] Step S36: The cloud server sends the network configuration information table to the terminal device.

[0072] The terminal device, as a user-operated device, can manage the network configuration. After generating the network configuration information table, the cloud server can send the network configuration information table to the terminal device so that the terminal device performs the next operation according to the network configuration information table.

[0073] Step S37: The terminal device obtains the network configuration information table fed back by the cloud server.

[0074] The network configuration information table is used to indicate the correspondence between the Provisioner and the unprovisioned device, wherein the Provisioner performs network configuration for the corresponding unprovisioned device, and one Provisioner corresponds to at least one unprovisioned device, and the Provisioner includes a terminal device and / or a Bluetooth Mesh gateway.

[0075] In step S38, the terminal device schedules each Provisioner to perform network configuration for the corresponding unconfigured device according to the network configuration information table.

[0076] In this embodiment of the present application, the terminal device has the authority to schedule each provisioner to perform network configuration. Therefore, the terminal device can schedule each provisioner to perform network configuration for the corresponding unprovisioned devices based on the unprovisioned devices assigned by each provisioner as recorded in the network configuration information table. For example, when a Bluetooth Mesh gateway is the provisioner performing network configuration, the Bluetooth Mesh gateway can perform network configuration for the corresponding unprovisioned devices under the scheduling of the terminal device.

[0077] It should be noted that the terminal device and the Bluetooth Mesh gateway, as Provisioners, can interact directly with the cloud server. Therefore, when the Provisioner (terminal device and / or Bluetooth Mesh gateway) performs network configuration for the corresponding unprovisioned device, it can directly interact with the cloud server to authenticate the unprovisioned device. Based on this, when the terminal device schedules each Provisioner to perform network configuration for the corresponding unprovisioned device according to the network configuration information table, each Provisioner can directly interact with the cloud server to authenticate the corresponding unprovisioned device during the network configuration process, thereby effectively shortening the network configuration time.

[0078] The device network configuration system provided in the embodiment of the present application can execute a device discovery instruction through a terminal device to scan and discover unprovisioned devices and send the scan results to the cloud server; at the same time, the Bluetooth Mesh gateway can obtain the device discovery instruction of the terminal device conveyed by the cloud server to scan and discover unprovisioned devices and send the scan results to the cloud server; furthermore, the cloud server can obtain the scan results of the terminal device and the scan results of the Bluetooth Mesh gateway, generate a network configuration information table based on the scan results of the terminal device and the scan results of the Bluetooth Mesh gateway, and send the network configuration information table to the terminal device. In the embodiment of the present application, the network configuration information table is used to indicate the correspondence between the Provisioner and the unprovisioned device, wherein the Provisioner performs network configuration for the corresponding unprovisioned device, and one Provisioner corresponds to at least one unprovisioned device, and the Provisioner includes the terminal device and / or the Bluetooth Mesh gateway. Based on the indication content of the network configuration information table, after obtaining the network configuration information table, the terminal device can schedule each Provisioner to perform network configuration for the corresponding unprovisioned device according to the network configuration information table, thereby realizing batch configuration of unprovisioned devices.

[0079] It can be seen that in the device discovery phase, the embodiment of the present application can scan and discover unprovisioned devices through the terminal device and the Bluetooth Mesh gateway, and send the scan results to the cloud server. Then, the cloud server can generate a network configuration information table based on the scan results of the terminal device and the Bluetooth Mesh gateway, and send the network configuration information table to the terminal device. Then, in the network configuration execution phase, the terminal device can schedule each Provisioner to perform network configuration for the corresponding unprovisioned device based on the network configuration information table. It can be seen that the embodiment of the present application can use each Provisioner in the Bluetooth Mesh network to perform parallel network configuration, thereby realizing batch network configuration of unprovisioned devices, which can effectively reduce network configuration time and improve device network configuration efficiency.

[0080] In some embodiments, the terminal device and the Bluetooth Mesh gateway have a certain signal range, and the terminal device and the Bluetooth Mesh gateway can perform discovery scans on unprovisioned devices that appear within the signal range. Therefore, the scanning results of the terminal device may include the signal strength of the unprovisioned devices scanned by the terminal device, and the scanning results of the Bluetooth Mesh gateway may include the signal strength of the unprovisioned devices scanned by the Bluetooth Mesh gateway.

[0081] It can be understood that, in the process of generating the network configuration information table based on the scanning results of the terminal device and the scanning results of the Bluetooth Mesh gateway, the cloud server can assign a Provisioner to each unconfigured device based on the signal strength of the unconfigured device scanned by the terminal device and the signal strength of the unconfigured device scanned by the Bluetooth Mesh gateway, so as to establish a correspondence between the Provisioner and the unconfigured device, and record the correspondence in the network configuration information table.

[0082] In a further embodiment, the cloud server can determine the signal strength between each unprovisioned device and each Provisioner based on the signal strength of the unprovisioned device scanned by the terminal device and the signal strength of the unprovisioned device scanned by the Bluetooth Mesh gateway, and thus allocate a Provisioner to each unprovisioned device based on the signal strength relationship between each unprovisioned device and each Provisioner, and the number of unprovisioned devices allocated by each Provisioner.

[0083] Optionally, there are differences in signal strength between each unprovisioned device and each Provisioner. The cloud server can assign Provisioners to each unprovisioned device based on the signal strength relationship between each unprovisioned device and each Provisioner, as well as the number of unprovisioned devices assigned to each Provisioner. The principle can be: for any unprovisioned device, the unprovisioned device is assigned to the Provisioner with the largest signal strength; if there are multiple Provisioners with the largest signal strength for an unprovisioned device, the unprovisioned device is assigned to the Provisioner with the least number of unprovisioned devices assigned to it.

[0084] In a specific example, the signal strength (Received Signal Strength Indication, RSSI) can be a specific signal strength value, or the signal strength can be converted into a link quality (Link Quality) level, for example: RSSI>-40dBm is converted to a Link Quality level of 3, RSSI between -50dBm and -40dBm is converted to a Link Quality level of 2, RSSI between -70dBm and -50dBm is converted to a Link Quality level of 1, and RSSI<-70dBm is converted to a Link Quality level of 0. Taking signal strength versus Link Quality as an example, if an unprovisioned device is discovered by multiple provisioners, the cloud server prioritizes assigning the device to the provisioner with the highest Link Quality level at the time of discovery based on the Link Quality levels of the device discovered by the multiple provisioners. If the device has the same Link Quality level, the cloud server prioritizes assigning the device to the provisioner with the fewest assigned unprovisioned devices based on the Link Quality levels of the device discovered by the multiple provisioners and the number of unprovisioned devices already assigned by the provisioners. For example, if Provisioner1 and Provisioner2 both discover unprovisioned device N, both with a Link Quality level of 3, and Provisioner1 is assigned to provision 10 unprovisioned devices, while Provisioner2 is assigned to provision 5 devices, unprovisioned device N will be assigned to Provisioner2 first.

[0085] It should be noted that the above example is only an optional implementation. There are many ways for the cloud server to assign Provisioner to each unprovisioned device. The embodiment of the present application does not limit this, as long as the cloud server can reasonably assign unprovisioned devices based on the scanning results of the terminal device and the scanning results of the Bluetooth Mesh gateway.

[0086] It can be seen that the terminal devices, Bluetooth Mesh gateways, and cloud servers in the device configuration system of the embodiment of the present application can operate in a multi-terminal collaborative manner, thereby realizing batch configuration of unconfigured devices in a large-scale Bluetooth Mesh network, and each Provisioner directly interacts with the cloud server when performing configuration for the corresponding unconfigured device (that is, each Provisioner can independently interact with the cloud server to perform configuration for the corresponding unconfigured device), which can effectively reduce the configuration time and improve the efficiency of device configuration.

[0087] The following introduces the device network configuration method provided in the embodiment of the present application from the perspective of the terminal device. The content described below can be referenced in correspondence with the content described above.

[0088] Figure 5 The following is an exemplary flowchart of an optional device network configuration method provided in an embodiment of the present application, which is applied to a terminal device, such as Figure 5 As shown, the following steps may be included:

[0089] Step S51: execute a device discovery instruction to scan and discover unconfigured devices.

[0090] Step S52: Send the scanning result of the terminal device to the cloud server.

[0091] Step S53, obtain the network configuration information table sent by the cloud server; the network configuration information table is used to indicate the correspondence between the Provisioner and the unconfigured device, wherein the Provisioner performs network configuration for the corresponding unconfigured device, and one Provisioner corresponds to at least one unconfigured device, and the Provisioner includes a terminal device and / or a Bluetooth Mesh gateway.

[0092] Step S54: According to the network configuration information table, each Provisioner is scheduled to perform network configuration for the corresponding unconfigured device.

[0093] It can be seen that the embodiment of the present application executes the device discovery instruction through the terminal device to scan and discover unconfigured devices, sends the scanning results to the cloud server, and then obtains the network configuration information table fed back by the cloud server, so that each Provisioner can be scheduled to perform network configuration for the corresponding unconfigured devices according to the network configuration information table, thereby realizing batch network configuration of unconfigured devices. Moreover, each Provisioner scheduled by the terminal device can directly interact with the cloud server and configure the network independently, which can effectively reduce the network configuration time and improve the equipment network configuration efficiency.

[0094] It should be noted that each Provisioner can send the network configuration progress to the cloud server during the network configuration process. The network configuration progress of one Provisioner is: the network configuration progress of the unconfigured device corresponding to the Provisioner. In the embodiment of the present application, during the network configuration execution phase of the unconfigured device, the terminal device needs to be informed of the network configuration status of the unconfigured device in a timely manner. Therefore, the terminal device can poll the cloud server for the network configuration progress of each Provisioner, and then update the network configuration information table based on the network configuration progress of each Provisioner. In order to re-schedule each Provisioner based on the updated network configuration information table, the efficiency of device network configuration can be further improved.

[0095] In some embodiments, Figure 6 Another optional flow chart of the device network configuration method according to the embodiment of the present application is shown as an example. Figure 5 and Figure 6 The process shown in FIG. 5 may further include the following steps after step S54:

[0096] Step S55: Obtain the network configuration progress of each Provisioner sent by the cloud server.

[0097] Step S56 : According to the network configuration progress, the corresponding Provisioner is readjusted for the unconfigured device corresponding to the Provisioner and whose network configuration has not been completed, so as to obtain an adjusted network configuration information table.

[0098] As an optional implementation, based on factors such as differences in the network provisioning capabilities of each Provisioner or different network provisioning requirements of the unprovisioned devices corresponding to each Provisioner, the network provisioning progress of each Provisioner is different. Therefore, the terminal device can determine the unprovisioned devices for which network provisioning has not been completed based on the network provisioning progress of each Provisioner sent by the cloud server, and thus readjust the corresponding Provisioner for the unprovisioned devices for which network provisioning has not been completed. The readjustment of the corresponding Provisioner can be based on the principle that the Provisioner that has completed the network provisioning task and is in an idle state performs network provisioning on the unprovisioned devices for which network provisioning has not been completed, thereby obtaining an adjusted network provisioning information table and realizing secondary scheduling of each Provisioner. In addition, by performing secondary scheduling of the terminal device according to the actual network provisioning progress of each Provisioner during the network provisioning process, the overall network provisioning time of unprovisioned devices in the Bluetooth Mesh network is further shortened.

[0099] It should be noted that the readjusted Provisioner can scan and re-assign unprovisioned devices within its signal range, and on this basis, the readjusted Provisioner can perform network provisioning on the unprovisioned devices.

[0100] In some embodiments, the unprovisioned device for which network provisioning has not been completed corresponding to the Provisioner may include the unprovisioned device for which network provisioning has not been performed corresponding to the Provisioner, or the unprovisioned device for which network provisioning has been performed but failed corresponding to the Provisioner.

[0101] Optionally, the terminal device readjusts the corresponding Provisioner for the unprovisioned device corresponding to the Provisioner based on the network configuration progress. This can be done by reallocating the Provisioner to the unprovisioned device based on the Provisioner's status, signal strength, and number of devices that have completed network configuration in the Bluetooth Mesh network. The Provisioner status refers to the fact that the readjusted Provisioner has completed the network configuration task and is in an idle state; the signal strength refers to the signal strength of the unprovisioned device detected by the readjusted Provisioner during scanning; and the number of devices that have completed network configuration refers to the number of devices that have completed network configuration by the readjusted Provisioner.

[0102] It should be noted that for unprovisioned devices that can only be discovered by a fixed Provisioner, such as unprovisioned devices that can only be discovered by a certain Bluetooth Mesh gateway, the terminal device does not readjust the corresponding Provisioner for such unprovisioned devices, and the Provisioner corresponding to such devices still performs network provisioning.

[0103] It should be further explained that, in the embodiment of the present application, the non-network-provisioned device corresponding to the Provisioner that has undergone network configuration but failed to be networked can be determined based on two network configuration failures as the non-network-provisioned device corresponding to the Provisioner that has undergone network configuration but failed to be networked. The conditions for determining the non-network-provisioned device that has undergone network configuration but failed to be networked can be set according to actual needs, and the embodiment of the present application does not limit this.

[0104] After the terminal device obtains the adjusted network configuration information table, it may return to step S54 and schedule each Provisioner to perform network configuration for the corresponding unconfigured device according to the network configuration information table.

[0105] It should be noted that when the network configuration information table is an adjusted network configuration information table, step S54 can be executed based on the adjusted network configuration information table; when the network configuration information table is a network configuration information table sent by the cloud server obtained by the terminal device, step S54 can be executed based on the network configuration information table sent by the cloud server.

[0106] It can be seen that in the device configuration method applied to the terminal device in the embodiment of the present application, when the terminal device schedules each Provisioner to perform configuration on the unconfigured device according to the configuration information table, it can implement secondary scheduling for each Provisioner according to the configuration progress of each Provisioner, so that the overall configuration time is minimized, the configuration time of the Bluetooth Mesh device is shortened, and the configuration efficiency is improved.

[0107] The following is an introduction to the device network configuration method provided in the embodiment of the present application from the perspective of the cloud server. The content described below can be referenced in correspondence with the content described above.

[0108] Figure 7 Another optional flow chart of the device network configuration method provided in the embodiment of the present application is shown as an example, and the method is applied to a cloud server, such as Figure 7 As shown, the following steps may be included:

[0109] Step S71: Obtain the scanning results corresponding to the unprovisioned devices found by the terminal device and the scanning results corresponding to the unprovisioned devices found by the Bluetooth Mesh gateway.

[0110] Step S72: Generate a network configuration information table based on the scanning results of the terminal device and the scanning results of the Bluetooth Mesh gateway; the network configuration information table is used to indicate the correspondence between the Provisioner and the unprovisioned device, wherein the Provisioner performs network configuration for the corresponding unprovisioned device, and one Provisioner corresponds to at least one unprovisioned device, and the Provisioner includes a terminal device and / or a Bluetooth Mesh gateway.

[0111] Step S73: Send the network configuration information table to the terminal device.

[0112] It can be seen that the cloud server of the embodiment of the present application obtains the scanning results of the terminal device and the scanning results of the Bluetooth Mesh gateway, and then generates a network configuration information table based on the scanning results of the terminal device and the scanning results of the Bluetooth Mesh gateway, so that the network configuration information table can be sent to the terminal device, so that the terminal device can schedule each Provisioner to perform network configuration for the corresponding unconfigured device according to the network configuration information table, thereby realizing batch configuration of unconfigured devices. Moreover, each Provisioner in the network configuration information table generated by the cloud server can directly interact with the cloud server and independently configure the network, which can effectively reduce the time consumption of network configuration and improve the efficiency of device network configuration.

[0113] In some embodiments, the scanning result of the terminal device may include the signal strength of the unprovisioned device scanned by the terminal device, and the scanning result of the Bluetooth Mesh gateway may include the signal strength of the unprovisioned device scanned by the Bluetooth Mesh gateway. As an optional implementation, the cloud server may assign a Provisioner to each unprovisioned device based on the signal strength of the unprovisioned device scanned by the terminal device and the signal strength of the unprovisioned device scanned by the Bluetooth Mesh gateway, so as to establish a corresponding relationship between the Provisioner and the unprovisioned device, thereby recording the corresponding relationship in the configuration information table.

[0114] In some further embodiments, the cloud server may determine the signal strength between each unprovisioned device and each Provisioner based on the signal strength of the unprovisioned device scanned by the terminal device and the signal strength of the unprovisioned device scanned by the Bluetooth Mesh gateway, and then assign a Provisioner to each unprovisioned device based on the signal strength relationship between each unprovisioned device and each Provisioner, and the number of unprovisioned devices assigned to each Provisioner.

[0115] In some further embodiments, the cloud server may assign any unprovisioned device to the Provisioner with the largest signal strength; if there are multiple Provisioners with the largest signal strength for an unprovisioned device, the unprovisioned device may be assigned to the Provisioner with the least number of allocated unprovisioned devices.

[0116] It can be seen that the embodiment of the present application is applied to the device network configuration method of the cloud server. The cloud server can reasonably generate a network configuration information table based on the scanning results corresponding to the unconfigured devices discovered by the terminal device scan and the scanning results corresponding to the unconfigured devices discovered by the Bluetooth Mesh gateway scan, so that the device network configuration system of the embodiment of the present application can effectively realize batch configuration of unconfigured devices.

[0117] To facilitate understanding of the device distribution method of the above device distribution system, Figure 8 The following example shows an optional example of each Provisioner finding an unprovisioned device in an embodiment of the present application. Figure 8 As shown in the figure, the provisioners in the Bluetooth Mesh network are terminal devices, gateway 1, gateway 2, and gateway 3. The dotted lines represent the signal range of each provisioner, and the unprovisioned devices are A, B, ..., W.

[0118] From the initiation of the device discovery process on the terminal device interface to the completion of device discovery, the unprovisioned devices discovered by each Provisioner are shown in Table 1:

[0119] Provisioner Unconfigured devices terminal equipment A, B, C, H, I, J, O Gateway 1 C,D,E,I,J,K,L,M,O,P,Q,R Gateway 2 D,E,F,G,K,L,M,N,P,Q Gateway 3 S, T, U, V, W

[0120] Table 1

[0121] It can be seen that the terminal device has discovered 7 unprovisioned devices, and gateway 1 has discovered 12 unprovisioned devices. Among them, gateway 1 found that the signal strength of the I, M broadcast packet was weak. Gateway 2 found 10 unprovisioned devices, and gateway 3 found 5 unprovisioned devices, totaling 34 unprovisioned devices. If light bulbs are included as unprovisioned devices, the number of unprovisioned light bulbs displayed on the terminal device's device discovery interface is 34.

[0122] Each Provisioner scans each unprovisioned device found and sends the scan results, which record the signal strength, to the cloud server. The cloud server generates a network configuration information table based on the scan results of each Provisioner. The network configuration information table is shown in Table 2:

[0123] Provisioner Unconfigured devices terminal equipment A, B, C, H, I, J, Gateway 1 D, K, O, P, Q, R Gateway 2 E, F, G, L, M, N Gateway 3 S, T, U, V, W

[0124] Table 2

[0125] It can be seen that the cloud server generates a network configuration information table based on the scanning results of each Provisioner, balancing the status of each Provisioner, the number of unprovisioned devices, and the signal strength of each Provisioner scanning the corresponding unprovisioned devices.

[0126] Assume that the terminal device notifies each Bluetooth Mesh gateway through the WiFi router that it has discovered an unprovisioned device. The wireless communication signal between Gateway 1 and the WiFi router is poor, or there are other interference factors, causing its configuration speed to be slower than that of other Provisioners. The cloud server obtains the configuration progress of each Provisioner. The terminal device and Gateway 2 complete the configuration tasks shown in Table 2. Gateway 1's unprovisioned device O has failed to configure the network twice, and unprovisioned device Q has not yet completed configuration. The cloud server sends the configuration progress of each Provisioner to the terminal device. Based on the configuration progress, the terminal device readjusts the Provisioners corresponding to unprovisioned devices O and Q, and reschedules the Provisioners that have completed the configuration tasks and are in an idle state.

[0127] Among them, if the unconfigured device O can be discovered by the terminal device, it is adjusted so that the terminal device performs network configuration on the unconfigured device O; if the unconfigured device Q can be discovered by the gateway 2, it is adjusted so that the gateway 2 performs network configuration on the unconfigured device Q.

[0128] Among them, reference Figure 8 Gateway 3 can only discover five unprovisioned devices: S, T, U, V, and W. These five unprovisioned devices cannot be discovered by other provisioners. In other words, the unprovisioned devices discovered by Gateway 3 do not overlap with those discovered by other provisioners. Therefore, gateway 3 can only perform network provisioning on these five unprovisioned devices, and gateway 3 can only perform network provisioning on these five unprovisioned devices. Therefore, in the network provisioning progress sent by the cloud server and obtained by the terminal device, even if gateway 3 has completed network provisioning and is idle, it will not be rescheduled. Even if other provisioners have completed network provisioning and are idle, if there are still unprovisioned devices among the unprovisioned devices configured by gateway 3, such as unprovisioned device S, this unprovisioned device S will not be configured by other provisioners.

[0129] The following describes the device network configuration apparatus provided in the embodiments of this application from the perspective of a terminal device. The device configuration described below can be considered the functional modules required by the terminal device to implement the device network configuration method provided in the embodiments of this application. The following description can be used in conjunction with the above description.

[0130] As an optional implementation, Figure 9 An optional block diagram of the device network distribution device provided in the embodiment of the present application is shown as an example. The device can be applied to a terminal device. Figure 9 , the apparatus may include:

[0131] The instruction execution module 91 is used to execute the device discovery instruction to scan and discover unconfigured network devices;

[0132] A result output module 92 is used to send the scanning result of the terminal device to the cloud server;

[0133] An information acquisition module 93 is configured to acquire a network configuration information table sent by the cloud server; the network configuration information table is configured to indicate a correspondence between a Provisioner and an unconfigured device, wherein a Provisioner performs network configuration for the corresponding unconfigured device, and one Provisioner corresponds to at least one unconfigured device, and the Provisioner includes a terminal device and / or a Bluetooth Mesh gateway;

[0134] The scheduling module 94 is used to schedule each Provisioner to perform network configuration for the corresponding unconfigured device according to the network configuration information table.

[0135] In some embodiments, the device network distribution apparatus further includes:

[0136] The progress acquisition module 95 is used to obtain the network configuration progress of each Provisioner sent by the cloud server;

[0137] The adjustment module 96 is configured to readjust the corresponding Provisioner for the unprovisioned device corresponding to the Provisioner and for which network provisioning has not been completed, according to the network provisioning progress, so as to obtain an adjusted network provisioning information table.

[0138] The scheduling module 94 is further configured to schedule each Provisioner to perform network configuration for the corresponding unconfigured device according to the adjusted network configuration information table.

[0139] In some embodiments, the unprovisioned device for which the provisioner has not completed network provisioning includes: an unprovisioned device for which the provisioner has not yet performed network provisioning, or an unprovisioned device for which the provisioner has performed network provisioning but failed to perform network provisioning;

[0140] The adjusting module 96 is configured to readjust the corresponding Provisioner for the unprovisioned device corresponding to the Provisioner and in an uncompleted network configuration state according to the network configuration progress, including the following steps:

[0141] Based on the status, signal strength, and number of devices that have completed network provisioning in the Bluetooth Mesh network, the Provisioner is reassigned to the unprovisioned device that has not completed network provisioning.

[0142] The embodiment of the present application also provides a terminal device, which can implement the device network configuration method provided by the embodiment of the present application by setting the device network configuration device described above. As an optional implementation, Figure 10 Optional block diagram of the terminal device provided in the embodiment of the present application, such as Figure 10 As shown, the terminal device may include: at least one processor 1, at least one communication interface 2, at least one memory 3 and at least one communication bus 4.

[0143] In an embodiment of the present application, the number of processor 1 , communication interface 2 , memory 3 , and communication bus 4 is at least one, and the processor 1 , communication interface 2 , and memory 3 communicate with each other through the communication bus 4 .

[0144] Optionally, the communication interface 2 may be an interface of a communication module for network communication. Optionally, the processor 1 may be a CPU (central processing unit), a GPU (Graphics Processing Unit), an NPU (embedded neural network processor), an FPGA (Field Programmable Gate Array), a TPU (tensor processing unit), an AI chip, an application-specific integrated circuit ASIC (Application Specific Integrated Circuit), or one or more integrated circuits configured to implement an embodiment of the present application.

[0145] The memory 3 may include a high-speed RAM memory, and may also include a non-volatile memory (non-volatile memory), such as at least one disk memory.

[0146] Among them, the memory 3 stores one or more computer-executable instructions, and the processor 1 calls the one or more computer-executable instructions to execute the device network configuration method executed by the terminal device in the embodiment of the present application.

[0147] An embodiment of the present application also provides a storage medium, which stores one or more computer-executable instructions. When the one or more computer-executable instructions are executed, the device network configuration method executed by the terminal device in the embodiment of the present application is implemented.

[0148] An embodiment of the present application also provides a computer program, which, when executed, implements the device network configuration method performed by the terminal device in the embodiment of the present application.

[0149] The following describes the device network configuration apparatus provided in the embodiments of this application from the perspective of a cloud server. The apparatus described below can be considered the functional modules required by the cloud server to implement the device network configuration method provided in the embodiments of this application. The following description can be used as a cross-reference with the above description.

[0150] As an optional implementation, Figure 11 Another optional block diagram of the device network configuration device provided in the embodiment of the present application is shown as an example. The device can be applied to a cloud server. Figure 11 , the apparatus may include:

[0151] The result acquisition module 111 is used to obtain the scanning results corresponding to the unprovisioned devices found by the terminal device and the scanning results corresponding to the unprovisioned devices found by the Bluetooth Mesh gateway;

[0152] An information table generation module 112 is configured to generate a network configuration information table based on the scan results of the terminal device and the scan results of the Bluetooth Mesh gateway; the network configuration information table is used to indicate the correspondence between the Provisioner and the unprovisioned device, wherein the Provisioner performs network configuration for the corresponding unprovisioned device, and one Provisioner corresponds to at least one unprovisioned device, and the Provisioner includes a terminal device and / or a Bluetooth Mesh gateway;

[0153] The sending module 113 is configured to send the network configuration information table to the terminal device.

[0154] In some embodiments, the scanning result of the terminal device includes: the signal strength of the unprovisioned device scanned by the terminal device; the scanning result of the Bluetooth Mesh gateway includes: the signal strength of the unprovisioned device scanned by the Bluetooth Mesh gateway;

[0155] The information table generating module 112 is configured to generate a network configuration information table according to the scanning results of the terminal device and the scanning results of the Bluetooth Mesh gateway, including the following steps:

[0156] According to the signal strength of the unprovisioned device scanned by the terminal device and the signal strength of the unprovisioned device scanned by the Bluetooth Mesh gateway, a Provisioner is assigned to each unprovisioned device to establish a correspondence between the Provisioner and the unprovisioned device; the correspondence is recorded in the configuration information table.

[0157] In some further embodiments, the information table generation module 112 allocates a Provisioner to each identified unprovisioned device according to the signal strength of the unprovisioned device scanned by the terminal device and the signal strength of the unprovisioned device scanned by the Bluetooth Mesh gateway. The steps are:

[0158] Determine the signal strength between each unprovisioned device and each provisioner based on the signal strength of the unprovisioned device scanned by the terminal device and the signal strength of the unprovisioned device scanned by the Bluetooth Mesh gateway;

[0159] Assign a Provisioner to each unprovisioned device based on the signal strength relationship between each unprovisioned device and each Provisioner, as well as the number of unprovisioned devices assigned to each Provisioner.

[0160] In some embodiments, the step of assigning a Provisioner to each unprovisioned device based on a signal strength relationship between each unprovisioned device and each Provisioner, and the number of unprovisioned devices assigned to each Provisioner, includes:

[0161] For any unprovisioned device, assign it to the Provisioner with the strongest signal strength. If there are multiple Provisioners with the strongest signal strength for an unprovisioned device, assign it to the Provisioner with the least number of assigned unprovisioned devices.

[0162] The present application also provides a cloud server comprising at least one memory and at least one processor. The memory stores one or more computer-executable instructions, and the processor invokes the one or more computer-executable instructions to execute the device network configuration method performed by the cloud server according to the present application. The block diagram structure of the cloud server may refer to the block diagram structure of the terminal device described above and will not be further described here.

[0163] An embodiment of the present application also provides a storage medium, which stores one or more computer-executable instructions. When the one or more computer-executable instructions are executed, the device network configuration method executed by the cloud server in the embodiment of the present application is implemented.

[0164] An embodiment of the present application also provides a computer program, which, when executed, implements the device network configuration method executed by the cloud server in the embodiment of the present application.

[0165] The above describes a plurality of embodiment schemes provided by the embodiments of the present application. The various optional modes introduced in the various embodiment schemes can be combined with each other and cross-referenced without conflict, thereby extending a variety of possible embodiment schemes, which can all be considered as the embodiment schemes disclosed and disclosed in the embodiments of the present application. Although the embodiments of the present application are disclosed as above, the present application is not limited thereto. Any person skilled in the art can make various changes and modifications without departing from the spirit and scope of the present application, and therefore the scope of protection of the present application should be based on the scope defined by the claims.

Claims

1. A device distribution network system, wherein: include: Terminal devices, Bluetooth Mesh gateways, and cloud servers; The terminal device is used to execute a device discovery instruction to scan and discover unconfigured network devices; The scanning result is sent to the cloud server; the network configuration information table fed back by the cloud server is obtained, the network configuration information table is used to indicate the corresponding relationship between the Provisioner and the unconfigured device, wherein the Provisioner performs network configuration for the corresponding unconfigured device, and one Provisioner corresponds to at least one unconfigured device, and the Provisioner includes a terminal device and / or a Bluetooth Mesh gateway; and according to the network configuration information table, each Provisioner is scheduled to perform network configuration for the corresponding unconfigured device; the terminal device polls the cloud server for the network configuration progress of each Provisioner, and then updates the network configuration information table according to the network configuration progress of each Provisioner, so as to re-schedule each Provisioner according to the updated network configuration information table; each Provisioner sends the network configuration progress to the cloud server during the network configuration process, and the network configuration progress is the network configuration progress of the unconfigured device corresponding to each Provisioner, and the terminal device directly interacts with the cloud server; The Bluetooth Mesh gateway is configured to obtain a device discovery instruction from the terminal device conveyed by the cloud server to scan and discover unprovisioned devices; send the scan results to the cloud server; and, when the Bluetooth Mesh gateway is the provisioner performing network provisioning, be dispatched by the terminal device to perform network provisioning for the corresponding unprovisioned device; The cloud server is used to obtain the scanning results of the terminal device and the scanning results of the Bluetooth Mesh gateway; and generate a network configuration information table according to the scanning results of the terminal device and the scanning results of the Bluetooth Mesh gateway; Send the network configuration information table to the terminal device.

2. The equipment distribution network system according to claim 1, wherein: The scanning result of the terminal device includes: the signal strength of the unconfigured device scanned by the terminal device; the scanning result of the Bluetooth Mesh gateway includes: the signal strength of the unconfigured device scanned by the Bluetooth Mesh gateway; The cloud server is configured to generate a network configuration information table according to the scanning result of the terminal device and the scanning result of the Bluetooth Mesh gateway, including: According to the signal strength of the unprovisioned device scanned by the terminal device and the signal strength of the unprovisioned device scanned by the Bluetooth Mesh gateway, a Provisioner is assigned to each unprovisioned device to establish a correspondence between the Provisioner and the unprovisioned device; the correspondence is recorded in the configuration information table.

3. The equipment distribution network system according to claim 2, wherein: Allocating a Provisioner to each unprovisioned device according to the signal strength of the unprovisioned device scanned by the terminal device and the signal strength of the unprovisioned device scanned by the Bluetooth Mesh gateway includes: Determine the signal strength between each unprovisioned device and each provisioner based on the signal strength of the unprovisioned device scanned by the terminal device and the signal strength of the unprovisioned device scanned by the Bluetooth Mesh gateway; Assign a Provisioner to each unprovisioned device based on the signal strength relationship between each unprovisioned device and each Provisioner, as well as the number of unprovisioned devices assigned to each Provisioner.

4. The equipment distribution network system according to claim 3, wherein: The allocating a Provisioner to each unprovisioned device according to the signal strength relationship between each unprovisioned device and each Provisioner, and the number of unprovisioned devices allocated to each Provisioner, includes: For any unprovisioned device, assign it to the Provisioner with the strongest signal strength. If there are multiple Provisioners with the strongest signal strength for an unprovisioned device, assign it to the Provisioner with the least number of assigned unprovisioned devices.

5. A device network configuration method, wherein: Applied to terminal equipment, including: Execute device discovery commands to scan and discover unconfigured devices; Sending the scanning result of the terminal device to the cloud server; Obtaining a network configuration information table sent by the cloud server; the network configuration information table is used to indicate the correspondence between the Provisioner and the unprovisioned device, wherein the Provisioner performs network configuration for the corresponding unprovisioned device, and one Provisioner corresponds to at least one unprovisioned device, the Provisioner includes a terminal device and / or a Bluetooth Mesh gateway, and the terminal device directly interacts with the cloud server; According to the network configuration information table, each Provisioner is scheduled to perform network configuration for the corresponding unconfigured device; The cloud server is polled for the network configuration progress of each Provisioner, and the network configuration information table is updated according to the network configuration progress of each Provisioner, so that each Provisioner can be rescheduled according to the updated network configuration information table. During the network configuration process, each Provisioner sends the network configuration progress to the cloud server. The network configuration progress is the network configuration progress of the unconfigured devices corresponding to each Provisioner.

6. The device network configuration method according to claim 5, wherein: The method further comprises: Get the network configuration progress of each Provisioner sent by the cloud server; According to the network configuration progress, for the unconfigured devices corresponding to the Provisioner and for which network configuration has not been completed, the corresponding Provisioner is readjusted to obtain an adjusted network configuration information table; According to the adjusted network configuration information table, each Provisioner is scheduled to perform network configuration for the corresponding unconfigured devices.

7. The device network configuration method according to claim 6, wherein: The unprovisioned device for which the provisioner has not completed network provisioning includes: the unprovisioned device for which the provisioner has not yet performed network provisioning, or the unprovisioned device for which the provisioner has performed network provisioning but failed to perform network provisioning; Re-adjusting the corresponding Provisioner for the unprovisioned device corresponding to the Provisioner and not yet completed with network provisioning according to the network provisioning progress includes: Based on the status, signal strength, and number of devices that have completed network provisioning in the Bluetooth Mesh network, the Provisioner is reassigned to the unprovisioned device that has not completed network provisioning.

8. A device network configuration method, wherein: Applied to cloud servers, including: Obtain the scan results of the terminal device scanning for unprovisioned devices, and the scan results of the Bluetooth Mesh gateway scanning for unprovisioned devices; Generate a network configuration information table based on the scan results of the terminal device and the scan results of the Bluetooth Mesh gateway; the network configuration information table is used to indicate the correspondence between the Provisioner and the unprovisioned device, wherein the Provisioner performs network configuration for the corresponding unprovisioned device, and one Provisioner corresponds to at least one unprovisioned device, and the Provisioner includes the terminal device and / or the Bluetooth Mesh gateway; Sending the network configuration information table to the terminal device, wherein the terminal device directly interacts with the cloud server; Receive the network configuration progress sent by each Provisioner during the network configuration process, where the network configuration progress is the network configuration progress of the unconfigured device corresponding to each Provisioner, and receive the network configuration progress of each Provisioner sent by the terminal device, so that the terminal device updates the network configuration information table according to the network configuration progress of each Provisioner, and re-schedules each Provisioner according to the updated network configuration information table.

9. The device network configuration method according to claim 8, wherein: The scanning result of the terminal device includes: the signal strength of the unconfigured device scanned by the terminal device; the scanning result of the Bluetooth Mesh gateway includes: the signal strength of the unconfigured device scanned by the Bluetooth Mesh gateway; Generating a network configuration information table according to the scanning result of the terminal device and the scanning result of the Bluetooth Mesh gateway includes: According to the signal strength of the unprovisioned device scanned by the terminal device and the signal strength of the unprovisioned device scanned by the Bluetooth Mesh gateway, a Provisioner is assigned to each unprovisioned device to establish a correspondence between the Provisioner and the unprovisioned device; the correspondence is recorded in the configuration information table.

10. The device network configuration method according to claim 9, wherein: Allocating a Provisioner to each unprovisioned device according to the signal strength of the unprovisioned device scanned by the terminal device and the signal strength of the unprovisioned device scanned by the Bluetooth Mesh gateway includes: Determine the signal strength between each unprovisioned device and each provisioner based on the signal strength of the unprovisioned device scanned by the terminal device and the signal strength of the unprovisioned device scanned by the Bluetooth Mesh gateway; Assign a Provisioner to each unprovisioned device based on the signal strength relationship between each unprovisioned device and each Provisioner, as well as the number of unprovisioned devices assigned to each Provisioner.

11. The device network configuration method according to claim 10, wherein: The allocating a Provisioner to each unprovisioned device according to the signal strength relationship between each unprovisioned device and each Provisioner, and the number of unprovisioned devices allocated to each Provisioner, includes: For any unprovisioned device, assign it to the Provisioner with the strongest signal strength. If there are multiple Provisioners with the strongest signal strength for an unprovisioned device, assign it to the Provisioner with the least number of assigned unprovisioned devices.

12. A terminal device, wherein: The method comprises at least one memory and at least one processor, wherein the memory stores one or more computer-executable instructions, and the processor calls the one or more computer-executable instructions to execute the device network configuration method according to any one of claims 5 to 7.

13. A cloud server, wherein: It includes at least one memory and at least one processor, the memory stores one or more computer-executable instructions, and the processor calls the one or more computer-executable instructions to execute the device network configuration method according to any one of claims 8 to 11.

14. A storage medium, wherein: The storage medium stores one or more computer-executable instructions, and when the one or more computer-executable instructions are executed, the device network configuration method according to any one of claims 5 to 7 or the device network configuration method according to any one of claims 8 to 11 is implemented.

Citation Information

Patent Citations

  • Bluetooth Mesh network and network distribution method and device thereof, and storage medium

    CN110493758A