An account anti-brushing method and a terminal

Abstract

The present invention discloses an account anti-brushing method and a terminal. By obtaining the role channel information and verification cache information corresponding to the login account included in the login request, obtaining the corresponding role switching times threshold according to the account channel information, then determining the number of times of switching that has occurred for the login account according to the verification cache information, comparing the number of times of switching that has occurred with the role switching times threshold, and determining whether to allow the login of the login account according to the comparison result. Different account channels have corresponding role switching times thresholds, and it is determined whether to allow login by comparing the number of times of switching that has occurred for the login account with the role switching times threshold, so as to effectively limit the number of times that users of different channels switch accounts when logging in to the account, prevent situations such as studios frequently switching accounts to brush leaderboard information rewards or frequently testing player accounts through technical means, prevent account brushing behavior while not affecting the normal login of users to the account, and improve the stability of the server.

Description

Technical Field

[0001] The present invention relates to the field of online game technology, and in particular to an account anti-brushing method and terminal. Background Art

[0002] Online games, referred to as "online games", are a type of sustainable individual multiplayer online games that use the Internet as a transmission medium, game operator servers and user computers as processing terminals, and game client software as an information interaction window, aiming to achieve entertainment, leisure, communication and virtual achievements.

[0003] With the increasing number of online game players, malicious users have gradually obtained user accounts from other channels and tried to obtain character information from all regions and servers, and studios have used a large number of accounts to brush data. This situation has seriously affected the gaming experience of normal players and posed a threat to the development of online games. Corresponding measures are urgently needed.

[0004] At present, the industry's general approach to preventing account swiping is to limit the number of IP (Internet Protocol Address) accesses and use data encryption and verification to prevent account swiping. However, this method has low portability and is more likely to be unable to effectively prevent public IP account swiping due to the variability of IP, which will also affect other normal users. Although data encryption and verification can prevent malicious swiping, it cannot prevent the situation where a studio has many normal accounts and uses these accounts to swipe data. If no countermeasures are taken for this situation, it will lead to an impact on server performance. Summary of the Invention

[0005] The technical problem to be solved by the present invention is to provide an account anti-swiping method and terminal, which can improve the stability of the server while preventing account swiping.

[0006] In order to solve the above technical problems, a technical solution adopted by the present invention is:

[0007] A method for preventing account fraud, comprising the steps of:

[0008] Receive a login request, and obtain account channel information and verification cache information corresponding to the login account included in the login request;

[0009] Obtaining a role switching count threshold corresponding to the login account according to the account channel information;

[0010] Determine the number of times the login account has been switched according to the verification cache information;

[0011] The number of switching times is compared with the role switching number threshold, and whether to allow login of the login account is determined according to the comparison result.

[0012] To solve the above technical problems, another technical solution adopted by the present invention is as follows:

[0013] An anti-brush terminal for an account, comprising a memory, a processor, and a computer program stored on the memory and executable on the processor, wherein when the processor executes the computer program, the following steps are implemented:

[0014] Receive a login request, and obtain the account channel information and verification cache information corresponding to the login account included in the login request;

[0015] Obtain the role switching times threshold corresponding to the login account according to the account channel information;

[0016] Determine the number of times of switching that has occurred corresponding to the login account according to the verification cache information;

[0017] Compare the number of times of switching that has occurred with the role switching times threshold, and determine whether to allow the login of the login account according to the comparison result.

[0018] The beneficial effects of the present invention are as follows: By obtaining the role channel information and verification cache information corresponding to the login account included in the login request, obtaining the corresponding role switching times threshold according to the account channel information, then determining the number of times of switching that has occurred corresponding to the login account according to the verification cache information, comparing the number of times of switching that has occurred with the role switching times threshold, and determining whether to allow the login of the login account according to the comparison result, each account channel has a corresponding role switching times threshold, and it is determined whether to allow login by comparing the number of times of switching that has occurred corresponding to the login account with the role switching times threshold, so that the number of times of switching the role when users of different channels log in to the account is effectively restricted, preventing situations such as studios frequently switching accounts to brush leaderboard information rewards or frequently testing player accounts through technical means. While not affecting the normal login of users to the account, it can prevent account brushing behavior and improve the stability of the server. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] Figure 1 It is a flowchart of steps in an anti-brush method for an account according to an embodiment of the present invention;

[0020] Figure 2 It is a schematic structural diagram of an anti-brush terminal for an account according to an embodiment of the present invention;

[0021] Figure 3 It is a flowchart of an anti-brush method for an account according to an embodiment of the present invention. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0022] To describe in detail the technical content, achieved objectives, and effects of the present invention, the following is described in conjunction with the embodiments and with reference to the accompanying drawings.

[0023] Please refer to Figure 1 , an embodiment of the present invention provides an anti-brush method for accounts, including the steps of:

[0024] Receive a login request, and obtain the account channel information and verification cache information corresponding to the login account included in the login request;

[0025] Obtain the role switching times threshold corresponding to the login account according to the account channel information;

[0026] Determine the number of times of switching that has occurred for the login account according to the verification cache information;

[0027] Compare the number of times of switching that has occurred with the role switching times threshold, and determine whether to allow the login of the login account according to the comparison result.

[0028] As can be seen from the above description, the beneficial effects of the present invention are as follows: By obtaining the role channel information and verification cache information corresponding to the login account included in the login request, obtaining the corresponding role switching times threshold according to the account channel information, then determining the number of times of switching that has occurred for the login account according to the verification cache information, comparing the number of times of switching that has occurred with the role switching times threshold, and determining whether to allow the login of the login account according to the comparison result. Each account channel has a corresponding role switching times threshold. By comparing the number of times of switching that has occurred for the login account with the role switching times threshold to determine whether to allow the login, the number of times of role switching when users of different channels log in to the account is effectively restricted, preventing situations such as studios frequently switching accounts to brush leaderboard information rewards or frequently testing player accounts through technical means. While not affecting the normal login of users, it can prevent account brushing behavior and improve the stability of the server.

[0029] Further, before the step of receiving the login request and obtaining the account channel information and verification cache information corresponding to the login account included in the login request, the following steps are included:

[0030] Set the corresponding role switching times threshold according to different account channels and save it.

[0031] As can be seen from the above description, since the number of times of role switching required for different account channels is different. For example, users of PC (Personal Computer) embedded pages usually have more normal switching times, while users of channels such as Web (web page) or H5 (HTML5, mobile web page) usually have fewer normal switching times. By setting the corresponding role switching times threshold according to different account channels, it is possible to neither affect the normal login of users nor prevent the account brushing behavior of lawbreakers and studios.

[0032] Further, the login request further includes historical role login information corresponding to the login account;

[0033] Before comparing the number of switched times with the role switching times threshold, the following steps are further included:

[0034] Judge whether the current role login information corresponding to the login account is consistent with the historical role login information according to the historical role login information. If so, allow the login of the login account and update the historical role login information. If not, execute the step of comparing the number of switched times with the role switching times threshold.

[0035] It can be seen from the above description that through the historical role login information, it can be judged whether the login request is a normal login. If it is determined to be a normal login, bypass the verification and directly log in, which can improve the efficiency of account login and does not affect the login of normal users.

[0036] Further, comparing the number of switched times with the role switching times threshold and determining whether to allow the login of the login account according to the comparison result includes:

[0037] Compare the number of switched times with the role switching times threshold, and judge whether the number of switched times is less than the role switching times threshold. If so, allow the login of the login account; otherwise, do not allow the login of the login account within a preset time.

[0038] It can be seen from the above description that by judging whether the number of switched times reaches the role switching times threshold, it can be determined whether the login request is the behavior of a normal user, preventing malicious users from obtaining user accounts of others from other channels and attempting to obtain role information of all server areas.

[0039] Further, the following steps are further included:

[0040] Obtain the verification code opening threshold corresponding to the login account according to the account channel information;

[0041] If the number of switched times is less than the role switching times threshold, allowing the login of the login account includes:

[0042] Compare the number of switched times with the verification code opening threshold, and judge whether the number of switched times is less than the verification code opening threshold. If so, allow the login of the login account and update the number of switched times of the login account;

[0043] If not, output a first verification code on the display interface and receive the input second verification code;

[0044] Determine whether the second verification code is equal to the first verification code. If they are equal, allow the login of the login account and update the number of times the login account has been switched. If they are not equal, prompt an error message.

[0045] As can be seen from the above description, by determining whether the number of times of switching reaches the verification code activation threshold, it is possible to effectively prevent studios from using scripts to brush accounts and repeatedly request the server, resulting in excessive occupation of the server and a decline in server performance, thereby improving the stability of the server.

[0046] Please refer to Figure 2 , Another embodiment of the present invention provides an anti-brushing terminal for an account, including a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, the following steps are implemented:

[0047] Receive a login request, and obtain the account channel information and verification cache information corresponding to the login account included in the login request;

[0048] Obtain the role switching times threshold corresponding to the login account according to the account channel information;

[0049] Determine the number of times the login account has been switched according to the verification cache information;

[0050] Compare the number of times of switching with the role switching times threshold, and determine whether to allow the login of the login account according to the comparison result.

[0051] As can be seen from the above description, by obtaining the role channel information and verification cache information corresponding to the login account included in the login request, obtaining the corresponding role switching times threshold according to the account channel information, then determining the number of times the login account has been switched according to the verification cache information, comparing the number of times of switching with the role switching times threshold, and determining whether to allow the login of the login account according to the comparison result, different account channels have corresponding role switching times thresholds, and determining whether to allow login according to the comparison between the number of times the login account has been switched and the role switching times threshold can effectively limit the number of times users of different channels can switch roles when logging in to the account. While not affecting the normal login of users, it can prevent account brushing behavior and improve the stability of the server.

[0052] Further, before the step of receiving the login request and obtaining the account channel information and verification cache information corresponding to the login account included in the login request, the following steps are included:

[0053] Set the corresponding role switching times threshold according to different account channels and save it.

[0054] As described above, since the number of times of role switching required for different account channels is different. For example, users of the embedded page on a PC (Personal Computer) need to switch roles more frequently, while users of channels such as Web (web page) or H5 (HTML5, a web page for mobile devices) need to switch roles less frequently. By setting corresponding role switching thresholds according to different account channels, it is possible to neither affect the normal login of users nor prevent the behavior of malicious users and studios from brushing accounts.

[0055] Further, the login request further includes historical role login information corresponding to the logged-in account;

[0056] Before comparing the number of switched times with the role switching threshold, the following steps are further included:

[0057] Judge whether the current role login information corresponding to the logged-in account is consistent with the historical role login information according to the historical role login information. If so, allow the login of the logged-in account and update the historical role login information. If not, execute the step of comparing the number of switched times with the role switching threshold.

[0058] As described above, through the historical role login information, it is possible to determine whether the login request is a normal login. If it is determined to be a normal login, bypass the verification and directly log in, which can improve the efficiency of account login and does not affect the login of normal users.

[0059] Further, comparing the number of switched times with the role switching threshold and determining whether to allow the login of the logged-in account according to the comparison result includes:

[0060] Compare the number of switched times with the role switching threshold, and judge whether the number of switched times is less than the role switching threshold. If so, allow the login of the logged-in account; otherwise, do not allow the login of the logged-in account within a preset time.

[0061] As described above, by judging whether the number of switched times reaches the role switching threshold, it is possible to determine whether the login request is the behavior of a normal user, and prevent malicious users from obtaining the user accounts of others from other channels and attempting to obtain the role information of all server areas.

[0062] Further, the following steps are further included:

[0063] Obtain the verification code activation threshold corresponding to the logged-in account according to the account channel information;

[0064] If the number of switched times is less than the role switching threshold, allowing the login of the logged-in account includes:

[0065] Compare the number of times switched with the verification code activation threshold to determine whether the number of times switched is less than the verification code activation threshold. If so, allow the login of the login account and update the number of times the login account has been switched;

[0066] If not, output a first verification code on the display interface and receive the input second verification code;

[0067] Determine whether the second verification code is equal to the first verification code. If they are equal, allow the login of the login account and update the number of times the login account has been switched. If they are not equal, prompt an error message.

[0068] As can be seen from the above description, by judging whether the number of times switched reaches the verification code activation threshold, it is possible to effectively prevent studios from using scripts to brush accounts and repeatedly request the server, resulting in the server being overoccupied and the server performance degrading, thereby improving the stability of the server.

[0069] Embodiment 1

[0070] Please refer to Figure 1 、 3 For a method and a terminal for preventing account brushing in this embodiment, the steps include:

[0071] S0. Set corresponding role switching times thresholds according to different account channels and save them;

[0072] For example, set corresponding role switching times thresholds according to different account channels and save them to the server configuration file. For example, "gate.userHandler.get_user": {"max_pre_day": 10, "platform": {"110": {"max_pre_day": 19}}}, where gate.userHandler.get_user is the interface service route for the login request, max_pre_day is the role switching times threshold within a day, platform is the special channel corresponding to the interface service route, and 110 represents the in-game embedded channel;

[0073] PC (Personal Computer) embedded page users have a relatively large number of normal switches, and the verification code activation threshold can be set higher. For users of channels such as Web or H5 (HTML5, mobile Web page), the number of normal switches is relatively small, and the verification code activation threshold and the role switching times threshold can be set lower;

[0074] S1. Receive a login request and obtain the account channel information and verification cache information corresponding to the login account included in the login request;

[0075] For example, as Figure 3 shown, receive a login request. According to the key (keyword) in the login request, such as the encrypted account ID: route: the current date 2020-11-25, obtain the account channel information and verification cache information corresponding to the account. The obtained information includes, for example, userCode (encrypted account ID), date, route, code (verification code), num (number of times);

[0076] Among them, the verification cache information is only cached for one day and expires after one day. After expiration, the verification cache information for the current day is re-cached. Route represents the account channel information corresponding to the account, and num represents the verification cache information corresponding to the account; when obtaining for the first time on the current day, num may be 0 and code may be an empty string;

[0077] S2. Obtain the role switching times threshold corresponding to the logged-in account according to the account channel information;

[0078] For example, obtain the max_pre_day corresponding to the logged-in account from the server configuration file according to route;

[0079] S3. Determine the number of times the logged-in account has been switched according to the verification cache information;

[0080] For example, determine the num corresponding to the logged-in account according to the verification cache information;

[0081] Among them, the login request also includes the historical role login information corresponding to the logged-in account;

[0082] For example, the login request also includes the historical role login information corresponding to the logged-in account, such as game ID + server area ID + server ID + role ID + encrypted account ID;

[0083] S31. Judge whether the current role login information corresponding to the logged-in account is consistent with the historical role login information. If so, allow the logged-in account to log in and update the historical role login information. If not, execute the step of comparing the number of times switched with the role switching times threshold;

[0084] For example, as Figure 3 shown, judge whether it is consistent with the current role login information according to game ID + server area ID + server ID + role ID + encrypted account ID. If so, allow the login and update the historical role login information of the account. If not, execute step S4;

[0085] S4. Compare the number of times switched with the role switching times threshold, and determine whether to allow the logged-in account to log in according to the comparison result;

[0086] Specifically, compare the number of switched times with the role switching times threshold to determine whether the number of switched times is less than the role switching times threshold. If so, allow the login of the login account; otherwise, do not allow the login of the login account within a preset time and prompt that the upper limit of the role switching times has been reached.

[0087] For example, as Figure 3 shown, compare num with max_pre_day to determine whether num is less than max_pre_day. If so, allow the login; otherwise, do not allow the login of this account within a day and prompt that the upper limit of the role switching times has been reached.

[0088] Embodiment 2

[0089] Please refer to Figure 3 , this embodiment further limits how to prevent studios from swiping accounts through scripts on the basis of Embodiment 1:

[0090] Specifically, set and save the corresponding verification code activation threshold according to different account channels;

[0091] For example, set the corresponding verification code activation threshold according to different account channels and save it to the server configuration file. For example, "gate.userHandler.get_user": {"bagin_pre_day": 1, "platform": {"110": {"bagin_pre_day": 20}}}, where bagin_pre_day is the verification code activation threshold within a day;

[0092] Among them, the verification code activation threshold can be set together with the role switching times threshold in step S0 of Embodiment 1. For example, "gate.userHandler.get_user": {"max_pre_day": 10, "bagin_pre_day": 1, "platform": {"110": {"max_pre_day": 19, "bagin_pre_day": 20}}};

[0093] Obtain the corresponding verification code activation threshold of the login account according to the account channel information;

[0094] For example, obtain the corresponding bagin_pre_day of this login account from the server configuration file according to route;

[0095] Specifically, if the number of switched times is less than the role switching times threshold, allowing the login of the login account includes:

[0096] Compare the number of switches with the verification code activation threshold to determine whether the number of switches is less than the verification code activation threshold. If so, allow the login of the login account, update the number of switches of the login account, and update the historical role login information;

[0097] If not, output a first verification code on the display interface and receive the input second verification code;

[0098] Determine whether the second verification code is equal to the first verification code. If equal, allow the login of the login account, update the number of switches of the login account, and update the historical role login information. If not equal, prompt an error message;

[0099] For example, as Figure 3 shown, compare num with bagin_pre_day to determine whether num is less than bagin_pre_day. If so, allow login, update num with num + 1, and update the historical role login information; if not, output a verification code on the display interface, receive the verification code input by the user, determine whether the verification code input by the user is equal to the output verification code. If equal, allow login, update num with num + 1, and update the historical role login information. If not equal, prompt a verification code error message;

[0100] Among them, the verification code can be set in any form, such as a graphic verification code, a digital verification code, etc.

[0101] Embodiment III

[0102] Please refer to Figure 2 , an anti-brush terminal for an account, including a memory, a processor, and a computer program stored on the memory and executable on the processor. When the processor executes the computer program, the steps in Embodiment I or Embodiment II are implemented.

[0103] In summary, for the account anti-brushing method and terminal provided by the present invention, since the number of times of role switching required for different account channels is different, the corresponding role switching times threshold is set and saved according to different account channels, which does not affect the normal login of users. When receiving the login request of a user, the role switching times threshold corresponding to the login account is obtained according to the account channel information corresponding to the login account included in the obtained login request, and then the number of times of switching corresponding to the login account is determined according to the verification cache information. It is judged whether the historical role login information included in the login request is consistent with the current role login information, so as to determine whether the login request is a normal login. If it is determined to be a normal login, the verification is bypassed and the user directly logs in, which can improve the efficiency of account login. Then, the number of times of switching is compared with the role switching times threshold, and whether to allow the account to log in is determined according to the comparison result, preventing malicious users from obtaining other people's user accounts from other channels and attempting to obtain role information of all server regions. The number of times of switching is compared with the verification code opening threshold, and whether to open the verification code is determined according to the comparison result, which can effectively prevent studios from brushing accounts through scripts and repeatedly requesting the server, resulting in excessive occupation of the server and a decline in server performance, and improving the stability of the server.

[0104] The above are only the embodiments of the present invention, and do not limit the patent scope of the present invention accordingly. All equivalent transformations made by using the content of the specification and drawings of the present invention, or directly or indirectly applied in related technical fields, are similarly included in the patent protection scope of the present invention.

Claims

1. An account anti-brushing method, characterized in that, Including the steps: Set the corresponding role switching times threshold according to different account channels and save it; Receive a login request, and obtain the account channel information and verification cache information corresponding to the login account included in the login request; Obtain the role switching times threshold corresponding to the login account according to the account channel information; Determine the number of times switched corresponding to the login account according to the verification cache information; Compare the number of times switched with the role switching times threshold, and determine whether to allow the login of the login account according to the comparison result, including: Compare the number of times switched with the role switching times threshold, and judge whether the number of times switched is less than the role switching times threshold. If so, allow the login of the login account; otherwise, do not allow the login of the login account within a preset time; Obtain the verification code opening threshold corresponding to the login account according to the account channel information; If the number of times switched is less than the role switching times threshold, allowing the login of the login account includes: Compare the number of times switched with the verification code opening threshold, and judge whether the number of times switched is less than the verification code opening threshold. If so, allow the login of the login account and update the number of times switched of the login account; If not, output the first verification code on the display interface and receive the input second verification code; Judge whether the second verification code is equal to the first verification code. If equal, allow the login of the login account and update the number of times switched of the login account. If not equal, prompt an error message.

2. The account anti-brush method according to claim 1, characterized in that, The login request further includes the historical role login information corresponding to the login account; Before comparing the number of times switched with the role switching times threshold, the following steps are further included: Judge whether the current role login information corresponding to the login account is consistent with the historical role login information according to the historical role login information. If so, allow the login of the login account and update the historical role login information. If not, execute the step of comparing the number of times switched with the role switching times threshold.

3. An anti-brush terminal for an account, comprising a memory, a processor, and a computer program stored on the memory and operable on the processor, characterized in that, When the processor executes the computer program, the following steps are implemented: Set the corresponding role switching times threshold according to different account channels and save it; Receive a login request, and obtain the account channel information and verification cache information corresponding to the login account included in the login request; Obtain the role switching times threshold corresponding to the login account according to the account channel information; Determine the number of times switched corresponding to the login account according to the verification cache information; Compare the number of times switched with the role switching times threshold, and determine whether to allow the login of the login account according to the comparison result, including: Compare the number of times switched with the role switching times threshold, and judge whether the number of times switched is less than the role switching times threshold. If so, allow the login of the login account; otherwise, do not allow the login of the login account within a preset time; Obtain the verification code opening threshold corresponding to the login account according to the account channel information; If the number of switched times is less than the role switching times threshold, allowing the login of the login account includes: Comparing the number of switched times with the verification code activation threshold, determining whether the number of switched times is less than the verification code activation threshold. If so, allowing the login of the login account and updating the number of switched times of the login account; If not, outputting a first verification code on the display interface and receiving a second verification code entered; Determining whether the second verification code is equal to the first verification code. If they are equal, allowing the login of the login account and updating the number of switched times of the login account. If not, prompting an error message.

4. The anti-brush terminal for an account according to claim 3, wherein The login request further includes the historical role login information corresponding to the login account; Before comparing the number of switched times with the role switching times threshold, the following steps are further included: Judging whether the current role login information corresponding to the login account is consistent with the historical role login information according to the historical role login information. If so, allowing the login of the login account and updating the historical role login information. If not, performing the step of comparing the number of switched times with the role switching times threshold.

Images