Abnormal response method, device and system

Abstract

The present application provides an exception response method, device, and system. In response to an exception, a client records the correspondence between exception data and a unique identifier, transmits the unique identifier to an exception tracking server, responds to a reproduction task request carrying the unique identifier, replays the exception data to obtain replay data, and transmits the replay data for locating the cause of the exception to the exception tracking server. It can be seen that the cause of the exception can be located based on the replay data, and because the playback is obtained based on the playback of the exception data, and the exception data includes not only the data of the exception, but also the data with a time interval with the occurrence of the exception within a preset range, that is, the data that can reflect the cause and effect of the exception, so it is helpful to increase the possibility of locating the cause of the exception.

Description

Technical Field

[0001] The present application relates to the field of electronic information, and in particular to an abnormal response method, device and system. Background Art

[0002] The application program used to implement the service running on the electronic device can be called a client. The client may encounter some unknown abnormal situations when providing service. Locating the cause of the abnormal situation is conducive to maintaining the stability of the service provided by the client.

[0003] Currently, after an abnormal situation occurs, the client usually reports the abnormal situation, but this abnormal response method of reporting the abnormal situation cannot provide sufficient support for locating the cause of the abnormal situation. Summary of the invention

[0004] The present application provides an abnormal response method, device and system, the purpose of which is to solve the problem of being unable to provide sufficient support for locating the cause of the abnormal situation.

[0005] In order to achieve the above objectives, this application provides the following technical solutions:

[0006] A first aspect of the present application provides an exception response method, which is applied to a client, and the method includes:

[0007] In response to an abnormality, recording a correspondence between abnormal data and a unique identifier, wherein the abnormal data includes data of the abnormal situation and causal data, wherein the causal data includes data within a preset range of a time interval with the occurrence of the abnormal situation;

[0008] transmitting the unique identifier to an anomaly tracking server;

[0009] In response to a recurrence task request carrying the unique identifier, replay based on the abnormal data to obtain replay data;

[0010] The playback data is transmitted to the abnormality tracking server, and the playback data is used to locate the cause of the abnormality.

[0011] Optionally, the replaying based on the abnormal data includes:

[0012] A service request carrying an identifier indicating playback is sent.

[0013] Optionally, the abnormal data includes:

[0014] The address of the service request, the method of the service request, the service request parameters, the service request header information, and the service request return content.

[0015] Optionally, before recording the correspondence between the abnormal data and the unique identifier, the method further includes:

[0016] A hash operation is performed on the abnormal data to obtain a hash value, where the hash value is the unique identifier.

[0017] Optionally, before replaying based on the abnormal data, the method further includes:

[0018] Confirm that the unique identifier has been recorded in the corresponding relationship stored locally.

[0019] A second aspect of the present application provides another abnormal response method, comprising:

[0020] In response to the occurrence of an exception, the client records the correspondence between the exception data and the unique identifier, wherein the exception data includes data of the exception and preceding and following causal data, wherein the preceding and following causal data includes data within a preset range of a time interval with the occurrence of the exception;

[0021] The client transmits the unique identifier to an anomaly tracking server;

[0022] The exception tracking server transmits the uniquely identified reproduction task request to the client based on the reproduction task configuration operation;

[0023] The client responds to the recurrence task request carrying the unique identifier and performs playback based on the abnormal data, wherein the playback includes: transmitting a service request carrying the identifier indicating playback to the service server;

[0024] The client transmits the playback data obtained by playback to the abnormality tracking server, and the playback data is used to locate the cause of the abnormality.

[0025] Optionally, also include:

[0026] The service server performs a first process based on the identifier indicating playback, where the first process is different from a second process, and the second process is a process for a service request that does not carry the identifier indicating playback.

[0027] A third aspect of the present application provides an abnormal response system, including:

[0028] Client, exception tracking server and business server;

[0029] The client is used to record the correspondence between the abnormal data and the unique identifier in response to the occurrence of the abnormality, and transmit the unique identifier to the abnormality tracking server, wherein the abnormal data includes data of the abnormal situation and before and after causal data, and the before and after causal data includes data with a time interval within a preset range with respect to the occurrence of the abnormal situation;

[0030] The exception tracking server is used to transmit the uniquely identified reproduction task request to the client based on the reproduction task configuration operation;

[0031] The client is also used to respond to the reproduction task request carrying the unique identifier, transmit a business request carrying an identifier representing playback to the business server, so as to play back based on the exception data, and transmit the playback data obtained by playback to the exception tracking server, wherein the playback data is used to locate the cause of the exception.

[0032] A fourth aspect of the present application provides an electronic device, including:

[0033] processor;

[0034] a memory for storing instructions executable by the processor;

[0035] The processor is configured to execute the instructions to implement the exception response method provided in the first aspect of the present application.

[0036] The fifth aspect of the present application provides a computer-readable storage medium. When the instructions in the computer-readable storage medium are executed by a processor of an electronic device, the electronic device is enabled to execute the exception response method provided in the first aspect or the second aspect of the present application.

[0037] The sixth aspect of the present application provides a computer program product, including a computer program / instruction, characterized in that when the computer program / instruction is executed by a processor, the exception response method provided in the first aspect or the second aspect of the present application is implemented.

[0038] The seventh aspect of the present application provides a client, comprising: a recording module, a transmission module, and a playback module. The recording module is used to record the correspondence between the abnormal data and the unique identifier in response to the occurrence of an exception, wherein the abnormal data includes data of the abnormal situation and causal data, and the causal data includes data within a preset range of the time interval with the occurrence of the abnormal situation. The transmission module is used to transmit the unique identifier to the exception tracking server. The playback module is used to respond to a reproduction task request carrying the unique identifier, and replay based on the abnormal data to obtain playback data.

[0039] The transmission module is also used to transmit the playback data to the abnormality tracking server, and the playback data is used to locate the cause of the abnormal situation.

[0040] Optionally, the playback module is specifically configured to send a service request carrying an identifier indicating playback to a service server.

[0041] Optionally, the client further includes: a calculation module, configured to perform a hash operation on the abnormal data to obtain a hash value serving as the unique identifier of the abnormal data before the recording module records the corresponding relationship between the abnormal data and the unique identifier.

[0042] Optionally, the client further includes: a confirmation module, configured to confirm that the unique identifier has been recorded in the corresponding relationship stored locally before the playback based on the abnormal data is performed.

[0043] The method, device, and system described in the present application are as follows: in response to an exception, the client records the correspondence between the exception data and the unique identifier, transmits the unique identifier to the exception tracking server, responds to a reproduction task request carrying the unique identifier, replays based on the exception data to obtain replay data, and transmits the replay data for locating the cause of the exception to the exception tracking server. It can be seen that the cause of the exception can be located based on the replay data, and because the playback is obtained based on the playback of the exception data, and the exception data includes not only the data of the exception, but also the data with a time interval with the occurrence of the exception within a preset range, that is, the data that can reflect the cause and effect of the exception, so it is beneficial to increase the possibility of locating the cause of the exception. BRIEF DESCRIPTION OF THE DRAWINGS

[0044] 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, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0045] Figure 1 This is a structural example diagram of the abnormal response system disclosed in the embodiment of the present application;

[0046] Figure 2 A flowchart of the abnormal response method disclosed in the embodiment of the present application;

[0047] Figure 3 This is an example diagram of the structure of the client disclosed in the embodiment of the present application. DETAILED DESCRIPTION

[0048] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0049] The terms used in the following embodiments are only for the purpose of describing specific embodiments and are not intended to be limiting of the present application. As used in the specification and appended claims of the present application, the singular expressions "one", "a kind", "said", "above", "the" and "this" are intended to also include expressions such as "one or more", unless there is a clear contrary indication in the context. It should also be understood that in the embodiments of the present application, "one or more" refers to one, two or more; "and / or" describes the association relationship of 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, where A and B can be singular or plural. The character " / " generally indicates that the objects associated before and after are in an "or" relationship.

[0050] References to "one embodiment" or "some embodiments" etc. described in this specification mean that a particular feature, structure or characteristic described in conjunction with the embodiment is included in one or more embodiments of the present application. Thus, the phrases "in one embodiment", "in some embodiments", "in some other embodiments", "in some other embodiments", etc. that appear at different places in this specification do not necessarily refer to the same embodiment, but mean "one or more but not all embodiments", unless otherwise specifically emphasized in other ways. The terms "including", "comprising", "having" and their variations all mean "including but not limited to", unless otherwise specifically emphasized in other ways.

[0051] The multiple involved in the embodiments of the present application means greater than or equal to two. It should be noted that in the description of the embodiments of the present application, the words "first", "second", etc. are only used for the purpose of distinguishing the description, and cannot be understood as indicating or implying relative importance, nor can they be understood as indicating or implying an order.

[0052] Taking the scenario of searching for videos on a video client as an example, the "abnormal situation", "abnormal point", "cause of locating the abnormal situation" and "abnormal response" described in the embodiments of the present application are defined and explained.

[0053] Assume that a user enters a keyword "XX" in the search bar of a video client. Normally, the client responds to the search instruction and displays videos searched based on the keyword "XX".

[0054] Assume that the following abnormal situation occurs on the client: the searched video is not displayed, but a white interface (which can be referred to as a "white screen") is displayed.

[0055] It is understandable that the display of a "white screen" is an abnormal situation occurring on the client, which can also be called an abnormal point.

[0056] After an abnormal situation occurs on the client, the backend connected to the client (or the client itself) needs to find the cause of the abnormal situation, that is, locate the cause of the abnormal situation. The processing of the abnormal situation, such as the client transmitting the abnormal point information to the backend to locate the cause, can be called an abnormal response.

[0057] During the research, the inventor found that the information based on the abnormal point alone is not enough to locate the cause of the abnormal situation. Furthermore, the inventor also found that the occurrence of the abnormal situation may be directly related to the user behavior, user environment, request sequence, etc. before the abnormal situation occurred on the client. Therefore, the preservation and playback (i.e., reproduction) of the operation of the client before and after the abnormal situation occurs is crucial to locate the cause of the abnormal situation.

[0058] The embodiments of the present application provide a method and device for abnormal response, the purpose of which is to save and reproduce the operation status of the client before and after the abnormal situation occurs, so as to improve the possibility of locating the cause of the abnormal situation.

[0059] Figure 1 The structure example diagram of the exception response system disclosed in the embodiment of the present application includes: a client 1, an exception tracking server 2 and a business server 3. In some implementations, the client 1 communicates with the exception tracking server 2 via the HTTP protocol.

[0060] It can be understood that the client 1 transmits a service request to the service server 3 based on the user's operation. In response to the service request, the service server 3 transmits service data to the client 1. The client 1 provides the service triggered by the user's operation based on the service data.

[0061] In the process of providing business services through collaboration between the client 1 and the business server 3, errors may occur in the process of transmitting business requests, and abnormal situations may occur such as business data returned by the business server 3 not meeting the requirements.

[0062] If an abnormal situation occurs in the process of providing services, the following will be triggered: Figure 2 The abnormal response method shown includes the following steps:

[0063] S01. Client 1 records abnormal data.

[0064] In this embodiment, abnormal data can be understood as data of abnormal situations, including but not limited to: abnormal business request, such as an error in the process of transmitting the business request, or the business data returned by the business server 3 does not meet the requirements, as well as display abnormality, abnormal client operation status such as no response, etc.

[0065] It is understandable that in order to reproduce the abnormal situation, the abnormal data includes not only the data of the abnormal situation, but also the data within a preset time interval with the occurrence of the abnormal situation (which may be referred to as before and after causal data or causal data), such as the data of the service request message within X minutes before and after the occurrence of the abnormal situation. X can be pre-configured.

[0066] In some implementations, taking a business request exception as an example, the exception data includes: the address of the business request, the method of the business request, the business request parameters, the business request header information (header), and the business request return content. The business request return content can be understood as the data returned by the business server in response to the business request. Taking the above search scenario as an example, the business request return content is the search result.

[0067] For example, to facilitate subsequent data comparison, the data is hashed to obtain a hash value, and the hash value and abnormal data are correspondingly stored in the client 1. It can be understood that based on the characteristics of the hash operation, the hash value calculated by the abnormal data is unique, that is, different abnormal data obtain different hash values.

[0068] In order to save resources of the client 1, in some implementations, the client 1 records abnormal data within a preset time range, such as 7*72 hours.

[0069] S02 , the client 1 transmits the hash value of the abnormal data, the abnormal time point and the identifier of the client 1 to the abnormality tracking server 2 .

[0070] The abnormal time point can be understood as the moment when the abnormal situation occurs.

[0071] In some implementations, there are multiple clients 1, and the identifier of the client 1 is unique.

[0072] As mentioned above, the client 1 transmits data to the exception tracking server 2 via the HTTP protocol. In some implementations, the client 1 transmits data via a pre-configured exception reporting interface between the client 1 and the exception tracking server 2, so that the backend personnel can view the exception data via the interface.

[0073] It is understandable that S01-S02 is the process of collecting and reporting abnormal data by the client 1. The back-end personnel can view the abnormal data on the abnormal tracking server 2. When the cause of the abnormal situation cannot be located based on the abnormal data, the back-end personnel configure a recurrence task on the abnormal tracking server 2. The configured recurrence task has a unique identifier, that is, the hash value of the abnormal data, thereby triggering the following steps.

[0074] S03, the client 1 receives the reproduction task request transmitted by the exception tracking server 2.

[0075] The reproduction task request includes an identifier of the reproduction task (a hash value of the abnormal data).

[0076] In some implementations, the client 1 receives the identification of the reproduction task through a pre-configured reproduction task delivery interface between the client 1 and the exception tracking server 2 .

[0077] In some implementations, the client 1 polls the exception tracking server 2 at a preset period to determine whether it has sent a recurrence task request.

[0078] S04. Client 1 determines that the task is its own task based on the identifier of the recurring task.

[0079] Because the hash value of the abnormal data is stored in S02, and the identifier of the recurrence task is the hash value, when the identifier of the recurrence task is consistent with the locally stored hash value, it is determined to be the own task.

[0080] S05. Client 1 reads the abnormal data corresponding to the identifier of the recurrence task.

[0081] It can be understood that the abnormal data corresponding to the identifier of the recurrence task is the abnormal data with the identifier of the recurrence task as a hash value.

[0082] S06. Client 1 plays back the abnormal data corresponding to the identifier of the recurrence task.

[0083] It can be understood that playback refers to reproducing the operations, instructions, and / or requests represented by the abnormal data in the order in which they occurred, and the specific method of playing back the abnormal data will not be described in detail here.

[0084] In some implementations, taking business request exceptions as an example, because playback is not a real business execution, an identifier indicating playback is added to the business request when the playback business request is transmitted, such as the header information X-replay: True. The business server 3 recognizes it as a business request in playback based on the identifier indicating playback, so it does not respond to shield the user's perception, so that playback is performed without the user's perception.

[0085] S07 . The client 1 transmits the playback data to the exception tracking server 2 .

[0086] Playback data can be understood as data generated, called, stored, and associated with the playback process.

[0087] In some implementations, after completing the playback, the client 1 packages the abnormal point information together and reports it to the abnormal tracking service through the abnormal recurrence troubleshooting interface (I03) for identification by the backend personnel. The backend personnel can locate the cause of the abnormal situation based on the playback data.

[0088] Taking the scenario of searching for videos on a video client as an example, suppose that after a user enters the keyword "XX" in the search bar of the video client and triggers the search, the video client displays a "white screen".

[0089] The video client captures the relevant signals showing the "white screen" and confirms that an abnormal situation has occurred. The video client records the abnormal data. In combination with this scenario, the video client collects the data of all business requests issued by the video client within X minutes, and calculates the data of each business request to obtain a hash value: 2E65E1689E2B698E967BA68C558D1B6A.

[0090] The video client reports the hash value: 2E65E1689E2B698E967BA68C558D1B6A, the abnormal time point: 2022-06-15 12:03:33, and the unique identifier of the video client (17e31cd65266087773404c70fed43d8e) to the abnormal tracking server.

[0091] The video client stores the hash value: 2E65E1689E2B698E967BA68C558D1B6A and the abnormal data locally.

[0092] The backend staff found the report in the exception tracking service background but could not reproduce the "white screen" situation, which resulted in the inability to locate the cause of the "white screen" and then issued a reproduction task.

[0093] The video client requests the exception tracking service to obtain information: Task 2E65E1689E2B698E967BA68C558D1B6A needs to be reproduced. The video client determines to execute the reproduction task based on the task ID 2E65E1689E2B698E967BA68C558D1B6A.

[0094] The video client reads the local abnormal data corresponding to 2E65E1689E2B698E967BA68C558D1B6A and reproduces the abnormal data. The reproduction includes at least the following steps: adding X-replay:True in the service request transmitted to the service server. The service server does not respond to the service request based on X-replay:True. It is understandable that although the service server did not respond to the service request, the service server has returned the search results when the real service request was made, and the search results are part of the abnormal data, so the playback data still includes the returned search results.

[0095] The video client records all the data of the reproduction request (i.e., the playback data), and packages all the data of the reproduction request with the abnormal point data and uploads them to the abnormality tracking service.

[0096] Backstage personnel obtained all the data of the reproduction request and analyzed and determined that unparseable characters appeared in a field of a certain data as the search result, causing the video client to display a "white screen".

[0097] In summary, the abnormal response method and system provided by the embodiment of the present application, after an abnormal situation occurs, the client stores the abnormal data and identification accordingly, and reports the identification of the abnormal data. The abnormal server can send a reproduction task to the client, and the client replays the abnormal situation based on the reproduction task and reports the playback data. Because the playback data includes data associated with the abnormal situation and data with a time interval within a preset range with the occurrence of the abnormal situation, the playback data can reflect the cause and effect of the abnormal situation, so it is helpful to locate the cause of the abnormal situation.

[0098] In addition, based on the identifier representing the playback, the client will automatically perform a reproduction test without the user being aware of it, greatly reducing the difficulty of locating the anomaly while minimizing disturbance to the user.

[0099] Figure 3 This is an example diagram of the structure of the client disclosed in the embodiment of the present application, including: a recording module, a transmission module, and a playback module.

[0100] The recording module is used to record the correspondence between abnormal data and the unique identifier in response to the occurrence of an abnormality, wherein the abnormal data includes data of the abnormal situation and causal data, wherein the causal data includes data within a preset range of time intervals with the occurrence of the abnormal situation.

[0101] The transmission module is used to transmit the unique identifier to the abnormality tracking server.

[0102] The playback module is used to respond to the reproduction task request carrying the unique identifier, and to play back based on the abnormal data to obtain playback data.

[0103] The transmission module is also used to transmit the playback data to the abnormality tracking server, and the playback data is used to locate the cause of the abnormal situation.

[0104] The playback module is specifically used to send a service request carrying an identifier indicating playback to the service server.

[0105] Furthermore, the client further includes: a calculation module, which is used to perform a hash operation on the abnormal data before the recording module records the corresponding relationship between the abnormal data and the unique identifier, so as to obtain a hash value as the unique identifier of the abnormal data.

[0106] Furthermore, the client further includes: a confirmation module, which is used to confirm that the unique identifier has been recorded in the corresponding relationship stored locally before the playback based on the abnormal data.

[0107] Figure 3 The client shown not only records the abnormal data, but also records the causal data of the abnormal data, so it can lay the foundation for locating the cause of the abnormal situation. In addition, an identifier indicating playback is added to the service request sent during the playback process, so that the service server can avoid making a real response, so that the user can achieve no feeling.

[0108] If the functions described in the method of the embodiment of the present application are implemented in the form of software functional units and sold or used as independent products, they can be stored in a storage medium readable by a computing device. Based on this understanding, the part of the embodiment of the present application that contributes to the prior art or the part of the technical solution can be embodied in the form of a software product, which is stored in a storage medium and includes several instructions to enable a computing device (which can be a personal computer, server, mobile computing device or network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present application. 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 code.

[0109] The various embodiments in this specification are described in a progressive manner, and each embodiment focuses on the differences from other embodiments. The same or similar parts between the various embodiments can be referenced to each other.

[0110] The above description of the disclosed embodiments enables those skilled in the art to implement or use the present application. Various modifications to these embodiments will be apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the present application. Therefore, the present application will not be limited to the embodiments shown herein, but will conform to the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. An abnormal response method, characterized in that: Applied to a client, the method comprises: In response to an abnormality, recording a correspondence between abnormal data and a unique identifier, wherein the abnormal data includes data of the abnormal situation and causal data, wherein the causal data includes data within a preset range of a time interval with the occurrence of the abnormal situation; Transmitting the unique identifier to an exception tracking server; so as to configure a reproduction task on the exception tracking server based on the unique identifier; receiving a recurrence task request transmitted by the exception tracking server, determining whether it is a task of the user based on a unique identifier included in the recurrence task request, and if it is determined to be a task of the user, responding to the recurrence task request carrying the unique identifier, replaying based on the exception data to obtain replay data; Transmitting the playback data to the abnormality tracking server, where the playback data is used to locate the cause of the abnormality; The replaying based on the abnormal data includes: A service request carrying an identifier indicating playback is sent, so that the service server identifies the service request as a playback service request based on the identifier indicating playback and does not respond to shield the user's perception.

2. The method according to claim 1, characterized in that The abnormal data includes: The address of the service request, the method of the service request, the service request parameters, the service request header information, and the service request return content.

3. The method according to claim 1, characterized in that Before recording the correspondence between the abnormal data and the unique identifier, the method further includes: A hash operation is performed on the abnormal data to obtain a hash value, where the hash value is the unique identifier.

4. The method according to claim 1, characterized in that: Before replaying based on the abnormal data, the method further includes: Confirm that the unique identifier has been recorded in the corresponding relationship stored locally.

5. An abnormal response method, characterized in that: include: In response to the occurrence of an exception, the client records the correspondence between the exception data and the unique identifier, wherein the exception data includes data of the exception and preceding and following causal data, wherein the preceding and following causal data includes data within a preset range of a time interval with the occurrence of the exception; The client transmits the unique identifier to an anomaly tracking server; The exception tracking server transmits the uniquely identified reproduction task request to the client based on the reproduction task configuration operation; The client receives the recurrence task request transmitted by the exception tracking server, determines whether it is its own task based on the unique identifier included in the recurrence task request, and if it is determined to be its own task, responds to the recurrence task request carrying the unique identifier and replays based on the exception data, wherein the replay includes: transmitting a business request carrying an identifier indicating replay to a business server; The client transmits the playback data obtained by playback to the abnormality tracking server, where the playback data is used to locate the cause of the abnormality; Among them, it also includes: The business server performs a first process based on the identifier indicating playback, the first process is different from a second process, the second process is a process for a business request that does not carry the identifier indicating playback, and the first process can shield the user's perception.

6. An abnormal response system, characterized in that: include: Client, exception tracking server and business server; The client is used to record the correspondence between the abnormal data and the unique identifier in response to the occurrence of the abnormality, and transmit the unique identifier to the abnormality tracking server, wherein the abnormal data includes data of the abnormal situation and before and after causal data, and the before and after causal data includes data with a time interval within a preset range with respect to the occurrence of the abnormal situation; The exception tracking server is used to transmit the uniquely identified reproduction task request to the client based on the reproduction task configuration operation; The client is also used to receive a recurrence task request transmitted by the exception tracking server, and determine whether it is its own task based on the unique identifier included in the recurrence task request. If it is determined to be its own task, the client transmits a business request carrying an identifier representing playback to the business server in response to the recurrence task request carrying the unique identifier, so as to perform playback based on the exception data, so that the business server recognizes it as a business request in playback based on the identifier representing playback, does not respond to shield the user's perception, and transmits playback data obtained through playback to the exception tracking server, where the playback data is used to locate the cause of the exception.

7. An electronic device, characterized in that: include: processor; a memory for storing instructions executable by the processor; The processor is configured to execute the instructions to implement the exception response method according to any one of claims 1 to 5. 8 . A computer-readable storage medium, when instructions in the computer-readable storage medium are executed by a processor of an electronic device, the electronic device is enabled to execute the abnormal response method according to any one of claims 1 to 5.

Images