Page behavior monitoring method, device, electronic device and storage medium

Abstract

The present application provides a page behavior monitoring method, device, electronic device and storage medium. The user's click instruction acts on the target page. The front-end device responds to the click instruction, generates request data and sends the request data to the back-end device. The request data includes an authentication token. The authentication token in the front-end device is updated according to preset rules. The back-end device receives the request data. If the authentication token is consistent with the target authentication token in the back-end device, the back-end device determines that the target page in the front-end device is in a normal page behavior state. To a certain extent, it solves the problem of malicious refreshing of system activity in various application systems, improves the system page behavior monitoring system, ensures the effectiveness of the target page click instruction, enables the system to operate normally, and protects the vitality of the software.

Description

Technical Field

[0001] The present application relates to the field of communication technology, and in particular to a method, device, electronic device and storage medium for monitoring page behavior. Background Art

[0002] As an essential factor in determining software vitality and lifecycle, application system activity has always been a frontline focus of market attention. Application systems use various incentives to stimulate user groups to increase system activity.

[0003] At present, the page behavior monitoring method is: after detecting that the user has not operated the system page for a certain period of time, the timer will be automatically stopped, and the score calculation will be automatically stopped to prevent the user from hanging up.

[0004] However, when periodic click operations are performed on the page through software editing scripts, the page behavior monitoring method will become ineffective, allowing users to use scripts to maliciously increase system activity in order to obtain rewards. Summary of the Invention

[0005] The present application provides a page behavior monitoring method, device, electronic device and storage medium to solve the problem of users using scripts to maliciously increase system activity in order to obtain rewards.

[0006] In a first aspect, the present application provides a page behavior monitoring method, applied to a front-end device, the method comprising:

[0007] In response to a click instruction on a target page, request data is generated, the request data including an authentication token, and the authentication token in the front-end device is updated according to a preset rule;

[0008] Send request data.

[0009] Optionally, the method further comprises:

[0010] Obtain user behavior monitoring data for the target page. The user behavior monitoring data is used to record a first user behavior and a second user behavior. The first user behavior is a user behavior on the target page, and the second user behavior is a user behavior on a page with the same attributes as the target page.

[0011] Send user behavior monitoring data.

[0012] Optionally, the method further comprises:

[0013] Receive the authentication token and replace the authentication token previously in the front-end device with the currently received authentication token.

[0014] In a second aspect, the present application provides a page behavior monitoring method, which is applied to a backend device, and the method includes:

[0015] Receive request data, including an authentication token;

[0016] If the authentication token is consistent with the target authentication token in the back-end device, it is determined that the target page in the front-end device is in a normal page behavior state.

[0017] Optionally, the method further comprises:

[0018] Receive user behavior monitoring data, where the user behavior monitoring data is used to record a first user behavior and a second user behavior, where the first user behavior is a user behavior acting on a target page, and the second user behavior is a user behavior acting on a page having the same attributes as the target page;

[0019] Determine the page behavior status of the target page based on user behavior monitoring data and a preset violation behavior set.

[0020] Optionally, the method further comprises:

[0021] Generate an authentication token according to a preset random algorithm and store it in the session state, wherein the most recently stored authentication token in the session state is the target authentication token;

[0022] Send the authentication token.

[0023] Optionally, generating an authentication token according to a preset random algorithm includes:

[0024] An authentication token is generated at a target time node according to a preset random algorithm, wherein the target time node is a random time node.

[0025] In a third aspect, the present application provides a page behavior monitoring device, which is applied to a front-end device and includes:

[0026] A generating module, configured to generate request data in response to a click instruction acting on a target page, wherein the request data includes an authentication token, and the authentication token in the front-end device is updated according to a preset rule;

[0027] The sending module is used to send request data.

[0028] In a fourth aspect, the present application provides a page behavior monitoring device, which is applied to a backend device, and the device includes:

[0029] A receiving module, configured to receive request data, wherein the request data includes an authentication token;

[0030] The determination module is used to determine that the target page in the front-end device is in a normal page behavior state if the authentication token is consistent with the target authentication token in the back-end device.

[0031] In a fifth aspect, the present application provides an electronic device, comprising: a memory, a processor;

[0032] Memory for storing processor-executable instructions;

[0033] The processor is used to implement the page behavior monitoring method involved in the first aspect and optional solutions or the page behavior monitoring method involved in the second aspect and optional solutions according to the executable instructions stored in the memory.

[0034] In a sixth aspect, the present application provides a computer-readable storage medium, which stores computer-executable instructions. When the computer-executable instructions are executed by a processor, they are used to implement the page behavior monitoring method involved in the first aspect and optional scheme or the second aspect and optional scheme.

[0035] In a seventh aspect, the present application provides a computer program product comprising instructions, which, when executed by a processor, implement the page behavior monitoring method involved in the first aspect and optional solutions or the second aspect and optional solutions.

[0036] The present application provides a page behavior monitoring method, device, electronic device and storage medium. The user's click instruction acts on the target page. The front-end device responds to the click instruction, generates request data and sends the request data to the back-end device. The request data includes an authentication token. The authentication token in the front-end device is updated according to preset rules. The back-end device receives the request data. If the authentication token is consistent with the target authentication token in the back-end device, the back-end device determines that the target page in the front-end device is in a normal page behavior state. To a certain extent, it solves the problem of malicious refreshing of system activity in various application systems, improves the system page behavior monitoring system, ensures the effectiveness of the target page click instruction, enables the system to operate normally, and protects the vitality of the software. BRIEF DESCRIPTION OF THE DRAWINGS

[0037] In order to more clearly illustrate the technical solutions in the present application or the prior art, a brief introduction will be given below to the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.

[0038] Figure 1 This is a structural diagram of a page behavior monitoring system according to an exemplary embodiment of the present application;

[0039] Figure 2 This is a flow chart of a page behavior monitoring method according to an exemplary embodiment of the present application;

[0040] Figure 3This is a flow chart of a page behavior monitoring method according to another exemplary embodiment of the present application;

[0041] Figure 4 This is a schematic structural diagram of a device for monitoring page behavior according to an exemplary embodiment of the present application;

[0042] Figure 5 This is a schematic structural diagram of a device for monitoring page behavior according to an exemplary embodiment of the present application;

[0043] Figure 6 This is a schematic diagram of the hardware structure of an electronic device according to an exemplary embodiment of the present application. DETAILED DESCRIPTION

[0044] To make the objectives, technical solutions, and advantages of this application more clear, the technical solutions in this application will be clearly and completely described below in conjunction with the accompanying drawings. Obviously, the embodiments described are only part of the embodiments of this application, not all of them. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.

[0045] The following specific embodiments are used to describe the technical solution of the present application in detail. The following specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described in detail in some embodiments.

[0046] With the advancement of informatization, the number of application systems created to meet user needs is increasing rapidly. Whether it's government services, facilitating daily life, education and science popularization, or social entertainment, all rely on the continuous enrichment of software. Application system activity, as a crucial factor in determining software vitality and lifecycle, has always been a frontline focus of market attention. To this end, various incentives for application systems have emerged, stimulating a large user base and increasing system activity. However, due to inadequate reward mechanisms or inadequate monitoring and prevention measures, vulnerabilities can be exploited to maliciously manipulate activity levels in exchange for rewards.

[0047] At present, the page behavior monitoring method is: after detecting that the user has not operated the system page for a certain period of time, the timer will be automatically stopped, and the score calculation will be automatically stopped to prevent the user from hanging up.

[0048] However, when periodic click operations are performed on the page through software editing scripts, the page behavior monitoring method will become ineffective, allowing users to use scripts to maliciously increase system activity in order to obtain rewards.

[0049] In response to the above problems, this application proposes a page behavior monitoring method, in which the back-end device randomly generates and stores an authentication token, and then sends the authentication token to the front-end device. When the user's click instruction acts on the front-end device, the front-end device responds to the click instruction, generates request data and sends it to the back-end device. The request data contains the authentication token. After the back-end device receives the request data, it compares the authentication token in the request data with the authentication token stored in the back-end device to see if they are the same, in order to monitor whether the page behavior is normal. To a certain extent, it solves the problem of malicious refreshing of system activity in various current application systems, and optimizes the system points acquisition mechanism, so that the system can operate normally and the vitality of the software is guaranteed.

[0050] Figure 1 This is a structural diagram of a page behavior monitoring system according to an exemplary embodiment of the present application. Figure 1 As shown, the page behavior monitoring system provided in this embodiment includes: a front-end device 110 and a back-end device 120. The front-end device 110 and the back-end device 120 communicate with each other. The front-end device 110 is used to send request data and user behavior monitoring data to the back-end device 120, and is also used to receive the authentication token sent by the back-end device 120. The back-end device 120 is used to receive the request data and user behavior monitoring data sent by the back-end device 120, and is also used to send the authentication token to the front-end device 110.

[0051] Figure 2 This is a flow chart of a page behavior monitoring method according to an exemplary embodiment of the present application. Figure 2 As shown, the page behavior monitoring method provided in this embodiment is based on Figure 1 The page behavior monitoring system shown in the figure includes the following steps:

[0052] S101. The front-end device generates request data in response to a click instruction on a target page. The request data includes an authentication token. The authentication token in the front-end device is updated according to a preset rule.

[0053] More specifically, the target page can be the video page of the user during the video learning process. The click instruction can be the user manually clicking on the target page, or the user clicking on the target page through a program. Among them, the user manually clicking on the target page is a normal page behavior; the user clicking on the target page through a program is an abnormal page behavior, which is an act of maliciously refreshing the system activity. When a click instruction occurs on the target page, the front-end device responds to the click instruction and generates request data, and the request data contains an authentication token. Among them, the authentication token in the request data is generated by the back-end device and sent to the front-end device. The authentication token can be a random sequence character string generated according to preset rules. The back-end device updates the authentication token according to the preset rules and sends the updated authentication token to the front-end device. The front-end device replaces the previous authentication token according to the latest authentication token sent by the back-end device.

[0054] For example, when a user accesses the login page of a video learning system, a click instruction acts on the login page, and the front-end device generates login request data according to the click instruction. The login request data includes the latest authentication token sent by the back-end device to the front-end device.

[0055] S102: The front-end device sends request data.

[0056] More specifically, the front-end device sends request data to the back-end device. On the system login page, the request data includes information such as the system login request, authentication token, username, and password; during the video learning process, the request data includes information such as the continuation learning request, authentication token, username, and password.

[0057] S103: The backend device receives the request data, which includes the authentication token.

[0058] More specifically, the back-end device receives the request data sent by the front-end device and performs accuracy verification on the request data.

[0059] S104: If the authentication token is consistent with the target authentication token in the backend device, the backend device determines that the target page in the frontend device is in a normal page behavior state.

[0060] More specifically, the backend device stores the latest authentication token generated according to preset rules locally, which is the target authentication token. Upon receiving request data from the frontend device, the authentication token in the request data is compared with the locally stored target authentication token. If the authentication token in the request data matches the target authentication token, the frontend device determines that the click instruction on the target page is a normal page behavior. If the authentication token in the request data does not match the target authentication token, the frontend device determines that the click instruction on the target page is a malicious attempt to manipulate system activity.

[0061] For example, when a user accesses the login page, the login request data received by the back-end device includes information such as a login system request, an authentication token, a user name, and a password. If the back-end device determines that the authentication token in the login request data is consistent with the locally stored target authentication token, and the user name and password are correct, then the target page login behavior in the front-end device is determined to be a normal page behavior, and the system login is successful. If the back-end device determines that the authentication token in the login request data is inconsistent with the locally stored target authentication token, then the target page in the front-end device is determined to be in an abnormal page behavior state, the system login request data cannot be submitted successfully, and there is a situation where a program is used to operate the login page. This click instruction is a malicious act of swiping the system activity.

[0062] In the method provided in this embodiment, the user's click instruction acts on the target page, and the front-end device generates request data in response to the click instruction and sends the request data to the back-end device, and the request data includes an authentication token. The back-end device receives the request data, and if the authentication token is consistent with the target authentication token in the back-end device, the back-end device determines that the target page in the front-end device is in a normal page behavior state. If the authentication token in the request data is inconsistent with the target authentication token, it is determined that the click instruction of the target page in the front-end device is an act of maliciously refreshing the system activity. To a certain extent, it solves the problem of malicious refreshing of system activity in various application systems, improves the system page behavior monitoring system, ensures the effectiveness of the click instruction of the target page, enables the system to operate normally, and protects the vitality of the software.

[0063] Figure 3 FIG. 1 is a flow chart of a method for monitoring page behavior according to another exemplary embodiment of the present application. Figure 3 As shown, the page behavior monitoring method provided in this embodiment also includes the following steps:

[0064] S201. The front-end device obtains user behavior monitoring data under the target page. The user behavior monitoring data is used to record a first user behavior and a second user behavior. The first user behavior is a user behavior acting on the target page, and the second user behavior is a user behavior acting on a page with the same attributes as the target page.

[0065] More specifically, user behavior monitoring data can be behavioral data such as the time the user stays on each page, whether there is any activity, etc. The front-end device uses a listener to monitor the user behavior monitoring data. The first user behavior and the second user behavior are abnormal user behavior data. The first user behavior includes behaviors such as the target page has no operation for a long time, the target page is opened multiple times in a short period of time, the number of user likes is too frequent, and the user's comments on the video content under the target page are consistent. The second user behavior includes behaviors such as the user opens the target page with multiple browsers, opens multiple target pages under the same browser, etc. The front-end device detects that there is abnormal user behavior data on the target page, prompts and warns the user account, and sends the abnormal user behavior data to the back-end device.

[0066] S202: The front-end device sends user behavior monitoring data.

[0067] S203. The backend device receives user behavior monitoring data, which is used to record a first user behavior and a second user behavior. The first user behavior is a user behavior on a target page, and the second user behavior is a user behavior on a page with the same attributes as the target page.

[0068] S204: The backend device determines the page behavior status of the target page based on the user behavior monitoring data and the preset violation behavior set.

[0069] More specifically, the contents of the preset violation behavior set may be: (1) the user does not operate the target page for a long time during the video learning process; (2) the target page is opened multiple times in a short period of time, and the target page stay time is less than 5 minutes; (3) the user likes the video too frequently, for example, multiple likes in a minute; (4) the user's comments on the learning video are consistent; (5) the user opens the learning page with multiple browsers or opens multiple target pages with the same browser during the video learning process.

[0070] Back-end equipment uses a classification algorithm to compare received user behavior monitoring data with similar cases and analyze the behavior. Classification is then performed. Based on the classification results, the target page's behavior status is determined to be within a pre-defined set of violations. The violations are then recorded in the audit log. The audit log records and archives the results of daily scans, making it easier for system administrators to trace and review them. System administrators can review and verify user violations. Repeated violations will be flagged as a priority, and system administrators can then, through the system management backend, take disciplinary action, such as reducing reward coefficients, freezing user accounts, and blocking IP logins.

[0071] In the method provided in this embodiment, the front-end device monitors user behavior data, notifies users of any anomalies, and sends them to the back-end device, which then categorizes and labels them. This allows real-time monitoring of the entire system's operational status, including malicious score manipulation, likes, and comments. Users who violate these rules are flagged for easier monitoring and to assist administrators in decision-making. This further improves the system's page behavior monitoring system, ensuring the system's normal operation and safeguarding the software's vitality.

[0072] Another embodiment of the present application provides a page behavior monitoring method, which includes the following steps:

[0073] S301. The backend device generates an authentication token according to a preset random algorithm and stores it in the session state, wherein the most recently stored authentication token in the session state is the target authentication token.

[0074] More specifically, the preset random algorithm includes a pseudo-random number algorithm. The back-end device uses the pseudo-random number algorithm to generate a Cross Site Request Forgery (CSRF) random string, and uses the latest CSRF random string as an authentication token, stored in the session state, and at the same time, sends the latest CSRF random string to the front-end device.

[0075] Optionally, the backend device generates an authentication token according to a preset random algorithm at a target time node, wherein the target time node is a random time node.

[0076] More specifically, the backend device generates an authentication token based on a preset random algorithm at random time points, and updates the authentication tokens in both the backend and frontend devices. If the backend device generates and updates the authentication token at fixed intervals, it could be easily cracked by a technician through program manipulation. Therefore, this embodiment utilizes random time points, and the authentication token update time is random. Furthermore, the authentication token is randomly generated using a preset random algorithm. This further reduces the possibility of users maliciously swiping system activity through plugins or scripts.

[0077] S302: The backend device sends an authentication token.

[0078] S303: The front-end device receives the authentication token and replaces the authentication token previously in the front-end device with the currently received authentication token.

[0079] More specifically, the front-end device receives the latest CSRF random string sent by the back-end device and replaces the previous CSRF random string with the latest CSRF random string. When the front-end device needs to initiate a request, it adds the latest CSRF random string to the request data or header information and sends it to the back-end device.

[0080] In the method provided in this embodiment, the backend device generates an authentication token at a random time using a preset random algorithm. The newly generated authentication token is then used to update the previously stored authentication tokens in both the frontend and backend devices. This randomization of the time and algorithm further reduces the possibility of users maliciously inflating system activity through plugins or scripts, improving the system's point-earning mechanism.

[0081] Figure 4 FIG. 1 is a structural diagram of a page behavior monitoring device according to an exemplary embodiment of the present application. Figure 4 As shown, the present application provides a page behavior monitoring device 400, which is applied to a front-end device. The device 400 includes:

[0082] The generating module 401 is used to generate request data in response to a click instruction on a target page. The request data includes an authentication token. The authentication token in the front-end device is updated according to a preset rule.

[0083] The sending module 402 is configured to send request data.

[0084] Specifically, this embodiment can refer to the above method embodiment, and its principles and technical effects are similar, so they will not be repeated here.

[0085] Figure 5 FIG. 1 is a structural diagram of a page behavior monitoring device according to an exemplary embodiment of the present application. Figure 5 As shown, the present application provides a page behavior monitoring device 500, which is applied to a backend device. The device 500 includes:

[0086] Receiving module 501, used to receive request data, the request data including the authentication token;

[0087] The determination module 502 is configured to determine that the target page in the front-end device is in a normal page behavior state if the authentication token is consistent with the target authentication token in the back-end device.

[0088] Specifically, this embodiment can refer to the above method embodiment, and its principles and technical effects are similar, so they will not be repeated here.

[0089] Figure 6 FIG. 1 is a schematic diagram of the hardware structure of an electronic device according to an exemplary embodiment of the present application. Figure 6 As shown, the electronic device 60 of this embodiment includes: a processor 61 and a memory 62; wherein,

[0090] Memory 62, a memory for storing processor-executable instructions;

[0091] The processor 61 is configured to implement the page behavior monitoring method in the above embodiment according to the executable instructions stored in the memory. For details, please refer to the relevant description in the above method embodiment.

[0092] Optionally, the memory 62 may be independent or integrated with the processor 61 .

[0093] When the memory 62 is independently provided, the electronic device 60 further includes a bus 63 for connecting the memory 62 and the processor 61 .

[0094] The present application also provides a computer-readable storage medium, in which computer instructions are stored. When the computer instructions are executed by a processor, they are used to implement the methods provided in the various embodiments described above.

[0095] Among them, the computer-readable storage medium can be a computer storage medium or a communication medium. The communication medium includes any medium that facilitates the transmission of a computer program from one place to another. The computer storage medium can be any available medium that can be accessed by a general-purpose or special-purpose computer. For example, a computer-readable storage medium is coupled to a processor so that the processor can read information from the computer-readable storage medium and write information to the computer-readable storage medium. Of course, the computer-readable storage medium can also be an integral part of the processor. The processor and the computer-readable storage medium can be located in an application-specific integrated circuit (ASIC). In addition, the ASIC can be located in a user device. Of course, the processor and the computer-readable storage medium can also exist in a communication device as discrete components.

[0096] The computer-readable storage medium may be implemented by any type of volatile or non-volatile memory device, or a combination thereof, such as static random-access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk. The storage medium may be any available medium that can be accessed by a general-purpose or special-purpose computer.

[0097] The present application also provides a computer program product, the program product including execution instructions stored in a computer-readable storage medium. At least one processor of a device can read the execution instructions from the computer-readable storage medium, and at least one processor executes the execution instructions so that the device implements the methods provided in the various embodiments described above.

[0098] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some or all of the technical features therein. These modifications or replacements do not deviate the essence of the corresponding technical solutions from the scope of the technical solutions of the embodiments of the present application.

Claims

1. A page behavior monitoring method, characterized in that: Applied to a front-end device, the method includes: In response to a click instruction on a target page, request data is generated, wherein the request data includes an authentication token, and the front-end device receives the authentication token updated by the back-end device according to a preset rule, wherein the authentication token is a random sequence character string generated according to the preset rule; Sending the request data; The method further comprises: Obtaining user behavior monitoring data for the target page, the user behavior monitoring data being used to record a first user behavior and a second user behavior, wherein the first user behavior is a user behavior acting on the target page, and the second user behavior is a user behavior acting on a page with the same attributes as the target page; the user behavior on the target page includes: opening the target page, liking the target page, and commenting on a video; Sending the user behavior monitoring data, wherein the user behavior monitoring data is used to instruct the backend device to determine the page behavior status of the target page according to a preset violation behavior set; the page behavior status is used to determine whether there is malicious refreshing of system activity; The method further comprises: Receive the authentication token and use the currently received authentication token to replace the authentication token previously in the front-end device; the replaced authentication token is used to send to the back-end device to determine the page behavior status corresponding to the target page in the front-end device.

2. A page behavior monitoring method, characterized in that: Applied to a backend device, the method includes: Receive request data, wherein the request data includes an authentication token, and the authentication token is a random sequence character string generated according to a preset rule; If the authentication token is consistent with the target authentication token in the back-end device, determining that the target page in the front-end device is in a normal page behavior state; The method further comprises: Receive user behavior monitoring data, the user behavior monitoring data being used to record a first user behavior and a second user behavior, wherein the first user behavior is a user behavior acting on the target page, and the second user behavior is a user behavior acting on a page having the same attributes as the target page; the user behavior on the target page includes: opening the target page, liking the target page, and commenting on a video; Determining the page behavior status of the target page based on the user behavior monitoring data and a preset violation behavior set; The method further comprises: Generate an authentication token according to a preset random algorithm and store it in the session state, wherein the most recently stored authentication token in the session state is the target authentication token; The authentication token is sent.

3. The page behavior monitoring method according to claim 2, characterized in that: Generating an authentication token according to a preset random algorithm includes: The authentication token is generated according to the preset random algorithm at a target time node, wherein the target time node is a random time node.

4. A page behavior monitoring device, characterized in that: Applied to front-end equipment, the device includes: a generation module, configured to generate request data in response to a click instruction acting on a target page, wherein the request data includes an authentication token, the front-end device receiving the authentication token updated by the back-end device according to a preset rule, the authentication token being a random sequence character string generated according to the preset rule; A sending module, configured to send the request data; an acquisition module, configured to acquire user behavior monitoring data for the target page, the user behavior monitoring data being used to record a first user behavior and a second user behavior, wherein the first user behavior is user behavior acting on the target page, and the second user behavior is user behavior acting on a page with the same attributes as the target page; user behaviors on the target page include: opening the target page, liking the target page, and commenting on a video; The sending module is used to send the user behavior monitoring data, and the user behavior monitoring data is used to instruct the back-end device to determine the page behavior status of the target page according to a preset violation behavior set; the page behavior status is used to determine whether there is any malicious behavior of refreshing the system activity; The receiving module is used to receive the authentication token and replace the authentication token previously in the front-end device with the currently received authentication token; the replaced authentication token is used to send to the back-end device to determine the page behavior status corresponding to the target page in the front-end device.

5. A page behavior monitoring device, characterized in that: Applied to back-end equipment, the device includes: A receiving module, configured to receive request data, wherein the request data includes an authentication token, and the authentication token is a random sequence character string generated according to a preset rule; a determination module, configured to determine that the target page in the front-end device is in a normal page behavior state if the authentication token is consistent with the target authentication token in the back-end device; The receiving module is configured to receive user behavior monitoring data, wherein the user behavior monitoring data is configured to record a first user behavior and a second user behavior, wherein the first user behavior is a user behavior acting on the target page, and the second user behavior is a user behavior acting on a page having the same attributes as the target page; the user behavior on the target page includes: a click behavior, a like behavior, and a video comment behavior on the target page; The determination module is configured to determine the page behavior status of the target page based on the user behavior monitoring data and a preset violation behavior set; A generation module, configured to generate an authentication token according to a preset random algorithm and store the authentication token in a session state, wherein the most recently stored authentication token in the session state is the target authentication token; The authentication token is sent.

6. An electronic device, characterized in that: include: Memory, processor; A memory for storing instructions executable by the processor; A processor is configured to implement the page behavior monitoring method according to any one of claims 1 to 3 according to the executable instructions stored in the memory.

7. A computer-readable storage medium, characterized in that The computer-readable storage medium stores computer-executable instructions, which, when executed by a processor, are used to implement the page behavior monitoring method according to any one of claims 1 to 3.

8. A computer program product comprising instructions, characterized in that When the instruction is executed by the processor, the page behavior monitoring method according to any one of claims 1 to 3 is implemented.

Images