A METHOD OF AND AN ARRANGEMENT FOR COMMUNICATING BY A SERVER WITH A NODE DEVICE OF A NETWORK OF INTERCONNECTED NODE DEVICES

Abstract

A method (50) of and an arrangement for communicating, by a server, with a target node device in a network of operatively interconnected node devices, wherein each node device of the network comprises a first communication interface for direct wireless communication with the server, and a second communication interface for inter-node device communication. The server determines (51) a current communication status of a target node device based on a last received uplink message of the target node device, prior to initiating message exchange with the target node device. The server then may communicate directly (52) with the target node device via the first communication interface, or via at least one other or delegate node device of the network selected by the server (53).

Claims

1. A method of communicating between a server and a target node device operating in a network (30) of operatively interconnected node devices, each node device comprising a first communication interface and a second communication interface, wherein said first communication interface is arranged for direct uplink and downlink wireless message exchange via a wireless communication system between said server and a node device, and said second communication interface is arranged for inter-node device communication between node devices in said network, wherein said server is arranged for keeping a record of a last message exchanged with each node device, said method comprising: determining, by said server, prior to communicating with said target node device, a current communication status of said target node device, based on said last message exchanged with said target node device; communicating, by said server with said target node device, via said first communication interface of said target node device, if said determined communication status of said target node device indicates availability for data exchange via said first communication interface, and communicating, by said server, with said target node device, via at least one other node device of said network selected by said server, if said determined communication status of said target node device indicates non-availability for data exchange via said first communication interface; wherein the record comprises a time stamp of each last exchanged message and said communication status of said target node device is determined by said server to be non-availability for data exchange via said first communication interface when said last exchanged message with said target node device is exchanged at a point in time prior to a predetermined time period from determining said communication status by said server.

2. The method according to claim 1, wherein said record of a last exchanged message with a node device further comprises at least one of an identification of said node device, an address of said node device, a geographical location of said node device, a delivery status, and type of said last exchanged message.

3. The method according to claim 1, wherein said late exchanged message comprises an uplink message.

4. The method according to claim 1, wherein communicating, by said server, with said target node device, via at least one other node device comprises: transmitting, by said server, a downlink message to said at least one other node device, via said first communication interface of said at least one other node device, wherein said downlink message is of a type to be forwarded, by said at least one other node device via said second communication interface, to said target node device.

5. The method according to claim 4, wherein said downlink message comprises an activation command for activating said target node device.

6. The method according to claim 1, wherein communicating, by said server, with said target node device, via at least one other node device comprises: transmitting, by said server, a downlink message to said at least one other node device, via said first communication interface of said at least one other node device, wherein said downlink message comprises an instruction of requesting said other node device to transmit an activation command, via said second communication interface, to said target node device.

7. The method according to claim 4, further comprising receiving, by said server, an uplink response message transmitted from said target node device, via said first communication interface, in response to receiving said activation command; and communicating, by said server, with said target node device via said first communication interface of said target node device.

8. The method according to claim 1, wherein said communicating, by said server, with said target node device, via at least one other node device is performed according to one of a single hop and a multi-hop protocol, in particular wherein said multi-hop protocol is a flooding routing algorithm.

9. The method according to claim 1, wherein said communicating, by said server, with said target node device, via at least one other node device is performed according to a secure algorithm including at least one of data encryption, source validation and integrity check.

10. The method according to claim 1, wherein a number of said at least one other node device is limited, in particular, smaller than or equal to five.

11. The method according to claim 1, wherein said at least one other node device is selected by said server based on at least one of a geographical distance between said at least one other node device and said target node device, and geographical locations of said at least one other node device and said target node device in said network.

12. The method according to claim 1, wherein said determining comprises determining a current communication status of a group of target node devices, and said communicating are performed for each target node device of said group of target node devices.

13. The method according to claim 1, wherein said node devices comprise lighting fixtures, and said communicating comprises exchanging control commands for controlling lighting of said lighting fixtures.

14. A communication arrangement comprising a server and a network of operatively interconnected node devices, each node device of said network comprising a first communication interface and a second communication interface, wherein said first communication interface is arranged for direct uplink and downlink wireless message exchange via a wireless communication system between said server and a node device, and said second communication interface is arranged for inter-node device communication between node devices in said network, wherein said server is arranged for keeping a record of a last message exchanged with each node device, wherein said server is arranged for: determining, prior to communicating with a target node device, a current communication status of said target node device, based on said last message exchanged with said target node device; communicating, with said target node device, via said first communication interface of said target node device, if said determined communication status of said target node device indicates availability for data exchange via said first communication interface, and communicating, with said target node device, via at least one other node device of said network selected by said server, if said determined communication status of said target node device indicates non-availability for data exchange via said first communication interface; wherein the record comprises a time stamp of each last exchanged message and said communication status of said target node device is determined by said server to be non-availability for data exchange via said first communication interface when said last exchanged message with said target node device is exchanged at a point in time prior to a predetermined time period from determining said communication status by said server; wherein said at least one other node device is arranged for: receiving, from said server, via said first communication interface, at least one of: a message to be forwarded to said target node device, and an instruction for requesting transmission of an activation command to said target node device, and transmitting, to said target node device, via said second communication interface at least one of: a message received from said server to be forwarded to said target node device, and an activation command to said target node device.

15. A computer program product comprising program code stored on a non-transitory computer readable medium, said program code arranged for performing said method according to claim 1, when said program code is executed by at least one processor.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

[0062] FIG. 1 illustrates, schematically, a diagram of an embodiment of a node device or terminal device arranged for operating in a network of operatively interconnected node devices, in accordance with the present disclosure.

[0063] FIG. 2 illustrates, schematically, an arrangement comprising a network of interconnected node devices as illustrated in FIG. 1 and a backend server, connected to the node devices via a wireless communication system, in accordance with an embodiment of the present disclosure.

[0064] FIG. 3 illustrates, in a flow chart diagram, an example of detailed steps of a method of communicating with a node device by a server in accordance with the present disclosure.

[0065] FIG. 4 illustrates, schematically, a secure transmission protocol applicable to the method of communication in accordance with the present disclosure.

DETAILED DESCRIPTION

[0066] The present disclosure is detailed below with reference to communication in a network of operatively interconnected node devices comprising lighting fixtures or lighting devices. Those skilled in the art will appreciate that the present disclosure is not limited to communication between node devices comprising lighting fixtures, but is equally applicable for communication with a wide variety of node devices enabled with data communication capabilities.

[0067] Throughout the description, the communication status of a node device is referred to as being unreachable for a remote or backend server when the first communication interface of the node device for direct communication with the server is in an inactive, sleep or power saving mode or even switched off, i.e. at least not in operation for receiving direct, i.e. downlink, DL, communication from the server. Further, the communication status of a node device is also referred to as being unreachable when the server cannot reach a node device caused by an incorrect or changed downlink data communication address of the node device, or the like.

[0068] FIG. 1 illustrates, schematically, a block diagram of an embodiment of a node device 10 arranged for operation in a network of operatively interconnected node devices, in accordance with the present disclosure.

[0069] The node device 10 comprises a control part or control device 11 and a lighting fixture or lighting device 12, comprising a lighting module 13, preferably a Light Emitting Diode, LED, lighting module or a plurality of LED lighting modules, operation of which may be controlled by the control device 11 from or through a remote control device, such as a remote or backend server (not shown), for example.

[0070] The control device 11 further comprises a first communication interface 14, such as a network adaptor or a transceiver, Tx/Rx 1, module, arranged for direct wireless message exchange or data packets 15 with such remote control device or backend server. The first communication interface 14 typically operates according to a mobile communication system technology in a licensed frequency band, such as 2G/3G/4G/5G cellular communication, and other long-range wireless communication technologies, such as known as Long Range Wide Area Network, LoRaWAN, and Narrowband IoT, NB-IoT, communication, for example. However, the first communication interface 14 may also operate according to a proprietary wireless communication protocol or technology.

[0071] The expression ‘direct wireless message exchange’ refers to downlink, DL, exchange of data via the first communication interface 14 over a wireless communication channel from a remote server to the node device 10, and uplink, UL, exchange of data via the first communication interface 14 from the node device 10 to the remote server, or the like.

[0072] The first communication interface 14 may be arranged for wired message exchange 16, such as for data exchange over an Ethernet connection or the like.

[0073] The control device 11 further comprises a second communication interface 17, such as a network adapter or transceiver, Tx/Rx 2, module arranged for short-range wireless 18 or wired 19 exchange of messages or data packets with another node device in the network, i.e. so called inter-node device communication. Network protocols for exchanging data by networked devices or nodes may comprise ZigBee™, Bluetooth™, as well as WiFi based protocols for wireless networks, and wired bus networks such as DALI™ (Digital Addressable Lighting Interface), DSI (Digital Serial Interface), DMX (Digital Multiplex), and KNX (or KNX based systems), and other proprietary protocols.

[0074] The control device 11 further comprises at least one microprocessor, μP, or controller 20, and at least one data repository or storage or memory 21, among others for storing computer program code instructions for operating the node device in accordance with the present disclosure, address information of the node device itself and other node devices, such as identifiers, IDs, Media Access Control, MAC, addresses and subscriber information of node devices. Instead of the repository 21, a separate memory or storage accessible to the at least one processor or controller 20 may be provided.

[0075] The at least one microprocessor or controller 20 communicatively interacts with and controls the first communication interface 14, the second communication interface 17, and the at least one repository or storage 21 via an internal data communication and control bus 23 of the control device 11. The first and second communication interfaces 14, 17 may be arranged for transferring/forwarding messages and data received by the node device 10 via the first communication interface 14 to another node device via the second communication interface 17.

[0076] The lighting fixture or lighting device 12 connects 24 to and is controlled from the data communication and control bus 23 by the at least one microprocessor or controller 20.

[0077] The second communication interface 17 is arranged for being active all the time, i.e. continuously staying in operation for receiving and transmitting inter-node communication messages, even when the node device 10 switches to a power saving or inactive mode, wherein some functional components or modules of the node device 10 are switched off, for example, among which the first communication interface 14, as a result of which direct communication between the node device 10 and a remote or backend server is not possible, i.e. the node device 10 is unreachable for a remote or backend server. Hence, via the second communication interface 17 inter-node device communication remains possible.

[0078] FIG. 2 illustrates, schematically, an hybrid communication arrangement, comprising a network 30 of a plurality of operatively and communicatively connected node devices 10, individually referred to as 10.sub.1, 10.sub.2, 10.sub.3, and 10.sub.4. Each node device 10 of the network 30 adopts a dual communication interface structure as described with reference to FIG. 1. That is, each node device 10 is arranged for direct message exchange 44—by its first communication interface 14—with a backend server 40 and a wireless communication system 45, such as a cellular communication system or a network using other long-range wireless communication technologies, as disclosed above. Reference numeral 43 refers to a communication interface of the server 40 arranged for communication over the wireless communication system 45, comparable to the first communication interface of a node device 10, as elucidated above.

[0079] The node devices 10 are arranged and connected for inter-node device communication by their second communication interfaces 17, illustrated by dash-dot lines 31. For simplicity sake, only four node devices 10 are shown in FIG. 2. In practice, however, the network 30 may comprise a large number of node devices 10, such as 30,000 or more, which may occupy a relatively large geographical area, such as lighting fixtures 12 mounted on lighting poles across a city or town.

[0080] In operation, each node device 10 transmits UL messages in a random fashion and/or time to the server 40, such as status data messages, acknowledgement of receipt messages, and heartbeat messages, for example. The server 40, in operation, the server 40 transmits DL control data messages to a node device 10.

[0081] The server 40 keeps a record 42 of UL and/or DL messages last received/transmitted from/to a respective node device 10.sub.1, 10.sub.2, 10.sub.3, 10.sub.4 in a database or storage or memory 41 accessible from the server 40.

[0082] In an embodiment of the present disclosure, the record 42 of a last exchanged message with a node device 10 comprises a time stamp of the last exchanged message and at least one of an identification of the node device 10, an address of the node device, and a geographical location of the node device.

[0083] Table 1 illustrates exemplary records 42, maintained by the server 40, of last received UL messages from several node devices 10 via the wireless communication system 45.

TABLE-US-00001 TABLE 1 Exemplary records of last received UL messages from node devices Device Device Time of last received Device ID address location uplink message 0001-2345-6789-0123 192.168.1.25 31.163868, 1546999809077 121.389519 0001-2345-6789-0124 192.168.1.26 31.163999, 1546999999022 121.389920

[0084] For each node device 10, table 1 comprises an identification of the node device, Device ID, which may be an arbitrary number, a device MAC address, an International Mobile Subscriber Identity, IMSI, or the like, a communication address of the first communication interface 14 of the node device, Device address, such as an Internet Protocol, IP, number IPv4, IPv6, mobile subscriber number, a geographic location of the node device, Device location, for example expressed in latitude and longitude coordinates of a geographic coordinate system, and time stamps of an uplink message last received from the node device 10, Time of last uplink message, in units of one millisecond, msec. or any other clock time related reference or unit.

[0085] In addition to or as an alternative of the time stamp referring to the last received uplink message, the record 42 may also comprise a time stamp referring to the last DL message transmitted from the server 40 to a respective node device 10. Further, the record 41 may comprise a delivery status or type of a last message transmitted to a node device, for example.

[0086] In table 1 above, the record 42 comprises metadata referring to the message last exchanged. In accordance with the present disclosure, keeping a record of a last message exchanged may also comprise storage of the content of the last message.

[0087] FIG. 3 illustrates, in a flow chart, an example of detailed steps of a method 50 of communicating with a node device 10 by a server 40 in accordance with the exemplary record 42 shown in Table 1 above. It is assumed that the server 40 intends to exchange a message or messages with the node device 10.sub.2 in FIG. 2, also called the target node device, having the device ID 0001-2345-6789-0123. The current time, expressed in the notation of Table 1 is assumed to be represented by 1547002509077. Further, after 10 minutes of inactivity, the first communication interface 14 of a node device 10 becomes unavailable for communication, i.e. goes into sleep mode, or change of IP address, etc.

[0088] Prior to initiating message exchange by the server 40 with the target node device 10.sub.2 via the wireless communication system 45, the server 40 determines a current communication status of the target node device 10.sub.2 based on the current time and the time of the last receive UL message from the target node device 10.sub.2, i.e. step 51 “Determining current communication status of target node device based on last exchanged message”.

[0089] For the node devices as illustrated in Table 1, a UL message from the target device 0001-2545-6789-0123 was last received by the server 2700000 units or msec., i.e. 45 minutes ago. Knowing the sleep mode cycle of the target node device 10.sub.2, the server 40 decides that the target node device is very likely unreachable via the communication system 45. That is to say, device 0001-2545-6789-0123 appears unreachable to the server 40.

[0090] Next, the server 40 determines whether at least one other node device 10 of the network 30 appears available for communication over the communication system 45. From checking the records 42 as shown in Table 1, it appears that the last UL message from node device 0001-2345-6789-9999, i.e. assume node device 10.sub.3 in network 30, is received 506732 msec. ago, i.e. less than 10 minutes ago. Hence, node device 10.sub.3 is most likely available and reachable via the communication system 45.

[0091] Accordingly, the server 40 determines that the target node device 10.sub.2 is available via inter-node device communication in the network 30 by the other node device 10.sub.3.

[0092] Hence, the server 40 selects the other node device 10.sub.3 as a delegate node device for exchanging a DL message with this other or delegate node device 10.sub.3 via the communication system 45 and the first communication interface 14 of this other node device 10.sub.3. That is step 53 “Communicating with target node device via at least one other node device if communication status indicates non-availability for data exchange via first communication interface”.

[0093] The DL message exchanged by the server 40 with the delegate node device 10.sub.3 may comprise information indicating to the delegate node device 10.sub.3 to which target node device a message is to be transmitted, and optionally how the message should be transmitted. As an example, the DL message may comprise one of a node device identification designating a specific target node device 10.sub.1, a group identification for designating a group of node devices as target node devices, a type of the message to be transmitted to a target node device by the other node device, such as a broadcast message identification for indicating a broadcast message, etc.

[0094] Dependent on the type of DL message received from the server 40, the selected other node device 10.sub.3 may transmit or relay the received DL message from the server 40, or a separate message, such as an activation command, for waking up one or a plurality of the target node devices, via the inter-node device communication of the network 30, i.e. the second communication interfaces 17.

[0095] When the DL message received by the delegate node device 10.sub.3 comprise an activation command for waking up or reconnecting to the target node device 10.sub.2, the target node device 10.sub.2 may activate its first transmission interface 14 and optionally transmit a response UL message, such as an acknowledgement message, a heartbeat message, or any other message to the server 40 via the communication system 45, to indicate to the server 40 that it is available for direct communication via its first communication interface 14.

[0096] Upon receiving such an optional message from the target node device 10.sub.2 by the server 40, i.e. optional step 54 “Receiving response from target node device”, the server 40, in step 55 “Communicating with target node device via first communicating interface”, may start direct message exchange between the server 40 and the target node device 10.sub.2. Direct communication between the server 40 and the target node device 10.sub.2 is the most efficient way of communication in this case.

[0097] It is noted that a response message, transmitted by the target node device 10.sub.2 to the server 40, may include the actual device address of the target node device 10.sub.2 for communication over the first communication interface 14, such that the server 40 is always aware of the actual communication address of the target node device 10.sub.2. In this manner, the method according to the present disclosure is also suitable for establishing communication with a target node device if the server 40, in step 52, determines from a delivery status of the last exchanged message, i.e. the last message transmitted from the server 40 to the target node device 10.sub.2, that this last message has not been received by the target node device 10.sub.2, for example.

[0098] Those skilled in the art will appreciate that the server 40 does not necessarily has to be informed of a power-save or sleep mode cycle of a node device 10. The server 40 may maintain a default power-save or sleep mode cycle for determining the communication status of a target node device, for example.

[0099] Hence, with the method of the present disclosure, ineffective communication between the server 40 and a sleeping node device or otherwise not reachable node device is prevented, such that available communication resources in the communication system 45 are not inefficiently occupied.

[0100] The activation command to be transmitted from the delegate or other node device 10.sub.3 to the target node device 10.sub.2, or group of target node devices, may be comprised in the instruction from the server 40, or created, compiled or generated by the delegate node device 10.sub.3 based on the instruction received from the server 40. Traffic load over the network 30 may be reduced by transmitting relative simple and straightforward instructions between the node devices.

[0101] As mentioned above, the delegate node device 10.sub.3 may directly relay a message received from the server 40 via its first communication interface 14 over the inter-node communication interfaces 17, such as for example a command to switch-off or switch-on a lighting module 13 of a lighting fixture 12 controlled by the target node device 10.sub.2.

[0102] However, in some circumstances or scenarios it may be contemplated that the target node device 10.sub.2 communicates with the server 40 through the second communication interface 17 and the intermediate or delegate node device 10.sub.3, for example in case of malfunctioning of the first communication interface 14 of the target node device 10.sub.2.

[0103] It can be contemplated that the delegate node device 10.sub.3 and the target node device 10.sub.2 may communicate wirelessly 18, via their second communication interfaces 17, respectively, if their physical or geographical distance or network locations indicate that the node devices are in each other communication range. That is, the server 40 may select the delegate node device not only based on availability for message exchange over the communication system 45, but also on the bases of its geographical location or distance to the target node device 10.sub.2, based on the device location information included in the record 42, see Table 1.

[0104] On the other hand, in some scenarios, the target device cannot be accessed by all selected delegation devices because of the limited range of their inter-node wireless communication. As an example, from FIG. 2, it can be seen that between node device 10.sub.4 and node device 10.sub.2 no inter-node device communication is possible. When node device 10.sub.4 is selected by the server 40 as delegate node device for reaching the target node device 10.sub.2, from one or more of the address for communication and/or the geographical location of the target node device 10.sub.2, for example, the delegate node device 10.sub.4 may determine that a DL message received from the server 40 for forwarding to or instructing the target node device 10.sub.2 may require at least one intermediate node device. Such that the transmission of the DL message or a respective instruction from the server has to be performed based on a multi-hop or mesh protocol in the network 30.

[0105] In practice, any available multi-hop protocol, such as ZigBee, Bluetooth, and the like may be used. In practice, a known flooding routing algorithm is sufficient for the purpose of relaying or delegating a DL message from the server to a target node device.

[0106] In order to avoid a broadcast storm in the network 30 of the node devices, only a predefined limited number of hops, e.g. 5 hops can be executed for the DL message. The number of hops can also be dynamically adjusted based on, for example, the distance between the other node devices and the target node device.

[0107] Furthermore, each of the other node devices may forward a DL message only one time to avoid multiple delivery of the same DL message from different other node devices to a target node device.

[0108] It will be appreciated that the server 40 may operate a plurality of delegate node devices simultaneously, to reach a particular target node device. For the purpose of efficient use of scarce transmission resources in the communication system 45. In an example at most five delegate nodes are operated by the server 40. This, also to avoid a data storm in the network 30.

[0109] On the other hand, if in step Slit is determined that a target node device is in a communication status for direct communication over the first communication interface 14, messages between the server 40 and with the target node device 10.sub.2 may be directly exchanged, i.e. step 52 “Communicating with target node device via first communication interface if communication status indicates availability for data exchange via first communication interface”.

[0110] Those skilled in the art will appreciate that step 51 may be performed by the server 40 once at the start or initiation of a message train to a node device, such that this step 51 is not performed each time for e message in a particular sequence. Step 51 may also be performed by the server 40 only after a certain time interval has been lapsed since a last status check for a particular node device, such as the time interval after which the node device enters its sleep mode or power-save mode, or after a default time period, as mentioned above.

[0111] An example of a UL message is a heartbeat message. Heartbeat messages are typically sent periodically to a destination on a non-stop basis from an originator's start-up until the originator's shutdown. When the destination identifies a lack of heartbeat messages during an anticipated arrival period, the destination may determine that the originator has failed, shutdown, or is generally no longer available. On the other hand, the heartbeat message may maintain the mapping of the Network Address Translation, NAT, consistent. Therefore, a node device sending heartbeat messages to a server enables the server to determine when the node device fails communication or is no longer available. When the node is available, from the heartbeat messages, the server knows the address of a node device to directly communicate with via the first communication interface.

[0112] By way of example, in prior art applications, a typical heartbeat message interval in the mobile operator's cellular network may range up to three minutes. After three minutes, the downlink message cannot be accepted by the node device, as the node device's address is not valid anymore because of a time-out of NAT mapping, or the node device goes into sleep mode, for example.

[0113] Assuming that the network 30 in accordance with the present disclosure is a street light system that comprises 36,000 node devices, and the node devices have an uplink message interval of 5 hours, which is 18,000 seconds. A simple calculation shows that the server 40 will roughly get every 0.5 seconds an uplink message from a node device, such as a heartbeat message, for example. If the time-out period is three minutes as mentioned above, this means that on average there are always around 360 node devices with an active communication status and that can receive downlink messages from the server 40 at any time. These active node devices may serve as a candidate for operating as a delegate node device to be selected by the server 40.

[0114] In a network with fewer node devices, a heartbeat message rate of less than 5 hour might be necessary. Anyhow, comparable to prior art systems, with the present disclosure the heartbeat rate may be much less or even completely absent, dependent on the nature of the arrangement.

[0115] It will be appreciated by those skilled in the art that the UL message may be any message, as long as it can facilitate the server to determine a current status of the node device 10 sending the UL message.

[0116] For the purpose of having a reasonable system efficiency, it is not necessary for the server 40 to inquire all node devices of a network for operating as a delegate node device. The server 40 may select only such node devices meeting set transmission and capacity and processing criteria, such as so as to have a balanced and sufficiently efficient system performance.

[0117] As an example, the server may select a node device distanced from the target node device by a distance smaller than a threshold value. As another example, the selected node device and the target node device are in a same cell of a mobile network, for example.

[0118] It is noted that direct communication between the target node device and the server may be based on commercial networks such as a cellular communication network, which are generally more secure and robust than inter-node communication in the network between the node devices. Against this background, it may be considered that the second communication interface is used only for the transmission or forwarding of an activation command and not for relay of messages from or to the server.

[0119] On the other hand, secure transmission may be implemented for both a DL message from the server 40 to the delegate node device 10.sub.3 and the (activation) message from the delegate node device 10.sub.3 to the target node device 10.sub.2.

[0120] FIG. 4 illustrates, schematically, a sequence of steps of a secure transmission protocol 60, applicable to the method of communication in accordance with the present disclosure. In FIG. 4, time runs from the top of the drawing to the bottom thereof.

[0121] The secure transmission proposed comprises two key parts, that is, source validation for validating whether the DL message is originated from the backend server 40, and an integrity check for the DL message. It is noted that the example as illustrated in FIG. 4 relates to a transmission protocol where the other or delegate node device or node devices 10.sub.3 forward a wake-up message received from the server 40, to a target node device or a group of target node devices 10.sub.2 without any further manipulation. Those skilled in the art will appreciate that the protocol may be adapted to a scenario where the delegate node device receives a first message from the server and then transmits a second message, different from the first message, to the target node device(s) which, however, will not be further elaborated here.

[0122] The protocol starts with step 61, “Create a common root wake-up key: K_wp, and an initial status value: WS_0”, where the server 40 creates a root wake-up key to be used by all the node devices, including the delegate or active node device 10.sub.3 and the target or inactive node device 10.sub.2, and sets an initial status at zero, or any other random integer.

[0123] Next, at step 62, “Send {K_wp, WS_0} protected in secure commissioning”, the created wake-up key and the initial status are sent to each node device 10.sub.2 and 10.sub.3, for example during commissioning of the node devices, ensuring secure transmission of the message.

[0124] At step 63, “Store K_wp and set device status DS=WS_0”, the node devices store the received common wake-up key K_wp, and set their device status DS in accordance with the received initial status, that is DS=WS_0.

[0125] The above steps take place at an initialization stage of a network of node devices, for example, during the commissioning of lighting fixtures of a street light system including a vast plurality of streetlights or lamp posts.

[0126] Next, when the server 40 determines that a specific target node device 10.sub.2 is inactive, and needs to be woken up, at step 64, the server 40 performs a number of operations to prepare an activation message, in this example a wake-up command, to be transmitted to the inactive target node device 10.sub.2, via the active other or delegate node device 10.sub.3. Specifically, the server 40 first creates a nonce M_ID, which is an arbitrary number, as the message ID. The server 40 then calculates, in accordance with a function F, a one-time wake-up key K_s=F(K_wp, M_ID), based on the root wake-up key and the message ID. Following that, the server sets the current status WS_n=WS_n−1+1, where n is the sequence number of the wake-up message. For example, for the first wake-up message (where n=1) send by the server 40, the current status will be calculated as: WS_1=WS_0+1. The last operation performed by the server 40 is to construct a wake-up command: wk_comm={payload, Hash(K_s, payload)}, where payload={M_ID, WS_n}, and Hash represents a hash function.

[0127] At step 65, “Send wk_comm protected in DTLS”, the wake-up command created at step 64 is transmitted from the server 40 to the active or delegate node device(s) 10.sub.3, via a Datagram Transport Layer Security, DTLS, protocol, which prevents the transmitted wake-up command from being eavesdropped, tampered or forged with. Alternatively, any other secure communication protocol may be applied, such as but not limited to Transport Layer Security, TLS, Internet Protocol Security, IPSec, etc.

[0128] At step 66, the delegate node device(s) 10.sub.3, which function as a relay device for transmitting the received wake-up command wk_comm to the target node device(s) 10.sub.2, checks whether the wake-up command is from a trustable source. Specifically, the target node device 10.sub.3 first checks if WS_n is larger than the device status DS. In case WS_n>DS, the wake-up key is calculated based on the root wake-up key and the message ID, i.e. calculate K_s same way. The hash value in the received wake-up command is verified by re-hashing the wake-up key and the payload. Upon successful verifying the hash value, that is, the received wake-up command is verified to be from a reliable source, i.e. the server 40, the device status DS is set equal to the received current status DS=WS_n.

[0129] The verified wake-up command is transmitted, transferred or forwarded to the target node device(s) 10.sub.2 at step 67. At step 68, the target node device 10.sub.2 again validates whether the wake-up command is from a trustable source, by way of the same method as used by the delegate node device 10.sub.3 at step 66.

[0130] After the wake-up command is validated and verified, the target node device 10.sub.2 transmits a heartbeat message to the server 40 at step 69, informing the server 2 that it is now available for communication directly, i.e. Heartbeat message including DS. Then, at step 70, the server 2 now communicates with the target node device 10.sub.2, now being active for direct communication with the server 40, by sending direct DL messages to the target node device 10.sub.2.

[0131] It will be appreciated that an embodiment of the present disclosure may also be any combination of the dependent claims and/or the above embodiments and a respective independent claim.

[0132] Other variations to the disclosed examples can be understood and effected by those skilled in the art in practicing the claimed disclosure, from a study of the drawings, the disclosure, and the appended claims. In the claims, the word “comprising” does not exclude other elements or steps, and the indefinite article “a” or “an” does not exclude a plurality. A single processor or transceiver or other unit may fulfil the functions of several items recited in the claims. The mere fact that certain measures are recited in mutually different dependent claims does not indicate that a combination of these measured cannot be used to advantage. A computer program may be stored/distributed on a suitable medium such as an optical storage medium or a solid-state medium supplied together with or as a part of the hardware, but may also be distributed in other forms, such as via the Internet or other wired or wireless telecommunication systems. Any reference signs in the claims should not be construed as limiting the scope thereof.