Page playback method and device

By acquiring and injecting page code, interface data and operation data, the user's operation process is realized, and the problem that the existing technology cannot meet the multi-account and multi-scene playback is solved, and the efficiency of user behavior tracking and page optimization is improved.

CN118916108AInactive Publication Date: 2024-11-08ZHEJIANG E COMMERCE BANK CO LTD
View PDF 5 Cites 0 Cited by

Patent Information

Application Number
CN202410990212.2
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-07-22
Publication Date
2024-11-08
Estimated Expiration
Not applicable · inactive patent

AI Technical Summary

Technical Problem

The existing UI recording and playback technology cannot meet the playback needs of different accounts in the same page scenario or multiple page scenarios, and cannot effectively track and reproduce user behavior and analyze user needs.

Method used

By receiving playback requests, the pre-collection of page code, interface data and operation data are obtained, and the page is injected into the page, and the page content and operation process are restored to realize the user's operation process playback on the page.

Benefits of technology

It realizes playback of different accounts in the same page scenario or multiple page scenarios, helping developers track user behavior, reproduce problems, analyze user needs, and optimize page design and user experience.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118916108A_ABST
    Figure CN118916108A_ABST
Patent Text Reader

Abstract

The embodiment of the invention discloses a page playback method and device. The method comprises the steps that according to a playback request, page codes, interface data and operation data which are collected in advance and related to a to-be-played-back page are obtained; injecting the page code and the interface data into the page, and restoring the page content; the operation data is injected into the page with the restored page content, and the operation process is restored; and playing back the restored page so as to play back the operation process of the user on the page.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] One or more embodiments of the present specification relate to the field of data processing technology, and in particular, to a page playback method and device. Background Art

[0002] As far as the promotion and application of websites are concerned, it is crucial to analyze user needs. Before analysis, it is necessary to collect the user's operation data on the page and replay the user's operation process on the page. By replaying user operation behavior, user behavior can be tracked so that developers can understand user behavior; user problems can also be reproduced to help developers locate the cause of the problem; user needs can also be analyzed to help developers optimize page design and functions and optimize user experience.

[0003] The UI recording and playback in the related playback technology is completed in a specific scenario through a fixed account, which cannot meet the playback needs of different accounts in the same page scenario or multiple page scenarios. Summary of the invention

[0004] One or more embodiments of the present specification describe a page playback method and device, which can extract the page code, interface data, and operation data of the historical user access pages collected in advance according to the playback needs, and restore and play back the user's operation process on the page.

[0005] In a first aspect, an embodiment of the present specification provides a page playback method, including:

[0006] Receive a playback request, wherein the playback request is used to request playback of the user's operation process on the page;

[0007] According to the playback request, obtain the pre-collected page code, interface data and operation data related to the requested playback page;

[0008] Inject page code and interface data into the page to restore page content;

[0009] Inject the operation data into the page that restores the page content to restore the operation process;

[0010] Respond to the playback request and replay the user's operation process on the page.

[0011] In a second aspect, the embodiment of the present specification provides a page playback device, a receiving module, receiving a playback request, wherein the playback request is used to request playback of a user's operation process on the page;

[0012] The acquisition module acquires the pre-collected page code, interface data and operation data related to the requested playback page according to the playback request;

[0013] The first restoration module injects the page code and interface data into the page to restore the page content;

[0014] The second restoration module injects the operation data into the page of the restored page content to restore the operation process;

[0015] The playback module responds to playback requests and plays back the user's operation process on the page.

[0016] In a third aspect, an embodiment of this specification provides an electronic device, including a processor and a memory;

[0017] The processor is connected to the memory;

[0018] The memory is used to store executable program code;

[0019] The processor runs a program corresponding to the executable program code by reading the executable program code stored in the memory, so as to execute the method described in the first aspect above.

[0020] In a fourth aspect, embodiments of this specification provide a computer storage medium having a computer program stored thereon, and when the computer program is executed by a processor, the method described in one or more embodiments of this specification is implemented.

[0021] The beneficial effects brought by the technical solutions provided by some embodiments of this specification include at least:

[0022] In one or more embodiments of the present specification, the page code, interface data and operation data related to the page to be replayed are obtained according to the playback request, the page code and interface data are injected into the page to restore the page content, and the operation data is injected into the page of the restored page content to restore the operation process, so that the user's operation process on the page can be replayed. Among them, the page code, interface data and operation data are pre-collected historical data. This method can meet the playback needs of different accounts in the same page scene or multiple page scenes, and thus facilitate developers to track user behavior, reproduce user problems, analyze user needs, etc. according to the playback content. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0024] Figure 1 This is a schematic diagram of a scene of page playback in an embodiment of this specification;

[0025] Figure 2 A flow chart of a page playback method provided in an embodiment of this specification;

[0026] Figure 3 A schematic diagram of the structure of a page playback device provided in an embodiment of this specification;

[0027] Figure 4 A schematic diagram of the structure of an electronic device provided in an embodiment of this specification. DETAILED DESCRIPTION

[0028] The technical solutions in the embodiments of this specification will be described clearly and completely below in conjunction with the drawings in the embodiments of this specification.

[0029] The terms "first", "second", "third", etc. in the description and claims of this specification and the above-mentioned drawings are used to distinguish different objects, rather than to describe a specific order. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions. For example, a process, method, system, product or device that includes a series of steps or units is not limited to the listed steps or units, but optionally includes steps or units that are not listed, or optionally includes other steps or units inherent to these processes, methods, products or devices.

[0030] Figure 1 A schematic diagram of a page playback scenario is shown. The computer device is a local device used by the demander to request page playback, which can be a PC (Personal Computer), tablet computer, laptop computer, mobile terminal, smart phone, etc. There is no restriction on the type of computer device. The demander is a person who needs to playback user operation behaviors, which can be a developer, user, etc. The demander sends a page operation playback request to the computer device, and the user's operation process on the page is played back by restoring the page content and operation data on the page.

[0031] See also Figure 2 A flow chart of a page playback method provided by an embodiment of this specification is shown.

[0032] like Figure 2 As shown, the method includes:

[0033] Step 102, receiving a playback request, wherein the playback request is used to request playback of the user's operation process on the page;

[0034] Step 104, according to the playback request, obtain the pre-collected page code, interface data and operation data related to the requested playback page;

[0035] Step 106, injecting the page code and interface data into the page to restore the page content;

[0036] Step 108, injecting the operation data into the page of restoring the page content, restoring the operation process;

[0037] Step 110, responding to the playback request, and playing back the user's operation process on the page.

[0038] The method of the embodiment of this specification is executed by the above-mentioned computer device.

[0039] The method obtains the page code, interface data and operation data related to the requested playback page according to the playback request, and then restores the page to achieve playback of the user's operation process on the page.

[0040] Next, each step will be described in detail.

[0041] In step 102, when the demander needs to know the user operation process of a certain page, a playback request is sent.

[0042] The demander can obtain all the page records visited by the user within a certain time (for example, a certain day) according to the user ID. When the demander selects the page to be replayed, the page ID of the page is obtained. At the same time, the operation time of the page and the business partition to which the page belongs are also obtained. Among them, the user ID is an ID defined by the backend management user, for example, an ID defined according to the sequence number of the user registration. Afterwards, the page ID of the page to be replayed, the operation time and the business partition to which the page belongs are formed into a playback request. The page ID is a page access link.

[0043] The operation time is used to represent the duration of the user's operation on this page, and the operation time is an interval time formed by the operation start time point and the operation end time point as endpoint values. For example, the operation time is (10:23-10:25) on May 1st.

[0044] The business partition to which the page belongs is used to identify which type of business the accessed page belongs to, and different business partitions need to be accessed using different interface data. For example, when the page is a learning web page, the business partition to which the page belongs is 01, and the required interface is interface 1. For another example, when the page is a game page, the business partition to which the page belongs is 02, and the required interface is interface 2. For another example, when the page is a financial page, the business partition to which the page belongs is 03, and the required interface is interface 3.

[0045] After receiving the playback request, step 104 is executed.

[0046] In step 104, according to the playback request, the pre-collected related information is obtained, that is, the page code, interface data and operation data related to the page requested to be played back.

[0047] Before executing step 102, the method of the embodiment of this specification further includes a pre-collection step, specifically including:

[0048] Step 1001, respectively collecting the page code, interface data and operation data of the page accessed by the user;

[0049] Step 1003, store the page code and the page ID in a first database in correspondence, store the interface data and the page ID in a second database in correspondence, and store the operation data and the page ID in a third database in correspondence.

[0050] When a user operates a page, the collection and storage process is executed. The above page code, interface data, and operation data are collected and stored respectively.

[0051] The page code is generally stored in a code repository, such as a gitlab repository. Set a scheduled task, for example, at the next moment after a user operates a page, collect the code of the relevant page from the code repository and store it in the first database. The first database can be an OB (Ocean Base) database.

[0052] The interface data generally includes the interface name, interface input and output parameters, etc. The call of the interface data is generally recorded in the bff log. The interface call records of the relevant pages in the bff log are collected, and the interface data is stored in the second database. The second database can be an ODPS (Open Data Processing Service) offline database.

[0053] The operation data includes operation information of all operations, and each operation information includes operation type and operation coordinate point. The operation type includes sliding operation and clicking operation. In addition, the operation type may also include input operation, but it is limited to input operation that does not involve personal privacy. For example, when the page is a learning page, the input operation refers to the input operation of the answer; for another example, when the page is a shopping page, the input operation refers to the input operation of information search; for another example, when the page is a financial page, the input operation refers to the input operation of the amount input.

[0054] Before collecting operation data, pre-set full tracking points on the page. Full tracking means that by loading a defined SDK code, the front end will automatically collect all events and report tracking data, which can present user operation behaviors. When configuring tracking points, configure the collection operation rules. Generally, sliding operations and click operations are collected. If necessary, input operations that do not involve personal privacy can also be collected. When a user performs the above operations on the page, the operation type, operation time and operation coordinate point can be obtained.

[0055] When the user completes a series of operations, all operation information in the operation data is arranged in chronological order to form an operation queue. For example, the operation queue is {click position 1 (15, 92), click position 2 (100, 50), click position 3 (80, 15)}.

[0056] The collected operation data is stored in a third database, which may be an ODPS (Open Data Processing Service) offline database.

[0057] In the above storage process, the page code, interface data, operation data and page code are stored in correspondence. Specifically, the page code and page ID are stored in correspondence in the first database. The business partition to which the page belongs, the page ID, and the interface data are stored in correspondence in the second database. The page ID, operation time, and operation data are stored in correspondence in the third database.

[0058] In this implementation, step 104 specifically includes:

[0059] Obtain a page code corresponding to the page ID from the first database; obtain interface data corresponding to the page ID and the business partition to which the page belongs from the second database; obtain operation data corresponding to the page ID and operation time from the third database.

[0060] In addition, during the pre-collection process, interface data and operation data can also be stored in the log.

[0061] The first log is used to store interface data within a short period of time, such as an sls log. The second database is used to store interface data for a longer period of time. For example, the first log is used to store interface data within three days, and the second database is used to store interface data over three days. The first log also periodically transfers interface data that is about to exceed three days to the second database for storage.

[0062] The second log is used to store operation data of a shorter period of time, such as an sls log. The third database is used to store operation data of a longer period of time. For example, the second log is used to store operation data within three days, and the third database is used to store operation data of more than three days. The second log also regularly transfers operation data that is about to exceed three days to the third database for storage.

[0063] In the above storage process, the page code, interface data, and operation data are stored in correspondence with the page code. Specifically, the page code and the page ID are stored in correspondence in the first database. The business partition to which the page belongs, the page ID, and the interface data are stored in correspondence in the first log or the second database. The page ID, operation time, and operation data are stored in correspondence in the second log or the third database.

[0064] In this embodiment, step 104 specifically includes:

[0065] Obtain the page code corresponding to the page ID from the first database; obtain the interface data corresponding to the page ID and the business partition to which the page belongs from the second database or log; obtain the operation data corresponding to the page ID and the operation time from the third database or log.

[0066] During the acquisition of interface data and operation data, it is necessary to determine whether the interface data is data collected in a short period of time or a long period of time. If it is data collected in a short period of time, the interface data can be obtained from the first log and the operation data can be obtained from the second log. If it is data collected in a long period of time, the interface data can be obtained from the second database and the operation data can be obtained from the third database.

[0067] In step 106, the page content is restored. The page code and the interface data can be injected into the page through a web page container or a headless browser to restore the page content.

[0068] In step 108, the operation process is restored. The operation data can be injected into the page through a web container or a headless browser to restore the operation process.

[0069] Afterwards, replay the page to replay the user's operation process on the page.

[0070] Specifically, the page code, such as HTML, CSS, JavaScript, etc., is first injected into the page, and then the interface data is injected. Then, the operation data is injected into the page that restores the page content in the form of an operation queue. After that, playback can be achieved by gradually executing each operation in the operation queue.

[0071] For example, when using a headless browser to restore and replay, inject HTML code, intercept HTTP requests and inject interface data. Call the API to gradually execute each operation in the operation queue.

[0072] For example, when using client software such as iframe to restore and replay, inject JavaScript code, then inject interception SDK code in front, and use postMessage or other forwarding proxy methods to inject interface data. Then, inject the operation data into the page that restores the page content in the form of an operation queue. After that, use the elementFromPoint method to gradually locate and execute each operation in the operation queue, and use the trigger method to execute specific operations to achieve playback.

[0073] The method of the embodiment of this specification can be applied to a variety of scenarios. The following description is based on learning and gaming scenarios, but is not limited to the above scenarios.

[0074] For example, when the page is a learning page, this method can be used to replay the student's operation process in the learning page. Inject code into the learning page, that is, perform full tracking configuration to collect the operations performed by students in the learning page. When the student clicks to select the question, clicks to select answer option A, clicks to cancel answer option A, and clicks to select answer option B, the collected operation data is {click position 1 (15,92), click position 2 (100,50), click position 3 (100,50), click position 4 (120,50)}. The above operation data is stored in the ODPS database.

[0075] When a teacher wants to understand the student's learning situation, he sends a playback request and obtains the page code, interface data and operation data of the learning page through the learning page ID. The method of the embodiment of this specification is used to realize page restoration and page playback. When a page is logged in and used by multiple student accounts, a page displays a question. The teacher understands the learning process of different students in the same question through playback, which helps the teacher analyze the student's learning behavior and improve the teaching quality. When a teacher needs to understand the learning process of a certain student, all page access records within a certain day can be obtained, and a playback request can be formed for each learning page to replay the student's operation process on each learning page to help the teacher analyze the student's learning behavior.

[0076] For example, when the page is a game page, this method can be used to replay the player's operation process in the game page. Inject code into the game page, that is, perform full tracking configuration to collect the operations performed by students in the learning page. When the player performs click←, click←, click↑, click↑ operations, the collected operation data is {click position 1 (15,50), click position 2 (10,50), click position 3 (10,55), click position 4 (10,60)}. The above operation data is stored in the ODPS database.

[0077] When a game developer wants to understand the game behavior of a player, a playback request is sent, and the page code, interface data, and operation data of the game page are obtained by learning the page ID. The method of the embodiment of this specification is used to implement page restoration and page playback. When a page is logged in and used by multiple player accounts, a page presents a game scene. Game developers use playback to understand the game process of multiple players in a certain game scene, and optimize game design by analyzing the player's behavior.

[0078] The above is a description of a specific embodiment of the present specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recorded in the claims can be performed in an order different from that in the embodiments and still achieve the desired results. In addition, the processes depicted in the drawings do not necessarily require the specific order or continuous order shown to achieve the desired results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0079] See also Figure 3 The structure diagram of a page playback device 1000 provided in an embodiment of this specification is shown.

[0080] like Figure 3 As shown, the device includes a receiving module 1001, an acquisition module 1002, a first restoration module 1003, a second restoration module 1004, and a playback module 1005, wherein:

[0081] The receiving module 1001 receives a playback request, where the playback request is used to request playback of the user's operation process on the page;

[0082] The acquisition module 1002 acquires the pre-collected page code, interface data and operation data related to the requested playback page according to the playback request;

[0083] The first restoration module 1003 injects the page code and interface data into the page to restore the page content;

[0084] The second restoration module 1004 injects the operation data into the page of the restored page content to restore the operation process;

[0085] The playback module 1005 responds to the playback request and plays back the user's operation process on the page.

[0086] The apparatus of the embodiments of this specification is set in a computer device.

[0087] The device obtains the page code, interface data and operation data related to the requested playback page according to the playback request, and then restores the page to realize the playback of the user's operation process on the page.

[0088] The device of the embodiment of this specification further includes a collection module 1006 and a storage module 1007 .

[0089] The collection module 1006 collects the page code, interface data and operation data of the page accessed by the user respectively;

[0090] The storage module 1007 stores the page code and the page ID in the first database in correspondence, stores the interface data and the page ID in the second database in correspondence, and stores the operation data and the page ID in the third database in correspondence.

[0091] The page code is generally stored in a code repository, such as a gitlab repository. Set a scheduled task, for example, at the next moment after a user operates a page, collect the code of the relevant page from the code repository and store it in the first database. The first database can be an OB (Ocean Base) database.

[0092] The interface data generally includes the interface name, interface input and output parameters, etc. The call of the interface data is generally recorded in the bff log. The interface call records of the relevant pages in the bff log are collected, and the interface data is stored in the second database. The second database can be an ODPS (Open Data Processing Service) offline database.

[0093] The operation data includes operation information of all operations, and each operation information includes operation type and operation coordinate point. The operation type includes sliding operation and clicking operation. In addition, the operation type may also include input operation, but it is limited to input operation that does not involve personal privacy. For example, when the page is a learning page, the input operation refers to the input operation of the answer; for another example, when the page is a shopping page, the input operation refers to the input operation of information search; for another example, when the page is a financial page, the input operation refers to the input operation of the amount input.

[0094] Before collecting operation data, pre-set full tracking points on the page. Full tracking means that by loading a defined SDK code, the front end will automatically collect all events and report tracking data, which can present user operation behaviors. When configuring tracking points, configure the collection operation rules. Generally, sliding operations and click operations are collected. If necessary, input operations that do not involve personal privacy can also be collected. When a user performs the above operations on the page, the operation type, operation time and operation coordinate point can be obtained.

[0095] When the user completes a series of operations, all operation information in the operation data is arranged in chronological order to form an operation queue. For example, the operation queue is {click position 1 (15, 92), click position 2 (100, 50), click position 3 (80, 15)}.

[0096] The collected operation data is stored in a third database, and the third database may be an ODPS (Open Data Processing Service) offline database.

[0097] The page code, interface data and operation data of the page where the operation occurs are collected in advance, and the relevant data is stored in the database. Then, the page code, interface data and operation data of the page to be played back are obtained according to the playback request, and the page is restored to realize the playback of the user's operation process on the page.

[0098] The receiving module parses the received playback request to obtain the page ID, the business partition to which the page belongs, and the operation time in the playback request.

[0099] The page ID is a page access link. The operation time is used to characterize the duration of the user's operation on this page. The operation time is an interval formed by the operation start time point and the operation end time point as endpoint values. The business partition to which the page belongs is used to identify which type of business the access page belongs to. Different business partitions need to use different interface data for access.

[0100] The acquisition module acquires the page code, interface data, and operation data related to the page ID according to the playback request. Specifically, the acquisition module includes:

[0101] A first acquisition unit acquires a page code corresponding to the page ID from a first database;

[0102] A second acquisition unit acquires interface data corresponding to the page ID and the business partition to which the page belongs from a second database;

[0103] The third acquisition unit acquires operation data corresponding to the page ID and the operation time from the third database.

[0104] In addition, the storage module 1007 also stores the interface data and the page ID in the first log in correspondence, and stores the operation data and the page ID in the second log in correspondence.

[0105] The first log is used to store interface data in a short period of time, such as an sls log. The second database is used to store interface data for a longer period of time. The second log is used to store operation data in a short period of time, such as an sls log. The third database is used to store operation data for a longer period of time.

[0106] Correspondingly, the second acquisition unit acquires interface data corresponding to the page ID and the business partition to which the page belongs from the second database or the first log; the third acquisition unit acquires operation data corresponding to the page ID and operation time from the third database or the second log.

[0107] During the acquisition of interface data and operation data, it is necessary to determine whether the interface data is data collected in a short period of time or a long period of time. If it is data collected in a short period of time, the interface data can be obtained from the first log and the operation data can be obtained from the second log. If it is data collected in a long period of time, the interface data can be obtained from the second database and the operation data can be obtained from the third database.

[0108] Afterwards, the first restoration module is used to restore the page content, and then the second restoration module is used to restore the operation process. The page code, the interface data and the operation data are injected into the page through the web page container or the headless browser to achieve restoration.

[0109] Finally, the playback module is used to replay the page, and the user's operation process on the page can be replayed.

[0110] The device of the embodiment of this specification can be applied to various scenarios. The following description is based on learning and gaming scenarios, but is not limited to the above scenarios.

[0111] For example, when the page is a learning page, this method can be used to replay the student's operation process in the learning page. Inject code into the learning page, that is, perform full tracking configuration to collect the operations performed by students in the learning page. When the student clicks to select the question, clicks to select answer option A, clicks to cancel answer option A, and clicks to select answer option B, the collected operation data is {click position 1 (15,92), click position 2 (100,50), click position 3 (100,50), click position 4 (120,50)}. The above operation data is stored in the ODPS database.

[0112] When a teacher wants to understand the student's learning situation, he sends a playback request and obtains the page code, interface data and operation data of the learning page through the learning page ID. The method of the embodiment of this specification is used to realize page restoration and page playback. When a page is logged in and used by multiple student accounts, a page displays a question. The teacher understands the learning process of different students in the same question through playback, which helps the teacher analyze the student's learning behavior and improve the teaching quality. When a teacher needs to understand the learning process of a certain student, all page access records within a certain day can be obtained, and a playback request can be formed for each learning page to replay the student's operation process on each learning page to help the teacher analyze the student's learning behavior.

[0113] For example, when the page is a game page, this method can be used to replay the player's operation process in the game page. Inject code into the game page, that is, perform full tracking configuration to collect the operations performed by students in the learning page. When the player performs click←, click←, click↑, click↑ operations, the collected operation data is {click position 1 (15,50), click position 2 (10,50), click position 3 (10,55), click position 4 (10,60)}. The above operation data is stored in the ODPS database.

[0114] When a game developer wants to understand the game behavior of a player, a playback request is sent, and the page code, interface data, and operation data of the game page are obtained by learning the page ID. The method of the embodiment of this specification is used to implement page restoration and page playback. When a page is logged in and used by multiple player accounts, a page presents a game scene. Game developers use playback to understand the game process of multiple players in a certain game scene, and optimize game design by analyzing the player's behavior.

[0115] See also Figure 4 A schematic diagram of the structure of an electronic device provided in an embodiment of this specification is shown.

[0116] like Figure 4 As shown, the electronic device 1100 may include: at least one processor 1101, at least one network interface 1104, a user interface 1103, a memory 1105 and at least one communication bus 1102.

[0117] The communication bus 1102 may be used to realize the connection and communication among the above-mentioned components.

[0118] The user interface 1103 may include buttons, and the optional user interface may also include a standard wired interface or a wireless interface.

[0119] The network interface 1104 may include, but is not limited to, a Bluetooth module, an NFC module, a Wi-Fi module, etc.

[0120] Among them, the processor 1101 may include one or more processing cores. The processor 1101 uses various interfaces and lines to connect the various parts of the entire electronic device 1100, and executes various functions and processes data of the routing device 1100 by running or executing instructions, programs, code sets or instruction sets stored in the memory 1105, and calling data stored in the memory 1105. Optionally, the processor 1101 can be implemented in at least one hardware form of DSP, FPGA, and PLA. The processor 1101 can integrate one or a combination of CPU, GPU, modem, etc. Among them, the CPU mainly processes the operating system, user interface, and application programs; the GPU is responsible for rendering and drawing the content to be displayed on the display screen; the modem is used to process wireless communications. It can be understood that the above-mentioned modem may not be integrated into the processor 1101, and it can be implemented separately through a chip.

[0121] Among them, the memory 1105 may include RAM or ROM. Optionally, the memory 1105 includes a non-transitory computer-readable medium. The memory 1105 can be used to store instructions, programs, codes, code sets or instruction sets. The memory 1105 may include a program storage area and a data storage area, wherein the program storage area may store instructions for implementing an operating system, instructions for at least one function (such as a touch function, a sound playback function, an image playback function, etc.), instructions for implementing the above-mentioned various method embodiments, etc.; the data storage area may store data involved in the above-mentioned various method embodiments, etc. The memory 1105 may also be at least one storage device located away from the aforementioned processor 1101. The memory 1105 as a computer storage medium may include an operating system, a network communication module, a user interface module and an application. The processor 1101 may be used to call the application stored in the memory 1105 and execute the method in one or more of the above-mentioned embodiments.

[0122] The embodiments of this specification also provide a computer-readable storage medium, which stores instructions, and when the instructions are executed on a computer or a processor, the computer or the processor executes one or more steps in the above embodiments. If the components of the above electronic device are implemented in the form of software functional units and sold or used as independent products, they can be stored in the computer-readable storage medium.

[0123] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function described in the embodiment of this specification is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted through the computer-readable storage medium. The computer instructions can be transmitted from a website site, computer, server or data center to another website site, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (Digital Subscriber Line, DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server, data center, etc. that contains one or more available media integrated. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a digital versatile disc (DVD)), or a semiconductor medium (eg, a solid state disk (SSD)).

[0124] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiments can be implemented by instructing the relevant hardware through a computer program, and the program can be stored in a computer-readable storage medium. When the program is executed, it can include the processes of the embodiments of the above-mentioned methods. The aforementioned storage medium includes: ROM, RAM, magnetic disk or optical disk and other media that can store program codes. In the absence of conflict, the technical features in this embodiment and the implementation scheme can be combined arbitrarily.

[0125] The embodiments described above are merely preferred embodiments of this specification and are not intended to limit the scope of this specification. Without departing from the design spirit of this specification, various modifications and improvements made to the technical solutions of this specification by ordinary technicians in this field should fall within the scope of protection determined by the claims of this specification.

Claims

1. Page playback method, including: Receive a playback request, wherein the playback request is used to request playback of the user's operation process on the page; According to the playback request, obtain the pre-collected page code, interface data and operation data related to the requested playback page; Inject page code and interface data into the page to restore page content; Inject the operation data into the page that restores the page content to restore the operation process; Respond to the playback request and replay the user's operation process on the page.

2. The method according to claim 1, further comprising: Collect page codes, interface data and operation data of user-accessed pages respectively; The page code and the page ID are stored in the first database in correspondence, the interface data and the page ID are stored in the second database in correspondence, and the operation data and the page ID are stored in the third database in correspondence.

3. The method according to claim 2, wherein the playback request includes a page ID, a business partition to which the page belongs, and an operation time; The step of obtaining, according to the playback request, the page code, interface data, and operation data collected in advance and related to the requested playback page, includes: Obtain a page code corresponding to the page ID from the first database; obtain interface data corresponding to the page ID and the business partition to which the page belongs from the second database; obtain operation data corresponding to the page ID and operation time from the third database.

4. The method according to claim 2, further comprising: The interface data and the page ID are stored in a first log in correspondence with each other, and the operation data and the page ID are stored in a second log in correspondence with each other.

5. The method according to claim 4, wherein the playback request includes a page ID, a business partition to which the page belongs, and an operation time; The step of obtaining, according to the playback request, the page code, interface data, and operation data collected in advance and related to the requested playback page, includes: Obtain the page code corresponding to the page ID from the first database; obtain the interface data corresponding to the page ID and the business partition to which the page belongs from the second database or the first log; obtain the operation data corresponding to the page ID and the operation time from the third database or the second log.

6. According to the method described in claim 2, the operation data is collected by pre-setting a full amount of embedding points on the page. 7 . The method according to claim 1 , wherein the operation types of the operation data to be collected include sliding operations and clicking operations.

8. According to the method of claim 1, the operation data includes operation information of all operations, each operation information includes an operation type and an operation coordinate point; all operation information in the operation data is arranged in chronological order to form an operation queue.

9. According to the method of claim 1, the page code, the interface data and the operation data are injected into the page through a web page container or a headless browser.

10. A page playback device, comprising: A receiving module receives a playback request, wherein the playback request is used to request playback of the user's operation process on the page; The acquisition module acquires the pre-collected page code, interface data and operation data related to the requested playback page according to the playback request; The first restoration module injects the page code and interface data into the page to restore the page content; The second restoration module injects the operation data into the page of the restored page content to restore the operation process; The playback module responds to playback requests and plays back the user's operation process on the page.

11. The apparatus according to claim 10, further comprising: The collection module collects the page code, interface data and operation data of the page visited by the user; The storage module stores the page code and the page ID in a first database in correspondence, stores the interface data and the page ID in a second database in correspondence, and stores the operation data and the page ID in a third database in correspondence.

12. The device according to claim 11, wherein the playback request includes a page ID, a business partition to which the page belongs, and an operation time; The acquisition module comprises: A first acquisition unit acquires a page code corresponding to the page ID from a first database; A second acquisition unit acquires interface data corresponding to the page ID and the business partition to which the page belongs from a second database; The third acquisition unit acquires operation data corresponding to the page ID and the operation time from the third database. 13 . The device according to claim 11 , wherein the storage module further stores the interface data and the page ID in a first log in correspondence with each other, and stores the operation data and the page ID in a second log in correspondence with each other.

14. The device according to claim 13, wherein the playback request includes a page ID, a business partition to which the page belongs, and an operation time; The acquisition module comprises: A first acquisition unit acquires a page code corresponding to the page ID from a first database; A second acquisition unit acquires interface data corresponding to the page ID and the business partition to which the page belongs from the second database or the first log; The third acquisition unit acquires operation data corresponding to the page ID and the operation time from the third database or the second log.

15. According to the device of claim 11, the operation data is collected by pre-setting a full amount of embedding points on the page.

16. The device according to claim 10, wherein the operation types of the operation data to be collected include sliding operations and clicking operations.

17. The device according to claim 10, wherein the operation data comprises operation information of all operations, each operation information comprises an operation type and an operation coordinate point; and all operation information in the operation data is arranged in chronological order to form an operation queue.

18. The device according to claim 10, wherein the page code, the interface data and the operation data are injected into the page through a web page container or a headless browser.

19. Electronic equipment, including processor and memory; The processor is connected to the memory; The memory is used to store executable program code; The processor runs a program corresponding to the executable program code by reading the executable program code stored in the memory, so as to execute the method according to any one of claims 1 to 9.

20. A computer-readable storage medium having a computer program stored thereon, wherein the computer program, when executed by a processor, implements the method according to any one of claims 1 to 9.

Citation Information

Patent Citations

  • Operation playback method and system for webpage terminal

    CN110109836A

  • Event playback method and device

    CN110795311A

  • Visualization processing method and device for data

    CN113505329A

  • Page operation recording method and device, page operation playback method and device, server and medium

    CN116302258A

  • Method and device for automatically burying points

    WO2017084508A1