Information recording method and device, information storage method, device and system

Abstract

One or more embodiments of the present specification provide an information recording method and device, an information storage method, device and system, wherein the information recording method includes: for a minimum business processing event of a target business triggered based on a user operation behavior, determining a target page element in a user access page involved in executing the minimum business processing event; and obtaining description information of the user operation behavior on the user access page. Based on the characteristic information of the determined target page element and the obtained description information, generate user behavior record information corresponding to the minimum business processing event. With the minimum business processing event as the minimum information upload node, send the user behavior record information of each minimum business processing event in the business processing link of the target business to the server.

Description

Technical Field

[0001] This document relates to the field of computer technology, and in particular to an information recording method and device, an information storage method, device and system. Background Art

[0002] At present, with the rapid development of Internet technology, the Internet has been widely used in people's daily study, work and life. People's daily affairs can be processed and presented through the Internet. Among them, online business processing services provided to users based on Internet technology are becoming more and more popular among users. For example, users can complete online insurance business processing, financial management business processing, etc. through applications installed on the client. Usually, during the business processing process, users need to provide information related to the business processing and perform operations related to the business processing, such as clicking a confirmation button, signing, etc.

[0003] However, after the online business is completed, disputes often occur, such as the user is unable to enjoy the corresponding service due to incorrect information provided by the user, or the user does not acknowledge that he or she has handled the relevant business because the business did not achieve the user's expected results. There are problems such as shirking responsibility and causing many troubles to users and service providers. Summary of the invention

[0004] The purpose of one or more embodiments of this specification is to provide an information recording method. The information recording method includes:

[0005] For the minimum business processing event of the target business triggered by the user operation behavior, determine the target page element in the user access page involved in executing the minimum business processing event; and obtain the description information of the user operation behavior on the user access page. Generate user behavior record information corresponding to the minimum business processing event based on the characteristic information and the description information of the target page element. Take the minimum business processing event as the minimum information upload node, and send the user behavior record information of each minimum business processing event in the business processing link of the target business to the server.

[0006] The purpose of one or more embodiments of this specification is to provide an information storage method. The information storage method includes:

[0007] Receive user behavior record information of each minimum business processing event in the business processing link of the target business sent by the client; wherein the minimum business processing event is a business processing event triggered by a user operation behavior, and the user behavior record information is generated based on the target page element in the user access page involved in executing the minimum business processing event and the description information of the user operation behavior on the user access page. Store the user behavior record information based on the upload node identifier corresponding to each of the minimum business processing events.

[0008] The purpose of one or more embodiments of this specification is to provide an information storage method. Applied to a server accessing a blockchain, the information storage method includes:

[0009] Receive user behavior record information of each minimum business processing event in the business processing link of the target business sent by the client; wherein the minimum business processing event is a business processing event triggered by a user operation behavior, and the user behavior record information is generated based on the target page element in the user access page involved in executing the minimum business processing event and the description information of the user operation behavior on the user access page. Based on the upload node identifier corresponding to each of the minimum business processing events, upload the user behavior record information to the blockchain.

[0010] The purpose of one or more embodiments of the present specification is to provide an information recording device. The information recording device includes:

[0011] A target page element determination module, which determines the target page element in the user access page involved in executing the minimum business processing event of the target business triggered by the user operation behavior. A behavior description information determination module, which obtains the description information of the user operation behavior on the user access page. A behavior record information generation module, which generates user behavior record information corresponding to the minimum business processing event based on the characteristic information of the target page element and the description information. A behavior record information upload module, which uses the minimum business processing event as the minimum information upload node and sends the user behavior record information of each minimum business processing event in the business processing link of the target business to the server.

[0012] The purpose of one or more embodiments of this specification is to provide an information storage device. The information storage device includes:

[0013] A behavior record information receiving module receives user behavior record information of each minimum business processing event in the business processing link of the target business sent by the client; wherein the minimum business processing event is a business processing event triggered by a user operation behavior, and the user behavior record information is generated based on the target page element in the user access page involved in executing the minimum business processing event and the description information of the user operation behavior on the user access page. A behavior record information storage module stores the user behavior record information based on the upload node identifier corresponding to each of the minimum business processing events.

[0014] The purpose of one or more embodiments of this specification is to provide an information storage device. Set on a server connected to a blockchain, the information storage device includes:

[0015] A behavior record information receiving module receives user behavior record information of each minimum business processing event in the business processing link of the target business sent by the client; wherein the minimum business processing event is a business processing event triggered by a user operation behavior, and the user behavior record information is generated based on the target page element in the user access page involved in executing the minimum business processing event and the description information of the user operation behavior on the user access page. A behavior record information chaining module uploads the user behavior record information to the blockchain based on the upload node identifier corresponding to each of the minimum business processing events.

[0016] One or more embodiments of the present specification aim to provide an information recording device, comprising: a processor; and a memory arranged to store computer-executable instructions.

[0017] When the computer executable instructions are executed, the processor determines the target page element in the user access page involved in executing the minimum business processing event of the target business triggered by the user operation behavior; and obtains the description information of the user operation behavior on the user access page. According to the characteristic information of the target page element and the description information, the user behavior record information corresponding to the minimum business processing event is generated. With the minimum business processing event as the minimum information upload node, the user behavior record information of each minimum business processing event in the business processing link of the target business is sent to the server.

[0018] One or more embodiments of the present specification provide an information storage device, comprising: a processor; and a memory arranged to store computer-executable instructions.

[0019] When the computer executable instructions are executed, the processor receives user behavior record information of each minimum business processing event in the business processing link of the target business sent by the client; wherein the minimum business processing event is a business processing event triggered by a user operation behavior, and the user behavior record information is generated based on the target page element in the user access page involved in executing the minimum business processing event and the description information of the user operation behavior on the user access page. Based on the upload node identifier corresponding to each of the minimum business processing events, the user behavior record information is stored.

[0020] One or more embodiments of the present specification provide an information storage device, comprising: a processor; and a memory arranged to store computer-executable instructions.

[0021] When the computer executable instructions are executed, the processor receives user behavior record information of each minimum business processing event in the business processing link of the target business sent by the client; wherein the minimum business processing event is a business processing event triggered based on user operation behavior, and the user behavior record information is generated based on the target page element in the user access page involved in executing the minimum business processing event and the description information of the user operation behavior on the user access page. Based on the upload node identifier corresponding to each of the minimum business processing events, the user behavior record information is uploaded to the blockchain.

[0022] The purpose of one or more embodiments of the present specification is to provide a storage medium for storing computer executable instructions. When the executable instructions are executed by the processor, for the minimum business processing event of the target business triggered by the user operation behavior, determine the target page element in the user access page involved in executing the minimum business processing event; and obtain the description information of the user operation behavior on the user access page. Based on the characteristic information of the target page element and the description information, generate user behavior record information corresponding to the minimum business processing event. Take the minimum business processing event as the minimum information upload node, and send the user behavior record information of each minimum business processing event in the business processing link of the target business to the server.

[0023] The purpose of one or more embodiments of the present specification is to provide a storage medium for storing computer executable instructions. When the executable instructions are executed by the processor, they receive user behavior record information for each minimum business processing event in the business processing link of the target business sent by the client; wherein the minimum business processing event is a business processing event triggered based on user operation behavior, and the user behavior record information is generated based on the target page element in the user access page involved in executing the minimum business processing event and the description information of the user operation behavior on the user access page. Based on the upload node identifier corresponding to each of the minimum business processing events, the user behavior record information is stored.

[0024] The purpose of one or more embodiments of this specification is to provide a storage medium for storing computer executable instructions. When the executable instructions are executed by the processor, they receive user behavior record information for each minimum business processing event in the business processing link of the target business sent by the client; wherein the minimum business processing event is a business processing event triggered based on user operation behavior, and the user behavior record information is generated based on the target page element in the user access page involved in executing the minimum business processing event and the description information of the user operation behavior on the user access page. Based on the upload node identifier corresponding to each of the minimum business processing events, the user behavior record information is uploaded to the blockchain. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0026] Figure 1 A schematic diagram of an application scenario of an information storage system provided for one or more embodiments of this specification;

[0027] Figure 2 A first flow chart of an information recording method applied to a client provided in one or more embodiments of this specification;

[0028] Figure 3 A second flow chart of the information recording method applied to a client provided in one or more embodiments of this specification;

[0029] Figure 4 A third flow chart of the information recording method applied to a client provided by one or more embodiments of this specification;

[0030] Figure 5 A fourth flow chart of an information recording method applied to a client provided by one or more embodiments of this specification;

[0031] Figure 6 A schematic diagram of a specific implementation principle of an information storage method provided in one or more embodiments of this specification;

[0032] Figure 7 A flowchart of an information storage method applied to a server provided in one or more embodiments of this specification;

[0033] Figure 8 A flowchart of an information storage method for a server connected to a blockchain provided in one or more embodiments of this specification;

[0034] Fig. 9 A schematic diagram of the module composition of an information recording device provided on a client side in one or more embodiments of this specification;

[0035] Fig.10 A schematic diagram of the module composition of an information storage device provided at a server end for one or more embodiments of this specification;

[0036] Fig.11 A schematic diagram of the module composition of an information storage device provided in a server connected to a blockchain according to one or more embodiments of this specification;

[0037] Fig.12 A schematic diagram of the structure of an information storage system provided for one or more embodiments of this specification;

[0038] Fig.13 A schematic diagram of the structure of an information recording device provided for one or more embodiments of this specification;

[0039] Fig.14 A schematic diagram of the structure of an information storage device provided for one or more embodiments of this specification. DETAILED DESCRIPTION

[0040] In order to enable persons skilled in the art to better understand the technical solutions in one or more embodiments of this specification, the technical solutions in one or more embodiments of this specification will be clearly and completely described below in conjunction with the drawings in one or more embodiments of this specification. Obviously, the described embodiments are only one or more partial embodiments of this specification, rather than all embodiments. Based on one or more embodiments of this specification, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of this document.

[0041] It should be noted that, in the absence of conflict, one or more embodiments and features in the embodiments in this specification can be combined with each other. One or more embodiments of this specification will be described in detail below with reference to the drawings and in combination with the embodiments.

[0042] One or more embodiments of the present specification provide an information recording method and device, an information storage method, device and system, which automatically generate user behavior record information based on the characteristic information of the target page elements in the user access page and the description information of the user operation behavior when processing the target business based on the user operation behavior, so as to realize efficient and lightweight recording of the user behavior information; at the same time, in the process of processing the target business, the user behavior record information corresponding to all the minimum business processing events recorded in the processing process of the target business is sent to the server in sequence with the minimum business processing event as the minimum information upload node, so as to realize the real-time uploading of the user behavior record information used for backtracking the processing process of the user's target business to the server, so that in the subsequent business dispute event, the user operation behavior of each user in the target business processing process can be restored based on the user behavior record information, so as to achieve the purpose of defining the responsibility of the business dispute event.

[0043] Figure 1 A schematic diagram of an application scenario of an information storage system provided in one or more embodiments of this specification, such as Figure 1 As shown, the system includes: a client, a server and a record information query terminal, wherein the client or the record information query terminal can be a mobile terminal such as a smart phone, a tablet computer, etc., the client or the record information query terminal can also be a terminal device such as a personal computer, the server can be a business service end for providing processing services for target businesses to users, the server can be an independent server, or it can be a server cluster composed of multiple servers.

[0044] The specific process of storing user behavior record information is as follows:

[0045] In step A1, the client monitors the minimum business processing event for the target business triggered by the user operation behavior; wherein, the minimum business processing event may include: an input event of business-related information, a check event of business-related matters, an agreement signing event, or a successful processing event, etc.; the user operation behavior may be a touch operation of the user on the operation page of the application corresponding to the target business. Correspondingly, the minimum business processing event is a business processing sub-event triggered by the user completing a certain business processing through an application on the client. The multiple minimum business processing events involved in the process of the user completing a certain business processing constitute the business processing link of the target business.

[0046] Step A2: If the minimum business processing event monitored by the client is a home page access event for the target business, the client sends a long link establishment request to the server to establish a long link between the server and the client.

[0047] Step A3, the client determines the target page element in the user access page involved in executing the monitored home page access event; and obtains description information of the user operation behavior on the service home page visited by the user.

[0048] In step A4, the client generates user behavior record information corresponding to the home page access event according to the determined feature information of the target page element and the acquired description information.

[0049] In step A5, the client uses the established long link to send the user behavior record information corresponding to the home page access event in the business processing link for executing the target business to the server.

[0050] Step A6: if the minimum business processing event monitored by the client is any intermediate business processing event in the target business handling process, the client sends the user behavior record information corresponding to each intermediate business processing event to the server in sequence according to the above steps A3 to A5; wherein, a user access page may correspond to multiple minimum business processing events;

[0051] Step A7, the server receives the user behavior record information corresponding to each minimum business processing event sent by the client in real time, and stores the user behavior record information in sequence based on the upload node identifier corresponding to each minimum business processing event; wherein, the user behavior record information of all minimum business processing events in the business processing link of the target business constitutes a complete record of all operations of the user on the business page of the target business during the target business processing process.

[0052] Step A8: If the minimum business processing event monitored by the client is a business processing end event for the target business, the client sends the user behavior record information corresponding to the business processing end event to the server in sequence according to the above steps A3 to A5, and stops the step of generating the user behavior record information to avoid mistakenly recording user behavior information that is not related to the target business processing; wherein the business processing end event may be an event triggered by the user clicking the confirmation control on the target business confirmation page; and,

[0053] In step A9, the client determines whether there is at least one behavior record information to be reissued in the user behavior record information uploaded for the target business. If so, the client uses the established long link to send the behavior record information to be reissued to the server until it is determined that the server has received all user behavior record information involved in the business processing link for executing the target business, thereby ensuring that all user operation behaviors on each business access page during the target business processing process can be fully restored later.

[0054] Among them, for the resending process of user behavior record information, the user behavior record information that has not been received can also be resent to the server in real time during the target business processing. At the same time, taking into account the possible unsuccessful resending, the user behavior record information that failed to be resent can be uploaded to the server again at the end of the target business processing.

[0055] Step A10, the client sends a long link disconnection request to the server, so that the server and the client disconnect the long link;

[0056] Specifically, after determining that the server has received all user behavior record information involved in the business processing link for executing the target business, the server is requested to disconnect the long link to avoid mistakenly uploading user behavior records unrelated to the target business to the server.

[0057] Furthermore, considering that after the server stores all the user behavior record information involved in the business processing link of executing the target business, there may be a need to trace the user's business processing process later, specifically:

[0058] In step B1, the server receives a behavior record query request sent by a record information query terminal; wherein the behavior record query request carries business processing identification information; the business processing identification information may be a unique identification of the business processing, such as a business order number; correspondingly, for the upload process of the user behavior record information, the upload node identification corresponding to the minimum business processing event may also include the business processing identification information, so that it is convenient for the server to associate and store multiple user behavior record information related to the same business processing identification information; that is, the upload node identification includes not only the identification information of each business processing sub-event in the business processing link, but also the unique identification information of the business processing link.

[0059] Step B2, the server searches for user behavior record information corresponding to the business processing identification information carried in the received behavior record query request from the stored historical behavior record information; wherein the queried user behavior record information includes: user behavior record information of all minimum business processing events in the business processing chain executed for the target business based on the operation behavior of the business requesting user;

[0060] Among them, taking the target business as insurance business as an example, the queried user behavior record information includes: user behavior record information of all minimum insurance processing events in the insurance processing link executed for the insurance business based on the operation behavior of the insured user;

[0061] Step B3, the server generates a user behavior retrospective video stream based on the queried user behavior record information for displaying the execution of the target business processing based on the user operation behavior; wherein, the user behavior retrospective video stream is used to restore the page information visited by the user during the target business processing, and the user's operation behavior information on all visited pages, wherein the operation behavior information includes the user's triggering actions on the page elements on the visited page (for example, click actions, sliding actions, etc.) and the relevant information entered by the user on the visited page.

[0062] In step B4, the server sends the generated user behavior retrospective video stream to the record information query terminal, so that the record information query terminal displays the received user behavior retrospective video stream on the display interface. In this way, the record information query terminal can restore all user operation behaviors of the user on each business access page during the target business handling process by displaying the user behavior retrospective video stream, thereby achieving the purpose of tracing back the user's target business handling process.

[0063] In the above application scenario, when business processing is performed on the target business based on user operation behavior, user behavior record information is automatically generated based on the characteristic information of the target page elements in the user access page and the description information of the user operation behavior, so as to realize efficient and lightweight recording of user behavior information; at the same time, in the process of target business processing, the minimum business processing event is used as the minimum information upload node, and the user behavior record information corresponding to all the minimum business processing events recorded for the target business is sent to the server in sequence, so that the user behavior record information used to trace the handling process of the user's target business is uploaded to the server in real time, so that in the subsequent business dispute event, the user operation behavior of each user in the target business handling process can be restored based on the user behavior record information, so as to achieve the purpose of defining the responsibility of the business dispute event.

[0064] Figure 2 A first flow chart of an information recording method provided in one or more embodiments of this specification, Figure 2 The method in can be Figure 1 The client executes in Figure 2 As shown, the method comprises at least the following steps:

[0065] S202, for a minimum business processing event of a target business triggered by a user operation behavior, determining a target page element in a user access page involved in executing the minimum business processing event;

[0066] The user operation behavior may include at least one of a single-click operation, a double-click operation, a sliding operation, an input operation, and a deletion operation; the target business may be set as needed in actual applications, such as insurance business, financial management business, mutual aid business, commodity purchase business, etc. Specifically, the business processing event triggered by the user's operation behavior in the current page of the first application corresponding to the target business is monitored through a specified script.

[0067] The above-mentioned minimum business processing event may be an input event of business-related information, a check event of business-related items, an agreement signing event, or a successful processing event, etc. Specifically, any page element in the user access page may be used as a target page element, or a key page element in the user access page may be used as a target page element.

[0068] S204, obtaining description information of user operation behavior on the user access page corresponding to the above minimum business processing event;

[0069] Specifically, the above-mentioned description information can be obtained from the application corresponding to the target business. By pre-setting the annotation information corresponding to the page elements related to the business processing, the description information of the corresponding operation behavior can be generated based on the annotation information. This can not only clearly describe the meaning of the user's operation behavior, but also provide an easy-to-understand tracing basis for the tracing of the user's operation behavior.

[0070] S206, generating user behavior record information corresponding to the above-mentioned minimum business processing event according to the determined characteristic information of the target page element and the acquired description information;

[0071] Among them, the characteristic information of the above-mentioned target page elements may include: element identification information, change information, code information, etc.; specifically, in order to ensure that the generated user behavior record information contains all key page element information of the accessed page, so that when the server subsequently restores the user operation behavior, all key page elements in the accessed page can be fully presented, thereby more realistically and intuitively restoring the user operation behavior of the user in the target business processing process, based on this, if the target page elements include page elements in the user access page that change based on the user operation behavior, then the characteristic information of the key page elements that have not changed based on the user operation behavior in the pre-stored user access page is obtained, and according to the characteristic information of the target page elements, the characteristic information of the key page elements and the description information of the user operation behavior, the user behavior record information corresponding to the currently monitored minimum business processing event is generated.

[0072] Specifically, the characteristic information of the target page elements and the description information of the user's operation behavior can be converted in binary form, and the converted information is determined as the user behavior record information of the corresponding minimum business processing event. The corresponding user access page and the user's operation behavior on the access page are subsequently rendered based on the user behavior record information, so as to restore the business page seen by the user under each minimum business processing event and the user's operation behavior on the business page in the form of a video stream, so as to realize a more intuitive tracing of user behavior.

[0073] S208, using the minimum business processing event as the minimum information upload node, sending the user behavior record information of each minimum business processing event in the business processing link of the target business to the server, so that the server stores the user behavior record information based on the upload node identifier corresponding to each minimum business processing event;

[0074] The upload node identifier may include a minimum processing event identifier and may also include timestamp information, and the timestamp information may include: an operation behavior timestamp and an information upload timestamp, and the user behavior record information corresponding to each minimum business processing event has a unique upload node identifier; specifically, the client sends the user behavior record information generated for the target business and the corresponding upload node identifier to the server in real time, wherein the user behavior record information may be behavior record information in binary form;

[0075] Specifically, the server stores the behavior record information in binary form, wherein the behavior record information records the full amount of operational behavior information of the user in the target business processing process, so that the server or query terminal can restore the video stream of the business page seen by the user and the operational behavior on the business page based on the binary behavior record information, thereby more completely and intuitively restoring the operational behavior of the user in the target business processing process, thereby achieving traceability of the operational behavior of the user in the target business processing process.

[0076] In one or more embodiments of the present specification, when business processing is performed on a target business based on user operation behavior, user behavior record information is automatically generated based on the characteristic information of the target page elements in the user access page and the description information of the user operation behavior, thereby achieving efficient lightweight recording of user behavior information compared to the video recording method, and achieving efficient and full recording of user behavior information compared to the point recording method; at the same time, during the target business processing process, the minimum business processing event is used as the minimum information upload node, and the user behavior record information corresponding to all the minimum business processing events recorded for the target business is sent to the server in sequence, so that the user behavior record information used to trace the handling process of the user's target business is uploaded to the server in real time, so that in the subsequent business dispute event, the user operation behavior of each user in the target business handling process can be restored based on the user behavior record information, so as to achieve the purpose of defining the responsibility for the business dispute event.

[0077] Furthermore, in order to improve the security and stability of information transmission between the client and the server, Figure 3 As shown, before determining the target page element in the user access page involved in executing the minimum business processing event, it also includes:

[0078] S210, determining a minimum business processing event of a target business triggered by a user operation behavior;

[0079] S212, if the minimum business processing event is a home page access event for the target business, a long link establishment request is sent to the server to establish a long link between the server and the client; specifically, a long link is established between the client and the server through the websocket protocol.

[0080] Correspondingly, the above S208, taking the minimum business processing event as the minimum information upload node, sends the user behavior record information of each minimum business processing event in the business processing link of the target business to the server, so that the server stores the user behavior record information based on the upload node identifier corresponding to each minimum business processing event, specifically including:

[0081] S2082, using the established long link to send user behavior record information of each minimum business processing event in the business processing link of the target business to the server, so that the server stores the user behavior record information based on the upload node identifier corresponding to each minimum business processing event;

[0082] S2084: If the minimum business processing event is a business processing end event for the target business, a long link disconnection request is sent to the server to disconnect the long link between the server and the client.

[0083] Furthermore, considering that user behavior record information may be lost during information transmission, in order to ensure that the user behavior record information of all minimum business processing events in the full link of business processing of the target business is stored normally, based on this, Figure 4 As shown, in S208, after taking the minimum business processing event as the minimum information uploading node and sending the user behavior record information of each minimum business processing event in the business processing link of the target business to the server, it also includes:

[0084] S214, receiving information storage feedback information returned by the server in response to the received user behavior record information;

[0085] S216, based on the received information storage feedback information, determine the behavior record information to be reissued from the sent user behavior record information.

[0086] Among them, for the determination process of the behavior record information to be reissued, a method of dynamically updating the upload node identifier set representing the unstored record information can be adopted. Based on this, the above S216, based on the received information storage feedback information, determines the behavior record information to be reissued from the sent user behavior record information, specifically including:

[0087] Step a1, based on the received information storage feedback information, determining the target node identifier corresponding to the stored user behavior record information;

[0088] Step a2, determining the behavior record information to be reissued from the sent user behavior record information according to the determined target node identifier and the upload node identifier corresponding to the sent user behavior record information;

[0089] Specifically, an upload node identifier set may be established, the upload node identifier set including: the upload node identifiers corresponding to the user behavior record information that has been sent to be stored; specifically, each time the user behavior record information is sent to the server, the upload node identifier corresponding to the user behavior record information is added to the upload node identifier set, and each time after receiving the information storage feedback information returned by the server, the upload node identifier of the stored user behavior record information determined based on the information storage feedback information is deleted from the upload node identifier set, that is, according to the upload status of the user behavior record information and the information storage feedback status of the server, the upload node identifier set is dynamically updated, so that the user behavior record information corresponding to the remaining upload node identifiers in the upload node identifier set is to be reissued or is being stored;

[0090] Specifically, if the upload node identifier includes the information upload timestamp, it is also possible to determine, based on the time interval between the information upload timestamp and the current time, whether the user behavior record information corresponding to the remaining upload node identifiers in the upload node identifier set is user behavior record information to be reissued or user behavior record information being stored.

[0091] Among them, for the determination process of the behavior record information to be reissued, a method of dynamically updating the storage status type of each user behavior record information can also be adopted. Based on this, the above S216, based on the received information storage feedback information, determines the behavior record information to be reissued from the sent user behavior record information, specifically including:

[0092] Step b1, based on the received information storage feedback information, updating the storage status type of the sent user behavior record information;

[0093] Step b2: determining the behavior record information to be reissued from the sent user behavior record information according to the updated storage status type.

[0094] Specifically, the upload node identifier may include: an operation behavior timestamp, and correspondingly, the information storage feedback information may include: a target operation timestamp corresponding to the currently stored user behavior record information;

[0095] Correspondingly, the above step b1, based on the received information storage feedback information, updates the storage status type of the sent user behavior record information, specifically including:

[0096] Update the storage status type of the user behavior record information whose operation behavior timestamp is equal to the target operation timestamp to stored; and

[0097] Determine, in the sent user behavior record information, the storage state type of the target behavior record information whose operation behavior timestamp is earlier than the target operation timestamp;

[0098] If it is determined that the storage status type is not stored, the storage status type of the target behavior record information is updated to pending reissue.

[0099] Specifically, the above information storage feedback information may also include: a target node identifier corresponding to the currently stored user behavior record information;

[0100] Correspondingly, considering that the upload process of user behavior record information is usually uploaded in sequence, in the absence of data loss, the upload node identifier in the information storage feedback information returned by the server is continuous. In order to quickly identify whether there is information loss, the upload node identifier of the current feedback can also be compared with the previous upload node identifier. Based on this, the above step b1, based on the received information storage feedback information, updates the storage status type of the sent user behavior record information, specifically including:

[0101] Update the storage status type of the user behavior record information corresponding to the target node identifier to stored; and

[0102] Determine whether the target node identifier and the previous uploading node identifier fed back by the server are adjacent node identifiers;

[0103] If it is not an adjacent node identifier, determining the storage state type of the target behavior record information corresponding to the intermediate upload node identifier between the target node identifier and the previous upload node identifier;

[0104] If it is determined that the storage status type is not stored, the storage status type of the target behavior record information is updated to pending reissue.

[0105] It should be noted that, in specific implementation, the process of determining the behavior record information to be reissued can be a combination of two methods: dynamically updating the storage status type of each user's behavior record information, and dynamically updating the upload node identifier set that represents the unstored record information.

[0106] Among them, in order to further ensure that the user behavior record information of all minimum business processing events in the entire chain of business processing of the target business is stored normally, so as to ensure the integrity of each user's operation behavior restored in the process of handling the target business based on the user behavior record information, based on this, Figure 5 As shown, in the above S2084, if the minimum business processing event is a business processing end event for the target business, a long link disconnection request is sent to the server to disconnect the long link between the server and the client, specifically including:

[0107] S20841, if the minimum business processing event is a business processing end event for the target business, determining at least one remaining behavior record information to be reissued;

[0108] S20842, sending at least one action record to be reissued to the server by using the established long link;

[0109] S20843, based on the information storage feedback information returned by the server for the behavior record information to be reissued, determining whether at least one behavior record information to be reissued has been completely stored in the server;

[0110] If it is determined that all the data have been stored, S20844 is executed to send a long link disconnection request to the server to disconnect the long link between the server and the client.

[0111] Wherein, for the lost user behavior record information, a method of reissuing upon discovery may be adopted, that is, once it is determined that a certain user behavior record information has been lost, the user behavior record information is immediately obtained from the local cache and uploaded to the server. Based on this, in S216, after determining the behavior record information to be reissued from the sent user behavior record information based on the received information storage feedback information, it also includes:

[0112] Obtain the behavior record information to be reissued in the local cache, and send the behavior record information to be reissued to the server; specifically, for each user behavior record information, before receiving the stored feedback information returned by the server, cache the user behavior record information locally on the client so that it can be quickly obtained when the subsequent information is reissued; correspondingly, after receiving the stored feedback information returned by the server, the user behavior record information can be deleted from the local cache.

[0113] Receiving the reissue information storage feedback information returned by the server for the above-mentioned to-be-reissued action record information;

[0114] Based on the received reissue information storage feedback information, at least one remaining behavior record information to be reissued is determined.

[0115] In order to further determine the lightweight of the uploaded information and to protect user privacy, based on this, the above S208, taking the minimum business processing event as the minimum information upload node, sends the user behavior record information of each minimum business processing event in the business processing link of the target business to the server, so that the server stores the user behavior record information based on the upload node identifier corresponding to each minimum business processing event, specifically including:

[0116] For each user behavior record information, generate behavior record information in binary format corresponding to the user behavior record information;

[0117] Taking the minimum business processing event as the minimum information upload node, the binary behavior record information corresponding to each minimum business processing event in the business processing link of the target business is sent to the server, so that the server stores the binary behavior record information based on the upload node identifier corresponding to each minimum business processing event.

[0118] Among them, considering that the user may perform multiple operations on the same page, in order to avoid including duplicate page information in the behavior record information corresponding to the multiple operations, for each operation behavior of the user, the target page element that changes based on the operation behavior in at least one page element included in the page is determined, so as to generate user behavior record information based on the characteristic information of the target page element. Specifically, with respect to the determination process of the target page element, the above S202, determining the target page element in the user access page involved in executing the minimum business processing event, specifically includes:

[0119] Monitoring whether there is an updated target CSS style in the CSS style corresponding to the user access page involved in executing the minimum business processing event; wherein the target CSS style is updated by the business processing module of the first application corresponding to the target business based on the minimum business processing event;

[0120] Monitoring whether there is a target DOM node to be updated in the DOM structure corresponding to the user access page involved in executing the minimum business processing event; wherein the target DOM node is updated by the business processing module of the first application corresponding to the target business based on the minimum business processing event;

[0121] The page element corresponding to the monitored target CSS style and / or target DOM node is determined as the target page element that changes based on the user operation behavior.

[0122] Among them, the above-mentioned first application can be an independent application for providing the target business service, or it can be a hosted application for providing the target business service, for example, a mini-program, which is hosted in the host application; the above-mentioned target page elements can include page elements operated by the user, and can also include page elements that are not operated by the user but are changed based on the user's operating behavior.

[0123] Specifically, when the user operates a page element in the current page of the first application, the corresponding CSS style will change, but the DOM nodes in the DOM structure may not necessarily change. Therefore, when there is no target DOM node, the target page element can be determined according to the target CSS style; when there is a target DOM node and the page element corresponding to the target DOM node is different from the page element corresponding to the target CSS style, the target page element is determined according to the target DOM node and the target CSS style; when there is a target DOM node and the page element corresponding to the target DOM node is the same as the page element corresponding to the target CSS style, the target page element can be determined according to the target DOM node or the target CSS node.

[0124] For example, taking the target business as insurance business, the agreement signing page of the first application may include n clauses, where n is a positive integer; when the user checks the check box of "I have read and agreed to the terms of the agreement", the agreement signing event is triggered, and the first application determines that the CSS style corresponding to the agreement signing page needs to be updated according to the agreement signing event to display the "√" representing the user's check operation, and at the same time, the "OK" button in the agreement signing page changes from gray representing inoperability to a bright color representing operability (such as blue, etc.). When the recording device monitors that there is an updated target CSS style in the CSS style of the agreement signing page, the page element check box and OK button corresponding to the target CSS style are determined as target page elements that change based on the user's check operation.

[0125] Specifically, since the CSS style and DOM structure can accurately reflect the changes of page elements, by monitoring the CSS style and DOM structure of the current page, the target page elements that change based on the user's operation behavior can be accurately determined.

[0126] The process of determining the description information of the user operation behavior, S204, obtaining the description information of the user operation behavior on the user access page corresponding to the minimum business processing event, specifically includes:

[0127] Receive description information of user operation behavior sent by the business processing module of the first application corresponding to the target business; wherein the description information is information generated based on the annotation information associated with the page element targeted by the user operation behavior when the business processing module of the first application executes the minimum business processing event; the annotation information is used to describe the operational meaning of the user operation behavior.

[0128] Each page of the first application corresponding to the target business includes at least one page element related to the target business, such as an input box, selection box, drop-down box, button, etc., for users to operate to complete the processing of the target business. And there is often a gap between different page elements in the page, that is, there will be blank areas, etc. During the processing of the target business, when the user operates the page elements related to the target business, the corresponding business processing event is triggered; when the user operates the page elements related to the non-target business in the page, for example, the user clicks on the blank area of ​​the current page or fixed text, image, etc. in order to light up the screen of the terminal device where the first application is located, the triggered event is not a business processing event.

[0129] In order to effectively trace back the user's operation behavior on the target business later, if the monitored event is a business processing event of the target business, the description information of the user's operation behavior is obtained from the first application.

[0130] Among them, considering that the data processed by the first application in the process of business processing is usually machine-readable data, when the user's operation behavior is subsequently traced back, the machine-readable data is not convenient for the tracer to understand the user's operation behavior. Based on this, the annotation information corresponding to the page elements related to the business processing is pre-set, and the operation meaning of the user operating the corresponding page element is described through the annotation information.

[0131] Specifically, when the user's operation behavior in the current page of the first application corresponding to the target business triggers a business processing event of the target business, the first application, when obtaining the business processing event, obtains the associated annotation information from the preset association relationship between the element identification information and the annotation information according to the element identification information of the page element operated by the user carried in the business processing event.

[0132] Generate description information of the user's operation behavior based on the acquired annotation information, element identification information of the page element operated by the user carried in the business processing event, etc.;

[0133] Alternatively, description information of the user's operation behavior is generated based on the acquired identification information, the user input information carried in the business processing event, and the element identification information of the page element operated by the user.

[0134] For example, taking the target business as insurance business, the user enters the number 10 (in years) in the input box for entering the insurance duration in the insurance information input page of the first application. When the first application obtains the insurance duration processing event triggered by the user's input operation, the corresponding annotation information "insurance duration entered by the user, unit: year" is obtained according to the element identification information 0004 of the page element operated by the user carried by the insurance duration processing event. Then, according to the obtained annotation information, the number 10 carried by the insurance duration processing event, and the element identification information 0004 of the page element operated by the user, the description information of the user's operation behavior is generated, such as the page element corresponding to the user operation element identification information 0004, and the insurance duration of 10 years is entered. It should be noted that the form of the description information here is only used for example and not for limitation. The specific form of the description information can be set by oneself according to the actual application as needed.

[0135] Therefore, by pre-setting the annotation information corresponding to the page elements related to business processing, the corresponding description information of the operation behavior is generated based on the annotation information, which can not only clearly describe the meaning of the user's operation behavior, but also provide an easy-to-understand tracing basis for the tracing of the user's operation behavior.

[0136] Furthermore, in order to be able to trace back all the user's operations during the business handling process and restore the entire process of business handling, specifically, if an event is monitored that is triggered by the user's operation behavior in the current page of the first application corresponding to the target business, the event information of the event is determined and the determined event information is recorded. Among them, the event information, such as event identification information, time information when the event is triggered, operation type of user operation corresponding to the event, etc. Among them, event identification information and operation type information can be obtained from the event, and the time information when the event is triggered can be obtained from the event. It is also possible to obtain the current time when the event is monitored and use it as event information triggered by the event. User operation types include click, double-click, input, and slide.

[0137] Specifically, when the user performs relevant processing of the target business in the current page of the first application, if he also operates other applications unrelated to the target business, the event triggered by the corresponding operation behavior will not be recorded. For example, when the user performs relevant processing of the target business in the current page of the first application, the user's chat application flashes, and the user clicks on the chat application. The first application will not record the event information of the event triggered by the click operation.

[0138] Specifically, according to the event identification information included in the acquired description information, the corresponding target event information is acquired from the recorded event information; the acquired description information and the characteristic information of the determined target page element are associated with the target event information and recorded, and the recorded information is determined as the behavior record information of the user's operation behavior. Thus, according to the behavior record information, the following information can be obtained: the user's operation behavior on the page element corresponding to a certain element identification information at a certain point in time triggered an event of a certain event identification information; the operation achieved a certain purpose and caused a certain change in the page.

[0139] For example, a behavior record includes event information such as event ID 11, 12:30 on June 1, 2020, and input operation. The description information includes that the user operates the page element corresponding to the element ID information 0004 and inputs the insurance duration of 10 years; the characteristic information of the target page element includes that the page element corresponding to the element ID information 0004 displays the number 10, etc. The following information can be obtained based on the behavior record information: the user enters the number 10 in the page element corresponding to the element ID information 0004 at 12:30 on June 1, 2020 to indicate that the insurance duration is 10 years. The input operation triggers the event with event ID 11; the page change caused by the input operation is that the page element corresponding to the element ID information 0004 changes from blank to displaying the number 10. Among them, when an event triggered by the user's operating behavior in the current page of the first application corresponding to the target business is monitored, regardless of whether the event is a business processing event or other event, the event information of the event is determined and recorded, and all the user's operating behaviors in the process of handling the target business can be recorded, so that the user's target business handling process can be more realistically restored based on the behavior record information.

[0140] In a specific embodiment, taking the target business as insurance business as an example, Figure 6 As shown, the specific implementation process of the above user behavior record information storage is:

[0141] (1) The client monitors the minimum business processing event for insurance handling business triggered by user operation behavior; wherein, the minimum business processing event may include: input event of relevant information of the insurance business handling process, check event of relevant items of the insurance business handling process, signing event of insurance notification agreement, or insurance success event, etc.; the user operation behavior may be a touch operation of the user on the operation page of the application providing the target business, that is, a touch operation on the operation page of the application providing the insurance business. Correspondingly, the minimum business processing event is a business processing sub-event triggered by the user completing the insurance business handling process through the application providing the insurance business on the client. The multiple minimum business processing events involved in the user completing the insurance business handling process constitute the business processing link of the insurance handling business.

[0142] (2) If the minimum business processing event monitored by the client is an insurance homepage access event for insurance processing business, a long link establishment request is sent to the server to establish a long link between the server and the client.

[0143] (3) The client determines the target page element in the user access page involved in executing the insurance home page access event monitored by the client; and obtains the description information of the user's operation behavior on the insurance home page visited by the user.

[0144] (4) The client generates user behavior record information corresponding to the insurance homepage visit event based on the determined feature information of the target page element and the obtained description information.

[0145] (5) The client uses the established long link to send the user behavior record information corresponding to the insurance homepage access event in the business processing link for executing insurance business handling to the server.

[0146] (6) If the minimum business processing event monitored by the client is any intermediate business processing event in the insurance business handling process, the client will send the user behavior record information corresponding to each intermediate business processing event to the server in sequence according to the above (3) to (5); wherein, a user access page may correspond to multiple minimum business processing events; wherein, the user access page may include: at least one of: the insurance item homepage, the insurance item selection page, the insurance item confirmation page, the platform agreement reading page, and the platform agreement confirmation page; for example, the user behavior record information 1 to n of all the minimum business processing events in the business processing link are sent to the server in sequence.

[0147] (7) The server receives the user behavior record information corresponding to each minimum business processing event sent by the client in real time, and stores the user behavior record information in sequence based on the upload node identifier corresponding to each minimum business processing event; wherein, the user behavior record information of all minimum business processing events in the business processing chain of the insurance handling business constitutes a complete record of all operations of the user on the insurance-related business pages during the insurance business handling process; correspondingly, the server stores the user behavior record information 1 to n in sequence based on the upload node identifiers 1 to n corresponding to each minimum business processing event.

[0148] (8) If the minimum business processing event monitored by the client is a business processing end event for insurance processing business, the client sends the user behavior record information corresponding to the business processing end event to the server in sequence according to the above (3) to (5), and stops the step of generating the user behavior record information to avoid erroneous recording of user behavior information unrelated to insurance business processing; wherein the business processing end event may be an event triggered by the user clicking the confirmation control on the insurance confirmation page; and,

[0149] (9) The client determines whether there is at least one behavior record to be reissued in the user behavior record information uploaded during the user's insurance business processing. If so, the client uses the established long link to send the behavior record information to be reissued to the server until it is determined that the server has received all user behavior record information involved in the business processing link for executing the insurance business processing, thereby ensuring that all user operation behaviors of the user on each insurance-related page during the insurance business processing process can be fully restored later.

[0150] Among them, with regard to the process of reissuing user behavior record information, the user behavior record information that has not been received can also be resent to the server in real time during the insurance business processing. At the same time, taking into account the possible unsuccessful reissuance, the user behavior record information that failed to be reissued can be uploaded to the server again at the end of the insurance business processing.

[0151] (10) The client sends a long connection disconnection request to the server, so that the server and the client disconnect the long connection;

[0152] Specifically, after determining that the server has received all user behavior record information involved in the business processing link for executing insurance business handling, the server is requested to disconnect the long link to avoid mistakenly uploading user behavior records unrelated to insurance business handling to the server.

[0153] Furthermore, considering that after the server stores all the user behavior record information involved in the business processing link of executing the insurance business, there may be a need to trace the user's insurance process later, specifically:

[0154] (11) The server receives a behavior record query request sent by the record information query terminal; wherein the behavior record query request carries the insurance policy number; correspondingly, for the process of uploading the user behavior record information, the upload node identifier corresponding to the minimum business processing event may also include the insurance policy number, so that the server can associate and store multiple user behavior record information related to the same insurance policy number.

[0155] (12) The server queries the user behavior record information corresponding to the insurance policy number carried in the received behavior record query request from the stored historical behavior record information; wherein the queried user behavior record information includes: user behavior record information of all minimum insurance processing events in the insurance business processing chain executed for the insurance business based on the operating behavior of the insured user.

[0156] (13) Based on the queried user behavior record information, the server generates a user behavior retrospective video stream for displaying the execution of insurance business processing based on the user's operation behavior; wherein, the user behavior retrospective video stream is used to restore the page information visited by the user during the insurance business processing, and the user's operation behavior information on all visited pages, wherein the operation behavior information includes the user's triggering actions on the page elements on the visited page (for example, click actions, sliding actions, etc.) and the relevant information entered by the user on the visited page.

[0157] (14) The server sends the generated user behavior retrospective video stream to the record information query terminal, so that the record information query terminal displays the received user behavior retrospective video stream. In this way, the record information query terminal can restore all user operation behaviors of the user on each business access page during the insurance process by displaying the user behavior retrospective video stream, thereby achieving the purpose of fully tracing the user's insurance behavior during the insurance business processing process.

[0158] Specifically, the above process records the user's full insurance behavior information for a certain insurance item, thereby ensuring the integrity of the video stream used to present the business page seen by the user and the insurance behavior on the business page that is subsequently restored based on the insurance behavior information, thereby resolving claims disputes arising during the insurance claims process.

[0159] In another specific embodiment, taking the target business as a financial management business as an example, the specific implementation process of the above user behavior record information storage is:

[0160] (1) The client monitors the minimum business processing event for the financial product purchase business triggered by the user operation behavior; wherein the minimum business processing event may include: an input event of relevant information of the financial product purchase process, a check event of relevant items of the financial product purchase process, a signing event of the financial product purchase notification agreement, or a financial product purchase success event, etc.; the user operation behavior may be a touch operation of the user on the operation page of the application corresponding to the financial business, and correspondingly, the minimum business processing event is a business processing sub-event triggered by the user completing the financial product purchase process through the application providing the financial product purchase service on the client, and multiple minimum business processing events involved in the user completing the financial product purchase process constitute a business processing link of the financial product purchase service.

[0161] (2) If the minimum business processing event monitored by the client is a financial product purchase homepage access event for the financial product purchase business, a long link establishment request is sent to the server to establish a long link between the server and the client.

[0162] (3) The client determines the target page element in the user access page involved in executing the financial product selection homepage access event monitored by the client; and obtains the description information of the user operation behavior on the financial product selection homepage accessed by the user.

[0163] (4) The client generates user behavior record information corresponding to the financial product selection homepage visit event based on the determined feature information of the target page element and the obtained description information.

[0164] (5) The client uses the established long link to send the user behavior record information corresponding to the financial product selection homepage access event in the business processing link for executing the financial product selection process to the server.

[0165] (6) If the minimum business processing event monitored by the client is any intermediate business processing event in the financial product purchase process, the client sends the user behavior record information corresponding to each intermediate business processing event to the server in sequence according to the above (3) to (5); wherein, a user access page may correspond to multiple minimum business processing events; wherein, the user access page may include: at least one of: a financial product introduction homepage, a financial product selection page, a financial product purchase confirmation page, a platform agreement reading page, and a platform agreement confirmation page.

[0166] (7) The server receives the user behavior record information corresponding to each minimum business processing event sent by the client in real time, and stores the user behavior record information in sequence based on the upload node identifier corresponding to each minimum business processing event; wherein, the user behavior record information of all minimum business processing events in the business processing chain of the financial product selection business constitutes a complete record of all operations of the user on the financial product selection-related business pages during the financial product selection process.

[0167] (8) If the minimum business processing event monitored by the client is a business processing end event for the financial product purchase business, the client sends the user behavior record information corresponding to the business processing end event to the server in sequence according to the above (3) to (5), and stops the step of generating the user behavior record information to avoid erroneously recording user behavior information that is not related to the financial product purchase process; wherein the business processing end event may be an event triggered by the user clicking the confirmation control on the financial product purchase confirmation page; and,

[0168] (9) The client determines whether there is at least one behavior record to be reissued in the user behavior record information uploaded during the financial management business processing process for the user. If so, the client uses the established long link to send the behavior record information to be reissued to the server until it is determined that the server has received all user behavior record information involved in the business processing link for executing the financial management business, thereby ensuring that all user operation behaviors of the user on the relevant pages for purchasing various financial products during the financial management business processing process can be fully restored later.

[0169] Among them, with regard to the process of reissuing user behavior record information, the user behavior record information that has not been received can also be resent to the server in real time during the financial management business processing. At the same time, taking into account the possible unsuccessful reissuance, the user behavior record information that failed to be resent can be uploaded to the server again at the end of the financial management business processing.

[0170] (10) The client sends a long connection disconnection request to the server, so that the server and the client disconnect the long connection;

[0171] Specifically, after determining that the server has received all user behavior record information involved in the business processing link for executing financial management business, the server is requested to disconnect the long link to avoid mistakenly uploading user behavior records unrelated to financial management business to the server.

[0172] Furthermore, considering that after the server stores all the user behavior record information involved in the business processing link of executing the financial management business, there may be a need to trace the user's financial product purchase process in the future, specifically:

[0173] (11) The server receives a behavior record query request sent by the record information query terminal; wherein the behavior record query request carries the financial product purchase order number; correspondingly, for the process of uploading the user behavior record information, the upload node identifier corresponding to the minimum business processing event may also include the financial product purchase order number, so that the server can associate and store multiple user behavior record information related to the same financial product purchase order number.

[0174] (12) The server queries the user behavior record information corresponding to the financial product purchase order number carried in the received behavior record query request from the stored historical behavior record information; wherein the queried user behavior record information includes: the user behavior record information of all minimum financial product purchase processing events in the financial management business processing chain executed for the financial management business based on the operation behavior of the financial management user.

[0175] (13) Based on the queried user behavior record information, the server generates a user behavior retrospective video stream for displaying the financial management business processing based on the user's operation behavior; wherein, the user behavior retrospective video stream is used to restore the page information visited by the user during the financial management business processing, and the user's operation behavior information on all visited pages, wherein the operation behavior information includes the user's triggering actions on the page elements on the visited page (for example, click actions, sliding actions, etc.) and the relevant information entered by the user on the visited page.

[0176] (14) The server sends the generated user behavior retrospective video stream to the record information query terminal, so that the record information query terminal displays the received user behavior retrospective video stream. In this way, the record information query terminal can restore all user operation behaviors of the user on each business access page during the financial product purchase process by displaying the user behavior retrospective video stream, thereby achieving the purpose of fully tracing the user's financial product purchase behavior during the financial business handling process.

[0177] Specifically, the above process records the user's full amount of financial product purchasing behavior information for a certain financial project, thereby ensuring the integrity of the video stream used to present the business page seen by the user and the financial product purchasing behavior on the business page that is subsequently restored based on the financial product purchasing behavior information, thereby resolving the problem of capital loss disputes arising in the process of financial risk assumption.

[0178] In another specific embodiment, taking the target business as a mutual aid business as an example, the specific implementation process of the above user behavior record information storage is:

[0179] (1) The client monitors the minimum business processing event for the mutual aid project joining business triggered by the user operation behavior; wherein the minimum business processing event may include: the input event of relevant information of the mutual aid project joining process, the check event of relevant matters of the mutual aid project joining process, the signing event of the mutual aid project participation notification agreement, or the mutual aid project participation success event, etc.; the user operation behavior may be the user's touch operation on the operation page of the application corresponding to the mutual aid business, and correspondingly, the minimum business processing event is the business processing sub-event triggered by the user completing the mutual aid project joining process through the application providing the mutual aid project joining service on the client, and the multiple minimum business processing events involved in the user completing the mutual aid project joining process constitute the business processing link of the mutual aid project joining process.

[0180] (2) If the minimum business processing event monitored by the client is a mutual aid project participation homepage access event for the mutual aid project joining process, a long link establishment request is sent to the server to establish a long link between the server and the client.

[0181] (3) The client determines the target page element in the user access page involved in executing the mutual aid project participation homepage access event monitored by the client; and obtains the description information of the user's operation behavior on the mutual aid project participation homepage page visited by the user.

[0182] (4) The client generates user behavior record information corresponding to the mutual aid project participation homepage visit event based on the determined feature information of the target page element and the obtained description information.

[0183] (5) The client uses the established long link to send the user behavior record information corresponding to the mutual aid project participation homepage visit event in the business processing link for executing the mutual aid business joining to the server.

[0184] (6) If the minimum business processing event monitored by the client is any intermediate business processing event in the mutual aid business joining process, the client will send the user behavior record information corresponding to each intermediate business processing event to the server in sequence according to the above (3) to (5); wherein, a user access page may correspond to multiple minimum business processing events; wherein, the user access page may include: at least one of the mutual aid project participation project homepage, the mutual aid project participation project selection page, the mutual aid project participation project confirmation page, the platform agreement reading page, and the platform agreement confirmation page.

[0185] (7) The server receives the user behavior record information corresponding to each minimum business processing event sent by the client in real time, and stores the user behavior record information in sequence based on the upload node identifier corresponding to each minimum business processing event; among them, the user behavior record information of all minimum business processing events in the business processing chain of the mutual aid project joining process constitutes a complete record of all operations of the user on the business pages related to the mutual aid project participation in the mutual aid business joining process.

[0186] (8) If the minimum business processing event monitored by the client is a business processing end event for the mutual aid project joining business, the client sends the user behavior record information corresponding to the business processing end event to the server in sequence according to the above (3) to (5), and stops the step of generating the user behavior record information to avoid erroneous recording of user behavior information unrelated to the mutual aid business joining; wherein the business processing end event can be an event triggered by the user clicking the confirmation control on the mutual aid project participation confirmation page; and,

[0187] (9) The client determines whether there is at least one behavior record to be reissued in the user behavior record information uploaded during the user's mutual aid project joining process. If so, the client uses the established long link to send the behavior record information to be reissued to the server until it is determined that the server has received all user behavior record information involved in the business processing link for executing the mutual aid business joining, thereby ensuring that all user operation behaviors of the user on the relevant pages of each mutual aid project participation during the mutual aid business joining process can be fully restored later.

[0188] Among them, with regard to the process of reissuing user behavior record information, the user behavior record information that has not been received can also be resent to the server in real time during the mutual aid business processing. At the same time, taking into account the possible unsuccessful reissuance, the user behavior record information that failed to be reissued can be uploaded to the server again at the end of the mutual aid business processing.

[0189] (10) The client sends a long connection disconnection request to the server, so that the server and the client disconnect the long connection;

[0190] Specifically, after determining that the server has received all user behavior record information involved in the business processing link for executing the mutual aid business, the server is requested to disconnect the long link to avoid mistakenly uploading user behavior records unrelated to the mutual aid business to the server.

[0191] Furthermore, considering that after the server stores all the user behavior record information involved in the business processing link of the mutual aid business, there may be a need to trace the user's participation in the mutual aid project, specifically:

[0192] (11) The server receives a behavior record query request sent by the record information query terminal; wherein the behavior record query request carries the mutual aid project participation order number; correspondingly, for the upload process of the user behavior record information, the upload node identifier corresponding to the minimum business processing event may also include the mutual aid project participation order number, so that it is convenient for the server to associate and store multiple user behavior record information related to the same mutual aid project participation order number.

[0193] (12) The server queries the user behavior record information corresponding to the mutual aid project participation number carried in the received behavior record query request from the stored historical behavior record information; wherein the queried user behavior record information includes: user behavior record information of all minimum mutual aid project participation processing events in the mutual aid project participation business processing link executed for the mutual aid business based on the operation behavior of the mutual aid project participating users.

[0194] (13) Based on the queried user behavior record information, the server generates a user behavior retrospective video stream for displaying the execution of mutual aid business joining based on the user's operation behavior; wherein, the user behavior retrospective video stream is used to restore the page information visited by the user during the mutual aid project joining process, and the user's operation behavior information on all visited pages, wherein the operation behavior information includes the user's triggering actions on the page elements on the visited page (for example, click actions, sliding actions, etc.) and the relevant information entered by the user on the visited page.

[0195] (14) The server sends the generated user behavior retrospective video stream to the record information query terminal, so that the record information query terminal displays the received user behavior retrospective video stream. In this way, the record information query terminal can restore all user operation behaviors of users on various business access pages during the process of participating in the mutual aid project by displaying the user behavior retrospective video stream, thereby achieving the purpose of fully tracing the user behavior of the user in the process of joining the mutual aid business.

[0196] Specifically, the above process records the user's full mutual aid project participation behavior information for a certain mutual aid project, thereby ensuring the integrity of the business page seen by the user and the video stream of the mutual aid project participation behavior on the business page that is subsequently restored based on the mutual aid project participation behavior information, thereby resolving claims disputes arising in the mutual aid project claims process.

[0197] The information recording method in one or more embodiments of the present specification, when performing business processing based on user operation behavior for the target business, automatically generates user behavior record information based on the characteristic information of the target page elements in the user access page and the description information of the user operation behavior, so as to realize efficient and lightweight recording of user behavior information; at the same time, during the target business processing process, the minimum business processing event is used as the minimum information upload node, and the user behavior record information corresponding to all the minimum business processing events recorded for the target business is sent to the server in sequence, so that the user behavior record information used to trace the handling process of the user's target business is uploaded to the server in real time, so that in the subsequent business dispute event, the operation behaviors of each user in the target business handling process can be restored based on the user behavior record information, so as to achieve the purpose of defining the responsibility of the business dispute event.

[0198] Corresponding to the above Figures 1 to 6 Based on the same technical concept, one or more embodiments of this specification also provide an information storage method. Figure 7 A flowchart of an information storage method provided in one or more embodiments of this specification, Figure 7 The methods in can be executed by the server, such as Figure 7 As shown, the method comprises at least the following steps:

[0199] S702, receiving user behavior record information of each minimum business processing event in the business processing link of the target business sent by the client; wherein the minimum business processing event is a business processing event triggered based on a user operation behavior, and the user behavior record information is generated based on a target page element in a user access page involved in executing the minimum business processing event and description information of the user operation behavior on the user access page;

[0200] S704: Store the received user behavior record information based on the upload node identifier corresponding to each minimum business processing event.

[0201] Furthermore, considering the tamper-proof nature of blockchain data storage, the server can also upload the user behavior record information to the blockchain after receiving the user behavior record information sent by the client, so that at least one blockchain node in the blockchain stores the user behavior record information in the blockchain.

[0202] Furthermore, before receiving the user behavior record information of each minimum service processing event in the service processing link of the target service sent by the client at S702, the method further includes:

[0203] Receiving a long link establishment request sent by a client; wherein the long link establishment request is issued by the client when determining that the minimum business processing event currently being executed is a home page access event for a target business;

[0204] Respond to the received long link establishment request and establish a long link with the client.

[0205] Correspondingly, the S702, receiving the user behavior record information of each minimum business processing event in the business processing link of the target business sent by the client, specifically includes:

[0206] The established long link is used to receive user behavior record information of each minimum business processing event in the business processing link of the target business sent by the client.

[0207] Furthermore, after receiving the user behavior record information of each minimum business processing event in the business processing link of the target business sent by the client by using the established long link, the method further includes:

[0208] Receiving a long link disconnection request sent by a client; wherein the long link disconnection request is sent by the client when determining that the currently executed minimum business processing event is a business processing end event for a target business;

[0209] In response to the received long link disconnection request, the long link is disconnected from the client.

[0210] Further, at S704, after storing the user behavior record information based on the upload node identifier corresponding to each minimum business processing event, the method further includes:

[0211] Receiving a behavior record query request sent by a record information query terminal; wherein the behavior record query request carries business processing identification information;

[0212] Obtaining user behavior record information corresponding to the above business processing identification information;

[0213] Based on the acquired user behavior record information, a user behavior retrospective video stream is generated for displaying the execution of target business processing based on the user operation behavior;

[0214] Sending the generated user behavior retrospective video stream to the record information query terminal so that the record information query terminal displays the received user behavior retrospective video stream;

[0215] Specifically, if the server uploads the user behavior record information to the blockchain after receiving the user behavior record information sent by the client, at least one blockchain node in the blockchain will store the user behavior record information in the blockchain; correspondingly, after receiving the behavior record query request sent by the record information query terminal, the server sends a behavior record acquisition request to at least one blockchain node in the blockchain, so that the blockchain node returns the user behavior record information corresponding to the business processing identification information carried in the behavior record query request.

[0216] The information storage method in one or more embodiments of the present specification, when performing business processing based on user operation behavior for the target business, automatically generates user behavior record information based on the characteristic information of the target page elements in the user access page and the description information of the user operation behavior, so as to realize efficient and lightweight recording of user behavior information; at the same time, in the process of processing the target business, the user behavior record information corresponding to all the minimum business processing events recorded for the target business is sent to the server in sequence with the minimum business processing event as the minimum information upload node, so as to realize the real-time uploading of the user behavior record information used to trace the handling process of the user's target business to the server, so that in the subsequent business dispute event, the operation behaviors of each user in the target business handling process can be restored based on the user behavior record information, so as to achieve the purpose of defining the responsibility of the business dispute event.

[0217] It should be noted that this embodiment in this specification and the previous embodiment in this specification are based on the same inventive concept, so the specific implementation of this embodiment can refer to the implementation of the aforementioned information storage method, and the repeated parts will not be repeated.

[0218] Corresponding to the above Figures 1 to 6 The information recording method described above is based on the same technical concept. One or more embodiments of this specification also provide an information storage method, which is applied to a server connected to a blockchain. Figure 8 A flowchart of an information storage method provided in one or more embodiments of this specification, Figure 8 The methods in can be executed by the server, such as Figure 8 As shown, the method comprises at least the following steps:

[0219] S802, receiving user behavior record information of each minimum business processing event in the business processing link of the target business sent by the client; wherein the minimum business processing event is a business processing event triggered based on a user operation behavior, and the user behavior record information is generated based on a target page element in a user access page involved in executing the minimum business processing event and description information of the user operation behavior on the user access page;

[0220] S804, uploading the received user behavior record information to the blockchain based on the upload node identifier corresponding to each minimum business processing event.

[0221] Wherein, a trusted execution environment TEE is deployed in the above-mentioned server, and the above-mentioned user behavior record information includes the behavior record information converted in binary form;

[0222] Correspondingly, the above S804, based on the upload node identifier corresponding to each minimum business processing event, uploads the received user behavior record information to the blockchain, specifically including:

[0223] In the trusted execution environment TEE, based on the upload node identifier corresponding to each minimum business processing event and the behavior record information converted in binary form, a user behavior backtracking video stream is generated for displaying the execution of the target business processing based on the user operation behavior;

[0224] The generated user behavior retrospective video stream is uploaded to the blockchain.

[0225] Wherein, in S804, after uploading the received user behavior record information to the blockchain based on the upload node identifier corresponding to each minimum business processing event, it also includes:

[0226] Receiving a behavior record query request sent by a record information query terminal; wherein the behavior record query request carries business processing identification information;

[0227] Obtaining user behavior record information corresponding to the above-mentioned business processing identification information from the blockchain;

[0228] Based on the acquired user behavior record information, a user behavior retrospective video stream is generated for displaying the execution of target business processing based on the user operation behavior;

[0229] The generated user behavior retrospective video stream is sent to the record information query terminal, so that the record information query terminal displays the user behavior retrospective video stream.

[0230] The information storage method in one or more embodiments of the present specification, when performing business processing based on user operation behavior for the target business, automatically generates user behavior record information based on the characteristic information of the target page elements in the user access page and the description information of the user operation behavior, so as to realize efficient and lightweight recording of user behavior information; at the same time, in the process of processing the target business, the user behavior record information corresponding to all the minimum business processing events recorded for the target business is sent to the server in sequence with the minimum business processing event as the minimum information upload node, so as to realize the real-time uploading of the user behavior record information used to trace the handling process of the user's target business to the server, so that in the subsequent business dispute event, the operation behaviors of each user in the target business handling process can be restored based on the user behavior record information, so as to achieve the purpose of defining the responsibility of the business dispute event.

[0231] It should be noted that this embodiment in this specification and the previous embodiment in this specification are based on the same inventive concept, so the specific implementation of this embodiment can refer to the implementation of the aforementioned information storage method, and the repeated parts will not be repeated.

[0232] Corresponding to the above Figures 1 to 6 The information recording method described above is based on the same technical concept. One or more embodiments of this specification also provide an information recording device, which is arranged at a client. Fig. 9 A schematic diagram of the module composition of an information recording device provided in one or more embodiments of this specification, the device is used to perform Figures 1 to 6 The information recording method described, such as Fig. 9 As shown, the device comprises:

[0233] A target page element determination module 902, which determines, for a minimum business processing event of a target business triggered by a user operation behavior, a target page element in a user access page involved in executing the minimum business processing event; and

[0234] A behavior description information determination module 904, which obtains description information of the user's operation behavior on the user access page;

[0235] A behavior record information generating module 906, which generates user behavior record information corresponding to the minimum business processing event according to the characteristic information of the target page element and the description information;

[0236] The behavior record information uploading module 908 uses the minimum business processing event as the minimum information uploading node and sends the user behavior record information of each minimum business processing event in the business processing link of the target business to the server.

[0237] Optionally, the above device further includes: a long link establishment module, which:

[0238] If the minimum service processing event is a home page access event for the target service, a long link establishment request is sent to the server to establish a long link between the server and the client;

[0239] Correspondingly, the behavior record information uploading module 908:

[0240] Using the long link, sending the user behavior record information of each of the minimum business processing events in the business processing link of the target business to the server;

[0241] Correspondingly, the above device further includes: a long link disconnection module, which:

[0242] If the minimum service processing event is a service processing end event for the target service, a long link disconnection request is sent to the server to disconnect the long link between the server and the client.

[0243] Optionally, the above device further includes: a reissue record determination module, which:

[0244] Receiving information storage feedback information returned by the server in response to the user behavior record information;

[0245] Based on the information storage feedback information, the behavior record information to be reissued is determined from the user behavior record information that has been sent.

[0246] Optionally, the reissue record determination module:

[0247] Based on the information storage feedback information, determining a target node identifier corresponding to the stored user behavior record information;

[0248] According to the target node identifier and the upload node identifier corresponding to the sent user behavior record information, the behavior record information to be reissued is determined from the sent user behavior record information.

[0249] Optionally, the reissue record determination module:

[0250] Based on the information storage feedback information, updating the storage status type of the sent user behavior record information;

[0251] According to the updated storage status type, the behavior record information to be reissued is determined from the sent user behavior record information.

[0252] Optionally, the upload node identifier includes: an operation behavior timestamp, and the information storage feedback information includes: a target operation timestamp corresponding to the currently stored user behavior record information;

[0253] The reissue record determination module:

[0254] Update the storage status type of the user behavior record information whose operation behavior timestamp is equal to the target operation timestamp to stored; and

[0255] Determine, in the sent user behavior record information, a storage state type of target behavior record information whose operation behavior timestamp is earlier than the target operation timestamp;

[0256] If the storage status type is not stored, the storage status type of the target behavior record information is updated to pending reissue.

[0257] Optionally, the information storage feedback information includes: a target node identifier corresponding to the currently stored user behavior record information;

[0258] The reissue record determination module:

[0259] updating the storage status type of the user behavior record information corresponding to the target node identifier to stored; and

[0260] Determine whether the target node identifier and the previous uploading node identifier fed back by the server are adjacent node identifiers;

[0261] If it is not an adjacent node identifier, determining the storage state type of the target behavior record information corresponding to the intermediate upload node identifier between the target node identifier and the previous upload node identifier;

[0262] If the storage status type is not stored, the storage status type of the target behavior record information is updated to pending reissue.

[0263] Optionally, the above device further includes: a first information resending module, which:

[0264] Determine at least one piece of behavior record information that is currently remaining and to be reissued;

[0265] Sending the at least one to-be-reissued behavior record information to the server by using the long link;

[0266] Determining whether all of the at least one behavior record information to be reissued has been stored in the server based on information storage feedback information returned by the server for the behavior record information to be reissued;

[0267] Correspondingly, the long link disconnection module:

[0268] If it is determined that all the data has been stored, a long link disconnection request is sent to the server.

[0269] Optionally, the above device further includes: a second information re-issuing module, which:

[0270] Acquire the pending reissue behavior record information cached locally, and send the pending reissue behavior record information to the server;

[0271] Correspondingly, the reissue record determination module

[0272] Receiving reissue information storage feedback information returned by the server for the to-be-reissued action record information;

[0273] Based on the reissue information storage feedback information, at least one remaining behavior record information to be reissued is determined.

[0274] Optionally, the behavior record information uploading module 908:

[0275] For each of the user behavior record information, generate behavior record information in binary format corresponding to the user behavior record information;

[0276] Sending the behavior record information in binary form corresponding to each of the minimum business processing events in the business processing link of the target business to the server.

[0277] Optionally, the target page element determination module 902:

[0278] Monitoring whether there is an updated target CSS style in the CSS style corresponding to the user access page involved in executing the minimum business processing event; wherein the target CSS style is updated by a business processing module of the first application corresponding to the target business based on the minimum business processing event;

[0279] Monitoring whether there is an updated target DOM node in the DOM structure corresponding to the user access page involved in executing the minimum business processing event; wherein the target DOM node is updated by the business processing module of the first application corresponding to the target business based on the minimum business processing event;

[0280] The target CSS style and / or the page element corresponding to the target DOM node is determined as the target page element that changes based on the user operation behavior.

[0281] Optionally, the behavior description information determining module 904:

[0282] Receive description information of the user operation behavior sent by the business processing module of the first application corresponding to the target business; wherein the description information is information generated based on the annotation information associated with the page element targeted by the user operation behavior when the business processing module executes the minimum business processing event; the annotation information is used to describe the operational meaning of the user operation behavior.

[0283] The information recording device in one or more embodiments of the present specification, when performing business processing on a target business based on user operation behavior, automatically generates user behavior record information based on feature information of target page elements in the user access page and description information of the user operation behavior, thereby realizing efficient and lightweight recording of user behavior information; at the same time, during the target business processing process, the user behavior record information corresponding to all minimum business processing events recorded for the target business is sent to the server in sequence with the minimum business processing event as the minimum information upload node, thereby realizing real-time uploading of user behavior record information used to trace the handling process of the user's target business to the server, so that in subsequent business dispute events, the operation behaviors of each user in the target business handling process can be restored based on the user behavior record information, thereby achieving the purpose of defining the responsibility for the business dispute events.

[0284] It should be noted that the embodiments of the information recording device in this specification and the embodiments of the information recording method in this specification are based on the same inventive concept, so the specific implementation of this embodiment can refer to the implementation of the corresponding information recording method mentioned above, and the repeated parts will not be repeated.

[0285] Corresponding to the above Figure 7 The information storage method described above is based on the same technical concept. One or more embodiments of this specification also provide an information storage device, which is arranged at a server end. Fig.10 A schematic diagram of the module composition of an information storage device provided in one or more embodiments of this specification, the device is used to execute Figure 7 Describes the information storage method, such as Fig.10 As shown, the device comprises:

[0286] The behavior record information receiving module 1002 receives the user behavior record information of each minimum business processing event in the business processing link of the target business sent by the client; wherein the minimum business processing event is a business processing event triggered based on the user operation behavior, and the user behavior record information is generated based on the target page element in the user access page involved in executing the minimum business processing event and the description information of the user operation behavior on the user access page;

[0287] The behavior record information storage module 1004 stores the user behavior record information based on the upload node identifier corresponding to each of the minimum business processing events.

[0288] Optionally, the above device further includes: a long link establishment module, which:

[0289] Receiving a long link establishment request sent by a client; wherein the long link establishment request is issued by the client when determining that the minimum business processing event currently being executed is a home page access event for a target business;

[0290] In response to the long link establishment request, a long link is established with the client.

[0291] Optionally, the behavior record information receiving module 1002:

[0292] The user behavior record information of each minimum business processing event in the business processing link of the target business sent by the client is received by using the long link.

[0293] Optionally, the above device further comprises: a long link disconnection module, which:

[0294] Receiving a long link disconnection request sent by a client; wherein the long link disconnection request is sent by the client when determining that the currently executed minimum business processing event is a business processing end event for a target business;

[0295] In response to the long link disconnection request, disconnect the long link from the client.

[0296] Optionally, the above device further includes: an information query response module, which:

[0297] Receiving a behavior record query request sent by a record information query terminal; wherein the behavior record query request carries business processing identification information;

[0298] Acquire the user behavior record information corresponding to the business processing identification information;

[0299] Based on the user behavior record information, a user behavior retrospective video stream is generated for showing the execution of target business processing based on the user operation behavior;

[0300] The user behavior retrospective video stream is sent to the record information query terminal, so that the record information query terminal displays the user behavior retrospective video stream.

[0301] The information storage device in one or more embodiments of the present specification, when performing business processing for a target business based on user operation behavior, automatically generates user behavior record information based on feature information of target page elements in the user access page and description information of the user operation behavior, thereby realizing efficient and lightweight recording of user behavior information; at the same time, during the target business processing process, the user behavior record information corresponding to all minimum business processing events recorded for the target business is sent to the server in sequence with the minimum business processing event as the minimum information upload node, thereby realizing real-time uploading of user behavior record information used to trace the handling process of the user's target business to the server, so that in subsequent business dispute events, the operation behaviors of each user in the target business handling process can be restored based on the user behavior record information, thereby achieving the purpose of defining the responsibility for the business dispute events.

[0302] It should be noted that the embodiments of the information storage device in this specification and the embodiments of the information recording method in this specification are based on the same inventive concept, so the specific implementation of this embodiment can refer to the implementation of the corresponding information recording method mentioned above, and the repeated parts will not be repeated.

[0303] Corresponding to the above Figure 8 The information storage method described above is based on the same technical concept. One or more embodiments of this specification also provide an information storage device, which is arranged on a server connected to the blockchain. Fig.11 A schematic diagram of the module composition of an information storage device provided in one or more embodiments of this specification, the device is used to execute Figure 8 Describes the information storage method, such as Fig.11 As shown, the device comprises:

[0304] The behavior record information receiving module 1102 receives the user behavior record information of each minimum business processing event in the business processing link of the target business sent by the client; wherein the minimum business processing event is a business processing event triggered based on the user operation behavior, and the user behavior record information is generated based on the target page element in the user access page involved in executing the minimum business processing event and the description information of the user operation behavior on the user access page;

[0305] The behavior record information chain module 1104 uploads the user behavior record information to the blockchain based on the upload node identifier corresponding to each of the minimum business processing events.

[0306] Optionally, a trusted execution environment TEE is deployed in the server, and the user behavior record information includes behavior record information converted in binary form;

[0307] The behavior record information uploading module 1104:

[0308] In the trusted execution environment TEE, based on the upload node identifier corresponding to each of the minimum business processing events and the behavior record information converted in binary form, a user behavior backtracking video stream is generated for displaying the execution of the target business processing based on the user operation behavior;

[0309] The user behavior retrospective video stream is uploaded to the blockchain.

[0310] Optionally, the above device further includes: an information query response module, which:

[0311] Receiving a behavior record query request sent by a record information query terminal; wherein the behavior record query request carries business processing identification information;

[0312] Obtaining the user behavior record information corresponding to the business processing identification information from the blockchain;

[0313] Based on the user behavior record information, a user behavior retrospective video stream is generated for showing the execution of target business processing based on the user operation behavior;

[0314] The user behavior retrospective video stream is sent to the record information query terminal, so that the record information query terminal displays the user behavior retrospective video stream.

[0315] The information storage device in one or more embodiments of the present specification, when performing business processing for a target business based on user operation behavior, automatically generates user behavior record information based on feature information of target page elements in the user access page and description information of the user operation behavior, thereby realizing efficient and lightweight recording of user behavior information; at the same time, during the target business processing process, the user behavior record information corresponding to all minimum business processing events recorded for the target business is sent to the server in sequence with the minimum business processing event as the minimum information upload node, thereby realizing real-time uploading of user behavior record information used to trace the handling process of the user's target business to the server, so that in subsequent business dispute events, the operation behaviors of each user in the target business handling process can be restored based on the user behavior record information, thereby achieving the purpose of defining the responsibility for the business dispute events.

[0316] It should be noted that the embodiments of the information storage device in this specification and the embodiments of the information recording method in this specification are based on the same inventive concept, so the specific implementation of this embodiment can refer to the implementation of the corresponding information recording method mentioned above, and the repeated parts will not be repeated.

[0317] Corresponding to the above Figures 1 to 6The information recording method described above is based on the same technical concept, and one or more embodiments of this specification also provide an information storage system. Fig.12 A schematic diagram of the structure of an information storage system provided in one or more embodiments of this specification, the system is used to execute Figures 1 to 6 The information recording method described, such as Fig.12 As shown, the system includes: a client and a server;

[0318] The client determines, for a minimum business processing event of a target business triggered by a user operation behavior, a target page element in a user access page involved in executing the minimum business processing event; and obtains description information of the user operation behavior on the user access page;

[0319] generating user behavior record information corresponding to the minimum business processing event according to the characteristic information of the target page element and the description information; and

[0320] Taking the minimum business processing event as the minimum information uploading node, sending the user behavior record information of each minimum business processing event in the business processing link of the target business to the server;

[0321] The server receives the user behavior record information and stores the user behavior record information based on the upload node identifier corresponding to each of the minimum business processing events.

[0322] The information storage system in one or more embodiments of the present specification, when performing business processing for a target business based on user operation behavior, automatically generates user behavior record information based on feature information of target page elements in the user access page and description information of the user operation behavior, thereby realizing efficient and lightweight recording of user behavior information; at the same time, during the target business processing process, the user behavior record information corresponding to all minimum business processing events recorded for the target business is sent to the server in sequence, taking the minimum business processing event as the minimum information upload node, thereby realizing real-time uploading of user behavior record information used to trace the handling process of the user's target business to the server, so that in subsequent business dispute events, the operation behaviors of each user in the target business handling process can be restored based on the user behavior record information, thereby achieving the purpose of defining the responsibility for business dispute events.

[0323] It should be noted that the embodiments of the information storage system in this specification and the embodiments of the information recording method in this specification are based on the same inventive concept, so the specific implementation of this embodiment can refer to the implementation of the corresponding information recording method mentioned above, and the repeated parts will not be repeated.

[0324] Furthermore, corresponding to the above Figures 1 to 6Based on the same technical concept, one or more embodiments of this specification also provide an information recording device, which is used to execute the above-mentioned information recording method, such as Fig.13 shown.

[0325] The information recording device may have relatively large differences due to different configurations or performances, and may include one or more processors 1301 and memory 1302, and the memory 1302 may store one or more storage applications or data. Among them, the memory 1302 may be a temporary storage or a permanent storage. The application stored in the memory 1302 may include one or more modules (not shown in the figure), and each module may include a series of computer executable instructions in the information recording device. Furthermore, the processor 1301 may be configured to communicate with the memory 1302 to execute a series of computer executable instructions in the memory 1302 on the information recording device. The information recording device may also include one or more power supplies 1303, one or more wired or wireless network interfaces 1304, one or more input and output interfaces 1305, one or more keyboards 1306, etc.

[0326] In a specific embodiment, the information recording device includes a memory and one or more programs, wherein the one or more programs are stored in the memory, and the one or more programs may include one or more modules, and each module may include a series of computer executable instructions in the information recording device, and the one or more programs are configured to be executed by one or more processors, including computer executable instructions for performing the following:

[0327] For a minimum business processing event of a target business triggered by a user operation behavior, determining a target page element in a user access page involved in executing the minimum business processing event; and

[0328] Obtaining description information of the user's operation behavior on the user access page;

[0329] Generating user behavior record information corresponding to the minimum business processing event according to the characteristic information of the target page element and the description information;

[0330] The minimum service processing event is used as the minimum information uploading node, and the user behavior record information of each minimum service processing event in the service processing link of the target service is sent to the server.

[0331] Optionally, when the computer executable instructions are executed, they further include computer executable instructions for performing the following:

[0332] If the minimum service processing event is a home page access event for the target service, a long link establishment request is sent to the server to establish a long link between the server and the client;

[0333] Correspondingly, the sending of the user behavior record information of each of the minimum business processing events in the business processing link of the target business to the server includes:

[0334] Using the long link, sending the user behavior record information of each of the minimum business processing events in the business processing link of the target business to the server;

[0335] If the minimum service processing event is a service processing end event for the target service, a long link disconnection request is sent to the server to disconnect the long link between the server and the client.

[0336] Optionally, when the computer executable instructions are executed, after sending the user behavior record information of each of the minimum business processing events in the business processing link of the target business to the server, the instructions further include:

[0337] Receiving information storage feedback information returned by the server in response to the user behavior record information;

[0338] Based on the information storage feedback information, the behavior record information to be reissued is determined from the user behavior record information that has been sent.

[0339] Optionally, when the computer executable instructions are executed, the step of determining the behavior record information to be reissued from the sent user behavior record information based on the information storage feedback information includes:

[0340] Based on the information storage feedback information, determining a target node identifier corresponding to the stored user behavior record information;

[0341] According to the target node identifier and the upload node identifier corresponding to the sent user behavior record information, the behavior record information to be reissued is determined from the sent user behavior record information.

[0342] Optionally, when the computer executable instructions are executed, the step of determining the behavior record information to be reissued from the sent user behavior record information based on the information storage feedback information includes:

[0343] Based on the information storage feedback information, updating the storage status type of the sent user behavior record information;

[0344] According to the updated storage status type, the behavior record information to be reissued is determined from the sent user behavior record information.

[0345] Optionally, when the computer executable instruction is executed, the upload node identifier includes: an operation behavior timestamp, and the information storage feedback information includes: a target operation timestamp corresponding to the currently stored user behavior record information;

[0346] The updating of the storage status type of the sent user behavior record information based on the information storage feedback information includes:

[0347] Update the storage status type of the user behavior record information whose operation behavior timestamp is equal to the target operation timestamp to stored; and

[0348] Determine, in the sent user behavior record information, a storage state type of target behavior record information whose operation behavior timestamp is earlier than the target operation timestamp;

[0349] If the storage status type is not stored, the storage status type of the target behavior record information is updated to pending reissue.

[0350] Optionally, when the computer executable instruction is executed, the information storage feedback information includes: a target node identifier corresponding to the currently stored user behavior record information;

[0351] The updating of the storage status type of the sent user behavior record information based on the information storage feedback information includes:

[0352] updating the storage status type of the user behavior record information corresponding to the target node identifier to stored; and

[0353] Determine whether the target node identifier and the previous uploading node identifier fed back by the server are adjacent node identifiers;

[0354] If it is not an adjacent node identifier, determining the storage state type of the target behavior record information corresponding to the intermediate upload node identifier between the target node identifier and the previous upload node identifier;

[0355] If the storage status type is not stored, the storage status type of the target behavior record information is updated to pending reissue.

[0356] Optionally, when the computer executable instruction is executed, sending a long link disconnection request to the server includes:

[0357] Determine at least one piece of behavior record information that is currently remaining and to be reissued;

[0358] Sending the at least one to-be-reissued behavior record information to the server by using the long link;

[0359] Determining whether all of the at least one behavior record information to be reissued has been stored in the server based on information storage feedback information returned by the server for the behavior record information to be reissued;

[0360] If it is determined that all the data has been stored, a long link disconnection request is sent to the server.

[0361] Optionally, when the computer executable instructions are executed, after determining the behavior record information to be reissued from the sent user behavior record information based on the information storage feedback information, further comprising:

[0362] Obtaining the pending reissue behavior record information cached locally, and sending the pending reissue behavior record information to the server;

[0363] Receiving reissue information storage feedback information returned by the server for the to-be-reissued action record information;

[0364] Based on the reissue information storage feedback information, at least one remaining behavior record information to be reissued is determined.

[0365] Optionally, when the computer executable instruction is executed, the sending of the user behavior record information of each minimum business processing event in the business processing link of the target business to the server includes:

[0366] For each of the user behavior record information, generate behavior record information in binary format corresponding to the user behavior record information;

[0367] Sending the behavior record information in binary form corresponding to each of the minimum business processing events in the business processing link of the target business to the server.

[0368] Optionally, when the computer executable instructions are executed, the determining of a target page element in a user access page involved in executing the minimum business processing event includes:

[0369] Monitoring whether there is an updated target CSS style in the CSS style corresponding to the user access page involved in executing the minimum business processing event; wherein the target CSS style is updated by a business processing module of the first application corresponding to the target business based on the minimum business processing event;

[0370] Monitoring whether there is an updated target DOM node in the DOM structure corresponding to the user access page involved in executing the minimum business processing event; wherein the target DOM node is updated by the business processing module of the first application corresponding to the target business based on the minimum business processing event;

[0371] The target CSS style and / or the page element corresponding to the target DOM node is determined as the target page element that changes based on the user operation behavior.

[0372] Optionally, when the computer executable instruction is executed, obtaining the description information of the user operation behavior on the user access page includes:

[0373] Receive description information of the user operation behavior sent by the business processing module of the first application corresponding to the target business; wherein the description information is information generated based on the annotation information associated with the page element targeted by the user operation behavior when the business processing module executes the minimum business processing event; the annotation information is used to describe the operational meaning of the user operation behavior.

[0374] The information recording device in one or more embodiments of the present specification, when performing business processing for a target business based on user operation behavior, automatically generates user behavior record information based on feature information of target page elements in the user access page and description information of the user operation behavior, thereby realizing efficient and lightweight recording of user behavior information; at the same time, during the target business processing process, the user behavior record information corresponding to all minimum business processing events recorded for the target business is sent to the server in sequence, taking the minimum business processing event as the minimum information upload node, thereby realizing real-time uploading of user behavior record information used to trace the handling process of the user's target business to the server, so that in subsequent business dispute events, the operation behaviors of each user in the target business handling process can be restored based on the user behavior record information, thereby achieving the purpose of defining the responsibility for the business dispute events.

[0375] Furthermore, corresponding to the above Figures 7 and 8 Based on the same technical concept, one or more embodiments of this specification also provide an information storage device, which is used to execute the above-mentioned information recording method, such as Fig.14 shown.

[0376] The information storage device may have relatively large differences due to different configurations or performances, and may include one or more processors 1401 and memory 1402, and the memory 1402 may store one or more storage applications or data. Among them, the memory 1402 may be a short-term storage or a persistent storage. The application stored in the memory 1402 may include one or more modules (not shown in the figure), and each module may include a series of computer executable instructions in the information storage device. Furthermore, the processor 1401 may be configured to communicate with the memory 1402 and execute a series of computer executable instructions in the memory 1402 on the information storage device. The information storage device may also include one or more power supplies 1403, one or more wired or wireless network interfaces 1404, one or more input and output interfaces 1405, one or more keyboards 1406, etc.

[0377] In a specific embodiment, the information storage device includes a memory and one or more programs, wherein the one or more programs are stored in the memory, and the one or more programs may include one or more modules, and each module may include a series of computer executable instructions in the information storage device, and the one or more programs configured to be executed by one or more processors include the following computer executable instructions:

[0378] The information storage device includes a memory and one or more programs, wherein the one or more programs are stored in the memory, and the one or more programs may include one or more modules, and each module may include a series of computer executable instructions in the information storage device, and the one or more programs are configured to be executed by one or more processors, including computer executable instructions for performing the following:

[0379] Receive user behavior record information of each minimum business processing event in the business processing link of the target business sent by the client; wherein the minimum business processing event is a business processing event triggered based on a user operation behavior, and the user behavior record information is generated based on the target page element in the user access page involved in executing the minimum business processing event and the description information of the user operation behavior on the user access page;

[0380] Based on the upload node identifier corresponding to each of the minimum business processing events, the user behavior record information is stored.

[0381] Optionally, when the computer executable instructions are executed, before receiving the user behavior record information of each minimum business processing event in the business processing link of the target business sent by the client, the computer executable instructions further include:

[0382] Receiving a long link establishment request sent by a client; wherein the long link establishment request is issued by the client when determining that the minimum business processing event currently being executed is a home page access event for a target business;

[0383] In response to the long link establishment request, a long link is established with the client.

[0384] Optionally, when the computer executable instruction is executed, the user behavior record information of each minimum business processing event in the business processing link of the target business sent by the receiving client includes:

[0385] The user behavior record information of each minimum business processing event in the business processing link of the target business sent by the client is received by using the long link.

[0386] Optionally, when the computer executable instructions are executed, after receiving the user behavior record information of each minimum business processing event in the business processing link of the target business sent by the client using the long link, the computer executable instructions further include:

[0387] Receiving a long link disconnection request sent by a client; wherein the long link disconnection request is sent by the client when determining that the currently executed minimum business processing event is a business processing end event for a target business;

[0388] In response to the long link disconnection request, the long link with the client is disconnected.

[0389] Optionally, when the computer executable instructions are executed, after storing the user behavior record information based on the upload node identifier corresponding to each of the minimum business processing events, the computer executable instructions further include:

[0390] Receiving a behavior record query request sent by a record information query terminal; wherein the behavior record query request carries business processing identification information;

[0391] Acquire the user behavior record information corresponding to the business processing identification information;

[0392] Based on the user behavior record information, a user behavior retrospective video stream is generated for showing the execution of target business processing based on the user operation behavior;

[0393] The user behavior retrospective video stream is sent to the record information query terminal, so that the record information query terminal displays the user behavior retrospective video stream.

[0394] The information storage device in one or more embodiments of the present specification, when performing business processing for a target business based on user operation behavior, automatically generates user behavior record information based on feature information of target page elements in the user access page and description information of the user operation behavior, thereby realizing efficient and lightweight recording of user behavior information; at the same time, during the target business processing process, the user behavior record information corresponding to all minimum business processing events recorded for the target business is sent to the server in sequence with the minimum business processing event as the minimum information upload node, thereby realizing real-time uploading of user behavior record information used to trace the handling process of the user's target business to the server, so that in subsequent business dispute events, the operation behaviors of each user in the target business handling process can be restored based on the user behavior record information, thereby achieving the purpose of defining the responsibility for the business dispute events.

[0395] In another specific embodiment, the information storage device includes a memory and one or more programs, wherein the one or more programs are stored in the memory, and the one or more programs may include one or more modules, and each module may include a series of computer executable instructions in the information storage device, and the one or more programs are configured to be executed by one or more processors, including computer executable instructions for performing the following:

[0396] Receive user behavior record information of each minimum business processing event in the business processing link of the target business sent by the client; wherein the minimum business processing event is a business processing event triggered based on a user operation behavior, and the user behavior record information is generated based on the target page element in the user access page involved in executing the minimum business processing event and the description information of the user operation behavior on the user access page;

[0397] Based on the upload node identifier corresponding to each of the minimum business processing events, the user behavior record information is uploaded to the blockchain.

[0398] Optionally, when the computer executable instruction is executed, a trusted execution environment TEE is deployed in the server, and the user behavior record information includes the behavior record information converted in binary form;

[0399] The uploading of the user behavior record information to the blockchain based on the upload node identifier corresponding to each of the minimum business processing events includes:

[0400] In the trusted execution environment TEE, based on the upload node identifier corresponding to each of the minimum business processing events and the behavior record information converted in binary form, a user behavior backtracking video stream is generated for displaying the execution of the target business processing based on the user operation behavior;

[0401] The user behavior retrospective video stream is uploaded to the blockchain.

[0402] Optionally, when the computer executable instructions are executed, after uploading the user behavior record information to the blockchain based on the upload node identifier corresponding to each of the minimum business processing events, the computer executable instructions further include:

[0403] Receiving a behavior record query request sent by a record information query terminal; wherein the behavior record query request carries business processing identification information;

[0404] Obtaining the user behavior record information corresponding to the business processing identification information from the blockchain;

[0405] Based on the user behavior record information, a user behavior retrospective video stream is generated for showing the execution of target business processing based on the user operation behavior;

[0406] The user behavior retrospective video stream is sent to the record information query terminal, so that the record information query terminal displays the user behavior retrospective video stream.

[0407] The information storage device in one or more embodiments of the present specification, when performing business processing for a target business based on user operation behavior, automatically generates user behavior record information based on feature information of target page elements in the user access page and description information of the user operation behavior, thereby realizing efficient and lightweight recording of user behavior information; at the same time, during the target business processing process, the user behavior record information corresponding to all minimum business processing events recorded for the target business is sent to the server in sequence with the minimum business processing event as the minimum information upload node, thereby realizing real-time uploading of user behavior record information used to trace the handling process of the user's target business to the server, so that in subsequent business dispute events, the operation behaviors of each user in the target business handling process can be restored based on the user behavior record information, thereby achieving the purpose of defining the responsibility for the business dispute events.

[0408] It should be noted that the embodiments of the information storage device in this specification and the embodiments of the information recording method in this specification are based on the same inventive concept, so the specific implementation of this embodiment can refer to the implementation of the corresponding information recording method mentioned above, and the repeated parts will not be repeated.

[0409] Furthermore, corresponding to the above Figures 1 to 6The method shown is based on the same technical concept. One or more embodiments of this specification also provide a storage medium for storing computer executable instructions. In a specific embodiment, the storage medium can be a USB flash drive, an optical disk, a hard disk, etc. When the computer executable instructions stored in the storage medium are executed by the processor, the following process can be implemented:

[0410] For a minimum business processing event of a target business triggered by a user operation behavior, determining a target page element in a user access page involved in executing the minimum business processing event; and

[0411] Obtaining description information of the user's operation behavior on the user access page;

[0412] Generating user behavior record information corresponding to the minimum business processing event according to the characteristic information of the target page element and the description information;

[0413] The minimum service processing event is used as the minimum information uploading node, and the user behavior record information of each minimum service processing event in the service processing link of the target service is sent to the server.

[0414] Optionally, when the computer executable instructions stored in the storage medium are executed by the processor, the following process is also implemented:

[0415] If the minimum service processing event is a home page access event for the target service, a long link establishment request is sent to the server to establish a long link between the server and the client;

[0416] Correspondingly, the sending of the user behavior record information of each of the minimum business processing events in the business processing link of the target business to the server includes:

[0417] Using the long link, sending the user behavior record information of each of the minimum business processing events in the business processing link of the target business to the server;

[0418] If the minimum service processing event is a service processing end event for the target service, a long link disconnection request is sent to the server to disconnect the long link between the server and the client.

[0419] Optionally, when the computer executable instructions stored in the storage medium are executed by the processor, after sending the user behavior record information of each of the minimum business processing events in the business processing link of the target business to the server, the computer executable instructions further include:

[0420] Receiving information storage feedback information returned by the server in response to the user behavior record information;

[0421] Based on the information storage feedback information, the behavior record information to be reissued is determined from the user behavior record information that has been sent.

[0422] Optionally, when the computer executable instructions stored in the storage medium are executed by the processor, the step of determining the behavior record information to be reissued from the sent user behavior record information based on the information storage feedback information includes:

[0423] Based on the information storage feedback information, determining a target node identifier corresponding to the stored user behavior record information;

[0424] According to the target node identifier and the upload node identifier corresponding to the sent user behavior record information, the behavior record information to be reissued is determined from the sent user behavior record information.

[0425] Optionally, when the computer executable instructions stored in the storage medium are executed by the processor, the step of determining the behavior record information to be reissued from the sent user behavior record information based on the information storage feedback information includes:

[0426] Based on the information storage feedback information, updating the storage status type of the sent user behavior record information;

[0427] According to the updated storage status type, the behavior record information to be reissued is determined from the sent user behavior record information.

[0428] Optionally, when the computer executable instructions stored in the storage medium are executed by the processor, the upload node identifier includes: an operation behavior timestamp, and the information storage feedback information includes: a target operation timestamp corresponding to the currently stored user behavior record information;

[0429] The updating of the storage status type of the sent user behavior record information based on the information storage feedback information includes:

[0430] Update the storage status type of the user behavior record information whose operation behavior timestamp is equal to the target operation timestamp to stored; and

[0431] Determine, in the sent user behavior record information, a storage state type of target behavior record information whose operation behavior timestamp is earlier than the target operation timestamp;

[0432] If the storage status type is not stored, the storage status type of the target behavior record information is updated to pending reissue.

[0433] Optionally, when the computer executable instructions stored in the storage medium are executed by the processor, the information storage feedback information includes: a target node identifier corresponding to the currently stored user behavior record information;

[0434] The updating of the storage status type of the sent user behavior record information based on the information storage feedback information includes:

[0435] updating the storage status type of the user behavior record information corresponding to the target node identifier to stored; and

[0436] Determine whether the target node identifier and the previous uploading node identifier fed back by the server are adjacent node identifiers;

[0437] If it is not an adjacent node identifier, determining the storage state type of the target behavior record information corresponding to the intermediate upload node identifier between the target node identifier and the previous upload node identifier;

[0438] If the storage status type is not stored, the storage status type of the target behavior record information is updated to pending reissue.

[0439] Optionally, when the computer executable instructions stored in the storage medium are executed by the processor, sending a long link disconnection request to the server includes:

[0440] Determine at least one piece of behavior record information that is currently remaining and to be reissued;

[0441] Sending the at least one to-be-reissued behavior record information to the server by using the long link;

[0442] Determining whether all of the at least one behavior record information to be reissued has been stored in the server based on information storage feedback information returned by the server for the behavior record information to be reissued;

[0443] If it is determined that all the data has been stored, a long link disconnection request is sent to the server.

[0444] Optionally, when the computer executable instructions stored in the storage medium are executed by the processor, after determining the behavior record information to be reissued from the sent user behavior record information based on the information storage feedback information, further includes:

[0445] Acquire the pending reissue behavior record information cached locally, and send the pending reissue behavior record information to the server;

[0446] Receiving reissue information storage feedback information returned by the server for the to-be-reissued action record information;

[0447] Based on the reissue information storage feedback information, at least one remaining behavior record information to be reissued is determined.

[0448] Optionally, when the computer executable instructions stored in the storage medium are executed by the processor, the sending of the user behavior record information of each minimum business processing event in the business processing link of the target business to the server includes:

[0449] For each of the user behavior record information, generate behavior record information in binary format corresponding to the user behavior record information;

[0450] Sending the behavior record information in binary form corresponding to each of the minimum business processing events in the business processing link of the target business to the server.

[0451] Optionally, when the computer executable instructions stored in the storage medium are executed by the processor, the determining of the target page element in the user access page involved in executing the minimum business processing event includes:

[0452] Monitoring whether there is an updated target CSS style in the CSS style corresponding to the user access page involved in executing the minimum business processing event; wherein the target CSS style is updated by a business processing module of the first application corresponding to the target business based on the minimum business processing event;

[0453] Monitoring whether there is an updated target DOM node in the DOM structure corresponding to the user access page involved in executing the minimum business processing event; wherein the target DOM node is updated by the business processing module of the first application corresponding to the target business based on the minimum business processing event;

[0454] The target CSS style and / or the page element corresponding to the target DOM node is determined as the target page element that changes based on the user operation behavior.

[0455] Optionally, when the computer executable instructions stored in the storage medium are executed by the processor, the obtaining of the description information of the user operation behavior on the user access page includes:

[0456] Receive description information of the user operation behavior sent by the business processing module of the first application corresponding to the target business; wherein the description information is information generated based on the annotation information associated with the page element targeted by the user operation behavior when the business processing module executes the minimum business processing event; the annotation information is used to describe the operational meaning of the user operation behavior.

[0457] When the computer executable instructions stored in the storage medium in one or more embodiments of the present specification are executed by the processor, when business processing is performed on the target business based on the user operation behavior, user behavior record information is automatically generated based on the characteristic information of the target page elements in the user access page and the description information of the user operation behavior, so as to realize efficient and lightweight recording of user behavior information; at the same time, in the process of processing the target business, the user behavior record information corresponding to all the minimum business processing events recorded for the target business is sent to the server in sequence with the minimum business processing event as the minimum information upload node, so as to realize the real-time uploading of the user behavior record information used to trace the processing process of the user's target business to the server, so that in the subsequent business dispute event, the operation behaviors of each user in the target business processing process can be restored based on the user behavior record information, so as to achieve the purpose of defining the responsibility of the business dispute event.

[0458] In another specific embodiment, the storage medium may be a USB flash drive, an optical disk, a hard disk, etc. When the computer executable instructions stored in the storage medium are executed by the processor, the following process can be implemented:

[0459] Receive user behavior record information of each minimum business processing event in the business processing link of the target business sent by the client; wherein the minimum business processing event is a business processing event triggered based on a user operation behavior, and the user behavior record information is generated based on the target page element in the user access page involved in executing the minimum business processing event and the description information of the user operation behavior on the user access page;

[0460] Based on the upload node identifier corresponding to each of the minimum business processing events, the user behavior record information is stored.

[0461] Optionally, when the computer executable instructions stored in the storage medium are executed by the processor, before receiving the user behavior record information of each minimum business processing event in the business processing link of the target business sent by the client, the computer executable instructions further include:

[0462] Receiving a long link establishment request sent by a client; wherein the long link establishment request is issued by the client when determining that the minimum business processing event currently being executed is a home page access event for a target business;

[0463] In response to the long link establishment request, a long link is established with the client.

[0464] Optionally, when the computer executable instructions stored in the storage medium are executed by the processor, the user behavior record information of each minimum business processing event in the business processing link of the target business sent by the receiving client includes:

[0465] The user behavior record information of each minimum business processing event in the business processing link of the target business sent by the client is received by using the long link.

[0466] Optionally, when the computer executable instructions stored in the storage medium are executed by the processor, after receiving the user behavior record information of each minimum business processing event in the business processing link of the target business sent by the client through the long link, the computer executable instructions further include:

[0467] Receiving a long link disconnection request sent by a client; wherein the long link disconnection request is sent by the client when determining that the currently executed minimum business processing event is a business processing end event for a target business;

[0468] In response to the long link disconnection request, the long link with the client is disconnected.

[0469] Optionally, when the computer executable instructions stored in the storage medium are executed by the processor, after storing the user behavior record information based on the upload node identifier corresponding to each of the minimum business processing events, the computer executable instructions further include:

[0470] Receiving a behavior record query request sent by a record information query terminal; wherein the behavior record query request carries business processing identification information;

[0471] Acquire the user behavior record information corresponding to the business processing identification information;

[0472] Based on the user behavior record information, a user behavior retrospective video stream is generated for showing the execution of target business processing based on the user operation behavior;

[0473] The user behavior retrospective video stream is sent to the record information query terminal, so that the record information query terminal displays the user behavior retrospective video stream.

[0474] When the computer executable instructions stored in the storage medium in one or more embodiments of the present specification are executed by the processor, when business processing is performed on the target business based on the user operation behavior, user behavior record information is automatically generated based on the characteristic information of the target page elements in the user access page and the description information of the user operation behavior, so as to realize efficient and lightweight recording of user behavior information; at the same time, in the process of processing the target business, the user behavior record information corresponding to all the minimum business processing events recorded for the target business is sent to the server in sequence with the minimum business processing event as the minimum information upload node, so as to realize the real-time uploading of the user behavior record information used to trace the processing process of the user's target business to the server, so that in the subsequent business dispute event, the operation behaviors of each user in the target business processing process can be restored based on the user behavior record information, so as to achieve the purpose of defining the responsibility of the business dispute event.

[0475] In another specific embodiment, the storage medium may be a USB flash drive, an optical disk, a hard disk, etc. When the computer executable instructions stored in the storage medium are executed by the processor, the following process can be implemented:

[0476] Receive user behavior record information of each minimum business processing event in the business processing link of the target business sent by the client; wherein the minimum business processing event is a business processing event triggered based on a user operation behavior, and the user behavior record information is generated based on the target page element in the user access page involved in executing the minimum business processing event and the description information of the user operation behavior on the user access page;

[0477] Based on the upload node identifier corresponding to each of the minimum business processing events, the user behavior record information is uploaded to the blockchain.

[0478] Optionally, when the computer executable instructions stored in the storage medium are executed by the processor, a trusted execution environment TEE is deployed in the server, and the user behavior record information includes behavior record information converted in binary form;

[0479] The uploading of the user behavior record information to the blockchain based on the upload node identifier corresponding to each of the minimum business processing events includes:

[0480] In the trusted execution environment TEE, based on the upload node identifier corresponding to each of the minimum business processing events and the behavior record information converted in binary form, a user behavior backtracking video stream is generated for displaying the execution of the target business processing based on the user operation behavior;

[0481] The user behavior retrospective video stream is uploaded to the blockchain.

[0482] Optionally, when the computer executable instructions stored in the storage medium are executed by the processor, after uploading the user behavior record information to the blockchain based on the upload node identifier corresponding to each of the minimum business processing events, the computer executable instructions further include:

[0483] Receiving a behavior record query request sent by a record information query terminal; wherein the behavior record query request carries business processing identification information;

[0484] Obtaining the user behavior record information corresponding to the business processing identification information from the blockchain;

[0485] Based on the user behavior record information, a user behavior retrospective video stream is generated for showing the execution of target business processing based on the user operation behavior;

[0486] The user behavior retrospective video stream is sent to the record information query terminal, so that the record information query terminal displays the user behavior retrospective video stream.

[0487] When the computer executable instructions stored in the storage medium in one or more embodiments of the present specification are executed by the processor, when business processing is performed on the target business based on the user operation behavior, user behavior record information is automatically generated based on the characteristic information of the target page elements in the user access page and the description information of the user operation behavior, so as to realize efficient and lightweight recording of user behavior information; at the same time, in the process of processing the target business, the user behavior record information corresponding to all the minimum business processing events recorded for the target business is sent to the server in sequence with the minimum business processing event as the minimum information upload node, so as to realize the real-time uploading of the user behavior record information used to trace the processing process of the user's target business to the server, so that in the subsequent business dispute event, the operation behaviors of each user in the target business processing process can be restored based on the user behavior record information, so as to achieve the purpose of defining the responsibility of the business dispute event.

[0488] It should be noted that the embodiments of the storage medium in this specification and the embodiments of the information recording method in this specification are based on the same inventive concept, so the specific implementation of this embodiment can refer to the implementation of the corresponding information recording method mentioned above, and the repeated parts will not be repeated.

[0489] The above is a description of a specific embodiment of the 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.

[0490] In the 1990s, improvements to a technology could be clearly distinguished as hardware improvements (for example, improvements to the circuit structure of diodes, transistors, switches, etc.) or software improvements (improvements to the method flow). However, with the development of technology, many improvements to the method flow today can be regarded as direct improvements to the hardware circuit structure. Designers almost always obtain the corresponding hardware circuit structure by programming the improved method flow into the hardware circuit. Therefore, it cannot be said that an improvement in a method flow cannot be implemented using a hardware entity module. For example, a programmable logic device (PLD) (such as a field programmable gate array (FPGA)) is such an integrated circuit whose logical function is determined by the user's programming of the device. Designers can "integrate" a digital system on a PLD by programming it themselves, without having to ask a chip manufacturer to design and produce a dedicated integrated circuit chip. Moreover, nowadays, instead of manually making integrated circuit chips, this kind of programming is mostly implemented by "logic compiler" software, which is similar to the software compiler used when developing and writing programs. The original code before compilation must also be written in a specific programming language, which is called hardware description language (HDL). There is not only one HDL, but many kinds, such as ABEL (Advanced Boolean Expression Language), AHDL (Altera Hardware Description Language), Confluence, CUPL (Cornell University Programming Language), HD Cal, JHDL (Java Hardware Description Language), Lava, Lola, My HDL, PALASM, RHDL (Ruby Hardware Description Language), etc. The most commonly used ones are VHDL (Very-High-Speed ​​Integrated Circuit Hardware Description Language) and Verilog. Those skilled in the art should also know that it is only necessary to program the method flow slightly in the above-mentioned hardware description languages ​​and program it into the integrated circuit, and then it is easy to obtain the hardware circuit that implements the logic method flow.

[0491] The controller can be implemented in any appropriate manner, for example, the controller can take the form of a microprocessor or processor and a computer-readable medium storing a computer-readable program code (such as software or firmware) that can be executed by the (micro)processor, a logic gate, a switch, an application-specific integrated circuit (ASIC), a programmable logic controller, and an embedded microcontroller. Examples of controllers include, but are not limited to, the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicone Labs C8051F320. The memory controller can also be implemented as part of the control logic of the memory. Those skilled in the art also know that in addition to implementing the controller in a purely computer-readable program code manner, the controller can be implemented in the form of a logic gate, a switch, an application-specific integrated circuit, a programmable logic controller, and an embedded microcontroller by logically programming the method steps. Therefore, this controller can be considered as a hardware component, and the devices included therein for implementing various functions can also be regarded as structures within the hardware component. Or even, the devices for implementing various functions can be regarded as both software modules for implementing the method and structures within the hardware component.

[0492] The systems, devices, modules or units described in the above embodiments may be implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer. Specifically, the computer may be, for example, a personal computer, a laptop computer, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.

[0493] For the convenience of description, the above devices are described in terms of functions and are divided into various units. Of course, when implementing one or more of the present specification, the functions of each unit can be implemented in the same or multiple software and / or hardware.

[0494] It will be appreciated by those skilled in the art that one or more embodiments of this specification may be provided as methods, systems, or computer program products. Therefore, one or more of this specification may be in the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, one or more of this specification may be in the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0495] One or more of the present specification is described with reference to flowcharts and / or block diagrams of methods, devices (systems), and computer program products according to one or more embodiments of the present specification. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0496] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0497] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 A step that specifies a function in one or more boxes.

[0498] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0499] The memory may include non-permanent storage in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM. The memory is an example of a computer-readable medium.

[0500] Computer readable media include permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. Information can be computer readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic tape disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer readable media does not include temporary computer readable media (transitory media), such as modulated data signals and carrier waves.

[0501] It should also be noted that the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, commodity or device. In the absence of more restrictions, the elements defined by the sentence "comprises a ..." do not exclude the existence of other identical elements in the process, method, commodity or device including the elements.

[0502] It should be understood by those skilled in the art that one or more embodiments of this specification may be provided as methods, systems or computer program products. Therefore, one or more of this specification may take the form of a complete hardware embodiment, a complete software embodiment or an embodiment combining software and hardware. Moreover, one or more of this specification may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0503] One or more of the present descriptions may be described in the general context of computer-executable instructions executed by a computer, such as program modules. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform specific tasks or implement specific abstract data types. One or more of the present descriptions may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are connected through a communications network. In a distributed computing environment, program modules may be located in local and remote computer storage media, including storage devices.

[0504] Each embodiment in this specification is described in a progressive manner, and the same or similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the system embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment.

[0505] The above description is only one or more embodiments of this specification and is not intended to limit this specification. For those skilled in the art, this specification may have various changes and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of this specification should be included in the scope of one or more claims of this specification.

Claims

1. An information recording method, comprising: For a minimum business processing event of a target business triggered by a user operation behavior, determining a target page element in a user access page involved in executing the minimum business processing event; as well as, Acquire description information of the user operation behavior on the user accessed page, wherein the description information is information generated based on annotation information associated with the page element targeted by the user operation behavior, and the annotation information is used to describe the operation meaning of the user operation behavior; Generating user behavior record information corresponding to the minimum business processing event according to the characteristic information of the target page element and the description information; The minimum service processing event is used as the minimum information uploading node, and the user behavior record information of each minimum service processing event in the service processing link of the target service is sent to the server.

2. The method according to claim 1, wherein: Also includes: If the minimum service processing event is a home page access event for the target service, a long link establishment request is sent to the server to establish a long link between the server and the client; Correspondingly, the sending of the user behavior record information of each of the minimum business processing events in the business processing link of the target business to the server includes: Using the long link, sending the user behavior record information of each of the minimum business processing events in the business processing link of the target business to the server; If the minimum service processing event is a service processing end event for the target service, a long link disconnection request is sent to the server to disconnect the long link between the server and the client.

3. The method according to claim 1, wherein: After sending the user behavior record information of each of the minimum service processing events in the service processing link of the target service to the server, the method further includes: Receiving information storage feedback information returned by the server in response to the user behavior record information; Based on the information storage feedback information, the behavior record information to be reissued is determined from the user behavior record information that has been sent.

4. The method according to claim 3, wherein: The step of determining the behavior record information to be reissued from the sent user behavior record information based on the information storage feedback information includes: Based on the information storage feedback information, determining a target node identifier corresponding to the stored user behavior record information; According to the target node identifier and the upload node identifier corresponding to the sent user behavior record information, the behavior record information to be reissued is determined from the sent user behavior record information.

5. The method according to claim 3, wherein: The step of determining the behavior record information to be reissued from the sent user behavior record information based on the information storage feedback information includes: Based on the information storage feedback information, updating the storage status type of the sent user behavior record information; According to the updated storage status type, the behavior record information to be reissued is determined from the sent user behavior record information.

6. The method according to claim 4, wherein: The upload node identifier includes: an operation behavior timestamp, and the information storage feedback information includes: a target operation timestamp corresponding to the currently stored user behavior record information; The updating of the storage status type of the sent user behavior record information based on the information storage feedback information includes: Update the storage status type of the user behavior record information whose operation behavior timestamp is equal to the target operation timestamp to stored; and Determine, in the sent user behavior record information, a storage state type of target behavior record information whose operation behavior timestamp is earlier than the target operation timestamp; If the storage status type is not stored, the storage status type of the target behavior record information is updated to pending reissue.

7. The method according to claim 5, wherein: The information storage feedback information includes: a target node identifier corresponding to the currently stored user behavior record information; The updating of the storage status type of the sent user behavior record information based on the information storage feedback information includes: updating the storage status type of the user behavior record information corresponding to the target node identifier to stored; and Determine whether the target node identifier and the previous uploading node identifier fed back by the server are adjacent node identifiers; If it is not an adjacent node identifier, determining the storage state type of the target behavior record information corresponding to the intermediate upload node identifier between the target node identifier and the previous upload node identifier; If the storage status type is not stored, the storage status type of the target behavior record information is updated to pending reissue.

8. The method according to claim 2, wherein: The sending a long link disconnection request to the server includes: Determine at least one piece of behavior record information that is currently remaining and to be reissued; Sending the at least one to-be-reissued behavior record information to the server by using the long link; Determining whether all of the at least one behavior record information to be reissued has been stored in the server based on information storage feedback information returned by the server for the behavior record information to be reissued; If it is determined that all the data has been stored, a long link disconnection request is sent to the server.

9. The method according to claim 3, wherein: After determining the behavior record information to be reissued from the sent user behavior record information based on the information storage feedback information, the method further includes: Obtaining the pending reissue behavior record information cached locally, and sending the pending reissue behavior record information to the server; Receiving reissue information storage feedback information returned by the server for the to-be-reissued action record information; Based on the reissue information storage feedback information, at least one remaining behavior record information to be reissued is determined.

10. The method according to claim 1, wherein: The sending of the user behavior record information of each minimum business processing event in the business processing link of the target business to the server includes: For each of the user behavior record information, generate behavior record information in binary format corresponding to the user behavior record information; Sending the behavior record information in binary form corresponding to each of the minimum business processing events in the business processing link of the target business to the server.

11. The method according to claim 1, wherein: The step of determining a target page element in a user access page involved in executing the minimum business processing event includes: Monitoring whether there is an updated target CSS style in the CSS style corresponding to the user access page involved in executing the minimum business processing event; wherein the target CSS style is updated by a business processing module of the first application corresponding to the target business based on the minimum business processing event; Monitoring whether there is an updated target DOM node in the DOM structure corresponding to the user access page involved in executing the minimum business processing event; wherein the target DOM node is updated by the business processing module of the first application corresponding to the target business based on the minimum business processing event; The target CSS style and / or the page element corresponding to the target DOM node is determined as the target page element that changes based on the user operation behavior.

12. The method according to claim 1, wherein: The obtaining of description information of the user operation behavior on the user access page includes: Receive description information of the user operation behavior sent by the business processing module of the first application corresponding to the target business; wherein the description information is information generated based on the annotation information associated with the page element targeted by the user operation behavior when the business processing module executes the minimum business processing event; the annotation information is used to describe the operational meaning of the user operation behavior.

13. An information storage method, comprising: Receive user behavior record information of each minimum business processing event in the business processing link of the target business sent by the client; wherein the minimum business processing event is a business processing event triggered based on a user operation behavior, and the user behavior record information is generated based on the target page element in the user access page involved in executing the minimum business processing event and the description information of the user operation behavior on the user access page, and the description information is information generated based on the annotation information associated with the page element targeted by the user operation behavior, and the annotation information is used to describe the operational meaning of the user operation behavior; Based on the upload node identifier corresponding to each of the minimum business processing events, the user behavior record information is stored.

14. The method according to claim 13, wherein: Before receiving the user behavior record information of each minimum business processing event in the business processing link of the target business sent by the client, it also includes: Receiving a long link establishment request sent by a client; wherein the long link establishment request is issued by the client when determining that the minimum business processing event currently being executed is a home page access event for a target business; In response to the long link establishment request, a long link is established with the client.

15. The method according to claim 14, wherein: The user behavior record information of each minimum business processing event in the business processing link of the target business sent by the receiving client includes: The user behavior record information of each minimum business processing event in the business processing link of the target business sent by the client is received by using the long link.

16. The method according to claim 15, wherein: After receiving the user behavior record information of each minimum business processing event in the business processing link of the target business sent by the client by using the long link, the method further includes: Receiving a long link disconnection request sent by a client; wherein the long link disconnection request is sent by the client when determining that the currently executed minimum business processing event is a business processing end event for a target business; In response to the long link disconnection request, disconnect the long link from the client.

17. The method according to claim 13, wherein: After storing the user behavior record information based on the upload node identifier corresponding to each of the minimum business processing events, the method further includes: Receiving a behavior record query request sent by a record information query terminal; wherein the behavior record query request carries business processing identification information; Acquire the user behavior record information corresponding to the business processing identification information; Based on the user behavior record information, a user behavior retrospective video stream is generated for showing the execution of target business processing based on the user operation behavior; The user behavior retrospective video stream is sent to the record information query terminal, so that the record information query terminal displays the user behavior retrospective video stream.

18. An information storage method, applied to a server connected to a blockchain, the method comprising: Receive user behavior record information of each minimum business processing event in the business processing link of the target business sent by the client; wherein the minimum business processing event is a business processing event triggered based on a user operation behavior, and the user behavior record information is generated based on the target page element in the user access page involved in executing the minimum business processing event and the description information of the user operation behavior on the user access page, and the description information is information generated based on the annotation information associated with the page element targeted by the user operation behavior, and the annotation information is used to describe the operational meaning of the user operation behavior; Based on the upload node identifier corresponding to each of the minimum business processing events, the user behavior record information is uploaded to the blockchain.

19. The method according to claim 18, wherein: A trusted execution environment TEE is deployed in the server, and the user behavior record information includes behavior record information converted in binary form; The uploading of the user behavior record information to the blockchain based on the upload node identifier corresponding to each of the minimum business processing events includes: In the trusted execution environment TEE, based on the upload node identifier corresponding to each of the minimum business processing events and the behavior record information converted in binary form, a user behavior backtracking video stream is generated for displaying the execution of the target business processing based on the user operation behavior; The user behavior retrospective video stream is uploaded to the blockchain.

20. The method according to claim 18, wherein: After uploading the user behavior record information to the blockchain based on the upload node identifier corresponding to each of the minimum business processing events, the method further includes: Receiving a behavior record query request sent by a record information query terminal; wherein the behavior record query request carries business processing identification information; Obtaining the user behavior record information corresponding to the business processing identification information from the blockchain; Based on the user behavior record information, a user behavior retrospective video stream is generated for showing the execution of target business processing based on the user operation behavior; The user behavior retrospective video stream is sent to the record information query terminal, so that the record information query terminal displays the user behavior retrospective video stream.

21. An information recording device, comprising: A target page element determination module, which determines, for a minimum business processing event of a target business triggered by a user operation behavior, a target page element in a user access page involved in executing the minimum business processing event; as well as, A behavior description information determination module, which obtains description information of the user operation behavior on the user accessed page, wherein the description information is information generated based on annotation information associated with the page element targeted by the user operation behavior, and the annotation information is used to describe the operation meaning of the user operation behavior; A behavior record information generating module, which generates user behavior record information corresponding to the minimum business processing event according to the characteristic information of the target page element and the description information; A behavior record information uploading module uses the minimum business processing event as the minimum information uploading node and sends the user behavior record information of each minimum business processing event in the business processing link of the target business to the server.

22. An information storage device, comprising: A behavior record information receiving module, which receives user behavior record information of each minimum business processing event in the business processing link of the target business sent by the client; wherein the minimum business processing event is a business processing event triggered based on the user operation behavior, and the user behavior record information is generated based on the target page element in the user access page involved in executing the minimum business processing event and the description information of the user operation behavior on the user access page, and the description information is information generated based on the annotation information associated with the page element targeted by the user operation behavior, and the annotation information is used to describe the operational meaning of the user operation behavior; A behavior record information storage module stores the user behavior record information based on the upload node identifier corresponding to each of the minimum business processing events.

23. An information storage device, provided on a server connected to a blockchain, comprising: A behavior record information receiving module, which receives user behavior record information of each minimum business processing event in the business processing link of the target business sent by the client; wherein the minimum business processing event is a business processing event triggered based on the user operation behavior, and the user behavior record information is generated based on the target page element in the user access page involved in executing the minimum business processing event and the description information of the user operation behavior on the user access page, and the description information is information generated based on the annotation information associated with the page element targeted by the user operation behavior, and the annotation information is used to describe the operational meaning of the user operation behavior; A behavior record information chain-uploading module uploads the user behavior record information to the blockchain based on the upload node identifier corresponding to each of the minimum business processing events.

24. An information storage system, comprising: Client and server; The client determines, for a minimum business processing event of a target business triggered by a user operation behavior, a target page element in a user access page involved in executing the minimum business processing event; And, obtaining description information of the user operation behavior on the user access page, wherein the description information is information generated based on annotation information associated with the page element targeted by the user operation behavior, and the annotation information is used to describe the operational meaning of the user operation behavior; Generating user behavior record information corresponding to the minimum business processing event according to the characteristic information of the target page element and the description information; as well as, Taking the minimum business processing event as the minimum information uploading node, sending the user behavior record information of each minimum business processing event in the business processing link of the target business to the server; The server receives the user behavior record information and stores the user behavior record information based on the upload node identifier corresponding to each of the minimum business processing events.

25. An information recording device, comprising: processor; as well as a memory arranged to store computer executable instructions which, when executed, cause the processor to: For a minimum business processing event of a target business triggered by a user operation behavior, determining a target page element in a user access page involved in executing the minimum business processing event; as well as, Acquire description information of the user operation behavior on the user accessed page, wherein the description information is information generated based on annotation information associated with the page element targeted by the user operation behavior, and the annotation information is used to describe the operation meaning of the user operation behavior; Generating user behavior record information corresponding to the minimum business processing event according to the characteristic information of the target page element and the description information; The minimum service processing event is used as the minimum information uploading node, and the user behavior record information of each minimum service processing event in the service processing link of the target service is sent to the server.

26. An information storage device, comprising: processor; as well as a memory arranged to store computer executable instructions which, when executed, cause the processor to: Receive user behavior record information of each minimum business processing event in the business processing link of the target business sent by the client; wherein the minimum business processing event is a business processing event triggered based on a user operation behavior, and the user behavior record information is generated based on the target page element in the user access page involved in executing the minimum business processing event and the description information of the user operation behavior on the user access page, and the description information is information generated based on the annotation information associated with the page element targeted by the user operation behavior, and the annotation information is used to describe the operational meaning of the user operation behavior; Based on the upload node identifier corresponding to each of the minimum business processing events, the user behavior record information is stored.

27. An information storage device comprising: processor; as well as a memory arranged to store computer executable instructions which, when executed, cause the processor to: Receive user behavior record information of each minimum business processing event in the business processing link of the target business sent by the client; wherein the minimum business processing event is a business processing event triggered based on a user operation behavior, and the user behavior record information is generated based on the target page element in the user access page involved in executing the minimum business processing event and the description information of the user operation behavior on the user access page, and the description information is information generated based on the annotation information associated with the page element targeted by the user operation behavior, and the annotation information is used to describe the operational meaning of the user operation behavior; Based on the upload node identifier corresponding to each of the minimum business processing events, the user behavior record information is uploaded to the blockchain.

28. A storage medium for storing computer executable instructions, wherein the executable instructions, when executed by a processor, implement the following method: For a minimum business processing event of a target business triggered by a user operation behavior, determining a target page element in a user access page involved in executing the minimum business processing event; as well as, Acquire description information of the user operation behavior on the user accessed page, wherein the description information is information generated based on annotation information associated with the page element targeted by the user operation behavior, and the annotation information is used to describe the operation meaning of the user operation behavior; Generating user behavior record information corresponding to the minimum business processing event according to the characteristic information of the target page element and the description information; The minimum service processing event is used as the minimum information uploading node, and the user behavior record information of each minimum service processing event in the service processing link of the target service is sent to the server.

29. A storage medium for storing computer executable instructions, wherein the executable instructions, when executed by a processor, implement the following method: Receive user behavior record information of each minimum business processing event in the business processing link of the target business sent by the client; wherein, The minimum business processing event is a business processing event triggered by a user operation behavior, the user behavior record information is generated based on the target page element in the user access page involved in executing the minimum business processing event and the description information of the user operation behavior on the user access page, the description information is information generated based on the annotation information associated with the page element targeted by the user operation behavior, and the annotation information is used to describe the operational meaning of the user operation behavior; Based on the upload node identifier corresponding to each of the minimum business processing events, the user behavior record information is stored.

30. A storage medium for storing computer executable instructions, wherein the executable instructions, when executed by a processor, implement the following method: Receive user behavior record information of each minimum business processing event in the business processing link of the target business sent by the client; wherein, The minimum business processing event is a business processing event triggered by a user operation behavior, the user behavior record information is generated based on the target page element in the user access page involved in executing the minimum business processing event and the description information of the user operation behavior on the user access page, the description information is information generated based on the annotation information associated with the page element targeted by the user operation behavior, and the annotation information is used to describe the operational meaning of the user operation behavior; Based on the upload node identifier corresponding to each of the minimum business processing events, the user behavior record information is uploaded to the blockchain.

Images