CN113448817A

CN113448817A - Page screen recording method and device and storage medium

Info

Publication number: CN113448817A
Application number: CN202110716048.2A
Authority: CN
Inventors: 胡明飞
Original assignee: Weikun Shanghai Technology Service Co Ltd
Current assignee: Weikun Shanghai Technology Service Co Ltd
Priority date: 2021-06-25
Filing date: 2021-06-25
Publication date: 2021-09-28

Abstract

The embodiment of the application discloses a page screen recording method, a page screen recording device and a storage medium, which can be applied to the field of security monitoring. The method comprises the following steps: when a page recording request aiming at a target service is received, generating a target tracking identifier aiming at the target service, and acquiring page data of an initial service page and page change data of the initial service page; when a page jump execution instruction is received, jumping from an initial service page to a jump service page with a target tracking identifier, and acquiring page data of the jump service page and page change data of the jump service page; and generating screen recording data according to the acquired page data, the page change data and the target tracking identifier, and sending the screen recording data to a server. By adopting the method and the device, the screen recording data of the service page aiming at the target service can be conveniently acquired.

Description

Page screen recording method and device and storage medium

Technical Field

The present application relates to the field of security monitoring, and in particular, to a method and an apparatus for recording a screen on a page, and a storage medium.

Background

At present, scenes needing page recording are often involved, so that compliance judgment, task learning and the like can be conveniently carried out according to recorded page data. At present, when page recording is carried out, a service page in a service execution process is mainly clicked, then data is reported for recording, if user behaviors are to be recorded more accurately, more clicking operations need to be carried out in the service page, the cost for recording the user behaviors is greatly improved, and the clicking operations are relatively complex. Therefore, how to conveniently acquire the record of the user behavior becomes an urgent problem to be solved.

Disclosure of Invention

The embodiment of the application provides a page screen recording method, a page screen recording device and a storage medium, which can conveniently acquire screen recording data of a service page aiming at a target service.

In a first aspect, an embodiment of the present application discloses a page screen recording method, where the method includes:

when a page recording request aiming at a target service is received, generating a target tracking identifier aiming at the target service; the service pages of the target service comprise a plurality of service pages, and the service pages comprise an initial service page and at least one jump service page;

displaying the initial service page, and acquiring page data of the initial service page and page change data of the initial service page;

generating first screen recording data aiming at the initial service page according to the page data of the initial service page, the page change data of the initial service page and the target tracking identification;

when a page jump execution instruction is received, jumping from the initial service page to the jump service page with the target tracking identifier, and acquiring page data of the jump service page and page change data of the jump service page;

generating second screen recording data aiming at the jump service page according to the page data of the jump service page, the page change data of the jump service page and the target tracking identification;

and sending the first screen recording data and the second screen recording data to a server.

In a second aspect, an embodiment of the present application discloses another page screen recording method, where the method includes:

receiving a plurality of screen recording data sent by a client, wherein the screen recording data comprises page data of a service page, page change data in the service page and a tracking identifier of a service corresponding to the service page;

acquiring a target tracking identifier of a target service, and determining a plurality of screen recording data aiming at the target service from the plurality of screen recording data according to the target tracking identifier;

analyzing the multiple screen recording data aiming at the target service to obtain page data and page change data of multiple service pages corresponding to the target service, and generating a restored service page corresponding to the target service according to the page data and page change data of the multiple service pages corresponding to the target service;

and playing back the restored service page according to the acquisition time of the page data and the page change data, and generating a target video aiming at the target service.

In a third aspect, an embodiment of the present application discloses a page screen recording device, where the device includes:

the system comprises a receiving unit, a processing unit and a processing unit, wherein the receiving unit is used for generating a target tracking identifier aiming at a target service when receiving a page recording request aiming at the target service; the service pages of the target service comprise a plurality of service pages, and the service pages comprise an initial service page and at least one jump service page;

the display unit is used for displaying the initial service page and acquiring page data of the initial service page and page change data of the initial service page;

the processing unit is used for generating first screen recording data aiming at the initial service page according to the page data of the initial service page, the page change data of the initial service page and the target tracking identifier;

the receiving unit is further configured to jump from the initial service page to the jump service page with the target tracking identifier when a page jump execution instruction is received, and acquire page data of the jump service page and page change data of the jump service page;

the processing unit is further configured to generate second screen recording data for the jump service page according to the page data of the jump service page, the page change data of the jump service page, and the target tracking identifier;

and the sending unit is used for sending the first screen recording data and the second screen recording data to a server.

In a fourth aspect, an embodiment of the present application discloses another page screen recording device, where the device includes:

the system comprises a receiving unit, a display unit and a display unit, wherein the receiving unit is used for receiving a plurality of screen recording data sent by a client, and the screen recording data comprises page data of a service page, page change data in the service page and a tracking identifier of a service corresponding to the service page;

the acquisition unit is used for acquiring a target tracking identifier of a target service and determining a plurality of screen recording data aiming at the target service from the plurality of screen recording data according to the target tracking identifier;

the processing unit is used for analyzing the multiple screen recording data aiming at the target service to obtain page data and page change data of multiple service pages corresponding to the target service, and generating a restored service page corresponding to the target service according to the page data and the page change data of the multiple service pages corresponding to the target service;

the processing unit is further configured to play back the restored service page according to the acquisition time of the page data and the page variation data, and generate a target video for the target service.

In a fifth aspect, an embodiment of the present application discloses a terminal, including a processor, a memory, and a network interface, where the processor, the memory, and the network interface are connected to each other, where the memory is used to store a computer program, and the computer program includes program instructions, and the processor is configured to call the program instructions to execute the method of the first aspect.

In a sixth aspect, an embodiment of the present application discloses a server, including a processor, a memory, and a network interface, where the processor, the memory, and the network interface are connected to each other, where the memory is used to store a computer program, and the computer program includes program instructions, and the processor is configured to call the program instructions to execute the method of the second aspect.

In a seventh aspect, an embodiment of the present application discloses a computer-readable storage medium, which stores a computer program, the computer program comprising program instructions, which, when executed by a processor, cause the processor to perform the method of the first or second aspect.

In the embodiment of the application, a page recording request for a target service can be received, a target tracking identifier for the target service is generated, page data and page change data of a plurality of service pages in the target service execution process are recorded, screen recording data are generated and sent to a server, so that the server can receive the screen recording data, and the screen recording data corresponding to the target service are converted into a target video according to the target tracking identifier. Therefore, screen recording data of the complete process aiming at the target service can be conveniently acquired.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings needed to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the following description are some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.

Fig. 1 is a schematic structural diagram of a page screen recording system according to an embodiment of the present application;

fig. 2 is a schematic flowchart of a page screen recording method according to an embodiment of the present application;

fig. 3 is a schematic flowchart of a method for acquiring screen recording data according to an embodiment of the present application;

fig. 4 is a schematic flowchart of another page screen recording method according to an embodiment of the present application;

fig. 5 is a schematic structural diagram of a page screen recording device according to an embodiment of the present application;

fig. 6 is a schematic structural diagram of another page screen recording device according to an embodiment of the present application;

fig. 7 is a schematic structural diagram of a terminal according to an embodiment of the present application;

fig. 8 is a schematic structural diagram of a server according to an embodiment of the present application.

Detailed Description

The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some, but not all, embodiments of the present application. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.

The technical scheme of the present application can be applied to a page screen recording system, please refer to fig. 1, and fig. 1 is a schematic structural diagram of a page screen recording system provided in an embodiment of the present application. As shown in fig. 1, the page screen recording system may include a client and a server. The client can realize complete screen recording of a service comprising a plurality of service pages, and specifically, screen recording data for the service can be obtained by acquiring page data and page change data of each service page and associating the plurality of service pages with a tracking identifier which uniquely identifies the service. The server can receive each screen recording data, can obtain the screen recording data aiming at the service based on the tracking identification, the page data, the page change data and the like of the service, and can further generate a video by combining the screen recording data of the service so as to conveniently check the operation process or the content change and the like in the service process at any time.

For example, the client can generate a target tracking identifier for a target service when receiving a page recording request for the target service; displaying an initial service page, and acquiring page data of the initial service page and page change data of the initial service page; generating first screen recording data aiming at the initial service page according to the page data of the initial service page, the page change data of the initial service page and the target tracking identification; when a page jump execution instruction is received, jumping from an initial service page to a jump service page with a target tracking identifier, and acquiring page data of the jump service page and page change data of the jump service page; generating second screen recording data aiming at the jump service page according to the page data of the jump service page, the page change data of the jump service page and the target tracking identification; and sending the first screen recording data and the second screen recording data to a server. The server can receive a plurality of screen recording data sent by the client; acquiring a target tracking identifier of a target service, and determining a plurality of screen recording data aiming at the target service from a plurality of screen recording data according to the target tracking identifier; analyzing the multiple screen recording data aiming at the target service to obtain page data and page change data of multiple service pages corresponding to the target service, and generating a restoration service page corresponding to the target service according to the page data and the page change data of the multiple service pages corresponding to the target service; and playing back and restoring the service page according to the acquisition time of the page data and the page change data, and generating a target video aiming at the target service. Therefore, screen recording data aiming at the target service can be obtained through the client, and the obtained screen recording data is converted into the target video through the server, so that the user behavior aiming at the target service is recorded through the video format, and the visualization of the user behavior record is realized.

Optionally, the client may operate in a terminal, and the terminal may be a smart phone, a tablet computer, a notebook computer, a desktop computer, and the like, which is not described herein again. A server may also be referred to as a server, a service device, or other names, and the present application is not limited thereto. The server may be an independent physical server, a server cluster or a distributed system formed by a plurality of physical servers, or a cloud server providing basic cloud computing services such as cloud service, a cloud database, cloud computing, cloud storage, domain name service, security service, and the like, which is not limited herein. The terminal and the server may be directly or indirectly connected through wired or wireless communication, and the application is not limited herein.

The technical scheme of the application can be applied to various scenes, such as compliance judgment, task learning, change feature extraction and the like according to the recorded page data, and the application is not limited. For example, with the rapid development of internet technology, the judgment of user behavior compliance in internet products is gradually gaining attention. The user behavior can be recorded by judging the user behavior compliance in the Internet product, and the illegal behavior in the recorded user behavior is identified.

It is to be understood that the foregoing scenarios are only examples, and do not constitute a limitation on application scenarios of the technical solutions provided in the embodiments of the present application, and the technical solutions of the present application may also be applied to other scenarios. For example, as can be known by those skilled in the art, with the evolution of system architecture and the emergence of new service scenarios, the technical solution provided in the embodiments of the present application is also applicable to similar technical problems.

Based on the above description, the embodiment of the application provides a page screen recording method. Referring to fig. 2, fig. 2 is a schematic flowchart of a page screen recording method according to an embodiment of the present disclosure. The method may be applied to the client and executed by the client, or may be executed by the terminal, and the following description uses the terminal as an example. As shown in fig. 2, the method may include steps S201-S206.

S201, when a page recording request aiming at the target service is received, generating a target tracking identifier aiming at the target service.

The service pages of the target service comprise a plurality of service pages, and the plurality of service pages comprise an initial service page and at least one jump service page. The target business may be any business processed by the client in various industries, such as investment business in the financial investment domain, reimbursement business in the financial domain, and the like, without limitation. The service page may indicate a page displayed in the client for executing the target service. Optionally, the service page may be a page of a browser, and is configured to display a web page for a target service, where the web page may be a Single page application (SPA for short), and the SPA jump may be regarded as a new page, that is, in the execution process of the target service, each time the SPA jump is performed, a service page is added to the target service. Further optionally, the web page may be an html page, an html5 page, or other web pages, which is not limited herein.

The page recording request may be a request for instructing a client to start page recording, and optionally, the page recording request may carry account information (such as a user identity identifier) of a user logged in the client, and may also include time point information when the page recording request is received, which is not limited herein. The target tracking information may be a unique identification number for the target service, so as to determine a plurality of service pages for the target service through the target tracking identification. In some scenarios, the target tracking identifier may also be referred to as a traceId, or the like, without limitation.

In one possible implementation, receiving a page recording request for a target service may include the following steps: determining the risk level of the target service; and when a service starting request aiming at the target service is received and the risk level of the target service indicates that the target service needs to be recorded, confirming that a page recording request aiming at the target service is received. The risk level of the target service may be used to indicate whether a screen needs to be recorded in the execution process of the target service (i.e., whether page data and page change data of a service page of the target service need to be acquired). Optionally, the risk level of the target service may be determined according to the importance of the target service and information such as an influence degree brought by an illegal action of the target service, and if the target service is important and the influence degree brought by the illegal action of the target service is large, it is determined that the risk level indication for the target service needs to record a screen of the target service. The service start request for the target service may be an operation of receiving a click instruction to start executing a control of the target service, or may be an operation of receiving a voice instruction to start executing the target service, or may be an operation of receiving a gesture operation instruction to start executing the target service, or may be an operation of generating an operation start request, which is not limited herein. It can be understood that when a service start request for a target service is received and the risk level of the target service indicates that the target service needs to be recorded, the client receives a page recording request for the target service, so as to generate a target tracking identifier for the target service, thereby reducing recording of unimportant user behaviors in the client, reducing transmission of redundant data, and improving efficiency of page screen recording.

In one possible embodiment, the target tracking identifier may be a string of numbers or letters or visible characters, for example, the target tracking identifier may be a string of 32 hexadecimal numbers. The visible characters are used to indicate characters that can be entered via the keyboard. Optionally, the target tracking id may include a timestamp, a random number, a number arranged according to the order of the generation time, and the like, which is not limited herein. The timestamp may be a time carried in the page recording request, or may be a time for generating the target tracking identifier, which is not limited herein. For example, the target tracking identifier may be expressed as sixteen octets (i.e. 32 hexadecimal digits), and the 32 hexadecimal digits are separated by hyphen, so as to obtain 5 groups of digits, such as 8-4-4-4-12, and a total of 36 characters (including 32 hexadecimal digits and 4 hyphens), so as to use the string of characters as the target tracking identifier.

S202, displaying the initial service page, and acquiring page data of the initial service page and page change data of the initial service page.

For example, after the user receives the page recording request for the target service, the client jumps from the service page a to the service page B, and then determines that the service page B is the initial service page for the target service. The page data may indicate document object model structure (DOM structure) data in the business page indicating a DOM structure in the business page, and the page variation data may indicate structural data in which the DOM structure in the business page is varied. It can be understood that the acquiring of the page data of the initial service page and the page change data of the initial service page may be acquiring of DOM structure data and DOM structure change data of the initial service page.

In one possible implementation, the DOM structure data of the initial service page may be represented as a DOM tree, and the DOM structure of the initial service page may be composed of a plurality of nodes, such as element nodes, text nodes, attribute nodes or comment nodes, and so on. Optionally, the type of the DOM structure change data for the initial service page may be data indicating that a value of a text node changes, or may be data indicating that an attribute node changes, or may be data indicating that a node is directly deleted from the DOM structure or indirectly removed through a sub-tree, or may be data indicating that a node is directly inserted into the DOM structure or data indicating that a node is indirectly inserted into the DOM structure through a sub-tree, and the like, which is not limited herein.

In one possible implementation, the obtaining of the page data of the initial service page and the page change data of the initial service page may include the following steps: determining target characteristic information of the page data to be acquired, where the target characteristic information includes a target data type and/or a target element identifier, and for example, the target characteristic information of the page data to be acquired may be determined according to a risk level of a target service; and further, page data and page change data in the initial service page can be obtained according to the target characteristic information. For example, the risk level may be used to indicate target characteristic information for the target service record screen, such as a target data type, where the target data type may indicate a node type of a DOM structure corresponding to page data of an initial service page, such as several nodes in annotation nodes that determine to acquire or not acquire the initial service page, so that a partial data amount of acquired page data may be reduced, and efficiency of acquiring page data may be improved. Optionally, the target data type may further indicate a type of DOM structure change data corresponding to the page data of the initial service page. For example, it may be determined to obtain only data of a text node that changes, or to obtain only data of an inserted node or a deleted node, and so on, and is not limited herein. For another example, the target element identifier of the page data to be acquired may be acquired to acquire the change data of the position where the target element identifier is located in the service page, for example, in the initial service page, as the page change data, and obtain the screen recording data including the page data (which may include other data except the data of the position where the target element identifier is located) and the page change data in the service page, for example, in the initial service page, so as to quickly determine the operation behavior and the change content of the data corresponding to the target element identifier.

It can be understood that the target feature information of the acquired page data and page change data determined according to the risk level of the target service may be determined when a page screen recording request for the target service is received, so that the page data of the target feature information is acquired when an initial service page is displayed, the page change data of the target feature information is monitored, and the page change data corresponding to the feature information is acquired only when the page change data of the target feature information is monitored. For example, if the risk level of the target service is relatively high and the importance level of the target service is relatively high, the full amount of page data and various types of page change data can be acquired when the page data and the page change data are acquired, and if the risk level of the target service is relatively low, important information in the execution process of the target service is most likely to be data of a change of a text node, when the page data and the page change data are acquired, partial types of page data can be acquired, and the page change data when the text node changes are monitored and acquired. Therefore, the storage of redundant data can be reduced, and the data volume of screen recording data can be reduced.

In one possible embodiment, when the initial service page is displayed, a page identifier for the initial service page may also be generated. The page identifier for the initial service page may be a unique identifier for the initial service page, so that the page data and the page change data for the initial service page are determined by the page identifier. That is, the obtained page data of the initial service page and the page data are both marked by the same page identifier. The generated relevant description for the page identifier may refer to the relevant description of the target tracking identifier in step S201, which is not described herein again. It is understood that the information such as the length or number of the page identifier and the information such as the length and numbering method of the target tracking identifier may be the same or different, but both the page identifier and the target tracking identifier have uniqueness.

S203, generating first screen recording data aiming at the initial service page according to the page data of the initial service page, the page change data of the initial service page and the target tracking identification.

The first screen recording data may be used to indicate screen recording data for an initial service page, and the first screen recording data may be used to restore the initial service page. Optionally, the first screen recording data may further include a page identifier.

In a possible implementation manner, generating the first screen recording data for the initial service page may further include the following steps: compressing the page data of the initial service page, the page change data of the initial service page and the target tracking identifier to obtain compressed screen recording data; and encrypting the compressed screen recording data to obtain first screen recording data aiming at the initial service page. The compressed screen recording data line is used for indicating data obtained after compression processing is performed on the page data of the initial service page, the page change data of the initial service page and the target tracking identifier, the data can be compressed through a compression algorithm, the compression processing means that on the premise that useful information is not lost, the data volume is reduced to reduce a storage space, and the transmission, storage and processing efficiency of the data is improved, for example, the compression processing is performed through a Lempel-Ziv (LZ) algorithm. Optionally, the page identifiers may be compressed together, so as to obtain compressed screen recording data. The compressed screen recording data is encrypted by an encryption algorithm, for example, an RC4, RC2, DES or AES series encryption algorithm is adopted, so that the safety of the data can be improved, and the risk of data leakage is reduced. Optionally, when the first screen recording data is generated, only the data that needs to be sent to the server may be compressed, or only the data that needs to be sent to the server may be encrypted, which is not limited herein.

Optionally, the encryption manner may be determined according to service feature information of the target service, where the service feature information includes a risk level, a service type, and the like, or may be determined according to feature information of a user corresponding to the target service, and the feature information of the user may include an authority feature of the user, an importance of the user, and the like, which is not limited herein. Further optionally, the corresponding relationship between the encryption mode and the service feature information of the target service may be preset, or the feature information of the user corresponding to the encryption mode and the target service may be preset, which is not limited in the present application. For example, if the risk level of the target service indicates that the screen recording data related to the target service needs to be encrypted with high intensity, the screen recording data of the target service is encrypted by adopting an encryption mode with a higher safety factor. Thereby contributing to the flexibility and reliability of data encryption processing.

S204, when a page jump execution instruction is received, jumping from the initial service page to the jump service page with the target tracking identifier, and acquiring page data of the jump service page and page change data of the jump service page.

The page jump execution instruction is used for instructing the page displayed by the client to jump from one service page to another service page. Optionally, the page jump execution instruction may be an operation of the client responding to a click to acquire a control of another service page, and confirming that the page jump execution instruction is received; the page jump execution instruction can also be used for confirming that the client side needs to jump to another service page according to the received information and confirming that the page jump instruction is received. The jump service page may be a service page to which the client jumps after receiving the page jump execution instruction. For example, when the user receives a page jump execution instruction and jumps from the service page C to the service page D, the service page D is used as a jump service page.

In a possible implementation manner, the target tracking identifier carried in the target tracking identifier jumps from the initial service page to the jump service page, and the target tracking identifier may be carried from the initial service page to the jump service page by a Uniform Resource Locator (URL), that is, the target tracking identifier is carried in the URL of the initial service page and the jump service page, so as to ensure that the target tracking identifiers in the same service execution process are the same. It can be understood that, in the target service execution process, when jumping from one jump service page to another jump service page, a target tracking identifier is also carried to jump from the one jump service page to another jump service page, so that in the target service execution process, regardless of how many jump service pages are jumped to, each service page for the target service has the same target tracking identifier, for example, the target tracking identifier can be carried in a URL of each service page (including the initial service page and all the jump service pages) corresponding to the target service.

In a possible implementation manner, the obtaining of the page data of the jump service page and the description of the page change data of the jump service page may refer to the obtaining of the page data of the initial service page and the description of the page change data of the initial service page in step S202, which is not described herein again. It can be understood that, the step may be referred to for the method for acquiring the page data and the page change data of all the jump service pages of the target service.

S205, second screen recording data aiming at the jump service page is generated according to the page data of the jump service page, the page change data of the jump service page and the target tracking identification.

The description of step S203 may be referred to for the related description of this step, and is not repeated herein.

In a possible implementation manner, if the target service can include a sub-service, the following steps can be executed, namely receiving a page recording request aiming at the target sub-service, generating a sub-service tracking identifier aiming at the target sub-service, and acquiring page data and page change data in the execution process of the target sub-service; binding the sub-service tracking identifier with the target tracking identifier; and generating sub-service screen recording data according to the page data and the page change data in the target sub-service execution process, the sub-service tracking identifier and the target tracking identifier, and sending the sub-service screen recording data to the server. The target sub-service is used for indicating a sub-service under the target service, and the page recording request for the target sub-service may be that, in the execution process of the target service, when a sub-service start instruction for the target sub-service is detected, it is determined that the page recording request for the target sub-service is received, so as to generate a sub-service tracking identifier for the target sub-service. For example, the target service is a service that needs to generate a document a, but if the document a needs to be generated and a document B and a document C need to be made, the target service may be determined as 3 sub-services (a service that generates the document a, a service that generates the document B, and a service that generates the document C), and when a page recording request for each sub-service is received, sub-service tracking identification information for the corresponding sub-service is generated, so as to distinguish data of a plurality of sub-services in the target service, thereby enhancing a connection between the sub-services, and avoiding that data for each service process is too much, which results in too long time for generating a target video for the target service and is inconvenient to refer.

In a possible implementation manner, if a service identification number is generated in the execution process of the target service process, the service identification number is bound with the target tracking identification, so that the relevance between the service flow and the screen recording data for the target service is improved, and the query is facilitated. The service identification number can be a document number, a serial number, a order number and the like generated in the service execution process, so that screen recording data of the service aiming at the target service identification number can be quickly inquired in the subsequent inquiry process. For example, in an order payment process, an order number is generated, and the order number is used as the service identification number to be bound with the target tracking identification, so that screen recording data of the order payment process indicated by the order number can be inquired subsequently according to the order number.

S206, the first screen recording data and the second screen recording data are sent to a server.

The server may be configured to receive, process, and store the first screen recording data and the second screen recording data, for example, the first screen recording data and the second screen recording data may be converted into a video format for storage. It can be understood that sending the first screen recording data and the second screen recording data to the server may be a unified sending manner, for example, after the target service is executed, the first screen recording data and the second screen recording data are sent to the server in a unified manner; for example, after the first screen recording data is obtained, the first screen recording data is sent to the server, and after the second screen recording data is obtained, the second screen recording data is sent to the server, which is not limited herein.

In a possible implementation manner, when the first screen recording data and the second screen recording data are sent to the server, the service identification number, the user identity information (such as a user identity identification number), the screen recording start time, the screen recording end time, and other related data of the first screen recording data or the second screen recording data may also be correspondingly sent to the server, so that the server queries the screen recording data or generates a video for a target service according to the related data.

It can be understood that the second screen recording data represents screen recording data of a jump service page in the service execution process, and screen recording data of any jump service page in the service execution process can be referred to as second screen recording data. The first screen recording data represents screen recording data of an initial service page in a service execution process, and the screen recording data of the initial service page of any service can be called as first screen recording data. The first screen recording data and the second screen recording data may also be collectively referred to as screen recording data.

In a possible implementation manner, when the screen recording data is sent to the server, the screen recording data of the current service page may not be completely sent to the server due to a skip of the service page or a poor network condition, and the terminal may store the screen recording data of the current service page into a storage area of the terminal, for example, in the terminal through an IndexDB (locally stored API provided by a browser). When the client jumps to the next service page, whether the IndexDB has the screen recording data which is not sent to the service page (such as the first screen recording data and the second screen recording data) or not is detected, and if the IndexDB has the screen recording data, the screen recording data in the storage area is sent to the server.

Here, an example of a business process is described, which describes an execution process of a business and an acquisition process of page data and page change data. Referring to fig. 3, fig. 3 is a schematic flowchart of a method for acquiring screen recording data according to an embodiment of the present application. As shown in fig. 3, when the terminal receives a page recording request for a target service (i.e. step 301), the terminal displays a service page 1 (i.e. an initial service page), and acquires page data and change data of the service page 1 to generate screen recording data corresponding to the service page 1 (i.e. step 302), when a page jump execution instruction is detected, jumps from the service page 1 to a service page 2, acquires page data and change data of the service page 2 to generate screen recording data corresponding to the service page 2 (i.e. step 303), and similarly, after jumping from the service page 2 to a service page 3, acquires page data and change data of the service page 3 to generate screen recording data corresponding to the service page 3 (i.e. step 304), until the target service is ended (i.e. step 305), so that screen recording data for the target service can be obtained, specifically including screen recording data for the service page 1, and aiming at the screen recording data of the service page 2 and the screen recording data of the service page 3, and sending the screen recording data to the server.

In the embodiment of the application, a page recording request for a target service can be received, a target tracking identifier for the target service is generated, page data and page change data of a plurality of service pages in the target service execution process are recorded, screen recording data are generated and sent to a server, so that the server can receive the screen recording data, and the screen recording data corresponding to the target service are converted into a target video according to the target tracking identifier. Therefore, the screen recording data of the complete process aiming at the target service can be conveniently acquired, and the recording cost is favorably reduced.

Referring to fig. 4, fig. 4 is a schematic flowchart of another page screen recording method according to an embodiment of the present application. The method can be applied to the server and executed by the server. The method may comprise steps S401-S404.

S401, receiving a plurality of screen recording data sent by a client.

The screen recording data includes page data of a service page, page change data in the service page, and a tracking identifier of a service corresponding to the service page, for example, each screen recording data includes page data of one service page, page change data in the service page, and a tracking identifier of a service corresponding to the service page. For example, the plurality of screen recording data may include the first screen recording data, the second screen recording data, and the like in fig. 2. The page data of the service page is used for indicating document object model structure (DOM structure) data in the service page, and the page change data of the service page can indicate structure data of DOM structure change in the service page. It can be understood that, corresponding to the screen recording data generated by the client, the screen recording data received by the server may further include a page identifier.

In a possible implementation manner, when receiving multiple screen recording data sent by the client, the server may further receive related data such as a service identification number, user identity information (such as a user identity number), screen recording start time, and screen recording end time corresponding to the screen recording data, so as to facilitate the server to query the screen recording data or generate a video for a target service according to the related data.

S402, acquiring a target tracking identifier of the target service, and determining a plurality of screen recording data aiming at the target service from the plurality of screen recording data according to the target tracking identifier.

The target tracking identifier may be a unique identifier generated in the target service execution process, so that a plurality of screen recording data for the target service may be determined from a plurality of screen recording data in the server through the target tracking identifier.

In a possible implementation manner, if the target tracking identifier is bound with a service identifier number of the target service in the client, a plurality of screen recording data for the target service can be determined from a plurality of screen recording data in the server through the service identifier. Therefore, screen recording data of specific services can be conveniently inquired.

S403, analyzing the multiple screen recording data aiming at the target service to obtain page data and page change data of multiple service pages corresponding to the target service, and generating a restored service page corresponding to the target service according to the page data and page change data of the multiple service pages corresponding to the target service.

The introduction of the page data and the page variation data of the service page may refer to the related description in fig. 2, which is not described herein again.

The restored service page is used for indicating a page restored according to the page data and the page change data of the service page, and it can be understood that the restored service page may be the same as or different from the service page displayed when the service page is acquired, and if the restored service page is different from the service page displayed when the service page is acquired, this may be because the acquired page data and the page change data of the service are only data of the target data type, or may be because the rendering effect of the server is different from the rendering effect of the client, which is not limited herein.

In a possible implementation manner, the screen recording data may further include a page identifier of each service page, and then generating the restored service page may include the following steps: determining page data and page change data aiming at the same service page from a plurality of screen recording data according to the page identification; converting the page data and the page change data of the same service page into one or more DOM structures aiming at the same service page; and rendering one or more DOM structures to obtain a restored service page corresponding to each service page. The page identifier may be an identifier number for each service page, and therefore, the page data and the page change data corresponding to each service page may be determined by the page identifier, so that the page data and the page change data for the same service page are determined from a plurality of screen recording data for the target service. Rendering the one or more DOM structures may be rendering the DOM structures through a browser, so as to obtain a restored service page corresponding to each service page. Optionally, Rendering the DOM structure through the browser may construct a Rendering Tree (Rendering Tree) through the DOM structure and the CSS rule Tree, and then obtain the restore service page through a reflow process and the like. It can be understood that, for the same service page, a DOM structure can be generated according to the page data of the service page, so as to obtain a corresponding restored service page, and the DOM structure corresponding to the page data can be adjusted based on the page change data on the basis of the page data of the service page, so as to obtain an adjusted DOM structure, obtain a restored service page after page change, and thus obtain a restored service page for the same service page.

In a possible implementation manner, if the screen recording data (such as the first screen recording data or the second screen recording data) sent by the client is screen recording data that is subjected to compression processing and encryption processing, after a plurality of screen recording data for the target service are determined, corresponding decryption processing may be performed on the plurality of screen recording data according to an encryption processing method, and decompression processing may be performed on the plurality of screen recording data after the decryption processing, so that page data and page change data of a plurality of service pages corresponding to the target service may be obtained. It can be understood that, if the client performs only encryption processing on the data to be sent to the server when generating the screen recording data for the target service, the server also performs only corresponding decryption processing on the screen recording data for the target service, and if the client performs only compression processing on the data to be sent to the server when generating the screen recording data for the target service, the server also performs only corresponding decompression processing on the screen recording data for the target service. It can be understood that the encryption mode of the client corresponds to the decryption mode of the server.

S404, playing back the restored service page according to the acquisition time of the page data and the page change data, and generating a target video for the target service.

The obtaining time is used for indicating the time point when the client obtains the page data and the page change data. The restoring service page playback and restoration service page according to the acquisition time of the page data and the page change data may be to play the restored service pages according to the acquisition time sequence, for example, there are 3 service pages for the target service, which are respectively a service page a, a service page B, and a service page C according to the acquisition time, and each service page corresponds to 4 restored service pages, so that 4 restored service pages of the service page a, 4 restored service pages of the service page B, and 4 restored service pages of the service page C, which are played according to the acquisition time sequence, can be obtained according to the acquisition time, and thus, the acquired page data and the page change data can be visualized, and the page change of the user in the process of executing the target service is played back, so as to record the user behavior.

The target video may be a video played back according to the restore service page, and the target video may be a video in any video format, such as an MPEG format, an AVI format, a naiv format, an ASF format, and so on. That is to say, a corresponding target video is generated according to screen recording data, so that the screen recording data can be stored in a video format, and therefore the integrity of a user behavior record indicated by the screen recording data can be maintained, if the screen recording data is directly stored, a page rendered according to the screen recording data may have an error, because some node information (such as a link or a picture) in the page data in the generated screen recording data may fail, and a page generated according to the screen recording data with the failed node information may be incomplete or have an error.

In one possible implementation, generating a target video for a target service may be generated from a headless browser, which is a web browser without a Graphical User Interface (GUI), typically controlled through a programming or command line interface. For example, a chord headless browser is called to generate a target video, a chord self-contained desktop capture (desktop capture) method is used, the method can capture the media stream information of the current page, and the media stream is converted into a segment of video and stored by using getUserMedia and MediaRecorder methods, so that the target video corresponding to the target service can be obtained.

In a possible implementation manner, the screen recording data corresponding to the sub-service can be further determined according to the sub-service identifier of the target service, and a video corresponding to the sub-service can be generated. For example, if the received screen recording data for the target service has a sub-service tracking identifier, acquiring screen recording data corresponding to each sub-service tracking identifier according to the sub-service tracking identifier, generating videos for the sub-services according to the screen recording data corresponding to the sub-service tracking identifier, and constructing an association relationship between the videos for the sub-services of the same target service, where the videos corresponding to the screen recording data for each sub-service have the same target tracking identifier but different sub-service tracking identifiers.

In a possible implementation manner, the screen recording data sent by the client may be processed in batch, which specifically includes the following steps: receiving a screen recording data batch processing instruction, wherein the screen recording data batch processing instruction carries batch processing conditions; acquiring screen recording data to be processed according to batch processing conditions; and determining a plurality of screen recording data aiming at the same service from the screen recording data to be processed according to the tracking identifier. The screen recording data batch acquisition instruction may indicate an instruction for acquiring screen recording data corresponding to a batch processing condition in batch, where the batch processing condition is used to indicate a condition that the screen recording data to be processed satisfies, where the batch processing condition may be that acquisition time of the screen recording data is within a target time region, where a user corresponding to the screen recording data is a target user, and where a service type of the screen recording data is a target service type, and the like, and where no limitation is made here. The screen recording data to be processed can be data corresponding to batch processing conditions, so that the screen recording data to be processed can be obtained from the screen recording data in the server through the batch processing conditions, then a plurality of screen recording data for the same service are determined from the screen recording data to be processed according to the tracking identification in the screen recording data to be processed, the screen recording data to be processed corresponding to each service are processed respectively, and videos for each service are obtained. Therefore, videos corresponding to the services can be generated in batches, and the video generation efficiency is improved.

In a possible implementation manner, when generating the target video, specific information of the video, such as a length and a width of the video, pixels of the video, a storage format of the video (e.g., an MPEG format, an AVI format, a naii format, an ASF format), and the like, may also be customized, which is not limited herein. The watermark of the target video can be customized, so that the copyright of the video or video content information and the like can be clarified in the video. The generated target video can be encrypted, so that only a user knowing the password can check the target video, and the safety of the target video is improved.

In a possible implementation manner, the corresponding target video generated by the screen recording data can be further marked according to the related data of the screen recording data, so that the corresponding target video can be queried through the marking. The related data may be a service identification number, acquisition time of screen recording data, user information, a service type, and the like, which is not limited herein.

In the embodiment of the application, a plurality of screen recording data sent by a client can be received, a target tracking identifier of a target service is obtained, a plurality of screen recording data for the target service are determined from the plurality of screen recording data according to the target tracking identifier, and a restoration service page corresponding to the target service is generated according to the plurality of screen recording data corresponding to the target service, so that the restoration service page is played back, and a target video for the target service is generated. Therefore, screen recording data of the complete process aiming at the target service can be conveniently acquired.

Referring to fig. 5, fig. 5 is a schematic structural diagram of a page screen recording device according to an embodiment of the present application. Alternatively, the data processing apparatus may be provided in a terminal. As shown in fig. 5, the page screen recording apparatus described in this embodiment may include:

a receiving unit 501, configured to generate a target tracking identifier for a target service when a page recording request for the target service is received; the service pages of the target service comprise a plurality of service pages, and the service pages comprise an initial service page and at least one jump service page;

a display unit 502, configured to display the initial service page, and obtain page data of the initial service page and page change data of the initial service page;

a processing unit 503, configured to generate first screen recording data for the initial service page according to the page data of the initial service page, the page change data of the initial service page, and the target tracking identifier;

the receiving unit 501 is further configured to, when a page jump execution instruction is received, jump from the initial service page to the jump service page with the target tracking identifier, and acquire page data of the jump service page and page change data of the jump service page;

the processing unit 503 is further configured to generate second screen recording data for the jump service page according to the page data of the jump service page, the page change data of the jump service page, and the target tracking identifier;

a sending unit 504, configured to send the first screen recording data and the second screen recording data to a server.

In one implementation, the processing unit 503 is further configured to:

determining a risk level of the target business;

when a service starting request aiming at the target service is received and the risk level of the target service indicates that the target service is recorded, determining to receive a page recording request aiming at the target service;

the processing unit 503 is specifically configured to:

determining target characteristic information of the page data to be acquired according to the risk level of the target service, wherein the target characteristic information comprises a target data type or a target element identifier;

and acquiring page data and page change data in the initial service page according to the target characteristic information.

In an implementation manner, the processing unit 503 is specifically configured to:

compressing the page data of the initial service page, the page change data of the initial service page and the target tracking identifier to obtain compressed screen recording data;

and encrypting the compressed screen recording data to obtain the first screen recording data aiming at the initial service page.

In one implementation manner, the target service includes a target sub-service, and the processing unit 503 is further configured to:

receiving a page recording request aiming at the target sub-service, generating a sub-service tracking identifier aiming at the target sub-service, and acquiring page data and page change data in the target sub-service execution process;

binding the sub-service tracking identifier with the target tracking identifier;

and generating sub-service screen recording data according to the page data and the page change data in the target sub-service execution process, the sub-service tracking identifier and the target tracking identifier, and sending the sub-service screen recording data to a server.

Referring to fig. 6, fig. 6 is a schematic structural diagram of another page screen recording device according to an embodiment of the present application. Alternatively, the data processing apparatus may be provided in a server. As shown in fig. 6, the page screen recording apparatus described in this embodiment may include:

a receiving unit 601, configured to receive multiple screen recording data sent by a client, where the screen recording data includes page data of a service page, page change data in the service page, and a tracking identifier of a service corresponding to the service page;

an obtaining unit 602, configured to obtain a target tracking identifier of a target service, and determine, according to the target tracking identifier, multiple screen recording data for the target service from the multiple screen recording data;

the processing unit 603 is configured to analyze the multiple screen recording data for the target service, obtain page data and page change data of multiple service pages corresponding to the target service, and generate a restored service page corresponding to the target service according to the page data and page change data of the multiple service pages corresponding to the target service;

the processing unit 603 is further configured to play back the restored service page according to the acquisition time of the page data and the page change data, and generate a target video for the target service.

In an implementation manner, the multiple screen recording data for the target service further includes a page identifier of each service page in multiple service pages corresponding to the target service, and the processing unit 603 is specifically configured to:

determining page data and page change data aiming at the same service page from the plurality of screen recording data according to the page identification;

converting the page data and page change data of the same service page into one or more DOM structures aiming at the same service page;

and rendering the one or more DOM structures to obtain a restored service page corresponding to each service page.

In an implementation manner, the processing unit 603 is specifically configured to:

decrypting the plurality of screen recording data aiming at the target service to obtain decrypted screen recording data;

and decompressing the decrypted screen recording data to obtain page data and page change data of a plurality of service pages corresponding to the target service.

It can be understood that each functional unit of the page screen recording device of this embodiment can be specifically implemented according to the method in the foregoing method embodiment in fig. 2 or fig. 4, and the specific implementation process thereof may refer to the description related to the method embodiment in fig. 2 or fig. 4, which is not described herein again.

Referring to fig. 7, fig. 7 is a schematic structural diagram of a terminal according to an embodiment of the present disclosure. The terminal described in this embodiment includes: a processor 701, a memory 702. Optionally, the server may further include a network interface 703 or a power supply module. Data may be exchanged between the processor 701, the memory 702, and the network interface 703.

The Processor 701 may be a Central Processing Unit (CPU), and may also be other general purpose processors, Digital Signal Processors (DSP), Application Specific Integrated Circuits (ASIC), Field-Programmable Gate arrays (FPGA) or other Programmable logic devices, discrete Gate or transistor logic devices, discrete hardware components, and so on. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.

The network interface 703 may include an input device such as a control panel, a microphone, a receiver, etc., and/or an output device such as a display screen, a transmitter, etc., to name but a few. For example, in an application embodiment, the network interface may include a receiver and a transmitter.

The memory 702, which may include both read-only memory and random-access memory, provides program instructions and data to the processor 701. A portion of the memory 702 may also include non-volatile random access memory. For example, the processor 701, when calling the program instruction, is configured to perform:

In one implementation, the processor 701 is further configured to:

determining a risk level of the target business;

the processor 701 is specifically configured to:

In one implementation, the processor 701 is specifically configured to:

In an implementation manner, the target service includes a target sub-service, and the processor 701 is specifically configured to:

Referring to fig. 8, fig. 8 is a schematic structural diagram of a server according to an embodiment of the present disclosure. The server described in this embodiment includes: a processor 801 and a memory 802. Optionally, the server may further include a network interface 803 or a power supply module. Data may be exchanged between the processor 801, the memory 802, and the network interface 803.

The Processor 801 may be a Central Processing Unit (CPU), and may be other general purpose Processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), an off-the-shelf Programmable Gate Array (FPGA) or other Programmable logic device, discrete Gate or transistor logic device, discrete hardware component, or the like. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.

The network interface 803 may include an input device such as a control panel, a microphone, a receiver, etc., and/or an output device such as a display screen, a transmitter, etc., to name but a few. For example, in an application embodiment, the network interface may include a receiver and a transmitter.

The memory 802, which may include both read-only memory and random-access memory, provides program instructions and data to the processor 801. A portion of the memory 802 may also include non-volatile random access memory. For example, the processor 801, when calling the program instructions, is configured to perform:

In an implementation manner, the multiple screen recording data for the target service further includes a page identifier of each service page in multiple service pages corresponding to the target service, and the processor 801 is specifically configured to:

In one implementation, the processor 801 is specifically configured to:

The embodiment of the present application also provides a computer-readable storage medium, in which program instructions are stored, and when the program is executed, some or all of the steps of the method in the embodiment corresponding to fig. 2 or fig. 4 may be included. The computer-readable storage medium may mainly include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application program required for at least one function, and the like; the storage data area may store data created according to the use of the blockchain node, and the like. The block chain is a novel application mode of computer technologies such as distributed data storage, point-to-point transmission, a consensus mechanism and an encryption algorithm. A block chain (Blockchain), which is essentially a decentralized database, is a series of data blocks associated by using a cryptographic method, and each data block contains information of a batch of network transactions, so as to verify the validity (anti-counterfeiting) of the information and generate a next block. The blockchain may include a blockchain underlying platform, a platform product service layer, an application service layer, and the like. Optionally, data related to the present application, such as screen recording data, video, etc., may be stored in the blockchain. For example, the server may block nodes in a chain of blocks.

It should be noted that, for simplicity of description, the above-mentioned embodiments of the method are described as a series of acts or combinations, but those skilled in the art should understand that the present application is not limited by the order of acts described, as some steps may be performed in other orders or simultaneously according to the present application. Further, those skilled in the art should also appreciate that the embodiments described in the specification are preferred embodiments and that the acts and modules referred to are not necessarily required in this application.

Those skilled in the art will appreciate that all or part of the steps in the methods of the above embodiments may be implemented by associated hardware instructed by a program, which may be stored in a computer-readable storage medium, and the storage medium may include: flash disks, Read-Only memories (ROMs), Random Access Memories (RAMs), magnetic or optical disks, and the like.

Embodiments of the present application also provide a computer program product or computer program comprising computer instructions stored in a computer-readable storage medium. The computer instructions are read by a processor of a computer device from a computer-readable storage medium, and the computer instructions are executed by the processor to cause the computer device to perform the steps performed in the embodiments of the methods described above. Alternatively, the computer device may be a terminal or a server, etc.

The page screen recording method, the page screen recording device and the storage medium provided by the embodiment of the application are described in detail, a specific example is applied in the description to explain the principle and the implementation of the application, and the description of the embodiment is only used for helping to understand the method and the core idea of the application; meanwhile, for a person skilled in the art, according to the idea of the present application, there may be variations in the specific embodiments and the application scope, and in summary, the content of the present specification should not be construed as a limitation to the present application.

Claims

1. A page screen recording method is characterized by comprising the following steps:

2. The method of claim 1, further comprising:

determining a risk level of the target business;

the acquiring the page data of the initial service page and the page change data of the initial service page includes:

3. The method according to claim 1, wherein the generating first screen recording data for the initial service page according to the page data of the initial service page, the page change data of the initial service page, and the target tracking identifier includes:

4. The method of any of claims 1-3, wherein the target service comprises a target sub-service, the method further comprising:

5. A page screen recording method is characterized by comprising the following steps:

6. The method according to claim 5, wherein the plurality of screen recording data for the target service further includes a page identifier of each service page in a plurality of service pages corresponding to the target service;

the analyzing the multiple screen recording data for the target service to obtain page data and page change data of multiple service pages corresponding to the target service, and generating a restored service page corresponding to the target service according to the page data and page change data of the multiple service pages corresponding to the target service, includes:

7. The method according to claim 5, wherein the analyzing the multiple screen recording data for the target service to obtain page data and page change data of multiple service pages corresponding to the target service includes:

8. A page screen recording device, comprising:

9. A page screen recording device, comprising:

10. A computer-readable storage medium, characterized in that the computer-readable storage medium stores a computer program comprising program instructions that, when executed by a processor, cause the processor to carry out the method according to any one of claims 1-7.