Alarm display method and device, terminal, medium and program product

Abstract

The invention relates to an alarm display method and device, a terminal, a medium and a program product. The method comprises the following steps: displaying a first alarm page, wherein the first alarm page comprises a combined alarm area corresponding to at least one alarm type identifier; in response to a trigger operation for the combined alarm area, a second alarm page is displayed, the second alarm page comprises alarm data of a plurality of alarm events, and the alarm type corresponding to each alarm event is the same as the alarm type represented by the alarm type identifier. By adopting the method, the alarm flexibility can be improved.

Description

Technical Field

[0001] The present application relates to the technical field of alarm display, and in particular to an alarm display method, device, terminal, medium and program product. Background Art

[0002] With the continuous development of new energy technology, the proportion of renewable energy power generation is increasing. However, due to the small single-unit power generation capacity and large number of energy equipment in renewable energy power generation, and the fact that renewable energy power generation is greatly affected by weather, environment, and power grid, a large amount of alarm data is easily generated during the renewable energy power generation process. The intelligent management platform displays each alarm data.

[0003] However, the above method has the problem of poor flexibility in alarm display. Summary of the invention

[0004] Based on this, it is necessary to provide an alarm display method, device, terminal, medium and program product that can improve alarm flexibility in response to the above technical problems.

[0005] In a first aspect, the present application provides an alarm display method. The alarm display method comprises:

[0006] Displaying a first alarm page, wherein the first alarm page includes a merged alarm area corresponding to at least one alarm type identifier;

[0007] In response to a trigger operation on the merged alarm area, a second alarm page is displayed, the second alarm page including alarm data of a plurality of alarm events, the alarm type corresponding to each of the alarm events being the same as the alarm type represented by the alarm type identifier.

[0008] In one of the embodiments, the alarm type identifier includes at least one of an alarm event identifier, an alarm cause identifier, a device identifier, and an alarm time.

[0009] In one of the embodiments, the merged alarm area includes the alarm type identifier, and the second alarm page includes the alarm type identifier.

[0010] In one of the embodiments, the alarm type identifier includes the alarm event identifier, and the merged alarm area further includes at least one of the following:

[0011] The subject identifier of the subject to which each of the alarm events belongs;

[0012] The alarm time corresponding to each of the alarm events;

[0013] The alarm importance level corresponding to the alarm type represented by the alarm type identifier;

[0014] The device identification abbreviation information corresponding to each of the alarm events.

[0015] In one embodiment, the alarm data of each alarm event includes at least one of the following:

[0016] the subject identification;

[0017] The alarm time;

[0018] The importance of the alarm;

[0019] The device identifier corresponding to each of the alarm events;

[0020] The alarm cause corresponding to each of the alarm events;

[0021] The alarm cause identifier corresponding to each of the alarm events;

[0022] Alarm repair suggestion information corresponding to each of the alarm events.

[0023] In one embodiment, the first alarm page further includes an alarm filter control, and the method further includes:

[0024] Acquire an alarm screening instruction based on the alarm screening control;

[0025] In response to the alarm screening instruction, the merged alarm area corresponding to the alarm screening instruction is displayed in the first alarm page.

[0026] In one embodiment, the method further comprises:

[0027] Receiving alarm reporting data, wherein the alarm reporting data includes a target alarm type identifier of a target alarm event and target alarm data;

[0028] Detecting whether the first alarm page displays a target merged alarm area corresponding to the target alarm type identifier;

[0029] If the first alarm page displays the target merged alarm area and a trigger operation for the target merged alarm area is detected, a second alarm page corresponding to the target merged alarm area is displayed, wherein the second alarm page corresponding to the target merged alarm area includes the target alarm data.

[0030] In one embodiment, the method further comprises:

[0031] If the first alarm page does not display the target merged alarm area, displaying the target merged alarm area in the first alarm page;

[0032] If a trigger operation for the target merged alarm area is detected, a second alarm page corresponding to the target merged alarm area is displayed.

[0033] In one of the embodiments, when recovery alarm data is received from a recovery alarm device, if all alarm events corresponding to the recovery alarm type identifier included in the recovery alarm data are not fully restored, the second alarm page corresponding to the recovery alarm type identifier does not include the alarm data corresponding to the recovery alarm device, and / or the merged alarm area corresponding to the recovery alarm type identifier in the first alarm page does not include the device identifier corresponding to the recovery alarm device.

[0034] In one of the embodiments, if all alarm events corresponding to the recovery alarm type identifier are recovered, the first alarm page does not include a merged alarm area corresponding to the recovery alarm type identifier.

[0035] In one embodiment, the method further comprises:

[0036] The merged alarm area corresponding to the recovery alarm type identifier is added to the historical alarm page, and the second alarm page corresponding to the recovery alarm type identifier is updated according to the recovery alarm data.

[0037] In one embodiment, the first alarm page further includes a historical alarm viewing control, and the method further includes:

[0038] In response to a trigger operation on the historical alarm viewing control, the historical alarm page is displayed.

[0039] In a second aspect, the present application further provides an alarm display device. The alarm display device comprises:

[0040] A first display module, configured to display a first alarm page, wherein the first alarm page includes a merged alarm area corresponding to at least one alarm type identifier;

[0041] The second display module is used to display a second alarm page in response to a trigger operation on the merged alarm area, wherein the second alarm page includes alarm data of multiple alarm events, and the alarm type corresponding to each of the alarm events is the same as the alarm type represented by the alarm type identifier.

[0042] In a third aspect, the present application further provides a terminal, wherein the terminal includes a memory and a processor, wherein the memory stores a computer program, and when the processor executes the computer program, the steps of the method described in the first aspect are implemented.

[0043] In a fourth aspect, the present application further provides a computer-readable storage medium having a computer program stored thereon, and when the computer program is executed by a processor, the steps of the method described in the first aspect are implemented.

[0044] In a fifth aspect, the present application further provides a computer program product. The computer program product includes a computer program, and when the computer program is executed by a processor, the steps of the method described in the first aspect are implemented.

[0045] The above-mentioned alarm display method, device, terminal, medium and program product, by displaying a first alarm page, the first alarm page includes a merged alarm area corresponding to at least one alarm type identifier, and in response to a trigger operation on the merged alarm area, displays a second alarm page, the second alarm page includes alarm data of multiple alarm events, and the alarm type corresponding to each alarm event is the same as the alarm type represented by the alarm type identifier. In this way, each alarm event is classified by the alarm type identifier, and multiple alarm events with the same alarm type represented by an alarm type identifier can be merged in the first alarm page through the same merged alarm area. When the alarm data of the multiple alarm events needs to be displayed (that is, the trigger operation for the merged alarm area is detected), the alarm data of the multiple alarm events are displayed in the second alarm page. Compared with the method of directly displaying all the alarm data of each alarm event in the related art, the embodiment of the present application can improve the situation of disorderly alarm display and redundant alarm information, and improve the flexibility of alarm. BRIEF DESCRIPTION OF THE DRAWINGS

[0046] In order to more clearly illustrate the technical solutions in the embodiments of the present application or related technologies, the drawings required for use in the embodiments of the present application or related technical descriptions will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without paying creative work.

[0047] Figure 1 A diagram of an implementation environment of an alarm display method in an embodiment;

[0048] Figure 2 A flowchart of an alarm display method in one embodiment;

[0049] Figure 3 A schematic diagram of a first warning page in another embodiment;

[0050] Figure 4 A schematic diagram of a first warning page in another embodiment;

[0051] Figure 5A schematic diagram of a first warning page in another embodiment;

[0052] Figure 6 A schematic diagram of a first warning page in another embodiment;

[0053] Figure 7 is a page schematic diagram of a second alarm page in another embodiment;

[0054] Figure 8 is a page schematic diagram of a second alarm page in another embodiment;

[0055] Fig. 9 This is a schematic diagram of a page showing a pop-up window of details in a second alarm page in another embodiment;

[0056] Fig.10 A schematic diagram of a first warning page in another embodiment;

[0057] Fig.11 A schematic diagram of a first warning page in another embodiment;

[0058] Fig.12 It is a schematic diagram of a flow chart of a terminal processing alarm reporting data in another embodiment;

[0059] Fig.13 A schematic diagram of a process of alarm recovery in another embodiment;

[0060] Fig.14 A schematic diagram of a historical alarm page in another embodiment;

[0061] Fig.15 A schematic diagram of a page for restoring a second alarm page corresponding to an alarm type identifier in another embodiment;

[0062] Fig.16 is a structural block diagram of an alarm display device in an embodiment;

[0063] Fig.17 FIG. 4 is a diagram showing the internal structure of a terminal in an embodiment. DETAILED DESCRIPTION

[0064] In order to make the purpose, technical solution and advantages of the present application more clearly understood, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0065] With the continuous development of new energy technology, the proportion of renewable energy power generation is increasing. However, due to the small single-unit power generation capacity and large number of energy equipment in renewable energy power generation, and the fact that renewable energy power generation is greatly affected by weather, environment, and power grid, a large amount of alarm data is easily generated during the renewable energy power generation process. For example, when a batch failure occurs, the energy equipment, as the alarm subject (or alarm device), will transmit a large amount of alarm data to the intelligent management platform.

[0066] Normally, the intelligent management platform will directly visualize each alarm data, which will result in a disorganized alarm display and redundant alarm information. It will fail to highlight useful information, is not conducive to assisting in the rapid and accurate identification of the cause of the alarm, and has a poor visual experience. Therefore, this alarm display method has relatively poor alarm flexibility.

[0067] In view of this, embodiments of the present application provide an alarm display method, device, terminal, medium, and program product, which can improve alarm flexibility.

[0068] Figure 1 A schematic diagram of an implementation environment of the alarm display method provided in an embodiment of the present application.

[0069] The data acquisition device can communicate with the cloud platform through the network, and the cloud platform can communicate with the terminal through the network. The network can be, for example, a wireless network. The data acquisition device can also communicate with various energy devices (such as Figure 1 The energy devices 1-n) shown communicate with each other in a network which may be, for example, a wired network or a wireless network.

[0070] Among them, energy equipment can be photovoltaic equipment, energy storage equipment, charging pile equipment, power equipment, etc. in power stations. Data acquisition equipment can be used to realize data collection and parameter configuration of power converters, such as inverters (or micro-inverters), optimizers, etc. The terminal can be, but is not limited to, various personal computers, laptops, smart phones, tablets, Internet of Things devices and portable wearable devices. Internet of Things devices can be smart speakers, smart TVs, smart air conditioners, smart car-mounted devices, projection devices, etc. Portable wearable devices can be smart watches, smart bracelets, head-mounted devices, etc. Head-mounted devices can be virtual reality (VR) devices, augmented reality (AR) devices, smart glasses, etc. An intelligent management platform software system is installed in the terminal. The intelligent management platform refers to a software system based on the Internet of Things technology that can collect, store, monitor and control various energy devices.

[0071] Optionally, the alarm display method provided in the embodiment of the present application can be applied to Figure 1In the data acquisition device shown; Optionally, the alarm display method provided in the embodiment of the present application can be applied to Figure 1 In the terminal shown; Optionally, the alarm display method provided in the embodiment of the present application is applied to Figure 1 In the case of the terminal shown, the cloud platform can undertake the main computing tasks in the alarm display process during the terminal's alarm display. The task allocation between the terminal and the cloud platform can be set by the terminal during implementation, and there is no restriction here.

[0072] It should be noted that Figure 1 The implementation environment shown does not limit the implementation environment of the alarm display method provided by the present application. In the actual implementation process, the implementation environment applied by the alarm display method provided by the present application may include Figure 1 The implementation environment shown may include more or fewer devices. For example, when the alarm display method provided in the embodiment of the present application is applied to a data acquisition device, the implementation environment may not include a cloud platform and a terminal, etc.

[0073] In an exemplary embodiment, Figure 2 As shown, a warning display method is provided, which is applied to Figure 1 The terminal in is taken as an example to illustrate, including the following steps 201 and 202:

[0074] Step 201: The terminal displays a first alarm page.

[0075] The first alarm page includes a merged alarm area corresponding to at least one alarm type identifier.

[0076] The terminal detects a trigger operation for the first alarm page, and displays the first alarm page. Exemplarily, if the user needs to view the alarm status of a power station or some power stations, the terminal can be triggered to display the first alarm page based on the display screen of the terminal.

[0077] The first alarm page may be an application (Application, APP) page, a computer-side Web (webpage) page, or an embedded visualization terminal page, etc., and no specific limitation is made to the page format of the first alarm page.

[0078] Taking the first alarm page corresponding to a power station as an example, the alarm types of various alarm events that may be generated by all energy equipment in the power station can be classified in advance, and corresponding alarm type identifiers can be defined for different alarm types. In this way, the corresponding alarm type can be represented by the alarm type identifier, such as "grid power failure", "internal equipment abnormality", "upgrade failure", etc.

[0079] When factors such as weather, environment, and power grid change, and energy equipment has equipment abnormalities or communication abnormalities, the energy equipment will generate an alarm event, and the energy equipment will push the alarm data corresponding to the alarm event to the terminal. The alarm data may include, for example, the equipment identification.

[0080] The terminal can classify the alarm types of each alarm event according to the alarm type identifier corresponding to each alarm event, and merge and display (or normalize) the alarm data of multiple alarm events belonging to the same alarm type identifier in the merged alarm area corresponding to the alarm type identifier in the first alarm page.

[0081] Exemplarily, valid alarm data may be displayed in the merged alarm area, and the valid alarm data may be generated by the terminal based on each alarm data (for example, the terminal generates valid alarm data for summarizing each alarm data), and / or the valid alarm data is the same content included in each alarm data.

[0082] In one possible implementation, a mapping relationship between each alarm type identifier and each alarm event can be preset in each energy device. In this way, after an alarm event is generated, when the energy device sends alarm data of the alarm event to the terminal, it can carry the alarm type identifier corresponding to the alarm event, so that the terminal can classify the alarm type of each alarm event according to the alarm type identifier corresponding to each alarm event.

[0083] In another possible implementation, a mapping relationship between each alarm type identifier and each alarm event can be preset in the terminal. After the energy device generates an alarm event, when the energy device sends the alarm data of the alarm event to the terminal, it may not carry the alarm type identifier corresponding to the alarm event. After the terminal receives the alarm data of multiple alarm events, the terminal classifies the alarm type of each alarm event according to the alarm type identifier corresponding to each alarm event based on the above mapping relationship.

[0084] After classifying each alarm event into an alarm type according to any of the above methods, the terminal combines and displays the alarm data of multiple alarm events belonging to the same alarm type identifier in a combined alarm area corresponding to the alarm type identifier in the first alarm page.

[0085] For example, see Figure 3 , Figure 3 The figure is a schematic diagram of an exemplary first alarm page, in which the first alarm page includes a merged alarm area corresponding to an alarm type identifier.

[0086] Of course, in other possible implementations, the first alarm page may also include merged alarm areas corresponding to two or more alarm type identifiers, and the merged alarm areas corresponding to each alarm type identifier are arranged in the first alarm page according to a preset arrangement rule, which may be a linear arrangement, for example. Figure 4 , Figure 4 This is a page diagram of an exemplary first alarm page, which includes four merged alarm areas (merged alarm area 1 to merged alarm area 4) corresponding to the alarm type identifiers, and the four merged alarm areas are arranged linearly in the first alarm page.

[0087] Step 202: The terminal displays a second alarm page in response to a trigger operation on the merged alarm area.

[0088] After the terminal displays the first alarm page, the terminal can detect the trigger operation through each merged alarm area in the first alarm page. If a trigger operation for a merged alarm area is detected, the terminal displays the second alarm page corresponding to the merged alarm area. The second alarm page includes alarm data of multiple alarm events, and the alarm type corresponding to each alarm event is the same as the alarm type represented by the alarm type identifier.

[0089] That is, the terminal merges the alarm data of multiple alarm events of the same alarm type (with the same alarm type identifier) ​​and displays them in the merged alarm area corresponding to the alarm type identifier in the first alarm page. If it is detected that a merged alarm area is triggered, all the alarm data of the multiple alarm events will be displayed.

[0090] In one possible implementation, the terminal may display the alarm data of each alarm event one by one in the second alarm page. For example, the terminal displays each alarm data as a data record in a row in the second alarm page. Of course, the terminal may also display each alarm data one by one in other display methods. There is no restriction on the way in which the terminal displays each alarm data one by one.

[0091] In another possible implementation, the terminal can also merge and display the same content in each alarm data, and display the different content in each alarm data one by one. For example, the alarm data sent by each energy device includes the alarm time and the device identification of the energy device. The alarm times are the same and the device identifications are different. In this way, the terminal can display only one alarm time in the second alarm page, and then display each device identification separately.

[0092] The above-mentioned embodiment classifies each alarm event through the alarm type identifier. Multiple alarm events with the same alarm type represented by an alarm type identifier can be merged into an alarm through the same merged alarm area in the first alarm page. When the alarm data of the multiple alarm events needs to be displayed (that is, a trigger operation for the merged alarm area is detected), the alarm data of the multiple alarm events are displayed in the second alarm page. Compared with the method of directly displaying the alarm data of all alarm events in the related art, the embodiment of the present application can improve the situation of disorganized alarm display and redundant alarm information, and enhance the flexibility of alarm.

[0093] The following is an exemplary introduction to the form of the alarm type identification.

[0094] In an embodiment of the present application, the alarm type identifier can be a field, multiple fields or a string. The field can be a natural language field, for example, a Chinese character field. The field can also be a machine language field. There is no specific restriction on the form of the alarm type identifier.

[0095] As an implementation, the alarm type identifier may include at least one of an alarm event identifier, an alarm cause identifier, a device identifier, and an alarm time.

[0096] The alarm event identifier may be an alarm ID (Identity) or an alarm name pre-set for the alarm event. In the actual implementation process, the alarm type identifier may be defined according to the actual alarm scenario, for example, the alarm type identifier may be defined as an alarm event identifier, for example, the alarm type identifier may be defined as an alarm cause identifier, for example, the alarm type identifier may be defined as an alarm time, for example, the alarm type identifier may be defined as an alarm event identifier + alarm time, and so on.

[0097] In this way, through different alarm type identifiers, each alarm event can be classified into alarm types of different dimensions. For example, the alarm type identifier is defined as the alarm event identifier (the alarm event identifier takes the alarm name as an example), then the alarm name can be used as the alarm type, and each alarm event that may be generated can be classified according to the alarm name; for example, the alarm type identifier is defined as the alarm cause identifier, then the alarm cause identifier can be used as the alarm type, and each alarm event that may be generated can be classified according to the alarm cause, so that the alarm events can be flexibly classified and can be flexibly selected during the implementation process, further improving the alarm flexibility of the embodiments of the present application.

[0098] In the following, based on the content included in the alarm type identifier, the content displayed in the merged alarm area and the second alarm page is exemplarily introduced.

[0099] As an implementation method, the merged alarm area displayed in the first alarm page includes an alarm type identifier, that is, the terminal displays the alarm type identifier in the merged alarm area corresponding to the alarm type identifier. In this way, in the first alarm page, the terminal will not display all the alarm data of each alarm event, but only display each alarm type identifier. The alarm data is normalized and displayed through the alarm type identifier, and as the definition of the alarm type identifier is different, the alarm type identifier displayed in the merged alarm area also changes accordingly, which greatly reduces the interference of invalid alarm information and can display alarms more concisely and effectively, which is conducive to improving operation and maintenance efficiency.

[0100] In an embodiment of the present application, the second alarm page also includes an alarm type identifier. As described above, the second alarm page also displays the alarm data of each alarm event. Displaying the alarm type identifier in the second alarm page is conducive to intuitively associating the alarm type identifier with the alarm data of each alarm event, so as to quickly locate the correspondence between the second alarm page and the alarm type identifier.

[0101] The above embodiment introduces that the alarm type identifier may include at least one of an alarm event identifier, an alarm cause identifier, a device identifier and an alarm time. Below, taking the alarm type identifier including the alarm event identifier as an example, the content in the merged alarm area displayed on the first alarm page and the content displayed on the second alarm page are exemplarily introduced.

[0102] In the case where the alarm type identifier includes the alarm event identifier, the merged alarm area also includes at least one of the following: the subject identifier of the subject to which each alarm event belongs; the alarm time corresponding to each alarm event; the alarm importance corresponding to the alarm type represented by the alarm type identifier; and the device identifier abbreviation information corresponding to each alarm event.

[0103] Among them, the subject to which the alarm event belongs may refer to which organization the alarm event is generated from. For example, taking the first alarm page corresponding to a power station as an example, the subject may refer to the identification of the corresponding power station; the importance of the alarm may be reflected by the alarm importance level. The alarm importance level may include, for example, important, secondary, etc. The granularity of the alarm importance level and the way of dividing the alarm importance level may be set by the user during implementation; the equipment identification abbreviation information corresponding to each alarm event may be obtained by abbreviating the equipment identification of the energy equipment corresponding to each alarm event, that is, the equipment identification abbreviation information is not the complete equipment identification.

[0104] The following is an exemplary description of the subject identification, alarm time, alarm importance, and device identification abbreviated information through diagrams.

[0105] See also Figure 5 , Figure 5is a schematic diagram of an exemplary first alarm page. Figure 5 The first alarm page shown includes a combined alarm area corresponding to an alarm type identifier. The alarm type identifier includes an alarm event identifier (alarm name): power grid power failure; the combined alarm area also includes the subject identifier of the subject (power station) to which each alarm event belongs: power station name ( Figure 5 The combined alarm area also includes the alarm time corresponding to each alarm event: Figure 5 2023-10-17 11:34:52 is shown; the combined alarm area also includes the alarm importance corresponding to the alarm type represented by the alarm type identifier: Figure 5 The "Important" label is shown; the combined alarm area also includes the device identification abbreviation information corresponding to each alarm event: Figure 5 The content selected by the red box.

[0106] In this way, in addition to displaying the alarm event identifier (such as Figure 5 The combined alarm area can be used to display the alarm name shown), and can also display one or more of the subject identification of the subject to which each alarm event belongs, the alarm time corresponding to each alarm event, the alarm importance corresponding to the alarm type represented by the alarm type identification, and the device identification abbreviation information corresponding to each alarm event, thereby improving the display richness of the combined alarm area, facilitating the rapid location of the cause of the fault based on the content displayed in the combined alarm area, and reducing the fault handling time.

[0107] See also Figure 6 , Figure 6 FIG. 1 is another exemplary schematic diagram of a first warning page. Figure 6 The first alarm page shown includes a combined alarm area corresponding to two alarm type identifiers. The alarm type identifier includes the device identifier: device identifier 1 and device identifier 2; the combined alarm area also includes the subject identifier of the subject (power station) to which each alarm event belongs: subject identifier 1 and subject identifier 2, and the subject identifier can be, for example, the power station name, power station ID, etc.; the combined alarm area also includes the alarm time corresponding to each alarm event: Figure 5 As shown, 2024-04-01 11:34:52; the merged alarm area also includes the alarm name abbreviation information corresponding to each alarm event.

[0108] In this way, in addition to displaying the device identification, the merged alarm area can also display one or more of the subject identification of the subject to which each alarm event belongs, the alarm time corresponding to each alarm event, and the alarm name abbreviation information corresponding to each alarm event, thereby improving the display richness of the merged alarm area and facilitating the rapid location of the cause of the fault based on the content displayed in the merged alarm area, thereby reducing the fault handling time.

[0109] In the case where the alarm type identifier includes the alarm event identifier, the alarm data of each alarm event displayed on the second alarm page includes at least one of the following: the subject identifier of the subject to which each alarm event belongs; the alarm time corresponding to each alarm event; the alarm importance corresponding to the alarm type represented by the alarm type identifier; the device identifier corresponding to each alarm event; the alarm cause corresponding to each alarm event; the alarm cause identifier corresponding to each alarm event; and the alarm repair suggestion information corresponding to each alarm event.

[0110] See also Figure 7 , Figure 7 is a schematic diagram of an exemplary second alarm page. Figure 7 The second alarm page shown includes an alarm type identifier, which includes an alarm event identifier (such as Figure 7 In addition to the alarm type identifier, the second alarm page also includes alarm data of each alarm event. The alarm data of each alarm event includes: the subject identifier of the subject to which each alarm event belongs: the power station name ( Figure 7 The alarm data of each alarm event also includes the alarm time corresponding to each alarm event: Figure 7 As shown, 2023-10-17 11:34:52; the alarm data of each alarm event also includes the alarm importance corresponding to the alarm type represented by the alarm type identifier: Figure 7 The “Important” label is shown; the alarm data of each alarm event also includes the equipment identification of the energy equipment corresponding to each alarm event: Figure 7 The device SN (Serial Number) shown in the figure includes Figure 7 The combiner box identification 1, energy storage device identification 1, charging pile identification 1, inverter identification 1, inverter identification 2, inverter identification 3, and inverter identification 4 shown in the second alarm page should be noted that the device SN displayed on the second alarm page is the complete device identification information corresponding to the device identification abbreviation information in the combined alarm area on the first alarm page; the alarm data of each alarm event also includes the alarm cause corresponding to each alarm event: Figure 7 The alarm data of each alarm event also includes an alarm cause identifier corresponding to each alarm event, and the alarm cause identifier corresponds to the alarm cause one by one. For example, the alarm cause identifier corresponding to the alarm cause "power outage" is "1"; the alarm data of each alarm event also includes alarm repair suggestion information corresponding to each alarm event: Figure 7 The repair suggestions section shown shows what is being done.

[0111] When the alarm type identifier includes the device identifier, the alarm data of each alarm event displayed on the second alarm page includes at least one of the following: the subject identifier of the subject to which each alarm event belongs; an alarm list; wherein the alarm list includes the alarm name and alarm time of each alarm event.

[0112] See also Figure 8 , Figure 8 is a schematic diagram of an exemplary second alarm page. Figure 8 The second alarm page shown includes an alarm type identifier, which includes a device identifier. In addition to the alarm type identifier, the second alarm page also includes alarm data of each alarm event. The alarm data of each alarm event includes: the subject identifier of the subject to which each alarm event belongs: the power station name ( Figure 8 The alarm data of each alarm event also includes an alarm list, which includes the alarm name and alarm time of each alarm event: the alarm name "offline" corresponds to the alarm time 2023-10-17 13:34:52, the alarm name "grid power failure" corresponds to the alarm time 2023-10-17 12:34:09, the alarm name "grid undervoltage" corresponds to the alarm time 2023-10-17 12:34:00, and the alarm name "internal fault" corresponds to the alarm time 2023-10-17 10:34:00.

[0113] Optionally, when the alarm type identifier includes a device identifier, in the second alarm page, if a trigger operation for a certain alarm name is detected, a detail pop-up window corresponding to the alarm name can also be displayed in the second alarm page, and the detail pop-up window includes at least one of the following contents: the alarm name, the alarm time corresponding to the alarm event corresponding to the alarm name, the alarm identifier corresponding to the alarm event, the alarm reason identifier corresponding to the alarm event, the alarm cause corresponding to the alarm event, and the alarm repair suggestion information corresponding to the alarm event.

[0114] See also Fig. 9 , Fig. 9 For Figure 8 After the alarm name "offline" is triggered on the second alarm page shown in the figure, the page diagram of the details pop-up window corresponding to the alarm name "offline" is shown in the figure. Fig. 9 The details pop-up window shown includes the alarm name ( Fig. 9 The alarm event corresponding to the alarm name shall include the alarm time 2023-10-17 11:34:52, the alarm ID corresponding to the alarm event, the alarm reason ID corresponding to the alarm event, the alarm reason corresponding to the alarm event, and the alarm repair suggestion information corresponding to the alarm event.

[0115] In this way, alarms are merged on the first alarm page by merging alarm areas to solve the problem of redundant alarm data display, and alarm data generated by the same type of equipment, different types of equipment, and the same equipment are displayed as one alarm record (i.e., merged alarm area) on the first alarm page, thereby achieving the purpose of reducing the presentation of alarm data, which is conducive to quickly and accurately locating the cause of the fault and improving the efficiency of solving on-site problems. Afterwards, when it is necessary to fully display the alarm data (such as detecting a trigger operation for the merged alarm area), the second alarm page will supplement the display of the complete alarm data, so that the alarm data can be fully displayed on the second alarm page, which is conducive to assisting in locating the cause of the fault and improving the accuracy of locating the cause of the fault.

[0116] The above embodiment only provides an exemplary introduction to the contents included in the first warning page and the second warning page. In other possible implementations, the first warning page and the second warning page may also include more or less content than that mentioned in the above embodiment. The above embodiment provides an exemplary introduction to the contents included in the first warning page and the second warning page and does not constitute a limitation on the contents included in the first warning page and the second warning page of the embodiment of the present application.

[0117] For example, the second alarm page may also include an "alarm details" field. For example, the first alarm page also includes an alarm filtering control. The terminal may obtain an alarm filtering instruction based on the alarm filtering control, and then the terminal responds to the alarm filtering instruction and displays the merged alarm area corresponding to the alarm filtering instruction in the first alarm page.

[0118] For example, Fig.10 As shown, in addition to multiple merged alarm areas, the first alarm page also includes an alarm filter control, which is used for the user to select a merged alarm area corresponding to a certain alarm type identifier. Exemplarily, the user can input an alarm filter instruction based on the alarm filter control, and the alarm filter instruction includes an alarm type identifier (such as an alarm name, or it can be an alarm identifier). The terminal displays the merged alarm area corresponding to the alarm type identifier in the first alarm page according to the alarm type identifier indicated by the alarm filter instruction.

[0119] For example, Fig.11 As shown, Fig.11 The first alarm page shown includes four merged alarm areas and an alarm filter control. The terminal can obtain an alarm filter instruction based on the alarm filter control, and then the terminal displays the merged alarm area corresponding to the alarm type identifier included in the alarm filter instruction in the first alarm page.

[0120] In this way, the merged alarm area that needs to be displayed can be easily filtered through the alarm filtering control, and the interface interaction method is simple and easy to implement.

[0121] The above embodiment exemplarily introduces the contents displayed on the first alarm page and the second alarm page. The following exemplarily describes the processing method after the terminal receives the alarm report data and the related process of alarm recovery.

[0122] See also Fig.12 In this embodiment, the alarm display method also includes Fig.12 Steps 1201 to 1204 are shown as follows:

[0123] Step 1201: The terminal receives alarm reporting data.

[0124] The alarm reporting data includes the target alarm type identifier of the target alarm event and the target alarm data.

[0125] Exemplarily, as described above, the mapping relationship between each alarm type identifier and each alarm event can be preset in each energy device. In this way, after the energy device generates an alarm event (referred to here as a target alarm event for distinction), when the energy device sends the target alarm data of the target alarm event to the terminal, it can carry the target alarm type identifier corresponding to the target alarm event.

[0126] Step 1202: The terminal detects whether the first alarm page displays a target merged alarm area corresponding to the target alarm type identifier.

[0127] In an embodiment of the present application, since the terminal merges and displays the alarm data of multiple alarm events belonging to the same alarm type identifier in the first alarm page, after the terminal receives the target alarm type identifier and the target alarm data, it can first detect whether the first alarm page displays the target merged alarm area corresponding to the target alarm type identifier.

[0128] Step 1203: If the first alarm page displays a target merged alarm area, the terminal adds the target alarm data to the second alarm page corresponding to the target merged alarm area.

[0129] If the first alarm page already displays the target merged alarm area, that is, the target alarm type identifier has been merged and displayed before the alarm reporting data is received, then the terminal does not need to add a new target merged alarm area to the first alarm page, but directly adds the target alarm data to the second alarm page corresponding to the target merged alarm area.

[0130] After the terminal adds the target alarm data to the second alarm page corresponding to the target merged alarm area, if the terminal detects a trigger operation for the target merged alarm area, the second alarm page corresponding to the target merged alarm area is displayed. It can be understood that the second alarm page corresponding to the target merged alarm area includes the above-mentioned target alarm data.

[0131] In this way, when the target merged alarm area is already displayed on the first alarm page, the target alarm data can be directly added to the second alarm page corresponding to the target merged alarm area, and the new alarm data (target alarm data) corresponding to the same alarm type identifier can be merged and displayed with the existing alarm data, thereby achieving good compatibility with new alarm events.

[0132] The above embodiment is introduced by taking the example that the terminal adds the target alarm data to the second alarm page corresponding to the target merged alarm area. Optionally, when the first alarm page displays the target merged alarm area, the cloud platform can also add the target alarm data to the second alarm page corresponding to the target merged alarm area. In this way, if the terminal detects a trigger operation for the target merged alarm area, the second alarm page corresponding to the target merged alarm area is directly pulled from the cloud platform and displayed, and the second alarm page corresponding to the target merged alarm area includes the target alarm data. By directly adding the target alarm data to the second alarm page corresponding to the target merged alarm area, the newly added alarm data (target alarm data) corresponding to the same alarm type identifier and the existing alarm data are combined and displayed, and good compatibility is achieved for the newly added alarm events, and the terminal can directly pull the second alarm page corresponding to the target merged alarm area from the cloud platform and display it, which can improve the efficiency of the terminal displaying the second alarm page corresponding to the target merged alarm area and save the computing resources of the terminal.

[0133] Step 1204: If the first alarm page does not display the target merged alarm area, the terminal displays the target merged alarm area in the first alarm page, and generates a second alarm page corresponding to the target merged alarm area according to the target alarm data.

[0134] If the target merged alarm area is not displayed on the first alarm page, it means that the target alarm type identifier has not been merged and displayed before the alarm reporting data is received. Then, the terminal needs to display the target merged alarm area in the first alarm page and add the target alarm data to the second alarm page corresponding to the target merged alarm area. In this way, if a trigger operation for the target merged alarm area is detected in the first alarm page, the terminal can display the second alarm page corresponding to the target merged alarm area.

[0135] In this way, in actual application scenarios, alarm events may occur one after another. In an embodiment of the present application, when the first alarm page does not display the target merged alarm area, after the terminal receives the target alarm type identifier and target alarm data of the target alarm event, it can add a new alarm to the first alarm page: target merged alarm area, and then generate a second alarm page corresponding to the target merged alarm area based on the target alarm data, thereby achieving reliable compatibility with new alarm events, being closer to actual alarm scenarios, and being conducive to the implementation and promotion of the embodiments of the present application.

[0136] The above embodiment is introduced by taking the example that the terminal adds the target alarm data to the second alarm page corresponding to the target merged alarm area. Optionally, the cloud platform can also add the target alarm data to the second alarm page corresponding to the target merged alarm area. In this way, after the terminal displays the target merged alarm area in the first alarm page, if a trigger operation for the target merged alarm area is detected, the second alarm page corresponding to the target merged alarm area can be directly pulled from the cloud platform and displayed. This embodiment can achieve reliable compatibility with new alarm events, is closer to the actual alarm scenario, is conducive to the implementation and promotion of the embodiment of the present application, and the terminal can directly pull the second alarm page corresponding to the target merged alarm area from the cloud platform and display it, which can improve the efficiency of the terminal displaying the second alarm page corresponding to the target merged alarm area and save the computing resources of the terminal.

[0137] See also Fig.13 In this embodiment, the alarm display method also includes Fig.13 Steps 1301 to 1304 are shown as follows:

[0138] Step 1301: The terminal receives recovery alarm data sent by the recovery alarm device.

[0139] If an alarm event is restored, the energy device (referred to here as the recovery alarm device for distinction) reports the recovery alarm data to the terminal. The recovery alarm data includes the recovery alarm type identifier of the recovery alarm event (i.e. the alarm event that has been restored). The recovery alarm type identifier refers to the alarm type identifier of the alarm event whose fault has been restored. Its content is consistent with the content included in the alarm type identifier of the above embodiment, and will not be repeated here.

[0140] Step 1302: The terminal detects whether all alarm events corresponding to the recovery alarm type identifiers are recovered.

[0141] It can be understood that before receiving the recovery alarm data, the terminal has displayed the merged alarm area corresponding to the recovery alarm type identifier in the first alarm page using the alarm display method of the embodiment of the present application, and the merged alarm area corresponding to the recovery alarm type identifier corresponds to a second alarm page, and the second alarm page is used to display the alarm data of each alarm event corresponding to the recovery alarm type identifier.

[0142] After receiving the recovery alarm data, the terminal can first detect whether all alarm events corresponding to the recovery alarm type identifier are restored. For example, for an alarm event, if the terminal receives the recovery alarm data sent by the alarm device corresponding to the alarm event, it is determined that the alarm event is restored.

[0143] Step 1303, if all alarm events corresponding to the recovery alarm type identifier are not fully recovered, the terminal deletes the alarm data corresponding to the recovery alarm device in the second alarm page corresponding to the recovery alarm type identifier, and / or the terminal deletes the device identifier corresponding to the recovery alarm device in the merged alarm area corresponding to the recovery alarm type identifier in the first alarm page.

[0144] If all alarm events corresponding to the recovery alarm type identifier are not fully recovered, optionally, the terminal may delete the alarm data corresponding to the recovery alarm device in the second alarm page corresponding to the recovery alarm type identifier. Optionally, as described above, the merged alarm area corresponding to the recovery alarm type identifier in the first alarm page may include device identifier abbreviation information corresponding to each alarm event. Then, the terminal may also delete the device identifier corresponding to the recovery alarm device in the merged alarm area corresponding to the recovery alarm type identifier in the first alarm page, thereby updating the first alarm page and / or the second alarm page.

[0145] In this way, when all alarm events corresponding to the restored alarm type identifiers are not fully restored, the first alarm page and / or the second alarm page are updated to ensure the accuracy of the merged alarm area in the first alarm page and the accuracy of the alarm data in the second alarm page.

[0146] In the above embodiment, when all the alarm events corresponding to the recovery alarm type identifier are not fully recovered, the terminal updates the first alarm page and / or the second alarm page. Optionally, the cloud platform may also update the first alarm page and / or the second alarm page, so that when the recovery alarm data sent by the recovery alarm device is received, if all the alarm events corresponding to the recovery alarm type identifier included in the recovery alarm data are not fully recovered, the second alarm page corresponding to the recovery alarm type identifier does not include the alarm data corresponding to the recovery alarm device, and / or the merged alarm area corresponding to the recovery alarm type identifier in the first alarm page does not include the device identifier corresponding to the recovery alarm device, that is, the cloud platform deletes the alarm data corresponding to the recovery alarm device in the second alarm page corresponding to the recovery alarm type identifier, and / or the cloud platform deletes the device identifier corresponding to the recovery alarm device in the merged alarm area corresponding to the recovery alarm type identifier in the first alarm page, so that the accuracy of the merged alarm area in the first alarm page and the accuracy of the alarm data in the second alarm page can be guaranteed, and the entire update process is implemented by the cloud platform, which can save the computing resources of the terminal.

[0147] Step 1304: If all alarm events corresponding to the recovery alarm type identifier are recovered, the terminal deletes the merged alarm area corresponding to the recovery alarm type identifier in the first alarm page.

[0148] If all the alarm events corresponding to the recovery alarm type identifier are recovered, the terminal may delete the merged alarm area corresponding to the recovery alarm type identifier in the first alarm page.

[0149] Optionally, when all alarm events corresponding to the recovery alarm type identifier are restored, the cloud platform may also delete the merged alarm area corresponding to the recovery alarm type identifier in the first alarm page. This embodiment does not restrict the executing entity for deleting the merged alarm area corresponding to the recovery alarm type identifier in the first alarm page.

[0150] In this way, in actual application scenarios, alarm events will not only occur one after another, but will also usually be restored one after another. Through the above implementation process, the embodiment of the present application can achieve good compatibility with the restored alarm events, which is closer to the actual alarm scenario and is conducive to the implementation and promotion of the embodiment of the present application.

[0151] In one embodiment, Fig.13 On the basis of the embodiment shown, if all alarm events corresponding to the recovery alarm type identifier are recovered, the terminal can also add the merged alarm area corresponding to the recovery alarm type identifier to the historical alarm page. For example, see Fig.14 , Fig.14This is a page diagram of a historical alarm page. The terminal still displays the historical alarm data in a merged alarm area on the historical alarm page. Compared with the traditional technology of not displaying historical alarm data or displaying historical alarm data one by one, the embodiment of the present application can reduce the problem of redundant display of historical alarm data, which is conducive to quickly finding historical alarm data and realizing rapid backtracking of historical alarms.

[0152] Optionally, similar to the first alarm page, the historical alarm page may also include a historical alarm filter control, and the historical alarm filter control is used to select a merged alarm area corresponding to a certain recovery alarm type identifier in the historical alarm page.

[0153] In an embodiment of the present application, the terminal can also update the second alarm page corresponding to the recovery alarm type identifier based on the recovery alarm data. For example, the recovery alarm data includes the alarm recovery time. The terminal can record the alarm recovery time in the second alarm page. The alarm recovery time can be the alarm recovery time corresponding to the last recovery alarm device corresponding to the recovery alarm type identifier.

[0154] For example, see Fig.15 , Fig.15 This is a page schematic diagram of restoring a second alarm page corresponding to an alarm type identifier. The terminal can record the alarm restoration time in the second alarm page corresponding to the alarm type identifier.

[0155] This embodiment can perform intelligent management of the restored alarm data by updating the historical alarm page and restoring the second alarm page corresponding to the alarm type identifier, thereby facilitating effective backtracking of historical alarms.

[0156] In one embodiment, the first alarm page also includes a historical alarm viewing control. Exemplarily, the historical alarm viewing control may be, for example, Fig.11 The bell icon shown in the upper right corner of the .

[0157] The terminal can display the historical alarm page in response to the trigger operation of the historical alarm viewing control. In this way, the historical alarm page can be quickly triggered and displayed in the first alarm page, so that the current alarm information (i.e., the first alarm page) and the historical alarm information (i.e., the historical alarm page) can be quickly switched, thereby realizing a more intelligent alarm display.

[0158] In general, the embodiment of the present application classifies the alarm types of various alarm events that may be generated by all energy equipment in the power station in advance, and defines corresponding alarm type identifiers for different alarm types. The energy equipment can carry the alarm type identifier when reporting the alarm data of the alarm event. In this way, the terminal can merge and display the alarm data of multiple alarm events belonging to the same alarm type identifier, which greatly reduces the interference of invalid alarm information and can display alarms more concisely and effectively, which is beneficial to improving operation and maintenance efficiency, and further beneficial to improving the operating reliability and power generation of the power station.

[0159] It should be understood that, although the various steps in the flowcharts involved in the above-mentioned embodiments are displayed in sequence according to the indication of the arrows, these steps are not necessarily executed in sequence according to the order indicated by the arrows. Unless there is a clear explanation in this article, the execution of these steps does not have a strict order restriction, and these steps can be executed in other orders. Moreover, at least a part of the steps in the flowcharts involved in the above-mentioned embodiments can include multiple steps or multiple stages, and these steps or stages are not necessarily executed at the same time, but can be executed at different times, and the execution order of these steps or stages is not necessarily to be carried out in sequence, but can be executed in turn or alternately with other steps or at least a part of the steps or stages in other steps.

[0160] Based on the same inventive concept, the embodiment of the present application also provides an alarm display device for implementing the alarm display method involved above. The implementation scheme for solving the problem provided by the device is similar to the implementation scheme recorded in the above method, so the specific limitations in one or more alarm display device embodiments provided below can refer to the limitations on the alarm display method above, and will not be repeated here.

[0161] In an exemplary embodiment, Fig.16 As shown, a warning display device is provided, comprising:

[0162] A first display module 1601 is used to display a first alarm page, where the first alarm page includes a merged alarm area corresponding to at least one alarm type identifier;

[0163] The second display module 1602 is used to display a second alarm page in response to a trigger operation on the merged alarm area, wherein the second alarm page includes alarm data of multiple alarm events, and the alarm type corresponding to each of the alarm events is the same as the alarm type represented by the alarm type identifier.

[0164] In one of the embodiments, the alarm type identifier includes at least one of an alarm event identifier, an alarm cause identifier, a device identifier, and an alarm time.

[0165] In one of the embodiments, the merged alarm area includes the alarm type identifier, and the second alarm page includes the alarm type identifier.

[0166] In one of the embodiments, the alarm type identifier includes the alarm event identifier, and the merged alarm area further includes at least one of the following:

[0167] The subject identifier of the subject to which each of the alarm events belongs;

[0168] The alarm time corresponding to each of the alarm events;

[0169] The alarm importance level corresponding to the alarm type represented by the alarm type identifier;

[0170] The device identification abbreviation information corresponding to each of the alarm events.

[0171] In one embodiment, the alarm data of each alarm event includes at least one of the following:

[0172] the subject identification;

[0173] The alarm time;

[0174] The importance of the alarm;

[0175] The device identifier corresponding to each of the alarm events;

[0176] The alarm cause corresponding to each of the alarm events;

[0177] The alarm cause identifier corresponding to each of the alarm events;

[0178] Alarm repair suggestion information corresponding to each of the alarm events.

[0179] In one of the embodiments, the first alarm page also includes an alarm filtering control, and the first display module 1601 is further used to obtain an alarm filtering instruction based on the alarm filtering control; in response to the alarm filtering instruction, the merged alarm area corresponding to the alarm filtering instruction is displayed in the first alarm page.

[0180] In one embodiment, the device further comprises:

[0181] A receiving module, used to receive alarm reporting data, wherein the alarm reporting data includes a target alarm type identifier of a target alarm event and target alarm data;

[0182] A detection module, used to detect whether the first alarm page displays a target merged alarm area corresponding to the target alarm type identifier;

[0183] The third display module is used to display a second alarm page corresponding to the target merged alarm area if the first alarm page displays the target merged alarm area and a trigger operation for the target merged alarm area is detected, wherein the second alarm page corresponding to the target merged alarm area includes the target alarm data.

[0184] In one of the embodiments, the third display module is also used to display the target merged alarm area in the first alarm page if the first alarm page does not display the target merged alarm area; if a trigger operation for the target merged alarm area is detected, a second alarm page corresponding to the target merged alarm area is displayed.

[0185] In one of the embodiments, when recovery alarm data is received from a recovery alarm device, if all alarm events corresponding to the recovery alarm type identifier included in the recovery alarm data are not fully restored, the second alarm page corresponding to the recovery alarm type identifier does not include the alarm data corresponding to the recovery alarm device, and / or the merged alarm area corresponding to the recovery alarm type identifier in the first alarm page does not include the device identifier corresponding to the recovery alarm device.

[0186] In one embodiment, if all alarm events corresponding to the recovery alarm type identifier are recovered, the first alarm page does not include the merged alarm area corresponding to the recovery alarm type identifier.

[0187] In one embodiment, the device further comprises:

[0188] The first adding module is used to add the merged alarm area corresponding to the recovery alarm type identifier to the historical alarm page, and update the second alarm page corresponding to the recovery alarm type identifier according to the recovery alarm data.

[0189] In one of the embodiments, the first alarm page further includes a historical alarm viewing control, and the device further includes:

[0190] The fourth display module is used to display the historical alarm page in response to a trigger operation on the historical alarm viewing control.

[0191] Each module in the above-mentioned alarm display device can be implemented in whole or in part by software, hardware and a combination thereof. Each module can be embedded in or independent of a processor in a computer device in the form of hardware, or can be stored in a memory in a computer device in the form of software, so that the processor can call and execute the operations corresponding to each module above.

[0192] In an exemplary embodiment, a terminal is provided, and its internal structure diagram can be as follows: Fig.17 As shown. The terminal includes a processor, a memory, an input / output interface, a communication interface, a display unit and an input device. Among them, the processor, the memory and the input / output interface are connected through a system bus, and the communication interface, the display unit and the input device are connected to the system bus through the input / output interface. Among them, the processor of the terminal is used to provide computing and control capabilities. The memory of the terminal includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The input / output interface of the terminal is used to exchange information between the processor and an external device. The communication interface of the terminal is used to communicate with an external terminal in a wired or wireless manner, and the wireless manner can be implemented through WIFI, a mobile cellular network, near field communication (Near Field Communication, NFC) or other technologies. When the computer program is executed by the processor, an alarm display method is implemented. The display unit of the terminal is used to form a visually visible picture, which can be a display screen, a projection device or a virtual reality imaging device. The display screen can be a liquid crystal display screen or an electronic ink display screen, and the input device of the terminal can be a touch layer covering the display screen, or a key, trackball or touchpad provided on the terminal housing, or an external keyboard, touchpad or mouse.

[0193] Those skilled in the art will understand that Fig.17 The structure shown in the figure is only a block diagram of a partial structure related to the scheme of the present application, and does not constitute a limitation on the terminal to which the scheme of the present application is applied. The specific terminal may include more or fewer components than shown in the figure, or combine certain components, or have a different arrangement of components.

[0194] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the steps in the above-mentioned embodiments of the alarm display method are implemented.

[0195] In one embodiment, a computer program product is provided, including a computer program, which implements the steps in the above-mentioned embodiments of the alarm display method when executed by a processor.

[0196] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with relevant regulations.

[0197] Those of ordinary skill in the art can understand that all or part of the processes in the above-mentioned embodiment methods can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to the memory, database or other medium used in the embodiments provided in the present application can include at least one of non-volatile memory and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. As an illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM). The database involved in each embodiment provided in this application may include at least one of a relational database and a non-relational database. Non-relational databases may include distributed databases based on blockchains, etc., but are not limited to this. The processor involved in each embodiment provided in this application may be a general-purpose processor, a central processing unit, a graphics processor, a digital signal processor, a programmable logic device, a data processing logic device based on quantum computing, an artificial intelligence (AI) processor, etc., but are not limited to this.

[0198] The technical features of the above embodiments may be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this application.

[0199] The above-described embodiments only express several implementation methods of the present application, and the descriptions thereof are relatively specific and detailed, but they cannot be understood as limiting the scope of the present application. It should be pointed out that, for a person of ordinary skill in the art, several variations and improvements can be made without departing from the concept of the present application, and these all belong to the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the attached claims.

Claims

1. A warning display method, characterized in that: The method comprises: Displaying a first alarm page, wherein the first alarm page includes a merged alarm area corresponding to at least one alarm type identifier; In response to a trigger operation on the merged alarm area, a second alarm page is displayed, the second alarm page including alarm data of a plurality of alarm events, the alarm type corresponding to each of the alarm events being the same as the alarm type represented by the alarm type identifier.

2. The method according to claim 1, characterized in that: The alarm type identifier includes at least one of an alarm event identifier, an alarm cause identifier, a device identifier, and an alarm time.

3. The method according to claim 2, characterized in that The combined alarm area includes the alarm type identifier, and the second alarm page includes the alarm type identifier.

4. The method according to claim 3, characterized in that: The alarm type identifier includes the alarm event identifier, and the merged alarm area further includes at least one of the following: The subject identifier of the subject to which each of the alarm events belongs; The alarm time corresponding to each of the alarm events; The alarm importance level corresponding to the alarm type represented by the alarm type identifier; The device identification abbreviation information corresponding to each of the alarm events.

5. The method according to claim 4, characterized in that The alarm data of each of the alarm events includes at least one of the following: the subject identification; The alarm time; The importance of the alarm; The device identifier corresponding to each of the alarm events; The alarm cause corresponding to each of the alarm events; The alarm cause identifier corresponding to each of the alarm events; Alarm repair suggestion information corresponding to each of the alarm events.

6. The method according to any one of claims 1 to 5, characterized in that: The first alarm page further includes an alarm filter control, and the method further includes: Acquire an alarm screening instruction based on the alarm screening control; In response to the alarm screening instruction, the merged alarm area corresponding to the alarm screening instruction is displayed in the first alarm page.

7. The method according to any one of claims 1 to 5, characterized in that: The method further comprises: Receiving alarm reporting data, wherein the alarm reporting data includes a target alarm type identifier of a target alarm event and target alarm data; Detecting whether the first alarm page displays a target merged alarm area corresponding to the target alarm type identifier; If the first alarm page displays the target merged alarm area and a trigger operation for the target merged alarm area is detected, a second alarm page corresponding to the target merged alarm area is displayed, wherein the second alarm page corresponding to the target merged alarm area includes the target alarm data.

8. The method according to claim 7, characterized in that The method further comprises: If the first alarm page does not display the target merged alarm area, displaying the target merged alarm area in the first alarm page; If a trigger operation for the target merged alarm area is detected, a second alarm page corresponding to the target merged alarm area is displayed.

9. The method according to claim 1, characterized in that: When receiving recovery alarm data sent by a recovery alarm device, if all alarm events corresponding to the recovery alarm type identifier included in the recovery alarm data have not been fully restored, the second alarm page corresponding to the recovery alarm type identifier does not include the alarm data corresponding to the recovery alarm device, and / or the merged alarm area corresponding to the recovery alarm type identifier in the first alarm page does not include the device identifier corresponding to the recovery alarm device.

10. The method according to claim 9, characterized in that If all the alarm events corresponding to the restoration alarm type identifier are restored, the first alarm page does not include the merged alarm area corresponding to the restoration alarm type identifier.

11. The method according to claim 10, characterized in that The method further comprises: The merged alarm area corresponding to the recovery alarm type identifier is added to the historical alarm page, and the second alarm page corresponding to the recovery alarm type identifier is updated according to the recovery alarm data.

12. The method according to claim 11, characterized in that The first alarm page also includes a historical alarm viewing control, and the method further includes: In response to a trigger operation on the historical alarm viewing control, the historical alarm page is displayed.

13. An alarm display device, characterized in that: The device comprises: A first display module, configured to display a first alarm page, wherein the first alarm page includes a merged alarm area corresponding to at least one alarm type identifier; The second display module is used to display a second alarm page in response to a trigger operation on the merged alarm area, wherein the second alarm page includes alarm data of multiple alarm events, and the alarm type corresponding to each of the alarm events is the same as the alarm type represented by the alarm type identifier.

14. A terminal comprising a memory and a processor, wherein the memory stores a computer program, characterized in that: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 12 are implemented.

15. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 12 are implemented.

16. A computer program product comprising a computer program, characterized in that When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 12 are implemented.

Images