A page operation collection and playback method and related components

Abstract

The application discloses a page operation collection method and a page operation playback method, which records the calling time before a user triggers the calling of the mobile device capability when the user interacts with the page and the mobile device, then initiates the calling of the mobile device capability through a two-way communication device, records the callback information of the mobile device after the user interacts with the page and the mobile device, and sends the callback information and the calling information of the mobile device to a storage database for information storage after the page receives the callback information, and meanwhile, the corresponding interactive behavior is intercepted in a simulation environment, and the way of calling the mobile device capability is replaced by the way of calling the log service to obtain the mobile device log of the user, so that the subsequent display style and logic change after the page interacts with the mobile device are simulated, and the playback of the interactive behavior of the page and the mobile device is realized. The application also discloses a page operation collection device, a page operation playback device, a device and a readable storage medium, which have corresponding technical effects.

Description

Technical Field

[0001] This invention relates to the field of computer technology, and in particular to a page operation acquisition method, apparatus, page operation playback method, apparatus, device, and readable storage medium. Background Technology

[0002] During web browsing and operation, there are often situations where it is necessary to record the user's browsing and operation information to generate verifiable web operation process record data, so as to perform web page playback and thus fully understand the content, key points and operation process of the web page.

[0003] There are two main existing methods for implementing page replay and user action replay. The first method involves collecting and storing static page text data for each page. This static text data can be used to visually reconstruct the page, displaying it in the order of timestamps to achieve visual replay of page actions. However, this method requires storing a large amount of data, putting significant pressure on network transmission and data storage devices, and also resulting in resource waste. The second method involves collecting user action data from the page to be replayed, converting this data into readable operation logs, and then using pre-set simulation software to simulate and replay user actions based on these logs when a replay request is detected. However, this method limits the replay scope to independent user actions on the page and interactions with the server, excluding interactions with mobile devices that are frequently involved in mobile pages, resulting in a partial omission in the replay process.

[0004] In summary, how to collect and play back the interaction process of mobile devices while avoiding resource waste is a technical problem that urgently needs to be solved by those skilled in the art. Summary of the Invention

[0005] The purpose of this invention is to provide a page operation acquisition method, apparatus, device, and readable storage medium to achieve the acquisition and playback of mobile device interaction processes while avoiding resource waste.

[0006] To solve the above-mentioned technical problems, the present invention provides the following technical solution:

[0007] A method for collecting page actions, comprising:

[0008] If a page is invoked for a mobile device, the invocation time is recorded;

[0009] A call request is initiated to the mobile device through a two-way communication device, so that the mobile device responds to the call request and executes the corresponding call operation;

[0010] The callback information generated by the mobile device executing the call operation is obtained through the bidirectional communication device, and subsequent operations are performed based on the callback information;

[0011] The call information is organized to generate an interaction behavior log, and the interaction behavior log is sent to a storage database; wherein, the call information includes: the callback information and the call time.

[0012] Optionally, before recording the call time if the page is triggered to access the mobile device, the method further includes:

[0013] Receive user interaction events on the page;

[0014] Extract the backtracking information of the behavioral event and send the backtracking information to the storage database;

[0015] If the page triggers a call to the server, the interaction behavior information is extracted from the logs recorded by the server and sent to the storage database.

[0016] A page operation acquisition device, comprising:

[0017] The triggering unit is used to record the call time if a page is triggered to call a mobile device;

[0018] The forwarding unit is used to initiate a call request to the mobile device through a two-way communication device, so that the mobile device responds to the call request and executes the corresponding call operation;

[0019] A callback unit is used to obtain callback information generated by the mobile device executing the call operation through the bidirectional communication device, and to perform subsequent operations based on the callback information;

[0020] The log unit is used to organize call information to generate interaction behavior logs and send the interaction behavior logs to the storage database; wherein, the call information includes: the callback information and the call time.

[0021] A method for replaying page operations includes:

[0022] If a page call to a mobile device is triggered for playback, the specified playback target is determined; wherein, the playback target includes the object to be played back and the playback time;

[0023] According to the playback target, the corresponding interaction behavior logs are extracted from the storage database; wherein, the interaction behavior logs are generated according to the aforementioned page operation collection method;

[0024] The call information is parsed from the interaction behavior log, and the call operation is simulated based on the call information;

[0025] The simulation of subsequent operations is performed based on the callback information in the call information.

[0026] Optionally, retrieving the corresponding interaction behavior logs from the storage database according to the playback target includes:

[0027] The log retrieval server is invoked to extract the corresponding interaction behavior logs from the storage database based on the playback target.

[0028] Optionally, the step of simulating the call operation based on the call information includes:

[0029] The call operation is simulated based on the Javascript.

[0030] Optionally, before retrieving the corresponding interaction behavior logs from the storage database according to the playback target, the method further includes:

[0031] The mobile device to be replayed and its capability name are determined based on the replay target.

[0032] The system outputs prompt information based on the mobile device to be played back and the device capability name.

[0033] A page operation playback device, comprising:

[0034] The target unit is used to determine the specified playback target if the page is triggered to play back the mobile device; wherein, the playback target includes the object to be played back and the playback time.

[0035] The extraction unit is used to extract the corresponding interaction behavior logs from the storage database according to the playback target; wherein the interaction behavior logs are generated according to the page operation collection method.

[0036] The first simulation unit is used to parse the call information from the interaction behavior log and simulate the call operation based on the call information;

[0037] The second simulation unit is used to simulate subsequent operations based on the callback information in the call information.

[0038] A computer device, comprising:

[0039] Memory, used to store computer programs;

[0040] A processor is configured to implement the page operation acquisition method and / or the page operation playback step when executing the computer program.

[0041] A readable storage medium storing a computer program, which, when executed by a processor, implements the page operation acquisition method and / or the page operation playback steps.

[0042] The method provided in this invention records the call time before a user interacts with a page and a mobile device, triggering a capability call from the mobile device. This helps determine the corresponding call operations at different times. Then, a capability call is initiated to the mobile device via a bidirectional communication device, allowing the mobile device to perform the corresponding operation and generate callback information. The callback information required by the page is then returned to the page via the bidirectional communication device. Upon receiving the callback information, the page, along with the previously stored call time and other page-to-mobile device call information, sends it to a storage database for storage. This information serves as the basis for page operation replay. Subsequent page logic is then executed using the callback information to ensure the continuity of user operations. This method can collect the interaction behavior between a page and a mobile device while ensuring the continuity of user page operations. Furthermore, based on the above collection method, this method replaces the JSBridge method of calling mobile device capabilities with a method of calling a log service to obtain user mobile device logs. This simulates the subsequent display style and logic changes after the page-mobile device interaction, achieving the replay of the interaction behavior between the page and the mobile device.

[0043] Accordingly, embodiments of the present invention also provide a page operation acquisition device, equipment, and readable storage medium corresponding to the above-described page operation acquisition method, which have the above-described technical effects, and will not be repeated here. Attached Figure Description

[0044] To more clearly illustrate the technical solutions in the embodiments of the present invention or related technologies, the drawings used in the description of the embodiments or related technologies will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0045] Figure 1 This is a flowchart illustrating the implementation of a page operation collection method in an embodiment of the present invention.

[0046] Figure 2 This is a flowchart illustrating the implementation of a page operation playback method in an embodiment of the present invention.

[0047] Figure 3 This is a schematic diagram of a playback platform according to an embodiment of the present invention;

[0048] Figure 4This is a schematic diagram of the structure of a page operation acquisition device according to an embodiment of the present invention;

[0049] Figure 5 This is a schematic diagram of the structure of a page operation playback device according to an embodiment of the present invention;

[0050] Figure 6 This is a schematic diagram of the structure of a computer device according to an embodiment of the present invention. Detailed Implementation

[0051] The core of this invention is to provide a page operation acquisition method that can acquire and replay the interaction process of mobile devices while avoiding resource waste.

[0052] To enable those skilled in the art to better understand the present invention, the invention will be further described in detail below with reference to the accompanying drawings and specific embodiments. Obviously, the described embodiments are merely some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0053] Currently, there are generally two methods for replaying user actions on web pages. The first method involves collecting and storing static page text data for each page. This static text data includes: the Document Object Model (DOM) of each historical text object model corresponding to the page to be replayed, the corresponding CSS styles, and the first timestamp of each DOM. After storing the static page text data, a page view corresponding to each DOM is generated. Then, based on the first timestamp of each DOM, the page views corresponding to each DOM are sorted and displayed. Thus, based on the historical text object model (DOM), the corresponding CSS (Cascading Style Sheets), and the timestamp of each DOM, the page views corresponding to each DOM are sorted and displayed, achieving a visual replay of the page operation process. The disadvantage of this approach is that it requires storing the page's content, structure, and style data, which is a large amount of data, putting a great burden on network transmission and data storage devices, and also resulting in resource waste.

[0054] The second approach involves acquiring user behavior data when the user interacts with the page and storing this data according to preset rules. When a replay command is detected, the replay operation is performed based on the stored user behavior data. The recorded user behaviors include clicking the mouse, moving the mouse, and inputting information. The drawback is that the replay scope is limited to independent user actions on the page (such as inputting content or moving the mouse) and interactions with the server (such as submitting a form).

[0055] Mobile web pages frequently involve interactions with mobile devices, such as uploading photos from the phone's album, facial recognition, scanning QR codes, and obtaining current location information. Simultaneously, mobile devices also need to send push notifications and update their status to the page. The results of these interactions depend on both the user's actions and basic information about the mobile device, such as permission settings and whether the device is malfunctioning. When replaying a mobile web page, it's essential to include not only the user's normal actions and interactions with the server but also the user's interactions with the mobile device. This ensures the completeness and accuracy of the replay process. Since the results of these interactions are heavily dependent on the user's mobile device, this method does not and cannot replay the events that frequently involve interactions with mobile devices within mobile web pages, resulting in partial omissions in the replay process.

[0056] This application expands and optimizes upon the approach of the second solution, focusing on solving the problem of recording and replaying the interaction between web pages (including commonly used HTML5 pages) and mobile devices when replaying mobile pages.

[0057] Please refer to Figure 1 , Figure 1 This is a flowchart of a page operation collection method according to an embodiment of the present invention. The method includes the following steps:

[0058] S101. If a page call to a mobile device is triggered, record the call time;

[0059] When a user's actions on the page are about to trigger a capability call on the mobile device, the page will first record the current time as the call time so that the page actions can be reproduced later based on the call time.

[0060] S102. A call request is initiated to the mobile device through a two-way communication device, so that the mobile device responds to the call request and executes the corresponding call operation;

[0061] After intercepting the page's direct calls to the mobile device, the system initiates calls to the mobile device's capabilities through a two-way communication device, so that the mobile device can execute the corresponding operations upon receiving the call request.

[0062] In this embodiment, a two-way communication device refers to a device that enables bidirectional communication between a webpage and a mobile device. The specific type of device is not limited in this embodiment; for example, it could be a JSBridge. JSBridge uses a JavaScript (an interpreted scripting language often used to add interactive behaviors to HTML pages, providing users with a smoother and more aesthetically pleasing browsing experience) engine or a WebView (a control based on the WebKit engine used to display web pages) container as a medium, communicating through a protocol to achieve bidirectional communication between the mobile device and the webpage. In this application, the JSBridge page can utilize the capabilities of the mobile device, and similarly, the mobile device can also call the JavaScript interface of the page through the JSBridge, thus achieving bidirectional communication between the mobile device and the page. It should be noted that this embodiment only uses JSBridge as an example of a two-way communication device; other device types can be described in the same way as in this embodiment, and will not be elaborated further here.

[0063] S103. Obtain the callback information generated by the mobile device executing the call operation through the two-way communication device, and perform subsequent operations based on the callback information;

[0064] After receiving the call request, the mobile device will execute the corresponding capability to generate callback information, and then return the callback information required by the page to the page through a two-way communication device, so that the page can perform subsequent operations based on the callback information, thus realizing two-way communication between the page and the mobile device.

[0065] S104. Organize the call information to generate an interaction behavior log, and send the interaction behavior log to the storage database; the call information includes: callback information and call time.

[0066] After receiving the callback, the page combines the previously stored call information between the page and the mobile device, such as the call time and the name of the called capability, and sends it to the database (storage database, such as a cloud database) used to store page operation collection information for storage. Then, the callback information is used to execute subsequent page logic, thereby ensuring the continuity of user page operation execution.

[0067] The method of organizing information can be set according to the needs of subsequent information reading. For example, information can be serialized, which is not limited here.

[0068] In addition, this embodiment does not limit the specific types of information included in the collected and organized call information. It only takes the inclusion of callback information (based on the callback information, the call response operation on the mobile device can be simulated) and call time (based on the call time, the page operation corresponding to the playback time specified by the user can be determined) as an example. Other information can also be included, such as the triggering user, the type of mobile device, etc. The specific settings can be made according to the actual usage needs, which will not be elaborated here.

[0069] Based on the above description, the technical solution provided by this invention records the call time before the user interacts with the page and the mobile device, triggering a capability call on the mobile device. This allows for the determination of the corresponding call operation at different times. Then, a capability call is initiated to the mobile device via a two-way communication device, enabling the mobile device to perform the corresponding operation and generate callback information. The callback information required by the page is then returned to the page via the two-way communication device. Upon receiving the callback information, the page, along with the previously stored call time and other page-related call information to the mobile device, sends it to a storage database for storage. This information serves as the basis for page operation replay. Subsequent page logic is then executed using the callback information to ensure the continuity of user operations. This method can collect the interaction behavior between the page and the mobile device while ensuring the continuity of user page operations.

[0070] It should be noted that, based on the above embodiments, the present invention also provides corresponding improvements. In the preferred / improved embodiments, steps that are the same as or corresponding to those in the above embodiments can be referred to each other, and the corresponding beneficial effects can also be referred to each other; however, these will not be elaborated upon in the preferred / improved embodiments herein.

[0071] In the above embodiments, the interaction behavior between the page and the mobile device is serialized and stored. The stored information includes methods called on the mobile device within the page (such as accessing the photo album or obtaining location), the time of the interaction behavior, and the callback information of the mobile device, which can realize the collection of interaction behavior between the page and the mobile device. In order to further realize the complete and comprehensive collection of page operations and thus realize complete page operation playback, before recording the call time if the page calls the mobile device, the following steps can be further performed:

[0072] (1) Receive user actions on the page;

[0073] (2) Extract the retrospective information of the behavioral event and send the retrospective information to the storage database;

[0074] User-independent behavioral events are serialized and stored. The stored retrospective information includes: the type of behavioral event (such as click or input), the time when the behavioral event occurred, and the element object on the page that the behavioral event acted on (such as a button or input box on the page).

[0075] (3) If the page triggers a call to the server, extract the interaction behavior information from the logs recorded by the server and send the interaction behavior information to the storage database.

[0076] Meanwhile, when interacting with the server within the page, server-side logs (such as form submissions and query statuses) are stored. Information related to the interaction behavior is extracted and stored, which may include the time, the specific service name called, and the service's input and output data.

[0077] In addition to collecting data from mobile devices, this embodiment further collects independent user behavior events on the page and interaction information between the page and the server, covering the full response collection of user page operations, thereby realizing complete page operation process backtracking.

[0078] In addition to the information stored separately as described above, these three types of logs can further record the user's ID and basic device information, and store them in different modules of the cloud database for later use. This embodiment does not limit this.

[0079] Corresponding to the above embodiment of the page operation collection method, this embodiment of the invention also provides a page operation playback method, please refer to... Figure 2 , Figure 2 This is a flowchart of a page operation playback method according to an embodiment of the present invention. The method mainly includes the following steps:

[0080] S201. If the page triggers a replay of a call to a mobile device, determine the specified replay target; wherein, the replay target includes the object to be replayed and the replay time.

[0081] like Figure 3 The diagram illustrates a replay platform (user-side page). The replay platform can be configured with a search area, a replay path list display area, a single-path replay area, and a mobile device experience area. The search area allows users to search for all paths taken by a user within a given time period (from entering a business process page to exiting it constitutes one path). All paths are displayed in chronological order. Replay of a single path includes displaying basic user information, page name, page dwell time, a timeline of in-page operations, and playback controls. The platform supports scanning QR codes using mobile devices to experience the page flow in the replay area, providing a more realistic representation of the user's operation path.

[0082] When a user initiates commands such as start playback, pause playback, speed up playback, or change playback page on the playback platform, if the playback involves calling a mobile device for playback, step S201 is triggered to determine the playback target specified by the user. The playback target mainly includes information that can be used to indicate the playback behavior, such as the object to be played back and the playback time. The object to be played back can be a subject that can initiate the operation, such as a user or a host, which is common to users.

[0083] It should be noted that this embodiment mainly introduces the implementation method of call replay between the page and the mobile device, that is, the implementation method of operation replay that requires calling the capabilities of the mobile device. The replay of other operations can be implemented with reference to relevant existing technologies, and will not be described in detail here.

[0084] S202. Extract the corresponding interaction behavior logs from the storage database according to the playback target;

[0085] The interaction behavior log is generated according to the aforementioned page operation collection method embodiment, and the details can be found in the description of the above embodiment, which will not be repeated here.

[0086] Based on the playback target, this method extracts the corresponding stored interaction behavior logs from the storage database. It modifies the part of common playback methods that calls native capabilities via JSBridge to instead extract the corresponding interaction behavior logs and retrieve mobile device callback information.

[0087] This embodiment does not limit the specific extraction process. For example, one could first locate the operation time of the object to be replayed based on the replay time, and then match the corresponding interaction behavior logs based on the operation time and the information of the object to be replayed. Of course, other methods can also be used for log extraction, which will not be elaborated here. Optionally, a request can be sent to a log retrieval server to retrieve and extract log information. Unlike the deployment environment, the log retrieval server will not execute business logic, but will return the server-side log information of the user at that time based on the information of the object to be replayed and the replay time, thereby enabling the retracing of the content displayed on the user's page.

[0088] Furthermore, before retrieving the corresponding interaction logs from the storage database based on the playback target, the following steps can be performed to prompt the user to perform actions and increase user engagement:

[0089] (1) Determine the mobile device to be replayed and the name of its capabilities based on the playback target;

[0090] (2) Output prompt information based on the mobile device to be played back and the device capability name.

[0091] An optional prompt can be added to determine whether the user wants to continue using the mobile device to replay the capability. Of course, this setting can also be omitted, and this embodiment does not limit this.

[0092] In addition, the above information prompts can be executed in parallel with step S202 to improve execution efficiency.

[0093] S203. Parse the call information from the interaction behavior log and simulate the call operation based on the call information;

[0094] After parsing the call information from the interaction behavior log, the execution time of the capability is strictly simulated, and the operation is simulated based on the call information.

[0095] Specifically, the simulation can be implemented using Javascript code. Furthermore, the element affected by the current action can be highlighted, allowing those observing the replay to more clearly see the user's actions at that moment.

[0096] S204. Simulate subsequent operations based on the callback information in the call information.

[0097] After the replay is completed, the subsequent logic in the page is executed using the obtained mobile device callback information, thus completing the interactive replay.

[0098] Based on the above introduction, this method replaces the way JSBridge calls mobile device capabilities with the way it calls a log service to obtain user mobile device logs. This simulates the subsequent display style and logic changes after the page interacts with the mobile device, thus realizing the replay of the interaction behavior between the page and the mobile device. It should be noted that the above method can be implemented by embedding a custom plugin into the original page code. The plugin is only introduced during the construction of the replay environment code. This method is relatively safe and reliable, and also facilitates subsequent function maintenance. Alternatively, it can be implemented by distinguishing different logic based on the construction environment in the original code. The specific implementation method can be chosen according to the actual development and application needs. This embodiment does not limit this approach.

[0099] Corresponding to the above method embodiments, this invention also provides a page operation acquisition device. The page operation acquisition device described below can be referred to in correspondence with the page operation acquisition method described above.

[0100] See Figure 4 As shown, the device includes the following modules: triggering unit 110, forwarding unit 120, callback unit 130, and logging unit 140.

[0101] The triggering unit 110 is mainly used to record the call time if the page is triggered to call a mobile device;

[0102] Forwarding unit 120 is mainly used to initiate a call request to the mobile device through a two-way communication device, so that the mobile device can respond to the call request and execute the corresponding call operation;

[0103] The callback unit 130 is mainly used to obtain the callback information generated by the mobile device executing the call operation through the bidirectional communication device, and to perform subsequent operations based on the callback information;

[0104] Log unit 140 is mainly used to organize call information to generate interaction behavior logs and send the interaction behavior logs to the storage database; the call information includes: callback information and call time.

[0105] This device can collect playback information of interactive operations between web pages and mobile devices.

[0106] Corresponding to the above method embodiments, this invention also provides a page operation playback device. The page operation playback device described below can be referred to in correspondence with the page operation playback method described above.

[0107] See Figure 5 As shown, the device includes the following modules: target unit 210, extraction unit 220, first simulation unit 230 and second simulation unit 240.

[0108] The target unit 210 is mainly used to determine the specified playback target if the page calls and replays the mobile device; the playback target includes the object to be replayed and the playback time.

[0109] Extraction unit 220 is mainly used to extract the corresponding interaction behavior logs from the storage database according to the playback target; wherein, the interaction behavior logs are generated according to the page operation collection method;

[0110] The first simulation unit 230 is mainly used to parse the call information from the interaction behavior log and simulate the call operation based on the call information;

[0111] The second simulation unit 240 is mainly used to simulate subsequent operations based on the callback information in the call information.

[0112] This device can replay the interactive operations between web pages and mobile devices.

[0113] Corresponding to the above method embodiments, this invention also provides a computer device. The computer device described below and the page operation acquisition method described above can be referred to in correspondence.

[0114] The computer device includes:

[0115] Memory, used to store computer programs;

[0116] A processor is used to execute a computer program to implement the steps of the page operation acquisition method and / or page operation playback method in the above method embodiments.

[0117] For details, please refer to Figure 6 This is a schematic diagram illustrating the specific structure of a computer device provided in this embodiment. The computer device can vary significantly due to differences in configuration or performance. It may include one or more central processing units (CPUs) 322 (e.g., one or more processors) and a memory 332. The memory 332 stores one or more computer application programs 342 or data 344. The memory 332 can be temporary or persistent storage. The program stored in the memory 332 may include one or more modules (not shown in the diagram), each module including a series of instruction operations on the data processing device. Furthermore, the central processing unit 322 may be configured to communicate with the memory 332 and execute the series of instruction operations stored in the memory 332 on the computer device 301.

[0118] Computer device 301 may also include one or more power supplies 326, one or more wired or wireless network interfaces 350, one or more input / output interfaces 358, and / or one or more operating systems 341.

[0119] The steps in the page operation acquisition method and / or page operation playback method described above can be implemented by the structure of a computer device.

[0120] Corresponding to the above method embodiments, this invention also provides a readable storage medium. The readable storage medium described below can be referred to in conjunction with the methods described above.

[0121] A readable storage medium storing a computer program, wherein when the computer program is executed by a processor, it implements the steps of the page operation acquisition method and / or page operation playback method of the above method embodiments.

[0122] The readable storage medium can specifically be a USB flash drive, external hard drive, read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk, or any other readable storage medium capable of storing program code.

[0123] Those skilled in the art will further recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of both. To clearly illustrate the interchangeability of hardware and software, the components and steps of the various examples have been generally described in terms of functionality in the foregoing description. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementations should not be considered beyond the scope of the invention.

Claims

1. A method for collecting page operations, characterized in that, include: If a page is invoked for a mobile device, the invocation time is recorded; A call request is initiated to the mobile device through a two-way communication device, so that the mobile device responds to the call request and executes the corresponding call operation; The callback information generated by the mobile device executing the call operation is obtained through the bidirectional communication device, and subsequent operations are performed based on the callback information; The system organizes call information to generate an interaction behavior log and sends the log to a storage database. The call information includes the callback information and the call time. Before recording the call time if a page is triggered to access a mobile device, the system further includes: Receive user interaction events on the page; Extract the backtracking information of the behavioral event and send the backtracking information to the storage database; If the page triggers a call to the server, the interaction behavior information is extracted from the logs recorded by the server and sent to the storage database.

2. A page operation acquisition device, suitable for control using the page operation acquisition method described in claim 1, characterized in that, include: The triggering unit is used to record the call time if a page is triggered to call a mobile device; The forwarding unit is used to initiate a call request to the mobile device through a two-way communication device, so that the mobile device responds to the call request and executes the corresponding call operation; A callback unit is used to obtain callback information generated by the mobile device executing the call operation through the bidirectional communication device, and to perform subsequent operations based on the callback information; The log unit is used to organize call information to generate interaction behavior logs and send the interaction behavior logs to the storage database; wherein, the call information includes: the callback information and the call time.

3. A method for replaying page operations, characterized in that, include: If a page call to a mobile device is triggered for playback, the specified playback target is determined; wherein, the playback target includes the object to be played back and the playback time; According to the playback target, the corresponding interaction behavior log is extracted from the storage database; wherein, the interaction behavior log is generated according to the page operation collection method according to claim 1; The call information is parsed from the interaction behavior log, and the call operation is simulated based on the call information; The simulation of subsequent operations is performed based on the callback information in the call information.

4. The page operation playback method according to claim 3, characterized in that, The step of retrieving the corresponding interaction behavior logs from the storage database according to the playback target includes: The log retrieval server is invoked to extract the corresponding interaction behavior logs from the storage database based on the playback target.

5. The page operation playback method according to claim 3, characterized in that, The step of simulating the call operation based on the call information includes: The call operation is simulated based on the Javascript.

6. The page operation playback method according to claim 3, characterized in that, Before retrieving the corresponding interaction behavior logs from the storage database according to the playback target, the method further includes: The mobile device to be replayed and its capability name are determined based on the replay target. The system outputs prompt information based on the mobile device to be played back and the device capability name.

7. A page operation playback device, characterized in that, include: The target unit is used to determine the specified playback target if the page is triggered to play back the mobile device; wherein, the playback target includes the object to be played back and the playback time. An extraction unit is used to extract corresponding interaction behavior logs from a storage database according to the playback target; wherein the interaction behavior logs are generated according to the page operation collection method according to claim 1; The first simulation unit is used to parse the call information from the interaction behavior log and simulate the call operation based on the call information; The second simulation unit is used to simulate subsequent operations based on the callback information in the call information.

8. A computer device, characterized in that, include: Memory, used to store computer programs; A processor, configured to execute the computer program to implement the page operation acquisition method as described in claim 1, and / or the page operation playback step as described in any one of claims 3 to 6.

9. A readable storage medium, characterized in that, The readable storage medium stores a computer program that, when executed by a processor, implements the page operation acquisition method as described in claim 1, and / or the page operation playback steps as described in any one of claims 3 to 6.

Images