A visual on-duty emergency response interactive method and device

Abstract

This article relates to the field of big data, and in particular to a visual on-duty emergency response interactive method and device. The method includes obtaining and displaying the first alarm information of the fault; generating shared alarm information based on the first alarm information; sending the shared alarm information to the technical support terminal; receiving a request for obtaining the second alarm information sent by the technical support terminal; obtaining the second alarm information based on the request for obtaining the second alarm information and the application authority of the fault; sending the second alarm information to the technical support terminal; receiving the fault handling plan generated by the technical support terminal based on the shared alarm information and the second alarm information; and executing the fault handling plan to solve the fault.

Description

Technical Field

[0001] This article relates to the field of information security technology and can be used in the financial field, especially a visual on-duty emergency response method and device. Background Art

[0002] As the types of banking services increase, the probability of banking business system failures may increase, and the operation of business systems is becoming increasingly complex. When a failure occurs, unlike the failure emergency processes of systems, networks and equipment with clear categories and fixed means, applications lack a unified and standardized emergency process when a failure occurs. At the same time, faced with a wide variety of application systems, the on-duty personnel cannot fully understand them, resulting in a relatively complex process for handling failures and a relatively long time to handle failures. Therefore, bank application system failures place high demands on on-duty personnel and manual intervention, and pose a severe test to the daily operation of the banking system.

[0003] The conventional method for solving financial system fault processing is usually that the on-duty personnel manually analyze each fault alarm, contact the business support personnel by phone for the alarms that are uncertain whether they need to be handled, find a solution under the guidance of the business support personnel, and then open the corresponding tools to perform a series of operations to troubleshoot the fault. This method of troubleshooting is time-consuming and cumbersome, and cannot solve the fault as quickly as possible.

[0004] In view of the cumbersome and time-consuming process of handling bank application failures, there is an urgent need to study a visual emergency response interactive system and method. When an application fails, the emergency response plan can be determined and handled quickly through the interaction between the system and business support personnel to avoid the failure causing the suspension of banking business and adversely affecting customer experience. Summary of the invention

[0005] To solve the above-mentioned problems of the prior art, the embodiments of this article provide a visual emergency handling interaction method, apparatus, computer equipment and storage medium, which solve the problem that the process of handling bank application failures in the prior art is cumbersome and time-consuming.

[0006] The embodiment of this article provides a visual emergency handling method, including:

[0007] Obtain the first alarm information of the fault and display it;

[0008] generating shared alarm information according to the first alarm information;

[0009] Sending the shared alarm information to a technical support terminal;

[0010] Receiving a request for obtaining second alarm information sent by the technical support terminal;

[0011] Acquire the second alarm information according to the request for acquiring the second alarm information and the application authority of the fault;

[0012] Sending the second alarm information to the technical support terminal;

[0013] Receiving a fault handling solution generated by the technical support terminal according to the shared alarm information and the second alarm information;

[0014] The fault handling solution is executed to resolve the fault.

[0015] According to one aspect of the embodiments of this document, the first alarm information is alarm information related to the fault, and includes at least: server information, alarm events, error information, and application responsible person information.

[0016] According to one aspect of the embodiments of this document, generating shared alarm information based on the first alarm information includes: obtaining full information of server information, alarm events and error information in the first alarm information; taking a screenshot of the display interface of the full information, and using the screenshot image as the shared alarm information.

[0017] According to one aspect of the embodiments of this document, the full information of the server information includes the server address, server name, and server network information; the full information of the alarm event includes the number, name, and danger level of the alarm event; the full information of the error information includes the error start time, error duration, and specific content of the error.

[0018] According to one aspect of the embodiments of this document, obtaining the full information of server information, alarm events and error information in the first alarm information further includes: obtaining the full information or partial full information of server information, alarm events and error information in the first alarm information according to the common level corresponding to the fault.

[0019] According to one aspect of the embodiments of this document, sending the shared alarm information to the technical support terminal further includes querying the address of the technical support terminal according to the application responsible person information in the first alarm information, and sending the shared alarm information to the technical support terminal.

[0020] According to one aspect of the embodiments of the present invention, before generating shared alarm information based on the first alarm information, the method also includes: determining key information of the first alarm information; matching the key information of the first alarm information in a preset scenario library; when the match is successful, generating a fault handling plan for the fault; when the match fails, generating shared alarm information based on the first alarm information.

[0021] According to one aspect of the embodiments of the present invention, obtaining the second alarm information based on the second alarm information request and the business authority of the fault further includes: obtaining fault information based on the demand information in the second alarm information request; comparing the authority information of the application responsible person in the second alarm information request with the application authority of the fault information, and using the fault information that is consistent with the authority of the application responsible person in the second alarm information request as the second alarm information.

[0022] According to one aspect of the embodiments of this document, the application permissions of the faults include: fault information related to various faults, and each type of fault information has a corresponding security level.

[0023] According to one aspect of the embodiments of this document, the fault handling solution generated by the technical support terminal based on the shared alarm information and the second alarm information includes: determining key information of the shared alarm information and the second alarm information; matching the key information in a preset scenario library; and when the match is successful, generating a fault handling solution for the fault.

[0024] According to one aspect of the embodiments of this document, the fault handling solution includes one or a combination of the following: repair, delete, restore, backup, stop running, and alarm.

[0025] The embodiment of the present invention also provides a visual on-duty emergency handling device, including:

[0026] A first alarm information acquisition unit, used to acquire and display the first alarm information of the fault;

[0027] A shared alarm information generating unit, configured to generate shared alarm information according to the first alarm information;

[0028] A shared alarm information sending unit, used for sending the shared alarm information to a technical support terminal;

[0029] A second alarm information request receiving unit, configured to receive a request for obtaining second alarm information sent by the technical support terminal;

[0030] A second alarm information obtaining unit, configured to obtain the second alarm information according to the second alarm information obtaining request and the application authority of the fault;

[0031] A second alarm information sending unit, used for sending the second alarm information to the technical support terminal;

[0032] A fault handling solution receiving unit, configured to receive a fault handling solution generated by the technical support terminal according to the shared alarm information and the second alarm information;

[0033] An execution unit is used to execute the fault handling solution to solve the fault.

[0034] The embodiments of the present invention further provide a computer device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the above method when executing the computer program.

[0035] The embodiments of the present invention also provide a computer-readable storage medium on which computer instructions are stored. When the computer instructions are executed by a processor, the above method is implemented.

[0036] By using the embodiments of this article, when an application fails, the emergency response plan for the failure can be determined promptly and accurately through the interaction between the system and business support personnel, and the failure can be quickly processed to avoid the failure causing the suspension of banking business and adversely affecting customer experience. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0038] Figure 1 The figure shows a schematic diagram of the network structure of the visual on-duty emergency response interactive system of the embodiment of this article;

[0039] Figure 2 It is a flowchart of a visual on-duty emergency response interaction method according to an embodiment of this invention;

[0040] Figure 3 The figure shows a structural schematic diagram of a visual on-duty emergency response interactive device according to an embodiment of this invention;

[0041] Figure 4 The figure shows a specific structural diagram of the visual on-duty emergency response interactive device according to the embodiment of this article;

[0042] Figure 5 The figure is a flow chart of an automatic fault handling solution of an embodiment of this article;

[0043] Figure 6 It is a flow chart of a method for generating shared alarm information according to an embodiment of this invention;

[0044] Figure 7 The flowchart of obtaining the second alarm information in the first embodiment of this article is shown;

[0045] Figure 8It is a flowchart of generating a fault handling solution according to the shared alarm information and the second alarm information in the embodiment of this article;

[0046] Fig. 9 Shown is a schematic diagram of the structure of a computer device according to an embodiment of this invention.

[0047] Description of the accompanying symbols:

[0048] 101. Emergency response interactive system;

[0049] 102. Duty server;

[0050] 103. Technical support terminal;

[0051] 301. A first alarm information obtaining unit;

[0052] 3011, display module;

[0053] 302, shared alarm information generating unit;

[0054] 303, shared alarm information sending unit;

[0055] 304, a second alarm information request receiving unit;

[0056] 305. A second alarm information obtaining unit;

[0057] 306. a second alarm information sending unit;

[0058] 307. Fault handling solution receiving unit;

[0059] 308, execution unit;

[0060] 3021. Determine module;

[0061] 3022, matching module;

[0062] 3071, fault handling solution display module;

[0063] 902. Computer equipment;

[0064] 904, processor;

[0065] 906. Memory;

[0066] 908, driving mechanism;

[0067] 910, input / output module;

[0068] 912. Input device;

[0069] 914. Output device;

[0070] 916. Presentation equipment;

[0071] 918. Graphical user interface;

[0072] 920, network interface;

[0073] 922, communication link;

[0074] 924. Communication bus. DETAILED DESCRIPTION

[0075] In order to enable those skilled in the art to better understand the technical solutions in this specification, the technical solutions in the embodiments of this specification will be clearly and completely described below in conjunction with the drawings in the embodiments of this specification. Obviously, the described embodiments are only part of the embodiments of this specification, not all of the embodiments. Based on the embodiments of this specification, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this specification.

[0076] It should be noted that the terms "first", "second", etc. in the specification and claims of this article and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchanged where appropriate, so that the embodiments of this article described here can be implemented in an order other than those illustrated or described here. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions, for example, a process, method, device, product or equipment that includes a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or equipment.

[0077] This specification provides method operation steps as described in the embodiments or flow charts, but more or fewer operation steps may be included based on routine or non-creative work. The order of steps listed in the embodiments is only one way of executing the order of many steps and does not represent the only execution order. When the system or device product is executed in practice, it can be executed in the order of the method shown in the embodiments or the drawings or in parallel.

[0078] It should be noted that the visualized on-duty emergency response interaction method and device in this article can be used in the financial field, and can also be used in any field other than the financial field. The application field of the visualized on-duty emergency response interaction method and device in this article is not limited.

[0079] like Figure 1The figure shows a network structure diagram of a visual on-duty emergency response interaction system according to an embodiment of the present invention, which describes a visual on-duty emergency response interaction method by combining an emergency response interaction system 101, an on-duty server 102, and a technical support terminal 103. The emergency response interaction system 101, the on-duty server 102, and the technical support terminal 103 can interact with each other.

[0080] In some embodiments of the present specification, the emergency handling interactive system 101 may be an electronic device with a network interaction function, or may be software running in the electronic device to provide business logic for data processing and network interaction. The emergency handling interactive system 101 may autonomously fail during normal operation and generate failure alarm information. The emergency handling interactive system 101 may send the failure alarm information to the duty server 102.

[0081] In some embodiments of the present specification, the duty server 102 may be an electronic device with a network interaction function, or may be software running in the electronic device and providing business logic for data processing and network interaction. The duty server 102 includes a first acquisition unit for acquiring the first alarm information of the fault, a shared alarm information generation unit 302 for generating shared alarm information according to the first alarm information, a shared alarm information sending unit 303 for sending the shared alarm information to the technical support terminal, a second alarm information request receiving unit 304 for receiving a request for acquiring the second alarm information sent by the technical support terminal 103, and a second alarm information sending unit 306 for sending the second alarm information to the technical support terminal 103.

[0082] In some embodiments of the present specification, the technical support terminal 103 may be a desktop computer, a tablet computer, a laptop computer, a smart phone, a digital assistant, a smart wearable device, etc. The technical support terminal 103 is not limited to the above-mentioned electronic devices with a certain entity, and it may also be software running in the above-mentioned electronic devices.

[0083] like Figure 2 The flowchart of a visual on-duty emergency response interactive method according to an embodiment of the present invention is shown. In this figure, a process method for generating a fault handling solution using alarm information is described, which specifically includes the following steps:

[0084] Step 201, obtaining and displaying the first alarm information of the fault;

[0085] Step 202, generating shared alarm information according to the first alarm information;

[0086] Step 203, sending the shared alarm information to a technical support terminal;

[0087] Step 204, receiving a request for obtaining second alarm information sent by the technical support terminal;

[0088] Step 205, obtaining the second alarm information according to the request for obtaining the second alarm information and the application authority of the fault;

[0089] Step 206, sending the second alarm information to the technical support terminal;

[0090] Step 207, receiving the fault handling solution generated by the technical support terminal according to the shared alarm information and the second alarm information;

[0091] Step 208: Execute the fault handling solution to resolve the fault.

[0092] As an embodiment of this article, the first alarm information is alarm information related to the fault, and the first alarm information at least includes: server information, alarm event, error information, application person in charge information, etc.

[0093] In this step, the fault is an abnormal event occurring in the application of the banking system, and the first alarm information of the fault is irregularly generated by the system application. The first alarm information of the fault is a collection of at least one alarm information of the fault, and the first alarm information includes an alarm log, an alarm list, etc. The first alarm information can be composed of codes, words, characters, letters, numbers, etc.

[0094] In this step, the server information includes the server address, server name, server memory, and server normal operation time. The alarm event includes: alarm start time, alarm event name, alarm device, alarm business department, alarm business type, alarm danger level, etc. The error information includes: error start time, error content, error business department, error business type, etc. The application person in charge information includes: application person in charge ID, application person in charge department, application person in charge authority level, application person in charge online time, application person in charge contact address, application person in charge corresponding terminal address, etc. The application person in charge contact address includes the application person in charge's mobile phone number, email address, instant messaging software user name, etc.

[0095] In this step, the first alarm information also includes historical alarm information events, the normal operation time of the historical alarm information from the current first alarm information, and the like.

[0096] In this step, after the duty server obtains the first alarm information generated by the system application, it displays the first alarm information in the form of a page on a display device with display function based on web front-end technology, through Java script plug-in (JavaScript), web real-time communication (WebTRC) transmission, and full-duplex communication protocol (WebSocket) based on transmission control protocol. The display device includes but is not limited to: computer monitors, monitoring screens, mobile device displays, etc.

[0097] As an embodiment of this invention, generating shared alarm information according to the first alarm information includes:

[0098] Obtaining the full amount of information of the server information, alarm event and error information in the first alarm information;

[0099] A screenshot is taken of the display interface of the full information, and the screenshot image is used as the shared alarm information.

[0100] In this step, the full information in the first alarm information is the information of all dimensions of the first alarm information. The system cannot generate a fault handling plan for the fault through the first alarm information, and it is necessary to obtain full information of more content related to the fault based on the first alarm information. Therefore, the content of the shared alarm information is more comprehensive than the content of the first alarm information. The display interface of the full information is saved as a screenshot image, and the shared alarm information is saved in a unified picture format, so that when it is displayed across terminals, the format can be stable when displayed on multiple display interfaces of multiple display terminals, and there will be no abnormal situations such as garbled characters, line breaks, and string disconnections.

[0101] As an embodiment of this invention, the full amount of information of the server information includes the server address, the server name, and the server network information;

[0102] The full information of the alarm event includes the number, name, and danger level of the alarm event;

[0103] The full amount of information of the error message includes the error start time, error duration, and specific content of the error.

[0104] In this step, the full information of the alarm event also includes the start time of the alarm event, the device that issued the alarm, the application that issued the alarm, the network environment where the alarm is located, etc. The full information of the error information also includes the error service type, historical error information, etc.

[0105] As an embodiment of this article, obtaining the full information of service information, alarm time and error information in the first alarm information further includes: obtaining the information or part of the full information of server information, alarm event and error information in the first alarm information shown according to the common level corresponding to the fault.

[0106] In this step, the common level corresponding to the fault indicates the frequency of occurrence of the fault within a period of time, and the common level corresponding to the fault can also reflect the safety level and / or importance level corresponding to the fault. Among them, the emergency response system can stipulate that faults with high common levels are faults that occur frequently in historical time and are easy to handle; faults with low common levels are faults that occur infrequently in historical time and are difficult to handle. Among them, the higher the common level corresponding to the fault, the more common the fault, the easier it is to handle, and the shorter the processing time; the lower the common level corresponding to the fault, the rarer the fault, the greater the difficulty of handling, and the longer the processing time.

[0107] In the embodiments of this document, full or partial information of server information, alarm events, and error information in the first alarm information may also be obtained based on the degree of harm and urgency corresponding to the fault.

[0108] In this step, for common faults of lower levels, the handling difficulty is greater, and the technical support end needs to obtain more information to assist the business support personnel in fault diagnosis. Therefore, it is necessary to obtain full information such as server information, alarm events, and error information in the first alarm information, so that technical support can determine the cause of the fault based on sufficient alarm information; for common faults of higher levels, the handling difficulty is less, and the business support terminal needs to obtain less information to assist the business support personnel in fault diagnosis. Obtaining partial full information, that is, partial information is sufficient to help the business support personnel determine how to solve the fault.

[0109] In this step, the corresponding level of the fault can be represented by a combination of numbers, letters, etc.

[0110] Taking banking business as an example, during the business process, two types of application failures occur: "availability disconnection" and "interface garbled characters". The common level corresponding to the failure "availability disconnection" is level 3, which means that the failure is relatively common, and the on-duty server can handle it by obtaining partial full information such as server ID, alarm event name, error information, or the basic content of the alarm information in the first alarm information; for another example, the common level corresponding to the failure "interface garbled characters" is level 1, which means that the "interface garbled characters" failure is rare and difficult to handle. The on-duty server needs to obtain the full information of the server, the full information of the alarm event, and the full information of the error information in the first alarm information before it can handle the relevant failures.

[0111] As an embodiment of this invention, sending the shared alarm information to the technical support terminal further includes: querying the address of the technical support terminal according to the application responsible person information in the first alarm information, and sending the shared alarm information to the technical support terminal.

[0112] In this step, the server may obtain multiple first alarm messages at the same time at a certain moment. As described in the above embodiment, the first alarm message includes application responsible personnel information. Among them, one first alarm message can be processed by at least one corresponding application responsible personnel, and the one application responsible personnel can process at least one first alarm message. In this step, the technical support terminal to which the first alarm message is to be sent can be determined according to the application responsible personnel information in the first alarm message. Among them, the address of the technical support terminal can be determined according to the ID of the application responsible personnel. For example, the address of the corresponding technical support terminal A is determined according to the ID of the application responsible personnel A in the first alarm message X, the address of the corresponding technical support terminal B is determined according to the ID of the application responsible personnel B in the first alarm message Y, and the address of the corresponding technical support terminal C is determined according to the ID of the application responsible personnel C in the first alarm message Z. Therefore, when sending the shared alarm message to the technical support terminal, the server needs to determine the application responsible personnel information in at least one first alarm message, determine the address of the technical support terminal, and then send the shared alarm message to the technical support terminal.

[0113] As an embodiment of this article, before generating shared alarm information based on the first alarm information, it also includes: determining the key information of the first alarm information; matching the key information of the first alarm information in a preset scenario library; when the match is successful, generating a fault handling plan for the fault; when the match fails, generating shared alarm information based on the first alarm information.

[0114] Before generating the shared alarm information in this step, the system first determines whether a fault handling solution for the fault can be directly generated according to the first alarm information. If a fault handling solution cannot be generated according to the first alarm information, subsequent steps are executed.

[0115] In this step, the system can identify the key information of the first alarm information by keyword extraction, text recognition, image recognition, etc. The key information can be one or any combination of the alarm name, application person in charge information, alarm event, server address, etc.

[0116] In this step, the system pre-sets a preset scenario library, which stores key information of historical alarm information and historical fault handling methods corresponding to the key information. For example, the preset scenario library contains the key information alarm name "telephone disconnected" and the corresponding fault handling method is "connect the telephone line"; for another example, the preset scenario library contains the key information alarm event "interface garbled" and the corresponding fault handling method is "restart the corresponding device / software", etc.

[0117] In this step, a fault handling solution for the fault can be matched and generated based on the key information already in the preset scenario library; when the key information cannot be matched in the preset scenario library, it means that the preset scenario library does not store the fault handling solution corresponding to the current fault, then shared alarm information is generated based on the first alarm information, and subsequent steps are executed.

[0118] As an embodiment of this invention, obtaining the second alarm information according to the request for obtaining the second alarm information and the service authority of the fault further includes:

[0119] Acquire fault information according to the requirement information in the second alarm information request;

[0120] According to the permission information of the application responsible person in the second alarm information request, the permission of the application responsible person is compared with the application permission of the fault information.

[0121] The fault information that is consistent with the authority of the application responsible person in the second alarm information request is used as the second alarm information.

[0122] In this step, the system cannot match the fault handling solution in the preset scenario library. The business support terminal makes a request to the system for the second alarm information based on the received shared alarm information. The second alarm information and the first alarm information can be different business information based on the same device, the same software, and the same application; or they can be different business information based on different devices, different software, and different applications. The second alarm information request can be made by the application responsible person of the business support terminal based on his or her authority information.

[0123] Among them, the demand information in the second alarm information request includes the application responsible person information, the server address of the second alarm information, etc. Among them, based on business security considerations, the application responsible person cannot make a second alarm information request beyond his authority. For example, the person in charge of the application with a low authority level cannot access the relevant information of the server with a high authority range. Therefore, it is necessary to compare the authority information of the application responsible person in the second alarm information request with the application authority of the fault information. If the authority information of the application responsible person is higher than the application authority of the fault information required in the second alarm information request, the system can obtain the fault information required in the second alarm information request, and use the fault information that matches the authority of the application responsible person in the second alarm information request as the second alarm information. If the authority information of the application responsible person is lower than the application authority of the fault information, the second alarm information request cannot be obtained. For example, when the application manager is diagnosing a fault, he needs to obtain more information about the fault, so the second alarm information request includes the need to obtain more information related to the fault. However, the application manager's authority does not allow him to obtain the address information of a certain server, but the second alarm information request includes the need to obtain the address information of the server. In this case, the system will send the fault information that meets the authority of the application manager to the technical support terminal of the application manager based on the application permissions corresponding to the relevant fault information involved in the fault, and will not obtain the server address information and feed it back to the technical support terminal of the application manager.

[0124] As an embodiment of this invention, the application authority of the fault includes: fault information involved in various faults, and each type of fault information has a corresponding security level.

[0125] In this step, different fault application permissions correspond to different security levels. The security level of the fault information is different from the common level corresponding to the fault described in the previous embodiment. The system determines whether the permission information of the application responsible person sends the second alarm information request based on the security level corresponding to the fault.

[0126] As an embodiment of this invention, the receiving of the fault handling solution generated by the technical support terminal according to the shared alarm information and the second alarm information includes:

[0127] The technical support terminal 103 determines key information of the shared alarm information and the second alarm information; matches the key information in a preset scenario library; and generates a fault handling solution for the fault when the match is successful.

[0128] In this step, the technical support terminal 103 receives the second alarm information, and the technical support terminal 103 determines the key information of the shared alarm information and the second alarm information by means of keyword extraction, text recognition, image recognition, etc. The specific method for determining the key information of the shared alarm information and the second alarm information can refer to the description of determining the key information of the first alarm information in the previous embodiment. The technical support terminal 103 will match the key information of the shared alarm information and the second alarm information in the preset scenario library. When a fault handling solution corresponding to the key information is matched in the preset scenario library, a fault handling solution for the fault is generated.

[0129] As an embodiment of this article, the fault handling solution includes one or a combination of the following: repair, delete, restore, backup, stop running, and alarm.

[0130] In this step, the troubleshooting solutions for the fault include repairing application data, deleting application data, restoring historical settings, backing up application data, stopping the current device / software, executing alarms, etc.

[0131] like Figure 3 The figure shows a schematic diagram of the structure of a visual on-duty emergency response interaction device according to an embodiment of the present invention. The figure describes the basic structure of the visual on-duty emergency response device, wherein the functional units and modules can be implemented in software, or can be implemented in general chips or specific chips. Part or all of the functional units and modules can be on the duty server, or part of them can also be on the technical support terminal 103, and the emergency response interaction is realized by cooperating with the duty server 102. The device specifically includes:

[0132] The first alarm information obtaining unit 301 is used to obtain and display the first alarm information of the fault.

[0133] The shared alarm information generating unit 302 is configured to generate shared alarm information according to the first alarm information.

[0134] The shared alarm information sending unit 303 is used to send the shared alarm information to the technical support terminal.

[0135] The second alarm information request receiving unit 304 is configured to receive a request for obtaining second alarm information sent by the technical support terminal.

[0136] The second alarm information obtaining unit 305 is configured to obtain the second alarm information according to the second alarm information obtaining request and the application authority of the fault.

[0137] The second alarm information sending unit 306 is configured to send the second alarm information to the technical support terminal.

[0138] The fault handling solution receiving unit 307 is configured to receive a fault handling solution generated by the technical support terminal according to the shared alarm information and the second alarm information.

[0139] The execution unit 308 is configured to execute the fault handling solution to resolve the fault.

[0140] Through the settings of the embodiments of this document, the key information of the first alarm information, the shared alarm information, and the key information of the second alarm information are combined, and the shared alarm information is displayed on the display interface to generate a fault handling plan corresponding to the fault, thereby reducing the steps for the on-duty personnel to display the fault to the business support terminal, reducing the time for fault handling, and comparing the permission information of the application responsible person with the application permission of the fault information to maximize the security of the application operation and fault repair process, and being able to solve the fault more accurately.

[0141] As an embodiment of this article, you can also refer to Figure 4 The figure shows a specific structural diagram of the visual on-duty emergency response interactive device of this embodiment. The first alarm information acquisition unit 301 is also used to display the first alarm information on the display interface after acquiring the first alarm information of the fault.

[0142] As an embodiment of this invention, the first alarm information obtaining unit 301 further includes:

[0143] The display module 3011 is used to centrally display the acquired first alarm information on a display interface according to a predetermined rule.

[0144] The shared alarm information generating unit 302 is used to determine the key information of the first alarm information and match the key information of the first alarm information in a preset scenario library before generating the shared alarm information.

[0145] As an embodiment of this invention, the shared alarm information generating unit 302 further includes:

[0146] A determination module 3021, used to identify and determine key information in the first alarm information;

[0147] The matching module 3022 is used to match the key information of the first alarm information in a preset scenario.

[0148] The fault handling solution receiving unit 307 is further configured to display the received fault handling solution on a display interface.

[0149] As an embodiment of this article, the fault handling solution receiving unit 307 further includes:

[0150] The fault handling solution display module 3071 is used to display the fault handling solution generated by the business support terminal on the display interface.

[0151] like Figure 5 The figure shows a flow chart of an automatic fault handling solution according to an embodiment of the present invention.

[0152] Step 501, determining key information of the first alarm information;

[0153] The first alarm information includes server information, alarm events, error information, application responsible person information, etc. Server information includes: server address, server name, server memory, server normal operation time, etc.; alarm events include: alarm IP, alarm start time, alarm end time, alarm number, alarm event name, alarm device, alarm business department, alarm business type, alarm danger level, etc.; error information includes: error start time, error content, error business department, error business type, etc.; application responsible person information includes: application person in charge ID, application person in charge department, application person in charge authority level, application person in charge on duty time, application person in charge contact address, etc.

[0154] In this step, the key information refers to the information with representative meanings in multiple fields of the first alarm information, including keywords, key words, key sentences, etc. The first alarm information contains a wide variety of information with complex content, and it is necessary to extract and determine the key information in the first alarm information in order to determine the fault and generate a corresponding fault handling solution.

[0155] In an exemplary embodiment of the present specification, the first alarm information is shown in the following table (see Table 1 below):

[0156] Main fields illustrate Example Application Short Name English name of the alarm application F-CCIS Application Chinese name The Chinese name of the alarm application Remote Banking Center Alarm IP Alarm server IP 84.XX.XX.XX Alarm start time Alarm start time YYYY-MM-DD HH:MM:SS Alarm end time Alarm end time YYYY-MM-DD HH:MM:SS Number of alarms Statistical alarm times 1 Alarm Type Type of alarm Unrecoverable / Unrecoverable Alarm details Alarm related content. Xxx Availability Support Manager Application support manager Zhang San Contact Details Contact phone 1XXXXXXXXX

[0157] Table 1

[0158] In this step, the emergency response system first pre-sets the key information that the system considers necessary. In this step, the key information can be manually adjusted and set in real time according to the actual business situation. Taking the banking system as an example, the emergency system pre-sets the key information as follows: alarm IP address, alarm details, alarm application, error application name, etc. Alternatively, the emergency system pre-sets the key information including: server IP address, alarm issuing device / software, etc.

[0159] Next, when an application fails, based on the generated first alarm information, the system identifies and determines the key information of the first alarm information from the first alarm information according to the preset. Among them, for each first alarm information, the key information in the alarm information is extracted and identified by methods such as keyword extraction, text recognition, and graphic image recognition. Taking banking business as an example, the system pre-sets the key information as "alarm application" and "alarm details". When a telephone banking application fails, the first alarm information displays a variety of information such as server information, alarm event information, and application responsible person information on the display interface. The system uses text recognition to identify and determine the key information of the first alarm information in the first alarm information as: alarm application "telephone banking" and alarm IP "192.12.168.22", which concisely and accurately expresses the key content of the first alarm information and accurately locates the server where the problem of the alarm application program occurs.

[0160] The key information of the first alarm information can be stored in a memory or a preset scenario library for application in subsequent steps.

[0161] Step 502, matching key information of the first alarm information in a preset scenario library;

[0162] In this step, based on the record of historical faults and the corresponding alarm information of the faults, the emergency handling system stores some faults with high frequency of occurrence and relatively simple and fixed fault handling solutions and their first alarm information in the preset scenario library. As described in step 502, the preset scenario library also stores key information preset by the system, so the preset scenario library stores at least one key information of at least one fault and the fault handling solution corresponding to the key information. When a fault occurs in the application, the emergency system matches the key information of the first alarm information determined in step 501 in the preset scenario library.

[0163] Taking banking business as an example, when an application fails, the key information in the first alarm information is determined to be "alarm application: telephone banking"; the preset scenario library stores the key information of the alarm information corresponding to the fault "availability disconnection": "alarm application" is "telephone banking", and "alarm IP is "192.12.168.22". Therefore, the key information of the first alarm information can match the key information of the "availability disconnection" fault in the preset scenario library.

[0164] Step 503: When the match succeeds, a fault handling solution for the fault is generated.

[0165] In this step, according to the key information of the first alarm information determined in step 501, the fault handling solution of the corresponding fault is matched in the preset scenario library. Taking banking business as an example, the preset scenario library stores the key information of the alarm information corresponding to the fault "availability disconnection": "alarm application" is "telephone banking", "alarm IP" is "192.12.168.22", and stores the fault handling solution corresponding to the fault "availability disconnection" "step 1cd / approot / abc sh stop.sh; step 2shstart.sh; step 3sqlplus sqlplus xxxx@XXXX; step 4update XX from XX where XXX" and so on. When the "availability disconnection" fault occurs in the actual application, the emergency system can match the key information "alarm application" and "alarm IP" of the first alarm information in the preset scenario library, and match it to the corresponding fault handling solution.

[0166] like Figure 6 Shown is a flow chart of a method for generating shared alarm information according to an embodiment of this invention.

[0167] Step 601, obtaining the full amount of server information, alarm events and error information in the first alarm information.

[0168] In this step, according to the records of historical alarm information, the alarm information of some faults has a low historical frequency and the faults are relatively rare, so the preset scenario library does not store the alarm information of this type of fault and the fault handling solution for the corresponding fault. The emergency response system cannot match the fault handling solution for the corresponding fault in the preset scenario library according to the key information of the first alarm information. Therefore, the system needs to obtain the full amount of information of the server information, alarm events and error information in the first alarm information, and obtain as much information as possible in the first alarm information.

[0169] Step 602: Obtain full or partial information of server information, alarm events, and error information in the first alarm information according to the common level corresponding to the fault.

[0170] In this step, the common level corresponding to the fault indicates the frequency of occurrence of the fault in the historical time, and the common level corresponding to the fault can also reflect the safety level and / or importance level corresponding to the fault. Among them, the emergency response system can stipulate that the fault with a high common level is a fault with a high frequency of occurrence in the historical time and a low difficulty in handling; the fault with a low common level is a fault with a low frequency of occurrence in the historical time and a high difficulty in handling.

[0171] Taking banking business failures as an example, the common level of the "telephone disconnection" failure is 5, indicating that the "telephone disconnection" failure occurs frequently in historical time, the failure is common, and the handling difficulty is small; while the common level of the "interface garbled characters" failure is 1, indicating that the "interface garbled characters" failure occurs less frequently in historical time, the failure is uncommon, and the handling difficulty is large.

[0172] For common faults with higher levels, it is necessary to obtain part of the full information in the first alarm information; for common faults with lower levels, it is difficult to handle, and the first alarm information may not be sufficient to solve the fault, so it is necessary to obtain the full information in the first alarm information. The common levels corresponding to the faults are represented by letters, numbers or words.

[0173] Step 603: Take a screenshot of the display interface of the full information, and use the screenshot image as the shared alarm information.

[0174] In this step, the full amount of information of the first alarm information can be displayed on one or more display interfaces, and stored in a storage device as a screenshot image as shared alarm information, so that the application responsible person can view the shared alarm information on the technical support terminal. The full amount of information can also be generated by shooting a video and capturing a fixed frame image and recording an alarm log. This embodiment does not limit the form of the full amount of information.

[0175] Step 604: Send the shared alarm information to a technical support terminal.

[0176] In this step, the duty server 102 obtains the address of the technical support terminal 103 according to the information of the application responsible person in the first alarm information, and sends the shared alarm information to the technical support terminal 103. Specifically, the first alarm information includes the information of the application responsible person, including: the application responsible person ID, the department to which the application responsible person belongs, the authority level of the application responsible person, the online time of the application responsible person, the contact address of the application responsible person, the corresponding terminal address of the application responsible person, etc. Among them, according to the corresponding terminal address of the application responsible person, the address of the technical support terminal to receive the shared alarm information is determined. The shared alarm information is displayed on the technical support terminal interface for the application responsible person to view.

[0177] like Figure 7 The figure shows a flow chart of obtaining the second alarm information according to an embodiment of this invention.

[0178] Step 701: receiving a request for obtaining second alarm information sent by a technical support terminal.

[0179] In the above steps, the emergency handling system cannot match the fault handling solution of the fault in the preset database according to the first alarm information, so upon receiving Figure 6 After receiving the shared alarm information in the, the technical support terminal 103 generates a second alarm information request, and sends a request for obtaining the second alarm information to the duty server 102. The second alarm information request includes the following demand information: permission information of the person in charge of the application (for example, the ID of the person in charge of the application, the job level of the person in charge of the application, the device access permission, the application access permission, etc.), fault information (for example, faulty application permission, faulty device, faulty network, faulty application, etc.), and the device and / or application requested to be accessed (for example, requesting to access the device and / or application that is mutually related to the device and / or application of the first alarm information, and requesting to access the device and / or application that is not related to the first alarm device and / or application).

[0180] The second alarm information request is input by the application responsible person from the technical support terminal 103 and sent by the technical support terminal to the duty server 102. The input of the application responsible person at the technical support terminal 103 includes but is not limited to: manually inputting instructions, voice inputting sentences, selecting corresponding buttons at the technical support terminal 103, etc.

[0181] Step 702: Acquire fault information according to the requirement information in the second alarm information request.

[0182] In this step, the demand information in the second alarm information request includes fault information, and the fault information is determined by the application responsible person at the technical support terminal 103. The fault information includes: one or any combination of fault application authority, fault occurrence address, fault occurrence type, fault device, fault network, fault application, other devices that may be related to the fault, other networks related to the fault, other applications related to the fault, etc.

[0183] The duty server 102 obtains the fault information determined by the application responsible person from the demand information in the second alarm information request.

[0184] Step 703: compare the permission information of the application responsible person in the second alarm information request with the application permission of the fault information.

[0185] In this step, by comparing the application authority of the fault information with the authority information of the application responsible person, it is determined whether the behavior of the application responsible person in issuing the second alarm information request is reasonable, so as to subsequently determine whether to obtain the second alarm information.

[0186] In this step, the application permissions of the fault information represent the security levels of multiple parties involved in the network, equipment, applications, etc. related to the fault, and the application permissions of the fault information are pre-set by the system. Among them, the application permissions of the fault are divided into levels. For example, the application permission security level of the fault device AD ​​is level 1; the application permission security level of the fault device EH is level 2; the application permission security level of the fault device IM is level 3, where levels 1, 2, and 3 represent the fault application permission levels from low to high, respectively. Alternatively, the application permission level of the fault application OQ is level 3; the application permission level of the fault application RT is level 4, etc. Among them, the application permissions of the fault information are Figure 6 The common levels corresponding to the faults are not the same.

[0187] Referring to step 701, the permission information of the person in charge of the application includes the ID of the person in charge of the application, the job level of the person in charge of the application, the device access rights, the application access rights, etc., and the permission information of the person in charge of the application is preset by the system. Among them, the job level and access rights of the person in charge of the application are distinguished by the divided levels. For example, the permission of the person in charge of application A is low level; the permission of the person in charge of application B is medium level; the permission of the person in charge of application C is high level. Alternatively, the permission of the person in charge of application A is level 1; the permission of the person in charge of application B is level 2; the permission of the person in charge of application C is level 3, where 1, 2, and 3 represent the permission levels from low to high respectively.

[0188] Among them, the application responsible person with a low authority level can only access the fault information involved in the fault of the low-level application authority and handle the fault, and the application responsible person with a high authority level can access the fault information involved in the fault of all application authorities and handle the fault. In this step, the permission information of the application responsible person and the application authority of the fault information can have other corresponding modes, which are not limited in this embodiment.

[0189] In the request for obtaining the second alarm information, by comparing the authority level of the application person in charge in the second alarm information request with the application authority of the fault information, it can be determined whether to obtain the second alarm information.

[0190] Step 704: Use the fault information that matches the authority of the application responsible person in the second alarm information request as the second alarm information.

[0191] By determining that the authority of the application person in charge meets the application authority of the fault information, the duty server 102 obtains the fault information that matches the authority of the application person in charge in the second alarm information request as the second alarm information. If the authority of the application person in charge does not meet the application authority of the fault information, this step is not performed, and the process returns to step 701 to obtain the second alarm information request again.

[0192] like Figure 8 The flowchart of the embodiment of this invention is a method for generating a fault handling solution according to the shared alarm information and the second alarm information, which can be run on the technical support terminal 103. The method specifically includes:

[0193] Step 801: Determine key information of the shared alarm information and the second alarm information.

[0194] The specific content of the key information for determining the shared alarm information and the second alarm information in this step can be found elsewhere in this article. Figure 5 Related description of step 501 in .

[0195] Step 802, matching the key information in a preset scene library;

[0196] The specific content of the key information for matching the shared alarm information and the second alarm information in the preset scenario in this step can be found elsewhere in this article. Figure 5 Related description of step 502 in .

[0197] Step 803: When the match is successful, a fault handling solution for the fault is generated.

[0198] The specific content of the key information for matching the shared alarm information and the second alarm information in the preset scenario in this step can be found elsewhere in this article. Figure 5 Related description of step 503 in .

[0199] When the match fails, the application responsible person inputs a manually set fault handling solution in the technical support terminal 103, and the technical support terminal sends it to the duty server 102. The application responsible person sends the fault handling solution to the duty server 102 in the technical support terminal 103 by manually inputting the fault handling solution instructions, voice inputting speech sentences, etc.

[0200] like Fig. 9The schematic diagram of the mechanism of a computer device provided in the embodiment of this article is shown. The computer device 902 may include one or more processors 904, such as one or more central processing units (CPUs), and each processing unit may implement one or more hardware threads. The computer device 902 may also include any memory 906, which is used to store any kind of information such as code, settings, data, etc. Non-restrictive, for example, the memory 906 may include any one or more combinations of the following: any type of RAM, any type of ROM, flash memory device, hard disk, optical disk, etc. More generally, any memory may use any technology to store information. Further, any memory may provide volatile or non-volatile retention of information. Further, any memory may represent a fixed or removable component of the computer device 902. In one case, when the processor 904 executes an associated instruction stored in any memory or a combination of memories, the computer device 902 may perform any operation of the associated instruction. The computer device 902 also includes one or more drive mechanisms 908 for interacting with any memory, such as a hard disk drive mechanism, an optical disk drive mechanism, etc.

[0201] The computer device 902 may also include an input / output module 910 (I / O) for receiving various inputs (via input devices 912) and for providing various outputs (via output devices 914). A specific output mechanism may include a presentation device 916 and an associated graphical user interface (GUI) 918. In other embodiments, the input / output module 910 (I / O), the input device 912, and the output device 914 may not be included, and the computer device 902 may be used as a computer device in a network. The computer device 902 may also include one or more network interfaces 920 for exchanging data with other devices via one or more communication links 922. One or more communication buses 924 couple the components described above together.

[0202] The communication link 922 may be implemented in any manner, for example, through a local area network, a wide area network (e.g., the Internet), a point-to-point connection, etc., or any combination thereof. The communication link 922 may include any combination of hardwired links, wireless links, routers, gateway functions, name servers, etc., governed by any protocol or combination of protocols.

[0203] In the embodiment of this paper, the duty server 102 and the technical support terminal 103 can be Fig. 9 The computer device.

[0204] Corresponds to Figure 1-Figure 2 and Figure 5-Figure 8The method in this article also provides a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, the steps of the above method are executed.

[0205] The embodiment of the present invention also provides a computer readable instruction, wherein when the processor executes the instruction, the program therein causes the processor to execute the following Figure 1-Figure 2 and Figure 5-Figure 8 The method shown.

[0206] It should be understood that in the various embodiments of this document, the size of the serial numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this document.

[0207] It should also be understood that in the embodiments of this article, the term "and / or" is only a description of the association relationship of the associated objects, indicating that three relationships may exist. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this article generally indicates that the associated objects before and after are in an "or" relationship.

[0208] Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of the two. In order to clearly illustrate the interchangeability of hardware and software, the composition and steps of each example have been generally described in terms of function in the above description. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this article.

[0209] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0210] In the several embodiments provided herein, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic, for example, the division of the units is only a logical function division, and there may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interfaces, devices or units, or can be electrical, mechanical or other forms of connection.

[0211] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the embodiments of this article.

[0212] In addition, each functional unit in each embodiment of this invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above integrated unit may be implemented in the form of hardware or in the form of software functional unit.

[0213] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this article is essentially or the part that contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions to enable a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of this article. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), disk or optical disk and other media that can store program codes.

[0214] Specific embodiments are used in this article to illustrate the principles and implementation methods of this article. The description of the above embodiments is only used to help understand the methods and core ideas of this article. At the same time, for general technicians in this field, according to the ideas of this article, there will be changes in the specific implementation methods and application scopes. In summary, the content of this specification should not be understood as a limitation on this article.

Claims

1. A visual on-duty emergency response interactive method, characterized in that: include: Obtaining and displaying first alarm information of the fault, wherein the first alarm information is alarm information related to the fault and includes at least: server information, alarm event, error information, and application responsible person information; Generating shared alarm information according to the first alarm information includes: obtaining full information of server information, alarm events and error information in the first alarm information; taking a screenshot of a display interface of the full information, and using the screenshot image as the shared alarm information; Sending the shared alarm information to a technical support terminal; Receiving a request for obtaining second alarm information sent by the technical support terminal; Acquiring the second alarm information according to the acquisition request for the second alarm information and the application authority of the fault includes: acquiring the fault information according to the demand information in the second alarm information request; comparing the authority information of the application responsible person in the second alarm information request with the application authority of the fault information; and using the fault information that matches the authority of the application responsible person in the second alarm information request as the second alarm information; Sending the second alarm information to the technical support terminal; Receiving the technical support terminal to generate a fault handling solution according to the shared alarm information and the second alarm information, including: determining, by the technical support terminal, key information of the shared alarm information and the second alarm information; matching the key information in a preset scenario library, and determining whether the match is successful, and when the match is successful, generating a fault handling solution for the fault, the key information including key information of the first alarm information and key information of the second alarm information; The fault handling solution is executed to resolve the fault.

2. The visual on-duty emergency response interactive method according to claim 1, characterized in that: The full amount of information of the server information includes server address, server name, and server network information; The full information of the alarm event includes the number, name, and danger level of the alarm event; The full amount of information of the error message includes the error start time, error duration, and specific content of the error.

3. The visual on-duty emergency response interactive method according to claim 2, characterized in that: The acquisition of the full amount of information of the server information, the alarm event and the error information in the first alarm information further includes: According to the common level corresponding to the fault, full or partial information of the server information, alarm event and error information in the first alarm information is obtained.

4. The visual on-duty emergency response interactive method according to claim 2, characterized in that: Sending the shared alarm information to the technical support terminal further includes: The address of the technical support terminal is queried according to the application responsible person information in the first alarm information, and the shared alarm information is sent to the technical support terminal.

5. The visual on-duty emergency response interactive method according to claim 1, characterized in that: Before generating shared alarm information according to the first alarm information, the method further includes: Determining key information of the first alarm information; Matching key information of the first alarm information in a preset scenario library; When the match is successful, a fault handling solution for the fault is generated; When the match fails, shared alarm information is generated according to the first alarm information.

6. The visual on-duty emergency response interactive method according to claim 1, characterized in that: The application authority of the fault includes: fault information involved in various faults, and each type of fault information has a corresponding security level.

7. The visual on-duty emergency response interactive method according to claim 1, characterized in that: The fault handling solution includes one or a combination of the following: repair, delete, restore, backup, stop running, and alarm.

8. A visual on-duty emergency response device, characterized in that: include: A first alarm information acquisition unit, used to acquire and display first alarm information of the fault, wherein the first alarm information is alarm information related to the fault and includes at least: server information, alarm events, error information, and application responsible person information; A shared alarm information generating unit, configured to generate shared alarm information according to the first alarm information, including: obtaining full information of server information, alarm events and error information in the first alarm information; taking a screenshot of a display interface of the full information, and using the screenshot image as the shared alarm information; A shared alarm information sending unit, used for sending the shared alarm information to a technical support terminal; A second alarm information request receiving unit, configured to receive a request for obtaining second alarm information sent by the technical support terminal; A second alarm information acquisition unit is used to acquire the second alarm information according to the second alarm information acquisition request and the application authority of the fault, including: acquiring fault information according to the demand information in the second alarm information request; comparing the authority information of the application responsible person in the second alarm information request with the application authority of the fault information; and using the fault information that matches the authority of the application responsible person in the second alarm information request as the second alarm information; A second alarm information sending unit, used for sending the second alarm information to the technical support terminal; A fault handling solution receiving unit, used to receive a fault handling solution generated by the technical support terminal according to the shared alarm information and the second alarm information, including: determining, by the technical support terminal, key information of the shared alarm information and the second alarm information; matching the key information in a preset scenario library, and determining whether the match is successful, and when the match is successful, generating a fault handling solution for the fault, the key information including key information of the first alarm information and key information of the second alarm information; An execution unit is used to execute the fault handling solution to solve the fault.

9. A computer device comprising a memory, a processor and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the computer program, the visual on-duty emergency response interaction method of any one of claims 1-7 is implemented.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the visual on-duty emergency response interaction method of any one of claims 1 to 7 is implemented.

Images