System comprising nodes in a mesh network and method in such a system

Abstract

A method in a system is disclosed, the system comprising a plurality of nodes, each node of the plurality of nodes being preconfigured with a first parameter enabling a node to communicate with at least one other node via a first mesh network, the plurality of nodes comprising at least one first node and a plurality of second nodes, wherein each of the at least one first node is communicatively coupled or coupleable with a server in which a node identifier of a respective node of the plurality of nodes and a corresponding node security key are stored. For each of the at least some node identifiers, the server encrypts a second set of parameters for the corresponding node using its node security key, where for the node, the second set of parameters enables the node to communicate with the at least one other node via the second mesh network. The server sends the encrypted second set of parameters to the first node (s) along with identifiers identifying nodes corresponding to respective ones of the encrypted second set of parameters. Each of the at least one first node sends a corresponding set of encrypted second parameters to the second node (s) via the first mesh network, the first nodes being communicatively coupled to each other to the second node (s) via the first mesh network. Each of the plurality of nodes decrypts its received encrypted second set of parameters using its node security key.

Description

Technical Field

[0001] This invention relates to a method in a system comprising multiple nodes, wherein each node is capable of communicating with at least one other node among the multiple nodes via a mesh network. The invention also relates to such a system. Through one or more embodiments of the invention, a mesh network through which multiple nodes can communicate can be readily provided. Background Technology

[0002] Different entities can be communicatively coupled via a communication network, enabling communication between them. Such an entity, which can be referred to as a node without loss of generality, can be included, for example, in a lighting device, thus forming a connected lighting system. Prior to the operation of the communication network, entities or nodes may need to be properly configured to allow communication between them. In other words, the communication network may need to be provided before its operation. As is known in the art, network provisioning generally refers to the process of establishing a network so that authorized users, devices, and servers can access it.

[0003] US10887447B2 relates to the configuration and / or management of smart nodes with limited user interfaces. It discloses a processing device configured to obtain an identifier of a first node in a set of nodes deployed at a building or other structure, associate the first node with a user account, obtain an identifier of a second node in the set of nodes, and associate the second node with the first node and the user account. Associating the first node with the user account may include, for example, establishing an association between the first node and the user account, in cases where the processing device does not have access to a network connection. Additionally or alternatively, the identifier of the first node may be sent to a backend server via a network connection, and configuration information for the first node may be received from the backend server in response. Summary of the Invention

[0004] In a connected lighting system comprising multiple nodes, only a limited number of nodes in the lighting system can have the ability to communicate with entities other than the other nodes. This can be described as most nodes having only a “local” radio frequency (RF) communication interface, enabling each node to communicate with other nodes in the connected lighting system, while one or more other nodes (e.g., a single node or only a few nodes) have both this “local” RF communication interface and a “cellular” communication interface, enabling the respective node among these one or more nodes to communicate with entities other than the other nodes. For ease of description, these other entities may be referred to as servers hereinafter, without loss of generality. A server could be, for example, a cloud server. This type of connected lighting system has a so-called hybrid lighting network architecture, which can significantly reduce the cost of the hardware required for the connected lighting system. Using this hybrid lighting network architecture, node-to-node communication and applications can be implemented via the “local” RF interface (e.g., via a mesh network such as Bluetooth mesh), and node-to-server communication and applications can be implemented via nodes having both the “local” RF communication interface and the “cellular” communication interface.

[0005] A network where multiple nodes of a connected lighting system can communicate via their “local” RF communication interfaces should be automatically provisioned from a server, which may be desirable or even required. The server can be remotely located relative to the nodes. Therefore, it may be desirable or even required that this provisioning be performed with little or no field operation. Node-to-node communication and applications can be implemented via the “local” RF interface and via a mesh network. Nodes in the connected lighting system with both “local” RF and “cellular” communication interfaces can act as so-called “embedded providers” to provision neighboring nodes into the mesh network. For this purpose, the server can select and notify nodes in the connected lighting system with both “local” RF and “cellular” communication interfaces to perform a traditional Bluetooth mesh network provisioning process with neighboring nodes, for example, a traditional Bluetooth mesh network provisioning process. To reduce the cost of the required hardware, a node with both a “local” RF and “cellular” communication interface can “manage” several (e.g., as many as possible) of nodes with only a “local” RF communication interface. However, when a node with both a "local" RF communication interface and a "cellular" communication interface acts as a so-called "embedded provider" to supply neighboring nodes to the mesh network, the node may only be able to supply neighboring nodes within a one-hop distance of it in the mesh network. This limits the number of adjacent or neighboring nodes that a node with both a "local" RF communication interface and a "cellular" communication interface can manage.

[0006] In view of the foregoing, the present invention focuses on providing a method that facilitates the supply of mesh networks through which multiple nodes can communicate, while keeping the cost of the required hardware relatively low.

[0007] According to a first aspect of the invention, a method is provided. The method is performed or implemented in a system comprising a plurality of nodes, wherein each of the plurality of nodes is pre-configured with a first parameter that enables the node to communicate with at least one other node among the plurality of nodes via a first mesh network. For each of the plurality of nodes, the first parameter includes a node identifier and a node security key, wherein the corresponding node identifier of each of the plurality of nodes uniquely identifies the node, and wherein the corresponding node security key of each of the plurality of nodes is unique for that node. The plurality of nodes includes at least one first node and a plurality of second nodes. Each of the at least one first node is communicatively coupled or coupled to a server, whereby the server stores the node identifier and the corresponding node security key of the corresponding node among the plurality of nodes. Each of the second nodes is communicatively coupled to one of the at least one first node via the first mesh network. The method includes, for each of the at least some node identifiers, the server encrypting a second set of parameters for the corresponding node using its node security key, wherein for each of the plurality of nodes, the second set of parameters enables the node to communicate with at least one other node among the plurality of nodes via a second mesh network different from the first mesh network. The method includes a server sending an encrypted second set of parameters along with an identifier identifying a node corresponding to a corresponding parameter set in the encrypted second set to a first node. The method further includes each of at least one first node sending the corresponding encrypted set of second parameters to a second node via a first mesh network, the first nodes being communicatively coupled to each other via the first mesh network. The method also includes each of a plurality of nodes using its node security key to decrypt the received encrypted second set of parameters.

[0008] According to a second aspect of the invention, a system is provided. The system includes a plurality of nodes, wherein each of the plurality of nodes is pre-configured with a first parameter, the first parameter enabling the node to communicate with at least one other node among the plurality of nodes via a first mesh network. For each of the plurality of nodes, the first parameter includes a node identifier and a node security key, wherein the corresponding node identifier of each of the plurality of nodes uniquely identifies the node, and wherein the corresponding node security key of each of the plurality of nodes is unique for that node. The system includes a server. The plurality of nodes includes at least one first node and a plurality of second nodes, wherein each of the at least one first node is communicatively coupled or combinable to the server, the node identifier and the corresponding node security key of the respective node among the plurality of nodes are stored in the server, and wherein each of the second nodes is communicatively coupled to one of the at least one first node via the first mesh network. For each of the at least some node identifiers, the server is configured to encrypt a second set of parameters of the corresponding node using the node security key of the corresponding node, wherein for each of the plurality of nodes, the second set of parameters enables the node to communicate with at least one other node among the plurality of nodes via a second mesh network. The server is configured to send an encrypted second set of parameters, along with an identifier identifying the node corresponding to the corresponding parameter set in the encrypted second set, to the first node. Each of at least one first node is configured to send its corresponding encrypted second set of parameters to the second node via a first mesh network, the first nodes being communicatively coupled to each other via the first mesh network. Each of the plurality of nodes is configured to decrypt its received encrypted second set of parameters using its node security key.

[0009] Through one or more embodiments of the present invention, a mesh network through which multiple nodes can communicate can be readily supplied. In particular, a mesh network through which multiple nodes can communicate can be supplied from a server (e.g., a remotely located server, such as a cloud server), requiring little or no on-site operation.

[0010] Of the multiple nodes, only the first node can be communicatively coupled or coupled to the server. Therefore, the first node may be the only node among the multiple nodes capable of communicating with at least one other node and with the server via (e.g., a first or second) mesh network, while the second node may be capable of communicating with at least one other node but not with the server (e.g., direct communication). For this purpose, the first node may be referred to as a proxy or intermediary node, acting as an intermediary between the second node and the server. Each of the at least one first node can be communicatively coupled or coupled to the server via a communication network such as the Internet. Each of the at least one first node can be communicatively coupled or coupled to the server via one or more secure communication paths, such as those known in the art.

[0011] With the aid of one or more embodiments of the present invention, a mesh network provisioning can be performed by a server via only a few nodes or even only a single node (i.e., a first node), multiple nodes can communicate through the mesh network, and the few nodes or even the single node is or can communicate with at least one other node among the multiple nodes and with the server via (e.g., a first or a second) mesh network. This is because each of the multiple nodes is pre-configured with a first parameter that enables the node to communicate with at least one other node among the multiple nodes via a first mesh network, and a second set of parameters that enables the node to communicate with at least one other node among the multiple nodes via a second mesh network can be transmitted or distributed to the node via the first mesh network. The distribution of the second set of parameters can be performed securely by means of the node security key of the corresponding node, the node security key being included in the first parameter associated with the first mesh network of the corresponding node.

[0012] In the context of this application, a node's (node) security key can in principle refer to any security credential that may be expected or required in order for a node to communicate securely with at least one other node among a plurality of nodes via a mesh network (e.g., a first or second mesh network).

[0013] During node manufacturing, each of the multiple nodes may have a first parameter pre-configured. Therefore, each of the multiple nodes may have a first parameter pre-configured as part of the node manufacturing process. For each of the multiple nodes, the first parameter may be stored in the node's memory.

[0014] As described above, for each of the at least some node identifiers, the server can use its node security key to encrypt the second set of parameters for the corresponding node. To determine which node identifier should be used for this operation, each second node can broadcast its node identifier via the first mesh network. Each of at least one first node can receive the node identifier of each of the second nodes via the first mesh network, and the first nodes are communicatively coupled to each of the second nodes via the first mesh network. Each of at least one first node can send the received node identifier along with its own node identifier to the server. The aforementioned at least some node identifiers may include node identifiers received from the first nodes or may consist of node identifiers received from the first nodes.

[0015] The steps of each second node broadcasting its node identifier via the first mesh network, each of at least one first node receiving the node identifier of each of the second nodes that are communicatively coupled to the first node via the first mesh network, and possibly each of at least one first node sending the received node identifier along with its own node identifier to the server, can be performed (e.g., only once) when the plurality of nodes first begin operation (e.g., power-on).

[0016] As described above, each of the at least one first node can send a corresponding encrypted second parameter set to a second node via a first mesh network, the first nodes being communicatively coupled to each other via the first mesh network. For example, each of the at least one first node can broadcast the encrypted second parameter set and an identifier identifying the node corresponding to the corresponding second parameter set in the encrypted second parameter set via the first mesh network. Then, each second node can determine which encrypted second parameter set is intended for use by the second node based on the identifier. Another possibility is that each of the at least one first node, based on the identifier, sends the corresponding encrypted second parameter set to the second node in a one-to-one transmission manner via the first mesh network, the first nodes being communicatively coupled to each other via the first mesh network, wherein each one-to-one transmission corresponds to a corresponding second node among the second nodes to which the first node is communicatively coupled via the first mesh network.

[0017] Each second node, after decrypting its encrypted second parameter set, can send its acknowledgment to the first node via the first mesh network, and the second nodes are communicatively coupled to the first nodes via the first mesh network. Each of at least one first node, after decrypting its encrypted second communication parameter set, can send its acknowledgment and any acknowledgments received from the second nodes via the first mesh network to the server, and the first nodes are communicatively coupled to the second nodes. For each of at least one first node, if within a selected time period after sending the encrypted second parameter set to the second node, the first node has not received acknowledgment from the second node, which is communicatively coupled to it via the first mesh network, that the second node has decrypted its encrypted second communication parameter set, then the first node can retransmit the encrypted second parameter set to the second node via the first mesh network at selected time intervals until the first node receives an acknowledgment.

[0018] After receiving confirmation from each of the multiple nodes, the server can send the following command to each of the at least one first node: each of the multiple nodes will then communicate via the second mesh network.

[0019] It should be noted that acknowledgment from each node to the server is an optional step. The server can simply send a command to each of at least one of the first nodes, and after the server sends an encrypted second set of parameters and an identifier identifying the node corresponding to the corresponding parameter set in the encrypted second set to the first node, each of the multiple nodes then communicates via the second mesh network. This is because, as is common knowledge, acknowledgment / reply for receiving a message is not a necessary feature of message delivery. It is an option to enhance the robustness / efficiency of communication between the two communicating parties, for example, by further checking whether the message has been successfully delivered through how the receiver acts / operates.

[0020] Each of at least one first node can send commands to a second node via a first mesh network, which will then communicate via a second mesh network. The first nodes are communicatively coupled to each other via the first mesh network. Alternatively or additionally, each of at least one first node can forward commands received from a server to a second node via the first mesh network, and the first nodes are communicatively coupled to the second node via the first mesh network.

[0021] Encryption of a second set of parameters corresponding to each of at least some node identifiers may include the server creating a data packet that includes the encrypted second set of parameters, the data packet including a header that includes the identifier of the node corresponding to the encrypted second set of parameters in the data packet.

[0022] The server may send an encrypted second parameter set, which it sends to the first node, along with an identifier identifying the node corresponding to the corresponding second parameter set in one or more messages. For example, for each first node, the server may send the encrypted second parameter set along with the identifier identifying the node corresponding to the encrypted second parameter set separately to the first node.

[0023] At least one of the first mesh network and the second mesh network may include a Bluetooth mesh network.

[0024] The server may be or include a cloud server. A cloud server may be configured to run cloud applications to perform one or more of the various operations described herein. The server may include storage containing node identifiers and corresponding node security keys for the respective nodes among a plurality of nodes.

[0025] According to a third aspect of the invention, a server is provided that is included in a system according to a second aspect of the invention.

[0026] According to a fourth aspect of the invention, at least one first node is provided in a system according to a second aspect of the invention.

[0027] Each or any one of the multiple nodes may be included in the lighting equipment. Each or any one of the multiple nodes may be included in a light pole arranged along the road.

[0028] Each or any lighting device or pole may include at least one light source. Each or any of the at least one light source may, for example, include a solid-state emitter, such as one or more light-emitting diodes (LEDs) and / or one or more lasers. Each or any LED may, for example, include or be composed of inorganic LEDs and / or organic LEDs (OLEDs). Solid-state light emitters are relatively cost-effective light sources because they are generally relatively inexpensive and have relatively high luminous efficiency and relatively long lifetime. Examples of LEDs include semiconductor, organic or polymer / polymer LEDs, light-pumped phosphor-coated LEDs, light-pumped nanocrystal LEDs, or any other similar devices readily understood by those skilled in the art. For example, the term LED may include a bare LED die disposed in a housing, which may be referred to as an LED package. According to another example, the term LED may cover chip-scale packaged (CSP) LEDs, which may include LED dies directly attached to a substrate such as a printed circuit board (PCB) without via a sub-mount.

[0029] Other objects and advantages of the invention are described below by way of exemplary embodiments. It should be noted that the invention relates to all possible combinations of the features in the claims. Other features and advantages of the invention will become apparent when the appended claims and the description herein are examined. Those skilled in the art will recognize that different features of the invention can be combined to create embodiments different from those described herein. Attached Figure Description

[0030] Exemplary embodiments of the present invention will now be described with reference to the accompanying drawings.

[0031] Figures 1 to 4 Each figure in the diagram is a schematic diagram of a system according to an embodiment of the present invention, used to illustrate the principles of one or more embodiments of the present invention.

[0032] Figure 5 and Figure 6 Each figure in the diagram is a schematic flowchart illustrating a method according to an embodiment of the present invention.

[0033] All accompanying drawings are schematic and not necessarily to scale, and generally only show the parts necessary to illustrate embodiments of the invention, where other parts may be omitted or merely suggested. Detailed Implementation

[0034] The invention will now be described below with reference to the accompanying drawings, in which exemplary embodiments of the invention are illustrated. However, the invention may be embodied in many different forms and should not be construed as limited to the embodiments set forth herein; rather, these embodiments are provided by way of example, thereby conveying the scope of the invention to those skilled in the art. In the drawings, the same reference numerals denote the same or similar parts having the same or similar functions, unless otherwise specifically stated.

[0035] Figure 1 This is a schematic diagram of a system 30 according to an embodiment of the present invention, used to illustrate the principles of one or more embodiments of the present invention. System 30 includes multiple nodes 1-10 and a server 20. According to... Figure 1 The embodiment of the invention shown includes system 30 with ten nodes; however, it should be understood that this is based on an example, and system 30 can in principle include any number of nodes. Therefore, system 30 can include more than... Figure 1 Showing fewer or more nodes.

[0036] Each of the plurality of nodes 1-10 is pre-configured with a first parameter that enables the node to communicate with at least one other node among the plurality of nodes 1-10 via a first mesh network. For each of the plurality of nodes 1-10, the first parameter includes a node identifier and a node security key, wherein the corresponding node identifier of each of the plurality of nodes 1-10 uniquely identifies the node, and wherein the corresponding node security key of each of the plurality of nodes 1-10 is unique to that node. The first mesh network may be referred to as a “default” mesh network. For example, each of the plurality of nodes 1-10 may have been pre-configured with the first parameter during node manufacturing. Therefore, each of the plurality of nodes 1-10 may have been pre-configured with the first parameter as part of the process of manufacturing the node. For each of the plurality of nodes, the first parameter may be stored in the node’s memory. Figure 1 (Not shown in the image). For each of the plurality of nodes 1-10, the first parameter may include one or more additional parameters. The pre-configuration of each of the plurality of nodes 1-10 having the first parameter can be performed by a mesh network provisioning process known in the art, such as a Bluetooth mesh network provisioning process known in the art. According to one or more embodiments of the invention, any one or more additional parameters of the first parameter may, for example, include a public key set, such as NetKey and AppKey known in the art. Such a public key set may be public to all nodes and may facilitate or allow initial node-to-node communication. Alternatively or additionally, any one or more additional parameters of the first parameter may include another or other types of pre-configured mesh network information for facilitating or enabling initial node-to-node communication.

[0037] The plurality of nodes 1-10 includes at least one first node and a plurality of second nodes, wherein each of the at least one first node is communicatively coupled or combinable to server 20, and server 20 stores node identifiers and corresponding node security keys for the respective nodes among the plurality of nodes 1-10, wherein each of the second nodes is communicatively coupled to one of the at least one first node via a first mesh network. Figure 1 The embodiment of the invention shown includes multiple nodes 1-10 comprising two first nodes 1, 10 and eight second nodes 2-9. However, it should be understood that... Figure 1 The number of the first node and the number of the second node shown are based on an example, and the number of the first node and the number of the second node can be compared. Figure 1 The number of first nodes can be fewer or more than the number of second nodes. However, the number of first nodes is usually less than the number of second nodes (e.g., much less). There may be a single first node, with the rest being second nodes.

[0038] After each of the multiple nodes 1-10 is pre-configured with the first parameter, the node identifier and corresponding node security key (and any other first parameter) of the corresponding node in the multiple nodes 1-10 can be sent (e.g., uploaded) to the server 20 as part of the above mesh network provisioning process.

[0039] For each of at least some node identifiers, server 20 is configured to encrypt a second set of parameters for the corresponding node using its node security key. This second set of parameters enables each of the plurality of nodes 1-10 to communicate with at least one other node among the plurality of nodes 1-10 via a second mesh network. The second mesh network differs from the first mesh network. As described above, the first mesh network can be referred to as the "default" mesh network. In this context, the second mesh network can be referred to as the "new" mesh network.

[0040] Typically, server 20 is configured to send an encrypted second parameter set along with an identifier identifying the node corresponding to the corresponding second parameter set in the encrypted second parameter set to the first node. Each of at least one first node is configured to send its corresponding encrypted second parameter set to the second node via a first mesh network, the first nodes being communicatively coupled to each other via the first mesh network. Each of the plurality of nodes 1-10 is configured to decrypt its received encrypted second parameter set using its node security key.

[0041] according to Figure 1 The embodiments of the present invention shown, without losing their generality, involve first node 1 being communicatively coupled to second nodes 2-5 via a first mesh network, and first node 10 being communicatively coupled to second nodes 5-9 or 6-9 via the first mesh network. Furthermore, according to... Figure 1 The embodiment of the invention shown, and without loss of generality, is such that server 20 is configured to send an encrypted second parameter set together with an identifier that identifies the node corresponding to the corresponding second parameter set in the encrypted second parameter set to the first nodes 1 and 10.

[0042] As described above, for each of at least some node identifiers, server 20 is configured to encrypt the second set of parameters for the corresponding node using the node security key of the corresponding node. According to Figure 1In the embodiment of the invention shown, server 20 is configured to encrypt a second set of parameters for each node identifier using the node security key of the corresponding node. Typically, to determine which node identifier should be used for this operation, each of the second nodes can broadcast its node identifier via a first mesh network. At least one of the first nodes can receive the node identifiers of each of the second nodes via the first mesh network, and the first nodes are communicatively coupled to each of the second nodes via the first mesh network. Each of the at least one first node can send the received node identifier along with its own node identifier to the server. The aforementioned at least some node identifiers may include node identifiers received from the first nodes or may consist of node identifiers received from the first nodes.

[0043] according to Figure 1 As shown and as Figure 1 As shown by the arrows in the embodiment of the invention, each of the second nodes 2-9 can broadcast its node identifier via the first mesh network, and each of the first nodes 1 and 10 can receive the node identifiers of each of the second nodes 2-9 via the first mesh network. The first nodes 1 and 10 are communicatively coupled to each of the second nodes 2-9 via the first mesh network. Each of the first nodes 1 and 10 can send the received node identifier along with its own node identifier to the server 20. The aforementioned node identifiers may include or be composed of node identifiers received from the first nodes 1 and 10.

[0044] The steps of each of the second nodes 2-9 broadcasting its node identifier via the first mesh network, each of the first nodes 1 and 10 receiving the node identifier of each of the second nodes 2-9 via the first mesh network, and each of the first nodes 1 and 10 sending the received node identifier along with its own node identifier to the server 20 can also be performed (e.g., only once) when the multiple nodes 1-10 first start operating (e.g., powering on).

[0045] According to one implementation example, multiple nodes 1-10 may include or be included in lighting equipment, such as light poles that may be arranged along a road. Before installing the nodes (or lighting equipment) at their intended locations, second parameters for the second mesh network may be created, and these second parameters, along with node identifiers, may be sent or uploaded to server 20, for example, by the person installing the nodes.

[0046] Figure 2This is a schematic diagram of system 30 according to an embodiment of the present invention, used to illustrate further principles of one or more embodiments of the present invention. Figure 2 The system 30 shown in the figure and Figure 1 The system 30 shown is the same as or similar to that shown, and Figure 1 and Figure 2 The same reference numerals in the figures indicate the same or similar parts that have the same or similar functions.

[0047] As referenced above Figure 1 As described, and also according to Figure 2 In the embodiment of the invention shown, server 20 is configured to encrypt a second set of parameters corresponding to a node using its node security key. Encryption of the second set of parameters for each node corresponding to at least some node identifiers may include server 20 creating a data packet including the encrypted second set of parameters, wherein the data packet includes a header that includes the identifier of the node corresponding to the encrypted second set of parameters in the data packet. Figure 2 As shown and as Figure 2 As shown by the arrows in the embodiment of the invention, the encrypted second parameter set can then be sent by server 20 along with an identifier identifying the node corresponding to the corresponding second parameter set in the encrypted second parameter set to the first nodes 1 and 10. The encrypted second parameter set can be sent by server 20 in one or more messages. For example, for each of the first nodes 1 and 10, server 20 can send the encrypted second parameter set along with the identifier identifying the node corresponding to the encrypted second parameter set to the first nodes 1 and 10 separately.

[0048] According to one implementation example, server 20 can create a first message for first node 1, which may include five data blocks, including an encrypted second set of parameters encrypted using the node security keys of the corresponding nodes in first node 1 and second nodes 2-5. Server 20 can also create a second message for first node 10, which may include four data blocks, including an encrypted second set of parameters encrypted using the node security keys of the corresponding nodes in first node 10 and second nodes 6-9. Server 20 can then send the first message to first node 1 and the second message to first node 10. Each of the first nodes 1 and 10 can be communicatively coupled to or coupled to server 20 via one or more secure communication paths (e.g., via one or more secure communication paths known in the art).

[0049] Figure 3 This is a schematic diagram of a system 30 according to an embodiment of the present invention, used to illustrate further principles of one or more embodiments of the present invention. Figure 3The system 30 shown is Figure 1 or Figure 2 The system 30 shown is the same as or similar to the system shown, and Figure 4 and Figure 1 or Figure 2 The same reference numerals in the figures indicate the same or similar parts that have the same or similar functions.

[0050] As mentioned above (refer to the reference) Figure 1 As described, and also according to Figure 3 In the embodiment of the invention shown, each of the first nodes 1 and 10 is configured to send a corresponding encrypted second parameter set to the second nodes 2-9 via a first mesh network. The first nodes 1 and 10 are communicatively coupled to the second nodes 2-9 via the first mesh network. These transmissions are... Figure 3 The arrows between the nodes are indicated in the text.

[0051] For example, based on the above references Figure 2 The described implementation example shows that the first node 1 can send a first message to the second nodes 2-5, and the first node 10 can send a second message to the second nodes 6-9.

[0052] Figure 4 This is a schematic diagram of a system 30 according to an embodiment of the present invention, used to illustrate further principles of one or more embodiments of the present invention. Figure 4 The system 30 shown in the figure and Figure 1 , Figure 2 or Figure 3 The system 30 shown is the same as or similar to that shown, and Figure 4 and Figure 1 , Figure 2 or Figure 3 The same reference numerals in the figures indicate the same or similar parts that have the same or similar functions.

[0053] As referenced above Figure 1 As described and according to Figure 4 In the embodiment of the invention shown, each of the plurality of nodes 1-10 is configured to use its node security key to decrypt the encrypted second set of parameters it receives.

[0054] according to Figure 3The embodiment of the invention shown, and as indicated by the arrows between nodes traveling in the direction from second nodes 2-9 to first nodes 1, 10, each of the second nodes 2-9, after decrypting its encrypted second set of parameters, can send its acknowledgment to the first nodes 1, 10 via the first mesh network, the second nodes being communicatively coupled to the first nodes 1, 10 via the first mesh network. Furthermore, as indicated by the arrows between the first nodes 1, 10 and the server 20, each of the first nodes 1, 10 can send its acknowledgment, as well as any acknowledgments received from the second nodes 2-9, to the server 20 after decrypting its encrypted second set of communication parameters, wherein the first nodes are communicatively coupled to the second nodes 2-9 via the first mesh network.

[0055] After receiving confirmation from each of the multiple nodes 1-10, server 20 can then send the following command to each of the first nodes 1 and 10 ( Figure 4 (Not shown in the image) Each of the plurality of nodes 1-10 will then communicate via a second mesh network. Furthermore, each of the first nodes 1 and 10 can send commands to the second nodes 2-9 via the first mesh network, wherein the first nodes 1 and 10 are communicatively coupled to the second nodes 2-9 via the first mesh network. Alternatively or additionally, each of the first nodes 1 and 10 can forward commands received from server 20 to the second nodes 2-9 via the first mesh network, wherein the first nodes 1 and 10 are communicatively coupled to the second nodes 2-9 via the first mesh network.

[0056] Figure 5 This is a schematic flowchart illustrating a method 100 according to an embodiment of the present invention. Method 100 is in a system comprising multiple nodes, wherein each of the multiple nodes is pre-configured with a first parameter that enables the node to communicate with at least one other node among the multiple nodes via a first mesh network. For each of the multiple nodes, the first parameter includes a node identifier and a node security key, wherein the corresponding node identifier uniquely identifies the node, and wherein the corresponding node security key is unique for each node. The multiple nodes include at least one first node and multiple second nodes, wherein each of the at least one first node is communicatively coupled or combinable to a server, and the server stores the node identifiers and corresponding node security keys of the corresponding nodes among the multiple nodes, wherein each of the second nodes is communicatively coupled to one of the at least one first nodes via the first mesh network.

[0057] according to Figure 5The embodiment of the invention shown includes seven steps S101 to S107. However, each of steps S101 to S103 is optional and can be omitted.

[0058] In S101, method 100 includes the second node in which each second node broadcasts its node identifier via the first mesh network.

[0059] In S102, each of the at least one first node receives a node identifier via a first mesh network of each of the second nodes, and the first node is communicatively coupled to each of the second nodes via the first mesh network.

[0060] In S103, each of the at least one first node sends the received node identifier along with its own node identifier to the server.

[0061] In S104, for each of the at least some node identifiers, the server uses the corresponding node's node security key to encrypt a second parameter set for the corresponding node, wherein for each of the plurality of nodes, the second parameter set enables the node to communicate with at least one other node among the plurality of nodes via a second mesh network different from the first mesh network. Figure 5 In the embodiment of the present invention shown, in S103, at least some node identifiers include node identifiers received by the server from the first node or node identifiers received by the server from the first node.

[0062] In S105, the server sends the encrypted second parameter set along with an identifier that identifies the node corresponding to the corresponding second parameter set in the encrypted second parameter set to the first node.

[0063] In S106, each of the at least one first node sends a corresponding encrypted second parameter set to the second node via the first mesh network, and the first nodes are communicatively coupled to the second node via the first mesh network.

[0064] In S107, each of the multiple nodes uses its node security key to decrypt the encrypted second set of parameters it receives.

[0065] Then method 100 can end.

[0066] Figure 6 This is a schematic flowchart illustrating a method 100 according to an embodiment of the present invention. Figure 6 The method 100 shown is similar to Figure 5 The method 100 shown, and with Figure 5 The method shown is the same as 100, including steps S104 to S107. However, with Figure 5 Compared to method 100 shown, Figure 6 The method 100 shown does not include steps S101 to S103, and further includes additional steps S108 to S111 and steps S112 and / or S113. However, each of steps S108 to S111 and steps S112 and / or S113 is optional and can be omitted.

[0067] Figure 6 The method 100 shown includes: in S108, each second node, after having decrypted its encrypted second parameter set, sends its acknowledgment (i.e., acknowledgment that the encrypted second parameter set of each second node has been decrypted) to the first node via the first mesh network, and the second nodes are communicatively coupled to the first node via the first mesh network.

[0068] In S109, each of at least one first node, after having decrypted its encrypted second set of communication parameters, sends its acknowledgment and any acknowledgments received from the second node to the server, the first nodes being communicatively coupled to the second nodes via the first mesh network.

[0069] In S110, for each of the at least one first node, if within a selected time period after the first node sends the encrypted second parameter set to the second node, the first node has not received confirmation from the second node that the second node has decrypted its encrypted second communication parameter set, then the first node retransmits the encrypted second parameter set to the second node via the first mesh network at selected time intervals until the first node has received confirmation, wherein the first node is communicatively coupled to the second node via the first mesh network.

[0070] In S111, after receiving confirmation corresponding to each of the multiple nodes, the server sends the following command to each of the at least one first node: each of the multiple nodes will then communicate via the second mesh network.

[0071] In S112, each of the at least one first node sends a command to the second node via the first mesh network, which will subsequently be communicated via the second mesh network, wherein the first nodes are communicatively coupled to each other via the first mesh network. Alternatively or additionally, in S113, each of the at least one first node forwards the command received from the server to the second node via the first mesh network, wherein the first nodes are communicatively coupled to each other via the first mesh network.

[0072] Then method 100 can end.

[0073] Although the invention has been illustrated in the accompanying drawings and the foregoing description, such description is to be considered illustrative or exemplary, not restrictive; the invention is not limited to the disclosed embodiments. Other variations of the disclosed embodiments can be understood and implemented by those skilled in the art in practicing the claimed invention by studying the drawings, the disclosure, and the appended claims. In the appended claims, the word "comprising" does not exclude other elements or steps, and the indefinite articles "a" or "an" do not exclude a plurality. The fact that certain measures are recited in mutually different dependent claims does not imply that combinations of these measures cannot be advantageously used. Any reference numerals in the claims should not be construed as limiting the scope.

Claims

1. A method (100) in a system comprising multiple nodes, each of the multiple nodes being pre-configured with a first parameter, the first parameter enabling the node to communicate with at least one other node among the multiple nodes via a first mesh network, wherein for each of the multiple nodes, the first parameter includes a node identifier and a node security key of the node, wherein the corresponding node identifier of each of the multiple nodes uniquely identifies the node, and wherein the corresponding node security key of each of the multiple nodes is unique for the node, the multiple nodes comprising at least one first node and a plurality of second nodes, wherein each of the at least one first node is communicatively coupled to or capable of being communicatively coupled to a server, the server storing the node identifier and the corresponding node security key of the corresponding node among the multiple nodes, wherein each of the second nodes is communicatively coupled to one of the at least one first nodes via the first mesh network, the method comprising: For each of at least some of the node identifiers, the server uses the node security key of the corresponding node to encrypt (S104) the second parameter set of the corresponding node, wherein for each of the plurality of nodes, the second parameter set enables the node to communicate with at least one other node among the plurality of nodes via a second mesh network different from the first mesh network. The server sends the encrypted second parameter set together with an identifier that identifies the node corresponding to the corresponding second parameter set in the encrypted second parameter set to the first node (S105). Each of the at least one first node sends (S106) the corresponding encrypted second parameter set to the second node—which is communicatively coupled to the first node via the first mesh network; Each of the plurality of nodes uses its node security key to decrypt (S107) the encrypted second set of parameters received by the node; The server sends (S111) the following command to each of the at least one first node: each of the plurality of nodes will then communicate via the second mesh network.

2. The method according to claim 1, further comprising: Each of the second nodes broadcasts its node identifier via the first mesh network (S101); Each of the at least one first node receives (S102) the node identifier of each of the second nodes of the second nodes that are communicatively coupled to each other via the first mesh network. as well as Each of the at least one first node sends the received node identifier along with its own node identifier to the server (S103). The node identifiers mentioned therein include either the node identifiers received from the first node or are composed of the node identifiers received from the first node.

3. The method according to claim 2, wherein when the plurality of nodes are powered on for the first time, the following steps are performed: Each of the second nodes broadcasts its node identifier via the first mesh network. Each of the at least one first node receives, via the first mesh network, the node identifier of each of the second nodes of the second nodes—which are communicatively coupled to each other via the first mesh network—and Each of the at least one first node sends the received node identifier along with its own node identifier to the server.

4. The method according to any one of claims 1 to 3, further comprising: After each of the second nodes has decrypted its encrypted second parameter set, it sends (S108) an acknowledgment of the completion of the decryption to the first node via the first mesh network—the second node is communicatively coupled to the first node via the first mesh network. as well as Each of the at least one first node, after having decrypted its encrypted second set of communication parameters, sends an acknowledgment of the completion of the decryption and any acknowledgments received from the second node to which the first node is coupled via the first mesh network to each other (S109) to the server.

5. The method according to claim 4, further comprising: For each of the at least one first node, if the first node has not received confirmation from the second node—which is communicatively coupled to the first node via the first mesh network—that the second node has decrypted the encrypted second communication parameter set of the second node within a selected time period after the first node sends the encrypted second parameter set to the second node, then the first node retransmits (S110) the encrypted second parameter set to the second node via the first mesh network at selected time intervals until the confirmation has been received by the first node.

6. The method according to claim 4 or 5, wherein the step of the server sending the (S111) command further comprises: After receiving an acknowledgment corresponding to each of the plurality of nodes, the server sends (S111) the following command to each of the at least one first node: each of the plurality of nodes will then communicate via the second mesh network.

7. The method of claim 6, further comprising: Each of the at least one first node sends (S112) a command to the second node—which is communicatively coupled to the first node via the first mesh network—to which the first node is communicatively coupled to the second node via the first mesh network; or Each of the at least one first node forwards (S113) the command received from the server to the second node—which is communicatively coupled to the first node via the first mesh network.

8. The method according to any one of claims 1 to 7, wherein encrypting the second parameter set of the node corresponding to each of at least some of the node identifiers by the server comprises: The server creates a data packet that includes an encrypted second set of parameters, wherein the data packet includes a header that includes the identifier of the node in the data packet corresponding to the encrypted second set of parameters.

9. A system (30) comprising: Multiple nodes (1-10), each of the multiple nodes being pre-configured with a first parameter, the first parameter enabling the node to communicate with at least one other node among the multiple nodes via a first mesh network, wherein for each of the multiple nodes, the first parameter includes a node identifier and a node security key, wherein the corresponding node identifier of each of the multiple nodes uniquely identifies the node, and wherein the corresponding node security key of each of the multiple nodes is unique to the node; as well as Server (20); The plurality of nodes includes at least one first node (1, 10) and a plurality of second nodes (2-9), wherein each of the at least one first node is communicatively coupled to or capable of being communicatively coupled to the server, the node identifier and the corresponding node security key of the respective node are stored in the server, and each of the second nodes is communicatively coupled to one of the at least one first node via the first mesh network; in: For each of at least some of the node identifiers, the server is configured to encrypt a second set of parameters for the corresponding node using the node security key of the corresponding node, wherein for each of the plurality of nodes, the second set of parameters enables the node to communicate with at least one other node among the plurality of nodes via a second mesh network. The server is configured to send an encrypted second set of parameters, together with an identifier that identifies the node corresponding to the corresponding second set of parameters in the encrypted second set, to the first node. Each of the at least one first node is configured to send the corresponding encrypted second parameter set to a second node—to which the first node is communicatively coupled via the first mesh network; Each of the plurality of nodes is configured to use its node security key to decrypt the encrypted second set of parameters it receives; and The server is configured to send the following command to each of the at least one first node: each of the plurality of nodes will then communicate via the second mesh network.

10. The system of claim 9, wherein only the first node among the plurality of nodes is communicatively coupled to or capable of being communicatively coupled to the server.

11. The system according to any one of claims 9 to 10, wherein: Each of the second nodes broadcasts its node identifier via the first mesh network; Each of the at least one first node is configured to receive, via the first mesh network, the node identifier of each of the second nodes of the second nodes—the first nodes being communicatively coupled to each other via the first mesh network; and Each of the at least one first node is configured to send the received node identifier together with its own node identifier to the server, wherein the at least some of the node identifiers include or consist of the node identifiers received from the first node.

12. The system according to any one of claims 9 to 11, wherein at least one of the first mesh network and the second mesh network comprises a Bluetooth mesh network.

13. The system according to any one of claims 9 to 12, wherein the server includes a cloud server.

Images