Event card management method, device, equipment and computing program product
The event card management method addresses inefficiencies in emergency event handling by real-time detection, generation, and continuous updating of event cards, improving notification efficiency and reducing delays.
Patent Information
- Application Number
- CN202410908090.8
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-07-08
- Publication Date
- 2024-12-06
AI Technical Summary
Existing systems face inefficiencies in recording, updating, and sharing event information during emergencies, leading to delayed handling and escalation due to manual processes and lack of immediate notification to relevant personnel.
An event card management method that includes polling alarm platforms for information, generating event cards based on this data, and continuously updating and pushing them through a card editing platform until the event is completed, ensuring real-time detection and notification to relevant groups.
Enhances the efficiency of event management by ensuring timely recording, updating, and sharing of event information, reducing delays in handling and escalation processes.
Smart Images

Figure CN119090412A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of computer technology, and in particular to an event card management method, device, equipment and computer program product. Background Art
[0002] When an emergency occurs in the banking system, the on-duty personnel notify the person in charge of the alarm system through the internal office communication system or by phone. The above method can avoid data loss and damage to a certain extent.
[0003] However, the person who is responsible for the root cause of the fault or needs to assist in the emergency may not be the one responsible for the alarm system. The event fault information is not quickly notified to all potential related personnel, which results in a lot of time spent in the search / handling process, ultimately affecting the duration of emergency handling.
[0004] In addition, the on-duty personnel cannot immediately know the importance level of the emergency and the corresponding process of notifying superiors (leaders) for this level. Therefore, the on-duty personnel can only pay attention to the time of notifying superiors based on the time of the incident and manually query their superiors based on the information of the person in charge of the alarm system, which may eventually lead to delays in event escalation.
[0005] Moreover, after the emergency is recovered, it is impossible to quickly know the initial classification of the emergency, and manual review of the classification rules is required, which also leads to a loss of manpower.
[0006] The above contents are only used to assist in understanding the technical solution of the present application and do not constitute an admission that the above contents are prior art. Summary of the invention
[0007] The main purpose of this application is to provide an event card management method, device, equipment and computer program product, aiming to solve the technical problem that when an accident occurs in the system, the accident cannot be recorded and updated, and the accident information cannot be shared, resulting in low accident handling efficiency.
[0008] To achieve the above objectives, the present application proposes an event card management method, which includes:
[0009] Poll the alarm platform through the card sharing platform to obtain alarm information;
[0010] Generate an event card based on the alarm information, and push the event card through a card editing platform;
[0011] The event card is polled and updated through the card editing platform to obtain a final event card, and the final event card is pushed.
[0012] In one embodiment, before the step of polling the alarm platform through the card sharing platform to obtain the alarm information, the method further includes:
[0013] Receive the user's login request;
[0014] Authenticating the login request through the authentication platform, obtaining a first authentication result, and sending it to the user;
[0015] receiving a second authentication request initiated by the user based on the first authentication result, parsing the second authentication request to obtain a second authentication result, where the second authentication result includes user information of the user;
[0016] Provide event management authority corresponding to the user based on the user information.
[0017] In one embodiment, the step of generating an event card based on the alarm information includes:
[0018] Parsing the alarm information to obtain the system number, system name, service unit number and alarm indicator;
[0019] Generate an event name according to the system number, system name, service unit number and alarm indicator;
[0020] Input the system number into the business continuity platform to obtain the system level corresponding to the system number, and input the system name and service unit number into the centralized configuration management platform to obtain the subsystem level and service unit level;
[0021] generating event categories according to the system level, subsystem level, and service unit level;
[0022] Output an event card based on the event name and event category.
[0023] In one embodiment, the step of pushing the event card through the card editing platform includes:
[0024] Writing the field values of the event card into the event card database;
[0025] Based on the event card database, the office communication system interface is called through the card editing platform to send the event card to a preset event emergency group;
[0026] The event card is pushed to the event emergency group through the push platform of the office communication system.
[0027] In one embodiment, the step of polling and updating the event card through the card editing platform to obtain a final event card and pushing the final event card includes:
[0028] Performing polling detection on the card database through the card editing platform;
[0029] When the end notification of the event card is detected, the event recovery status of the event card is obtained;
[0030] The event card is updated based on the event recovery status to obtain a final event card;
[0031] The final event card is pushed to the event emergency group through the push platform of the office communication system.
[0032] In one embodiment, after the step of polling the card database through the card editing platform, the method further includes:
[0033] When it is detected that the event card has event upgrade information, the event upgrade information is collected through the event upgrade reminder platform;
[0034] Based on the event escalation information, a corresponding reminder time is obtained through the event escalation reminder platform;
[0035] Based on the event upgrade information, the event card is updated through the card editing platform to obtain an updated event card;
[0036] Based on the reminder event, the updated event card is pushed to the corresponding event handler via the push platform of the office communication system.
[0037] In one embodiment, after the step of polling and updating the event card through the card editing platform to obtain a final event card and pushing the final event card, the method further includes:
[0038] Parsing the final event card to obtain the service type, system level, availability loss ratio and fault duration corresponding to the final event card;
[0039] Based on the service type, system level, availability loss ratio and fault duration, event rating is performed through a preset event rating management table to obtain a rating result of the final event card.
[0040] In addition, to achieve the above purpose, the present application also proposes an event card management device, the event card management device comprising:
[0041] The detection module is used to poll the alarm platform through the card sharing platform to obtain alarm information;
[0042] A generation module, used to generate an event card based on the alarm information, and push the event card through a card editing platform;
[0043] The updating module is used to poll and update the event card through the card editing platform to obtain the final event card and push the final event card.
[0044] In addition, to achieve the above-mentioned purpose, the present application also proposes an event card management device, which includes: a memory, a processor, and a computer program stored in the memory and executable on the processor, and the computer program is configured to implement the steps of the event card management method described above.
[0045] In addition, to achieve the above-mentioned purpose, the present application also provides a computer program product, which includes a computer program, and when the computer program is executed by a processor, the steps of the event card management method described above are implemented.
[0046] One or more technical solutions proposed in this application have at least the following technical effects:
[0047] The embodiment of the present application proposes an event card management method, device, equipment and computer program product, which polls and detects the alarm platform through a card sharing platform to obtain alarm information; generates an event card based on the alarm information, and pushes the event card through a card editing platform; polls and updates the event card through the card editing platform to obtain a final event card, and pushes the final event card. Thus, the alarm platform is detected in real time through the card sharing platform to see whether there is alarm information. If there is, an event card is generated based on the obtained alarm information, and then the event card is pushed and polled and updated through the card editing platform until the event is completed, and the final event card is pushed, which solves the problem that when an accident occurs in the system, the accident cannot be recorded and updated, and the accident information cannot be shared, resulting in low accident handling efficiency, and improves the efficiency of event card management. BRIEF DESCRIPTION OF THE DRAWINGS
[0048] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.
[0049] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, for ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.
[0050] Figure 1 A flowchart of the first embodiment of the event card management method of the present application is provided;
[0051] Figure 2 This is a schematic diagram of the user login interface involved in the event card management method of this application;
[0052] Figure 3 The event card management method of this application involves a schematic diagram of the operation options after the alarm information is parsed;
[0053] Figure 4 This is a schematic diagram of the first row of event cards in the event card management method of this application;
[0054] Figure 5 The event card management method for this application involves a schematic diagram of obtaining an event name row;
[0055] Figure 6 The event card management method for this application involves obtaining a schematic diagram of an event category row;
[0056] Figure 7 The event card management method for this application involves obtaining a schematic diagram of a deployment platform row;
[0057] Figure 8 The event card management method for this application involves obtaining a schematic diagram of the processing personnel and the escalation status;
[0058] Fig. 9 This is a schematic diagram of the event card management method for this application involving one-click card generation and push;
[0059] Fig.10 This is a schematic diagram of an event card editing platform related to the event card management method of this application;
[0060] Fig.11 This is a schematic diagram of an emergency group involved in the event card management method of this application;
[0061] Fig.12 A flowchart of the second embodiment of the event card management method of the present application is provided;
[0062] Fig.13 This is a schematic diagram of entering event card information related to the event card management method of this application;
[0063] Fig.14 This is a schematic diagram of the event card processing completed by the event card management method of this application;
[0064] Fig.15 This is a schematic diagram of the emergency group start switch involved in the event card management method of this application;
[0065] Fig.16This is a schematic diagram of a final event card involved in the event card management method of this application;
[0066] Fig.17 This is a schematic diagram of event upgrades involved in the event card management method of this application;
[0067] Fig.18 This is a schematic diagram of the robot event card information push involved in the event card management method of this application;
[0068] Fig.19 This is a schematic diagram of the change operation notification involved in the event card management method of this application;
[0069] Fig. 20 This is a schematic diagram of the alarm platform query processing object involved in the event card management method of this application;
[0070] Fig.21 This is a schematic diagram of an Excel sheet for event classification management related to the event card management method of this application;
[0071] Fig. 22 This is a schematic diagram of a database table of event severity grading rules related to the event card management method of this application;
[0072] Fig.23 This is a schematic diagram of the event rating calculation involved in the event card management method of this application;
[0073] Fig.24 This is a schematic diagram of the overall operation process of the event card management method of this application;
[0074] Fig.25 This is a schematic diagram of the event management system architecture involved in the event card management method of this application;
[0075] Fig.26 This is a schematic diagram of the module structure of the event card management device according to an embodiment of the present application;
[0076] Fig. 27 This is a schematic diagram of the device structure of the hardware operating environment involved in the event card management method in the embodiment of the present application.
[0077] The purpose, features and advantages of this application will be further described in conjunction with the embodiments and with reference to the accompanying drawings. DETAILED DESCRIPTION
[0078] It should be understood that the specific embodiments described herein are only used to explain the technical solutions of the present application and are not used to limit the present application.
[0079] In order to better understand the technical solution of the present application, a detailed description will be given below in conjunction with the accompanying drawings and specific implementation methods.
[0080] The main solution of the embodiment of the present application is: receiving a login request from a user; authenticating the login request through the authentication platform to obtain a first authentication result and sending it to the user; receiving a second authentication request initiated by the user based on the first authentication result, parsing the second authentication request to obtain a second verification result, the second verification result including the user information of the user; providing the event management authority corresponding to the user based on the user information. Parsing the alarm information to obtain the system number, system name, service unit number and alarm index; generating an event name according to the system number, system name, service unit number and alarm index; inputting the system number into the business continuity platform to obtain the system level corresponding to the system number, inputting the system name and service unit number into the centralized configuration management platform to obtain the subsystem level and service unit level; generating an event category according to the system level, subsystem level and service unit level; outputting an event card based on the event name and event category. Writing the field value of the event card into the event card database; based on the event card database, calling the office communication system interface through the card editing platform, sending the event card to the preset event emergency group; pushing the event card to the event emergency group through the push platform of the office communication system. The card database is polled and detected through the card editing platform; when the end notification of the event card is detected, the event recovery status of the event card is obtained; based on the event recovery status, the event card is updated to obtain the final event card; and the final event card is pushed to the event emergency group through the push platform of the office communication system. When it is detected that the event card has event upgrade information, the event upgrade information is collected through the event upgrade reminder platform; based on the upgrade information, the event card is updated to obtain the updated event card; and the updated event card is pushed to the event emergency group through the push platform of the office communication system. The final event card is parsed to obtain the business type, system level, availability loss ratio and fault duration corresponding to the final event card; based on the business type, system level, availability loss ratio and fault duration, the event is graded through the preset event grade management table to obtain the grade result of the final event card. Thus, the problem that when an accident occurs in the system, the accident cannot be recorded and updated, and the accident information cannot be shared, resulting in low accident handling efficiency is solved, the management of event cards is realized, and the efficiency of event card management is improved.Based on the scheme of the present invention, based on the fact that event fault information is not quickly notified to all potential related personnel in reality, a lot of time is spent in finding people or handling the incident, which ultimately affects the duration of emergency handling, and the on-duty personnel need to manually query their superiors based on the time of event occurrence, the time for human attention to notify superiors, and the information of the person in charge of the alarm system, which may eventually lead to delays in event escalation, an event card management method is designed, and the effectiveness of the event card management method of the present invention is verified when managing event cards. Finally, the efficiency of event card management performed by the method of the present invention is significantly improved.
[0081] In this embodiment, for the convenience of description, the event card management device is used as the execution subject for explanation below.
[0082] Due to the prior art, when an emergency occurs, the on-duty personnel notify the person in charge of the alarm system through the internal office communication system or by phone to handle it. However, the person who handles the root cause of the fault or needs to assist in the emergency may not be the person in charge of the alarm system. The event fault information is not quickly notified to all potential related personnel, resulting in a lot of time in the search / handling stage, which ultimately affects the duration of emergency handling. In addition, when an emergency occurs, the on-duty personnel cannot immediately know the importance level of the emergency and the notification escalation (leadership) process corresponding to the level. The on-duty personnel need to manually query their superiors based on the time of the incident, the time for manual attention to the notification escalation leader, and the person in charge information of the alarm system, which may eventually lead to delayed event escalation. After the emergency is restored, the initial classification of the emergency cannot be quickly known, and manual review of the classification rules is required. All of the above situations will lead to untimely management of emergencies.
[0083] The present application provides a solution, which polls the alarm platform through a card sharing platform, generates an event card when the alarm information is received, and pushes the event card through the card editing platform. At the same time, the event card is continuously polled and updated through the card editing platform to continuously follow up on the handling of the event.
[0084] From the above embodiments, it can be seen that the present application performs polling detection on the alarm platform through the card sharing platform to obtain alarm information; generates an event card based on the alarm information, and pushes the event card through the card editing platform; polls and updates the event card through the card editing platform to obtain the final event card, and pushes the final event card. Thus, the alarm platform is detected in real time through the card sharing platform to see whether there is alarm information. If there is, an event card is generated based on the obtained alarm information, and then the event card is pushed and polled and updated through the card editing platform until the event is completed, and the final event card is pushed, which solves the problem that when an accident occurs in the system, the accident cannot be recorded and updated, and the accident information cannot be shared, resulting in low accident handling efficiency, and improves the efficiency of event card management.
[0085] It should be noted that the execution subject of this embodiment can be a computing service device with data processing, network communication and program running functions, such as a tablet computer, a personal computer, a mobile phone, etc., or an electronic device capable of realizing the above functions, an event card management device, etc. The following takes the event card management device as an example to illustrate this embodiment and the following embodiments.
[0086] Based on this, the present application embodiment provides an event card management method, referring to Figure 1 , Figure 1 This is a flow chart of the first embodiment of the event card management method of the present application.
[0087] In this embodiment, the event card management method includes steps S04 to S06:
[0088] Before explaining the embodiments of the present application, it should be clear that the problem addressed by the scheme of the present embodiment is that in the processing of a business system, when an emergency occurs, the on-duty personnel are required to notify the person in charge of the alarm system through the internal office communication system or by telephone to handle it. However, the person who handles the root cause of the fault or needs to assist in the emergency may not be the person in charge of the alarm system. The event fault information is not quickly notified to all potential relevant personnel, resulting in a lot of time in the search / handling stage, which ultimately affects the duration of emergency handling. In addition, the on-duty personnel cannot immediately know the importance level of the emergency and the notification escalation (leadership) process corresponding to the level. The on-duty personnel need to manually query their superiors based on the time of the incident, the time to manually pay attention to the notification escalation leader, and the person in charge information of the alarm system, which may eventually cause delays in event escalation. In addition, after the emergency is recovered, it is impossible to quickly know the initial classification of the emergency, and it is necessary to manually review the classification rules.
[0089] Step S04, polling the alarm platform through the card sharing platform to obtain alarm information;
[0090] In the event management system, the alarm platform is preferentially polled and detected through the card sharing platform. Among them, the card sharing platform is pre-integrated in the event management system. Therefore, after logging into the event management system, the card sharing platform will poll and detect the alarm platform. The alarm platform is a platform for abnormal analysis of the business system. It can analyze the business system based on the pre-set rule parameters. When an abnormal situation occurs in the business system (such as business data errors, business system processing failures, and serious lack of customer information, etc.), the alarm platform will learn the corresponding fault information during polling detection, and convert it into alarm information, waiting for the next step to be executed.
[0091] Step S05, generating an event card based on the alarm information, and pushing the event card through a card editing platform;
[0092] After obtaining the corresponding alarm information of the business system, it is necessary to generate an event card. For example, when the current business system fails to obtain the customer's payment information, the corresponding event card can be generated with the time, service unit, customer information and person in charge;
[0093] After obtaining the event card, it also needs to be pushed to the corresponding processing port and business personnel so that the processing port can perform corresponding processing on the occurred fault, and the business personnel can be aware of the system fault and suspend related business to avoid customer dissatisfaction with the business. The processing port includes but is not limited to the communication port of the processing personnel in the same department, superiors and external staff, etc. At the same time, when it comes to business processing, the present embodiment can also notify the corresponding business personnel; the card push in the present embodiment is mainly carried out through the card editing platform, which can not only push the event card to the corresponding personnel, but also perform operations such as event upgrade, event cancellation and event information change on the event card.
[0094] Step S06: poll and update the event card through the card editing platform to obtain a final event card, and push the final event card.
[0095] Considering that abnormal situations in the business system may be upgraded or resolved, the card editing platform in this embodiment will also poll and update the event cards, that is, continuously receive the evolution direction and evolution status of the event cards to obtain the final event card, and push the final event card.
[0096] Specifically, before the step S04 of polling the alarm platform through the card sharing platform to obtain the alarm information, the method further includes:
[0097] Step S01, receiving a user's login request;
[0098] Step S02, authenticating the login request through the authentication platform, obtaining a first authentication result, and sending it to the user;
[0099] Step S03, receiving a second authentication request initiated by the user based on the first authentication result, parsing the second authentication request to obtain a second authentication result, wherein the second authentication result includes user information of the user;
[0100] Step S04: providing the event management authority corresponding to the user based on the user information.
[0101] In order to ensure the security of the business system, this embodiment also provides a corresponding login strategy. In order to prevent external personnel or non-related business personnel from affecting the event card, the event management system of this embodiment receives the user's login request and connects to the internal application unified authentication platform, such as Figure 2 As shown, the QR code scanning authentication mode is adopted. The client adopts the encryption method of public-private key pair. After the user successfully scans the code through the internal APP, the first authentication result is returned. After the client obtains the first authentication result, it initiates the second authentication to the authentication server through the encryption process to obtain the second authentication result.
[0102] It should be clear that the login process in this embodiment is based on the description of an internal employee of an enterprise. In other embodiments, in order to ensure the management and control of non-related business personnel, corresponding permission control can also be added to the system login. The specific authentication platform is set according to actual business needs.
[0103] After completing the user login and knowing the corresponding system operation authority of the user, the alarm platform can be polled to obtain the alarm information and perform corresponding operations, such as the above step S05. The step of generating an event card based on the alarm information includes:
[0104] Step S051, parsing the alarm information to obtain the system number, system name, service unit number and alarm indicator;
[0105] Step S052, generating an event name according to the system number, system name, service unit number and alarm indicator;
[0106] Step S053, inputting the system number into the business continuity platform to obtain the system level corresponding to the system number, and inputting the system name and service unit number into the centralized configuration management platform to obtain the subsystem level and service unit level;
[0107] Step S054, generating an event category according to the system level, subsystem level and service unit level;
[0108] Step S055: outputting an event card based on the event name and event category.
[0109] After receiving the alarm information sent by the alarm platform, the alarm information is analyzed to obtain the following Figure 3 The system number, system name, service unit number and alarm indicators are displayed, and corresponding operations are automatically displayed, such as "one-click card creation", "close" and "withdraw", etc.
[0110] When the user chooses to create a card with one click, or does not perform the corresponding operation for a period of time, the automatic card creation process will be performed for this alarm;
[0111] It is noted in advance that the event card in this embodiment includes a first row, an event name row, an event category row, a deployment platform row, an occurrence time row, an event source row, an event impact row, and a processing personnel and escalation status row, etc.;
[0112] Therefore, the above automatic card creation process is:
[0113] (1) First line: Figure 4 As shown, the date in the alarm information occurrence time is intercepted and the number of events on that day is automatically calculated by the background;
[0114] (2) Event name line: Figure 5 As shown, it is obtained by concatenating the system number, system name, service unit number, and alarm indicator in the alarm information;
[0115] (3) Event category row: e.g. Figure 6 As shown, the importance levels of systems, subsystems, and service units are obtained by calling the internal business continuity platform and the centralized configuration management platform;
[0116] (4) Deployment platform: Figure 7 As shown, the name of the platform where the application is running is obtained by calling the internal centralized configuration management platform;
[0117] (5) Occurrence time row: obtain the alarm (date) time in the alarm information;
[0118] (6) Event source line: the default is the internal alarm platform;
[0119] (7) Event impact line: Match the alarm information text and output a description of the changes in success rate / number of requests / response time;
[0120] (8) Processing personnel and upgrade status: Figure 8As shown, by calling the internal alarm platform, the agent telephone system, the organization and the human resources management system interface, the information and rank of the person who has been notified by telephone are automatically obtained. Among them, the upgrade situation should be added accordingly according to the subsequent content, which will not be repeated in this embodiment.
[0121] After the corresponding event card is output, in order to realize the rapid processing of the emergency, the above step S05, the step of pushing the event card through the card editing platform includes:
[0122] Step S056, writing the field value of the event card into the event card database;
[0123] Step S057, based on the event card database, calling the office communication system interface through the card editing platform, and sending the event card to a preset event emergency group;
[0124] Step S058: Push the event card to the event emergency group via the push platform of the office communication system.
[0125] like Fig. 9 As shown, in addition to generating an event card, it is also necessary to notify the corresponding personnel of the event card. In this embodiment, when the event card is shared with one click, click Fig.10 The front-end interface 2 (card editing platform or event card editing module) shown in the figure has three options: shortcut key / drop-down selection box / manual entry, which triggers the call of the back-end API to update / supplement the event card information in the database table and displays it on the front-end interface 2. The values of each field in the event card will be written into the database (event card information table) and automatically loaded into the front-end interface 2 (event card editing module). Subsequently, since the event card database records the corresponding processing personnel and processing team information, the internal office communication system robot can be called to automatically push the event card information to the dedicated emergency group of our company's internal office communication software for broadcast sharing. It should be clear that the internal dedicated emergency group in this embodiment is as follows: Fig.11 As shown, it is generated based on the content recorded in the event card database.
[0126] This embodiment uses the above scheme to specifically poll the alarm platform through the card sharing platform to obtain alarm information; generate an event card based on the alarm information, and push the event card through the card editing platform; poll and update the event card through the card editing platform to obtain the final event card, and push the final event card. Thus, the card sharing platform detects in real time whether there is alarm information on the alarm platform. If there is, an event card is generated based on the obtained alarm information, and then the card editing platform pushes and polls the event card until the event is completed, and then pushes the final event card. This solves the problem that when an accident occurs in the system, the accident cannot be recorded and updated, and the accident information cannot be shared, resulting in low accident handling efficiency, and improves the efficiency of event card management.
[0127] Based on the first embodiment of the present application, in the second embodiment of the present application, the same or similar contents as those in the above-mentioned embodiment 1 can be referred to the above introduction, and will not be repeated in the following. Fig.12 In step S06, the event card is polled and updated through the card editing platform to obtain a final event card, and the step of pushing the final event card also includes:
[0128] Step S061, polling the card database through the card editing platform;
[0129] Step S065, when the end notification of the event card is detected, the event recovery status of the event card is obtained;
[0130] Step S066, updating the event card based on the event recovery status to obtain a final event card;
[0131] Step S067: Push the final event card to the event emergency group via the push platform of the office communication system.
[0132] In the above embodiment, the generation and push of event cards have been described. With the processing of the staff, the event cards may be solved accordingly, so the card editing platform will poll the card database for detection;
[0133] When it is detected that the event card has been processed (i.e., the end notification), the event recovery status of the event card is obtained, and then the event card is updated based on the event response status to obtain the final event card;
[0134] At this time, you can Fig.13 As shown, manually enter the recovery time / business type / availability loss ratio, etc. Fig.14As shown, hover the mouse to preview and confirm that the content is correct, then click the <End of Emergency Group> button to send the event card (end stage) to the internal dedicated emergency group;
[0135] Send the final event card to the internal dedicated emergency group. You can manually enter all field values and click Fig.15 The <Emergency Group Start and End> button shown will Fig.16 The event card (all stages) shown is sent to the internal dedicated emergency group. It should be noted that for fault reporting events without alarm information, event cards can also be manually registered through the editing module;
[0136] It should be clear that the above content can be manually operated, for example, the system maintenance personnel determine whether to create a card after receiving the alarm information and whether to end the emergency group notification after the event processing is completed.
[0137] The above embodiment mainly describes the scenario where the event card ends. However, in the actual processing scenario, the event may not end, but rather escalate to a certain extent. This embodiment further proposes a strategy, that is, after the step of polling the card database through the card editing platform in step S061, the method further includes:
[0138] Step S062, when it is detected that the event card has event upgrade information, the event upgrade information is collected through the event upgrade reminder platform;
[0139] Step S063, based on the event upgrade information, obtaining a corresponding reminder time through the event upgrade reminder platform;
[0140] Step S064, based on the event upgrade information, updating the event card through the card editing platform to obtain an updated event card;
[0141] Step S065: Based on the reminder event, the updated event card is pushed to the corresponding event handler through the push platform of the office communication system.
[0142] Different requirements for the timeliness of upgrading (leadership) are required for system failures of different importance levels. The on-duty personnel need to upgrade to leaders of different ranks step by step according to the requirements of each time point. Therefore, this embodiment also provides an event upgrade reminder module. This module monitors the occurrence of new events in real time by polling the event card information table in the background. After the new event occurs, it reminds the on-duty personnel to manually upgrade the leader by phone. The upgrade reminder information is pushed, for example, the leader position to be upgraded and the leader's name, etc. Therefore, the upgrade reminder is only pushed to the duty group, not the emergency group. However, in order to make the relevant personnel aware of the handling matters, the card editing platform will also update the event card based on the event upgrade information to obtain the updated event card. In addition, the event card can also be updated based on the event upgrade information to obtain the updated event card. According to the corresponding system level, each time point that needs to be upgraded is monitored until the event is restored or all time point reminders are completed. At the same time, the internal organization and human resources management system interface is called to query the name of the upgraded role (leader), and the upgrade reminder is actively pushed to the corresponding event handler through the office communication system robot;
[0143] The specific process is as follows Fig.17 As shown, the event card database is polled by the back-end server to obtain the upgrade information of the event card, and the sending time, system level, person in charge and recovery time of the updated event are recorded;
[0144] Then, the event card is updated according to the above recorded content to obtain an updated event card;
[0145] Then Fig.18 As shown, the updated event card is pushed to the event emergency group through the push platform of the office communication system;
[0146] It should be clear that this embodiment also includes the situation where there is an alarm change, such as Fig.19 As shown, by calling the internal change risk control system to query whether there is a release record for the application within 24 hours, if not, fill in <No change release found yet> in the event card, if yes, fill in <Released> in the event card and automatically push the release record through the office communication system robot to contact the release executor to roll back the release, and then the alarm information notification generates the outbound call record as shown below Fig. 20 shown.
[0147] After the card processing is completed, the event can also be traced back and rated. Therefore, after the above step S06, polling and updating the event card through the card editing platform to obtain the final event card and pushing the final event card, the method further includes:
[0148] Step S07, parsing the final event card to obtain the service type, system level, availability loss ratio and fault duration corresponding to the final event card;
[0149] Step S08, based on the service type, system level, availability loss ratio and fault duration, event rating is performed through a preset event rating management table to obtain a rating result of the final event card.
[0150] For the classification of event cards, this embodiment adopts an event classification module, which electronically stores the event classification management method in the database, and then automatically calculates and generates the initial classification of the event through the database table according to the transaction type, system level, actual impact ratio or request failure ratio, fault duration and other field information in the alarm information when the event end button is clicked and the broadcast event ends (it also supports manual recalculation by clicking the button), so as to judge the severity level of the event at the first time. Fig.21 The Excel spreadsheet shown;
[0151] Convert the above table into an electronic form. Fig. 22 The rule table (database table) shown, the upper and lower limits in the database table are the boundary values of the square areas of each severity level in the above Excel legend when the transaction type and system level are fixed;
[0152] Once you understand how the event rating is calculated, you can Fig.23 To classify an event, select the business type and enter the availability loss ratio on the WEB front-end card editing page, then click the <End Emergency Group> button or the <Calculate> button to pass the business type (transaction type), system level, fault duration, and availability loss ratio into the database classification rule table for calculation. The initial classification result (severity) of the event is matched according to the upper and lower limits of the fault duration and the availability impact ratio.
[0153] This embodiment uses the above scheme to specifically poll the card database through the card editing platform; when the end notification of the event card is detected, the event recovery status of the event card is obtained; based on the event recovery status, the event card is updated to obtain the final event card; and the final event card is pushed to the event emergency group through the push platform of the office communication system. Thus, the card sharing platform detects in real time whether there is alarm information on the alarm platform. If there is, an event card is generated based on the obtained alarm information, and then the card editing platform pushes and polls the event card until the event is completed, and then pushes the final event card, which solves the problem of low accident handling efficiency caused by the inability to record and update the accident and the inability to share the accident information when an accident occurs in the system, thereby improving the efficiency of event card management.
[0154] For example, to help understand the implementation process of the event card management method obtained by combining this embodiment with the above-mentioned embodiment 1, please refer to Fig.24 , Fig.24 A brief flow chart of an event card management method is provided, specifically:
[0155] The overall framework of this embodiment is as follows Fig.25 As shown, it includes a WEB front end (browser interface), and performs identity authentication and initial grading on the back end server (API) through the WEB front end, while the back end server edits the card for the alarm information obtained by the internal application, generates the card, and broadcasts it to the WEB front end;
[0156] In addition, the backend server periodically polls the database (including the event classification rule table and the event card information table).
[0157] Reference Fig.24 Schematic diagram, after receiving a login request sent by a user through a browser access interface, this embodiment receives a scan code verification from the user through the authentication platform;
[0158] Then, if the authentication fails, it will display that the authentication fails and the login fails. If the authentication passes, the second authentication information with the login user information is obtained, and the second authentication information is matched with the restricted rule query. If there is a restricted rule, the output is that the user has no authority and the login fails.
[0159] Then, in the absence of restricted rules, the logged-in user information is obtained, and the corresponding alarm page (page 1) is loaded, wherein the alarm information of the alarm page is obtained by polling the alarm platform interface;
[0160] Then, after confirming the one-click card creation on the alarm interface, the corresponding event card is generated and broadcast and shared. At the same time, the background polls the event card to see if there is an upgraded reminder;
[0161] Then, when the event card is upgraded or changed, the card editing interface is loaded for polling and updating, and the card event can also be graded at the end of the event;
[0162] Finally, after the event is over, the final event card will be broadcast and shared.
[0163] It should be noted that the above examples are only used to understand the present application and do not constitute a limitation on the event card management method of the present application. More simple transformations based on this technical concept are all within the scope of protection of the present application.
[0164] This application also provides an event card management device, please refer to Fig.26 , the event card management device comprises:
[0165] The detection module 10 is used to poll the alarm platform through the card sharing platform to obtain alarm information;
[0166] A generating module 20, configured to generate an event card based on the alarm information, and push the event card through a card editing platform;
[0167] The updating module 30 is used to poll and update the event card through the card editing platform to obtain the final event card and push the final event card.
[0168] The event card management device provided by the present application adopts the event card management method in the above embodiment, which can solve the technical problem that when an accident occurs in the system, the accident cannot be recorded and updated, and the accident information cannot be shared, resulting in low accident handling efficiency. Compared with the prior art, the beneficial effects of the event card management device provided by the present application are the same as the beneficial effects of the event card management method provided by the above embodiment, and the other technical features in the event card management device are the same as the features disclosed in the above embodiment method, which will not be repeated here.
[0169] The present application provides an event card management device, which includes: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute the event card management method in the above-mentioned embodiment one.
[0170] Reference below Fig. 27, which shows a schematic diagram of the structure of an event card management device suitable for implementing the embodiment of the present application. The event card management device in the embodiment of the present application may include but is not limited to mobile terminals such as mobile phones, laptop computers, digital broadcast receivers, PDAs (Personal Digital Assistants), PADs (Portable Application Descriptions), PMPs (Portable Media Players), vehicle-mounted terminals (such as vehicle-mounted navigation terminals), etc., and fixed terminals such as digital TVs, desktop computers, etc. Fig. 27 The event card management device shown is merely an example and should not bring any limitation to the functions and scope of use of the embodiments of the present application.
[0171] like Fig. 27 As shown, the event card management device may include a processing device 1001 (e.g., a central processing unit, a graphics processor, etc.), which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM: Read Only Memory) 1002 or a program loaded from a storage device 1003 to a random access memory (RAM: Random Access Memory) 1004. In RAM1004, various programs and data required for the operation of the xxx device are also stored. The processing device 1001, ROM1002, and RAM1004 are connected to each other through a bus 1005. An input / output (I / O) interface 1006 is also connected to the bus. Generally, the following systems can be connected to the I / O interface 1006: an input device 1007 including, for example, a touch screen, a touch pad, a keyboard, a mouse, an image sensor, a microphone, an accelerometer, a gyroscope, etc.; an output device 1008 including, for example, a liquid crystal display (LCD: Liquid Crystal Display), a speaker, a vibrator, etc.; a storage device 1003 including, for example, a magnetic tape, a hard disk, etc.; and a communication device 1009. The communication device 1009 can allow the event card management device to communicate wirelessly or wired with other devices to exchange data. Although the event card management device with various systems is shown in the figure, it should be understood that it is not required to implement or have all the systems shown. More or fewer systems can be implemented or have alternatively.
[0172] In particular, according to the embodiments disclosed in the present application, the process described above with reference to the flowchart can be implemented as a computer software program. For example, the embodiments disclosed in the present application include a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program includes a program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from a network through a communication device, or installed from a storage device 1003, or installed from a ROM 1002. When the computer program is executed by the processing device 1001, the above-mentioned functions defined in the method of the embodiment disclosed in the present application are executed.
[0173] The event card management device provided by the present application adopts the event card management method in the above embodiment, which can solve the technical problem that when an accident occurs in the system, the accident cannot be recorded and updated, and the accident information cannot be shared, resulting in low accident handling efficiency. Compared with the prior art, the beneficial effects of the event card management device provided by the present application are the same as the beneficial effects of the event card management method provided by the above embodiment, and the other technical features in the event card management device are the same as the features disclosed in the method of the previous embodiment, which will not be repeated here.
[0174] It should be understood that the various parts disclosed in this application can be implemented by hardware, software, firmware or a combination thereof. In the description of the above embodiments, specific features, structures, materials or characteristics can be combined in any one or more embodiments or examples in a suitable manner.
[0175] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art who is familiar with the present technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.
[0176] The present application provides a computer-readable storage medium having computer-readable program instructions (ie, computer programs) stored thereon, and the computer-readable program instructions are used to execute the event card management method in the above-mentioned embodiment.
[0177] The computer-readable storage medium provided in the present application may be, for example, a USB flash drive, but is not limited to electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, systems or devices, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In this embodiment, the computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in combination with an instruction execution system, system or device. The program code contained on the computer-readable storage medium may be transmitted using any appropriate medium, including but not limited to: wires, optical cables, RF (Radio Frequency), etc., or any suitable combination of the above.
[0178] The computer-readable storage medium may be included in the event card management device; or may exist independently without being assembled into the event card management device.
[0179] The above-mentioned computer-readable storage medium carries one or more programs. When the above-mentioned one or more programs are executed by the event card management device, the event card management device: polls the alarm platform through the card sharing platform to obtain alarm information; generates an event card based on the alarm information, and pushes the event card through the card editing platform; polls and updates the event card through the card editing platform to obtain the final event card, and pushes the final event card.
[0180] Computer program code for performing the operations of the present application may be written in one or more programming languages or a combination thereof, including object-oriented programming languages such as Java, Smalltalk, C++, and conventional procedural programming languages such as "C" or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, as a separate software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., via the Internet using an Internet service provider).
[0181] The flow chart and block diagram in the accompanying drawings illustrate the possible architecture, function and operation of the system, method and computer program product according to various embodiments of the present application. In this regard, each square box in the flow chart or block diagram can represent a module, a program segment or a part of a code, and the module, the program segment or a part of the code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the square box can also occur in a sequence different from that marked in the accompanying drawings. For example, two square boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each square box in the block diagram and / or flow chart, and the combination of the square boxes in the block diagram and / or flow chart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.
[0182] The modules involved in the embodiments described in this application may be implemented by software or hardware, wherein the name of the module does not constitute a limitation on the unit itself in some cases.
[0183] The readable storage medium provided by the present application is a computer-readable storage medium, which stores computer-readable program instructions (i.e., computer programs) for executing the above-mentioned event card management method, and can solve the technical problem that when an accident occurs in the system, the accident cannot be recorded and updated, and the accident information cannot be shared, resulting in low accident handling efficiency. Compared with the prior art, the beneficial effects of the computer-readable storage medium provided by the present application are the same as the beneficial effects of the event card management method provided by the above-mentioned embodiment, and will not be repeated here.
[0184] The present application also provides a computer program product, including a computer program, which implements the steps of the event card management method as described above when executed by a processor.
[0185] The computer program product provided by the present application can solve the technical problem that when an accident occurs in the system, the accident cannot be recorded and updated, and the accident information cannot be shared, resulting in low accident handling efficiency. Compared with the prior art, the beneficial effects of the computer program product provided by the present application are the same as the beneficial effects of the event card management method provided in the above embodiment, and will not be repeated here.
[0186] The above descriptions are only some embodiments of the present application, and are not intended to limit the patent scope of the present application. All equivalent structural changes made using the contents of the present application specification and drawings under the technical concept of the present application, or direct / indirect applications in other related technical fields are included in the patent protection scope of the present application.
Claims
1. An event card management method, characterized in that: The method is applied to an event management system, which includes a card sharing platform and a card editing platform. The method includes: Polling the alarm platform through the card sharing platform to obtain alarm information; Generate an event card based on the alarm information, and push the event card through the card editing platform; The event card is polled and updated through the card editing platform to obtain a final event card, and the final event card is pushed.
2. The method according to claim 1, characterized in that The event management system further includes an authentication platform. Before the step of polling the alarm platform through the card sharing platform to obtain the alarm information, the method further includes: Receive the user's login request; Authenticating the login request through the authentication platform, obtaining a first authentication result, and sending it to the user; receiving a second authentication request initiated by the user based on the first authentication result, parsing the second authentication request to obtain a second authentication result, where the second authentication result includes user information of the user; Provide event management authority corresponding to the user based on the user information.
3. The method according to claim 1, characterized in that The step of generating an event card based on the alarm information comprises: Parsing the alarm information to obtain the system number, system name, service unit number and alarm indicator; Generate an event name according to the system number, system name, service unit number and alarm indicator; Input the system number into the business continuity platform to obtain the system level corresponding to the system number, and input the system name and service unit number into the centralized configuration management platform to obtain the subsystem level and service unit level; generating event categories according to the system level, subsystem level, and service unit level; Output an event card based on the event name and event category.
4. The method according to claim 1, characterized in that The step of pushing the event card through the card editing platform includes: Writing the field values of the event card into the event card database; Based on the event card database, the office communication system interface is called through the card editing platform to send the event card to a preset event emergency group; The event card is pushed to the event emergency group through the push platform of the office communication system.
5. The method according to claim 4, characterized in that The step of polling and updating the event card through the card editing platform to obtain a final event card and pushing the final event card includes: Performing polling detection on the card database through the card editing platform; When the end notification of the event card is detected, the event recovery status of the event card is obtained; The event card is updated based on the event recovery status to obtain a final event card; The final event card is pushed to the event emergency group through the push platform of the office communication system.
6. The method according to claim 5, characterized in that After the step of polling the card database through the card editing platform, the method further includes: When it is detected that the event card has event upgrade information, the event upgrade information is collected through the event upgrade reminder platform; Based on the event escalation information, a corresponding reminder time is obtained through the event escalation reminder platform; Based on the event upgrade information, the event card is updated through the card editing platform to obtain an updated event card; Based on the reminder event, the updated event card is pushed to the corresponding event handler via the push platform of the office communication system.
7. The method according to claim 1, characterized in that After the step of polling and updating the event card through the card editing platform to obtain a final event card and pushing the final event card, the method further includes: Parsing the final event card to obtain the service type, system level, availability loss ratio and fault duration corresponding to the final event card; Based on the service type, system level, availability loss ratio and fault duration, event rating is performed through a preset event rating management table to obtain a rating result of the final event card.
8. An event card management device, characterized in that: The device comprises: The detection module is used to poll the alarm platform through the card sharing platform to obtain alarm information; A generation module, used to generate an event card based on the alarm information, and push the event card through a card editing platform; The updating module is used to poll and update the event card through the card editing platform to obtain the final event card and push the final event card.
9. An event card management device, characterized in that: The device comprises: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the computer program is configured to implement the steps of the event card management method according to any one of claims 1 to 7.
10. A computer program product, characterized in that The computer program product comprises a computer program, and when the computer program is executed by a processor, the steps of the event card management method according to any one of claims 1 to 7 are implemented.
