Alarm event processing method, device, apparatus, and storage medium

Abstract

The application provides a kind of processing method, device and equipment of alarm event and storage medium, belong to computer technical field, wherein, the processing method of alarm event includes: obtaining first alarm event;First alarm event is used to represent that intelligent device is abnormal;In the case where it is determined that first alarm event meets preset upgrade condition, at least one target device to be upgraded is determined, and corresponding upgrade package is sent to at least one target device;Wherein, preset upgrade condition indicates that alarm event supporting processing by device upgrade can be processed.This application uses the above-mentioned processing method of alarm event, can more timely and effectively process the alarm event supporting processing by the way of device upgrade, reduces the damage situation after device continues to run abnormally, improves the stability and reliability of device work.

Description

Technical Field

[0001] This invention relates to the field of computer technology, and in particular to a method, apparatus, device, and storage medium for handling alarm events. Background Technology

[0002] With the rapid development of the energy internet, energy sites such as photovoltaic power plants and energy storage stations are evolving towards high intelligence and unmanned operation. Various intelligent devices in these energy sites, such as smart inverters, residential / commercial energy storage, data acquisition units, and backup power boxes, are typically deployed in complex environments, widely distributed, and require long-term continuous operation. Their operational stability and timeliness directly affect the energy efficiency and safety of the entire site.

[0003] Currently, smart devices generate alarms when malfunctions occur, and technicians manually handle these alarms periodically. However, this method often lacks timeliness and can easily lead to equipment damage. Furthermore, on-site installers are often unsure which upgrade package to use after an alarm is triggered, resulting in low troubleshooting efficiency. Summary of the Invention

[0004] This invention provides a method, apparatus, device, and storage medium for handling alarm events, in order to solve the problem that in the prior art, these alarms are handled manually on a regular basis, but this method often lacks timeliness and is prone to causing equipment damage.

[0005] In a first aspect, the present invention provides a method for processing alarm events, the method comprising: Obtain the first alarm event; the first alarm event is used to characterize abnormal operation of the smart device; If the first alarm event meets the preset upgrade conditions, at least one target device to be upgraded is identified, and a corresponding upgrade package is sent to at least one of the target devices; wherein, the preset upgrade conditions indicate alarm events that can be processed through device upgrade.

[0006] In some embodiments, determining that the first alarm event meets preset escalation conditions includes: Determine whether the target feature information in the first alarm event matches the preset upgrade rule in the preset upgrade rule library; If so, then the first alarm event is determined to meet the preset escalation conditions.

[0007] In some embodiments, the first alarm event includes a target feature information; the preset upgrade rule base includes multiple first type upgrade rules, and each first type upgrade rule includes a preset sub-upgrade condition; The step of determining whether the target feature information in the first alarm event matches a preset upgrade rule in the preset upgrade rule base; if so, determining that the first alarm event meets the preset upgrade condition includes: The target feature information is matched with a preset sub-upgrade condition in each of the first type of upgrade rules. If a matching first type of upgrade rule exists, the first alarm event is determined to satisfy the preset upgrade condition.

[0008] In some embodiments, the first alarm event includes multiple target feature information; the preset upgrade rule base includes multiple second type upgrade rules, and the second type upgrade rules include multiple preset sub-upgrade conditions; The step of determining whether the target feature information in the first alarm event matches a preset upgrade rule in the preset upgrade rule base; if so, determining that the first alarm event meets the preset upgrade condition includes: The multiple target feature information is matched with multiple preset sub-upgrade conditions in each of the second type upgrade rules; if a matching second type upgrade rule exists, the first alarm event is determined to satisfy the preset upgrade conditions.

[0009] In some embodiments, the preset sub-upgrade conditions are the following: Condition A: Does a preset alarm indicator exist? Condition B: Has the preset alarm duration been reached? Condition C: Does there exist a situation where every device type-alarm type combination in the first set generates an alarm? The first set includes K combinations of device types-alarm types, where K is a natural number and K>=1. Condition D: Does there exist a situation where no alarm is generated for each device type-alarm type in the second set? The second set includes M combinations of device types-alarm types, where M is a natural number and M>=1. Condition E: Is there a situation where the device version number is lower than, equal to, or not equal to the preset version number? The first type of upgrade rule includes any one of conditions A, B, C, D, and E; or, The second type of upgrade rule includes multiple conditions A, B, C, D, and E, where the number of each preset sub-upgrade condition is greater than or equal to 1.

[0010] In some embodiments, condition C includes any of the following: C1 condition: In the first set, is there a situation where there are multiple first combinations of the same device type corresponding to different alarm types, and all of the multiple first combinations generate alarms; C2 condition: In the first set, are there multiple second combinations of different device types corresponding to different alarm types, and are there multiple second combinations that all generate alarms? And / or, the D condition includes any of the following: D1 condition: In the second set, is there a situation where the same device type corresponds to multiple third combinations of different alarm types, and none of the multiple third combinations generate an alarm? D2 condition: In the second set, are there multiple fourth combinations with different device types corresponding to different alarm types, and none of the multiple fourth combinations generate an alarm?

[0011] In some embodiments, the target feature information includes: The device identifier and at least one of the following: alarm identifier, alarm type, alarm duration, and device version number; The device identifier is used to indicate the device's registration information.

[0012] In some embodiments, after acquiring the first alarm event, the method further includes: The first alarm event is displayed through a pre-configured visual interface; Upon receiving an alarm handling instruction input by the user through the visual interface, it is determined whether the first alarm event meets the preset escalation conditions.

[0013] In some embodiments, before sending the corresponding upgrade package to at least one of the target devices, the method further includes: Based on the correspondence between the preset upgrade conditions and the preset upgrade packages, at least one candidate upgrade package is determined; If the device type corresponding to the candidate upgrade package matches the device type of the target device, the candidate upgrade package will be used as the upgrade package corresponding to the target device. If the candidate upgrade package includes multiple device types that match the target device, a sub-upgrade package corresponding to the device type that matches the target device is extracted from the candidate upgrade package, and the sub-upgrade package is used as the upgrade package corresponding to the target device.

[0014] In some embodiments, sending the corresponding upgrade package to at least one of the target devices satisfies at least one of the following: Upon receiving upgrade package instruction information input by the user through a visual interface, at least one upgrade package indicated by the upgrade package instruction information shall be regarded as an upgrade package corresponding to at least one of the target devices; Based on the priority of the first alarm event, a corresponding upgrade package is sent to at least one of the target devices.

[0015] In some embodiments, sending a corresponding upgrade package to at least one of the target devices based on the priority of the first alarm event includes: If the priority of the first alarm event is higher than the priority of the second alarm event, send the corresponding upgrade package to at least one of the target devices; The second alarm event is an alarm event corresponding to other upgrade packages to be sent by the cloud server.

[0016] Secondly, the present invention also provides an alarm event processing apparatus, the apparatus comprising: The acquisition module is used to acquire the first alarm event; the first alarm event is used to characterize the abnormal operation of the smart device; The sending module is configured to, upon determining that the first alarm event meets preset upgrade conditions, identify at least one target device to be upgraded and send a corresponding upgrade package to at least one of the target devices; wherein the preset upgrade conditions indicate alarm events that support processing through device upgrades.

[0017] Thirdly, the present invention also provides a method for processing alarm events, the method comprising: Send a first alarm event, which is used to characterize the abnormal operation of the smart device.

[0018] Fourthly, the present invention also provides an intelligent system, comprising: at least one intelligent device and a cloud server, wherein at least one intelligent device is connected to the cloud server; The smart device is used to send a first alarm event, which indicates that the smart device is malfunctioning. The cloud server is used to acquire the first alarm event; if it is determined that the first alarm event meets the preset upgrade conditions, it determines at least one target device to be upgraded and sends a corresponding upgrade package to at least one target device; wherein, the preset upgrade conditions indicate alarm events that support processing through device upgrade.

[0019] Fifthly, the present invention also provides an electronic device, including a memory and a processor, wherein the memory stores a computer program, and the processor is configured to run the computer program to implement the alarm event processing method described in the first or third aspect above.

[0020] In a sixth aspect, the present invention also provides a non-transitory computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the alarm event processing method described in the first or third aspect above.

[0021] In a seventh aspect, the present invention also provides a computer program product, including a computer program that, when executed by a processor, implements the alarm event processing method described in the first or third aspect above.

[0022] Compared with existing technologies, the alarm event processing method, apparatus, device, and storage medium provided by this invention can be applied to a cloud server used to monitor alarm events, allowing the cloud server to handle alarm events from smart devices more promptly. Specifically, after obtaining a first alarm event indicating abnormal operation of a smart device, the cloud server can first determine whether the first alarm event meets preset upgrade conditions. If the preset upgrade conditions are met, it is considered that the alarm event can be handled through device upgrade. Therefore, the cloud server can identify at least one target device to be upgraded and send a corresponding upgrade package to at least one target device, so that the target device can upgrade using the corresponding upgrade package, thereby resolving the alarm event. Compared with the manual handling of alarms by technicians periodically in related technologies, this application, using the above-mentioned alarm event processing method, can handle alarm events that can be handled through device upgrade more promptly and effectively, reducing the possibility of damage after continuous abnormal operation of the device, improving the stability and reliability of device operation, and improving the efficiency of device fault handling.

[0023] Details of one or more embodiments of the present invention are set forth in the following drawings and description to make other features, objects and advantages of the invention more readily apparent. Attached Figure Description

[0024] The accompanying drawings, which are included to provide a further understanding of the invention and constitute a part of this invention, illustrate the invention. Those skilled in the art will recognize that other drawings can be derived from these drawings without any inventive effort. The illustrative embodiments of the invention and their descriptions are used to explain the invention and do not constitute an undue limitation of the invention. In the drawings: Figure 1 This is one of the flowcharts illustrating the alarm event processing method provided by the present invention.

[0025] Figure 2 This is the second flowchart illustrating the alarm event handling method provided by the present invention.

[0026] Figure 3This is the third flowchart illustrating the alarm event handling method provided by the present invention.

[0027] Figure 4 This is a schematic diagram of the alarm event processing device provided by the present invention.

[0028] Figure 5 This is the fourth flowchart illustrating the alarm event handling method provided by the present invention.

[0029] Figure 6 This is a schematic diagram of the structure of the intelligent system provided by the present invention.

[0030] Figure 7 This is a schematic diagram of the physical structure of the electronic device provided by the present invention. Detailed Implementation

[0031] To more clearly understand the objectives, technical solutions, and advantages of this invention, the technical solutions of this invention will be clearly and completely described and explained below with reference to the accompanying drawings and embodiments. Obviously, the described embodiments are only some embodiments of this invention, not all embodiments. Based on the embodiments of this invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this invention.

[0032] Unless otherwise defined, the technical or scientific terms used in this invention shall have the general meaning understood by one of ordinary skill in the art to which this invention pertains. Words such as “a,” “an,” “an,” “the,” “the,” and “these” used in this invention do not indicate quantitative limitation and may be singular or plural. The terms “comprising,” “including,” “having,” and any variations thereof used in this invention are intended to cover non-exclusive inclusion; for example, a process, method, system, product, or device that comprises a series of steps or modules (units) is not limited to the listed steps or modules (units) but may include steps or modules (units) not listed, or may include other steps or modules (units) inherent to these processes, methods, products, or devices. The terms “connected,” “linked,” and “coupled” used in this invention are not limited to physical or mechanical connections but may include electrical connections, whether direct or indirect. “A plurality” used in this invention refers to two or more. “And / or” describes the relationship between related objects, indicating that three relationships may exist; for example, “A and / or B” can represent: A alone, A and B simultaneously, and B alone. Normally, the character " / " indicates that the objects before and after it are in an "or" relationship. The terms "first," "second," "third," etc., used in this invention are merely for distinguishing similar objects and do not represent a specific ordering of the objects.

[0033] The alarm event processing method, apparatus, device, and storage medium of the present invention are described below with reference to the accompanying drawings.

[0034] In the first aspect, the present invention provides a method for processing alarm events, which can be applied to a cloud server used to monitor alarm events. The cloud server can reuse an existing management platform or be an independently set platform, and this application does not limit this.

[0035] Figure 1 This is one of the flowcharts illustrating the alarm event processing method provided by the present invention, such as... Figure 1 As shown, the handling method for this alarm event includes the following steps: Step 101: Obtain the first alarm event. The first alarm event is used to characterize abnormal operation of the smart device.

[0036] It should be noted that the above-mentioned abnormal operation of smart devices may be due to the smart device itself malfunctioning, lacking operating permissions, or having an incompatible software version; or malfunctioning, lacking operating permissions, or having an incompatible software version of other devices connected to the smart device.

[0037] Therefore, the first alarm event can correspond to one or more devices, or to one or more types of devices, without any restrictions.

[0038] For example, a first alarm event corresponds to an alarm or fault occurring in a certain inverter; another example is that a first alarm event corresponds to an alarm or fault occurring in both an inverter and an energy storage device.

[0039] Optionally, obtaining the first alarm event may include the following specific implementation: after receiving device information reported by one or more devices, or one or more types of devices, determine that the first alarm event has occurred based on this device information.

[0040] This solution can be executed by a gateway or a cloud server.

[0041] Step 102: If the first alarm event meets the preset upgrade conditions, determine at least one target device to be upgraded and send the corresponding upgrade package to at least one target device. Among them, the preset upgrade conditions are used to restrict whether alarm events are handled through device upgrades.

[0042] It should be noted that the at least one target device to be upgraded as determined by the cloud server mentioned above may be at least some of the smart devices corresponding to the first alarm event, or other related devices. This application does not impose any restrictions on this.

[0043] For example, if the first alarm event is: the data acquisition device generates an alarm and the energy storage device generates an alarm, then the cloud server can determine at least one target device to be upgraded based on the first alarm event. This target device can be either the data acquisition device or the energy storage device, or both the data acquisition device and the energy storage device, or other devices such as the inverter or backup power box related to the data acquisition device.

[0044] For example, if the abnormal operation of the smart device indicated by the first alarm event refers to a fault in the smart device itself, lack of running permissions, or incompatibility of the software version, then the smart device can be identified as the target device.

[0045] For example, if the abnormal operation of the smart device represented by the first alarm event mentioned above refers to the failure of other devices connected to the smart device, lack of running permissions, or incompatibility of software versions, then the other devices connected to the smart device can be identified as the target device.

[0046] For example, the output voltage of microinverters and energy storage devices is set to 220V at the factory in my country, while the actual products are installed in the United States (where the grid voltage is 110V). If the above devices are installed and used directly in the United States, abnormal operation will occur. In this case, cloud server assistance is needed to upgrade the above devices before they can be used to make them suitable for the grid voltage of 110V.

[0047] It should also be noted that not all alarm events can be handled through equipment upgrades. For example, if an energy storage device is damaged and cannot be used due to a fault, the fault cannot be resolved by upgrading the energy storage device.

[0048] The alarm event processing method in this application embodiment is for alarm events that can be processed through device upgrades. Therefore, after the cloud server obtains the first alarm event, it needs to determine whether the first alarm event is an alarm event that can be processed through device upgrades. Specifically, this is determined by whether the first alarm event meets the preset upgrade conditions.

[0049] If the first alarm event is determined to meet the preset upgrade conditions, it is considered that the first alarm event is an alarm event that can be handled through device upgrade. Therefore, the cloud server can determine at least one target device to be upgraded based on the first alarm event. It is believed that the alarm can be cleared after upgrading the device of the at least one target device. The cloud server then sends the corresponding upgrade package to the at least one target device so that the at least one target device can use the corresponding upgrade package to upgrade the device and clear the alarm.

[0050] It should also be noted that the upgrade package corresponding to the target device can be an upgrade package that corresponds to at least one of the device type, device model and device version number of the target device.

[0051] For example, if the target device is a data acquisition device, the upgrade package corresponding to the data acquisition device can be sent to the data acquisition device as the upgrade package corresponding to the target device, so that the data acquisition device can use the upgrade package to upgrade.

[0052] Optionally, a preset database may store multiple upgrade packages, which correspond to at least one of the device type, device model, and device version number, so that the cloud server can call the required upgrade package and send it to the device for upgrade.

[0053] Optionally, if the cloud server determines that the first alarm event does not meet the preset upgrade conditions, it considers that the first alarm event cannot be handled by device upgrade. Therefore, it can output alarm prompt information, such as displaying the alarm through a visual interface or providing voice reminders, to promptly remind technicians to handle the alarm and reduce the impact on the normal operation of the system.

[0054] In this embodiment, the alarm event handling method can be applied to a cloud server used to monitor alarm events, allowing the cloud server to handle alarm events from smart devices more promptly. Specifically, after obtaining a first alarm event indicating abnormal operation of a smart device, the cloud server can first determine whether the first alarm event meets preset upgrade conditions. If the preset upgrade conditions are met, it is considered that the alarm event can be handled through device upgrade. Therefore, the cloud server can identify at least one target device to be upgraded and send a corresponding upgrade package to at least one target device, so that the target device can upgrade using the corresponding upgrade package, thereby resolving the alarm event. Compared to the manual handling of alarms by technicians periodically in related technologies, this application, using the above-mentioned alarm event handling method, can handle alarm events that can be handled through device upgrade more promptly and effectively, reducing the possibility of damage after continuous abnormal operation of the device, improving the stability and reliability of device operation, and improving the efficiency of device fault handling.

[0055] In some embodiments, a specific implementation method is provided for determining that the first alarm event meets preset escalation conditions. In step 102 above, a specific implementation method for determining that the first alarm event meets preset escalation conditions may include: Step 1-1: Determine whether the target feature information in the first alarm event matches the preset upgrade rule in the preset upgrade rule library; If so, then the first alarm event is determined to meet the preset escalation conditions.

[0056] It should be noted that the aforementioned target characteristic information includes, for example, device attribute information and alarm attribute information related to the first alarm event. This device attribute information and alarm attribute information can be used to determine whether the first alarm event can be handled through device upgrades. For example, if the device type related to the first alarm event is a certain type (such as a data acquisition device), then it is considered that the alarm event can be handled through device upgrades.

[0057] Specifically, the cloud server may have a built-in or pre-stored pre-set upgrade rule library, which may include multiple pre-set upgrade rules.

[0058] When determining whether the first alarm event meets the preset upgrade conditions, the cloud server can use multiple preset upgrade rules in the preset upgrade rule library for judgment. Specifically, the cloud server can first extract the corresponding target feature information from the first alarm event to facilitate matching among multiple preset upgrade rules in the preset upgrade rule library. If the target feature information matches the preset upgrade rules in the preset upgrade rule library, it is determined that the first alarm event meets the preset upgrade conditions, and it is considered that the alarm event can be handled through device upgrade.

[0059] Optionally, a specific implementation of the target feature information is provided. The target feature information may include: a device identifier and at least one of the following: Alarm identifier, alarm type, alarm duration, device version number; The device identifier is used to indicate the device's registration information.

[0060] It should be noted that the above-mentioned device identifier can be used to indicate the device type of at least one device, such as inverter, residential / commercial energy storage device, data acquisition device, backup power box, etc. It can also be used to indicate the device's registration information: registration region, service provider information, user information, etc.

[0061] It should also be noted that the above alarm identifier can be used to indicate that at least one device generates an alarm, or it can be used to indicate the alarm type corresponding to the first alarm event, such as whether the first alarm event is an alarm generated by a single device or an alarm generated by multiple devices, or it can be used to indicate whether the alarm type corresponding to the first alarm event supports processing through device upgrades. This application does not impose any restrictions on this.

[0062] It should also be noted that the above alarm types can indicate whether the first alarm event is generated by a single device or multiple devices; they can also indicate the nature of the alarm, such as device hardware failure, performance bottleneck, logic error, etc.; and they can also indicate whether the first alarm event can be handled through device upgrade, which is not limited in this application.

[0063] It should also be noted that the alarm duration mentioned above indicates the duration from the time the alarm occurred to the current time.

[0064] It should also be noted that the device version number mentioned above can indicate the version information of the operating system or firmware that the device is running.

[0065] In some embodiments, a specific implementation method is provided for determining whether a first alarm event meets a preset escalation condition using a first type of escalation rule. The first alarm event may include target feature information; the preset escalation rule base may include multiple first type escalation rules, and each first type escalation rule may include a preset sub-escalation condition; Step 1-1 above may include: Steps 1-11: Match a target feature with a preset sub-upgrade condition in each first type upgrade rule. If a matching first type upgrade rule exists, determine that the first alarm event meets the preset upgrade condition.

[0066] It should be noted that a target feature may include a device identifier and at least one of the following: alarm identifier, alarm type, alarm duration, and device version number.

[0067] For example, target characteristic information may include an inverter (device identifier) ​​generating an XX1 alarm (alarm identifier and / or alarm type).

[0068] For example, a target characteristic information may include an inverter (device identifier) ​​generating an XX1 alarm (alarm identifier and / or alarm type) that has been in effect for 5 minutes (alarm duration).

[0069] Specifically, the preset upgrade rule base may include multiple first-type upgrade rules, and these first-type upgrade rules may include a preset sub-upgrade condition. If a target feature of an alarm event matches a preset sub-upgrade condition in a first-type upgrade rule, then it can be determined that the alarm event meets the preset upgrade condition.

[0070] For the first alarm event, if it includes a target feature, multiple first-type upgrade rules in the preset upgrade rule base can be used to determine whether the first alarm event meets the preset upgrade conditions. Specifically, the cloud server can match the target feature included in the first alarm event with multiple first-type upgrade rules. If the target feature included in the first alarm event matches a preset sub-upgrade condition in a certain first-type upgrade rule, then it can be determined that the first alarm event meets the preset upgrade conditions.

[0071] For example, the aforementioned preset upgrade rule base includes three first-type upgrade rules: rule 1, rule 2, and rule 3.

[0072] Rule 1 includes condition A, rule 2 includes condition B, and rule 3 includes condition C; the first alarm event 1 includes target feature information 1.

[0073] The target feature information is matched with condition A in rule 1, condition B in rule 2, and condition C in rule 3 respectively. If it matches condition A, the first alarm event 1 is determined to meet the preset escalation conditions.

[0074] For example, the target feature information included in the first alarm event is, for example, that the inverter generates an XX1 alarm. If a preset sub-upgrade condition in a certain first type of upgrade rule is that the inverter generates an XX1 alarm, then it can be considered that the target feature information included in the first alarm event matches a preset sub-upgrade condition in the first type of upgrade rule. At this time, it can be determined that the first alarm event meets the preset upgrade condition.

[0075] In some embodiments, a specific implementation method is provided for determining whether a first alarm event meets preset escalation conditions using a second type of escalation rule. The first alarm event may include multiple target feature information; the preset escalation rule base may include multiple second type escalation rules, and the second type escalation rules may include multiple preset sub-escalation conditions; For example, the aforementioned preset upgrade rule base includes three second-type upgrade rules: rule 4, rule 5, and rule 6.

[0076] Rule 4 includes conditions B, C, and D; rule 5 includes conditions A and B; and rule 6 includes conditions A1, A2, B1, B2, and C. Conditions A1 and A2, for example, represent conditions A applicable to different devices or device types, and conditions B1 and B2 are similar. The first alarm event 2 includes multiple target feature information items 2, 3, and 4.

[0077] Multiple target feature information 2, 3, and 4 are matched with the conditions in rules 4, 5, and 6 respectively. If target feature information 2 matches condition B, target feature information 3 matches condition D, and target feature information 4 matches condition C, then the first alarm event 2 is determined to meet the preset escalation conditions.

[0078] Step 1-1 above may include: Steps 1-12: Match multiple target feature information with multiple preset sub-upgrade conditions in each second type upgrade rule; if a matching second type upgrade rule exists, determine that the first alarm event meets the preset upgrade conditions.

[0079] It should be noted that multiple target feature information may include multiple device identifiers and at least one of the following: alarm identifier, alarm type, alarm duration, and device version number.

[0080] For example, multiple target feature information may include: 1) The inverter (device identifier) ​​generates an XX1 alarm (alarm identifier and / or alarm type).

[0081] 2) The energy storage device (device identifier) ​​generates an XX2 alarm (alarm identifier and / or alarm type).

[0082] For example, multiple target feature information may include: 1) The inverter (device identifier) ​​generated an XX1 alarm (alarm identifier and / or alarm type) which has been in effect for 5 minutes (alarm duration).

[0083] 2) The backup power box (equipment identifier) ​​generates an XX3 alarm (alarm identifier and / or alarm type).

[0084] Specifically, the preset upgrade rule base may include multiple second-type upgrade rules, which may include multiple preset sub-upgrade conditions. If multiple target feature information of an alarm event matches multiple preset sub-upgrade conditions in a certain second-type upgrade rule, it can be determined that the alarm event meets the preset upgrade conditions.

[0085] For a first alarm event, if the first alarm event includes a combination of multiple target feature information, multiple second-type upgrade rules in the preset upgrade rule base can be used to determine whether the first alarm event meets the preset upgrade conditions. Specifically, the cloud server can match the combination of multiple target feature information included in the first alarm event with multiple second-type upgrade rules. If the combination of multiple target feature information included in the first alarm event matches a combination of multiple preset sub-upgrade conditions in a certain second-type upgrade rule, then it can be determined that the first alarm event meets the preset upgrade conditions.

[0086] For example, the first alarm event includes multiple target feature information such as: 1) The inverter generates an XX1 alarm; 2) The energy storage device generates an XX2 alarm.

[0087] If a second type of upgrade rule includes both preset sub-upgrade conditions related to the inverter and the generation of alarm XX1, and preset sub-upgrade conditions related to the energy storage device and the generation of alarm XX2, then the combination of multiple target feature information included in the first alarm event can be considered to match the combination of multiple preset sub-upgrade conditions in the second type of upgrade rule. In this case, it can be determined that the first alarm event meets the preset upgrade conditions.

[0088] In some embodiments, a specific implementation of preset sub-upgrade conditions is provided. The preset sub-upgrade conditions can be the following: 1) Condition A: Does a preset alarm flag exist? 2) Condition B: Whether the preset alarm duration has been reached; 3) Condition C: Does there exist a situation where every device type-alarm type combination in the first set generates an alarm? The first set includes K combinations of device types-alarm types, where K is a natural number and K>=1; 4) Condition D: Does there exist a situation where no alarm is generated for each group of device type-alarm type in the second set? The second set includes M groups of device type-alarm type combinations, where M is a natural number and M>=1; Optionally, a specific implementation of the C condition and / or the D condition is provided.

[0089] <1> Condition C can include any of the following: C1 condition: In the first set, is there a situation where the same device type corresponds to multiple first combinations with different alarm types, and multiple first combinations generate alarms? For example, in the inverter device type, at least one device generates an alarm of type XX1, and at least one device generates an alarm of type XX2.

[0090] C2 condition: In the first set, are there multiple second combinations of different device types corresponding to different alarm types, and are there multiple second combinations that all generate alarms? For example, at least one device in the energy storage device category generates an alarm, and at least one device in the backup power box category generates an alarm.

[0091] And / or, <2> Condition D can include any of the following: D1 condition: In the second set, are there multiple third combinations of the same device type corresponding to different alarm types, and are there cases where none of the multiple third combinations generate alarms? For example, the inverter device type did not generate alarms of type XX1, nor did it generate alarms of type XX2.

[0092] D2 condition: In the second set, are there multiple fourth combinations with different device types corresponding to different alarm types, and are there multiple fourth combinations that do not generate alarms?

[0093] For example, no alarms were generated for the energy storage device type and no alarms were generated for the backup power box type.

[0094] For example, assuming K=5, the combinations of K groups of device type-alarm type can be shown in the following table:

[0095] For example, assuming M=4, the combinations of M groups of device types - alarm types can be shown in the following table:

[0096] 5) Condition E: Does the device version number exist that is lower than, equal to, or not equal to the preset version number? The first type of upgrade rule includes any one of conditions A, B, C, D, and E; or, The second type of upgrade rule includes multiple conditions A, B, C, D, and E, where the number of each preset sub-upgrade condition is greater than or equal to 1.

[0097] Specifically, the first type of upgrade rule and the second type of upgrade rule in the aforementioned preset upgrade rule base can be composed of the aforementioned preset sub-upgrade conditions.

[0098] For the first type of upgrade rule, it includes a preset sub-upgrade condition, namely, any one of condition A, condition B, condition C, condition D, and condition E, which is used to determine whether the alarm event related to a single alarm corresponding to a single device or a single device type supports processing through device upgrade.

[0099] For example, the first type of upgrade rule can be illustrated in the following table:

[0100] It should be noted that in the above-mentioned single device or single device type corresponding to a single alarm, a single alarm can refer to a single device generating an alarm (not involving an alarm type or only involving a single alarm type), or at least one device of a single device type generating an alarm of the same alarm type.

[0101] For example, taking an inverter as an example, the following situations are possible: Scenario 1: Single device: 1) A target feature is: if a certain inverter (single device) has a preset alarm flag, then the inverter is instructed to generate an alarm, which satisfies the above condition A and matches rule 1 in the preset rule base.

[0102] 2) A target feature is: a certain inverter (single device) generates an alarm of type XX1. If the C condition of the preset sub-upgrade condition includes the set of (inverter, XX1 alarm), then the above C condition is satisfied and it matches rule 3 in the preset rule base. In this case, the inverter in (inverter, XX1 alarm) refers to the device type.

[0103] Scenario 2: Equipment of a single device type: 1) A target feature is: if at least one device of the inverter type (a single device type) has a preset alarm flag, then the inverter type is instructed to generate an alarm, which satisfies the above condition A and matches rule 1 in the preset rule base.

[0104] 2) A target feature is: In the device type of inverter (a single device type), at least one device generates an alarm of type XX1. If the C condition of the preset sub-upgrade condition includes the set of (inverter, XX1 alarm), then the above C condition is satisfied and it matches rule 3 in the preset rule base.

[0105] The above are merely illustrative examples; other possible combinations will not be described in the embodiments of this application.

[0106] For the second type of upgrade rule, it includes multiple preset sub-upgrade conditions, namely, conditions A, B, C, D, and E, which are used to determine whether alarm events other than the alarm events corresponding to the first type of upgrade rule mentioned above can be processed through device upgrade.

[0107] For example, the second type of upgrade rules can be illustrated in the following table:

[0108] It should be noted that technicians can flexibly set multiple of the following conditions for each rule in the second type of upgrade rules, including conditions A, B, C, D, and E, according to the actual situation. The table above is only an example and does not impose any restrictions.

[0109] Specifically, it can handle the following situations related to alarm events: Scenario 1: The same device generates different alarms, which belong to different alarm types: For example, a certain inverter (single device) generates an alarm of type XX1 and an alarm of type XX2 at the same time.

[0110] Scenario 2: Devices of the same type generate different alarms, where these alarms belong to different alarm categories: For example, in the inverter device type, at least one device generates an alarm of type XX1, and at least one device generates an alarm of type XX2.

[0111] Scenario 3: Alarms are generated by different types of equipment: For example, at least one device in the energy storage device category generates an alarm, and at least one device in the backup power box category generates an alarm.

[0112] For example, at least one device in the energy storage device category generates an alarm of type XX3, and at least one device in the backup power box category generates an alarm of type XX4.

[0113] For example, in the energy storage device category, at least one device generates an alarm of type XX3; in the backup power box category, at least one device generates an alarm of type XX4; and in the inverter category, at least one device generates an alarm of type XX1.

[0114] Scenario 4: Among devices of different types, some generate alarms while others do not: For example, at least one device in the energy storage device category generates an alarm, while none of the devices in the inverter category generate an alarm.

[0115] For example, at least one device in the energy storage device category generates an alarm of type XX3, while no devices in the inverter category generate any alarms.

[0116] The above are merely illustrative examples; other possible combinations will not be described in the embodiments of this application.

[0117] For example, when using multiple target feature information for rule matching, if the multiple target feature information is: a certain inverter (single device) has a preset alarm identifier and the alarm duration is 5 minutes, then it indicates that the inverter generates an alarm and the alarm duration has reached the preset alarm duration (for example, set to 2 minutes), which satisfies the above conditions A and B, and matches rule 5 in the preset rule base.

[0118] In some embodiments, determining whether the target feature information matches the preset sub-upgrade conditions may include at least one of the following: 1) Determine the type of alarm device: If the first alarm event corresponds to receiving alarm information from a certain device, the cloud server can determine whether there is a preset upgrade rule corresponding to the alarm ID in the preset upgrade rule library based on the alarm identifier (ID) of the received device. If there is, it is considered that the upgrade of the corresponding device is supported, such as the upgrade of inverters, residential / commercial energy storage devices, data acquisition devices, backup power boxes and other device types.

[0119] 2) Determine the alarm duration: Cloud servers can be configured to handle alarm events immediately or after a certain period of time, depending on the device type and alarm type. If an alarm event is set to be handled after a certain period of time, and the alarm event disappears before the preset alarm duration is reached, then the alarm event does not need to be handled, nor does the alarm trigger escalation process need to be executed.

[0120] 3) Equipment type combination judgment: The alarm trigger escalation process is only executed when multiple alarm combinations are met simultaneously. The alarms in the multiple alarm combinations are related by, but are not limited to, AND and NOT logic.

[0121] Example 1: For the same type of equipment or the same equipment, such as an inverter, both generate alarm XX1 and alarm XX2.

[0122] Example 2: Different types of equipment, such as energy storage equipment generating alarm XX, and at the same time, the backup power box generates alarm XX.

[0123] Example 3: Different types of equipment, such as energy storage equipment generating alarm XX, while the inverter does not generate alarm XX.

[0124] 4) Device version number rules: Upgrades can only be performed after certain conditions are met: Example 1: An upgrade is only performed when the inverter generates an XX alarm and the inverter's device version number is equal to, <, > or ≠ .xx.xx.xx version (i.e., the default version number).

[0125] Example 2: An upgrade will only be performed when the inverter generates an XX alarm and the device version number of the energy storage device is equal to, <, > or ≠ .xx.xx.xx version (i.e., the preset version number).

[0126] It should be noted that the above preset version number can be flexibly set according to device type, etc., and the preset version number corresponding to different device types is often different.

[0127] In some of these embodiments, a specific implementation of handling alarm events via user instructions is provided. Figure 2 This is a second flowchart illustrating the alarm event processing method provided by the present invention, as shown below. Figure 2As shown, after step 101, the following steps may also be included: Step 103: Display the first alarm event through a pre-set visual interface; Step 104: Upon receiving an alarm processing instruction input by the user through the visual interface, determine whether the first alarm event meets the preset escalation conditions.

[0128] Specifically, a visual interface can be set up on the cloud server side. After the cloud server obtains the first alarm event, it can first display the first alarm event through the visual interface for users to view.

[0129] If a user believes that the first alarm event needs to be handled, they can input alarm handling instructions through the visual interface to instruct the cloud server to handle the first alarm event. After receiving the alarm handling instructions, the cloud server will determine whether the first alarm event meets the preset escalation conditions and proceed with the subsequent processing flow. The visual interface provides a human-computer interaction interface, which makes it easy for users to choose whether to execute the alarm event handling process for the first alarm event according to the actual situation, thus improving the flexibility of the system.

[0130] If the cloud server does not receive an alarm handling instruction within a certain period of time, it can choose to automatically execute the alarm event handling process or not execute the alarm event handling process according to the pre-configuration.

[0131] In some embodiments, a specific implementation method for obtaining the upgrade package corresponding to the target device is provided. In step 102 above, before sending the corresponding upgrade package to at least one target device, the following steps may also be included: Step 2-1: Based on the correspondence between preset upgrade conditions and preset upgrade packages, determine at least one candidate upgrade package; Step 2-21: If the device type of the candidate upgrade package matches the device type of the target device, the candidate upgrade package is used as the upgrade package corresponding to the target device. Step 2-22: If multiple device types corresponding to the candidate upgrade package include a device type that matches the target device, split the candidate upgrade package into a sub-upgrade package corresponding to the device type that matches the target device, and use the sub-upgrade package as the upgrade package corresponding to the target device.

[0132] It should be noted that steps 2-21 and 2-22 above are steps to be performed selectively based on the conditions that are met.

[0133] It should also be noted that the correspondence between the above-mentioned preset upgrade conditions and preset upgrade packages can be stored in the preset upgrade rule base in advance.

[0134] Specifically, after determining that the first alarm event meets the preset upgrade conditions and identifying at least one target device to be upgraded, the cloud server needs to first obtain the upgrade package corresponding to at least one target device and send the upgrade package to the corresponding target device so that the target device can perform the device upgrade.

[0135] When obtaining the upgrade package corresponding to the target device, the cloud server can determine at least one candidate upgrade package based on the correspondence between preset upgrade conditions and preset upgrade packages. For example, if the first alarm event meets a certain preset upgrade condition, the cloud server can use the preset upgrade package corresponding to that preset upgrade condition as a candidate upgrade package.

[0136] For a given candidate upgrade package, the following two scenarios may exist: Scenario 1: If the device type of the candidate upgrade package matches the device type of the target device, the cloud server will directly use the candidate upgrade package as the upgrade package corresponding to the target device.

[0137] For example, if the device type corresponding to the candidate upgrade package is an inverter, and the device type of the target device is also an inverter, the cloud server can directly use the candidate upgrade package as the upgrade package corresponding to the target device.

[0138] Scenario 2: If the candidate upgrade package corresponds to multiple device types, including the device type that matches the target device, the cloud server will split the candidate upgrade package into a sub-upgrade package corresponding to the device type that matches the target device, and use the sub-upgrade package as the upgrade package corresponding to the target device.

[0139] For example, if a candidate upgrade package corresponds to multiple device types - inverter, data acquisition device and energy storage device, and the target device is an inverter, then the cloud server needs to split the candidate upgrade package into a sub-upgrade package corresponding to the inverter, and use the sub-upgrade package as the upgrade package corresponding to the target device.

[0140] For example, identifying at least one target device to be upgraded and sending a corresponding upgrade package to at least one of the target devices can include the following specific implementation methods: 1) The device type of the target device is consistent with the device type in the upgrade package: When the target device and the upgrade package are a perfect match, select the appropriate upgrade package and send it directly to the target device.

[0141] Scenario 1: An inverter generates an XX alarm. Select an upgrade package for one inverter and send it to the inverter.

[0142] Scenario 2: When an energy storage device generates an alarm, select an upgrade package for one backup power box and send it to the backup power box.

[0143] Scenario 3: The inverter generates alarm XX and the energy storage device generates alarm XX. Select the upgrade package for the inverter + energy storage device and send it to the inverter and the energy storage device respectively.

[0144] Scenario 4: When both the inverter and the energy storage device generate alarm XX, only the upgrade package corresponding to the inverter is sent to the inverter.

[0145] 2) The device type of the target device is inconsistent with the device type in the upgrade package: The upgrade package only requires upgrade packages corresponding to the inverter and data acquisition device. However, if the candidate upgrade package includes upgrade packages for the inverter, data acquisition device, and energy storage device, the cloud server can split the candidate upgrade package, obtain only the upgrade packages for the inverter and data acquisition device, and distribute them to the inverter and data acquisition device respectively.

[0146] Optionally, after obtaining the upgrade package corresponding to the target device, the cloud server can choose to immediately distribute the upgrade package, delay the distribution of the upgrade package for a certain period of time, or distribute the upgrade package after completing a certain operation, based on the pre-set or user-indicated execution time, as follows: 1) Upgrade Now: After obtaining the upgrade package corresponding to the target device, the cloud server immediately sends the upgrade package to the corresponding device to perform the upgrade.

[0147] 2) Delay the upgrade for a certain period of time: After obtaining the upgrade package corresponding to the target device, the cloud server can set a certain delay, such as 30 minutes, before sending the upgrade package to the corresponding device for upgrade execution.

[0148] 3) Upgrade after fulfilling certain operational requirements: For alarms generated during the power plant commissioning process, you can choose to upgrade at a certain step during commissioning (equipment commissioning) or wait until commissioning is completed before issuing the upgrade package to the corresponding equipment for upgrade execution.

[0149] In some embodiments, in step 102 above, sending the corresponding upgrade package to at least one target device can satisfy at least one of the following: 1) Upon receiving upgrade package instruction information input by the user through the visual interface, at least one upgrade package indicated by the upgrade package instruction information shall be used as the upgrade package corresponding to at least one target device; 2) Based on the priority of the first alarm event, send the corresponding upgrade package to at least one target device.

[0150] Specifically, on the one hand, through human-computer interaction, the user can indicate at least one upgrade package corresponding to the target device. A visual interface can be used as the interface for human-computer interaction. When the cloud server receives the upgrade package instruction information input by the user through the visual interface, it can take the at least one upgrade package indicated by the upgrade package instruction information as the upgrade package corresponding to at least one target device for subsequent distribution.

[0151] On the other hand, when the cloud server sends the corresponding upgrade package to at least one target device, it can refer to the priority of the first alarm event. For example, if the priority of the first alarm event is the highest, it can send the corresponding upgrade package to at least one target device after sending the current upgrade package.

[0152] For example, when the cloud server receives upgrade package instruction information input by the user through the visual interface, it can use at least one upgrade package indicated by the upgrade package instruction information as the upgrade package corresponding to at least one target device, and then send the corresponding upgrade package to at least one target device with reference to the priority corresponding to the first alarm event.

[0153] In some embodiments, a specific implementation of sending upgrade packages based on priority is provided. The specific implementation of sending a corresponding upgrade package to at least one target device based on the priority of the first alarm event may include: If the priority of the first alarm event is higher than the priority of the second alarm event, send the corresponding upgrade package to at least one target device; The second alarm event is an alarm event corresponding to other upgrade packages to be sent by the cloud server.

[0154] Specifically, the cloud server can first compare the priority of the first alarm event with the priority of the second alarm event corresponding to other upgrade packages to be sent by the cloud server. If the priority of the first alarm event is higher than the priority of the second alarm event, the corresponding upgrade package will be sent to at least one target device first.

[0155] The following example illustrates the alarm event handling method provided in the embodiments of this application, which relates to over-the-air (OTA) upgrades of smart devices at energy sites.

[0156] In related technologies, when equipment malfunctions or fails to operate normally under specific conditions, on-site personnel often struggle to accurately and promptly diagnose the cause. Manual upgrades also often fail to provide accurate and timely updates, resulting in low problem-solving efficiency. Furthermore, for certain alarms on some products, failure to promptly upgrade the equipment can lead to damage.

[0157] Figure 3 This is the third flowchart illustrating the alarm event processing method provided by the present invention, as shown below. Figure 3 As shown, it includes the following steps: Step 301: The cloud server digitizes the alarms of the power station equipment and generates alarm IDs, so that the alarms can be uniquely identified by the equipment type and alarm ID.

[0158] Optionally, the aforementioned power station equipment may include, for example, inverters, energy storage devices, backup power boxes, and data acquisition devices.

[0159] Optionally, an alarm ID can be represented by one or more codes, or by an alarm ID plus a cause ID, where the cause ID is used to indicate the cause of the alarm, such as the specific reason for the abnormal operation of the smart device.

[0160] Step 302: The cloud server completes the sorting out of alarm trigger upgrade rules and embeds them into the cloud server.

[0161] Specifically, alarms based on device type and device upgrade requirements are planned and organized into rules, which are then embedded into the cloud server.

[0162] Step 303: The device generates an alarm and uploads the alarm information to the cloud server.

[0163] Optionally, the alarm information may include the device serial number (SN) and the alarm ID, whereby the device serial number can indicate which device generated the alarm.

[0164] Specifically, after one or more devices in a power plant generate an alarm, they actively report the device alarm and upload the alarm information to the cloud server.

[0165] Step 304: The cloud server determines whether the alarm event corresponding to the alarm information meets the preset upgrade conditions based on the alarm trigger upgrade rules.

[0166] It should be noted that the implementation details regarding whether an alarm event meets the preset escalation conditions can be found in the above embodiments and will not be repeated here.

[0167] Specifically, the cloud server listens to the data reports from each power station. When it detects an alarm in a power station, it immediately executes the alarm trigger escalation rules and determines whether the alarm event corresponding to the alarm information meets the preset escalation conditions.

[0168] Step 305: After determining that the alarm event corresponding to the alarm information meets the preset upgrade conditions, the cloud server sends out the upgrade package selected according to the rules.

[0169] Step 306: The device performs an upgrade task based on the upgrade package.

[0170] Specifically, after receiving the upgrade package, the power station selects the corresponding equipment to perform the upgrade based on the upgrade content in the package.

[0171] Step 307: After the device upgrade is completed, the alarm disappears.

[0172] In the embodiments of this application, at least the following beneficial effects exist: 1) This solution addresses the challenges of timely detection, accurate diagnosis, and rapid resolution of equipment malfunctions, often leading to equipment damage due to delayed handling. Specifically, the cloud server monitors equipment status in real-time. Upon detecting an alarm, it automatically and immediately upgrades the system according to established rules, improving the timeliness of problem resolution and reducing equipment damage caused by untimely upgrades.

[0173] 2) Supports multi-dimensional combination logic for alarms of various device types, multiple devices, alarm duration, software version, etc., to better meet various complex scenarios.

[0174] 3) Based on different device types, alarms can be generated by customizing different built-in rules and selecting different upgrade packages to meet different usage scenarios.

[0175] 4) By identifying and marking potential alarms generated by the device and conducting a comprehensive analysis of the upgrade strategy after the alarm is generated, the rules and device upgrade packages are pre-built into the cloud server. During the generation, transmission, and storage of alarms, the device is marked with an identifier. After receiving the corresponding alarm identifier, the cloud server finds the corresponding upgrade package based on the various built-in rules and automatically triggers the device upgrade, thereby achieving the goal of quickly handling problems and avoiding device damage.

[0176] It should be noted that the steps shown in the above process or in the flowchart of the accompanying figures can be executed in a computer system such as a set of computer-executable instructions, and although a logical order is shown in the flowchart, in some cases the steps shown or described may be executed in a different order than that shown here.

[0177] Secondly, the present invention also provides an alarm event processing apparatus for implementing the above embodiments and preferred embodiments, which will not be repeated hereafter. The terms "module," "unit," "subunit," etc., used below refer to combinations of software and / or hardware that implement a predetermined function. Although the apparatus described in the following embodiments is preferably implemented in software, hardware implementation, or a combination of software and hardware, is also possible and contemplated. The alarm event processing apparatus provided by the present invention will be described below, and the alarm event processing apparatus described below corresponds to the alarm event processing method described above.

[0178] Figure 4This is a schematic diagram of the alarm event processing device provided by the present invention, as shown below. Figure 4 As shown, the alarm event processing device 400 includes: The acquisition module 401 is used to acquire the first alarm event; the first alarm event is used to characterize the abnormal operation of the smart device; The sending module 402 is used to determine at least one target device to be upgraded when it is determined that the first alarm event meets the preset upgrade conditions, and send the corresponding upgrade package to the at least one target device; wherein the preset upgrade conditions indicate alarm events that support processing through device upgrade.

[0179] It should be noted that the above modules can be functional modules or program modules, and can be implemented through software or hardware. For modules implemented through hardware, the above modules can reside in the same processor; or the above modules can be located in different processors in any combination.

[0180] Thirdly, this invention also provides a method for handling alarm events, applicable to smart devices. Figure 5 This is the fourth flowchart illustrating the alarm event processing method provided by the present invention, as shown below. Figure 5 As shown, the handling method for this alarm event includes the following steps: Step 501: Send the first alarm event. The first alarm event is used to characterize the abnormal operation of the smart device.

[0181] It should be noted that the above-mentioned abnormal operation of smart devices includes malfunctions of the smart device itself, lack of running permissions, incompatible software versions, etc.; or malfunctions of other devices connected to the smart device, lack of running permissions, incompatible software versions, etc.

[0182] Specifically, for each of the many smart devices, in the event of an abnormal operation, a first alarm event can be sent to the cloud server for the cloud server to handle. Specifically, the cloud server sends a corresponding upgrade package to at least one specific target device among the smart devices, so that the target device can upgrade through the corresponding upgrade package to resolve the first alarm event and enable the device to operate normally.

[0183] Optionally, when a device malfunctions, it may be necessary to upgrade the device to enable it to function properly. After the device sends a first alarm event to the cloud server, the cloud server can determine that the target device is the device based on the first alarm event if it meets the preset upgrade conditions. Then, it can send the corresponding upgrade package to the device. After receiving the corresponding upgrade package, the device can upgrade itself based on the upgrade package.

[0184] For example, if device A malfunctions due to incompatibility with its own software version, the cloud server can identify device A as the target device and send a compatible software version upgrade package to device A, so that device A can upgrade based on the compatible software version upgrade package and thus operate normally.

[0185] Optionally, if the device can operate normally after the upgrade, the first alarm event can be cleared.

[0186] Optionally, if the device still malfunctions after the upgrade, the first alarm event can be reported to the cloud server, which can then send a notification to the user for further processing by technical personnel.

[0187] Fourthly, the present invention also provides an intelligent system. Figure 6 This is a schematic diagram of the structure of the intelligent system provided by the present invention, as shown below. Figure 6 As shown, the intelligent system 600 includes: at least one intelligent device 601 and a cloud server 602, wherein at least one intelligent device 601 is connected to the cloud server 602; The smart device 601 is used to send a first alarm event, which is used to indicate that the smart device is malfunctioning. The cloud server 602 is used to acquire the first alarm event; if the first alarm event meets the preset upgrade conditions, it identifies at least one target device to be upgraded and sends the corresponding upgrade package to the at least one target device; wherein, the preset upgrade conditions indicate alarm events that support processing through device upgrade.

[0188] Optionally, after the above-mentioned at least one smart device 601 is connected to the cloud server 602, it can communicate with the cloud server 602 to facilitate the transmission of the first alarm event and / or upgrade package.

[0189] It should be noted that the implementation details of the operations performed by the intelligent device 601 and the cloud server 602 in the above intelligent system can be referred to the implementation details in any of the above embodiments, and will not be repeated here.

[0190] Fifthly, the present invention also provides an electronic device. Figure 7 This is a schematic diagram of the physical structure of the electronic device provided by the present invention, such as... Figure 7As shown, the electronic device may include: a processor 710, a communications interface 720, a memory 730, and a communication bus 740, wherein the processor 710, the communications interface 720, and the memory 730 communicate with each other via the communication bus 740. The processor 710 can call logical instructions in the memory 730 to execute a method for handling alarm events, the method including: Obtain the first alarm event; the first alarm event is used to characterize abnormal operation of the smart device; If the first alarm event meets the preset upgrade conditions, at least one target device to be upgraded is identified, and a corresponding upgrade package is sent to the at least one target device; wherein, the preset upgrade conditions indicate alarm events that can be processed through device upgrade.

[0191] Furthermore, the logical instructions in the aforementioned memory 730 can be implemented as software functional units and, when sold or used as independent products, can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, in essence, or the part that contributes to the prior art, or a part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods of the various embodiments of the present invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0192] The present invention also provides an electronic device including a memory and a processor, the memory storing a computer program and the processor being configured to run the computer program to perform the steps in any of the above method embodiments.

[0193] Optionally, the electronic device may further include a transmission device and an input / output device, wherein the transmission device is connected to the processor and the input / output device is connected to the processor.

[0194] Optionally, in this embodiment, the processor can be configured to perform the following steps via a computer program: Step 1: Obtain the first alarm event; the first alarm event is used to characterize abnormal operation of the smart device.

[0195] Step 2: If the first alarm event meets the preset upgrade conditions, identify at least one target device to be upgraded and send the corresponding upgrade package to the at least one target device; wherein, the preset upgrade conditions indicate alarm events that can be processed through device upgrade.

[0196] It should be noted that the specific examples in this embodiment can refer to the examples described in the above embodiments and optional implementations, and will not be repeated in this embodiment.

[0197] Fourthly, in conjunction with the alarm event processing method provided in the above embodiments, the present invention also provides a non-transitory computer-readable storage medium storing a computer program, which, when executed by a processor, implements the steps in any of the above alarm event processing method embodiments.

[0198] Fifthly, in conjunction with the alarm event processing method provided in the above embodiments, the present invention also provides a computer program product, which includes a computer program that, when executed by a processor, implements the steps in any of the above method embodiments.

[0199] The device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs. Those skilled in the art can understand and implement this without any creative effort.

[0200] Through the above description of the embodiments, those skilled in the art can clearly understand that each embodiment can be implemented by means of software plus necessary general-purpose hardware platforms, and of course, it can also be implemented by hardware. Based on this understanding, the above technical solutions, in essence or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product can be stored in a computer-readable storage medium, such as ROM / RAM, magnetic disk, optical disk, etc., including several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute the methods of various embodiments or some parts of embodiments.

[0201] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, and not to limit them; although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features; and these modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present invention.

Claims

1. A method for handling alarm events, characterized in that, The method includes: Obtain the first alarm event; the first alarm event is used to characterize abnormal operation of the smart device; If the first alarm event meets the preset upgrade conditions, at least one target device to be upgraded is identified, and a corresponding upgrade package is sent to at least one of the target devices; wherein, the preset upgrade conditions indicate alarm events that can be processed through device upgrade.

2. The alarm event processing method according to claim 1, characterized in that, The step of determining that the first alarm event meets the preset escalation conditions includes: Determine whether the target feature information in the first alarm event matches the preset upgrade rule in the preset upgrade rule library; If so, then the first alarm event is determined to meet the preset escalation conditions.

3. The alarm event processing method according to claim 2, characterized in that, The first alarm event includes target feature information; The preset upgrade rule base includes multiple first-type upgrade rules, and each first-type upgrade rule includes a preset sub-upgrade condition; The step is to determine whether the target feature information in the first alarm event matches the preset upgrade rule in the preset upgrade rule library; If so, then the first alarm event is determined to meet the preset escalation conditions, including: The target feature information is matched with a preset sub-upgrade condition in each of the first type of upgrade rules. If a matching first type of upgrade rule exists, the first alarm event is determined to satisfy the preset upgrade condition.

4. The alarm event processing method according to claim 2, characterized in that, The first alarm event includes multiple target feature information; The preset upgrade rule base includes multiple second-type upgrade rules, and the second-type upgrade rules include multiple preset sub-upgrade conditions; The step is to determine whether the target feature information in the first alarm event matches the preset upgrade rule in the preset upgrade rule library; If so, then the first alarm event is determined to meet the preset escalation conditions, including: The multiple target feature information are matched with multiple preset sub-upgrade conditions in each of the second type of upgrade rules; If a matching second type of upgrade rule exists, then the first alarm event is determined to meet the preset upgrade conditions.

5. The method for handling alarm events according to claim 3 or 4, characterized in that, The preset sub-upgrade conditions are as follows: Condition A: Does a preset alarm indicator exist? Condition B: Has the preset alarm duration been reached? Condition C: Does there exist a situation where every device type-alarm type combination in the first set generates an alarm? The first set includes K combinations of device types-alarm types, where K is a natural number and K>=1. Condition D: Does there exist a situation where no alarm is generated for each device type-alarm type in the second set? The second set includes M combinations of device types-alarm types, where M is a natural number and M>=1. Condition E: Is there a situation where the device version number is lower than, equal to, or not equal to the preset version number? The first type of upgrade rule includes any one of conditions A, B, C, D, and E; or, The second type of upgrade rule includes multiple conditions A, B, C, D, and E, where the number of each preset sub-upgrade condition is greater than or equal to 1.

6. The alarm event processing method according to claim 5, characterized in that, Condition C includes any of the following: C1 condition: In the first set, is there a situation where there are multiple first combinations of the same device type corresponding to different alarm types, and all of the multiple first combinations generate alarms; C2 condition: In the first set, are there multiple second combinations of different device types corresponding to different alarm types, and are there multiple second combinations that all generate alarms? And / or, the D condition includes any of the following: D1 condition: In the second set, is there a situation where the same device type corresponds to multiple third combinations of different alarm types, and none of the multiple third combinations generate an alarm? D2 condition: In the second set, are there multiple fourth combinations with different device types corresponding to different alarm types, and none of the multiple fourth combinations generate an alarm? 7. The method for handling alarm events according to claim 5, characterized in that, The target feature information includes: The device identifier and at least one of the following: alarm identifier, alarm type, alarm duration, and device version number; The device identifier is used to indicate the device's registration information.

8. The method for handling alarm events according to any one of claims 1 to 4, characterized in that, After acquiring the first alarm event, the method further includes: The first alarm event is displayed through a pre-configured visual interface; Upon receiving an alarm handling instruction input by the user through the visual interface, it is determined whether the first alarm event meets the preset escalation conditions.

9. The method for handling alarm events according to any one of claims 1 to 4, characterized in that, Before sending the corresponding upgrade package to at least one of the target devices, the method further includes: Based on the correspondence between the preset upgrade conditions and the preset upgrade packages, at least one candidate upgrade package is determined; If the device type corresponding to the candidate upgrade package matches the device type of the target device, the candidate upgrade package will be used as the upgrade package corresponding to the target device. If the candidate upgrade package includes multiple device types that match the target device, a sub-upgrade package corresponding to the device type that matches the target device is extracted from the candidate upgrade package, and the sub-upgrade package is used as the upgrade package corresponding to the target device.

10. The method for handling alarm events according to any one of claims 1 to 4, characterized in that, Sending the corresponding upgrade package to at least one of the target devices satisfies at least one of the following: Upon receiving upgrade package instruction information input by the user through a visual interface, at least one upgrade package indicated by the upgrade package instruction information shall be regarded as an upgrade package corresponding to at least one of the target devices; Based on the priority of the first alarm event, a corresponding upgrade package is sent to at least one of the target devices.

11. The method for handling alarm events according to claim 10, characterized in that, The step of sending a corresponding upgrade package to at least one of the target devices based on the priority of the first alarm event includes: If the priority of the first alarm event is higher than the priority of the second alarm event, send the corresponding upgrade package to at least one of the target devices; The second alarm event is an alarm event corresponding to other upgrade packages to be sent by the cloud server.

12. An alarm event processing device, characterized in that, The device includes: The acquisition module is used to acquire the first alarm event; the first alarm event is used to characterize the abnormal operation of the smart device; The sending module is configured to, upon determining that the first alarm event meets preset upgrade conditions, identify at least one target device to be upgraded and send a corresponding upgrade package to at least one of the target devices; wherein the preset upgrade conditions indicate alarm events that support processing through device upgrades.

13. A method for handling alarm events, characterized in that, The method includes: Send a first alarm event, which is used to characterize the abnormal operation of the smart device.

14. An intelligent system, characterized in that, include: At least one smart device and a cloud server, wherein at least one of the smart devices is connected to the cloud server; The smart device is used to send a first alarm event, which indicates that the smart device is malfunctioning. The cloud server is used to obtain the first alarm event; If the first alarm event meets the preset upgrade conditions, at least one target device to be upgraded is identified, and a corresponding upgrade package is sent to at least one of the target devices; wherein, the preset upgrade conditions indicate alarm events that can be processed through device upgrade.

15. An electronic device comprising a memory and a processor, characterized in that, The memory stores a computer program, and the processor is configured to run the computer program to perform the alarm event processing method according to any one of claims 1 to 11, or to perform the alarm event processing method according to claim 13.

16. A non-transitory computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by the processor, it implements the alarm event processing method according to any one of claims 1 to 11, or the alarm event processing method according to claim 13.

17. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by the processor, it implements the alarm event processing method according to any one of claims 1 to 11, or the alarm event processing method according to claim 13.

Images