Method and server for upgrading a smart lighting system and network device of a smart lighting system
By combining internal and external communication protocols, OTA upgrades of smart lighting systems are performed using proxy devices, solving the problem of time-consuming upgrades in existing technologies and achieving rapid and automated system updates.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- LEDVANCE GMBH
- Filing Date
- 2024-12-03
- Publication Date
- 2026-06-05
Smart Images
Figure CN122160252A_ABST
Abstract
Description
Technical Field
[0001] The technical field of this disclosure generally relates to intelligent networks. Specifically, this disclosure relates to methods and servers for upgrading intelligent lighting systems, as well as network devices for intelligent lighting systems. Background Technology
[0002] Lighting systems with known intelligent programmable devices exist. Programmable devices can include controllers with software or firmware to provide any desired functionality. Sometimes, especially with the release of new software or hardware, updating such systems is necessary, which can be a very time-consuming and tedious task. Summary of the Invention
[0003] The purpose of this application is to provide a particularly easy and quick method for performing upgrades to intelligent lighting systems.
[0004] According to a first aspect, a method is provided for upgrading an intelligent lighting system having multiple network devices or network-enabled devices, the network devices being configured to communicate wirelessly based on at least one internal communication protocol and at least one external communication protocol.
[0005] Specifically, network devices, or at least some network devices, can be configured to communicate with each other internally (i.e., within the network) based on at least one internal communication protocol (such as ZigBee, Bluetooth, or other mesh communication protocols). ZigBee is a registered trademark of the ZigBee Alliance. Bluetooth is a registered trademark of the Bluetooth SIG (Special Interest Group).
[0006] Network devices, or at least some network devices, may be further configured to communicate with external devices, such as servers, based on at least one external communication protocol, such as BLE (Bluetooth Low Energy) or Wi-Fi. Bluetooth is a registered trademark of the Bluetooth SIG. Wi-Fi is a registered trademark of the Wireless Fidelity Alliance.
[0007] The method involves sending an OTA (Over-The-Air) file to at least one primary agent device among a plurality of network devices. The OTA file may contain software or firmware for over-the-air upgrades of the network devices.
[0008] At least one agent device may include one or more agent devices that can be configured as OTA clients to receive OTA files from an external server via an external communication path, or from another network device configured as an OTA server via an internal communication path. Here, the external server can be a mobile application or a PC-based application. When the agent device has finished receiving the entire file, it will check the OTA file and decide whether to update the agent device. The agent device will then automatically configure itself as an OTA server. As an OTA server, it can notify other devices that new firmware is available for upgrades. An internal communication path can be established based on at least one internal communication protocol, and an external communication path can be established based on at least one external communication protocol. In some embodiments, the at least one internal communication protocol and the at least one external communication protocol may include one or more common communication protocols.
[0009] The method further includes: updating at least one first agent device by updating the firmware of at least one first agent device based on an OTA file, and automatically configuring the agent device (i.e., at least one agent device) as an OTA server. The method also includes: sending an OTA file from at least one first agent device to at least one second agent device among a plurality of network devices, and updating at least one second agent device by updating the firmware of at least one second agent device based at least partially on the OTA file received from at least one first agent device.
[0010] Therefore, once the OTA file is transmitted to at least one of the multiple network devices, the lighting system update can be performed by the network devices with virtually no external assistance by repeating the above steps until all network devices are eventually updated.
[0011] Furthermore, lighting system updates can be performed in an avalanche fashion, where a second agent transfers OTA files to a third agent, from the third agent to a fourth agent, and so on. Therefore, OTA file transfer can be accelerated, and the overall system update time can be significantly reduced.
[0012] Sending an OTA file to an agent device, specifically, sending an OTA file from a server or from another network device acting as an OTA server to an agent device, may include: sending an OTA notification message containing version information of the OTA file; when checking the OTA version, the agent device verifies the version; and the agent device indicates that it is ready to receive the OTA file.
[0013] Specifically, version information can be provided in the image ID within the header of the OTA file. The image ID serves as a unique identifier to identify a specific firmware or software version and ensures that the correct software is used for the update of the corresponding device.
[0014] Verification of the OTA version may include checking whether the OTA file version is newer than the current version implemented in the agent device. Once it is verified that the version is newer than the current version, the agent device can instruct the server or another network device acting as the server to be ready to receive the OTA file.
[0015] Configuring at least one first agent device may include disabling the OTA client function and enabling the OTA server function of at least one agent device. In some embodiments, this is done during the restart of at least one agent device. Therefore, the agent device can switch from OTA client mode to OTA server mode. By disabling the OTA client function, any OTA file transfers to the agent device, such as from an application on the server or any other network device, can be prevented.
[0016] Before sending the OTA file to at least one second agent device, at least one first agent device can identify whether the network is busy, and if the network is busy, it can delay the sending of the OTA file for a predefined time. Thus, when the network or other network devices are not busy and are able to receive the OTA file, at least one first agent device can begin sending the OTA file.
[0017] In some embodiments, before sending the OTA file to at least one second agent device, at least one first agent device sends OTA notification messages to other network devices. Specifically, after a predefined delay time, at least one first agent device may act as an OTA server to begin notifying other devices to update them.
[0018] Specifically, at least one agent device can be configured to transmit OTA files to the first N (e.g., the first 3) agent devices that respond accordingly to OTA notifications. By sending OTA files, a second agent device acts as an OTA server, sending notifications and OTA files to the first N third agent devices. Thus, by repeating the above steps, each network device requiring an update can ultimately be updated directly from an external server or from another network device with 1, 2, or even more hops.
[0019] The method may include initiating an update process via an external server or server device carrying an OTA file for OTA upgrades of a lighting system. The external server or server device may be, for example, a portable device, such as a smartphone, or a personal computer with a specific program configured to carry the OTA file. Specifically, the server device may be configured with appropriate software or applications capable of reading the OTA file from the server's memory unit. The external server may establish wireless communication with an initial agent device among multiple network devices based on at least one external communication protocol (e.g., BLE or WIFI) and send the OTA file to the initial agent device. The initiation may include: reading the OTA file from the external server's memory unit, obtaining an image ID from the OTA file, and scanning for network devices supporting at least one communication protocol for the same image ID.
[0020] The initial proxy device can be selected, at least in part, based on the RSSI (Received Signal Strength Indicator). Specifically, the initial proxy device can be the nearest network device displaying the strongest RSSI, enabling reliable communication to be established between the external server and the network.
[0021] The initial proxy device can also be selected, at least in part, based on the date of its last firmware update. For example, if no Bluetooth network device matches its image ID with the image ID of the OTA file, the Bluetooth network device with the latest firmware update will be selected as the initial proxy device. This increases the likelihood that the initial proxy device is not completely outdated and can be used to execute the method.
[0022] According to the second aspect, a network device for an intelligent lighting system is provided.
[0023] The network device includes a processor and a memory unit for storing firmware, data, and machine-readable instructions for the processor.
[0024] The network device also includes an interface configured to communicate wirelessly based on at least one internal communication protocol for communicating with other network devices within the lighting system and at least one external communication protocol for communicating with an external server.
[0025] At least one external communication protocol may include, for example, BLE or Wi-Fi. At least one internal communication protocol may include, for example, Zigbee or Bluetooth, for wirelessly connecting network devices to build a smart network.
[0026] The machine-readable instructions include instructions to cause the processor to receive an OTA file from the OTA server and update the firmware based on the OTA file received from the OTA server. The OTA server can be an external device that is at least configured as an OTA server and / or another network device that is at least temporarily configured as an OTA server among a plurality of network devices.
[0027] Machine-readable instructions may also include instructions to configure a network device as an OTA server and to resend OTA files to other network devices for updating the firmware of those other network devices.
[0028] According to a third aspect, a server is provided for upgrading an intelligent lighting system having multiple network devices. Specifically, the network devices can be configured as network devices according to the second aspect above. The server includes a processor and a memory unit for storing data and machine-readable commands for the processor.
[0029] The server also includes an interface configured to communicate wirelessly with network devices based on at least one external communication protocol, such as BLE or Wi-Fi.
[0030] The memory unit contains OTA files for upgrading network devices, and the machine-readable instructions include instructions for the processor to establish wireless communication with the initial agent device of the lighting system, read the OTA files, and send the OTA files to the initial agent device via wireless communication.
[0031] Machine-readable instructions may include commands to instruct the processor to read and send the OTA file header to the initial agent device. Therefore, the initial agent device can check if the OTA file header matches its own. In this case, the initial agent device can initiate the OTA process itself and then reboot to switch from an OTA client to an OTA server. If the OTA file does not match the initial agent device, the initial agent device can switch to an OTA server to transfer the OTA file to other network devices. Therefore, even if the initial agent device does not need to upgrade or the OTA file does not match its own, the server can still initiate a system upgrade.
[0032] In the following description, details are provided to describe embodiments of this specification. However, it will be apparent to those skilled in the art that embodiments can be practiced without these details.
[0033] Some components in the embodiments have similar components. Similar components may have the same name or similar component numbers. Where appropriate, the description of one component may be applied by referring to another similar component, thereby reducing textual repetition and not limiting this disclosure. Attached Figure Description
[0034] Figure 1 A method for upgrading a smart lighting system according to an embodiment is illustrated schematically, and
[0035] Figure 2 A flowchart of a method for controlling a lamp in a lighting system according to an embodiment is shown. Detailed Implementation
[0036] Figure 1 A method for upgrading a smart lighting system according to an embodiment is illustrated schematically.
[0037] Specifically, Figure 1 A smart lighting system 1 with multiple network devices 2 is shown. The smart lighting system 1 may substantially include, as follows: Figure 1 The corresponding pictogram in the diagram represents any number of controllable lights, switches, and / or sensors.
[0038] Network device 2 is configured to communicate with each other via a wireless communication path based on at least one internal wireless communication protocol. Figure 1 The solid double arrow in the diagram represents the wireless communication path 3 between network devices 2 within the lighting system 1 based on the internal communication protocol.
[0039] At least some network devices 2 can be configured as intelligent network devices that support the upgrade process according to this method. Specifically, such network devices may include a processor, a memory unit for storing firmware, data, and machine-readable instructions for the processor, and an interface. For simplicity, the processor, memory unit, and interface of network device 2 are not shown.
[0040] The interface can be configured for wireless communication based on at least one internal communication protocol (e.g., Zigbee). In this document, internal communication refers to communication between network devices 2 within the lighting system 1.
[0041] The interface can also be configured to wirelessly communicate with, for example, external devices or devices not belonging to System 1, based on at least one external communication protocol. Specifically, network device 2 can be configured to implement multiple communication protocols simultaneously within network device 2, such as Bluetooth and Zigbee.
[0042] Machine-readable instructions may include instructions to cause the processor to receive an OTA file from an OTA server and to update the firmware based on the OTA file received from the OTA server. Machine-readable instructions may also include instructions to cause the processor to configure network device 2 as an OTA server and to send OTA files to other network devices for upgrading the firmware of those devices. Specifically, the OTA file may be transmitted from one network device to another via wireless transmission 4 (as indicated by the unidirectional arrow).
[0043] Figure 1 A server 5 configured to initiate a system upgrade is also shown. In this embodiment, server 5 is configured as a portable smart device containing OTA files for an OTA upgrade of the lighting system 1.
[0044] Specifically, server 5 may include a processor, a memory unit for storing firmware, data, and machine-readable instructions for the processor, and an interface configured to communicate wirelessly with network devices. For simplicity, the processor, memory unit, and interface of server 5 are not shown.
[0045] The memory unit of server 5 contains OTA files for upgrading network device 2, and the machine-readable instructions include instructions to enable the processor to establish wireless communication with the initial agent device of the lighting system, read the OTA files, and send the OTA files to the initial agent device.
[0046] The hollow double arrow represents the wireless communication path 6 between server 5 and the initial agent device.
[0047] Figure 2 A flowchart of a method for controlling a lamp in a lighting system according to an embodiment is shown.
[0048] Method 100 includes sending an OTA file 110 to at least one first agent device among a plurality of network devices.
[0049] The OTA file transmission in step 110 can be performed by an external server via wireless communication path 6, such as... Figure 1 As shown. In this scenario, at least one first agent device will be the initial agent device, which first receives the OTA file from server 5.
[0050] The OTA file transmission in step 110 can also be performed by any network device 2 that has already received the OTA file (specifically, as an OTA client), and switch from OTA client mode to OTA server mode.
[0051] Therefore, at least one first agent device does not necessarily include the initial agent device that first obtains the OTA file from the server during the upgrade process.
[0052] Method 100 also includes updating 120 at least one first agent device. Specifically, after the upgrade process is initiated by the server, and once at least one agent device has received the OTA file, in step 120, at least one agent device can upgrade its firmware based on the received OTA file.
[0053] The method also includes configuring at least one first agent device 130 as an OTA server. Specifically, the configuration in step 130 may include disabling the OTA client function and enabling the OTA server function of at least one agent device. Configuring at least one first agent device may include restarting at least one first agent device such that, after restarting, the at least one first agent device can operate as an OTA server rather than as an OTA client. By disabling the OTA client function, any interference with the upgrade process caused by OTA file transfers from, for example, applications on the server or any other network device to at least one first agent device can be prevented. Once the agent device completes the OTA file transfer task, the OTA client function is re-enabled, preparing for the next new firmware upgrade.
[0054] The method also includes sending an OTA file from at least one agent device to at least one second agent device among a plurality of network devices, and updating at least one second agent device by updating the firmware of at least one second agent device based at least in part on the OTA file received from at least one first agent device.
[0055] Return to reference Figure 1 The above methods and steps can be aided by Figure 1 The arrows shown are used for visualization. Specifically, server 5 can establish a wireless communication path 6 with the initial agent device and perform wireless transmission 4 of OTA files to the initial agent device.
[0056] The selection of the initial or first agent device may be based at least in part on the strength of the wireless communication path or RSSI in order to ensure reliable transmission of OTA files to System 1.
[0057] Some devices on the internal network, such as legacy sensors, may only support internal protocols and not external ones. These legacy devices cannot act as proxy devices to receive OTA files directly from external servers (e.g., via Bluetooth-enabled mobile applications). Users can connect to other types of Bluetooth / Wi-Fi capable devices and use that specific Bluetooth / Wi-Fi capable device as a proxy. In this case, the selection of the initial proxy device can also be based, at least in part, on the date of its last firmware update. For example, if a network device's firmware update is significantly outdated, this might indicate that the network device is unsuitable as a proxy for performing OTA updates, as it could itself be waiting to be updated by other internal devices. In this case, server 5 can search for another network device that can be selected as the initial proxy device.
[0058] This first transmission of OTA files from server 5 to lighting system 1 Figure 1 The number 1 is represented by a circled number.
[0059] Upon receiving the OTA file, the initial agent device can perform the upgrade and send or transmit OTAs for other network devices. This "second-generation transport" in... Figure 1 The OTA file is marked with a circled number 2. Transmission or forwarding of OTA files can be repeated in the "third generation" (marked with a circled number 3), or further transmitted, eventually updating the entire network. Each network device acting as an OTA server can transmit OTA files to multiple other network devices, such as two, three, or more, multiplying the update coverage by each generation, thus significantly reducing update time for large networks.
[0060] For example, in steps 110 and / or 140 above, sending the OTA file to the agent device may include: sending an OTA notification message containing version information of the OTA file, having the receiving agent device or OTA client verify the version, and instructing the OTA server to be ready to receive the OTA file. Specifically, when checking the OTA version, the OTA client may respond to the OTA server, which may be an external server or a network device acting as an OTA server, and the OTA client may indicate that the OTA file is ready.
[0061] Specifically, upon receiving an OTA notification message or OTA file header, if the OTA file is for a proxy device or OTA client, the proxy device or OTA client can check the OTA file header and begin updating itself. Afterwards, the proxy device can automatically restart and reboot in OTA server mode.
[0062] If the OTA header check instruction file is not for the agent device or OTA client, the agent device or OTA client switches from OTA client mode to OTA server mode without updating its firmware.
[0063] Switching to OTA server mode, with or without prior firmware updates, may include: disabling OTA client mode so that the OTA agent device is unaffected by any OTA servers scanning for OTA clients. Switching to OTA server mode may also include: automatically notifying other devices about upcoming firmware updates.
[0064] Before sending the OTA file in steps 110 and / or 140, the OTA server and / or the network device acting as the OTA server can identify whether the network of System 1 or other network devices is busy, and if the network is identified as busy, the sending of the OTA file can be delayed for a predefined time, such as 2 minutes. This avoids unnecessary data traffic.
[0065] The method described above provides an effective and rapid approach to system upgrades, especially for gatewayless systems, as such systems cannot be remotely updated, and on-site updates using traditional methods can be extremely time-consuming. Essentially, OTA upgrades can be initiated by any updating device to neighboring devices, and during the update process, it accelerates the updating of more devices.
[0066] While at least one exemplary embodiment has been given in the foregoing detailed description, it should be understood that numerous variations exist. It should also be understood that the one or more exemplary embodiments are merely examples and are not intended to limit the scope, applicability, or configuration of this disclosure in any way. Rather, the foregoing detailed description will provide those skilled in the art with a convenient roadmap for implementing one or more exemplary embodiments.
[0067] Figure Labels
[0068] 1 Intelligent Lighting System
[0069] 2 Network equipment
[0070] 3 Wireless Communication Path
[0071] 4 Wireless transmission
[0072] 5 servers
[0073] 6 Wireless Communication Paths
[0074] 7 Device Locator Module
[0075] 100 Methods to Upgrade Your Smart Lighting System
[0076] 110 sends the OTA file to at least one first agent device.
[0077] 120 Update at least one first agent device
[0078] 130 Configure at least one first agent device as an OTA server
[0079] 140 sends OTA files from at least one first agent device to at least one second agent device.
[0080] 150 Update at least one second agent device
Claims
1. A method for upgrading an intelligent lighting system (1) having multiple network devices (2), the multiple network devices (2) being configured to communicate wirelessly based on at least one internal communication protocol and at least one external communication protocol, the method comprising: Send (110) over-the-air download file to at least one of the plurality of network devices (2), Based on the over-the-air downloaded file, the at least one first agent device is updated (120) by updating the firmware of the at least one first agent device. The at least one first agent device is automatically configured (130) as an over-the-air download server. Sending the over-the-air download file from the at least one first proxy device (140) to at least one second proxy device among the plurality of network devices (2), and The at least one second agent device is updated (150) by updating the firmware of the at least one second agent device based at least in part on the over-the-air download file received from the at least one first agent device.
2. The method according to claim 1, wherein, Sending the over-the-air download to the proxy device includes: sending an over-the-air download notification message containing version information of the over-the-air download file; when checking the over-the-air download version, the proxy device verifies the version and indicates that it is ready to receive the over-the-air download file.
3. The method according to claim 1 or 2, wherein, The configuration of the at least one first agent device includes: disabling the over-the-air (OTA) client function and enabling the OTA server function of the at least one first agent device.
4. The method according to any one of the preceding claims, wherein, Before sending the over-the-air download file to at least one second proxy device, the at least one first proxy device identifies whether the network is busy, and if the network is busy, delays the sending of the over-the-air download file by a predefined time.
5. The method according to any one of the preceding claims, wherein, Before sending the over-the-air download file to at least one second agent, the at least one first agent sends an over-the-air download notification message to other network devices for updates.
6. The method according to any one of the preceding claims further comprises: An update process is initiated by an external server carrying an over-the-air download file for an over-the-air upgrade of the lighting system (1), wherein the external server establishes wireless communication with an initial proxy device among the plurality of network devices (2), and The over-the-air download file is sent to the initial agent device based on at least one external communication protocol.
7. The method according to claim 6, wherein, The initial agent is selected based at least in part on the received signal strength indicator.
8. The method according to claim 6 or 7, wherein, The initial agent is selected based at least in part on the date of its last firmware update.
9. A network device for an intelligent lighting system (1), comprising: A processor and a memory unit, the memory unit being used to store firmware, data, and machine-readable instructions for the processor, and An interface configured to communicate wirelessly based on at least one internal communication protocol and at least one external communication protocol, wherein the machine-readable instructions include instructions for the processor to: Receive over-the-air download files from an over-the-air download server to update the firmware based on the over-the-air download files received from the over-the-air download server. Configure the network device as an over-the-air download server, and The over-the-air downloaded file is resent to other network devices for updating the firmware of those devices.
10. A server for upgrading an intelligent lighting system (1) having a plurality of network devices (2) according to claim 9, the server comprising: A processor and a memory unit, the memory unit being used to store data and machine-readable commands for the processor, and An interface configured to wirelessly communicate with a network device, wherein the memory unit contains an over-the-air (OTA) file for upgrading the network device, and the machine-readable instructions include instructions for the processor to establish wireless communication with an initial agent device of the lighting system (1), read the OTA file, and send the OTA file to the initial agent device via the wireless communication.