Firmware upgrade management method and system

Abstract

The invention provides a firmware upgrade management method and system, and the method comprises the steps: a cloud device adds a to-be-distributed upgrade task to a first upgrade list when the to-be-distributed upgrade task meets a priority upgrade condition; otherwise, adding to a second upgrading list; the first relay equipment executes the upgrading task in the first upgrading list and transmits corresponding firmware upgrading data to the first type of equipment; and the cloud equipment executes the upgrading task in the second upgrading list, and transmits corresponding firmware upgrading data to the second type of equipment through the second relay equipment. And when the cloud equipment distributes the upgrade tasks, dynamic decision making is carried out based on the priority upgrade conditions to determine the execution modes of the upgrade tasks to be distributed, and then the execution modes are added to the corresponding upgrade lists. According to the method, rapid and convenient upgrading channels of multiple devices in the system are opened through different strategy scheduling, and through dynamic scheduling, the device upgrading efficiency is improved, the operation steps are reduced, and therefore better experience is brought.

Description

Technical Field

[0001] This invention relates to the field of communication technology, and more specifically, to a firmware upgrade management method and system. Background Technology

[0002] With the rapid development of technology, smart devices are gradually entering households. It's common for homes to use multiple smart devices (smart lights, smart switches, etc.). As functionality upgrades or technology advances, the firmware of these smart devices may need to be updated. Managing firmware upgrades in homes with multiple smart devices to ensure efficiency and improve user experience has become a pressing issue for those skilled in the art. Summary of the Invention

[0003] The purpose of this invention is to provide a firmware upgrade management method and system to improve the above-mentioned problems.

[0004] To achieve the above objectives, the technical solutions adopted in the embodiments of the present invention are as follows:

[0005] In a first aspect, embodiments of the present invention provide a firmware upgrade management system, the firmware upgrade management system comprising: a cloud device, a first relay device, a second relay device, and a device to be upgraded, wherein the cloud device communicates with the device to be upgraded through the first relay device or the second relay device, and the communication speed between the first relay device and the device to be upgraded is higher than the communication speed between the second relay device and the device to be upgraded.

[0006] The cloud device is used to determine whether the upgrade task to be assigned meets the priority upgrade conditions when allocating upgrade tasks; if it does, the upgrade task to be assigned is added to the first upgrade list and the updated first upgrade list is sent to the first relay device; if it does not meet the conditions, the upgrade task to be assigned is added to the second upgrade list.

[0007] The first relay device is used to execute the upgrade task in the first upgrade list and transmit the corresponding firmware upgrade data to the first type of device, wherein the first type of device is the device to be upgraded corresponding to the upgrade task in the first upgrade list;

[0008] The cloud device is also used to execute upgrade tasks in the second upgrade list and transmit corresponding firmware upgrade data to the second type of device through the second relay device, wherein the second type of device is the device to be upgraded corresponding to the upgrade task in the second upgrade list.

[0009] Secondly, embodiments of the present invention provide a firmware upgrade management method, applied to the aforementioned firmware upgrade management system, the firmware upgrade management method comprising:

[0010] When the cloud device assigns upgrade tasks, it determines whether the upgrade task to be assigned meets the priority upgrade conditions. If it does, the upgrade task to be assigned is added to the first upgrade list, and the updated first upgrade list is sent to the first relay device. If it does not meet the conditions, the upgrade task to be assigned is added to the second upgrade list.

[0011] The first relay device executes the upgrade task in the first upgrade list and transmits the corresponding firmware upgrade data to the first type of device, wherein the first type of device is the device to be upgraded corresponding to the upgrade task in the first upgrade list;

[0012] The cloud device executes the upgrade tasks in the second upgrade list and transmits the corresponding firmware upgrade data to the second type of device through the second relay device, wherein the second type of device is the device to be upgraded corresponding to the upgrade task in the second upgrade list.

[0013] Thirdly, embodiments of the present invention provide a firmware upgrade management method, applied to a cloud device in the aforementioned firmware upgrade management system, the firmware upgrade management method comprising:

[0014] When assigning upgrade tasks, determine whether the upgrade tasks to be assigned meet the priority upgrade conditions;

[0015] If the conditions are met, the upgrade task to be assigned is added to the first upgrade list, and the updated first upgrade list is sent to the first relay device so that the first relay device executes the upgrade task in the first upgrade list and transmits the corresponding firmware upgrade data to the first type of device, wherein the first type of device is the device to be upgraded corresponding to the upgrade task in the first upgrade list.

[0016] If the conditions are not met, the upgrade task to be assigned will be added to the second upgrade list;

[0017] The upgrade tasks in the second upgrade list are executed, and the corresponding firmware upgrade data is transmitted to the second type of devices through the second relay device. The second type of devices are the devices to be upgraded corresponding to the upgrade tasks in the second upgrade list.

[0018] Compared to existing technologies, the firmware upgrade management method and system provided in this invention include: a cloud device, a first relay device, a second relay device, and a device to be upgraded. The cloud device communicates with the device to be upgraded through the first relay device or the second relay device, with the communication speed between the first relay device and the device to be upgraded being higher than that between the second relay device and the device to be upgraded. When allocating upgrade tasks, the cloud device determines whether the upgrade tasks to be allocated meet priority upgrade conditions. If they do, the upgrade tasks to be allocated are added to a first upgrade list, and the updated first upgrade list is sent to the first relay device. If they do not meet the conditions, the upgrade tasks to be allocated are added to a second upgrade list. The first relay device executes the upgrade tasks in the first upgrade list and transmits corresponding firmware upgrade data to a first type of device, where the first type of device is the device to be upgraded corresponding to the upgrade tasks in the first upgrade list. The cloud device also executes the upgrade tasks in the second upgrade list and transmits corresponding firmware upgrade data to a second type of device through the second relay device, where the second type of device is the device to be upgraded corresponding to the upgrade tasks in the second upgrade list. When allocating upgrade tasks, cloud-based devices make dynamic decisions based on priority upgrade criteria to determine the execution method of each task and add it to the corresponding upgrade list. This enables the use of different scheduling strategies to create a fast and convenient upgrade channel for multiple devices within the system. Dynamic scheduling improves device upgrade efficiency, reduces operational steps, and thus delivers a better user experience.

[0019] To make the above-mentioned objects, features and advantages of the present invention more apparent and understandable, preferred embodiments are described below in detail with reference to the accompanying drawings. Attached Figure Description

[0020] To more clearly illustrate the technical solutions of the embodiments of the present invention, the accompanying drawings used in the embodiments will be briefly introduced below. It should be understood that the following drawings only show some embodiments of the present invention and should not be regarded as a limitation on the scope. For those skilled in the art, other related drawings can be obtained based on these drawings without creative effort.

[0021] Figure 1 This is a schematic diagram of the firmware upgrade management system provided in an embodiment of the present invention.

[0022] Figure 2 This is one of the flowcharts illustrating the firmware upgrade management method provided in this embodiment of the invention.

[0023] Figure 3 This is a second flowchart illustrating the firmware upgrade management method provided in this embodiment of the invention.

[0024] Figure 4This is the third flowchart illustrating the firmware upgrade management method provided in this embodiment of the invention.

[0025] In the diagram: 10 - Cloud device; 20 - First relay device; 30 - Second relay device; 40 - Device to be upgraded. Detailed Implementation

[0026] To make the objectives, technical solutions, and advantages of the embodiments of the present invention clearer, the technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. The components of the embodiments of the present invention described and shown in the accompanying drawings can generally be arranged and designed in various different configurations.

[0027] Therefore, the following detailed description of the embodiments of the invention provided in the accompanying drawings is not intended to limit the scope of the claimed invention, but merely to illustrate selected embodiments of the invention. All other embodiments obtained by those skilled in the art based on the embodiments of the invention without inventive effort are within the scope of protection of the invention.

[0028] It should be noted that similar reference numerals and letters in the following figures indicate similar items; therefore, once an item is defined in one figure, it does not need to be further defined and explained in subsequent figures. Furthermore, in the description of this invention, terms such as "first," "second," etc., are used only to distinguish descriptions and should not be construed as indicating or implying relative importance.

[0029] It should be noted that, in this document, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0030] In the description of this invention, it should be noted that the terms "upper," "lower," "inner," "outer," etc., indicate the orientation or positional relationship based on the orientation or positional relationship shown in the accompanying drawings, or the orientation or positional relationship in which the product of this invention is usually placed when in use. They are only for the convenience of describing this invention and simplifying the description, and do not indicate or imply that the device or element referred to must have a specific orientation, or be constructed and operated in a specific orientation. Therefore, they should not be construed as limiting this invention.

[0031] In the description of this invention, it should also be noted that, unless otherwise explicitly specified and limited, the terms "set" and "connection" should be interpreted broadly. For example, they can refer to a fixed connection, a detachable connection, or an integral connection; they can refer to a mechanical connection or an electrical connection; they can refer to a direct connection or an indirect connection through an intermediate medium; and they can refer to the internal connection of two components. Those skilled in the art can understand the specific meaning of the above terms in this invention based on the specific circumstances.

[0032] The following detailed description of some embodiments of the present invention is provided in conjunction with the accompanying drawings. Unless otherwise specified, the following embodiments and features can be combined with each other.

[0033] This invention provides a firmware upgrade management system that can identify firmware version information in real time and schedule upgrades through multiple channels. It records the current version number and target version number of multiple user devices, and combines the characteristics of near-field and far-field communication to upgrade user devices by scheduling different upgrade methods.

[0034] Please refer to Figure 1 , Figure 1 This is a schematic diagram of the firmware upgrade management system provided in an embodiment of the present invention. The firmware upgrade management system includes: a cloud device 10, a first relay device 20, a second relay device 30, and a device to be upgraded 40. The cloud device 10 can be a cloud server, and the cloud device 10 connects to the first relay device 20 and the second relay device 30 via wired and / or wireless networks.

[0035] The first relay device 20 is a device equipped with a first communication module. This first communication module is a high-speed, short-range communication module (e.g., a Bluetooth communication module). The second relay device 30 is a device equipped with a second communication module. This second communication module is a low-speed, long-range communication module (e.g., a Zigbee module). Optionally, the communication speed of the first communication module is higher than that of the second communication module, and the communication distance of the second communication module is greater than that of the first communication module.

[0036] Optionally, the first relay device 20 is a mobile phone, computer, laptop, or PAD, and the second relay device 30 is a gateway device.

[0037] It should be noted that the device to be upgraded 40 is equipped with a first communication module and / or a second communication module. The device to be upgraded 40 can wirelessly connect with the first relay device 20 via its first communication module, and can wirelessly connect with the second relay device 30 via its second communication module. The communication speed between the first relay device 20 and the device to be upgraded 40 is higher than the communication speed between the second relay device 30 and the device to be upgraded 40.

[0038] The cloud device 10 communicates with the device to be upgraded 40 through the first relay device 20 or the second relay device 30, and can transmit the corresponding firmware upgrade data to the device to be upgraded 40, as follows.

[0039] When allocating upgrade tasks, the cloud device 10 determines whether the upgrade task to be assigned meets the priority upgrade conditions. If it does, the upgrade task to be assigned is added to the first upgrade list, and the updated first upgrade list is sent to the first relay device 20. If it does not meet the conditions, the upgrade task to be assigned is added to the second upgrade list.

[0040] It should be noted that the cloud device 10 stores the current firmware version information of each user device associated with the user account. When an employee configures the update version information corresponding to a user device in the cloud device 10, if the cloud device 10 identifies that the current firmware version information of the user device is inconsistent with the update version information, it determines that the user device is the device 40 to be upgraded, generates firmware upgrade data corresponding to the device 40 to be upgraded based on the update version information, and then generates the upgrade task corresponding to the device 40 to be upgraded.

[0041] The first relay device 20 is used to execute the upgrade tasks in the first upgrade list and transmit the corresponding firmware upgrade data to the first type of device, wherein the first type of device is the device 40 to be upgraded corresponding to the upgrade task in the first upgrade list.

[0042] The cloud device 10 is also used to execute upgrade tasks in the second upgrade list and transmit corresponding firmware upgrade data to the second type of device through the second relay device 30. The second type of device is the device 40 to be upgraded corresponding to the upgrade task in the second upgrade list.

[0043] In this embodiment of the invention, when allocating upgrade tasks, the cloud device makes dynamic decisions based on priority upgrade conditions to determine the execution method of the upgrade tasks to be assigned, and then adds them to the corresponding upgrade list. This enables the establishment of fast and convenient upgrade channels for multiple devices within the system through different scheduling strategies. Dynamic scheduling improves device upgrade efficiency, reduces operation steps, and thus brings a better user experience.

[0044] Based on the foregoing, this embodiment of the invention also provides an optional implementation method for how the first relay device 20 executes the upgrade tasks in the first upgrade list, please refer to the following text.

[0045] The first relay device 20 is used to execute the upgrade tasks in the first upgrade list and send the target upgrade request to the cloud device 10.

[0046] The target upgrade request includes the identifier of the first target device, which is the device 40 to be upgraded corresponding to the highest priority upgrade task in the first upgrade list.

[0047] The cloud device 10 is used to send the firmware upgrade data corresponding to the first target device to the first relay device 20 after receiving the target upgrade request, so that the first relay device 20 transmits the firmware upgrade data corresponding to the first target device to the first target device.

[0048] Optionally, the first relay device 20 is also used to send an upgrade completion notification to the cloud device 10 after completing the firmware upgrade of the first target device.

[0049] The upgrade completion notification includes the identifier of the first target device.

[0050] The cloud device 10 is used to delete the upgrade task corresponding to the first target device from the first upgrade list after receiving the upgrade completion prompt, thereby avoiding the repeated execution of the task.

[0051] Building upon the preceding text, this embodiment of the invention also provides an optional implementation method for how cloud device 10 executes the upgrade tasks in the second upgrade list, as detailed below.

[0052] The cloud device 10 is used to send corresponding firmware upgrade data to the second target device through the second relay device 30. The second target device is the device 40 to be upgraded corresponding to the highest priority upgrade task in the second upgrade list.

[0053] It should be understood that after receiving the firmware upgrade data, the first target device and the second target device can complete the firmware upgrade based on it.

[0054] Building upon the preceding text, this embodiment of the invention also provides an optional implementation method to ensure that the first relay device 20 completes the upgrade task efficiently and accurately. Please refer to the following text.

[0055] The first relay device 20 is also used to generate an alarm when the strength of its communication signal with the first target device is lower than a preset strength.

[0056] It should be noted that when the distance between the first relay device 20 and the first target device is too far, or when there are obstacles with high isolation between them, the communication signal strength between them will be affected. When the communication signal strength is lower than the preset strength, it may cause the firmware upgrade data transmission to be lost, affecting the efficiency and success rate of the firmware upgrade. Therefore, when the communication signal strength between the first relay device 20 and the first target device is lower than the preset strength, an alarm prompt is generated to remind the user to bring the first relay device 20 closer to the device 40 to be upgraded for the upgrade. In this way, the upgrade failure rate caused by unstable device connection can be reduced.

[0057] In one alternative implementation, the alarm notification may include a navigation path from the current location of the first relay device to the first target device.

[0058] In some scenarios, when the number of upgrade tasks in the first upgrade list exceeds the preset number, how to make reasonable arrangements to ensure upgrade efficiency? This embodiment of the invention also provides an optional implementation method: when any upgrade task executed by the first relay device 20 ends (including success or failure), if there are still unexecuted upgrade tasks in the first upgrade list; or, in an idle state, when a new first upgrade list is received, the first relay device 20 can prioritize the upgrade tasks in the first upgrade list, as detailed below.

[0059] The first relay device 20 is used to obtain the communication signal strength between itself and the first type of device.

[0060] The first relay device 20 is used to prioritize the upgrade tasks in the first upgrade list stored by the first type of device according to the communication signal strength of the first type of device, and the upgrade task corresponding to the first type of device with the strongest communication signal strength has the highest priority.

[0061] Based on the foregoing, this embodiment of the invention also provides an optional implementation regarding how to set the priority upgrade conditions, which include any one or more of the first condition, the second condition, and the third condition.

[0062] The first condition indicates that the device to be assigned has established a wireless communication connection with the first relay device 20 within a preset time interval, wherein the device to be assigned is the device 40 to be upgraded corresponding to the upgrade task to be assigned.

[0063] It should be understood that the first relay device 20 will upload the device connection records of its deployed first communication module (which may be, but is not limited to, a Bluetooth module) to the cloud device 10. These device connection records include the identifier of the user device that established a communication connection with the first relay device 20 and the corresponding connection time. The cloud device 10 can determine, based on these device connection records, whether the device to be assigned has established a wireless communication connection with the first relay device 20 within a preset time interval.

[0064] The second condition indicates that the device to be assigned has a valid active time period within the preset time interval. The valid active time period is the active time period when the distance between the first relay device 20 and the device to be assigned is less than the preset distance, and the active time period is the usage time period when the usage frequency is higher than the preset frequency.

[0065] Optionally, the user device can send usage logs to the cloud device 10 via the first relay device 20 and / or the second relay device 30. These usage logs include the usage time of each user device session. The cloud device 10 can analyze the user device's usage logs to determine the usage time periods and frequency corresponding to each period, thereby creating a user profile. This user profile includes the user device's active time periods.

[0066] The first relay device 20 can also upload its corresponding log file to the cloud device 10. The log file includes the latitude and longitude information of the first relay device 20 at various points in time.

[0067] The cloud device 10 can obtain the latitude and longitude of the first relay device 20 and the latitude and longitude of the device to be assigned during the active time period, and then determine whether the distance between the first relay device 20 and the device to be assigned during the active time period is less than a preset distance. If it is less, it means that the active time period is a valid active time period.

[0068] The third condition indicates that the current state of the device to be assigned in the current time period is consistent with the expected state of the device to be assigned in the current time period in the user profile.

[0069] In one alternative implementation, the remote control signaling of the device to be upgraded is received through its deployed first communication module. If the upgrade data transmission occupies the first communication module, it will be unable to receive remote control signaling, thus preventing the device to be upgraded from making state changes. For example, when upgrading a lighting product, it is impossible to control the switch of the lighting fixture. To overcome this problem, the third condition mentioned above can be used to determine whether to execute the corresponding upgrade task through the first relay device 20.

[0070] It should be understood that if the current state of the device to be assigned in the current time period matches the expected state of the device in the user profile in the current time period, it means that the state of the device to be assigned will not change during this time period. Therefore, the first relay device 20 can be used to perform its corresponding upgrade task. Otherwise, the second relay device 30 is used to transmit its corresponding firmware upgrade data.

[0071] In one optional implementation, a device is considered to meet the priority upgrade condition when it meets any one of the first, second, and third conditions; or, a device is considered to meet the priority upgrade condition when it meets all of the first, second, and third conditions.

[0072] In one alternative implementation, the cloud device 10 can also prioritize the upgrade tasks in the second upgrade list to ensure task execution efficiency, as described below.

[0073] Cloud device 10 is also used to obtain the usage frequency of the second type of device.

[0074] Optionally, cloud device 10 can determine its usage frequency based on the usage logs of the second type of device.

[0075] Cloud device 10 is also used to prioritize upgrade tasks in its stored second upgrade list based on the usage frequency of the second type of devices, with the upgrade task corresponding to the second type of device with the highest usage frequency having the highest priority.

[0076] It should be noted that when a user transmits a priority specification request, the priority specification request includes the priority ordering information of the upgrade tasks corresponding to the first type of device in the first upgrade list and / or the priority ordering information of the upgrade tasks corresponding to the second type of device in the second upgrade list. The cloud device 10 can adjust the first upgrade list and / or the second upgrade list according to the priority specification request transmitted by the user.

[0077] Building upon the foregoing, this invention provides an optional implementation method to further ensure the efficiency of the upgrade task execution, as detailed below.

[0078] The cloud device 10 is also used to determine whether the number of upgrade tasks to be executed in the first upgrade list is greater than a preset value when the second upgrade list is empty.

[0079] The preset value can be, but is not limited to, 2.

[0080] If the value is greater than the preset value, the cloud device 10 is also used to move the lowest priority upgrade task in the first upgrade list to the second upgrade list.

[0081] By moving unexecuted upgrade tasks from the first upgrade list to the second upgrade list, the cloud device 10 can execute these upgrade tasks, thereby improving the firmware upgrade efficiency in the system.

[0082] This invention also provides a firmware upgrade management method, applied to the aforementioned firmware upgrade management system. Please refer to... Figure 2The firmware upgrade management methods include S110, S210, and S120, which are described in detail below.

[0083] S110: When the cloud device assigns upgrade tasks, it determines whether the upgrade tasks to be assigned meet the priority upgrade conditions. If they do, the upgrade tasks to be assigned are added to the first upgrade list, and the updated first upgrade list is sent to the first relay device. If they do not meet the conditions, the upgrade tasks to be assigned are added to the second upgrade list.

[0084] S210, the first relay device executes the upgrade task in the first upgrade list and transmits the corresponding firmware upgrade data to the first type of device.

[0085] The first category of equipment refers to the equipment to be upgraded corresponding to the upgrade tasks in the first upgrade list.

[0086] S120, the cloud device executes the upgrade tasks in the second upgrade list, and transmits the corresponding firmware upgrade data to the second type of device through the second relay device.

[0087] The second category of equipment refers to the equipment to be upgraded corresponding to the upgrade tasks in the second upgrade list.

[0088] This invention also provides a firmware upgrade management method, applied to cloud devices within the aforementioned firmware upgrade management system. Please refer to... Figure 3 The firmware upgrade management methods include S111, S112, S113 and S121, which are described in detail below.

[0089] S111: When assigning upgrade tasks, determine whether the upgrade tasks to be assigned meet the priority upgrade conditions. If they do, proceed to S112; otherwise, proceed to S113.

[0090] S112, add the upgrade tasks to be assigned to the first upgrade list, and send the updated first upgrade list to the first relay device.

[0091] So that the first relay device executes the upgrade task in the first upgrade list and transmits the corresponding firmware upgrade data to the first type of device, wherein the first type of device is the device to be upgraded corresponding to the upgrade task in the first upgrade list.

[0092] S113, Add the upgrade task to be assigned to the second upgrade list.

[0093] S121, execute the upgrade task in the second upgrade list, and transmit the corresponding firmware upgrade data to the second type of device through the second relay device, wherein the second type of device is the device to be upgraded corresponding to the upgrade task in the second upgrade list.

[0094] Based on the foregoing, this embodiment of the invention also provides an optional implementation method, please refer to... Figure 4 Firmware upgrade management methods also include S131 and S132, which are described in detail below.

[0095] S131, when the second upgrade list is empty, determine whether the number of upgrade tasks to be executed in the first upgrade list is greater than a preset value. If it is greater than the preset value, execute S132; if it is less than or equal to the preset value, remain unchanged.

[0096] S132, move the lowest priority upgrade task in the first upgrade list to the second upgrade list.

[0097] Among them, the upgrade task with the lowest priority can be the upgrade task corresponding to the device to be upgraded with the lowest communication signal strength with the first relay device.

[0098] It should be noted that the firmware upgrade management method provided in this embodiment can perform the functions and uses shown in the firmware upgrade management system embodiments described above, in order to achieve the corresponding technical effects. For the sake of brevity, any parts not mentioned in this embodiment can be referred to the corresponding content in the above embodiments.

[0099] In summary, the firmware upgrade management method and system provided by this invention includes: a cloud device, a first relay device, a second relay device, and a device to be upgraded. The cloud device communicates with the device to be upgraded through the first relay device or the second relay device, with the communication speed between the first relay device and the device to be upgraded being higher than that between the second relay device and the device to be upgraded. When allocating upgrade tasks, the cloud device determines whether the upgrade task to be allocated meets the priority upgrade conditions. If it does, the upgrade task to be allocated is added to a first upgrade list, and the updated first upgrade list is sent to the first relay device. If it does not meet the conditions, the upgrade task to be allocated is added to a second upgrade list. The first relay device executes the upgrade tasks in the first upgrade list and transmits corresponding firmware upgrade data to a first type of device, wherein the first type of device is the device to be upgraded corresponding to the upgrade task in the first upgrade list. The cloud device also executes the upgrade tasks in the second upgrade list and transmits corresponding firmware upgrade data to a second type of device through the second relay device, wherein the second type of device is the device to be upgraded corresponding to the upgrade task in the second upgrade list. When allocating upgrade tasks, cloud-based devices make dynamic decisions based on priority upgrade criteria to determine the execution method of each task and add it to the corresponding upgrade list. This enables the use of different scheduling strategies to create a fast and convenient upgrade channel for multiple devices within the system. Dynamic scheduling improves device upgrade efficiency, reduces operational steps, and thus delivers a better user experience.

[0100] The above description is merely a preferred embodiment of the present invention and is not intended to limit the invention. Various modifications and variations can be made to the present invention by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present invention should be included within the scope of protection of the present invention.

[0101] It will be apparent to those skilled in the art that the present invention is not limited to the details of the exemplary embodiments described above, and that the invention can be implemented in other specific forms without departing from its spirit or essential characteristics. Therefore, the embodiments should be considered in all respects as exemplary and non-limiting, and the scope of the invention is defined by the appended claims rather than the foregoing description. Thus, all variations falling within the meaning and scope of equivalents of the claims are intended to be included within the present invention. No reference numerals in the claims should be construed as limiting the scope of the claims.

Claims

1. A firmware upgrade management system, characterized by, The firmware upgrade management system includes: a cloud device, a first relay device, a second relay device, and a device to be upgraded. The cloud device communicates with the device to be upgraded through the first relay device or the second relay device. The communication speed between the first relay device and the device to be upgraded is higher than the communication speed between the second relay device and the device to be upgraded. The cloud device is used to determine whether the upgrade task to be assigned meets the priority upgrade conditions when allocating upgrade tasks; if it does, the upgrade task to be assigned is added to the first upgrade list and the updated first upgrade list is sent to the first relay device; if it does not meet the conditions, the upgrade task to be assigned is added to the second upgrade list. The first relay device is used to execute the upgrade task in the first upgrade list and transmit the corresponding firmware upgrade data to the first type of device, wherein the first type of device is the device to be upgraded corresponding to the upgrade task in the first upgrade list; The cloud device is also used to execute upgrade tasks in the second upgrade list and transmit corresponding firmware upgrade data to the second type of device through the second relay device, wherein the second type of device is the device to be upgraded corresponding to the upgrade task in the second upgrade list.

2. The firmware upgrade management system as described in claim 1, characterized in that, The first relay device is used to execute the upgrade task in the first upgrade list and send a target upgrade request to the cloud device. The target upgrade request includes the identifier of the first target device, which is the device to be upgraded corresponding to the highest priority upgrade task in the first upgrade list. Upon receiving the target upgrade request, the cloud device sends firmware upgrade data corresponding to the first target device to the first relay device, so that the first relay device transmits the firmware upgrade data corresponding to the first target device to the first target device.

3. The firmware upgrade management system as described in claim 2, characterized in that, The first relay device is also used to generate an alarm when the strength of its communication signal with the first target device is lower than a preset strength.

4. The firmware upgrade management system as described in claim 2, characterized in that, The first relay device is used to obtain the communication signal strength between itself and the first type of device; The first relay device is used to prioritize the upgrade tasks in its stored first upgrade list according to the communication signal strength of the first type of device, with the upgrade task corresponding to the first type of device with the strongest communication signal having the highest priority.

5. The firmware upgrade management system of claim 1, wherein, The priority upgrade conditions include any one or more of the first condition, the second condition, and the third condition; The first condition indicates that the device to be assigned has established a wireless communication connection with the first relay device within a preset time interval, wherein the device to be assigned is the device to be upgraded corresponding to the upgrade task to be assigned; The second condition indicates that the device to be assigned has a valid active time period within a preset time interval. The valid active time period is the active time period when the distance between the first relay device and the device to be assigned is less than a preset distance, and the active time period is the usage time period when the usage frequency is higher than a preset frequency. The third condition indicates that the current state of the device to be assigned in the current time period is consistent with the expected state of the device to be assigned in the current time period as described in the user profile.

6. The firmware upgrade management system as described in claim 1, characterized in that, The cloud device is also used to obtain the usage frequency of the second type of device; The cloud device is also used to prioritize the upgrade tasks in the second upgrade list it stores based on the usage frequency of the second type of device, with the upgrade task corresponding to the second type of device with the highest usage frequency having the highest priority.

7. The firmware upgrade management system as described in claim 1, characterized in that, The cloud device is also used to determine whether the number of upgrade tasks to be executed in the first upgrade list is greater than a preset value when the second upgrade list is empty; If the value is greater than a preset value, the cloud device is also used to move the lowest priority upgrade task in the first upgrade list to the second upgrade list.

8. A firmware upgrade management method characterized by, The firmware upgrade management system applied to any one of claims 1 to 7, the firmware upgrade management method comprising: When the cloud device assigns upgrade tasks, it determines whether the upgrade task to be assigned meets the priority upgrade conditions. If it does, the upgrade task to be assigned is added to the first upgrade list, and the updated first upgrade list is sent to the first relay device. If it does not meet the conditions, the upgrade task to be assigned is added to the second upgrade list. The first relay device executes the upgrade task in the first upgrade list and transmits the corresponding firmware upgrade data to the first type of device, wherein the first type of device is the device to be upgraded corresponding to the upgrade task in the first upgrade list; The cloud device executes the upgrade tasks in the second upgrade list and transmits the corresponding firmware upgrade data to the second type of device through the second relay device, wherein the second type of device is the device to be upgraded corresponding to the upgrade task in the second upgrade list.

9. A firmware upgrade management method, characterized by, The firmware upgrade management method, applied to a cloud device in any one of claims 1 to 7, comprises: When assigning upgrade tasks, determine whether the upgrade tasks to be assigned meet the priority upgrade conditions; If the conditions are met, the upgrade task to be assigned is added to the first upgrade list, and the updated first upgrade list is sent to the first relay device so that the first relay device executes the upgrade task in the first upgrade list and transmits the corresponding firmware upgrade data to the first type of device, wherein the first type of device is the device to be upgraded corresponding to the upgrade task in the first upgrade list. If the conditions are not met, the upgrade task to be assigned will be added to the second upgrade list; The upgrade tasks in the second upgrade list are executed, and the corresponding firmware upgrade data is transmitted to the second type of devices through the second relay device. The second type of devices are the devices to be upgraded corresponding to the upgrade tasks in the second upgrade list.

10. The firmware upgrade management method as described in claim 9, characterized in that, The method further includes: When the second upgrade list is empty, determine whether the number of upgrade tasks to be executed in the first upgrade list is greater than a preset value; If the value is greater than the preset value, the upgrade task with the lowest priority in the first upgrade list will be moved to the second upgrade list.

Images