Inventors: Mark KEATING, Jwalant DHOLAKIA, Jonathan LLOYD, Glen RILEY, and

John WACLAWSKY

FIELD OE THE INVENTION

[001] The invention disclosed broadly relates to monitoring the quality of aggregated control links and lighting node operation in a mesh lighting network. More particularly, the invention relates to self-healing in a lighting network when lighting nodes are affected by poor link quality or experience operational degradation.

BACKGROUND OF THE INVENTION

[002] A system to control a distributed, mesh lighting network is disclosed in the co-pending US patent application serial No. 15/709,935, filed September 20, 2017, entitled“System and Method for Bottom -Up Invocation of Control Signal Repeaters in a Mesh Lighting Network”, incorporated herein by reference.

[003] During build-out of the mesh lighting network, when a new lighting device is installed, it is in a discovery mode in which it will periodically transmit a discovery message. When a commissioned node, a repeater node, or a gateway to the central management system receives the discovery message with an acceptable node identity and a sufficient link quality indication (LQI), the new lighting device may join the network and is commissioned. After the lighting device has become commissioned in the lighting network, if the network connection degrades too much or the device loses its connection to the network, it reverts to the discovery mode and, once again, will periodically transmit a discovery message.

[004] The mesh lighting network is self-organized via repeaters into a network of lighting nodes with repeaters fanning out control signals from a central management system to each lighting node. Lighting nodes with connectivity through one or more specific repeaters may be set up or dynamically combined to be managed as a group from a CMS or gateway. Each lighting node, in repeater mode, is capable of forwarding control signals to additional lighting nodes. During build-out of the mesh network, as new lighting nodes are installed, the control network automatically selects a node whose repeater function will provide the most efficient or reliable distribution of control signals to the new node or new group of nodes being installed.

[005] Occasionally, network, environmental or other factors, such as gateway or repeater hardware failures, interference due to weather conditions, noisy electronic devices and/or multipath radio propagation impacts or cable cuts, may cause signal degradation or loss in the aggregated links between a lighting node in the network and the central management system.

[006] What is needed is a way to monitor the quality of the aggregated links between a lighting node in mesh lighting network and the central management system, and to automatically command or allow a lighting node experiencing poor link quality, to enter a discovery mode to find a better quality link and rejoin the network.

[007] What is needed is a way to combine link quality monitoring with operational monitoring of a lighting node to determine whether the illumination by a node is failing.

[008] What is needed is a way to combine link quality monitoring with operational monitoring of a lighting node to detect a failing node and to compensate for illumination deficiencies of the failing node.

SUMMARY OF TUI INVENTION

[009] Example embodiments of the invention monitor the quality of the aggregated links between a lighting node in a mesh lighting network and a central management system. In accordance with the invention, when the central management system determines that a lighting node is experiencing poor link quality, it automatically commands the lighting node to disconnect from the network and enter the discovery mode to find a better quality link and rejoin the network, in a self-healing process. In addition, when a lighting node finds itself unable to communicate with the network it may decide to disconnect from the network on its own and enter discovery mode. [0010] In accordance with an example embodiment of the invention, the central management system polls lighting nodes with a real time status message (RTSM) command and the polled lighting node measures the received link quality indication (LQI) of the polling command. The received LQI is a characterization of the strength and/or quality of the received polling command frame and indicates any degradation in the aggregated links between the polled lighting node and the central management system. The polled lighting node acknowledges the command by transmitting back to the central management system a real time status message (RTSM) that includes in its payload the lighting node’s received link quality indication (LQI) of the polling command.

[0011] The central management system captures the received data and link quality indication (LQI) of the polling command as a link quality data point for the responding polled lighting node. The central management system tracks and accumulates the link quality data points received for each polled lighting node. The central management system also computes an average or other statistical characterization of link quality. The statistical characterization of a node’s link quality is compared with a threshold value, such as a threshold value for LQI. The comparison may indicate any degradation in the aggregated links between the polled lighting node and the central management system. If sufficient degradation in the link quality is indicated, then the central management system automatically commands the lighting node to disconnect from the network and enter a discovery mode to find a better quality link and rejoin the network. If commands can no longer flow to the lighting node or be accurately received by the lighting node then the lighting node will disconnect itself. When either of these conditions happen, the lighting node continues to operate on its current lighting schedule until it rejoins the network and receives a schedule update from the central management system.

[0012] If the discovery node is within radio range of a gateway, a new link may be formed with the gateway if the link quality indication (LQI) of the link is greater than a threshold discovery LQI. If the discovery node is beyond radio range of a gateway, the discovery node may then broadcast a repeater request message to nearby commissioned nodes. The central management system may permit a nearby commissioned node to become a repeater for the discovery node, and form a new link, if the link quality indication (LQI) of the link is greater than a threshold discovery value LQI.

[0013] In an example embodiment of the invention, operational monitoring of a lighting node may be included in the process of link quality monitoring. The lighting node may report its illumination and operational status in the payload of the real time status message (RTSM), along with the lighting node’s received link quality indication (LQI), in response to a polling command. The central management system receives the illumination and operational status of the responding lighting node to determine whether the illumination by the node is failing.

[0014] There are numerous embodiments possible for this invention, including embodiments that expand the concept of self-healing from a single node to groups of nodes that operate cooperatively to achieve a functional objective in the face of node degradation or failure. In a particular grouping example embodiment of the invention, upon determining that the node’s operation is failing, the central management system may optionally control the operation of nearby lighting nodes to compensate for any illumination deficiencies of the failing node. If the central management system detects a node problem, then nearby nodes may be logically grouped and their lighting

characteristics (intensity and color) changed and lighting direction controlled to compensate for illumination and color quality issues. The central management system monitors operation of the lighting node with the real time status message command, and receives the real time status message including an indication of status of the operation of the lighting node. The central management system compares the indication of status of the operation from the lighting node with an operational threshold value. When the status of the operation from the lighting node is indicated by the comparison as insufficient, the central management system designates one or more lighting nodes nearby the insufficient or degraded lighting node, as comprising a new lighting node group that includes the degraded lighting node. The central management system transmits one or more compensate commands to one or more lighting nodes in the new group, to modify its operation to compensate for the insufficiency of lighting due to a degraded node.

[0015] In accordance with an example embodiment of the invention, the central management system may compile a map of the accumulated link quality data points along with any illumination and operational status received for all of the polled lighting nodes, to map out the overall health of the network.

DESCRIPTION OF THE MOI RES

[0016] Figure 1 A illustrates an example network diagram of the central management system (CMS) connected over a wired or wireless connection to a gateway (GW) that wired or wirelessly communicates with a plurality of lighting nodes in a network. The central management system polls lighting nodes with a real time status message (RTSM) command and the polled lighting node measures the received link quality indication (LQI) of the polling command. The received LQI is a characterization of the strength and/or quality of the received polling command frame and indicates any degradation in the aggregated links between the polled lighting node and the central management system. The polled lighting node acknowledges the command by transmitting back to the central management system a real time status message (RTSM) that includes in its payload, the lighting node’s received link quality indication (LQI) of the polling command.

[0017] Figure 1B illustrates the example network of Figure 1 A, showing the CMS determining that Node N5 has poor link quality and in response, sending a command to Node N5 to disconnect from the control network and enter the discovery mode to find a better quality link and rejoin the network.

[0018] Figure 1C illustrates the example network of Figure 1B, showing Node N5 disconnecting from the control network and entering the discovery mode. The figure shows the discovery lighting node N5 attempting to wirelessly broadcast a discovery message to the wireless gateway GW1, however, the discovery node N5 is beyond radio range of the gateway GW 1.

[0019] Figure 1D illustrates the example network of Figure 1C, showing the discovery node N5 then broadcasting a repeater request message that is received by a nearby commissioned node N3. [0020] Figure 1E illustrates the example network of Figure 1D, showing the nearby commissioned node N3 receiving a command from the CMS to turn on its repeater function so that it can serve as a repeater for the discovery node N5.

[0021] Figure 1F illustrates the example network of Figure 1E, showing Node N5 discovering a better quality link L5 to the commissioned node repeater N3 and rejoining the network.

[0022] Figure 2A illustrates an example sequence diagram of the operation of the network shown in Figures 1 A to 1F, showing the CMS determining that Node N5 has poor link quality and in response, sending a command to Node N5 to disconnect from the control network and enter the discovery mode to find a better quality link and rejoin the network.

[0023] Figure 2B illustrates an example sequence diagram following the sequence shown in Figure 2A, showing the discovery lighting node N5 reconnecting to the network via the higher quality link L5 to the commissioned node repeater N3 and rejoining the network.

[0024] Figure 3 A illustrates an example network diagram of the central management system (CMS) connected over a wired or wireless connection to a gateway (GW) that wired or wirelessly communicates with a plurality of lighting nodes in a network. A commissioned lighting node N5 is shown with its illumination failing.

[0025] Figure 3B illustrates the example network of Figure 3 A, showing the central management system combining link quality monitoring with operational monitoring of a lighting node to determine whether the illumination by a node is failing. The central management system monitors operation of the lighting node with the real time status message and associated commands, and receives the real time status message including an indication of status of the operation of the lighting node from the lighting node, as well as the lighting node’s received link quality indication (LQI) of the polling command.

[0026] Figure 3C illustrates the example network of Figure 3B, showing the central management system comparing the indication of status of the operation from the lighting node with an operational threshold value. When the status of the operation from the lighting node is indicated by the comparison as insufficient or degraded, the central management system designates one or more lighting nodes nearby the degraded lighting node as comprising a new lighting node group which includes the degraded lighting node.

[0027] Figure 3D illustrates the example network of Figure 3C, showing the central management system transmitting compensate commands to at least one of the one or more lighting nodes in the new group, and to subsequently modify the operation of one or more nearby lighting nodes to compensate for the insufficiency of the degraded lighting node.

[0028] Figure 4 illustrates an example sequence diagram of the operation of the network shown in Figures 3 A to 3D, showing the central management system monitoring operation of the lighting node with the real time status message and associated

commands, and receiving the real time status message including an indication of status of the operation of the lighting node from the degraded lighting node. The central management system is shown transmitting compensate commands to at least one of the one or more lighting nodes in the newly formed group, to modify the lighting node’s operation to compensate for the insufficiency of the degraded lighting node.

[0029] Figure 5 is an example functional block diagram of the lighting device node N5, in accordance with an example embodiment of the invention.

[0030] Figure 6A is an example flow diagram of steps performed by the lighting node for encoding a message.

[0031] Figure 6B is an example flow diagram of steps performed by the central management system (CMS).

[0032] Figure 6C is an example flow diagram of steps performed by the central management system (CMS), for monitoring the status of the operation of the lighting node.

DISCUSSION OF THU PREFERRED EMBODIMENTS

[0033] Example embodiments of the invention monitor the quality of the aggregated links between a lighting node in a distributed, mesh lighting network and a central management system. The operation of the mesh lighting network and central management system are disclosed in the co-pending US patent application serial No. 15/709,935, filed September 20, 2017, entitled“System and Method for Bottom-Up Invocation of Control Signal Repeaters in a Mesh Lighting Network”, incorporated herein by reference. The mesh lighting network is self-organized via repeaters into a network of lighting devices with repeaters fanning out control signals from the central management system to each lighting device. Each lighting device, in repeater mode, is capable of forwarding control signals to additional lighting devices. During build-out of the mesh network, as new lighting devices are installed, the control network automatically selects a device whose repeater function will provide the most efficient or reliable distribution of control signals to the new device or new group of devices being installed.

[0034] In accordance with the invention, the central management system polls a lighting node in the mesh lighting network, sending a command message for the lighting node to measure a link quality indication (LQI) of the received command message. The lighting node returns a status message, including in its payload the measured LQI. The central management system computes from the lighting node’s status messages, a statistical characterization of the link quality of the lighting node and compares it with a threshold quality value. If the comparison indicates sufficient degradation in link quality, the central management system automatically transmits a disconnect command to the lighting node. In response, the lighting node disconnects and enters a discovery mode to find a better quality link to rejoin the network. In addition, when a lighting node finds itself unable to communicate with the network it may decide to disconnect from the network on it’s own and enter discovery mode.

[0035] In example embodiments of the invention, the central management system combines link quality monitoring with operational monitoring of a lighting node to determine whether the illumination by a node is failing. The central management system monitors operation of the lighting node with the real time status message and associated commands, and receives the real time status message including an indication of status of the operation of the lighting node from the lighting node, as well as the lighting node’s received link quality indication (LQI) of the polling command. [0036] In example embodiments of the invention, if a node has illumination problems or node failure occurs, then nearby nodes may be dynamically included in a new grouping of lights and their light output, color and/or orientation adjusted to mitigate or alleviate any illumination or color deficit issues caused by a degraded lighting node.

[0037] Figure 1 A illustrates an example network diagram of the central management system (CMS) 101 connected over a wired or wireless connection 104 to a gateway GW 1 that wired or wirelessly communicates with a plurality of lighting nodes Nl, N2, N3, N4, and N5 in a control network. There may be a plurality of lighting node devices in the distributed lighting network 104. Lighting node devices Nl, N2, N3, N4, N5, are in a branch along First Ave. Other branches, not shown, may light up parks, bridges, bike and hiking trails, parking lots, etc. Each lighting device includes an LED lighting array and digital components shown in Figure 5.

[0038] The central management system 101 polls lighting nodes, such as node

N5, with a real time status message (RTSM) command 150 and the polled lighting node N5 measures the received link quality indication (LQI) of the polling command 150. The received LQI is a characterization of the strength and/or quality of the received polling command frame 150 and indicates any degradation in the aggregated links, for example L4 and L5, between the polled lighting node N5 and the central management system 101. The polled lighting node N5 acknowledges the command 150 by transmitting back to the central management system 101 a real time status message (RTSM) 152 that includes in its payload, the lighting node’s received link quality indication (LQI) of the polling command 150. In addition (but not shown), repeater node N4 may optionally measure link quality about frames from N5 received by N4 and also report that to the CMS within the RTSM message 152.

[0039] Link Quality Indication (LQI) is a characterization of the strength and/or quality of a received frame, which is typically represented by an integer scale ranging from zero to 255. The reason for a low LQI value can be twofold: a low signal strength and/or high signal distortions that reduce the accuracy expectations of a received frame, for example by interference due to weather conditions and/or multipath propagation impacts and/or noise impacting cable runs. In some embodiments a low LQI value may be an indication of poor link quality. Therefore, a low LQI value may trigger a request for frame retransmission. High LQI values, however, are typically designed to indicate a sufficient signal strength and low signal distortions in a received frame. In this case the expectations are that the frame contains accurate data. Typically the LQI value is almost always high, for example 255, for scenarios with very low signal distortions and a signal strength much greater than a defined sensitivity level. In this case, the packet error rate tends towards zero and an increase of the signal strength, i.e. by increasing the transmission power, cannot decrease the error rate any further. This is only one example of the specification of LQI values. In other embodiments the meaning of the scale may be reversed and the range of LQI numbers may be different.

[0040] Received signal strength indication (RSSI) or energy detection (ED) may be used to evaluate the signal strength and also employed to determine if link

performance is acceptable. The received signal power, as indicated by received signal strength indication (RSSI) value or energy detection (ED) value, may not, by itself, characterize the signal quality and the ability to decode a signal. They are two of a number of measured or defined metrics that may be used to decide if a link is suitable for reliable data transmission.

[0041] LQI and RSSEED may be applied together, depending on the optimization criteria. If a low frame error rate (corresponding to a high throughput) is the optimization criterion, then the LQI value may be taken into consideration. If, however, the target is a low transmission power, then the RSSEED value is also helpful. Various combinations of LQI and RSSEED are possible for making communication decisions. As a rule of thumb, information on RSSEED is useful in order to differentiate between links with high LQI values. However, transmission links with low LQI values may be discarded from decisions, even if the RSSEED values are high, since RSSEED is merely information about the received signal strength, whereas the source of the signal strength may be an interferer.

[0042] Figure 1B illustrates the example network of Figure 1 A, showing the CMS

101 determining that Node N5 has poor link quality and in response, sending a command 154 to Node N5 to disconnect from the control network and enter the discovery mode to find a better quality link and rejoin the network.

[0043] The central management system 101 captures the received link quality indication (LQI) of the polling command 150, as a link quality data point for the responding polled lighting node N5. The central management system 101 tracks and accumulates the link quality data points received for each polled lighting node Nl, N2, N3, N4, and N5 and computes an average or other statistical characterization of the node’s link quality. The statistical characterization of the node’s link quality is compared with a threshold value, such as a threshold value for LQI. The comparison may indicate any degradation in the aggregated links L4 and L5 between the polled lighting node N5 and the central management system 101.

[0044] If degradation in the link quality is indicated, then the central management system 101 automatically commands the lighting node N5 by sending the disconnect command 154 to node N5 to disconnect from the network, and enter a discovery mode to find a better quality link and rejoin the network. When this happens, the lighting node N5 continues to operate on its current lighting schedule until it rejoins the network and receives a schedule update from the central management system 101.

[0045] Figure 1C illustrates the example network of Figure 1B, showing Node N5 disconnecting from the control network and entering the discovery mode. Node N5 reverts to the discovery mode and begins to periodically transmit a discovery message M5. The figure shows the discovery lighting node N5 attempting to wirelessly broadcast a discovery message M5 to the wireless gateway GW1, however, the discovery node N5 is beyond radio range of the gateway GW 1.

[0046] Figure 1D illustrates the example network of Figure 1C, showing the discovery node N5 continuing in a mode of being beyond radio range of the gateway GW1. Node N5 continues in the discovery mode and periodically broadcasts a repeater request message M5’ that is received by a nearby commissioned node N3, which replies with an acknowledgement ACK. It is possible that other commissioned nodes may also respond with acknowledgements. The discovery node N5 then transmits a unicast request message M5” to the nearby commissioned node N3. In response, the commissioned node N3 transmits a request N3’ to the central management system (CMS) to become a repeater for the discovery node N5.

[0047] The CMS Repeater Approval Timer (RAT) 148 is triggered whenever the

CMS 101 sends the command to a commissioned node (CN) to become a commissioned node repeater (CNR), to halt the creation of repeaters for some time period (typically 5 minutes). This ensures that all discovery messages that meet some efficiency or reliability criteria (in whitelist 145 and > Discovery LQI) will have time to be received by the CMS and be added to the commissioning queue, whether they are in range of the gateway or are forwarded via other repeaters. The RAT timer also resets whenever a discovery message is received.

[0048] Figure 1E illustrates the example network of Figure 1D, showing the nearby commissioned node N3 receiving a command 156 from the CMS to turn on its repeater function so that it can serve as a repeater for the discovery node N5. The central management system (CMS) verifies that the discovery node N5’s ID is in the whitelist 145, processes the request for discovery node N5 to determine the most efficient or reliable path (network) to use and log this best path, verifies that the repeater approval timer (RAT) 148 has expired, and sends an“operating parameter” command with “Repeater = True”, back to the selected commissioned node N3, commanding it to become a repeater (CNR). The central management system (CMS) then resets the RAT timer 148.

[0049] The repeater approval timer 148 in the central management system 101 starts the delay interval each time a command is transmitted to another lighting node to invoke the repeater function in the another lighting node, thereby automatically preventing an excessive number of repeaters being created in the wireless network. [0050] Figure 1F illustrates the example network of Figure 1E, showing Node N5 discovering a better quality link to the commissioned node repeater N3 and rejoining the network. The figure shows the discovery node N5 transmitting a discovery message M5 to the commissioned node repeater N3 for forwarding to the gateway GW 1 and the central management system (CMS). The repeated discovery message N2’ includes the received LQI or some other efficiency metric related to the discovery message as it was received by the repeater N3. The CMS 101 processes the single discovery message received via the repeater, sends an ACK l, if the received LQI, within the message payload of this example, is greater than or equal to the threshold Discovery LQI. The CMS then adds the node N5 to the commissioning Queue and logs it in the device table. The Repeater Approval Timer (RAT) 148 is reset.

[0051] The central management system 101 includes a processor 122 comprising a dual central processor unit (CPU) or multi-CPU 124/125, a random access memory (RAM) 126 and read only memory (ROM) 128. The memories 126 and/or 128 include computer program code, including control software 130. The memory 207 in the central management system 101 includes a node best path list 151. The memory 207 in the central management system 101 includes a node commission list 144, a whitelist 145, a set of link quality indication (LQI) threshold values 146 or contains other efficiency and reliability metrics, and a repeater approval timer (RAT) 148. The central management system 101 includes a wired or wireless communications unit transceiver 140 that includes a transmit/receive (TX/RX) buffer 142, which is configured to communicate via gateway GW 1 with the lighting node devices via the network 104. The communications unit 140 includes IEEE 802. xx and other communication protocols, depending the connectivity requirements between the CMS (101) and the gateway (GW1). Other examples of the network 104, include twisted pair, coax cable, Ethernet, Infrared, RFID, WiFi, Bluetooth, Bluetooth Low Energy, ultra-narrow band communications protocol from Sigfox, LTE-M, any Low Power Wireless Area Network (LPWAN) protocol, any M2M communication protocol, cellular, IEEE 802.15.4 RF, or LoRa Low Power Wide Area Network. The central management system 101 may include a radio

communications unit 140 that includes a transmit/receive (TX/RX) buffer 142 and optionally a cell phone transceiver and a WiFi transceiver to communicate with the lighting node devices 104 via radio communications units in the devices.

[0052] The central management system (CMS) 101 includes program software

130 in the memory 207, to send commands and interrogate RTSM responses from a lighting node. The program software 130 receives the RTSM with the link quality indication (LQI) or in other embodiments, other efficiency and reliability metrics. The program software 130 compares the LQI with a threshold LQI value. The program software 130 then sends a disconnect command to the lighting node if the LQI is less than the threshold value.

[0053] In one example embodiment, a node addressing scheme may be used by the CMS 101 to commission discovery nodes and to control and communicate with commissioned nodes and commissioned node repeaters. An example addressing scheme for the lighting nodes may include an address with fields for a customer ID, site ID, network ID, lighting group ID, which may indicate services grouping (parks, trails, streets, bridges, parking lots etc.) or functional grouping (motion detectors or cameras associated with the lighting node), device node ID, nearest street address, GPS location and device type, which may indicate device’s processor size and storage size. Either an installer or operation of a pre-existing lighting plan will have stored into the memory of a newly installed lighting node, one or more of the values for customer ID, site ID, network ID, lighting group ID, device node ID, nearest street address, GPS location, device type, processor size and storage size. When a discovery node broadcasts a discovery message, including its stored the address, which is received by the gateway GW 1 and CMS, the CMS stores the address in the node best path table 151. Every commissioned node served by the CMS, has its address stored in the node best path table 151, along with the address or identity of the gateway and any repeater through which the node communicates with the CMS.

[0054] In accordance with an example embodiment of the invention, the central management system 101 may compile a map of the accumulated the link quality data points received for all of the polled lighting nodes Nl, N2, N3, N4, and N5, to map out the overall health of the network. The central management system may cause a notice to be sent of the link quality of any of the lighting nodes Nl, N2, N3, N4, and N5.

[0055] Figure 2A illustrates an example sequence diagram of the operation of the network shown in Figures 1 A to 1F, showing the CMS 101 determining that Node N5 has poor link quality and in response, sending a command to Node N5 to disconnect from the control network and enter the discovery mode to find a better quality link and rejoin the network.

[0056] The central management system 101 polls lighting nodes, such as node N5

(which begins in this example as a commissioned node), with a real time status message (RTSM) command 150, for example, and the polled lighting node N5 measures the received link quality indication (LQI) of the polling command 150. This LQI is the link quality of frames received at node N5 from node N3. The polled lighting node N5 acknowledges the command 150 by transmitting back to the central management system 101 a real time status message (RTSM) 152 that includes in its payload, the lighting node’s received link quality indication (LQI) of the polling command 150. In addition, the link quality may also be reported for the frames received at node N3 from N5.

Optionally node N5 may also be forced into discovery, if its link quality has degraded sufficiently. In other embodiments of the invention, node N5 may be forced into discovery, if an LQI is below a threshold for messages passing in either direction on the L5 link.

[0057] If the CMS 101 determines that Node N5 has poor link quality from link

L5, it sends a disconnect command 154 to Node N5 to disconnect from the control network and enter the discovery mode to find a better quality link and rejoin the network. If N5 can no longer receive meaningful frames from N3, it will eventually time out and enter discovery mode.

[0058] The discovery lighting node N5 is shown initially attempting to wirelessly broadcast a discovery message M5 to the wireless gateway GW1, however, the discovery node N5 is beyond radio range of the gateway GW 1. The discovery node N5 then broadcasts a repeater request message M5’ that is received by a nearby commissioned node N3, which replies with an acknowledgement ACK. It is possible that other commissioned nodes may also respond with acknowledgements. The discovery node N5 then transmits a unicast request message M5” to the nearby commissioned node N3. In response, the commissioned node N3 transmits a request N3’ to the central management system (CMS) to become a repeater for the discovery node N5. The central management system (CMS) verifies that the discovery node N5’s ID is in the whitelist 145, processes the request for discovery node N5 to determine the most efficient or reliable path

(network) to use and log this best path, verifies that the repeater approval timer (RAT) 148 has expired, and sends an“operating parameter” command with“Repeater = True”, back to the selected commissioned node N3, commanding it to become a repeater (CNR). The central management system (CMS) then resets the RAT timer 148.

[0059] Figure 2B illustrates an example sequence diagram following the sequence shown in Figure 2A, showing the discovery lighting node N5 reconnecting to the network via the higher quality link L5 to the commissioned node repeater N3 and rejoining the network. The figure shows the discovery node N5 transmitting a discovery message M5 to the commissioned node repeater N3 for forwarding to the gateway GW 1 and the central management system (CMS). The repeated discovery message N3” includes the received LQI or some other efficiency metric related to the discovery message as it was received by the repeater N3. The CMS 101 processes the single discovery message received via the repeater, sends an ACK l, if the received LQI, within the message payload of this example, is greater than or equal to the threshold Discovery LQI. The CMS then adds the node N5 to the commissioning Queue and logs it in the device table. The Repeater Approval Timer (RAT) 148 is reset.

[0060] In example embodiments of the invention, the best path for maximizing reliability or speed of communication between a lighting node and the central

management system CMS, may be based on other metrics than the received link quality indication (LQI) of the discovery message. Example alternate metrics may include propagation delay of the discovery message, respective service group ID of the lighting node, respective functional group ID of the lighting node, respective processor size of the lighting node, and respective storage size of the lighting node. [0061] Another metric may be the relative priority of network traffic of the lighting group of which the lighting node is a member. For example, whichever node among several, has the larger processor, larger amount of storage, or better connections, would be selected by the CMS to handle the most important traffic having the highest relative priority, such as safety and security traffic from nodes associated with security cameras or motion detectors. If the lighting node is a member of a services group with security cameras, for example, then the lighting node may have traffic that is more important and is a higher relative priority than traffic from another grouping of simple street lights. Accordingly, the repeater selection criterion used by the CMS to support prioritized load balancing, gives the node associated with cameras, for example, the faster path through the more powerful repeater, for a more efficient communication path from the node to the CMS, thereby maximizing reliability or speed of communication between the lighting node and the CMS.

[0062] In embodiments of the invention, lighting networks may be designed as a plurality of partitioned lighting groups, where a group identified by a group ID may be composed of lighting nodes performing a specific function and producing network traffic having a relatively high priority. The associated repeaters in the group will only support nodes in the group having that specific function, as identified by the group ID. An example is lighting nodes having camera connections or motion detector triggers, which produce network traffic having a relatively high priority. In such cases, network traffic of a given relative priority may be directed to specific repeaters using the group ID and, when necessary, nodes of this group may be activated as repeaters to only provide connectivity to specifically dedicated groups of nodes having the same group ID, such as lights in a park or highway lights. Similarly, lighting on a bridge may utilize only repeaters dedicated for that purpose. This provides a significant advantage. For example, when activating repeaters for bridge lights or re-balancing bridge lighting, repeater creation and re-balancing activity can remain unaffected in other non-bridge lighting node groupings.

[0063] In embodiments of the invention, the CMS may employ multiple RATs and use them to assign different delay values for the Repeater Approval Timer (RAT) 148 to the different lighting groups, where speed is important either for initial group build-out, re-balancing of traffic flows, or recovery from an outage. This has the advantage that waits for the RAT to expire may be localized within lighting groups and not network wide. The rate of formation of new repeaters in a lighting group depends, in part, on the RAT 148 value assigned by the CMS to the group. To accelerate the initial creation of repeaters in a group, the CMS may dynamically change RAT values and assign a short duration RAT delay value when the rollout of the lighting group is started. Then, after a relatively small number of repeaters have been created in the group, in order to limit overpopulation of the repeaters in the group, the CMS may assign a longer duration RAT delay value.

[0064] The repeater approval timer (RAT) provides at least one of variable delay intervals for invoking the repeater function in lighting nodes of at least one individual group of lighting nodes or different delay intervals for invoking the repeater function in lighting nodes of different ones of a plurality of groups of lighting nodes.

[0065] In this manner, multiple Repeater Approval Timers 148 may be created by the CMS, with each separate RAT 148 associated with a respective service group, functional group, a group of geographically co-located lighting nodes, or any grouping of lighting nodes specified in a lighting plan. Different RAT timers may also have different delay values assigned by the CMS, which may vary from long to short delays, to adjust how quickly or often new repeaters can be activated, thereby accommodating different relative priorities of network traffic handled by respective groups of repeaters.

[0066] Figure 3 A illustrates an example network diagram of the central management system (CMS) 101 connected over a wired or wireless connection 104 to a gateway GW 1 that wired or wirelessly communicates with a plurality of lighting nodes Nl, N2, N3, N4, N5 in a network. Commissioned Node N2 illuminates area A2, commissioned Node N3 illuminates area A3 and commissioned Node N5 illuminates area A5. The commissioned lighting node N5 is shown with its illumination failing.

[0067] Figure 3B illustrates the example network of Figure 3 A, showing the central management system combining link quality monitoring with operational monitoring of a lighting node to determine whether the illumination by a node is failing. The central management system monitors operation of the lighting node with the real time status message and associated commands, and receives the real time status message including an indication of status of the operation of the lighting node from the lighting node, as well as the lighting node’s received link quality indication (LQI) of the polling command. The central management system 101 monitors operation of the lighting node N5 using real time status message 150. The figure shows the central management system 101 receiving the real time status message (RTSM) 152 including an indication of status of failing illumination of the lighting node N5 from the lighting node. The central management system may cause a notice to be sent of the operational status of the lighting node. The central management system may compile a map of the accumulated link quality data points along with any illumination and operational status received for all of the polled lighting nodes, to map out the overall health of the network.

[0068] Figure 3C illustrates the example network of Figure 3B, showing the central management system 101 comparing the indication of status of the operation from the lighting node N5 with an operational threshold value. When the status of the operation from the lighting node is indicated by the comparison as insufficient, because of illumination failing or color change, the central management system 101 designates one or more lighting nodes N2, N3, and N4 nearby the lighting node N5 as comprising a new lighting node group Gl, which includes the failing lighting node N5. The CMS may use node neighbor information compiled in the node neighbor table 149, to designate the one or more lighting nodes N2, N3, and N4 as being nearby the failing lighting node N5.

[0069] Figure 3D illustrates the example network of Figure 3C, showing the central management system 101 transmitting a compensate command 155 to the new lighting group nodes N2, N3, and N4, to modify their operation in such a way to compensate for the insufficiency of the lighting node N5, by increasing their

intensity/brightness, expanding their illumination area, or redirecting their illumination to the area A5 previously illuminated by node N5. Optimally, grouping may be logically accomplished internally within the CMS and individual commands may be issued from the CMS to the effected lighting nodes to modify their operation. Example modifications may include increased illumination, color change or direction orientation to compensate for an illumination deficiency at node N5.

[0070] Figure 4 illustrates an example sequence diagram of the operation of the network shown in Figures 3 A to 3D, showing the central management system 101 monitoring operation of the lighting node N5 with a command 150, and receiving the real time status message 152 including an indication of status of the operation of the lighting node N5 from the lighting node N5. The central management system 101 is shown transmitting a compensate command 155 to a newly formed group of lighting nodes N2, N3, and N4, to modify their operation to compensate for the insufficiency of the lighting from node N5.

[0071] The concept of“self-healing” may be applied at a node level, for example when a node light output is degraded or the node fails (no light). The node problem may be determined from the illumination and/or operational status data. This data may be analyzed by any number of algorithms to decide if action needs to be taken, such as alerting operations (sending maintenance people a text message etc.) that a node failure is eminent or has occurred and then grouping other (nearby) nodes to compensate for illumination or color deficit problems. In the example, node degradation or node failure has occurred in node N5 and the other nearby nodes were commanded to adjust their light output and/or direction and/or color intensity, etc. to compensate for the lower lighting intensity or color defect occurring as a result of problems at node N5. The nearby nodes may be identified because they are within radio range of node N5. Or the nearby nodes may be identified by nodes reporting who their neighbors are when they are activated, or these nodes may be identified by their GPS coordinates at the CMS, etc. The CMS may use node neighbor information compiled in the node neighbor table 149, to decide which nodes to contact and dynamically form a grouping of nodes operating in

unison/cooperatively to mitigate or correct the lighting deficit by the defective node N5. [0072] Figure 5 is an example functional block diagram of the lighting device node N5, in accordance with an embodiment of the invention, showing an example lighting device N5 connected to the wireless network 104. The lighting node device includes data such as node ID, address, gateway ID, repeater status, illumination status, group affinity, functional characteristics (video usage, motion detector attachments, etc.), other identity characteristics and operational status in its memory 307. The lighting node device includes a wireless communications unit 340 coupled to the encoder/decoder 334, which is configured to broadcast the discovery message in the wireless network 104. The network 104 includes the central management system 101 configured to receive the discovery message, commission the lighting node Nl, and provide the timeout value, configuration parameters, and other information. Using LQI information as the criterion, then the best path is considered also the most reliable path. Other reliability or efficiency criteria may be considered for the best path or a combination of criteria.

[0073] The example lighting device N5 shown in Figure 5, includes a wireless communications unit transceiver 340 that includes a transmit/receive (TX/RX) buffer 342, which is configured to communicate with the central management system 101 via the network 104. The communications unit 340 includes any needed communication protocol to communicate with a CMS 101 over the network Ll. The device N5 activates the LED driver circuit 354 controlled by the processor 322, to power the LED light array 360 with either line power, solar cell/photovoltaic power, or battery power 353.

Depending on the control parameters in a lighting schedule, the light array 360 may be turned on, its illumination level adjusted, its color changed, or turned off, in response.

The LED driver circuit 354 controls the voltage and current patterns sent to each LED element (Red, Green, Blue) in the LED array 360. The LED array 360 may be a single light fixture with a plurality of Red, Green and Blue LEDs contained in the light fixture, or it may be an array of LED’s.

[0074] The example lighting device N5 includes a processor 322 comprising a dual central processor unit (CPU) or multi-CPU 324/325, a random access memory (RAM) 326 and read only memory (ROM) 328. The memories 326 and/or 328 include computer program code for responding to lighting control information messages 170 from the central management system 101. [0075] The following example steps in the flow diagram 400 of Figure 6A, are performed by the lighting node, represent computer code instructions stored in the RAM and/or ROM memory, which when executed by the central processing units (CPU), carry out the functions of the example embodiments of the invention. The steps may be carried out in another order than shown and individual steps may be combined or separated into component steps. The flow diagram has the following steps:

[0076] Step 402: receiving by the lighting node, a command message from a central management system to measure a received link quality indication (LQI) of the command message received by the lighting node over aggregated network links between the lighting node and the central management system, and to return a status message including a measured value of the received link quality indication (LQI) to the central management system;

[0077] Step 404: receiving by the lighting node, a disconnect command from the central management system to disconnect from the network and to disconnect from the network in response to the disconnect command;

[0078] Step 406: entering by the lighting node, a discovery mode and periodically broadcast a discovery message in the network in response to disconnecting from the network;

[0079] Step 408: determining by the lighting node, whether an acknowledgement has been received from a gateway of the central management system or from a repeater in the network, in response to the broadcasting of the discovery message, enabling the lighting node to rejoin the network; and

[0080] Step 410: wirelessly connecting by the lighting node, to the gateway of the central management system or to the repeater in the network and rejoining the network.

[0081] The following example steps in the flow diagram 450 of Figure 6B, are performed by the central management system (CMS) represent computer code instructions stored in the RAM and/or ROM memory, which when executed by the central processing units (CPU), carry out the functions of the example embodiments of the invention. The steps may be carried out in another order than shown and individual steps may be combined or separated into component steps. The flow diagram has the following steps:

[0082] Step 452: transmitting, by a central management system, a command message to a lighting node, to measure a received link quality indication (LQI) of the command message received by the lighting node over aggregated network links between the lighting node and the central management system, and receiving a status message including a measured value of the received link quality indication (LQI) from the lighting node;

[0083] Step 454: comparing, by the central management system, a statistical characterization of the measured value of the link quality indication (LQI) with a threshold link quality value, to determine whether there is degradation in quality of the aggregated links between the lighting node and the central management system; and

[0084] Step 456: transmitting, by the central management system, a disconnect command to the lighting node to cause the lighting node to disconnect from the network, and to cause the lighting node to enter a discovery mode to find a better quality link and rejoin the network, when the degradation in quality of the aggregated links is determined.

[0085] The following example steps in the flow diagram 470 of Figure 6C, are performed by the central management system (CMS) for monitoring the status of the operation of the lighting node, represent computer code instructions stored in the RAM and/or ROM memory, which when executed by the central processing units (CPU), carry out the functions of the example embodiments of the invention. The steps may be carried out in another order than shown and individual steps may be combined or separated into component steps. The flow diagram has the following steps:

[0086] Step 472: transmitting, by a central management system, a command message to a lighting node, to measure a received link quality indication (LQI) of the command message received by the lighting node over aggregated network links between the lighting node and the central management system, and receiving from the lighting node a status message including a measured value of the received link quality indication (LQI) and an indication of status of the operation of the lighting node;

[0087] Step 474: comparing, by the central management system, a statistical characterization of the measured value of the link quality indication (LQI) with a threshold link quality value, to determine whether there is degradation in quality of the aggregated links between the lighting node and the central management system;

[0088] Step 476: transmitting, by the central management system, a disconnect command to the lighting node to cause the lighting node to disconnect from the network, and to cause the lighting node to enter a discovery mode to find a better quality link and rejoin the network, when the degradation in quality of the aggregated links is determined;

[0089] Step 478: comparing, by the central management system, the indication of status of the operation from the lighting node with an operational threshold value;

[0090] Step 480: Step 476: when the status of the operation of the lighting node is indicated by the comparison as insufficient, designating one or more lighting nodes nearby the lighting node as comprising a lighting node group with the degraded lighting node; and

[0091] Step 482: transmitting compensate commands to one or more lighting nodes in the lighting node group to compensate for the indicated insufficiency of the lighting node.

[0092] Although specific example embodiments of the invention have been disclosed, persons of skill in the art will appreciate that changes may be made to the details described for the specific example embodiments, without departing from the spirit and the scope of the invention.