Method and coordinator device for selectively debugging node devices in a network

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 device interact with each other to check and confirm that a coordinator time indication associated with a commissioning start time recorded by the coordinator device and a node time indication associated with a commissioning start time recorded by the node device are identical or very similar or close in time. The coordinator device then commissions the node device by adding the node device to the network created by the coordinator device. This ensures that only desired or intended node devices are added to 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 of a network, and more particularly, to a method and a coordinator device for selectively debugging node devices in a network. Background Art

[0002] Electrical or electronic devices such as lighting devices and IoT devices, as well as devices supporting enhanced machine type communications, such as eMTC, all include data communication capabilities and are often deployed in networks comprising multiple interconnected devices.

[0003] These devices, commonly referred to as node devices or terminal devices, or router devices, depending on their roles in different networks, may include communication interfaces, such as network adapters or transceiver modules, for communication between node devices, and may also communicate with remote devices (such as back-end devices or back-end servers).

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

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

[0006] For IoT node devices such as ZigBee node devices, commissioning is the first step in establishing a wireless IoT network. However, the commissioning process is generally open because the ZigBee coordinator device can join, pull, or collect any node device into its network as long as the node device searches for a network to join at the point in time when the network created by the coordinator device is available for joining.

[0007] When more than one coordinator device belonging to different networks performs a network joining action at the same time, the node device will randomly join the available networks. In this case, the node device is more likely to join the wrong network, which will cause network connectivity problems and generate operational conflicts.

[0008] One approach to ensuring that only a specific group of node devices will join a particular network is to have the coordinator device store the identifiers of the node devices that are permitted to join the coordinator device's network. However, this approach places an additional storage burden on the coordinator device and requires significant manual effort to enter the node device identifiers into the storage device. Furthermore, due to the uncertainty associated with the expected nodes in a particular network, this approach is largely impractical for practical applications.

[0009] US2016248629A1 discloses a debugging tool capable of configuring and debugging devices belonging to different ZigBee public profiles.

[0010] The "XBee / XBee-PRO S2C Zigbee RF module" proposes to prevent unwanted devices from joining the network by enabling permission to join for a short period of time when a new device needs to be added to the network.

[0011] "Understanding ZigBee Commissioning" (January 1, 2007) deals with the ZigBee joining process, preventing unexpected nodes from joining a ZigBee network. It discloses preventing unwanted devices from joining by pressing a button on the coordinator to allow devices to join for a period of time.

[0012] US2010150063A1 relates to a Zigbee joining process for reducing the possibility of unexpected nodes joining by using a time window during which the coordinator allows nodes to join.

[0013] US2016142263A1 relates to a wireless node and a method for operating the wireless node, wherein the wireless node comprises a controller arranged for wireless communication with at least one further wireless node in order to determine the capabilities of the wireless node and to create a network, wherein characteristics of the network depend on the capabilities of the wireless node.

[0014] Therefore, a debugging method is indeed needed to ensure that all node devices are able to join the correct IoT network. Summary of the Invention

[0015] In a first aspect of the present disclosure, a method for selectively debugging a node device by a coordinator device in a network is provided. The network is created by the coordinator device, and each of the coordinator device and the node device operates according to a time base and records a debugging start time. The method includes the following steps:

[0016] - The coordinator device transmits a network available message;

[0017] - receiving, by the coordinator device, a join request from a node device, where the join request includes a node time indication related to a commissioning start time of the node device;

[0018] - a determination by the coordinator device that the coordinator time indication matches the node time indication, and

[0019] - The coordinator device commissions the node device by joining the node device to the network.

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

[0021] In an embodiment, the coordinator time indication and the node device time indication include the debugging start time of the coordinator and the debugging start time of the node device respectively.

[0022] Specifically, the solution according to one embodiment of the present disclosure relies on the coordinator device checking that the debugging start times recorded by the coordinator device and the node device, respectively, and the debugging start times associated with the power-on times of the coordinator device and the node device, respectively, are the same or very similar in time or close to each other. The temporal proximity or equality between the power-on times of the coordinator device and the node device helps ensure that the network created by the coordinator device is the correct network for the node device to join. This is based on the assumption that the debugging of the coordinator device and the node device begins as soon as they are powered on.

[0023] In one embodiment, the method of the present disclosure is particularly advantageous when the coordinator device performs a double check with the node device to determine that the coordinator device and the node device are powered on at the same time or that the node device is powered on shortly after the coordinator device is powered on. In an embodiment related to this concept, the join request is transmitted by the node device in response to determining that the coordinator time indication matches the node time indication.

[0024] To implement the solution of the present disclosure, the coordinator device first transmits a network available message indicating the availability of the network created by the coordinator device. The network available message includes a coordinator time indication associated with the commissioning start time of the coordinator device. Upon receiving the network available message, the node device transmits a join request to the coordinator device, requesting to join the network created by the coordinator device. Transmission of the join request may be specifically dependent on the node device determining that the coordinator time indication matches a node time indication associated with the commissioning start time of the node device.

[0025] Thereafter, the coordinator device (again) determines and confirms that the coordinator time indication and the node time indication match each other, in order to determine that the commissioning start times of the coordinator device and the node device are the same or very similar to each other. Thereafter, the coordinator device commissions the node device by adding the node device to the network.

[0026] Thus, in one embodiment, the method of the present disclosure performs a bidirectional check of the commissioning start time of both the coordinator device and the node device, and allows the node device to join the network created or owned by the coordinator device only when the coordinator time indication and the node time indication associated with the commissioning start time of the coordinator device and the commissioning start time of the node device, respectively, match each other. This double check ensures that the network will only have node devices that are powered on at the same time or after the coordinator device is powered on to join the network, and that other node devices (such as node devices) that have been powered on for a period of time before the coordinator device is powered on will not accidentally or erroneously join the network.

[0027] The method does not require additional storage in the coordinator device for storing identifiers of node devices that are allowed to join the network, which is advantageous, especially considering that the coordinator device typically does not have a large storage capacity.

[0028] In one embodiment, selective debugging is basically achieved by turning on the coordinator device and the node devices at the same time, which is direct and easy to control and does not require special control instructions.

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

[0030] In this case, a node device seeking to join a network can operate in what is known as a passive scanning mode, i.e., the node device merely listens and waits for beacon messages, which are network availability messages indicating the presence or availability of a network created by a coordinator device. Receiving messages such as beacon messages allows the node device to check and determine whether the network is the correct one to join.

[0031] This allows the coordinator device to have greater flexibility in controlling when node devices are allowed to join the network. Specifically, when the coordinator device is powered on before the node devices, it can prepare to create the network and then send messages, instructions, or sensing to enable or power on the node devices that are inferred to be allowed to join the network. The coordinator device then broadcasts a beacon message inviting the node devices to join the network.

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

[0033] In this scenario, a node device seeking to join a network operates in what's known as active scanning mode. In this mode, a node device sends a beacon request message, requesting to join the network. Upon receiving the beacon request message, the coordinator device transmits a beacon message, a beacon response message, to the node device. The beacon response message includes a coordinator time indication, which is correlated with the coordinator device's commissioning start time. The node device then checks to see if the coordinator time indication matches the node time indication, thereby determining whether the network is the correct one to join.

[0034] The above interaction process between the coordinator device and the node device is easy to implement, especially for the assumption that the coordinator device and the node device are powered at the same time. The node device actively searches for available networks, which can help improve the overall debugging efficiency.

[0035] In one embodiment of the present disclosure, the step of determining that the coordinator time indication matches the node time indication includes the following steps:

[0036] - calculating, by the coordinator device, the time difference between the debugging start time of the coordinator device and the debugging start time of the node device, and

[0037] - The coordinator device determines that the time difference is less than a predefined threshold.

[0038] To determine whether the coordinator time indication matches the node time indication, the coordinator device checks whether the two devices started commissioning at approximately the same time. This is achieved 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 there is a match when the time difference is less than a predefined threshold (such as 10 seconds).

[0039] The node device determines in a similar manner whether the coordinator indication matches the node indication.

[0040] This determination step involves simple arithmetic operations and comparisons and can be easily performed by the coordinator device without requiring many computing resources.

[0041] In an embodiment of the present disclosure, the coordinator time indication related to the debugging start time of the coordinator device includes a first elapsed time from the power supply of the coordinator device to the network available message transmitted by the coordinator device, and the node time indication related to the debugging start time of the node device includes a second elapsed time from the power supply of the node device to the join request transmitted by the node device, and the calculation step includes calculating the time difference between the first elapsed time and the second elapsed time.

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

[0043] From the coordinator device side, the commissioning start time is calculated as the elapsed time from the time the coordinator device transmits a ready message indicating that commissioning has begun to the time the coordinator device transmits a network available message. Regardless of whether the node device is powered on at the same time as the coordinator device or after the coordinator device, its commissioning start time will simply be calculated from the time the node device is powered on to the time the node device transmits a join request.

[0044] Using relative time as time indication is advantageous because possible deviations of the system time of the coordinator device and the node devices can be offset, which helps ensure accurate implementation of the method. On the other hand, using absolute time as time indication is also easy and straightforward.

[0045] In another embodiment of the present disclosure, the coordinator device and the node device are synchronized and powered on substantially at the same time, the coordinator time indication related to the debugging start time of the coordinator device includes a first time when the coordinator device is powered on, the node time indication related to the debugging start time of the node device includes a second time when the node device is powered on, and the calculation step includes calculating the time difference between the first time and the second time.

[0046] This is particularly true when the coordinator and node devices are synchronized and powered simultaneously. In this case, the coordinator and node time indications can be absolute times. Absolute times can be equal to the power-on time of the coordinator or node device. The determination step is even more straightforward, as it involves a simple, mathematical calculation of the recorded power-on times of both devices.

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

[0048] As a supplementary measure to ensure that the coordinator device and the node devices can determine that their commissioning start times are the same or very similar, the coordinator device generates a limited number of flags within a short time window, such as a short time after the coordinator device creates the network. The coordinator device further includes a flag in each network available message transmitted within a short time window, thereby including such a flag.

[0049] The flag can be a random number. Since the number of flags is limited, the number of network availability messages transmitted that include the flag is also limited. Only node devices that were powered on within a short period of time will receive the network availability message along with the flag. Therefore, if a network availability message received by a node device includes this flag, the node device can determine that it was powered on at approximately the same time as the coordinator device.

[0050] Upon receiving a network available message including the flag, the node device first determines whether the coordinator's time indication matches the node's time indication and then checks whether the flag exists. This allows the node device to confirm, using two different criteria, that the coordinator's commissioning start time is the same as, or very similar to, its own commissioning start time. When transmitting a join request, the node device also includes the received flag in the join request.

[0051] Therefore, in an embodiment of the present disclosure, the step of determining that the coordinator time indication matches the node time indication further comprises determining that the flag matches one of a plurality of flags transmitted by the coordinator device.

[0052] If the flag included in the join request from the node device is a previously generated and transmitted flag, the coordinator device determines that the node device is acceptable to join the network. This is an additional measure to prevent the coordinator device from attracting unwanted or undesirable node devices into its network.

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

[0054] Therefore, it limits the transmission of the Network Available message, which can be a beacon response or a network beacon message, to a specific range. As an example, the transmission of the Network Available message is limited to node devices that are two hops away from the coordinator device. This means that if the node device receiving the Network Available message is more than two hops away, the Network Available message will be discarded, thereby avoiding unnecessary transmission of larger fields.

[0055] In one embodiment of the present disclosure, each of the coordinator device and the node device operates a medium access control MAC data processing protocol sublayer, wherein the coordinator time indication and the node time indication are respectively included in the MAC transmission offset field of the network available message and the join request.

[0056] The MAC sublayer is part of the data link layer defined by the Open Systems Interconnection (OSI) model, which conceptualizes how communication data should be processed between systems.

[0057] Transmitting messages exchanged between the coordinator device and the node devices, ie, the network available message including the coordinator time indication and the join request including the node time indication, as MAC sublayer messages has the advantage of reducing the amount of traffic in the wireless channel on which the network operates.

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

[0059] Message transmission from a source device to a destination device in a network typically involves the MAC sublayer and / or the network layer. For message broadcasts, the network layer typically relies on MAC sublayer broadcasts to deliver messages from the source device to the destination device. That is, if a message is traveling within the same network, it typically does not go to the network layer for data processing.

[0060] Therefore, in the present disclosure, the implementation of determining in the MAC layer that the coordinator time indication matches the node time indication is more efficient in terms of usage of computational resources. Overall, better performance is achieved by performing the determination at the lower MAC sub-layer.

[0061] A second aspect of the present disclosure provides a coordinator device, where the coordinator device is arranged to selectively debug node devices in a network based on the method according to the first aspect of the present disclosure, the network being created by the coordinator device.

[0062] A third aspect of the present disclosure provides a node device, where the node device is arranged to be selectively debugged based on the method according to the first aspect of the present disclosure.

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

[0064] The method of the present disclosure may be advantageously used to configure or commission a large number of node devices comprising lighting fixtures such as lighting features in a building or in a stadium.

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

[0066] The above and other features and advantages of the present invention will be best understood from the following description with reference to the accompanying drawings, in which the same reference numerals represent the same components or components that perform the same or equivalent functions or operations. BRIEF DESCRIPTION OF THE DRAWINGS

[0067] Figure 1 A diagram schematically shows two coordinator devices debugging multiple node devices.

[0068] Figure 2An embodiment of a method for creating a network by a coordinator device according to an embodiment of the present disclosure is schematically illustrated in the form of a flowchart.

[0069] Figure 3 An embodiment of a method for selectively debugging a node device by a coordinator device according to the present disclosure is schematically illustrated in the form of a flowchart.

[0070] Figure 4 An example of the detailed format of the MAC sublayer beacon payload is schematically shown.

[0071] Figure 5 An embodiment of a coordinator device arranged for selectively debugging node devices according to the present disclosure is schematically illustrated.

[0072] Figure 6 An embodiment of a node device arranged to be selectively debugged according to the present disclosure is schematically illustrated. DETAILED DESCRIPTION

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

[0074] The present disclosure is described in detail below with reference to lighting devices acting as node devices of a network, the network being created by a coordinator device commissioning 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 networks of various node devices having network communication connectivity, as indicated in the background section.

[0075] Figure 1 Diagram 100 schematically shows two coordinator devices 10 and 20 configuring a plurality of node devices 11 - 18 and 21 - 27 .

[0076] With the deployment of more and more Internet of Things (IoT) networks (such as ZigBee networks), it is common to have more than one network including multiple node devices in the same place (such as in the same building or around a community). Figure 1 In the figure shown, two networks 19, 29 created by two coordinator devices 10, 20 respectively exist at the same location.

[0077] After creating the corresponding networks 19, 29, the coordinator devices 10 and 20 operate to commission the node devices, i.e., the lighting devices 11-18 and 21-27, by adding the node devices to the networks 19, 29. In practice, based on the deployment or installation plan, it is required that some lighting devices should join a specific network, while other lighting devices should join other (multiple) networks. Figure 1 In the example of FIG, it is designed that lighting devices 11-18 will join the network 19 created by the coordinator device 10, and lighting devices 21-27 will join the network 29 created by the coordinator device 20, as shown in FIG. Figure 1 As shown by the dotted line in .

[0078] However, debugging node devices by, for example, two or more different coordinator devices may encounter an inconvenient problem, that is, some node devices may join the wrong network, especially when two coordinator devices 10, 20 operate simultaneously to join or pull node devices 11-18, 21-27 into the network 19, 29. Figure 1 In the example shown in FIG, the arrow for each node device indicates the network that the node device joins. It can be seen that node devices 13 and 27 are mistakenly pulled into the wrong network, as indicated by the arrows outside of node devices 13 and 27.

[0079] In such cases, it is very difficult for the customer to try to resolve the problem on their own. In fact, in most cases, a trained technician or engineer must be involved to resolve the problem.

[0080] Furthermore, during project development, many node devices will frequently join or leave network(s), which increases the chances for a node device to join the wrong network.

[0081] A method for selectively debugging node devices by a coordinator device will provide a solution for eliminating the above-mentioned problems, and the method will be described in detail below.

[0082] Figure 2 Exemplary steps of a method 30 for creating a network by a coordinator device according to an embodiment of the present disclosure are schematically shown in the form of a flowchart.

[0083] A coordinator device, such as a dongle or modem operating as a ZigBee coordinator, is a device that can start or create a network and is responsible for selecting a channel, a personal area network identifier (PAN ID), security policy, and stack configuration for the network. After the coordinator device has started the network, it can allow original devices, such as node devices or end devices, to join the network.

[0084] In the present disclosure, after the coordinator device is powered on and before it creates a new network, at step 31 "coordinator scans channels", such as Figure 1The coordinator device 10 of the coordinator device scans all channels to discover "Network Existence?", any possible existing networks created by different coordinator devices at step 32. Existing networks are open for node devices to join.

[0085] If the coordinator device 10 does not find any open or existing networks at step 32, it proceeds to step 35, "Coordinator Creates New Network," to create a new network. The coordinator device 10 may send a ready message to the mobile phone of the field engineer or technician, or turn on an optical indicator to indicate to the field engineer or technician that the node devices can be powered. The coordinator device 10 may also send a relay drive message to power the node devices 11-18. The coordinator device 10 then creates the new network 19.

[0086] If the coordinator device 10 receives a beacon message of network joining permission in some channel, that is, it is determined at step 32 that there is a network open and available for node devices to join, such as by Figure 1 If the coordinator device 20 creates the network 29 , the coordinator device 10 detects the commissioning start time of the network 29 and checks whether the commissioning start time of the existing network has been recently recorded at step 33 “Latest recorded commissioning start time of existing network?”

[0087] In the event that the commissioning start time of network 29 is significantly different from the commissioning start time of the new network 19 to be opened or created by the coordinator device 10, that is, the determination result of step 33 is negative, the coordinator device 10 will proceed to step 35 and prepare to create a new network as described above.

[0088] On the other hand, if the debugging start time of the existing network 29 indicates that the debugging start time has just been recorded, that is, the determination result of step 33 is affirmative, it is very likely that the debugging of the existing network 29 is still in progress. In this case, in order to prevent unnecessary node devices from being pulled into or added to the existing network 29, at step 34 "coordinator waits for a period of time", the coordinator device 10 will wait for a period of time, for example, several minutes, to ensure that its own debugging start time will be different from the debugging start time of the existing network 29.

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

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

[0091] Figure 3 Exemplary steps of a method 40 for selectively debugging node devices in a network by a coordinator device according to an embodiment of the present disclosure are schematically illustrated in the form of a flowchart.

[0092] use Figure 3 The method assumes that the coordinator device has been powered on and has created a network for the node device to join, which is achieved by transmitting, for example, a network allow join command allowing the node device to join. It is also assumed that all original node devices to be commissioned, that is, the original node devices to join the network created by the coordinator device, have also been powered on.

[0093] In addition to reference Figure 2 Besides the described concept of powering the coordinator device first and then subsequently powering the node devices, it is also possible that both the coordinator device and the node devices are synchronized in their system time and powered at the same time.

[0094] In step 41 , “the coordinator device and the node device record their respective debugging start times”. Both the coordinator device and the node device record the debugging start time, which may be an absolute time or a relative time.

[0095] An example of the commissioning start time recorded as an absolute time may be the system clock time when the coordinator device or the node device is powered on. This is applicable when the coordinator device and the node device are synchronized and powered on at the same time.

[0096] In contrast, when recording the commissioning start time as a relative time, the coordinator device counts its commissioning start time as 0 seconds and starts a timer that records the time elapsed since the commissioning start time. Zero seconds for the coordinator device can be the time when the coordinator device is powered on, or the time when the coordinator device transmits a ready message to cause a node device to be powered on. The coordinator device may also know the power-on time of an original or uncommissioned node device. In this case, once the node device is turned on or powered on, the coordinator device can record its commissioning start time.

[0097] In a similar manner, a node device records its commissioning start time as a relative time, which is typically the elapsed time from when the node device was powered on.

[0098] Therefore, the commissioning start time recorded as a relative time is a variable that increments as time elapses from when commissioning is deemed to have started to when the coordinator or node device transmits a message (which may be a network available message) or a join request, as described below.

[0099] Relative time is particularly applicable to scenarios where the coordinator device is first powered on and a period of time must be waited after powering on before a network is created for node devices to join. Those skilled in the art will appreciate that relative commissioning start time can also be applied to other scenarios, regardless of whether the coordinator device and node devices are synchronized or started simultaneously.

[0100] At step 42, "the coordinator device transmits a network available message, optionally including a coordinator time indication related to the commissioning start time of the coordinator device," the coordinator device transmits a network available message indicating that the network created by the coordinator device is now available to be joined. Furthermore, the network available message also includes the coordinator time indication, i.e., a time indication related to the commissioning start time recorded by the coordinator device, which is either an absolute time or a relative time.

[0101] According to the channel scanning mode adopted by the node device, the network available message may be different messages transmitted by the coordinator device in different ways.

[0102] With the active scanning method, node devices send beacon request packets to detect available networks. Therefore, the coordinator device does not have to send beacon packets all the time.

[0103] In practice, a raw or uncommissioned node device will issue a beacon request on some channel and wait for a response from the open network. Upon receiving a beacon request message from a node device, the coordinator device will transmit a beacon response to the node device. Optionally, the beacon response includes a node time indication related to the commissioning start time of the coordinator device.

[0104] Using the passive scanning method, the node device being debugged only listens for packets in the channel to check for available networks. The coordinator device will continue to send out network beacons to inform the node device and other node devices of the existence of the network it has created. The network beacon contains a coordinator time indication related to the commissioning start time of the coordinator device.

[0105] The coordinator time indication related to 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, which is defined in ZigBee 3.0, for example.

[0106] Figure 4 An example of a detailed format of a MAC sublayer beacon payload is schematically shown 50. Specifically, a reserved bit 51 and a Tx offset 52 may be used to implement transmission of a coordinator or node time indication, ie, a commissioning start time recorded by a coordinator device or a node device.

[0107] like Figure 4As shown, reserved bit 51 can be used to indicate whether selective debugging is applied or enabled. For example, when "01" is set for bits 16 and 17, it indicates that selective debugging is enabled.

[0108] In addition, "Tx offset" 52 can be used to store the debugging start time. This part contains 24 bits and can store absolute or relative time, which records the time when debugging started or the time elapsed from the start of debugging.

[0109] In addition to including the coordinator time indication in the transmitted network available message, the coordinator device may further generate and include a flag in the transmitted network available message.

[0110] 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 debugger is started.

[0111] Specifically, for the active scanning method, the coordinator device will receive many beacon requests at the beginning of the commissioning process, especially for large-scale networks. The coordinator will generate a limited number of flags based on the number of node devices to be commissioned or added to its network, and include the flags in the network available message (i.e., beacon response message) transmitted by the coordinator device. After a short period of time, the transmitted beacon response message will return to the normal state and will not include the random number.

[0112] For passive scanning, the coordinator device will always send network beacons and the node devices will only listen. The coordinator will control the network beacons containing random numbers for debugging in a similar manner to ensure that only the network beacons transmitted within a short period after the debugging process starts include the random number as a flag.

[0113] These special network beacons are broadcast to node devices, thus ensuring that all node devices powered at the time will receive the network beacon containing the random number. The time window for node devices to receive these random numbers is also very short, which makes it difficult to pull unwanted node devices into the network.

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

[0115] Return Reference Figure 3 , at step 43 , the node device that receives the network available message from the coordinator device compares the coordinator time indication and the node time indication and determines that the two time indications match each other.

[0116] 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. If the time difference is sufficiently small, for example, less than a predefined threshold such as 0.5 seconds, the node device determines that the commissioning start time in the network available message is similar to the commissioning start time of the node device. This indicates that the currently available network is the network that the node device should join.

[0117] If the network available message also includes a random number as a flag, the node device first confirms that the coordinator's time indication matches the node's time indication. Knowing that the currently available network is the correct one to join, the node device stores the random number received from the coordinator. Otherwise, it discards the random number and waits for another message to join another network.

[0118] After confirming that the network created by the coordinator device is the network it should join, at step 44 , the node device transmits a joining request, such as an association request, to the coordinator device.

[0119] When transmitting the join request, the node device also includes its commissioning start time in the join message, and optionally includes the received flag, so that the coordinator device can also check and confirm that the commissioning start time of the coordinator device and the commissioning start time of the node device match each other.

[0120] In the case where the commissioning start time is a relative time, the commissioning start time of the node device included as the node time indication in the join request is calculated from time zero until the join message is transmitted.

[0121] Those skilled in the art will appreciate that the node device may transmit a join request including its commissioning start time immediately after receiving the network available message. This still allows the coordinator device to determine in subsequent steps that the commissioning start time of the node device is the same as or very close to the commissioning start time of the coordinator device.

[0122] At step 45, the coordinator device receives the join request and checks to determine that the debug state time of the node device is similar to the debug start time of the coordinator device. The coordinator device may perform the check in the same manner as the node device.

[0123] In the case where the received flag is also included in the transmitted join request, the coordinator device also checks to see if the received flag is one of the flags it generated and transmitted to the node device. This further confirms 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.

[0124] When it is confirmed that the debugging state time of the node device is similar to or identical to the debugging start time of the coordinator device, at step 46 , the coordinator device will allow the node device to join the network, which may be performed according to a standard protocol.

[0125] As an example, the coordinator device can send an association response containing the short address of the node device to the node device. The node device will then apply the network key and issue a data request. The coordinator device then returns the network key to the node.

[0126] If the network key verification is successful, the commissioning process is complete. After commissioning, the Tx offset can still be used as the original parameter.

[0127] The above describes a method for selectively commissioning node devices by a coordinator device, which only allows node devices that are turned on or powered on at the same time as the coordinator device or a short time after the coordinator device to join the network created by the coordinator device. Therefore, only node devices that are expected to join the network will be pulled into the network, while preventing other node devices (such as those node devices that were powered on before the coordinator node device was powered on) from being mistakenly joined to the network.

[0128] Figure 5 A coordinator device 60 for executing the above method is shown in a schematic diagram.

[0129] The coordinator device 60 operates a communication interface 61, such as a network adapter or a transceiver, Tx / Rx, module is arranged to exchange messages or data packets, such as network available messages, join messages as described above, with the node devices in the network created by the coordinator device 60 wirelessly 52 or wired 53. The network protocol used to exchange data through the networked coordinator device and the node devices may include ZigBee TM 、Bluetooth TM , and WiFi-based protocols for wireless networks, as well as protocols such as DALI TM (Digital Addressable Lighting Interface), DSI (Digital Serial Interface), DMX (Digital Multiplex), and KNX (or KNX-based systems), as well as other proprietary protocols.

[0130] The coordinator device 60 further includes at least one microprocessor, μP, or controller 64, and at least one data repository or storage device or memory 65 for storing, for example, the network identification of the coordinator device 66 and information related to the node devices, such as the node device's identifier, ID, media access control MAC, address, and subscriber information. The data repository 65 may also store the commissioning start time recorded by the coordinator device 60. Instead of the data repository 65, a separate memory or storage device accessible by the at least one processor or controller 64 may be provided.

[0131] At least one microprocessor or controller 64 communicatively interacts with and controls the communication interface 61 and at least one data repository or storage device 65 via an internal data communication and control bus 69 of the coordinator device 60. The at least one microprocessor or controller 64 can operate one or more selective debugging algorithms or applications, such as a protocol stack for controlling the node device, and the node device 100 including the MAC sublayer function, to perform the above-described method of selectively debugging the node device.

[0132] Figure 6 In the schematic diagram, a node device 70 is shown, which is arranged to be configured according to the method described above. Figure 5 The coordinator device 60 is used for debugging.

[0133] The node device 70 includes a control part or control device 710 and a load, such as a lighting fixture or lighting device 720, which includes a lighting module 721, preferably a light emitting diode LED, a lighting module or multiple LED lighting modules, whose operation can be controlled by the control device 710 from a remote control device or through a remote control device, for example such as a remote or back-end server (not shown).

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

[0135] The control device 710 further includes at least one microprocessor, μP, or controller 75, and at least one data repository or storage device or memory 76 for storing address information 77 of the node device itself and other node devices, such as the node device's identifier, ID, media access control (MAC), address, and subscriber information. The data repository 76 may also store a coordinator time indication associated with the commissioning start time recorded by the coordinator device, received by the node device 70 from the coordinator device, and its own time indication associated with the commissioning start time recorded by the node device 70. In lieu of the data repository 76, a separate memory or storage device accessible by the at least one processor or controller 75 may be provided.

[0136] At least one microprocessor or controller 75 communicatively interacts with and controls the communication interface 71 and at least one data repository or storage device 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 a protocol stack of the node device 70 including MAC sublayer functionality, to interact with the coordinator device and execute methods selectively debugged by the coordinator device.

[0137] The lighting fixture or luminaire 720 is connected to and controlled by the data communication and control bus 79 via a connection link 74 by at least one microprocessor or controller 710 .

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

[0139] The present disclosure is not limited to the examples disclosed above, and those skilled in the art may modify and enhance it outside the scope of the present disclosure disclosed in the appended claims without applying creative skills and for any data communication, data exchange and data processing environment, system or network.

Claims

1. A method for selectively debugging node devices (11, 21) by a coordinator device (10, 20) in a network, wherein the network is created by the coordinator device (10, 20), the method comprising the following steps: The coordinator device stores (41) the debugging start time; Transmitting (42) a network available message by the coordinator device (10, 20); Receiving (44) a join request from the node device (11, 21) by the coordinator device (10, 20), the join request including a node time indication related to the commissioning start time of the node device; determining (45) by the coordinator device (10, 20) that the debugging start time of the coordinator device matches the node time indication, and The coordinator device (10, 20) commissions (46) the node device by adding the node device to the network.

2. The method of claim 1 , wherein the network availability message includes a coordinator time indication related to the commissioning start time of the coordinator device (10, 20), and the join request is transmitted by the node device (11, 21) in response to determining that the coordinator time indication matches the node time indication.

3. The method according to claim 1 or 2, wherein the transmitting step includes one of the following steps: the coordinator device (10, 20) broadcasts a beacon message indicating the availability of the network as the network available message, and in response to receiving a beacon request message from the node device (11, 21), the coordinator device (10, 20) transmits a beacon response message indicating the availability of the network as the network available message.

4. The method according to any one of the preceding claims, wherein the step of determining that the coordinator indication matches the node indication comprises the following steps: The coordinator device (10, 20) calculates a time difference between the debugging start time of the coordinator device (10, 20) and the debugging start time of the node device, and The coordinator device (10, 20) determines that the time difference is smaller than a predefined threshold.

5. The method according to claim 4, wherein the coordinator time indication related to the commissioning start time of the coordinator device (10, 20) includes a first elapsed time from when the coordinator device (10, 20) is powered on to when the network available message is transmitted by the coordinator device (10, 20), and the node time indication related to the commissioning start time of the node device includes a second elapsed time from when the node device (11, 21) is powered on to when the join request is transmitted by the node device (11, 21), and the calculating step includes calculating the time difference between the first elapsed time and the second elapsed time.

6. The method according to claim 4, wherein the coordinator device (10, 20) and the node device (11, 21) are synchronized and powered on at substantially the same time, the coordinator time indication related to the commissioning start time of the coordinator device (10, 20) includes a first time when the coordinator device (10, 20) is powered on, the node time indication related to the commissioning start time of the node device (11, 21) includes a second time when the node device (11, 21) is powered on, and the calculating step includes calculating a time difference between the first time and the second time.

7. The method according to any of the preceding claims, wherein the transmitted network available message further comprises one of a plurality of flags generated by the coordinator device (10, 20) within a time window after creation of the network, the join request further comprising the flag.

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

9. The method according to any one of the preceding claims, wherein the transmitted network available message is transmitted to node devices (11, 21) within a limited number of hops from the coordinator device (10, 20).

10. According to the method of any one of the preceding claims, each of the coordinator device (10, 20) and the node device (11, 21) operates according to a medium access control MAC data processing protocol sublayer, wherein the coordinator time indication and the node time indication are included in the MAC transmission offset field of the join request and the network available message, respectively.

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

12. A coordinator device (10, 20) arranged for selectively commissioning node devices in a network created by the coordinator device (10, 20) according to the method of any of the preceding claims.

13. A node device (11, 21) arranged to be selectively debugged according to the method according to any one of claims 1 to 12.

14. The node device (11, 21) according to claim 13, comprising a lighting fixture.

15. A computer program product, comprising a computer-readable storage medium storing instructions, wherein when the instructions are executed on at least one processor, the at least one processor is caused to perform the method according to any one of claims 1 to 12.

Images