Operation recording method, playback method, device, computer device and storage medium

Abstract

The present disclosure provides an operation recording method, a playback method, a device, a computer device and a storage medium, wherein the operation recording method comprises: in response to a recording trigger operation, obtaining operation information corresponding to each target operation executed by different processing processes, the operation information comprising timestamp information and processing process identifiers; wherein the processing process identifier is used to determine a first operation type of the target operation, the first operation type comprising a synchronous execution operation and an asynchronous execution operation; and storing the timestamp information and the processing process identifier of the target operation as a target recording result of the target operation.

Description

Technical Field

[0001] This disclosure relates to the field of computer technology, and more specifically, to an operation recording method, playback method, apparatus, computer device, and storage medium. Background Technology

[0002] When using a terminal device, users can use the device's operation recording function to record their actions for practical needs such as page browsing guidance and page function instruction, in order to meet different user requirements.

[0003] In related technologies, when using the operation recording function of a terminal device to record a user's operation, only basic information such as the duration of each operation is often recorded. However, due to the different processing performance of different devices, when playing back the user's operation on different devices, the response time of different operations may vary due to device performance and other reasons. Therefore, playback abnormalities may occur, which in turn affects the user experience. Summary of the Invention

[0004] This disclosure provides at least one operation recording method, playback method, apparatus, computer device, and storage medium.

[0005] In a first aspect, embodiments of this disclosure provide an operation recording method, including:

[0006] In response to a recording trigger operation, operation information corresponding to each target operation executed by different processing processes is obtained. The operation information includes timestamp information and processing process identifier. The processing process identifier is used to determine a first operation type of the target operation, which includes synchronous execution operation and asynchronous execution operation.

[0007] The timestamp information of the target operation and the process identifier are stored as the target recording result of the target operation.

[0008] In one possible implementation, the timestamp information corresponding to each target operation includes timestamp information of multiple operation steps constituting each target operation;

[0009] The step of storing the timestamp information of the target operation and the processing process identifier as the target recording result of the target operation includes:

[0010] Based on the timestamp information corresponding to each operation step, a second operation type for the target operation corresponding to the operation step is determined; wherein, the second operation type is used to characterize the interaction method between the user and the terminal device;

[0011] The second operation type, timestamp information, and processing process identifier of the target operation are stored as the target recording result of the target operation.

[0012] In one possible implementation, the second operation type of the target operation includes a long press operation;

[0013] The step of determining the second operation type of the target operation corresponding to each operation step based on the timestamp information corresponding to each operation step includes:

[0014] If the time interval between the start trigger operation and the end trigger operation at the first target location is detected to meet the first preset requirement, the second operation type of the currently recorded target operation is determined to be a long press operation.

[0015] In one possible implementation, the second operation type of the target operation includes multi-finger operation;

[0016] The step of determining the second operation type of the target operation corresponding to each operation step based on the timestamp information corresponding to each operation step includes:

[0017] If the time interval between trigger operations at multiple second target locations is found to meet the second preset requirement, the second operation type of the currently recorded target operation is determined to be a multi-finger operation.

[0018] In one possible implementation, the method further includes determining a third operation type corresponding to the target operation; the third operation type includes a floating window trigger operation and a normal page trigger operation;

[0019] The step of storing the timestamp information of the target operation and the processing process identifier as the target recording result of the target operation includes:

[0020] The third operation type, timestamp information, and processing process identifier of the target operation are stored as the target recording result of the target operation.

[0021] In one possible implementation, the method further includes: after detecting an operation step for the target floating window, adding operation information of the operation step for the target floating window to a preset proxy floating window, wherein the preset proxy floating window has a higher level than the target floating window.

[0022] The method further includes determining a third operation type corresponding to the target operation according to the following method:

[0023] The third operation type corresponding to the target operation obtained from the preset proxy floating window is determined as the floating window trigger operation; and,

[0024] The third operation type corresponding to the target operation obtained from the page is determined as the ordinary page-triggered operation.

[0025] In one possible implementation, the target recording result corresponding to the target operation also includes the operation result corresponding to the target operation;

[0026] The step of storing the timestamp information of the target operation and the processing process identifier as the target recording result of the target operation includes:

[0027] Obtain the operation result corresponding to the target operation;

[0028] The operation result, timestamp information, and processing process identifier of the target operation are stored as the target recording result of the target operation.

[0029] Secondly, this disclosure also provides an operation playback method, including:

[0030] Obtain a target recording result determined based on any of the operation recording methods described in the first aspect; wherein the target recording result contains operation information corresponding to the target operation, and the operation information includes timestamp information and a processing process identifier for executing the target operation;

[0031] Based on the processing process identifier, a first operation type is determined for each target operation; wherein, the first operation type includes synchronous execution operations and asynchronous execution operations;

[0032] Based on the timestamp information corresponding to the target operation and the first operation type, the target operation is replayed.

[0033] In one possible implementation, the timestamp information corresponding to each target operation includes timestamp information of multiple operation steps constituting each target operation;

[0034] The step of replaying the target operation based on the timestamp information corresponding to the target operation and the first operation type includes:

[0035] Based on the timestamp information of each operation step corresponding to the asynchronous and synchronous execution operations, the execution order of each operation step is determined.

[0036] The target operation is replayed according to the execution order of each operation step corresponding to the asynchronous and synchronous execution operations, and the operation result of the asynchronous execution operation.

[0037] Thirdly, embodiments of this disclosure also provide an operation recording device, including:

[0038] The first acquisition module is configured to, in response to a recording trigger operation, acquire operation information corresponding to each target operation executed by different processing processes, wherein the operation information includes timestamp information and processing process identifier; wherein the processing process identifier is used to determine a first operation type of the target operation, the first operation type including synchronous execution operation and asynchronous execution operation;

[0039] The storage module is used to store the timestamp information of the target operation and the processing process identifier as the target recording result of the target operation.

[0040] In one possible implementation, the timestamp information corresponding to each target operation includes timestamp information of multiple operation steps constituting each target operation;

[0041] The storage module, when storing the timestamp information of the target operation and the processing process identifier as the target recording result of the target operation, is used for:

[0042] Based on the timestamp information corresponding to each operation step, a second operation type for the target operation corresponding to the operation step is determined; wherein, the second operation type is used to characterize the interaction method between the user and the terminal device;

[0043] The second operation type, timestamp information, and processing process identifier of the target operation are stored as the target recording result of the target operation.

[0044] In one possible implementation, the second operation type of the target operation includes a long press operation;

[0045] The storage module, when determining the second operation type of the target operation corresponding to each operation step based on the timestamp information corresponding to each operation step, is used for:

[0046] If the time interval between the start trigger operation and the end trigger operation at the first target location is detected to meet the first preset requirement, the second operation type of the currently recorded target operation is determined to be a long press operation.

[0047] In one possible implementation, the second operation type of the target operation includes multi-finger operation;

[0048] The storage module, when determining the second operation type of the target operation corresponding to each operation step based on the timestamp information corresponding to each operation step, is used for:

[0049] If the time interval between trigger operations at multiple second target locations is found to meet the second preset requirement, the second operation type of the currently recorded target operation is determined to be a multi-finger operation.

[0050] In one possible implementation, the storage module is further configured to determine a third operation type corresponding to the target operation; the third operation type includes a floating window trigger operation and a normal page trigger operation;

[0051] The storage module, when storing the timestamp information of the target operation and the processing process identifier as the target recording result of the target operation, is used for:

[0052] The third operation type, timestamp information, and processing process identifier of the target operation are stored as the target recording result of the target operation.

[0053] In one possible implementation, the storage module is further configured to: after detecting an operation step for the target floating window, add the operation information of the operation step for the target floating window to a preset proxy floating window, wherein the preset proxy floating window has a higher level than the target floating window.

[0054] The storage module is further configured to determine a third operation type corresponding to the target operation according to the following steps:

[0055] The third operation type corresponding to the target operation obtained from the preset proxy floating window is determined as the floating window trigger operation; and,

[0056] The third operation type corresponding to the target operation obtained from the page is determined as the ordinary page-triggered operation.

[0057] In one possible implementation, the target recording result corresponding to the target operation also includes the operation result corresponding to the target operation;

[0058] The storage module, when storing the timestamp information of the target operation and the processing process identifier as the target recording result of the target operation, is used for:

[0059] Obtain the operation result corresponding to the target operation;

[0060] The operation result, timestamp information, and processing process identifier of the target operation are stored as the target recording result of the target operation.

[0061] Fourthly, embodiments of this disclosure also provide an operation playback recording, including:

[0062] The second acquisition module is used to acquire a target recording result determined based on any of the operation recording methods described in the first aspect; wherein the target recording result contains operation information corresponding to the target operation, and the operation information includes timestamp information and a processing process identifier for executing the target operation;

[0063] The determining module is used to determine a first operation type for each target operation based on the processing process identifier; wherein, the first operation type includes synchronous execution operations and asynchronous execution operations;

[0064] The playback module is used to perform playback processing on the target operation based on the timestamp information corresponding to the target operation and the first operation type.

[0065] In one possible implementation, the timestamp information corresponding to each target operation includes timestamp information of multiple operation steps constituting each target operation;

[0066] The playback module, when performing playback processing on the target operation based on the timestamp information corresponding to the target operation and the first operation type, is used to:

[0067] Based on the timestamp information of each operation step corresponding to the asynchronous and synchronous execution operations, the execution order of each operation step is determined.

[0068] The target operation is replayed according to the execution order of each operation step corresponding to the asynchronous and synchronous execution operations, and the operation result of the asynchronous execution operation.

[0069] Fifthly, embodiments of this disclosure also provide a computer device, including: a processor, a memory, and a bus, wherein the memory stores machine-readable instructions executable by the processor, and when the computer device is running, the processor communicates with the memory via the bus, and when the machine-readable instructions are executed by the processor, they perform the steps in any of the possible implementations of the first or second aspect described above.

[0070] In a sixth aspect, embodiments of this disclosure also provide a computer-readable storage medium storing a computer program that, when executed by a processor, performs the steps in any of the possible implementations of the first or second aspect described above.

[0071] The operation recording method, playback method, apparatus, computer device, and storage medium provided in this disclosure, during operation recording, record operation information corresponding to each target operation executed by different processing processes, including timestamp information and processing process identifier information. This allows for determination of whether each target operation is executed synchronously or asynchronously based on the processing process identifier. By recording the processing process identifier used to determine whether a target operation is executed synchronously or asynchronously, subsequent operation playback based on the recording results allows for assessment of whether the target operation is asynchronous and whether waiting for previous target operations to complete is necessary. This avoids playback anomalies caused by differences in operation response times.

[0072] To make the above-mentioned objects, features and advantages of this disclosure more apparent and understandable, preferred embodiments are described below in detail with reference to the accompanying drawings. Attached Figure Description

[0073] To more clearly illustrate the technical solutions of the embodiments of this disclosure, the accompanying drawings used in the embodiments will be briefly described below. These drawings are incorporated in and constitute a part of this specification. They illustrate embodiments conforming to this disclosure and, together with the specification, serve to explain the technical solutions of this disclosure. It should be understood that the following drawings only show some embodiments of this disclosure and should not be considered as limiting the scope. Those skilled in the art can obtain other related drawings based on these drawings without creative effort.

[0074] Figure 1 A flowchart of an operation recording method provided by an embodiment of this disclosure is shown;

[0075] Figure 2 A flowchart of an operation playback method provided by an embodiment of this disclosure is shown;

[0076] Figure 3 A schematic diagram of the architecture of an operation recording device provided in an embodiment of this disclosure is shown;

[0077] Figure 4 A schematic diagram of the architecture of an operation playback device provided in an embodiment of this disclosure is shown;

[0078] Figure 5 A schematic diagram of the structure of a computer device provided in an embodiment of this disclosure is shown. Detailed Implementation

[0079] To make the objectives, technical solutions, and advantages of the embodiments of this disclosure clearer, the technical solutions of the embodiments of this disclosure will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this disclosure, and not all of them. The components of the embodiments of this disclosure described and shown in the accompanying drawings can generally be arranged and designed in various different configurations. Therefore, the following detailed description of the embodiments of this disclosure provided in the accompanying drawings is not intended to limit the scope of the claimed disclosure, but merely represents selected embodiments of this disclosure. All other embodiments obtained by those skilled in the art based on the embodiments of this disclosure without inventive effort are within the scope of protection of this disclosure.

[0080] It should be noted that similar labels and letters in the following figures indicate similar items. Therefore, once an item is defined in one figure, it does not need to be further defined and explained in subsequent figures.

[0081] In this document, the term "and / or" merely describes a relationship, indicating that three relationships can exist. For example, A and / or B can represent three cases: A alone, A and B simultaneously, and B alone. Furthermore, the term "at least one" in this document means any combination of at least two of any one or more elements. For example, including at least one of A, B, and C can mean including any one or more elements selected from the set consisting of A, B, and C.

[0082] It is understood that before using the technical solutions disclosed in the various embodiments of this disclosure, users should be informed of the types, scope of use, and usage scenarios of the personal information involved in this disclosure in an appropriate manner in accordance with relevant laws and regulations, and user authorization should be obtained.

[0083] For example, upon receiving a user's active request, a prompt message is sent to the user to explicitly inform them that the requested operation will require the acquisition and use of the user's personal information. This allows the user to independently choose whether to provide personal information to the software or hardware, such as the electronic device, application, server, or storage medium performing the operations of this disclosed technical solution, based on the prompt message.

[0084] As an optional but non-limiting implementation, in response to a user's active request, sending a prompt message to the user can be done via a pop-up window, where the prompt message can be presented in text format. Furthermore, the pop-up window can also include a selection control allowing the user to choose "agree" or "disagree" to provide personal information to the electronic device.

[0085] It is understood that the above notification and user authorization process are merely illustrative and do not constitute a limitation on the implementation of this disclosure. Other methods that comply with relevant laws and regulations may also be applied to the implementation of this disclosure.

[0086] Research has found that when users are using terminal devices, they can use the device's operation recording function to record their actions to meet their different needs, such as guiding page browsing or teaching page functions.

[0087] Specifically, as applications offer an increasingly rich variety of pages, some users may be unable to find the page they want to browse due to unfamiliarity with the application's operation. To help these users access the desired page, the corresponding actions can be recorded to guide them through the process. Alternatively, since different functions within an application require specific actions to be performed, recording these actions can help users quickly familiarize themselves with the application's relevant functions.

[0088] In related technologies, when using the operation recording function of a terminal device to record a user's operation, only basic information such as the duration of each operation is often recorded. However, due to the different processing performance of different devices, when playing back the user's operation on different devices, the response time of different operations may vary due to device performance and other reasons. Therefore, playback abnormalities may occur, which in turn affects the user experience.

[0089] For example, taking triggering operations as an example, triggering operations in actual applications can include various triggering operations such as single click, long press, and multi-finger operation. However, since the relevant technologies do not record the timestamp information corresponding to each step of the user's operation in detail, various triggering operations are often simply recorded as triggering operations without distinguishing what kind of triggering operation it is.

[0090] Based on the above research, this disclosure provides an operation recording method, playback method, apparatus, computer device, and storage medium. During operation recording, operation information, including timestamp information and process identifier information, is recorded for each target operation executed by different processing processes. This allows for determination of whether each target operation is executed synchronously or asynchronously based on the process identifier. By recording the process identifier used to determine whether a target operation is synchronous or asynchronous, subsequent operation playback based on the recording results allows for assessment of whether the target operation is asynchronous and whether waiting for previous target operations to complete is necessary. This avoids playback anomalies caused by differences in operation response times.

[0091] To facilitate understanding of this embodiment, a detailed description of the operation recording method disclosed in this disclosure is provided first. The execution entity of the operation recording method provided in this disclosure is generally a computer device with a certain computing capability. This computer device may include, for example, a terminal device, a server, or other processing devices. The terminal device may be a user equipment (UE), mobile device, user terminal, terminal, personal digital assistant (PDA), handheld device, computing device, in-vehicle device, wearable device, etc. In some possible implementations, this operation recording method can be implemented by a processor calling computer-readable instructions stored in memory.

[0092] See Figure 1 The diagram shows a flowchart of an operation recording method provided in an embodiment of this disclosure. The method includes steps S101 to S102, wherein:

[0093] S101: In response to the recording trigger operation, obtain the operation information corresponding to each target operation executed by different processing processes, wherein the operation information includes timestamp information and processing process identifier; wherein, the processing process identifier is used to determine the first operation type of the target operation, the first operation type includes synchronous execution operation and asynchronous execution operation.

[0094] S102: Store the timestamp information of the target operation and the processing process identifier as the target recording result of the target operation.

[0095] The following is a detailed explanation of the steps described above.

[0096] Regarding S101, the recording trigger operation can be initiated by the user against a preset operation recording button in the target application. Once the operation recording button is triggered, the current trigger operation can be determined as the recording trigger operation. The timestamp information corresponding to each target operation can include the timestamp information of multiple operation steps constituting each target operation. The operation steps can be part of the operation content in the target operation. The target operation consists of at least one operation step. Taking the target operation as a click operation as an example, the click operation can consist of a press operation and a release operation. That is, detecting one press operation and one release operation can be regarded as performing one click operation. The operation information corresponding to the operation step can include the operation target corresponding to the operation step, the location information corresponding to the operation target, the timestamp information corresponding to the operation step, etc., wherein the operation target can be a triggerable component in the target display page of the target application, such as a triggerable button, link, etc. The operation information corresponding to each target operation executed by different processing processes can be the operation information obtained after user authorization.

[0097] The asynchronous execution operation refers to an asynchronous relationship between other target operations. Subsequent target operations can only be executed after the asynchronous execution operation has been completed. For example, triggering a button on a subpage can be considered an asynchronous execution operation because the target application needs to load the subpage after triggering the button. Loading the subpage is time-consuming, and other operations cannot be performed during the loading process. Therefore, this type of operation can be considered asynchronous. The synchronous execution operation, on the other hand, is synchronous in relationship with other target operations. Other target operations can be executed without confirming the completion of the synchronous execution operation.

[0098] In one possible implementation, when determining the first operation type of the target operation based on the processing process identifier, the first operation type of the target operation whose corresponding processing process identifier is the main process can be determined as a synchronous execution operation, and the first operation type of the target operation whose corresponding processing process identifier is the non-main process (i.e., child process) can be determined as an asynchronous execution operation.

[0099] The processing process identifier corresponding to the target operation can be the processing process identifier corresponding to each operation step of the target operation.

[0100] For example, taking the target operation as entering the mini-program page and performing operation step 1, and the triggering operation for entering the mini-program page as the triggering operation for the corresponding button on the mini-program page, since the triggering operation for the corresponding button on the mini-program page is handled by the main process corresponding to the current main page, a processing process identifier "main process" can be added to the operation step "triggering operation for the corresponding button on the mini-program page" in the target operation (which may include two steps, such as pressing and releasing). Since the operation 1 needs to be performed on the mini-program page, a processing process identifier "non-main process" can be added to the operation step "operation step 1" in the target operation. In order to complete the recording of the operation content of the non-main process, after detecting the triggering operation corresponding to the non-main process, the operation content of the triggering operation can be sent to the main process so that the operation recording can be completed in the main process.

[0101] For example, taking the target operation as including triggering a button to open the mini-program, performing operation 1 on the mini-program, returning to the main program, and performing operation 2, the obtained processing process identifier can be:

[0102] 1: Action(MotionEvent(ACTION_DOWN), main process)

[0103] 2: Action(MotionEvent(ACTION_UP), main process)

[0104] 3: Action (Operation 1, not in the main process)

[0105] 4: Action (Back, not in the main process)

[0106] 5: Action (Operation 2, Main Process)

[0107] Here, Action represents the target operation to be performed; MotionEvent represents the operation steps, where ACTION_DOWN represents a press operation, ACTION_UP represents a release operation, and Back represents a return operation; "main process" indicates that the processing process is identified as the main process, and "non-main process" indicates that the processing process is identified as a non-main process.

[0108] In this way, by obtaining the process identifiers corresponding to each target operation, the target application can be enabled to record multi-process operations.

[0109] S102: Store the timestamp information of the target operation and the processing process identifier as the target recording result of the target operation.

[0110] Here, when storing the timestamp information of the target operation and the processing process identifier as the target recording result of the target operation, the operation information of each target operation containing the processing process identifier can be stored sequentially according to the timestamp information of each target operation.

[0111] Furthermore, the target recording result may also include a second operation type for characterizing the interaction method between the user and the terminal device. The second operation type may include operation types such as long press operation, multi-finger operation, and text editing operation.

[0112] Specifically, when determining the second operation type of the target operation, the second operation type of the target operation corresponding to the operation step can be determined based on the timestamp information corresponding to each operation step.

[0113] In one possible implementation, if the time interval between the start trigger operation and the end trigger operation at the first target location is detected to meet a first preset requirement, the second operation type of the currently recorded target operation is determined to be a long press operation.

[0114] Here, the first preset requirement may be that the time interval between the start triggering operation and the end triggering operation at the first target location is greater than a preset first time interval, such as 2 seconds.

[0115] Specifically, when determining the time interval between the start trigger operation and the end trigger operation at the first target location, it can be determined based on the timestamp information corresponding to the start trigger operation and the timestamp information corresponding to the end trigger operation.

[0116] For example, if the timestamp of the start trigger operation at location A is the 1st second after recording starts, and the timestamp of the end trigger operation at location A is the 3.5th second after recording starts, then the duration of the current trigger operation at location A (i.e., the time interval) can be determined to be 2.5 seconds, which is greater than the preset first time interval of 2 seconds. Therefore, the target operation at location A can be determined to be a long press operation at location A.

[0117] In one possible implementation, if the time interval between trigger operations at multiple second target locations is detected to meet a second preset requirement, the second operation type of the currently recorded target operation is determined to be a multi-finger operation.

[0118] Here, the second preset requirement may be that the time interval between the initial triggering operations at multiple second target locations is less than a preset second time interval, such as 0.5 seconds.

[0119] Specifically, when determining the time interval between the initial triggering operations for multiple second target locations, it can be based on any two initial triggering operations with similar timestamp information; or it can be based on the timestamp information corresponding to the pre-specified initial triggering operations, such as using the timestamp information corresponding to the first executed initial triggering operation and the last executed initial triggering operation to determine the time interval between the initial triggering operations for multiple second target locations.

[0120] For example, if the timestamps of the initial trigger operations at positions B, C, and D are 1 second, 1.2 seconds, and 1.6 seconds after recording starts, respectively, then the time intervals between the current initial trigger operations are 0.2 seconds and 0.4 seconds, which are less than the preset second time interval of 0.5 seconds. Therefore, the target operation at positions B, C, and D can be determined to be a multi-finger operation at positions B, C, and D. Alternatively, the timestamps corresponding to the initial trigger operations at positions B and D can be used to determine that the time interval between the trigger operations at positions B, C, and D is 0.6 seconds, which is greater than the preset second time interval, and the time interval between the initial trigger operations at positions B and C is 0.2 seconds, which is less than the preset second time interval. Therefore, the target operation at positions B, C, and D can be determined to be a multi-finger operation at positions B and C, and a trigger operation at position D.

[0121] In practical applications, in order to enable the target application to record text editing operations, a text content monitoring event can be set up to monitor the changes in the text content at the third target position when a trigger operation occurs at a preset third target position, so as to obtain the text content change information at the third target position and use the text content change information at the third target position as the operation information corresponding to the text editing operation.

[0122] For example, taking the text editing operation as first inputting "abcd" and then deleting "cd", the text content change information that the text content detection event can obtain is as follows:

[0123] a.TextChangeAction(changeType=insert,position=0,inserted="a");

[0124] b.TextChangeAction(changeType=insert, position=1, inserted="b");

[0125] c.TextChangeAction(changeType=insert,position=2,inserted="c");

[0126] d.TextChangeAction(changeType=insert,position=3,inserted="d");

[0127] e.TextChangeAction(changeType=delete, position=2, deleted=2).

[0128] Here, TextChangeAction indicates that a change in text content has been detected; changeType indicates the type of change in text content, insert indicates input, delete indicates deletion; position indicates the position where the change occurred, 0, 1, 2, 3 respectively indicate the (N+1)th position from left to right where the change occurred (N takes values ​​from 0 to 3), for example, 0 indicates the first position from left to right; inserted="" is used to indicate the input content; deleted=" is used to indicate the number of positions to be deleted.

[0129] Specifically, the text content corresponding to each step from a to e is a, ab, abc, abcd, ab.

[0130] In one possible implementation, the method further includes determining a third operation type corresponding to the target operation, the third operation type including a floating window trigger operation and a normal page trigger operation;

[0131] Here, the floating window trigger operation is an operation initiated for a floating window displayed in the target application; the normal page trigger operation is an operation initiated for a target page in the target application, such as the main page of the target application; after detecting the operation steps for the target floating window, the operation information of the operation steps for the target floating window can be added to a preset proxy floating window, wherein the preset proxy floating window has a higher level than the target floating window.

[0132] In practical applications, when obtaining the operation information corresponding to each operation step, the method used is event callback. Since the floating window's layer is lower than the main page of the target application, and the rendering window's layer cannot meet the layer requirements of the event callback, the floating window trigger operation cannot be directly recorded.

[0133] In this way, by adding the operation information of the operation steps for the target floating window to a preset proxy floating window at a higher level than the target floating window, the floating window trigger operation for the target floating window can be recorded, thereby enabling the target application to have a floating window operation recording function.

[0134] In one possible implementation, when determining the third operation type of the target operation corresponding to the operation step, the third operation type of the target operation corresponding to the operation information obtained from the preset proxy floating window can be determined as the floating window triggered operation; and the third operation type of the target operation corresponding to the operation information obtained from the page can be determined as the normal page triggered operation.

[0135] Here, the operation information obtained from the page can be operation information obtained from the target page, such as the main page of the target application.

[0136] Furthermore, when recording the target recording result of the target operation, the timestamp information of the target operation and the processing process identifier can be stored as the target recording result of the target operation.

[0137] The timestamp information of the target operation may include the timestamp information corresponding to each operation step of the target operation.

[0138] Thus, by storing the processing process identifier used to determine the first operation type, the second operation type used to characterize the interaction method of the target operation (whether it is a long press operation, multi-finger operation, etc.), the operation information (the operation target corresponding to the operation, the location of the operation target, etc.), and the third operation type used to characterize the target operation on the page (whether it is a trigger operation for the floating window, a trigger operation for the main page, etc.) in a preset storage format (e.g., text format, video format, etc.), the target recording result of the target operation can be obtained.

[0139] Furthermore, in order to record the target operation in more detail, the target recording result corresponding to the target operation may also include the operation result corresponding to the target operation.

[0140] Here, when recording the target operation, the operation result corresponding to the target operation can be the subsequent action performed by the target application after the target operation is executed.

[0141] For example, taking the target operation as a trigger operation on the button corresponding to subpage A, the operation result corresponding to the target operation is to open subpage A.

[0142] In this way, by recording the operation results corresponding to the target operation, the subsequent actions that the target application needs to perform after executing the target operation can be recorded, which facilitates the replay processing of the target operation.

[0143] Furthermore, in order to ensure that the target recording result can meet the personalized needs of different users during playback, after obtaining the target recording result, a recording result editing operation can also be performed on the target recording result. The recording result editing operation includes deleting the target recording result corresponding to any target operation, editing the target recording result corresponding to any target operation, etc.

[0144] See Figure 2 The diagram shows a flowchart of an operation recording method provided in an embodiment of this disclosure. The method includes steps S201 to S203, wherein:

[0145] S201: Obtain the target recording result determined based on any of the operation recording methods described in the embodiments of this disclosure; the target recording result includes operation information corresponding to the target operation, and the operation information includes timestamp information and a processing process identifier for executing the target operation.

[0146] Here, the timestamp information corresponding to each target operation may include the timestamp information of multiple operation steps that constitute each target operation.

[0147] S202: Based on the processing process identifier, determine the first operation type of each target operation; wherein, the first operation type includes synchronous execution operation and asynchronous execution operation.

[0148] S203: Based on the timestamp information corresponding to the target operation and the first operation type, perform replay processing on the target operation.

[0149] In one possible implementation, when replaying the target operation, for any target operation, the replay process can be performed sequentially based on the timestamp information corresponding to each operation step contained in the target operation.

[0150] Here, when replaying each operation step included in the target operation in sequence, the operation content corresponding to each operation step in the target recording result can be obtained, and each operation step can be replayed according to the operation content and timestamp information corresponding to each operation step.

[0151] In one possible implementation, when performing playback processing on the target operation based on the timestamp information corresponding to the target operation and the first operation type, the following steps A1 to A3 can be used:

[0152] A1: Based on the timestamp information of each operation step corresponding to the asynchronous execution operation and the synchronous execution operation, the execution order of each operation step is determined.

[0153] A2: The target operation is replayed according to the execution order of each operation step corresponding to the asynchronous execution operation and the synchronous execution operation, and the operation result of the asynchronous execution operation.

[0154] Here, when the subsequent actions corresponding to the asynchronous execution operation have been completed, the result of the asynchronous execution operation can be determined as completed. At this time, the remaining target operations can continue to be replayed according to the execution order until the replay of each target operation is completed.

[0155] Furthermore, when the second operation type of the target operation is a sliding operation, the sliding operation can be replayed according to the page sliding speed when the sliding operation is recorded; after the replay of any of the target operations, the target operation after the target operation can be replayed according to the operation interval between recording the target operation and the target operation after the target operation.

[0156] The operation recording method provided in this disclosure records operation information, including timestamp information and process identifier information, corresponding to each target operation executed by different processing processes. This allows the method to determine whether each target operation is executed synchronously or asynchronously based on the process identifier. By recording the process identifier used to determine whether a target operation is synchronous or asynchronous, subsequent operation playback based on the recording results allows the method to determine whether waiting for previous target operations to complete is necessary when executing a target operation asynchronously. This avoids playback anomalies caused by differences in operation response times.

[0157] Those skilled in the art will understand that, in the above-described method of the specific implementation, the order in which each step is written does not imply a strict execution order and does not constitute any limitation on the implementation process. The specific execution order of each step should be determined by its function and possible internal logic.

[0158] Based on the same inventive concept, this disclosure also provides an operation recording device corresponding to the operation recording method. Since the principle of the device in this disclosure for solving the problem is similar to the operation recording method described above, the implementation of the device can refer to the implementation of the method, and the repeated parts will not be described again.

[0159] Reference Figure 3The diagram shown is an architectural schematic of an operation recording device provided in an embodiment of this disclosure. The device includes: a first acquisition module 301 and a storage module 302; wherein,

[0160] The first acquisition module 301 is used to acquire, in response to a recording trigger operation, operation information corresponding to each target operation executed by different processing processes. The operation information includes timestamp information and processing process identifier. The processing process identifier is used to determine a first operation type of the target operation. The first operation type includes synchronous execution operation and asynchronous execution operation.

[0161] The storage module 302 is used to store the timestamp information of the target operation and the processing process identifier as the target recording result of the target operation.

[0162] In one possible implementation, the timestamp information corresponding to each target operation includes timestamp information of multiple operation steps constituting each target operation;

[0163] The storage module 302, when storing the timestamp information of the target operation and the processing process identifier as the target recording result of the target operation, is used for:

[0164] Based on the timestamp information corresponding to each operation step, a second operation type for the target operation corresponding to the operation step is determined; wherein, the second operation type is used to characterize the interaction method between the user and the terminal device;

[0165] The second operation type, timestamp information, and processing process identifier of the target operation are stored as the target recording result of the target operation.

[0166] In one possible implementation, the second operation type of the target operation includes a long press operation;

[0167] The storage module 302, when determining the second operation type of the target operation corresponding to each operation step based on the timestamp information corresponding to each operation step, is used for:

[0168] If the time interval between the start trigger operation and the end trigger operation at the first target location is detected to meet the first preset requirement, the second operation type of the currently recorded target operation is determined to be a long press operation.

[0169] In one possible implementation, the second operation type of the target operation includes multi-finger operation;

[0170] The storage module 302, when determining the second operation type of the target operation corresponding to each operation step based on the timestamp information corresponding to each operation step, is used for:

[0171] If the time interval between trigger operations at multiple second target locations is found to meet the second preset requirement, the second operation type of the currently recorded target operation is determined to be a multi-finger operation.

[0172] In one possible implementation, the storage module 302 is further configured to determine a third operation type corresponding to the target operation; the third operation type includes a floating window trigger operation and a normal page trigger operation;

[0173] The storage module 302, when storing the timestamp information of the target operation and the processing process identifier as the target recording result of the target operation, is used for:

[0174] The third operation type, timestamp information, and processing process identifier of the target operation are stored as the target recording result of the target operation.

[0175] In one possible implementation, the storage module 302 is further configured to: after detecting an operation step for the target floating window, add the operation information of the operation step for the target floating window to a preset proxy floating window, wherein the preset proxy floating window has a higher level than the target floating window.

[0176] The storage module 302 is further configured to determine a third operation type corresponding to the target operation according to the following steps:

[0177] The third operation type corresponding to the target operation obtained from the preset proxy floating window is determined as the floating window trigger operation; and,

[0178] The third operation type corresponding to the target operation obtained from the page is determined as the ordinary page-triggered operation.

[0179] In one possible implementation, the target recording result corresponding to the target operation also includes the operation result corresponding to the target operation;

[0180] The storage module 302, when storing the timestamp information of the target operation and the processing process identifier as the target recording result of the target operation, is used for:

[0181] Obtain the operation result corresponding to the target operation;

[0182] The operation result, timestamp information, and processing process identifier of the target operation are stored as the target recording result of the target operation.

[0183] Reference Figure 4The diagram shown is an architectural schematic of an operation playback device provided in an embodiment of this disclosure. The device includes: a second acquisition module 401, a determination module 402, and a playback module 403; wherein,

[0184] The second acquisition module 401 is used to acquire a target recording result determined by the operation recording method according to any embodiment of the present disclosure; wherein, the target recording result includes operation information corresponding to the target operation, and the operation information includes timestamp information and a processing process identifier for executing the target operation;

[0185] The determining module 402 is used to determine a first operation type for each target operation based on the processing process identifier; wherein, the first operation type includes synchronous execution operations and asynchronous execution operations;

[0186] The playback module 403 is used to perform playback processing on the target operation based on the timestamp information corresponding to the target operation and the first operation type.

[0187] In one possible implementation, the timestamp information corresponding to each target operation includes timestamp information of multiple operation steps constituting each target operation;

[0188] The playback module 403, when performing playback processing on the target operation based on the timestamp information corresponding to the target operation and the first operation type, is used to:

[0189] Based on the timestamp information of each operation step corresponding to the asynchronous and synchronous execution operations, the execution order of each operation step is determined.

[0190] The target operation is replayed according to the execution order of each operation step corresponding to the asynchronous and synchronous execution operations, and the operation result of the asynchronous execution operation.

[0191] The operation recording device provided in this embodiment records operation information, including timestamp information and process identifier information, corresponding to each target operation executed by different processing processes during operation recording. This allows the device to determine whether each target operation is executed synchronously or asynchronously based on the process identifier. By recording the process identifier used to determine whether a target operation is executed synchronously or asynchronously, subsequent operation playback based on the recording results allows the device to determine whether it needs to wait for previous target operations to complete before executing its own target operation, thus avoiding playback anomalies caused by differences in operation response times.

[0192] The processing flow of each module in the device and the interaction flow between each module can be referred to the relevant descriptions in the above method embodiments, and will not be detailed here.

[0193] Based on the same technical concept, this disclosure also provides a computer device. (See also...) Figure 5 The diagram shows the structure of a computer device 500 provided in this embodiment of the present disclosure, including a processor 501, a memory 502, and a bus 503. The memory 502 stores execution instructions and includes main memory 5021 and external memory 5022. The main memory 5021, also called internal memory, is used to temporarily store computational data in the processor 501 and data exchanged with external memory 5022 such as a hard disk. The processor 501 exchanges data with the external memory 5022 through the main memory 5021. When the computer device 500 is running, the processor 501 and the memory 502 communicate through the bus 503, causing the processor 501 to execute the following instructions:

[0194] In response to a recording trigger operation, operation information corresponding to each target operation executed by different processing processes is obtained. The operation information includes timestamp information and processing process identifier. The processing process identifier is used to determine a first operation type of the target operation, which includes synchronous execution operation and asynchronous execution operation.

[0195] The timestamp information of the target operation and the process identifier are stored as the target recording result of the target operation.

[0196] In one possible implementation, the timestamp information corresponding to each target operation in the instructions of the processor 501 includes timestamp information of multiple operation steps constituting each target operation.

[0197] The step of storing the timestamp information of the target operation and the processing process identifier as the target recording result of the target operation includes:

[0198] Based on the timestamp information corresponding to each operation step, a second operation type for the target operation corresponding to the operation step is determined; wherein, the second operation type is used to characterize the interaction method between the user and the terminal device;

[0199] The second operation type, timestamp information, and processing process identifier of the target operation are stored as the target recording result of the target operation.

[0200] In one possible implementation, the second operation type of the target operation in the instructions of the processor 501 includes a long press operation;

[0201] The step of determining the second operation type of the target operation corresponding to each operation step based on the timestamp information corresponding to each operation step includes:

[0202] If the time interval between the start trigger operation and the end trigger operation at the first target location is detected to meet the first preset requirement, the second operation type of the currently recorded target operation is determined to be a long press operation.

[0203] In one possible implementation, the second operation type of the target operation in the instructions of the processor 501 includes a multi-finger operation;

[0204] The step of determining the second operation type of the target operation corresponding to each operation step based on the timestamp information corresponding to each operation step includes:

[0205] If the time interval between trigger operations at multiple second target locations is found to meet the second preset requirement, the second operation type of the currently recorded target operation is determined to be a multi-finger operation.

[0206] In one possible implementation, the instructions of the processor 501 further include determining a third operation type corresponding to the target operation; the third operation type includes a floating window trigger operation and a normal page trigger operation;

[0207] The step of storing the timestamp information of the target operation and the processing process identifier as the target recording result of the target operation includes:

[0208] The third operation type, timestamp information, and processing process identifier of the target operation are stored as the target recording result of the target operation.

[0209] In one possible implementation, the instructions of the processor 501 further include: after detecting an operation step for the target floating window, adding the operation information of the operation step for the target floating window to a preset proxy floating window, wherein the preset proxy floating window has a higher level than the target floating window.

[0210] The method further includes determining a third operation type corresponding to the target operation according to the following method:

[0211] The third operation type corresponding to the target operation obtained from the preset proxy floating window is determined as the floating window trigger operation; and,

[0212] The third operation type corresponding to the target operation obtained from the page is determined as the ordinary page-triggered operation.

[0213] In one possible implementation, the instructions of the processor 501 may include, in the target recording result corresponding to the target operation, an operation result corresponding to the target operation.

[0214] The step of storing the timestamp information of the target operation and the processing process identifier as the target recording result of the target operation includes:

[0215] Obtain the operation result corresponding to the target operation;

[0216] The operation result, timestamp information, and processing process identifier of the target operation are stored as the target recording result of the target operation;

[0217] Alternatively, the processor 501 may execute the following instructions:

[0218] Obtain a target recording result determined by the operation recording method according to any embodiment of this disclosure; wherein, the target recording result includes operation information corresponding to the target operation, and the operation information includes timestamp information and a processing process identifier for executing the target operation;

[0219] Based on the processing process identifier, a first operation type is determined for each target operation; wherein, the first operation type includes synchronous execution operations and asynchronous execution operations;

[0220] Based on the timestamp information corresponding to the target operation and the first operation type, the target operation is replayed.

[0221] In one possible implementation, the timestamp information corresponding to each target operation in the instructions of the processor 501 includes timestamp information of multiple operation steps constituting each target operation.

[0222] The step of replaying the target operation based on the timestamp information corresponding to the target operation and the first operation type includes:

[0223] Based on the timestamp information of each operation step corresponding to the asynchronous and synchronous execution operations, the execution order of each operation step is determined.

[0224] The target operation is replayed according to the execution order of each operation step corresponding to the asynchronous and synchronous execution operations, and the operation result of the asynchronous execution operation.

[0225] This disclosure also provides a computer-readable storage medium storing a computer program, which, when executed by a processor, performs the steps of the operation recording method described in the above-described method embodiments. The storage medium may be a volatile or non-volatile computer-readable storage medium.

[0226] This disclosure also provides a computer program product carrying program code. The program code includes instructions that can be used to execute the steps of the operation recording method described in the above method embodiments. For details, please refer to the above method embodiments, which will not be repeated here.

[0227] The aforementioned computer program product can be implemented through hardware, software, or a combination thereof. In one optional embodiment, the computer program product is specifically embodied in a computer storage medium; in another optional embodiment, the computer program product is specifically embodied in a software product, such as a software development kit (SDK), etc.

[0228] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems and devices described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here. In the several embodiments provided in this disclosure, it should be understood that the disclosed systems, devices, and methods can be implemented in other ways. The device embodiments described above are merely illustrative. For example, the division of units is only a logical functional division; in actual implementation, there may be other division methods. Furthermore, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Another point is that the displayed or discussed mutual coupling or direct coupling or communication connection may be through some communication interfaces; the indirect coupling or communication connection of devices or units may be electrical, mechanical, or other forms.

[0229] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0230] In addition, the functional units in the various embodiments of this disclosure can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0231] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a processor-executable, non-volatile, computer-readable storage medium. Based on this understanding, the technical solution of this disclosure, in essence, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this disclosure. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0232] Finally, it should be noted that the above-described embodiments are merely specific implementations of this disclosure, used to illustrate the technical solutions of this disclosure, and not to limit it. The protection scope of this disclosure is not limited thereto. Although this disclosure has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that any person skilled in the art can still modify or easily conceive of changes to the technical solutions described in the foregoing embodiments, or make equivalent substitutions for some of the technical features, within the scope of the technology disclosed in this disclosure. Such modifications, changes, or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this disclosure, and should all be covered within the protection scope of this disclosure. Therefore, the protection scope of this disclosure should be determined by the protection scope of the claims.

Claims

1. An operation recording method, characterized in that, include: In response to a recording trigger operation, operation information corresponding to each target operation executed by different processing processes in a multi-process operation is obtained. The operation information includes timestamp information and processing process identifier. The processing process identifier is used to determine a first operation type of the target operation. The first operation type includes synchronous execution operation and asynchronous execution operation. The asynchronous execution operation is asynchronously related to other target operations. Subsequent target operations are executed only after the asynchronous execution operation is completed. The timestamp information corresponding to each target operation includes timestamp information of multiple operation steps constituting each target operation. The timestamp information of the target operation and the process identifier are stored as the target recording result of the target operation.

2. The method according to claim 1, characterized in that, The timestamp information corresponding to each target operation includes the timestamp information of multiple operation steps that constitute each target operation; The step of storing the timestamp information of the target operation and the processing process identifier as the target recording result of the target operation includes: Based on the timestamp information corresponding to each operation step, a second operation type for the target operation corresponding to the operation step is determined; wherein, the second operation type is used to characterize the interaction method between the user and the terminal device; The second operation type, timestamp information, and processing process identifier of the target operation are stored as the target recording result of the target operation.

3. The method according to claim 2, characterized in that, The second operation type of the target operation includes a long press operation; The step of determining the second operation type of the target operation corresponding to each operation step based on the timestamp information corresponding to each operation step includes: If the time interval between the start trigger operation and the end trigger operation at the first target location is detected to meet the first preset requirement, the second operation type of the currently recorded target operation is determined to be a long press operation.

4. The method according to claim 2, characterized in that, The second operation type of the target operation includes multi-finger operation; The step of determining the second operation type of the target operation corresponding to each operation step based on the timestamp information corresponding to each operation step includes: If the time interval between trigger operations at multiple second target locations is found to meet the second preset requirement, the second operation type of the currently recorded target operation is determined to be a multi-finger operation.

5. The method according to claim 1, characterized in that, The method further includes determining a third operation type corresponding to the target operation; the third operation type includes floating window triggered operation and normal page triggered operation; The step of storing the timestamp information of the target operation and the processing process identifier as the target recording result of the target operation includes: The third operation type, timestamp information, and processing process identifier of the target operation are stored as the target recording result of the target operation.

6. The method according to claim 5, characterized in that, The method further includes: after detecting the operation steps for the target floating window, adding the operation information of the operation steps for the target floating window to a preset proxy floating window, wherein the preset proxy floating window has a higher level than the target floating window; The method further includes determining a third operation type corresponding to the target operation according to the following method: The third operation type corresponding to the target operation obtained from the preset proxy floating window is determined as the floating window trigger operation; and, The third operation type corresponding to the target operation obtained from the page is determined as the ordinary page-triggered operation.

7. The method according to any one of claims 1 to 6, characterized in that, The target recording result corresponding to the target operation also includes the operation result corresponding to the target operation; The step of storing the timestamp information of the target operation and the processing process identifier as the target recording result of the target operation includes: Obtain the operation result corresponding to the target operation; The operation result, timestamp information, and processing process identifier of the target operation are stored as the target recording result of the target operation.

8. An operation playback method, characterized in that, include: Obtain a target recording result determined by the operation recording method according to any one of claims 1 to 7; wherein the target recording result includes operation information corresponding to the target operation, and the operation information includes timestamp information and a processing process identifier for executing the target operation; Based on the processing process identifier, a first operation type is determined for each target operation; wherein, the first operation type includes synchronous execution operations and asynchronous execution operations; Based on the timestamp information corresponding to the target operation and the first operation type, the target operation is replayed.

9. The method according to claim 8, characterized in that, The timestamp information corresponding to each target operation includes the timestamp information of multiple operation steps that constitute each target operation; The step of replaying the target operation based on the timestamp information corresponding to the target operation and the first operation type includes: Based on the timestamp information of each operation step corresponding to the asynchronous and synchronous execution operations, the execution order of each operation step is determined. The target operation is replayed according to the execution order of each operation step corresponding to the asynchronous and synchronous execution operations, and the operation result of the asynchronous execution operation.

10. An operation recording device, characterized in that, include: The first acquisition module is configured to, in response to a recording trigger operation, acquire operation information corresponding to each target operation executed by different processing processes in a multi-process operation. The operation information includes timestamp information and a processing process identifier. The processing process identifier is used to determine a first operation type of the target operation. The first operation type includes synchronous execution operations and asynchronous execution operations. The asynchronous execution operation is asynchronously related to other target operations. Subsequent target operations are executed only after the asynchronous execution operation is completed. The timestamp information corresponding to each target operation includes timestamp information of multiple operation steps constituting each target operation. The storage module is used to store the timestamp information of the target operation and the processing process identifier as the target recording result of the target operation.

11. An operation playback device, characterized in that, include: The second acquisition module is used to acquire the target recording result determined by the operation recording method according to any one of claims 1 to 7; wherein the target recording result includes operation information corresponding to the target operation, and the operation information includes timestamp information and a processing process identifier for executing the target operation; The determining module is used to determine a first operation type for each target operation based on the processing process identifier; wherein, the first operation type includes synchronous execution operations and asynchronous execution operations; The playback module is used to perform playback processing on the target operation based on the timestamp information corresponding to the target operation and the first operation type.

12. A computer device, characterized in that, include: The computer device includes a processor, a memory, and a bus. The memory stores machine-readable instructions executable by the processor. When the computer device is running, the processor communicates with the memory via the bus. When the machine-readable instructions are executed by the processor, the steps of the operation recording method as described in any one of claims 1 to 7 are performed. Alternatively, perform the steps of the operation playback method as described in claim 8 or 9.

13. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by a processor, performs the steps of the operation recording method as described in any one of claims 1 to 7. Alternatively, perform the steps of the operation playback method as described in claim 8 or 9.

Images