Method for selectively commissioning node devices in a network and coordinator device - Patents.com

Abstract

A method for selectively commissioning node devices by a coordinator device in a network created by the coordinator device is disclosed. The coordinator device and the node devices interact with each other to check and confirm that the coordinator temporal indication of the commissioning start time recorded by the coordinator device and the node temporal indication of the commissioning start time recorded by the node devices are the same or very similar or close in time to each other. In this case, the coordinator device commissions the node devices by joining the network created by the coordinator device. This ensures that only desired or expected node devices join the network created and managed by the coordinator device.

Description

[Technical field]

[0001] The present disclosure relates generally to the field of managing node devices in a network, and more specifically to a method and a coordinator device for selectively commissioning node devices in a network. [Background technology]

[0002] For example, electrical or electronic devices with data communication capabilities, such as lighting devices and Internet of Things (IoT) devices, as well as devices supporting enhanced Machine-Type Communication (eMTC), are increasingly being deployed into networks of multiple interconnected devices.

[0003] Depending on their role in different networks, these devices, commonly referred to as node devices or terminal devices, or router devices, may include communication interfaces, such as network adapters or transceiver modules, for communication between node devices and possibly with remote devices, such as back-end devices or back-end servers.

[0004] The communications interface may operate according to network protocols for exchanging data by networked devices or nodes, such as, for example, specified ZigBee, Bluetooth, and WiFi based protocols for wireless networks, as well as wired bus networks such as DALI (Digital Addressable Lighting Interface), DSI (Digital Serial Interface), DMX (Digital Multiplex), KNX (and KNX-based systems), and proprietary communications technologies and protocols.

[0005] Furthermore, the communication interface may operate according to wireless mobile communication standards, such as, for example, specified 2G / 3G / 4G / 5G cellular communications, as well as other long-range wireless communication technologies, such as Long Range Wide Area Network (LoRaWAN) and Narrowband IoT (NB-IoT), or proprietary communication technologies, and / or wired data exchange communication technologies.

[0006] For IoT node devices, such as ZigBee node devices, commissioning is the first step to establish a wireless IoT network. However, the commissioning process is generally open in the sense that a ZigBee coordinator device can have, pull in, or attract node devices to its network, as long as the node devices are searching for a network to join at the time the network created by the coordinator device is open for participation.

[0007] If two or more coordinator devices belonging to different networks perform network join actions at the same time, the node devices will randomly join available networks, which makes it easier for the node devices to join the wrong network, causing problems in network connectivity and resulting in operation confliction.

[0008] A way to ensure that only a particular group of node devices join a particular network is to have the coordinator device store identifiers of the node devices that are allowed to join the coordinator device's network. However, this approach imposes extra storage burden on the coordinator device and requires significant manual effort to enter identifiers of the node devices into the storage means. Moreover, such an approach is inherently impractical for practical applications due to the uncertainties associated with the nodes expected in a particular network.

[0009] US2016248629A1 discloses a commissioning tool that can configure and commission devices that belong to different ZigBee public profiles.

[0010] The "XBee / XBee-PRO S2C Zigbee RF module" suggests that when a new device needs to be added to the network, it can prevent unwanted devices from joining by enabling short-time joining authorization on the network. Summary of the Invention [Problem to be solved by the invention]

[0011] Therefore, there is a real need for a commissioning method that ensures that all node devices are able to join the correct IoT network. [Means for solving the problem]

[0012] In a first aspect of the present disclosure, there is provided a method of selectively commissioning node devices by a coordinator device in a network created by the coordinator device, wherein each of the coordinator device and the node devices operates according to a time basis and records a commissioning start time, the method comprising: - sending, by the coordinator device, a network-available message; - receiving, by the coordinator device, from the node device, a join request including a node temporal indication regarding a commissioning start time of the node device; - determining, by the coordinator device, that a coordinator temporal indication matches a node temporal indication; - commissioning the node device by joining the node device to the network, by a coordinator device; A method is presented, including:

[0013] The present disclosure is based on the insight that a time-based selective commissioning method can be used to ensure that node devices join the correct or appropriate or intended network created by a coordinator device.

[0014] In one embodiment, the coordinator temporal indication and the node device temporal indication include a commissioning start time of the coordinator and the node device, respectively.

[0015] In particular, the solution according to one embodiment of the present disclosure relies on checking by the coordinator device that the commissioning start times recorded by the coordinator device and the node device, respectively, and relative to the powered-up times of the coordinator device and the node device, respectively, are the same or very similar or close in time to each other. The temporal proximity or equality between the powering up times of the coordinator device and the node device helps to ensure that the network created by the coordinator device is the correct network for the node device to join. This is based on a scenario in which the coordinator device and the node device start commissioning when they are powered up.

[0016] In one embodiment, the method of the present disclosure is particularly advantageous when the coordinator device performs a twofold check with the node device to determine that the coordinator device and the node device are powered up at the same time, or the node device is powered up shortly after the power-up of the coordinator device. In one embodiment for this scenario, the join request is transmitted by the node device in response to determining that the coordinator temporal indication matches the node temporal indication.

[0017] For the implementation of the solution of the present disclosure, the coordinator device first sends a network availability message indicating the availability of the network created by the coordinator device. The network availability message includes a coordinator temporal indication regarding the commissioning start time of the coordinator device. Upon receiving the network availability message, the node device sends a join request to the coordinator device, requesting to join the network created by the coordinator device. The sending of the join request may be specifically dependent on the node device determining that the coordinator temporal indication matches the node temporal indication regarding the commissioning start time of the node device.

[0018] The coordinator device then (again) determines and confirms that the coordinator temporal indication and the node temporal indication match each other, which determines that the commissioning start times of both the coordinator device and the node device are the same or very similar to each other. The coordinator device then commissions the node device by joining it to the network.

[0019] Therefore, in one embodiment, the method of the present disclosure performs a two-way check of the commissioning start times of both the coordinator device and the node device, and allows a node device to join a network created or owned by the coordinator device only if the coordinator temporal indication and the node temporal indication for the commissioning start times of the coordinator device and the node device, respectively, match each other. This double check ensures that only node devices that are turned on simultaneously with or after the power-up of the coordinator device join the network, and that other node devices, such as node devices that are already powered up before the power-up of the coordinator device, do not accidentally or erroneously join the network.

[0020] The method does not require extra storage by the coordinator device to store identifiers of node devices that are allowed to join the network, which is advantageous, especially considering that coordinator devices typically do not have powerful storage capabilities.

[0021] In one embodiment, selective commissioning is essentially achieved by turning on the coordinator device and the node devices simultaneously, which is simple and easy to control and does not require special control instructions.

[0022] In one embodiment of the present disclosure, the transmitting step includes broadcasting, by the coordinator device, a beacon message indicating availability of the network as a network available message.

[0023] In this case, a node device that wants to join a network can operate in a so-called passive scan mode, i.e., the node device just listens and waits for beacon messages, which are network availability messages that indicate the presence or availability of a network created by a coordinator device. By receiving such a beacon message, the node device can verify and determine whether the network is the correct network to join.

[0024] This allows the coordinator device to have more flexibility in controlling the time when the node devices are allowed to join the network. Specifically, if the coordinator device is turned on before the node devices, the coordinator device can prepare to create the network and send a message or instruction or an inducement to turn on or power up the node devices that are expected and allowed to join the network. The coordinator device then broadcasts a beacon message to invite the node devices to join the network.

[0025] In another embodiment of the present disclosure, the transmitting step includes transmitting, by the coordinator device, a beacon response message indicating availability of the network as a network availability message in response to receiving a beacon request message from the node device.

[0026] In this case, a node device that wants to join the network works in a so-called active scan mode. In this mode, the node device sends a beacon request message to request to join the network. Upon receiving the beacon request message, the coordinator device sends a beacon message, i.e. a beacon response message, to the node device. The beacon response message includes a coordinator temporal indication regarding the commissioning start time of the coordinator device. The node device then checks and determines whether the network is the correct network to join by checking whether the coordinator temporal indication matches the node temporal indication.

[0027] The above interaction procedure between the coordinator device and the node devices is easy to implement, especially in the scenario where the coordinator device and the node devices are powered up at the same time. The node devices' proactive search for available networks can help improve the overall commissioning efficiency.

[0028] In one embodiment of the present disclosure, the step of determining whether the coordinator temporal indication matches the node temporal indication comprises: - calculating, by the coordinator device, a time difference between a commissioning start time of the coordinator device and a commissioning start time of the node device; - determining, by the coordinator device, that the time difference is less than a predetermined threshold; Includes.

[0029] To determine that a coordinator temporal indication matches a node temporal indication, the coordinator device checks whether the two devices start commissioning at approximately the same time, which is accomplished by calculating the time difference between the commissioning start time of the coordinator device and the commissioning start time of the node device, and determining that a match exists if the time difference is less than a predefined threshold, such as 10 seconds.

[0030] The node device similarly determines that the coordinator indication matches the node indication.

[0031] Such a determination step involves simple arithmetic operations and comparisons and can be easily performed by the coordinator device without requiring significant computational resources.

[0032] In one embodiment of the present disclosure, the coordinator temporal indication regarding the commissioning start time of the coordinator device includes a first elapsed time from when the coordinator device is powered up to when a network available message is sent by the coordinator device, and the node temporal indication regarding the commissioning start time of the node device includes a second elapsed time from when the node device is powered up to when a join request is sent by the node device, and the calculating step includes calculating a time difference between the first elapsed time and the second elapsed time.

[0033] In this case, both the coordinator temporal indication and the node temporal indication are relative times calculated to indicate the commissioning start time of the coordinator device and the node device, respectively. This approach is generally applicable to various scenarios, regardless of whether the coordinator device and the node device are synchronized and / or powered up at the same time.

[0034] On the coordinator device side, the commissioning start time is calculated as the elapsed time from when the coordinator device sends a ready message indicating that commissioning has started to when the network available message is sent by the coordinator device. Whether the node device is started at the same time as the coordinator device or after the coordinator device, the commissioning start time of the node device will simply be calculated from the power-up of the node device to when the join request is sent by the node device.

[0035] The use of relative time as a time indication is advantageous in that possible deviations in the system times of, for example, the coordinator device and the node device can be offset, helping to ensure correct execution of the method, whereas the use of absolute time as a time indication is also simple and straightforward.

[0036] In a further embodiment of the present disclosure, the coordinator device and the node device are synchronized and powered up at substantially the same time, the coordinator temporal indication regarding the commissioning start time of the coordinator device includes a first time that the coordinator device was powered up and the node temporal indication regarding the commissioning start time of the node device includes a second time that the node device was powered up, and the calculating step includes calculating a time difference between the first time and the second time.

[0037] This is especially applicable when the coordinator device and the node device are synchronized and powered up at the same time. In this case, the coordinator temporal indication and the node temporal indication can be absolute time. The absolute time may be equivalent to the power-up time of the coordinator device or the node device. The determination step is even simpler since it involves a simple and arithmetic calculation of the recorded power-up times of both devices.

[0038] In one embodiment of the present disclosure, the transmitted network available message further includes a flag generated by the coordinator device within a time window after the creation of the network, and the join request further includes the flag.

[0039] As an additional measure to ensure that the coordinator device and the node devices can determine that their commissioning start times are the same or very similar to each other, the coordinator device generates a limited number of flags within a time window, such as a short period of time after the coordinator device creates the network. The coordinator device further includes one flag in each network availability message sent within the short period of time, and thus the network availability message includes such a flag.

[0040] The flag may be a random number. Since the number of flags is limited, the number of network availability messages that include the flag is also limited. Only node devices that are powered up within this short period will receive the network availability message with the flag. Therefore, a node device can determine that the node device is powered up at essentially the same time as the coordinator device if the network availability message it receives includes such a flag.

[0041] When a node device receives a network available message including a flag, it first determines that the coordinator temporal indication matches the node temporal indication, and then checks that the flag exists. This allows the node device to check that the commissioning start time of the coordinator device is the same or very similar to its own commissioning start time by two different criteria. And when sending a join request, the node device includes the received flag in the join request.

[0042] Therefore, in one embodiment of the present disclosure, the step of determining that the coordinator temporal indication matches the node temporal indication further includes determining that the flag matches one of a plurality of flags transmitted by the coordinator device.

[0043] The coordinator device determines that a node device is allowed to join the network if the flag included in the join request from the node device is a flag that was previously generated and transmitted, as an additional measure to prevent the coordinator device from drawing unnecessary or undesirable node devices into its network.

[0044] In one embodiment of the present disclosure, a network availability message is sent to node devices within a limited number of hops from a coordinator device.

[0045] This limits the transmission of the network availability message, which may be a beacon response or a network beacon message, to a specified range. As an example, the transmission of the network availability message is limited to node devices that are two hops away from the coordinator device, which means that if the node device receiving the network availability message is more than two hops away, the network availability message is discarded, thereby avoiding unnecessary transmission to a larger field.

[0046] In one embodiment of the present disclosure, each of the coordinator device and the node device operates according to a Medium Access Control (MAC) data processing protocol sublayer, and the coordinator temporal indication and the node temporal indication are included in a MAC transmission offset field of the network available message and the join request, respectively.

[0047] The MAC sub-layer is part of the data link layer defined by the Open System Interconnections (OSI) model, which conceptualizes how communication data should be handled between systems.

[0048] Sending messages exchanged between the coordinator device and the node devices, i.e., network availability messages including coordinator time indications and join requests including node time indications, as MAC sublayer messages has the advantage of reducing traffic on the wireless channels on which the network operates.

[0049] In one embodiment of the present disclosure, the determining step is performed by a MAC data processing protocol sublayer.

[0050] The transmission of a message from a source device to a destination device in a network usually involves the MAC sublayer and / or the network layer. For broadcasting a message, the network layer usually relies on the MAC sublayer broadcast to forward the message from the source device to the destination device. That is, the message usually does not go to the network layer for data processing if the message propagates within the same network.

[0051] Therefore, in the present disclosure, an implementation at the MAC layer that determines whether the coordinator temporal indication matches the node temporal indication is more efficient in terms of computational resource usage. Overall, better performance is achieved by making the decision at the lower MAC sublayer.

[0052] A second aspect of the present disclosure provides a coordinator device configured to selectively commission node devices in a network created by the coordinator device based on a method according to the first aspect of the present disclosure.

[0053] A third aspect of the present disclosure provides a node device configured to be selectively commissioned based on a method according to the first aspect of the present disclosure.

[0054] In one embodiment of the present disclosure, the node device includes a lighting fixture.

[0055] The methods of the present disclosure can be advantageously used to configure or commission a large number of node devices including lighting fixtures, such as lighting functions in a building or stadium.

[0056] In a fourth aspect of the present disclosure, there is provided a computer program product comprising a computer-readable storage medium storing instructions that, when executed on at least one processor, cause the at least one processor to perform a method according to the first aspect of the present disclosure.

[0057] The above and other features and advantages of the present disclosure will be best understood from the following description taken in conjunction with the accompanying drawings, in which like reference numerals indicate identical parts or parts performing the same or equivalent functions or operations, and in which: [Brief description of the drawings]

[0058] [Figure 1]1 illustrates a schematic diagram of two coordinator devices commissioning multiple node devices. [Diagram 2] 1 illustrates, in a flow chart type diagram, an embodiment of a method for creating a network by a coordinator device according to an embodiment of the present disclosure. [Diagram 3] 1 illustrates, in a flow chart type diagram, an embodiment of a method for selectively commissioning node devices by a coordinator device according to the present disclosure. [Figure 4] 13 illustrates an example of a detailed format of a MAC sublayer beacon payload. [Diagram 5] 1 illustrates an embodiment of a coordinator device configured to selectively commission node devices according to the present disclosure. [Figure 6] 1 illustrates generally one embodiment of a node device configured to be selectively commissioned in accordance with the present disclosure. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0059] Embodiments contemplated by the present disclosure will now be described in more detail with reference to the accompanying drawings. The disclosed subject matter should not be construed as being limited to only the embodiments described herein. Rather, the illustrated embodiments are provided as examples to convey the scope of the subject matter to those skilled in the art.

[0060] The present disclosure is detailed below with reference to lighting devices acting as node devices of a network created by a coordinator device that commissions the lighting devices in the network. Those skilled in the art will appreciate that the present disclosure is not limited to commissioning a network of lighting devices, but is applicable to a wide variety of networks of node devices capable of network communication connectivity, as illustrated in the Background section.

[0061] FIG. 1 shows a schematic diagram 100 in which two coordinator devices 10 and 20 configure a plurality of node devices 11-18 and 21-27.

[0062] As Internet of Things (IoT) networks, such as ZigBee networks, continue to evolve, they often include two or more networks with multiple node devices at the same site, such as within the same building or within a community neighborhood. In the diagram shown in Figure 1, two networks 19, 29 created by two coordinator devices 10, 20, respectively, exist at the same site.

[0063] After creating the respective networks 19, 29, the coordinator devices 10, 20 operate to commission the node devices, i.e., lighting devices 11-18, 21-27, by joining the node devices to the networks 19, 29. In practice, based on the deployment or installation plan, it is required that certain lighting devices should join a certain network, while other lighting devices should join other(s) network(s). In the example of Fig. 1, the lighting devices 11-18 are designed to join the network 19 created by the coordinator device 10, and the lighting devices 21-27 are designed to join the network 29 created by the coordinator device 20, as shown by the dashed lines in Fig. 1.

[0064] However, commissioning of these node devices, for example, by two or more different coordinator devices, may encounter complications. That is, some node devices may join the wrong network, especially when two coordinator devices 10, 20 operate simultaneously to join or attract node devices 11-18, 21-27 to networks 19, 29. In the example of FIG. 1, the arrows by each node device indicate the network that the node device joins. As shown by the arrows beside node devices 13, 27, it can be seen that node devices 13, 27 are mistakenly attracted to the wrong network.

[0065] In this case, it is very difficult for the customer to try to solve the problem themselves, and in most cases, a trained technician or engineer is required to solve the problem.

[0066] In addition, during the progress of a project, many node devices will frequently join or leave the network, increasing the possibility that a node device will join the wrong network.

[0067] The method of selective commissioning of node devices by a coordinator device, detailed below, provides a solution to avoid the above problems.

[0068] FIG. 2 illustrates, in a flow chart type diagram, exemplary steps of a method 30 for creating a network by a coordinator device according to one embodiment of the present disclosure.

[0069] A coordinator device, such as a modem or dongle acting as a ZigBee coordinator, is a device that can initiate or create a network and is responsible for selecting a channel, a personal area network identifier (PAN ID), a security policy, and a stack profile for the network. After initiating the network, the coordinator device can allow raw devices, such as node devices or end devices, to join the network.

[0070] In the present disclosure, after a coordinator device is powered up and before creating a new network, a coordinator device such as the coordinator device 10 of Fig. 1 scans all channels in step 31 "coordinator scanning channels" and discovers possible existing networks created by different coordinator devices in step 32 "network existing?" The existing networks are open for node devices to join.

[0071] If the coordinator device 10 does not find an open or existing network in step 32, the coordinator device 10 proceeds to step 35 “coordinator creating a new network” and creates a new network. The coordinator device 10 may send a ready message to the mobile phone of the field engineer or technician, or may turn on an optical indicator to indicate to the field engineer or technician that the node devices can be powered up. The coordinator device 10 may also send a relay drive message to power up the node devices 11-18. The coordinator device 10 then creates a new network 19.

[0072] If the coordinator device 10 receives a beacon message on a channel granting permission to join the network, i.e., if in step 32 it is determined that there is a network already opened and available for node devices to join, such as the network 29 created by the coordinator device 20 in FIG. 1, the coordinator device 10 detects the commissioning start time of the network 29 and checks in step 33 “commissioning start time of the existing network recently recorded?” whether the commissioning start time of the existing network has been recently recorded.

[0073] If the commissioning start time of the network 29 in question is significantly different from the commissioning start time of the new network 19 to be opened or created by the coordinator device 10, i.e., if the judgment result of step 33 is negative, the coordinator device 10 proceeds to step 35 and prepares to create the new network as described above.

[0074] On the other hand, if the commissioning start time of the existing network 29 indicates that the commissioning start time has just been recorded, i.e., the determination result of step 33 is positive, it is likely that the commissioning of the existing network 29 is still in progress. In this case, in order to prevent undesirable node devices from being drawn into or joining the existing network 29, in step 34 “coordinator waiting for a while”, the coordinator device 10 waits for a while, e.g., several minutes, so that its commissioning start time is different from the commissioning start time of the existing network 29.

[0075] The coordinator device 10 then proceeds to step 35 and prepares to create the new network 19. The coordinator device 10 may send a ready message to the mobile phone of the field engineer, or may turn on the lights to indicate to the field engineer that the node devices can be powered up. The coordinator device 10 may also send a relay drive message to power up the node devices 11-18.

[0076] The coordinator device 10 may create a new network 19 in a channel with less interference and send a network permit join command to allow the node devices to join the new network 19.

[0077] FIG. 3 illustrates, in a flow chart type diagram, exemplary steps of a method 40 for selectively commissioning node devices in a network by a coordinator device according to one embodiment of the present disclosure.

[0078] In the method of Figure 3, it is assumed that the coordinator device has already been powered up and created a network for the node devices to join. This is accomplished, for example, by sending a network-authorization join command to allow the node devices to join. It is also assumed that all row node devices to be commissioned, i.e., intended to join the network created by the coordinator device, are also powered up.

[0079] Besides the scenario described with reference to FIG. 2, in which the coordinator device is powered up first and then the node devices, it is also possible that both the coordinator device and the node devices are synchronized in their system time and powered up at the same time.

[0080] In step 41 “coordinator device and node device recording respective commissioning start time”, both the coordinator device and the node device record the commissioning start time, which may be an absolute time or a relative time.

[0081] An example of a commissioning start time recorded as an absolute time is the system clock time when the coordinator device or the node device is powered up, which is applicable when the coordinator device and the node device are synchronized and powered up at the same time.

[0082] In contrast, when recording the commissioning start time as a relative time, the coordinator device counts the commissioning start time as time 0 seconds and starts a timer to record the elapsed time from the commissioning start time. The 0 seconds of the coordinator device may be the time when the coordinator device is powered up, or may be the time when the coordinator device sends a ready message to power up the node device. It is also possible for the coordinator device to know the power-up time of a low or uncommissioned node device. In this case, the coordinator device can record the commissioning start time when the node device is turned on or powered up.

[0083] The node device also records the commissioning start time as a relative time, which is typically an elapsed time counted from when the node device was powered up.

[0084] Thus, the commissioning start time, recorded as a relative time, is a variable that increments over time from when commissioning is considered to have started until the coordinator or node device sends a message, which may be a network availability message or a join request, as described below.

[0085] The relative time is particularly applicable to a scenario where the coordinator device is powered up first and needs to wait for some time after being powered up before creating a network for the node devices to join in. Those skilled in the art can envision that the relative commissioning start time is also applicable to other scenarios, regardless of whether the coordinator device and the node devices are synchronized or not, or whether they start up at the same time or not.

[0086] In step 42 “the coordinator device transmitting a network-available message, optionally, comprising coordinator temporal indication related to commissioning start time of coordinator device”, the coordinator device transmits a network-available message indicating that the network created by the coordinator device is available for joining. Furthermore, the network-available message also includes a coordinator temporal indication, i.e. a time indication, related to the commissioning start time recorded by the coordinator device, which may be either an absolute time or a relative time.

[0087] Depending on the channel scanning mode adopted by the node device, the network availability message may be a different message sent by the coordinator device in different manners.

[0088] In the active scan method, a node device sends out a beacon request packet to detect an available network, so the coordinator device does not need to send a beacon packet all the time.

[0089] In practice, a raw or uncommissioned node device will send out a beacon request on a channel and wait for a response from the open network. When the coordinator device receives a beacon request message from a node device, it will send a beacon response to the node device. Optionally, the beacon response includes a coordinator temporal indication regarding the commissioning start time of the coordinator device.

[0090] In the passive scanning method, the node device to be commissioned just listens to packets on the channel to check for available networks. The coordinator device keeps sending out network beacons to inform the node device and other node devices of the existence of the network created by the coordinator device. The network beacon includes a coordinator temporal indication of the commissioning start time of the coordinator device.

[0091] The coordinator temporal indication regarding the commissioning start time of the coordinator device in the beacon response or network beacon message may be included as a MAC sublayer beacon payload parameter, for example as defined in ZigBee 3.0.

[0092] 4 shows a schematic diagram of an example of a detailed format of a MAC sub-layer beacon payload 50. In particular, a Reserved bit 51 and a Tx Offset 52 may be used to realize the transmission of a coordinator or node temporal indication, i.e. the commissioning start time recorded by the coordinator device or the node device.

[0093] 4, reserved bit 51 may be used to indicate whether selective commissioning is applied or enabled. For example, if "01" is set in bits 16, 17, this indicates that selective commissioning is enabled.

[0094] Additionally, "Tx Offset" 52 may be used to store the commissioning start time. This section contains 24 bits and may store an absolute or relative time that records the time when commissioning started or the time since commissioning started, respectively.

[0095] In addition to including a coordinator temporal indication in the transmitted network availability message, the coordinator device may further generate a flag to include in the transmitted network availability message.

[0096] The flag may be a random number generated by the coordinator device within a very short period of time, such as a small time window, from when the commissioning procedure begins.

[0097] Specifically, in the case of the active scanning method, especially in a large network, the coordinator device will receive many beacon requests at the beginning of the commissioning procedure. The coordinator generates a limited number of flags depending on the number of node devices to be commissioned or joined to its network, and includes the flags in the network availability message, i.e., the beacon response message, sent by the coordinator device after the short period of time returns to the normal state and does not include the random number.

[0098] In the case of passive scanning, the coordinator device will always send a network beacon and the node devices will just listen. The coordinator will also control the network beacon, which contains a random number used for commissioning, so that only network beacons sent within a short period after the start of the commissioning procedure will contain the random number as a flag.

[0099] These special network beacons are broadcast to node devices so that all node devices that are powered up at this time receive the network beacon containing the random number, and the time window for node devices to receive these random numbers is short, which makes it difficult to recruit unexpected node devices into the network.

[0100] The "Tx offset" 52 may also be used to store a flag generated by the coordinator device.

[0101] Returning to FIG. 3, in step 43, a node device receiving a network available message from a coordinator device compares the coordinator temporal indication with the node temporal indication and determines that the two temporal indications match each other.

[0102] Specifically, the node device calculates the time difference between the commissioning start time recorded by the coordinator device and the commissioning start time recorded locally by the node device itself. If the time difference is small enough, e.g., less than a predefined threshold, such as 0.5 seconds, the commissioning start time in the network available message is determined to be similar to the commissioning start time of the node device. This suggests that the currently available network is the network that the node device should join.

[0103] If the network availability message also contains a random number as a flag, the node device first determines whether the coordinator temporal indication matches the node temporal indication. If the node device finds that the currently available network is the correct network to join, it stores the random number received from the coordinator device. If not, the node device discards the random number and waits for another message to join another network.

[0104] After verifying that the network created by the coordinator device is the network that the node device should join, the node device sends a join request, such as an association request, to the coordinator device in step 44 .

[0105] When a node device sends a join request, it includes its own commissioning start time and, optionally, the received flag in the join message, so that the coordinator device may also check and verify that the coordinator device's commissioning start time and the node device's commissioning start time match each other.

[0106] If the commissioning start time is a relative time, the commissioning start time of the node device included as the node temporal indication in the join request is calculated from time 0 to the time the join message is sent.

[0107] Those skilled in the art can envision that a node device can send a join request including its commissioning start time immediately after receiving a network available message, which also allows the coordinator device to determine in a next step that the commissioning start time of the node device is the same or very close to the commissioning start time of the coordinator device.

[0108] In step 45, the coordinator device receives the join request and checks to determine that the commissioning start time of the node devices is similar to the commissioning start time of the coordinator device. The coordinator device can perform the check in the same way as the node devices.

[0109] If the sent join request also includes the received flag, the coordinator device checks that the received flag is one of the flags it generated and sent to the node device, which further verifies that the commissioning start time recorded by the coordinator device and the commissioning start time recorded by the node device are the same or very similar to each other.

[0110] Upon verifying that the commissioning start time of the node device is similar or the same as the commissioning start time of the coordinator device, in step 46 the coordinator device allows the node device to join the network, which may be performed according to a standard protocol.

[0111] As an example, the coordinator device may send an association response to the node device, including the short address of the node device. The node device then applies the network key and sends out a data request. The coordinator device then returns the network key to the node.

[0112] If the network key is successfully verified, the commissioning process is completed. After commissioning, the Tx offset may be used as the original parameter.

[0113] Thus, a method of selectively commissioning node devices by a coordinator device is described that allows only node devices that are turned on or powered up at the same time as or shortly after the coordinator device to join a network created by the coordinator device. This ensures that only node devices that are desirable to join the network are pulled into the network and prevents other node devices, such as node devices that are powered up before the coordinator node device is powered up, from being inadvertently joined to the network.

[0114] FIG. 5 shows in a schematic diagram a coordinator device 60 adapted to carry out the above described method.

[0115] The coordinator device 60 operates a communication interface 61, such as a network adapter or transceiver (Tx / Rx) module, for wireless (62) or wired (63) exchange of messages or data packets, such as the network availability messages, join messages, etc., described above, with the node devices in the network created by the coordinator device 60. Network protocols for exchanging data with the networked coordinator device and node devices may include ZigBee, Bluetooth, and WiFi based protocols for wireless networks, as well as wired bus networks such as Digital Addressable Lighting Interface (DALI), Digital Serial Interface (DSI), Digital Multiplex (DMX), and KNX (or a KNX-based system), as well as other proprietary protocols, etc.

[0116] Furthermore, the coordinator device 60 includes at least one microprocessor (μP) or controller 64 and at least one data repository or storage or memory 65 for storing information about the node devices, such as, among others, for example, the network identity 66 of the coordinator device, as well as the identifiers (IDs), Media Access Control (MAC) addresses, and subscriber information of the node devices. The data repository 65 may also store the commissioning start times recorded by the coordinator device 60. Instead of the data repository 65, a separate memory or storage accessible to the at least one processor or controller 64 may be provided.

[0117] At least one microprocessor or controller 64 communicatively interacts with and controls the communication interface 61 and at least one data repository or storage 65 via an internal data communication and control bus 69 of the coordinator device 60. The at least one microprocessor or controller 64 may operate the protocol stack of the node device 100, including, for example, one or more selective commissioning algorithms or applications and MAC sublayer functions for controlling the node device, and perform the method of selectively commissioning the node device described above.

[0118] FIG. 6 shows in a schematic diagram a node device 70 configured to be commissioned by the coordinator device 60 of FIG. 5 according to the method described above.

[0119] The node device 70 includes a controller or control device 710 and a load, such as a lighting fixture or lighting device 720, including a lighting module 721, preferably a Light Emitting Diode (LED) lighting module or a plurality of LED lighting modules. The operation of the load may be controlled by the control device 710 from or via a remote control device, such as a remote or back-end server (not shown).

[0120] The control device 710 operates a communication interface 71, such as a network adapter or transceiver (Tx / Rx) module, for short-range wireless (72) or wired (73) exchange of messages or data packets with other node devices in the network (i.e., so-called inter-node device communication), and with the coordinator device. Network protocols for exchanging data with the networked devices or nodes may include ZigBee, Bluetooth, and WiFi based protocols for wireless networks, as well as wired bus networks such as DALI (Digital Addressable Lighting Interface), DSI (Digital Serial Interface), DMX (Digital Multiplex), and KNX (or KNX-based systems), as well as other proprietary protocols.

[0121] Furthermore, the control device 710 includes at least one microprocessor (μP) or controller 75 and at least one data repository or storage or memory 76 for storing address information 77 of other node devices and the node device itself, such as, among others, node device identifiers (IDs), Media Access Control (MAC) addresses, and subscriber information. The data repository 76 may also store the coordinator temporal indication of the commissioning start time recorded by the coordinator device and its own temporal indication of the commissioning start time recorded by the node device 70, which the node device 70 receives from the coordinator device. Instead of the data repository 76, a separate memory or storage accessible to the at least one processor or controller 75 may be provided.

[0122] At least one microprocessor or controller 75 communicatively interacts with and controls the communication interface 71 and at least one data repository or storage 76 via an internal data communication and control bus 79 of the control device 710. The at least one microprocessor or controller 75 may operate one or more algorithms or applications and protocol stacks of the node device 70, including MAC sublayer functions, interact with the coordinator device, and execute methods selectively commissioned by the coordinator device.

[0123] Lighting fixtures or lighting devices 720 connect to a data communication and control bus 79 and are controlled from the data communication and control bus 79 by at least one microprocessor or controller 710 via connecting link 74 .

[0124] Those skilled in the art will appreciate that any electrical load other than or in addition to the lighting fixtures or lighting devices 720 may be connected to the control bus 79 via the connecting link 74, such as an access point device or a geographic routing device.

[0125] The present disclosure is not limited to the examples disclosed above, but can be modified and extended by those skilled in the art beyond the scope of the present disclosure disclosed in the appended claims, without the need to apply inventive skills, for use in any data communication, data exchange and data processing environment, system or network.

Claims

1. 1. A method of selectively commissioning node devices by a coordinator device in a network created by the coordinator device, the method comprising: storing, by the coordinator device, a commissioning start time; sending, by the coordinator device, a network availability message; receiving, by the coordinator device, a join request from the node device, the join request including a node temporal indication regarding a commissioning start time of the node device; determining, by the coordinator device, that the commissioning start time of the coordinator device matches the node temporal indication; commissioning, by the coordinator device, the node device by joining the node device to the network; A method comprising:

2. 2. The method of claim 1, wherein the network availability message includes a coordinator temporal indication regarding the commissioning start time of the coordinator device, and the join request is sent by the node device in response to determining that the coordinator temporal indication matches the node temporal indication.

3. 3. The method of claim 1 or 2, wherein the transmitting step includes either broadcasting, by the coordinator device, a beacon message indicating availability of the network as the network available message, and transmitting, by the coordinator device, a beacon response message indicating availability of the network as the network available message in response to receiving a beacon request message from the node device.

4. The step of determining whether a coordinator temporal indication matches the node temporal indication comprises: calculating, by the coordinator device, a time difference between the commissioning start time of the coordinator device and the commissioning start time of the node device; determining, by the coordinator device, that the time difference is less than a predetermined threshold; The method of any one of claims 1 to 3, comprising:

5. 5. The method of claim 4, wherein the coordinator temporal indication of the commissioning start time of the coordinator device comprises a first elapsed time from when the coordinator device is powered up to when the network available message is sent by the coordinator device, and the node temporal indication of the commissioning start time of the node device comprises a second elapsed time from when the node device is powered up to when the join request is sent by the node device, and the calculating step comprises calculating a time difference between the first elapsed time and the second elapsed time.

6. 5. The method of claim 4, wherein the coordinator device and the node device are synchronized and powered up at substantially the same time, the coordinator temporal indication of the commissioning start time of the coordinator device includes a first time that the coordinator device was powered up and the node temporal indication of the commissioning start time of the node device includes a second time that the node device was powered up, and the calculating step includes calculating a time difference between the first time and the second time.

7. 7. The method of claim 1, wherein the transmitted network availability message includes one of a plurality of flags generated by the coordinator device within a time window after creation of the network, and the join request includes the flag.

8. The method described in claim 7, wherein the step of determining that a coordinator temporal indication matches the node temporal indication includes determining that the flag included in the join request matches one of the plurality of flags.

9. The method according to claim 1 , wherein the transmitted network availability message is transmitted to node devices within a limited number of hops from the coordinator device.

10. 10. The method of claim 1, wherein each of the coordinator device and the node device operates according to a media access control (MAC) data processing protocol sublayer, and the coordinator temporal indication and the node temporal indication are included in a MAC transmission offset field of the network available message and the join request, respectively.

11. The method of claim 10 , wherein the determining step is performed by the MAC data processing protocol sublayer.

12. A coordinator device configured for selectively commissioning node devices in a network created by said coordinator device according to the method of any one of claims 1 to 11.

13. 12. A node device configured to be selectively commissioned in accordance with the method of any preceding claim.

14. The node device of claim 13 comprising a lighting fixture.

15. A computer program comprising instructions which, when executed on at least one processor, cause the at least one processor to perform the method of any one of claims 1 to 11.

Images