Abnormal operation analysis method and device, equipment and storage medium

Abstract

The invention provides an abnormal operation analysis method and device, equipment and a storage medium, which are used for solving the problem of relatively low analysis flexibility in an abnormal operation analysis process. The method at least comprises the following steps: presenting an application maintenance interface of an application program; wherein the application maintenance interface comprises an operation analysis identifier set for the to-be-analyzed object; in response to a first operation triggered for the operation analysis identifier, switching from the application maintenance interface to the operation analysis interface; wherein the operation analysis interface comprises a multimedia control and an abnormal identifier; the multimedia control includes: an operation process for playback in a first multimedia format; the operation process is a process of triggering each object operation when the to-be-analyzed object uses the target program; the abnormal identifier is at least used for marking the playback position of the abnormal operation in the object operations on the multimedia control. The analysis flexibility of the abnormal operation analysis process is improved through the operation process of multimedia format playback and marking the playback position of the abnormal operation.

Description

Technical Field

[0001] This application relates to the field of computer technology, and in particular to an abnormal operation analysis method, apparatus, device and storage medium. Background Technology

[0002] With the continuous development of technology, the application's maintenance end can perform data analysis on the log data generated by the application to identify abnormal operations triggered on the application.

[0003] For example, third-party mini-programs that rely on instant messaging applications include both the user end and the maintenance end. Each user can trigger object operations on the third-party mini-program through the user end to use the application functions provided by the third-party mini-program; the maintenance end can collect the corresponding log data generated by the triggered object operations during the operation of the third-party mini-program. Thus, the maintenance end can analyze the abnormal operations triggered by each user during the use of the third-party mini-program based on the log data.

[0004] In related technologies, the application's maintenance arm collects log data corresponding to object operations triggered by the application and stores the obtained log data in a database. Therefore, based on the log data stored in the database, abnormal operation analysis methods typically include:

[0005] The program maintenance end retrieves the stored log data from the database and arranges the retrieved log data in the order of the trigger time of the corresponding object operation in the data list interface for the maintenance object to view;

[0006] The maintenance object selects the log data corresponding to the object operation triggered by a certain object to be analyzed from the data list interface, and marks each selected data to be analyzed in the list presented in the data list interface.

[0007] When performing data analysis on each piece of data to be analyzed, the system enters a data analysis interface that only presents the data to be analyzed in a list format. The maintenance object performs a comprehensive analysis on each piece of data to be analyzed and marks the abnormal data that represents abnormal operations in each piece of data to be analyzed in the data analysis interface. The analyzed abnormal data is then stored in the database as a basis for subsequent maintenance of the application.

[0008] However, since there are many operation points in the application that can trigger object operations, the object to be analyzed may trigger a large number of object operations during the use of the application. As a result, when the maintenance object selects the data to be analyzed from the list presented in the data list interface, it is easy to have multiple selections or omissions, thereby reducing the accuracy of the selected data to be analyzed, affecting the maintenance effect of the application and the user experience of the application.

[0009] Furthermore, the application's maintenance end not only needs to wait for the maintenance object to select each piece of data to be analyzed, but also needs to wait for the maintenance object to analyze the data. This causes the maintenance end to consume a long time, waiting for the response to the operation triggered by the maintenance object, which reduces the efficiency of the abnormal operation analysis process and also affects the maintenance effect and user experience of the application.

[0010] It is evident that the analytical flexibility of the abnormal operation analysis process under the relevant technologies is relatively low. Summary of the Invention

[0011] This application provides an abnormal operation analysis method, apparatus, device, and storage medium to address the problem of low analytical flexibility in the abnormal operation analysis process.

[0012] Firstly, an abnormal operation analysis method is provided, including:

[0013] The application maintenance interface of the application is presented; wherein, the application maintenance interface includes: operation analysis identifiers set for the object to be analyzed;

[0014] In response to a first operation triggered by the operation analysis identifier, the application maintenance interface switches to the operation analysis interface; wherein, the operation analysis interface includes: a multimedia control and an exception identifier; the multimedia control includes: an operation process played back in a first multimedia format; the operation process is: the process of triggering various object operations when the object to be analyzed uses the target program; the exception identifier is used at least to: mark the playback position of the exception operation in each object operation on the multimedia control.

[0015] Secondly, an abnormal operation analysis device is provided, comprising:

[0016] Presentation module: used to present the application maintenance interface of the application; wherein, the application maintenance interface includes: operation analysis identifiers set for the object to be analyzed;

[0017] Switching module: used to switch from the application maintenance interface to the operation analysis interface in response to a first operation triggered by the operation analysis identifier; wherein, the operation analysis interface includes: a multimedia control and an exception identifier; the multimedia control includes: an operation process played back in a first multimedia format; the operation process is: the process of triggering various object operations when the object to be analyzed uses the target program; the exception identifier is used at least to: mark the playback position of the exception operation in each object operation on the multimedia control.

[0018] Optionally, when the first multimedia format includes a graph format, the multimedia control includes an operation process curve; the operation process curve includes: the change in the number of triggers of each object operation triggered during the operation within a unit time; the playback position is: the position of the trigger time of the abnormal operation mapped in the operation process curve.

[0019] Optionally, when the first multimedia format includes a video format, the multimedia control includes an operation process video; the operation process video includes: the changes in the interface content of each application interface presented by the application during the operation within a unit of time; the playback position is: the position of the abnormal operation trigger time mapped in the playback progress of the operation process video.

[0020] Optionally, the multimedia control further includes playback control options; the playback control options are used to control the operation process video to start or stop playback at any of the application interfaces.

[0021] Optionally, the presentation module is further configured to:

[0022] After switching from the application maintenance interface to the operation analysis interface, in response to the second operation triggered for the playback position, the operation analysis interface displays a brief description of the abnormal operation and a detailed analysis entry for the operation details of the abnormal operation; the data size of the operation description is smaller than the data size of the operation details.

[0023] Optionally, when multiple abnormal operations exist in each object operation, the abnormal identifier is used to: mark the playback position of one abnormal operation in each abnormal operation group on the multimedia control; the abnormal identifier is also used to: mark the playback position of other abnormal operations in the multiple abnormal operations besides the abnormal operations included in the abnormal operation group on the multimedia control; wherein, the abnormal operation group includes: at least two abnormal operations in the multiple abnormal operations whose positional distance between playback positions is less than a marking distance threshold.

[0024] Optionally, the switching module is further configured to:

[0025] After the details analysis entry that presents the operation details of the abnormal operation, in response to a third operation triggered by the details analysis entry, the operation analysis interface switches to the details analysis interface; wherein, the details analysis interface includes: operation details of at least one historical operation with the same exception type as the abnormal operation among the historical operations triggered by each user object of the application; each user object includes the object to be analyzed, each historical operation includes the operation of each object, and the at least one historical operation includes the abnormal operation.

[0026] Optionally, the operation summary includes the exception type of the abnormal operation; the operation details include at least: interface identifier and exception trigger location; wherein, the interface identifier represents: the abnormal application interface presented by the application when the abnormal operation is triggered; the exception trigger location is: the trigger location of the abnormal operation in the abnormal application interface.

[0027] Optionally, the exception identifier is further used to: mark the exception type of the exception operation in a second multimedia format at the playback location.

[0028] Optionally, the switching module is specifically used for:

[0029] In response to a first operation triggered by the operation analysis identifier, operation data for each object operation is obtained; wherein the operation data is used to describe the corresponding object operation from multiple reference dimensions.

[0030] Based on the operation data of each object operation, determine the operation association relationship between every two object operations;

[0031] When it is determined that among the object operations, there are at least two object operations whose operation association relationship satisfies the abnormal association condition, the at least two object operations are respectively regarded as the corresponding abnormal operations.

[0032] Based on the operation data obtained for each abnormal operation, the interface switches from the application maintenance interface to the operation analysis interface.

[0033] Optionally, when the multiple reference dimensions include type dimension, time dimension and space dimension, the operation data includes: the operation type, trigger time and operation trigger position of the corresponding object operation; wherein, the operation trigger position is: the trigger position of the corresponding object operation in the application interface presented by the application.

[0034] Optionally, the switching module is specifically used for:

[0035] For each pair of object operations, when the erroneous operation association condition among the abnormal association conditions is determined to be satisfied, the operation association relationship between the corresponding two object operations is determined as an erroneous operation relationship; wherein, the erroneous operation association condition includes:

[0036] Both object operations are of type "Create Touch Track";

[0037] The time interval between the trigger times of the two object operations is less than the erroneous operation interval threshold.

[0038] The positional distance between the respective trigger positions of the two object operations is greater than the erroneous operation distance threshold.

[0039] During the operation, the average number of target operations triggered per unit time reaches a preset density value; wherein, the target operation is: among the object operations, the operation type is the object operation of creating touch trajectory type.

[0040] Optionally, the switching module is specifically used for:

[0041] For each pair of object operations, if the operation data satisfies the invalid association condition among the abnormal association conditions, the operation association relationship between the corresponding two object operations is determined to be an invalid operation relationship; wherein, the invalid association condition includes:

[0042] The operation type of the first object operation in the two object operations is click type;

[0043] The time interval between the trigger times of the two object operations is less than the invalid interval threshold.

[0044] The operation type of the second object operation in the two object operations is not within the specified type range.

[0045] Optionally, the switching module is specifically used for:

[0046] For each pair of object operations, when the emotional association condition among the abnormal association conditions is satisfied, the operation association relationship between the corresponding two object operations is determined to be an emotional operation relationship; the emotional association condition includes:

[0047] In each object operation, the number of intermediate operations is greater than a preset threshold; wherein, the intermediate operation is: an object operation whose trigger time is within the time interval formed by the trigger times of the two object operations.

[0048] The time interval between the trigger times of each of the two intermediate operations is less than the emotional interval threshold.

[0049] The positional distance between the triggering positions of each of the two intermediate operations is less than the emotional distance threshold.

[0050] Optionally, the operation data may further include: the start time and end time of the operation process;

[0051] The switching module is specifically used for:

[0052] Obtain the position area data from the initial display data of the operation analysis interface; wherein, the position area data represents the position area of ​​the multimedia control on the operation analysis interface;

[0053] For each of the aforementioned abnormal operations, the following operations are performed respectively: based on the operation data of the abnormal operation, determine the trigger time of the abnormal operation as a relative time in the playback duration formed by the start and end times of the operation process; based on the location area data, determine the proportional relationship between the playback duration and the location area; based on the proportional relationship, map the relative time to the playback position in the location area;

[0054] Based on the initial display data and the replay positions of each abnormal operation, the operation analysis interface is generated, and the application maintenance interface is switched to the operation analysis interface.

[0055] Thirdly, a computer program product is provided, including a computer program that, when executed by a processor, implements the method described in the first aspect.

[0056] Fourthly, a computer device is provided, comprising:

[0057] Memory, used to store program instructions;

[0058] A processor is configured to invoke program instructions stored in the memory and execute the method described in the first aspect according to the obtained program instructions.

[0059] Fifthly, a computer-readable storage medium is provided, the computer-readable storage medium storing computer-executable instructions for causing a computer to perform the method as described in the first aspect.

[0060] In this embodiment, the application maintenance interface includes operation analysis identifiers set for the objects to be analyzed. Therefore, the operation analysis identifiers can be used to filter out the object operations triggered by the object during the use of the application with one click, without having to input the filter conditions first and then filter according to the filter conditions. This improves the efficiency of obtaining the operations of each object and also improves the flexibility of abnormal operation analysis.

[0061] Furthermore, by using operation analysis identifiers, we can conduct targeted analysis of the operations performed on each object of the object to be analyzed. This allows for a more human-centered analysis of the application from the user's perspective, which can improve the accuracy and flexibility of abnormal operation analysis to a certain extent.

[0062] Furthermore, after the first operation is triggered by the operation analysis identifier, the application maintenance interface switches to the operation analysis interface. In the operation analysis interface, the operation process of each object operation triggered by the object to be analyzed is replayed in a first multimedia format through multimedia controls. Thus, the operation process of the object to be analyzed can be presented vividly from a visual perspective. Compared with the method of using a list to quantify the operation process, the replayed operation process is more intuitive and interactive, improving the flexibility of abnormal operation analysis.

[0063] Furthermore, in the operation analysis interface, the playback position of the abnormal operation can be marked on the multimedia control through the exception identifier. This vividly and clearly presents where the abnormal operation occurred during the operation process, and can more comprehensively display the characteristics of the abnormal operation. This helps to assist in the subsequent optimization process of the application and improves the flexibility of abnormal operation analysis. Attached Figure Description

[0064] Figure 1A This application is one field of study for the abnormal operation analysis method provided in the embodiments of this application;

[0065] Figure 1B This is a schematic diagram illustrating the principle of anomaly analysis methods in related technologies.

[0066] Figure 1C This is one application scenario of the abnormal operation analysis method provided in the embodiments of this application;

[0067] Figure 2 A flowchart illustrating an abnormal operation analysis method provided in this application embodiment;

[0068] Figure 3A A schematic diagram illustrating the principle of the abnormal operation analysis method provided in this application embodiment;

[0069] Figure 3B A schematic diagram of the abnormal operation analysis method provided in the embodiments of this application. Figure 2 ;

[0070] Figure 3C A schematic diagram three illustrating the principle of the abnormal operation analysis method provided in this application embodiment;

[0071] Figure 4AA schematic diagram four illustrating the principle of the abnormal operation analysis method provided in this application embodiment;

[0072] Figure 4B A schematic diagram five illustrating the principle of the abnormal operation analysis method provided in this application embodiment;

[0073] Figure 4C A schematic diagram six illustrating the principle of the abnormal operation analysis method provided in this application embodiment;

[0074] Figure 4D A schematic diagram seven illustrating the principle of the abnormal operation analysis method provided in this application embodiment;

[0075] Figure 5A A schematic diagram of the abnormal operation analysis method provided in the embodiments of this application. Figure 8 ;

[0076] Figure 5B A schematic diagram of the abnormal operation analysis method provided in the embodiments of this application. Figure 9 ;

[0077] Figure 5C A schematic diagram of the principle of the abnormal operation analysis method provided in the embodiments of this application is shown in Figure 10.

[0078] Figure 5D 11. A schematic diagram illustrating the principle of the abnormal operation analysis method provided in this application embodiment;

[0079] Figure 5E A schematic diagram twelve illustrating the principle of the abnormal operation analysis method provided in this application embodiment;

[0080] Figure 6A A schematic diagram thirteen illustrating the principle of the abnormal operation analysis method provided in this application embodiment;

[0081] Figure 6B Fourteen is a schematic diagram illustrating the principle of the abnormal operation analysis method provided in the embodiments of this application;

[0082] Figure 7A A schematic diagram fifteen illustrating the principle of the abnormal operation analysis method provided in this application embodiment;

[0083] Figure 7B A schematic diagram sixteen illustrating the principle of the abnormal operation analysis method provided in the embodiments of this application;

[0084] Figure 8 A schematic diagram of the abnormal operation analysis device provided in this application embodiment;

[0085] Figure 9 A schematic diagram of the abnormal operation analysis device provided in the embodiments of this application. Figure 2 . Detailed Implementation

[0086] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings.

[0087] The following explanations of some terms used in the embodiments of this application are provided to facilitate understanding by those skilled in the art.

[0088] (1) Event sequence:

[0089] An event sequence is a sequence of events with timestamps. In this embodiment, object operations can be treated as events, representing interaction events, UI change events, etc., generated by the object to be analyzed in the application.

[0090] This application relates to Artificial Intelligence (AI) technology and cloud computing, such as common smart homes, smart wearable devices, virtual assistants, smart speakers, smart marketing, autonomous driving, smart transportation, smart maps, driver assistance systems, in-vehicle terminals, aircraft, digital twins, virtual humans, robots, AI-generated content (AIGC), conversational interaction, smart healthcare, smart customer service, and game AI. It is believed that with the development of technology, artificial intelligence technology and cloud computing will be applied in more fields and play an increasingly important role.

[0091] It should be noted that, in the embodiments of this application, the operations involving the acquisition of operational data require user permission or consent when applied to specific products or technologies, and the collection, use and processing of related data must comply with the relevant laws, regulations and standards of the relevant countries and regions.

[0092] In this application embodiment, the terms "module" or "unit" refer to a computer program or part of a computer program that has a predetermined function and works with other related parts to achieve a predetermined goal, and can be implemented wholly or partially using software, hardware (such as processing circuitry or memory), or a combination thereof. Similarly, a processor (or multiple processors or memory) can be used to implement one or more modules or units. Furthermore, each module or unit can be part of an overall module or unit that includes the functionality of that module or unit.

[0093] The application areas of the abnormal operation analysis method provided in the embodiments of this application will be briefly introduced below.

[0094] With the continuous development of technology, the application's maintenance end can perform data analysis on the log data generated by the application to identify abnormal operations triggered on the application.

[0095] For example, third-party mini-programs that rely on instant messaging applications include both the user end and the maintenance end. Each user can trigger object operations on the third-party mini-program through the user end to use the application functions provided by the third-party mini-program; the maintenance end can collect the corresponding log data generated by the triggered object operations during the operation of the third-party mini-program. Thus, the maintenance end can analyze the abnormal operations triggered by each user during the use of the third-party mini-program based on the log data.

[0096] Please refer to Figure 1A (1) refers to the application client of a third-party mini-program, through which users can purchase goods, view logistics, participate in promotional activities, and return or exchange goods. Please refer to [link / reference]. Figure 1A (2) is the program maintenance terminal of the third-party mini program. The maintenance object can log in to the program maintenance terminal through the maintenance account. The maintenance object can view the log data generated by each operation object using the third-party mini program during use, so as to analyze the abnormal operations triggered by each operation object during the use of the third-party mini program. The analysis results can be recorded through the program maintenance terminal.

[0097] Under related technologies, whenever the application's maintenance arm collects log data corresponding to object operations triggered by the application, it stores the obtained log data in the database. Please refer to... Figure 1B Based on the log data stored in the database, anomaly analysis methods typically include:

[0098] The program maintenance end retrieves the stored log data from the database and arranges the retrieved log data in the order of the trigger time of the corresponding object operation in the data list interface for the maintenance object to view;

[0099] The maintenance object selects the log data corresponding to the object operation triggered by a certain object to be analyzed from the data list interface, and marks each selected data to be analyzed in the list presented in the data list interface.

[0100] When performing data analysis on each piece of data to be analyzed, the system enters a data analysis interface that only presents the data to be analyzed in a list format. The maintenance object performs a comprehensive analysis on each piece of data to be analyzed and marks the abnormal data that represents abnormal operations in each piece of data to be analyzed in the data analysis interface. The analyzed abnormal data is then stored in the database as a basis for subsequent maintenance of the application.

[0101] However, since there are many operation points in the application that can trigger object operations, the object to be analyzed may trigger a large number of object operations during the use of the application. As a result, when the maintenance object selects the data to be analyzed from the list presented in the data list interface, it is easy to have multiple selections or omissions, thereby reducing the accuracy of the selected data to be analyzed, affecting the maintenance effect of the application and the user experience of the application.

[0102] Furthermore, the application's maintenance end not only needs to wait for the maintenance object to select each piece of data to be analyzed, but also needs to wait for the maintenance object to analyze the data. This causes the maintenance end to consume a long time, waiting for the response to the operation triggered by the maintenance object, which reduces the efficiency of the abnormal operation analysis process and also affects the maintenance effect and user experience of the application.

[0103] It is evident that the analytical flexibility of the abnormal operation analysis process under the relevant technologies is relatively low.

[0104] To address the issue of low analytical flexibility in the abnormal operation analysis process, this application proposes an abnormal operation analysis method. In this method, an application maintenance interface is presented, which includes operation analysis identifiers set for the object to be analyzed. In response to a first operation triggered by the operation analysis identifier, the application maintenance interface switches to the operation analysis interface. The operation analysis interface includes a multimedia control and an abnormal identifier. The multimedia control includes an operation process replayed in a first multimedia format. The operation process is the process by which the object to be analyzed triggers operations of various objects when using the target program. The abnormal identifier is used at least to mark the playback position of the abnormal operation in each object's operation on the multimedia control.

[0105] In this embodiment, the application maintenance interface includes operation analysis identifiers set for the objects to be analyzed. Therefore, the operation analysis identifiers can be used to filter out the object operations triggered by the object during the use of the application with one click, without having to input the filter conditions first and then filter according to the filter conditions. This improves the efficiency of obtaining the operations of each object and also improves the flexibility of abnormal operation analysis.

[0106] Furthermore, by using operation analysis identifiers, we can conduct targeted analysis of the operations performed on each object of the object to be analyzed. This allows for a more human-centered analysis of the application from the user's perspective, which can improve the accuracy and flexibility of abnormal operation analysis to a certain extent.

[0107] Furthermore, after the first operation is triggered by the operation analysis identifier, the application maintenance interface switches to the operation analysis interface. In the operation analysis interface, the operation process of each object operation triggered by the object to be analyzed is replayed in a first multimedia format through multimedia controls. Thus, the operation process of the object to be analyzed can be presented vividly from a visual perspective. Compared with the method of using a list to quantify the operation process, the replayed operation process is more intuitive and interactive, improving the flexibility of abnormal operation analysis.

[0108] Furthermore, in the operation analysis interface, the playback position of the abnormal operation can be marked on the multimedia control through the exception identifier. This vividly and clearly presents where the abnormal operation occurred during the operation process, and can more comprehensively display the characteristics of the abnormal operation. This helps to assist in the subsequent optimization process of the application, such as optimizing defects or design problems in the application, as well as lag problems in the network transmission process, and improves the flexibility of abnormal operation analysis.

[0109] The application scenarios of the abnormal operation analysis method provided in this application are described below.

[0110] Please refer to Figure 1C This diagram illustrates an application scenario of the abnormal operation analysis method provided in this application. The application scenario includes a server 101 and a client 102. The client 102 includes an application user 1021 and an application maintenance user 1022. The server 101 and the application user 1021 can communicate with each other, and the server 101 and the application maintenance user 1022 can also communicate with each other. The communication method can be wired, such as through a network cable or serial cable; or wireless, such as through Bluetooth or Wi-Fi. No specific limitation is imposed.

[0111] Application user 1021 generally refers to devices that can trigger object operations for applications, such as terminal devices, third-party applications that can be accessed by terminal devices, or web pages that can be accessed by terminal devices.

[0112] Application maintenance terminal 1022 generally refers to devices that can display application maintenance interfaces, such as terminal devices, third-party applications that can be accessed by terminal devices, or web pages that can be accessed by terminal devices.

[0113] The term "server" generally refers to a device that can provide display data for application user terminal 1021 or application maintenance terminal 1022 to present the interface, such as a terminal device or a server.

[0114] Terminal devices include, but are not limited to, mobile phones, computers, smart medical devices, smart home appliances, vehicle terminals, or aircraft. Servers include, but are not limited to, cloud servers, local servers, or associated third-party servers. Both client 101 and server 102 can use cloud computing to reduce the use of local computing resources; similarly, they can also use cloud storage to reduce the use of local storage resources.

[0115] As one embodiment, the server 101 and the client 102 can be the same device, or they can be different devices, or they can be different devices with some modules shared, etc., and there are no specific restrictions.

[0116] The following is based on Figure 1C Based on the application maintenance terminal 1022, the abnormal operation analysis method provided in this application embodiment will be described in detail. Please refer to... Figure 2 This is a flowchart illustrating an abnormal operation analysis method provided in an embodiment of this application.

[0117] S201 presents the application maintenance interface.

[0118] The application maintenance interface includes operation analysis identifiers set for the object to be analyzed. The object to be analyzed can refer to one or more operation objects of the application; this application uses one object to be analyzed as an example.

[0119] Operational analysis indicators can be icons; please refer to the following: Figure 3A (1) In this context, triggering the icon allows you to access the operation analysis interface.

[0120] Operation analysis identifiers can include an icon and the name text of the object to be analyzed. Please refer to [reference needed]. Figure 3A In (2), for example, if the name text is "Zhang San", the icon is a triangle located within the display area of ​​the name text and does not obscure the position of the name text. Then, the presence of an icon indicates that the operation analysis interface can be entered by triggering the operation analysis indicator; the absence of an icon indicates that the operation analysis interface cannot be entered by triggering the indicator.

[0121] Operation analysis identifiers can be text data; please refer to [reference needed]. Figure 3A(3) contains a trigger log of an object operation triggered by the object to be analyzed, “Zhang San”. By triggering any position in the trigger log, you can enter the operation analysis interface.

[0122] Operational analysis identifiers can be text data and icons; please refer to [reference needed]. Figure 3A In (4), in addition to the trigger log mentioned above, the triangle mentioned above is also included.

[0123] The application maintenance interface can contain trigger logs for each operation triggered by various objects in the application, arranged in a list format. These logs can include the operation object, the trigger time of the operation, the trigger location of the operation within the application's interface, the operation type, and the operation result, among other details. There are no specific limitations; please refer to [reference needed]. Figure 3B .

[0124] Operation types include various methods such as single click, double click, long press, swipe, gesture, voice, button press, and facial recognition, with no specific restrictions. Operation results include changes to the application interface, whether data is submitted to the server, whether the application is redirected, whether a file is downloaded, and whether other applications are launched in the background, with no specific restrictions.

[0125] The application maintenance interface can also contain only individual operation objects, with each operation object associated with the trigger logs of various object operations triggered during the use of the application. When an operation object is selected, the corresponding trigger logs can be retrieved. There are no specific limitations; please refer to [reference needed]. Figure 3C .

[0126] S202, in response to the first operation triggered by the operation analysis flag, the application maintenance interface is switched to the operation analysis interface.

[0127] The first operation can be a variety of actions, such as single click, double click, long press, swipe, gesture, voice, button, facial recognition, etc., with no specific restrictions.

[0128] The operation analysis interface includes multimedia controls and exception markers. The multimedia controls contain the operation process replayed in a first multimedia format. The operation process is the process triggered when the object to be analyzed uses the target program. The exception markers are used at least to mark the playback position of abnormal operations in each object's operation on the multimedia controls.

[0129] The first multimedia format can be one or more of the following: video, audio, animation, graphs, etc., without specific limitations. Video formats can present the operation process more realistically and intuitively. Compared to video formats, animation formats can reduce the amount of data processed when presenting the operation process, thus avoiding playback stuttering. Graph formats can present the quantified operation process in an intuitive way, improving the flexibility of abnormal operation analysis.

[0130] Audio formats, such as voice narration of the operation process, such as "After launching the shopping mini-program, you enter the shopping mini-program homepage. After 20 seconds, you click the search box on the homepage and enter the search keywords...", allow users to understand the operation process without looking at the screen. In addition, anomaly indicators can be added to the voice narration of the operation process using prompts or other methods. This allows users to know the playback position of abnormal operations without looking at the screen, improving the flexibility of anomaly analysis.

[0131] The following section uses graph and video formats, and their combinations, as examples to illustrate the process of switching from the application maintenance interface to the operation analysis interface.

[0132] The first multimedia format includes graph format:

[0133] The multimedia control includes an operation process curve. This curve shows the change in the number of object operations triggered during the operation, per unit of time.

[0134] For example, if the object being analyzed triggers two object operations on the application during the first unit of time in the operation process, then a point is recorded at the first position on the horizontal axis of the operation process curve, corresponding to the position with the vertical axis of 3. If the object triggers four object operations on the application during the second unit of time, then a point is recorded at the second position on the horizontal axis of the operation process curve, corresponding to the position with the vertical axis of 4. This process continues, connecting the recorded points to form the operation process curve. Please refer to [reference needed]. Figure 4A (1) is an operation process curve, the horizontal and vertical axes of which are not shown.

[0135] The playback location is the position of the abnormal operation trigger time mapped onto the operation process curve.

[0136] For example, if the trigger time of an abnormal operation corresponds to the 7th time unit on the operation process curve, then the position of the 7th time unit on the operation process curve can be marked as the replay position of the abnormal operation. There are various marking methods, such as using lines, patterns, text, colors, etc., and no restrictions are imposed here. Please refer to [reference needed]. Figure 4AIn (2), the playback position of the abnormal operation is marked with a vertical line.

[0137] Using graphs, the quantified operation process can be presented intuitively, improving the flexibility of anomaly analysis. Replaying the events clearly shows the relative trigger time of the anomaly within the entire process, as well as the operation status of each object before and after the anomaly, which aids in the analysis of anomalies.

[0138] The first multimedia format includes video formats:

[0139] The multimedia control includes a video of the operation process. This video includes the various application interfaces displayed during operation, and the changes in interface content within a unit of time.

[0140] For example, each unit of time in the operation process corresponds to a video frame. By recording the application interface displayed by the application within each unit of time using these video frames, an operation process video can be created, which can recreate the actual operation process. Please refer to [reference needed]. Figure 4B (1) is a playback screen of an operation process video during playback (each unit time is not shown in the figure). The object to be analyzed enters the application interface by triggering an object operation in the previous application interface. On the application interface, the mini program waits to trigger the next object operation. The playback progress below can show the relative presentation position of the application interface in the whole operation process.

[0141] The playback position is the location of the abnormal operation triggered at the point in time, mapped to the playback progress of the video during the operation.

[0142] For example, if the trigger time of an abnormal operation corresponds to the 7th time unit in the playback progress, then the 7th time unit in the playback progress can be marked as the replay position of the abnormal operation. There are various marking methods, such as using lines, patterns, text, colors, etc., and these are not limited here. Please refer to [reference needed]. Figure 4B In (2), an exclamation mark is used to mark the playback position of the abnormal operation.

[0143] Video format allows for a more realistic and intuitive presentation of the operation process, improving the flexibility of anomaly analysis. Playback positions clearly demonstrate the relative trigger time of the anomaly within the entire operation, as well as the application interface displayed when the anomaly is triggered, aiding in the analysis of anomalies.

[0144] As one embodiment, the multimedia control also includes playback control options. These playback control options allow control over whether the operation process video starts or stops playing from any application interface. This means that the playback control options can be used to control the operation process video to start or stop playing from any video frame, eliminating the need to play the operation process video from the beginning each time and improving the playback flexibility.

[0145] Please refer to Figure 4C Playback control options may include options to start, pause, and end playback of the operation process video; options to select the start position or playback interval for playback progress; options to fast forward or rewind for playback progress; options to select the playback size of the operation process video; options to select the playback speed of the operation process video, etc., with no specific limitations.

[0146] The first multimedia format includes video format and graph format:

[0147] Based on the preceding introduction, please refer to... Figure 4D (1) includes an operation process curve and a playback frame of the operation process video during playback. The unit time of the operation process curve corresponds to the unit time of the operation process video. If the trigger time of an abnormal operation corresponds to the 7th unit time in the operation process curve, then the trigger time of the abnormal operation also corresponds to the 7th unit time in the playback progress. Please refer to [reference needed]. Figure 4D (2) Mark the playback position of the abnormal operation with a vertical line on the operation process curve and mark the playback position of the abnormal operation with an exclamation mark on the playback progress.

[0148] As one example, after switching from the application maintenance interface to the operation analysis interface, further operations can be performed on the operation analysis interface to enrich its display effects and operability.

[0149] In response to the second operation triggered by the playback location, the operation analysis interface displays a brief overview of the abnormal operation and a detailed analysis entry point showing the operation details. The data size of the operation overview is smaller than that of the operation details.

[0150] The second operation is, for example, hovering over the playback position, such as placing the mouse cursor at the playback position; or it could be a single click, double click, long press, swipe, gesture, voice, key press, face recognition, etc., with no specific restrictions.

[0151] The operation summary provides a brief overview of the corresponding abnormal operation, while the operation details provide a comprehensive description. For example, the operation summary includes the exception type of the operation, while the operation details include the operation type, exception type, trigger time, and trigger location.

[0152] The second step allows for quick acquisition of key information about abnormal operations without requiring the user to navigate to a different screen, thus improving the efficiency of obtaining such information and enhancing the flexibility of abnormal operation analysis.

[0153] Please refer to Figure 5A When the mouse cursor is placed at the playback position, a display box is overlaid on the operation analysis interface. On the left side of the display box, the abnormal operation type is shown as "invalid click". On the right side of the display box, a details button is shown, which is the entry point for details analysis. You can view the operation details of the abnormal operation by triggering this details button.

[0154] As one embodiment, when there are multiple abnormal operations in each object operation, the abnormal identifier is used to: mark the playback position of one abnormal operation in each abnormal operation group on the multimedia control; the abnormal identifier is also used to: mark the playback position of other abnormal operations in the multiple abnormal operations besides the abnormal operations included in the abnormal operation group on the multimedia control; wherein, the abnormal operation group includes: at least two abnormal operations in the multiple abnormal operations whose positional distance between the playback positions is less than the marking distance threshold.

[0155] When multiple abnormal operations exist, if at least two abnormal operations are very close to each other in the playback position of the multimedia control, in order to avoid overlapping display of various abnormal markers, reduce visual clutter, improve the readability of abnormal markers, and improve the flexibility of abnormal operation analysis, at least two abnormal operations that are very close to each other in the playback position can be grouped into an abnormal operation. For this group of abnormal operations, only one abnormal marker is marked, and the marked position is the playback position of any one of the abnormal operations in the group.

[0156] Please refer to Figure 5B In (1), there are multiple abnormal operations whose playback positions are very close, and the positional distance between the playback positions is less than the mark distance threshold. If the abnormal identifier of each abnormal operation is presented in the multimedia control, it will cause visual clutter.

[0157] Please refer to Figure 5B In (2), for multiple abnormal operations where the playback positions are very close and the distance between the playback positions is less than the mark distance threshold, only one abnormal identifier is presented, which improves the flexibility of abnormal operation analysis.

[0158] As one example, after presenting the details analysis entry for abnormal operations, the details analysis entry can be operated to perform a more in-depth analysis of the abnormal operations.

[0159] In response to a third action triggered by the details analysis entry point, the system switches from the operation analysis interface to the details analysis interface. The details analysis interface contains: operation details of at least one historical operation with the same exception type as the abnormal operation, triggered by each user object of the application. Each user object contains the object to be analyzed, each historical operation contains the operation performed on that object, and at least one historical operation contains the abnormal operation.

[0160] The third operation can be, for example, a single click, double click, long press, swipe, gesture, voice, button press, or facial recognition, etc., with no specific restrictions.

[0161] Therefore, the detailed analysis interface can include not only the abnormal operations triggered by the object to be analyzed for this type of exception, but also the historical operations triggered by each user object for this type of exception. This allows for horizontal comparative analysis of this exception type, identifying the problem that caused the exception, and improving the flexibility of exception operation analysis.

[0162] Please refer to Figure 5C The object to be analyzed is object_1, and the exception type is invalid click. The analysis focuses on the operation details of multiple historical operations with the exception type "invalid click" triggered by various objects in the application, originating from objects_15 and_19. The detailed analysis interface will then display the operation details of these multiple historical operations with the exception type "invalid click," including exception operations_4,_5, and_6 triggered by object_1; historical operations_11 and_22 triggered by object_15; and exception operations_4 and_14 triggered by object_19.

[0163] As one embodiment, the operation summary may include the exception type of the abnormal operation, and may also include the number of abnormal operations in the aforementioned abnormal operation group, etc., without any specific limitations. The operation details may include: an interface identifier and the exception trigger location. The interface identifier represents the abnormal application interface presented by the application when the abnormal operation is triggered. The exception trigger location is the location where the abnormal operation is triggered within the abnormal application interface.

[0164] Without switching interfaces, users can quickly learn about the operation overview, such as the type of exception or the number of exceptions in the exception operation group. By looking at the operation details, users can gain a more comprehensive understanding of the exception operation and conduct accurate exception operation analysis, thus improving the flexibility of exception operation analysis.

[0165] Please refer to Figure 5D(1) is a schematic diagram of an operation. The abnormal type is invalid click type. The number of abnormal operations in the abnormal operation group is 3, which means that there are 3 abnormal operations of invalid click type near the playback position.

[0166] Please refer to Figure 5D In (2), there is a schematic diagram of operation details. Interface identifier_1 represents the application interface with interface identifier_1 in the application, such as the home page of the application. Abnormal trigger position_1 represents the trigger position of abnormal application interface with identifier_1, such as the rectangular area formed by coordinates (0,0), (0,4), (2,0), (2,4).

[0167] As one embodiment, the anomaly identifier is also used to mark the anomaly type of the abnormal operation at the playback location in a second multimedia format. The second multimedia format may include, for example, sound, animation, images, colors, etc., and is not specifically limited. By using the anomaly identifier in the second multimedia format, the anomaly type can be displayed more intuitively and vividly, facilitating a quick understanding of the anomaly type of the abnormal operation and improving the flexibility of anomaly operation analysis.

[0168] For example, please refer to Figure 5E If the exception type is invalid operation, an exclamation mark can be used as the exception identifier; if the exception type is erroneous operation, an "×" symbol can be used as the exception identifier; if the exception type is erroneous operation, an unhappy emoticon can be used as the exception identifier, and so on. There are no specific restrictions.

[0169] As one embodiment, in response to the first operation triggered by the operation analysis identifier, the process of switching from the application maintenance interface to the operation analysis interface also includes some data processing procedures, which are described below.

[0170] In response to the first action triggered by the operation analysis identifier, the operation data for each object operation is retrieved. This operation data describes the corresponding object operation from multiple reference dimensions. Operation data may include, for example, the trigger logs, log data, or operation details mentioned earlier, and is not specifically limited. These multiple reference dimensions may include, for example, type, time, space, and object dimensions, and are not specifically limited.

[0171] Based on the operation data of each object operation, the operation association relationship between every two object operations is determined. If at least two object operations are found to have an operation association relationship that satisfies the abnormal association condition, then these at least two object operations are identified as the corresponding abnormal operations. Based on the obtained operation data of each abnormal operation, the interface switches from the application maintenance interface to the operation analysis interface.

[0172] When the first operation is triggered, the abnormal operations that exist in the process of the object to be analyzed using the application can already be identified. When switching to the operation analysis interface, the operation data of each abnormal operation is already prepared. Therefore, through a single first operation, each abnormal operation can be viewed in the operation analysis interface. There is no need to manually filter the operation data of each object operation of the object to be analyzed first, and then summarize the operation data of each object operation of the object to be analyzed in one interface before analyzing the abnormal operations. This greatly reduces the difficulty of abnormal operation analysis, improves analysis efficiency, and thus improves analysis flexibility.

[0173] Please refer to Figure 6A This is a flowchart illustrating a data processing process, including a display device and a data processing device for a terminal equipment.

[0174] S601, the display device generates a data acquisition command in response to a first operation triggered by an operation analysis flag.

[0175] The data acquisition instruction is used to acquire operation data of various object operations triggered during the process of the object being analyzed using the application. These object operations can be those triggered during the most recent one or more times the object being analyzed opened and closed the application; they can also be those triggered during the process of the object being analyzed using the application since it was registered; or they can be those triggered during one or more times the object being analyzed opened and closed the application, as obtained by the data processing device authorized by the object being analyzed, etc., and there are no specific restrictions.

[0176] S602, the display device sends a data acquisition command to the data processing device, and the data processing device receives the data acquisition command sent by the display device.

[0177] S603, the data processing device retrieves the operation data of each object operation from the database based on the data acquisition instruction.

[0178] S604, the data processing device determines the operation association relationship between every two object operations based on the obtained operation data and according to the abnormal association conditions.

[0179] If the individual operation data of two object operations satisfy the abnormal association conditions, then the operation association between these two object operations is an abnormal relationship, such as a relationship of erroneous operation, invalid operation, or emotional operation. If the individual operation data of two object operations do not satisfy the abnormal association conditions, then the operation association between these two object operations is a normal relationship.

[0180] S605, the data processing device respectively treats at least two object operations with an abnormal operation relationship as corresponding abnormal operations and obtains the operation data of each abnormal operation.

[0181] S606, the data processing device sends the respective operation data of each abnormal operation to the display device, and the display device receives the respective operation data of each abnormal operation sent by the data processing device.

[0182] S607, the display device switches from the application maintenance interface to the operation analysis interface based on the operation data of each abnormal operation obtained.

[0183] As one embodiment, when multiple reference dimensions include type, time, and space, the operation data includes: the operation type, trigger time, and operation trigger location of the corresponding object operation. The operation trigger location is: the trigger location of the corresponding object operation in the application interface presented by the application.

[0184] Trigger locations can be, for example, the relative position of the selected option box in the application interface of the corresponding object operation; the coordinate sequence involved in the corresponding object operation; the display position of the face image in the application interface after face recognition; or the touch position in the application interface of a touch operation with the same operation result as the gesture after the corresponding object operation obtains a gesture, etc., without any specific restrictions.

[0185] By using multiple reference dimensions, abnormal operations can be presented more comprehensively, enabling a full analysis of abnormal operations and improving the accuracy and flexibility of abnormal operation analysis.

[0186] As one example, when determining the operational association between any two object operations, there are multiple abnormal association conditions. For example, each type of abnormality corresponds to one abnormal association condition, which allows for targeted and accurate identification of abnormal operations.

[0187] The following section will use three abnormal association conditions as examples to illustrate the concepts.

[0188] Error-related conditions:

[0189] For each pair of object operations on their respective operation data, when it is determined that the erroneous operation association condition in the abnormal association conditions is met, the operation association relationship between the corresponding two object operations is determined as an erroneous operation relationship; wherein, the erroneous operation association conditions include:

[0190] Both object operations are of type "Create Touch Track". The "Create Touch Track" type can be an operation initiated by a touch on the screen, indicating that the touch did not end immediately. If the touch continues for one or more units of time and the touch position changes, a touch track can be formed. Alternatively, if the touch continues for one or more units of time and the touch position remains unchanged, a touch track for a single point can be formed, i.e., a long press.

[0191] The time interval between the trigger times of the two object operations is less than the erroneous operation interval threshold.

[0192] The distance between the trigger positions of the two object operations is greater than the erroneous operation distance threshold.

[0193] During the operation, the average number of target operations triggered per unit time reaches a preset density value. The target operations are: among all object operations, those with the operation type of creating touch trajectory.

[0194] If two object operations are both touch-start operations, and the triggering times of these two object operations are close, and the triggering locations are far apart, and there are many object operations near these two object operations that are also touch-start operations, then these two object operations are considered to be erroneous operations, and these two object operations can be treated as abnormal operations respectively.

[0195] By using correlation conditions for erroneous operations, erroneous operations that occur during the use of the application can be accurately identified, thus improving the accuracy of anomaly analysis. This eliminates the need for maintenance personnel to manually analyze data, increasing the flexibility and efficiency of anomaly analysis.

[0196] For example, when long-pressing a certain position on the screen, the long press may be interrupted due to the hand movements or body position changes of the object being analyzed. In this case, the long press will be restarted, and at least two object operations recorded during the period from the last long press to the interruption will be abnormal operations of the erroneous type.

[0197] For example, the operation type, trigger time, and trigger location in the operation data can be denoted as (t, T, D). Then, the operation data for each object operation can be denoted as {(t1, T1, D1), (t2, T2, D2), ..., (t... n T n D n Let the touch trajectory type be "touchStart", the operation interval threshold be "TimeGapThreshold", and the operation distance threshold be "DisThreshold". Then, if there exist i and j such that Ti = T j = touchStart; and t j - t i < TimeGapThreshold, and |D j- D i | > DisThreshold, and for each object operation included in the preset time period, the operation type is the target operation of the create touch trajectory type, and the density within the preset time period exceeds the preset density value. Then, the object operations corresponding to (t i , T i , D i ) and (t j , T j , D j ) are respectively recorded as abnormal operations, and the abnormal type is the misoperation type.

[0198] Invalid association condition:

[0199] For the operation data of each of the two object operations, when it is determined that the invalid association condition in the abnormal association condition is satisfied, the operation association relationship between the corresponding two object operations is determined as an invalid operation relationship; where the invalid association condition includes:

[0200] The operation type of the first object operation in the two object operations is the click type. For example, the first object operation is a light touch, that is, the touch ends immediately after a short touch.

[0201] The time interval between the trigger times of the two object operations is less than the invalid interval threshold.

[0202] The operation type of the second object operation in the two object operations is not within the specified type range. The specified type range can include multiple operation types, such as the mutation type that can cause changes to the Document Object Model (DOM); it also includes the refresh type, denoted as the FullSnapshot type; it also includes the AppEvent type that triggers the system event of the application

[0203] If two object operations occur, one of which is a touch operation, and both operations are triggered close together, and the other object operation is not of type mutation, full snapshot, or appEvent, then after a touch operation, the application should wait for a response, not execute other object operations consecutively. Therefore, if other object operations are executed consecutively after a touch operation, and these operations are not of type mutation, full snapshot, or appEvent (which are within the reasonable range), then the other object operation can be considered invalid and recorded as an exception.

[0204] By associating invalid operations with certain conditions, invalid operations that occur during the use of the application can be accurately identified, thus improving the accuracy of anomaly analysis. This eliminates the need for maintenance personnel to manually analyze data, enhancing the flexibility and efficiency of anomaly analysis.

[0205] For example, the operation type, trigger time, and trigger location in the operation data can be denoted as (t, T, D). Then, the operation data for each object operation can be denoted as {(t1, T1, D1), (t2, T2, D2), ..., (t... n T n D n Given an invalid interval threshold of 500 milliseconds and a click type denoted as "tap", then, if there exists i such that T i =tap, and for all j, if there exists t j -t i <500ms, T j ≠mutation and T j ≠ Full Snapshot, and T j ≠AppEvent, then (t) can be used as an example. j T j D j The corresponding object operation is denoted as an exception operation, and the exception type is invalid operation type.

[0206] Emotional association conditions:

[0207] For each pair of object operations, when the emotional association condition among the abnormal association conditions is met, the operation association relationship between the corresponding two object operations is determined to be an emotional operation relationship; the emotional association condition includes:

[0208] Among the operations of each object, the number of intermediate operations is greater than the preset quantity threshold. The intermediate operation is: among the operations of each object, the object operation whose triggering time is within the time interval formed by the triggering times of the two object operations.

[0209] The time interval between the triggering times of every two intermediate operations is less than the emotion interval threshold.

[0210] The position distance between the triggering positions of every two intermediate operations is less than the emotion distance threshold.

[0211] Then, if there are more intermediate operations between two object operations, and the triggering times of these two object operations and each intermediate operation are close, and the triggering positions are close, it means that these two object operations and each intermediate operation are continuous and identical object operations triggered for the same position area. Then, it can be considered that these two object operations and each intermediate operation are emotional type abnormal operations, such as multiple angry clicks, etc.

[0212] Through the emotion operation association condition, it is possible to accurately judge the emotional operations that occur when the object to be analyzed uses the application program, so as to accurately identify abnormal operations and improve the accuracy of abnormal operation analysis. It does not require maintenance personnel to view data for manual analysis, which improves the flexibility and efficiency of abnormal operation analysis.

[0213] For example, the operation type, triggering time, and triggering position in the operation data can be recorded as (t, T, D). Then, the operation data of each object operation can be recorded as {(t1, T1, D1), (t2, T2, D2), …… (t n , T n , D n )} sequence. The preset quantity threshold is recorded as "CountThreshold", the emotion interval threshold is recorded as "TimeGapThreshold", and the emotion distance threshold is recorded as "DisThreshold".

[0214] Then, if there exist i and j such that j + i - 1 ≥ CountThreshold, and for all k, if i ≤ k < j, then t k+1 −t k < TimeGapThreshold, and |D j- D i | < DisThreshold, (t i , T i , D i ) to (t j , T j , D jEach operation data operation between the two operations is considered an emotional type of abnormal operation.

[0215] As one embodiment, the operation data also includes: the start time and end time of the operation process. This start time and end time can be the start and end of the playback duration of the operation process. For example, if the playback duration is 20 minutes, then the start time is 0 and the end time is 20 minutes. It can also be the actual trigger time of the operation process. For example, if the application starts at 8:26 am and exits at 12:03 pm, then the start time is 8:26 am and the end time is 12:03 pm, etc. There are no specific restrictions.

[0216] Therefore, when switching from the application maintenance interface to the operation analysis interface based on the operation data of each abnormal operation, the trigger time of the abnormal operation can be mapped to the playback position of the multimedia control first, and then the operation analysis interface can be presented. This allows the playback position of the abnormal operation to be directly displayed in the operation analysis interface without needing to calculate it at the trigger operation stage, thus improving the efficiency and flexibility of abnormal operation analysis.

[0217] Retrieve position area data from the initial display data of the operation analysis interface. Initial display data includes, for example, patterns, styles, and text displayed in the initial state of the operation analysis interface. Position area data represents the position area of ​​multimedia controls on the operation analysis interface. Position areas include, for example, sub-regions representing the position of the operation process video, the operation process curve, the playback progress, and the playback control options.

[0218] The following section describes the replay position mapping process for an abnormal operation. The replay position mapping process for other abnormal operations is similar and will not be repeated here.

[0219] Based on the operational data of the abnormal operation, determine the trigger time of the abnormal operation and its relative time within the playback duration formed by the start and end times of the operation. Based on the location region data, determine the proportional relationship between the playback duration and the location region. Based on the proportional relationship, map the relative time to the playback position within the location region.

[0220] For example, taking the mapping in the playback progress as an example, that is, the position sub-region of the playback progress mapped in the position region, then please refer to formula (1).

[0221]

[0222] Where, p i Indicates the location of the follow-up visit, t i p represents relative time. start This indicates the starting position of the playback progress in the operation analysis interface, pend This indicates the end position of the playback progress in the operation analysis interface, t start t represents the start time of the operation process. end This indicates the start and end times of the operation process.

[0223] After obtaining the replay location of each abnormal operation, an operation analysis interface can be generated based on the initial display data and the obtained replay location of each abnormal operation, and the application maintenance interface can be switched to the operation analysis interface.

[0224] Please refer to Figure 6B The operation data for each abnormal operation is arranged sequentially according to its trigger time. Each operation data includes the operation identifiers of the M abnormal operations that triggered sequentially during the operation of the object under analysis, denoted as abnormal operation_1, abnormal operation_2, ..., and abnormal operation_M; it also includes the start and end times of the application's lifecycle within which each abnormal operation was triggered, denoted as t. start _1 and t end _1; also includes the trigger time of each abnormal operation, denoted as trigger time_1, trigger time_2, ... and trigger time_M; also includes some other data that are not listed here.

[0225] For example, if the playback position is added to the playback progress bar, the position sub-region of the playback progress bar in the multimedia control is shown by the dashed box in the figure. Then, based on the initial display data of the operation analysis interface, the length data of the position sub-region of the playback progress bar can be obtained, including the coordinates of the start and end positions of the playback progress bar.

[0226] For example, the playback position can be added to the operation process curve, as shown by the dashed box in the multimedia control. Then, based on the initial display data of the operation analysis interface, the length data of the position sub-region of the operation process curve can be obtained, including the coordinates of the start and end positions of the curve.

[0227] Therefore, according to t start _1 and t end The ratio between the difference of _1 and the difference between the coordinates of the start and end positions of the playback progress is used to obtain a proportional relationship. Therefore, based on this proportional relationship, the trigger time of each abnormal operation can be determined in relation to t. start The difference of _1 is scaled proportionally to obtain the playback position of the abnormal operation in the playback progress (as shown by the black vertical lines in the figure).

[0228] The following is an example of the abnormal operation analysis method provided in the embodiments of this application.

[0229] Each object operation triggered by the object to be analyzed can be regarded as an operation event, and abnormal operations are abnormal events. The object operations can be arranged into an event sequence or event list according to the trigger time.

[0230] When the application maintenance interface is displayed, the system switches from the application maintenance interface to the operation analysis interface in response to a click action triggered by an operation analysis flag set for the object to be analyzed within the application maintenance interface. Please refer to [link / reference]. Figure 7A The operation analysis interface displays multimedia controls and exception indicators. The multimedia controls include a video player and an operation process curve. The video player plays the operation process video and displays playback control options. These options include a progress bar slider, start / pause playback options, a 5-second rewind option, a 5-second fast forward option, speed adjustment options, and full-screen playback options. The operation analysis interface also provides options to view operation details for each operation event of the object being analyzed, displaying the details of each event in a list format. Finally, the interface includes a help option to explain the function of each element.

[0231] The operation analysis interface displays the operation process curve, which also shows the replay positions of each abnormal event of the object to be analyzed. Icons representing the abnormal type and the number of abnormal events near the corresponding replay position indicate the replay location. Abnormal events near a replay position are only presented as a single replay position.

[0232] Merged presentation can be achieved in the following ways:

[0233] Each abnormal event of the object to be analyzed is assigned to an event list, denoted as `event`. A preset distance threshold, denoted as `merge_threshold`, is used as the merging condition.

[0234] Define a merge function. If, according to the trigger time, there are at least two adjacent exception events, and the positional distance between the replay positions of any two adjacent exception events is less than merge_threshold, then these at least two exception events can be considered as a group of exception events.

[0235] The merge function includes two parameters: `event` and `merge_threshold`. An empty list, `merged_events`, is initialized to store the merged exception event groups. An empty list, `current_group`, is also initialized to temporarily store the event group currently being built.

[0236] The merge function includes the following features: iterates through each exception event in the events list; checks if current_group is empty; if current_group is empty, adds the currently iterated exception event to current_group; if current_group is not empty, continues with the following steps: retrieves the last event in current_group; calculates the absolute value of the position difference between the currently iterated event events[i] and the last event last_event in current_group; if this difference is less than merge_threshold, adds the currently iterated event events[i] to current_group; if this difference is not less than merge_threshold, adds the current_group to merged_events and resets current_group to a new list containing only the currently iterated event events[i]; checks if there are any unprocessed exception events in current_group; if current_group is not empty, adds them to merged_events; and returns the final merged event list merged_events.

[0237] Based on the calculated playback position of the abnormal event or group of abnormal events, it is drawn onto the corresponding position of the multimedia control. Hover and click interactions can also be added. When hovered, detailed information about the abnormal event expands; when clicked, the log operation video can directly jump to the corresponding playback position.

[0238] Please refer to Figure 7B On the operation process curve presented in the operation analysis interface, when the mouse control is hovered over it, a vertical line can be displayed to indicate the position of the mouse control's hovering position on the operation process curve.

[0239] When the mouse hovers over a playback location, the system can display the name of the exception type represented by an icon, as well as the quantity unit of the aforementioned values, indicating how many times the exception type was triggered near that playback location. It can also display a detailed analysis entry, such as "View Similar Sessions," to access the detailed analysis interface and present the occurrence of exception events of this type in the usage of all users of the application, that is, to display the operation details of each user when exception events of this type occurred.

[0240] In this embodiment, each abnormal event can be displayed as a bubble on the playback progress, allowing users to intuitively see the time distribution of abnormal events during playback. Viewing detailed information about abnormal events by clicking or hovering the mouse over the bubble enhances the interactive experience. This method is intuitive and easy to understand, avoiding the length and complexity of traditional list displays.

[0241] By calculating the location of abnormal events and pinpointing them precisely to the playback progress, the system allows maintenance personnel to quickly locate the specific time point in time when the abnormal event occurred. After the maintenance personnel click on the bubble, the video of the operation process can directly jump to the corresponding playback position, thus achieving rapid location and efficient analysis. This precise location and efficient analysis feature improves the efficiency of maintenance personnel in handling abnormal events.

[0242] Based on the same inventive concept, embodiments of this application provide an abnormal operation analysis device capable of realizing the functions corresponding to the aforementioned abnormal operation analysis method. Please refer to... Figure 8 The device includes a presentation module 801 and a switching module 802, wherein:

[0243] Presentation module 801: used to present the application maintenance interface of the application; wherein, the application maintenance interface includes: operation analysis identifiers set for the object to be analyzed;

[0244] Switching module 802: Used to switch from the application maintenance interface to the operation analysis interface in response to the first operation triggered by the operation analysis identifier; wherein, the operation analysis interface includes: multimedia controls and exception identifiers; the multimedia controls include: the operation process played back in a first multimedia format; the operation process is: the process of triggering the operation of each object when the object to be analyzed uses the target program; the exception identifier is used at least to: mark the playback position of the exception operation in each object operation on the multimedia controls.

[0245] In one possible embodiment, when the first multimedia format includes a graph format, the multimedia control includes an operation process curve; the operation process curve includes: the change in the number of triggers of each object operation triggered during the operation within a unit of time; the playback position is: the position of the trigger time of the abnormal operation mapped in the operation process curve.

[0246] In one possible embodiment, when the first multimedia format includes a video format, the multimedia control includes an operation process video; the operation process video includes: the various application interfaces presented by the application during the operation, and the changes in the interface content within a unit of time; the playback position is: the trigger time of the abnormal operation, mapped to the position in the playback progress of the operation process video.

[0247] In one possible embodiment, the multimedia control further includes playback control options; the playback control options are used to control the operation process video to start or stop playback at any of the application interfaces.

[0248] In one possible embodiment, the presentation module 801 is further configured to:

[0249] After switching from the application maintenance interface to the operation analysis interface, in response to the second operation triggered by the playback location, the operation analysis interface displays a brief description of the abnormal operation and a detailed analysis entry for the operation details of the abnormal operation; the data size of the operation description is smaller than that of the operation details.

[0250] In one possible embodiment, when multiple abnormal operations exist in each object operation, the abnormal identifier is used to: mark the playback position of one abnormal operation in each abnormal operation group on the multimedia control; the abnormal identifier is also used to: mark the playback position of other abnormal operations in the multiple abnormal operations besides the abnormal operations included in the abnormal operation group on the multimedia control; wherein, the abnormal operation group includes: at least two abnormal operations in the multiple abnormal operations whose positional distance between the playback positions is less than the marking distance threshold.

[0251] In one possible embodiment, the switching module 802 is further configured to:

[0252] After the details analysis entry point for presenting the operation details of the abnormal operation is displayed, in response to the third operation triggered by the details analysis entry point, the operation analysis interface switches to the details analysis interface; wherein, the details analysis interface includes: operation details of at least one historical operation with the same exception type as the abnormal operation among the historical operations triggered by each user object of the application; each user object includes the object to be analyzed, each historical operation includes the operation of each object, and at least one historical operation includes the abnormal operation.

[0253] In one possible embodiment, the operation summary includes the exception type of the abnormal operation; the operation details include at least: an interface identifier and an exception trigger location; wherein, the interface identifier represents: the abnormal application interface presented by the application when the abnormal operation is triggered; the exception trigger location is: the trigger location of the abnormal operation in the abnormal application interface.

[0254] In one possible embodiment, the exception identifier is also used to: mark the exception type of the exception operation in a second multimedia format at the playback location.

[0255] In one possible embodiment, the switching module 802 is specifically used for:

[0256] In response to the first operation triggered by the operation analysis identifier, the operation data of each object operation is obtained; wherein, the operation data is used to describe the corresponding object operation from multiple reference dimensions.

[0257] Based on the operation data of each object operation, determine the operation association relationship between every two object operations;

[0258] When it is determined that there are at least two object operations in each object operation that satisfy the abnormal association condition, at least two object operations are respectively regarded as the corresponding abnormal operations.

[0259] Based on the operation data obtained for each abnormal operation, the interface switches from the application maintenance interface to the operation analysis interface.

[0260] In one possible embodiment, when multiple reference dimensions include type dimension, time dimension and space dimension, the operation data includes: the operation type, trigger time and operation trigger location of the corresponding object operation; wherein, the operation trigger location is: the trigger location of the corresponding object operation in the application interface presented by the application.

[0261] In one possible embodiment, the switching module 802 is specifically used for:

[0262] For each pair of object operations on their respective operation data, when it is determined that the erroneous operation association condition in the abnormal association conditions is met, the operation association relationship between the corresponding two object operations is determined as an erroneous operation relationship; wherein, the erroneous operation association conditions include:

[0263] Both object operations are of type "Create Touch Track";

[0264] The time interval between the trigger times of the two object operations is less than the erroneous operation interval threshold.

[0265] The distance between the trigger points of two object operations is greater than the erroneous operation distance threshold.

[0266] During the operation, the average number of target operations triggered per unit time reaches a preset density value; among them, the target operations are: among the object operations, the operation type is the object operation of creating touch trajectory.

[0267] In one possible embodiment, the switching module 802 is specifically used for:

[0268] For each pair of object operations on their respective operation data, if it is determined that the invalid association condition among the abnormal association conditions is met, the operation association relationship between the corresponding two object operations is determined to be an invalid operation relationship; where invalid association conditions include:

[0269] The operation type of the first object operation in the two object operations is click type;

[0270] The time interval between the trigger times of the two object operations is less than the invalid interval threshold;

[0271] The operation type of the second object operation in the two object operations is not within the specified type range.

[0272] In one possible embodiment, the switching module 802 is specifically used for:

[0273] For each pair of object operations, when the emotional association condition among the abnormal association conditions is met, the operation association relationship between the corresponding two object operations is determined to be an emotional operation relationship; the emotional association condition includes:

[0274] In each object operation, the number of intermediate operations exceeds a preset threshold; where intermediate operations are defined as: object operations whose trigger time falls within the time interval formed by the trigger times of the two object operations.

[0275] The time interval between the trigger times of each of the two intermediate operations is less than the emotional interval threshold.

[0276] The positional distance between the triggering positions of each two intermediate operations is less than the emotional distance threshold.

[0277] In one possible embodiment, the operation data further includes: the start time and end time of the operation process;

[0278] The switching module 802 is specifically used for:

[0279] Obtain the position area data from the initial display data of the operation analysis interface; whereby the position area data represents the position area of ​​the multimedia control on the operation analysis interface;

[0280] For each abnormal operation, perform the following operations: Based on the operation data of the abnormal operation, determine the trigger time of the abnormal operation and the relative time in the playback duration formed by the start and end times of the operation process; Based on the location area data, determine the proportional relationship between the playback duration and the location area; Based on the proportional relationship, map the relative time to the playback position in the location area.

[0281] Based on the initial displayed data and the replay positions of each abnormal operation, an operation analysis interface is generated, and the application maintenance interface is switched to the operation analysis interface.

[0282] Please refer to Figure 9 This is a computer device 900 provided in the embodiments of this application. The computer device 900 can, for example, be... Figure 1CThe client 101 or server 102 in the system. The current and historical versions of the data storage program and the application software corresponding to the data storage program can be installed on a computer device 900, which includes a processor 980 and a memory 920. In some embodiments, the computer device 900 may include a display unit 940, which includes a display panel 941 for displaying a user-interactive interface, etc.

[0283] In one possible embodiment, the display panel 941 may be configured in the form of a liquid crystal display (LCD) or an organic light-emitting diode (OLED).

[0284] The processor 980 is used to read a computer program and then execute the methods defined by the computer program. For example, the processor 980 reads a data storage program or file, thereby running the data storage program on the computer device 900 and displaying the corresponding interface on the display unit 940. The processor 980 may include one or more general-purpose processors, and may also include one or more DSPs (Digital Signal Processors) for performing related operations to implement the technical solutions provided in the embodiments of this application.

[0285] The memory 920 generally includes main memory and secondary storage. Main memory can be random access memory (RAM), read-only memory (ROM), and cache, etc. Secondary storage can be a hard disk, optical disk, USB flash drive, floppy disk, or magnetic tape drive, etc. The memory 920 is used to store computer programs and other data. The computer programs include applications corresponding to each client, and other data may include data generated after the operating system or applications are run, including system data (e.g., operating system configuration parameters) and user data. In this embodiment, the computer program is stored in the memory 920, and the processor 980 executes the computer program in the memory 920 to implement any of the methods described in the preceding figures.

[0286] The aforementioned display unit 940 is used to receive input digital information, character information, or contact touch operations / non-contact gestures, and to generate signal inputs related to user settings and function control of the computer device 900. Specifically, in this embodiment, the display unit 940 may include a display panel 941. The display panel 941, for example, is a touch screen, which can collect touch operations performed by the user on or near it (such as operations performed by the user using a finger, stylus, or any suitable object or accessory on or on the display panel 941), and drive corresponding connection devices according to a pre-set program.

[0287] In one possible embodiment, the display panel 941 may include two parts: a touch detection device and a touch controller. The touch detection device detects the player's touch position and the signal generated by the touch operation, and transmits the signal to the touch controller. The touch controller receives touch information from the touch detection device, converts it into touch point coordinates, and sends it to the processor 980. It can also receive and execute commands from the processor 980.

[0288] The display panel 941 can be implemented using various types such as resistive, capacitive, infrared, and surface acoustic wave. In addition to the display unit 940, in some embodiments, the computer device 900 may also include an input unit 930. The input unit 930 may include an image input device 931 and other input devices 932, wherein the other input devices may include, but are not limited to, one or more of the following: a physical keyboard, function keys (such as volume control buttons, power buttons, etc.), a trackball, a mouse, and a joystick.

[0289] In addition to the above, the computer device 900 may also include a power supply 990 for powering other modules, an audio circuit 960, a near-field communication module 970, and an RF circuit 910. The computer device 900 may also include one or more sensors 950, such as an accelerometer, a light sensor, and a pressure sensor. The audio circuit 960 specifically includes a speaker 961 and a microphone 962, for example, the computer device 900 can use the microphone 962 to collect the user's voice and perform corresponding operations.

[0290] As one embodiment, the number of processors 980 can be one or more, and the processors 980 and the memory 920 can be coupled together or relatively independent.

[0291] As one example, Figure 9 The processor 980 in the middle can be used to implement, for example Figure 8 The functions of the presentation module 801 and the switching module 802 in the middle.

[0292] As one example, Figure 9 The processor 980 in the text can be used to implement the functions of the server or terminal devices discussed above.

[0293] Those skilled in the art will understand that all or part of the steps of the above method embodiments can be implemented by a computer program. The aforementioned computer program can be stored in a computer-readable storage medium. When the computer program is executed, it performs the steps of the above method embodiments. The aforementioned storage medium includes various media capable of storing program code, such as mobile storage devices, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0294] Alternatively, if the integrated units of this invention are implemented as software functional modules and sold or used as independent products, they can also be stored in a computer-readable storage medium. Based on this understanding, the technical solutions of the embodiments of this invention, or the parts that contribute to the prior art, can be embodied in the form of software products, for example, through computer program products. These computer program products are stored in a storage medium and include computer programs used to cause a computer device to execute all or part of the methods described in the various embodiments of this invention. The aforementioned storage medium includes various media capable of storing program code, such as mobile storage devices, ROM, RAM, magnetic disks, or optical disks.

[0295] Obviously, those skilled in the art can make various modifications and variations to this application without departing from the spirit and scope of this application. Therefore, if such modifications and variations fall within the scope of the claims of this application and their equivalents, this application also intends to include such modifications and variations.

Claims

1. An abnormal operation analysis method, characterized in that, include: The application maintenance interface of the application is presented; wherein, the application maintenance interface includes: operation analysis identifiers set for the object to be analyzed; In response to a first operation triggered by the operation analysis identifier, the application maintenance interface switches to the operation analysis interface; wherein, the operation analysis interface includes: a multimedia control and an exception identifier; the multimedia control includes: an operation process played back in a first multimedia format; the operation process is: the process of triggering various object operations when the object to be analyzed uses the target program; the exception identifier is used at least to: mark the playback position of the exception operation in each object operation on the multimedia control.

2. The method according to claim 1, characterized in that, When the first multimedia format includes a graph format, the multimedia control includes an operation process curve; the operation process curve includes: the change in the number of triggers of each object operation triggered during the operation within a unit time; the playback position is: the position of the trigger time of the abnormal operation mapped in the operation process curve.

3. The method according to claim 1, characterized in that, When the first multimedia format includes a video format, the multimedia control includes an operation process video; the operation process video includes: the changes in the interface content of each application interface presented by the application during the operation within a unit of time; the playback position is: the position of the abnormal operation trigger time mapped in the playback progress of the operation process video.

4. The method according to claim 3, characterized in that, The multimedia control also includes playback control options; the playback control options are used to control the operation process video to start or stop playback at any of the application interfaces.

5. The method according to claim 1, characterized in that, After switching from the application maintenance interface to the operation analysis interface, the following is also included: In response to the second operation triggered at the playback location, the operation analysis interface displays a brief description of the abnormal operation and a detailed analysis entry for the operation details of the abnormal operation; the data size of the operation description is smaller than the data size of the operation details.

6. The method according to claim 5, characterized in that, When multiple abnormal operations exist in the operations of each object, the abnormal identifier is used to: mark the playback position of one abnormal operation in each abnormal operation group on the multimedia control; the abnormal identifier is also used to: mark the playback position of other abnormal operations in the multiple abnormal operations besides the abnormal operations included in the abnormal operation group on the multimedia control; wherein, the abnormal operation group includes: at least two abnormal operations in the multiple abnormal operations whose positional distance between playback positions is less than the marking distance threshold.

7. The method according to claim 5, characterized in that, Following the detailed analysis entry point that presents the operation details of the abnormal operation, the following is also included: In response to a third operation triggered by the details analysis entry, the operation analysis interface switches to the details analysis interface; wherein, the details analysis interface includes: operation details of at least one historical operation with the same exception type as the abnormal operation among the historical operations triggered by each user object of the application; each user object includes the object to be analyzed, each historical operation includes the operation of each object, and the at least one historical operation includes the abnormal operation.

8. The method according to claim 5, characterized in that, The operation summary includes the exception type of the abnormal operation; the operation details include at least: interface identifier and exception trigger location; wherein, the interface identifier represents: the abnormal application interface presented by the application when the abnormal operation is triggered; the exception trigger location is: the trigger location of the abnormal operation in the abnormal application interface.

9. The method according to claim 1, characterized in that, The anomaly identifier is also used to: mark the anomaly type of the abnormal operation in a second multimedia format at the playback location.

10. The method according to any one of claims 1 to 9, characterized in that, The first operation triggered in response to the operation analysis identifier, switching from the application maintenance interface to the operation analysis interface, includes: In response to a first operation triggered by the operation analysis identifier, operation data for each object operation is obtained; wherein the operation data is used to describe the corresponding object operation from multiple reference dimensions. Based on the operation data of each object operation, determine the operation association relationship between every two object operations; When it is determined that among the object operations, there are at least two object operations whose operation association relationship satisfies the abnormal association condition, the at least two object operations are respectively regarded as the corresponding abnormal operations. Based on the operation data obtained for each abnormal operation, the interface switches from the application maintenance interface to the operation analysis interface.

11. The method according to claim 10, characterized in that, When the multiple reference dimensions include type dimension, time dimension and space dimension, the operation data includes: the operation type, trigger time and operation trigger position of the corresponding object operation; wherein, the operation trigger position is: the trigger position of the corresponding object operation in the application interface presented by the application.

12. The method according to claim 11, characterized in that, The step of determining the operational association between every two object operations based on their respective operation data includes: For each pair of object operations, when the erroneous operation association condition among the abnormal association conditions is determined to be satisfied, the operation association relationship between the corresponding two object operations is determined as an erroneous operation relationship; wherein, the erroneous operation association condition includes: Both object operations are of type "Create Touch Track"; The time interval between the trigger times of the two object operations is less than the erroneous operation interval threshold. The positional distance between the respective trigger positions of the two object operations is greater than the erroneous operation distance threshold. During the operation, the average number of target operations triggered per unit time reaches a preset density value; wherein, the target operation is: among the object operations, the operation type is the object operation of creating touch trajectory type.

13. The method according to claim 11, characterized in that, The step of determining the operational association between every two object operations based on their respective operation data includes: For each pair of object operations, if the operation data satisfies the invalid association condition among the abnormal association conditions, the operation association relationship between the corresponding two object operations is determined to be an invalid operation relationship; wherein, the invalid association condition includes: The operation type of the first object operation in the two object operations is click type; The time interval between the trigger times of the two object operations is less than the invalid interval threshold. The operation type of the second object operation in the two object operations is not within the specified type range.

14. The method according to claim 11, characterized in that, The step of determining the operational association between every two object operations based on their respective operation data includes: For each pair of object operations, when the emotional association condition among the abnormal association conditions is satisfied, the operation association relationship between the corresponding two object operations is determined to be an emotional operation relationship; the emotional association condition includes: In each object operation, the number of intermediate operations is greater than a preset threshold; wherein, the intermediate operation is: an object operation whose trigger time is within the time interval formed by the trigger times of the two object operations. The time interval between the trigger times of each of the two intermediate operations is less than the emotional interval threshold. The positional distance between the triggering positions of each of the two intermediate operations is less than the emotional distance threshold.

15. The method according to claim 11, characterized in that, The operation data also includes: the start time and end time of the operation process; The process of switching from the application maintenance interface to the operation analysis interface based on the operation data obtained for each abnormal operation includes: Obtain the position area data from the initial display data of the operation analysis interface; wherein, the position area data represents the position area of ​​the multimedia control on the operation analysis interface; For each of the aforementioned abnormal operations, the following operations are performed respectively: based on the operation data of the abnormal operation, determine the trigger time of the abnormal operation as a relative time in the playback duration formed by the start and end times of the operation process; based on the location area data, determine the proportional relationship between the playback duration and the location area; based on the proportional relationship, map the relative time to the playback position in the location area; Based on the initial display data and the replay positions of each abnormal operation, the operation analysis interface is generated, and the application maintenance interface is switched to the operation analysis interface.

16. An abnormal operation analysis device, characterized in that, include: Presentation module: used to present the application maintenance interface of the application; wherein, the application maintenance interface includes: operation analysis identifiers set for the object to be analyzed; Switching module: used to switch from the application maintenance interface to the operation analysis interface in response to a first operation triggered by the operation analysis identifier; wherein, the operation analysis interface includes: a multimedia control and an exception identifier; the multimedia control includes: an operation process played back in a first multimedia format; the operation process is: the process of triggering various object operations when the object to be analyzed uses the target program; the exception identifier is used at least to: mark the playback position of the exception operation in each object operation on the multimedia control.

17. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the method as described in any one of claims 1 to 15.

18. A computer device, characterized in that, include: Memory, used to store program instructions; A processor is configured to invoke program instructions stored in the memory and execute the method as described in any one of claims 1 to 15 according to the obtained program instructions.

19. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions for causing a computer to perform the method as described in any one of claims 1 to 15.

Images