Risk control method and device for target service, equipment and medium
By analyzing the correlation information of target business requests, risk control calculations and response controls are performed based on pre-configured risk control information to identify and block malicious behaviors, thus solving the problem of users cracking application operation rules and achieving effective risk control and fairness maintenance.
Patent Information
- Application Number
- CN202410901827.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-07-05
- Publication Date
- 2024-11-26
- Estimated Expiration
- Not applicable · inactive patent
Smart Images

Figure CN119030733A_ABST
Abstract
Description
Technical Field
[0001] The present application belongs to the field of Internet technology, and specifically relates to an application request processing method, device, equipment and medium. Background Art
[0002] With the rapid development of Internet technology, various online businesses have become increasingly diverse, providing great convenience for users. However, this convenience also brings new challenges, especially in terms of risk control and security management.
[0003] At present, during the operation of the application, there are users who use abnormal means to crack the normal operation rules of the application, so that their own accounts conduct unequal transactions with the application background, and then obtain the same benefits at a lower cost, reducing the fairness of the application relative to other users, seriously disrupting the market order, and causing huge economic losses.
[0004] Therefore, how to identify and intercept malicious behavior of users is a technical problem that needs to be solved urgently by those skilled in the art. Summary of the invention
[0005] The embodiments of the present application provide a risk control method, device, equipment and medium for a target business, the purpose of which is to identify and intercept malicious behavior of users by analyzing the associated information of target business requests, effectively avoid economic losses caused by malicious behavior, and help establish a good usage environment and maintain the fairness of applications.
[0006] In a first aspect, this embodiment provides a risk control method for a target business, the method comprising:
[0007] Obtain a target service request issued by a user through a client for a target service;
[0008] Determine the risk control workflow corresponding to the target business based on the pre-configured risk control information;
[0009] Reading the associated information corresponding to the target business request according to the risk control workflow;
[0010] Starting the risk control workflow, performing risk control calculation on the associated information corresponding to the target business request, and obtaining a risk control calculation result;
[0011] Determining an execution rule corresponding to the risk control calculation result according to the risk control rule for the target business in the pre-configured risk control information;
[0012] The target service request is responded to and controlled according to the execution rule.
[0013] Further, reading the associated information corresponding to the target business request according to the risk control workflow includes:
[0014] Determining the type of associated information to be obtained according to the risk control workflow, the type of associated information including: at least one of account information, device information, and network address information;
[0015] Acquire association information corresponding to the association information type in a historical request record database.
[0016] Further, determining the risk control workflow corresponding to the target business based on the pre-configured risk control information includes:
[0017] Receive pre-configured risk control information;
[0018] Obtaining an application ID according to the target business request;
[0019] Obtain the corresponding risk control workflow from the risk control information according to the application ID.
[0020] Further, the risk control workflow is started, and risk control calculation is performed on the associated information corresponding to the target business request to obtain a risk control calculation result, including:
[0021] Matching the associated information with the preset judgment conditions in the risk control workflow;
[0022] If the match is consistent, the risk control calculation result is determined to be that the user has malicious behavior;
[0023] If the match is inconsistent, the risk control calculation result is determined to be that the user has not engaged in malicious behavior.
[0024] Further, determining the execution rule corresponding to the risk control calculation result according to the risk control rule for the target business in the pre-configured risk control information includes:
[0025] If the risk control calculation result shows that the user has malicious behavior, the first rule is determined to be executed;
[0026] If the risk control calculation result shows that the user has no malicious behavior, the second rule is determined to be the execution rule;
[0027] Accordingly, the target service request is controlled in response to the execution rule, including:
[0028] If the execution rule is the first rule, interrupting the response to the target service request;
[0029] If the execution rule is the second rule, the target service request is responded to.
[0030] Furthermore, after starting the risk control workflow, the method further includes:
[0031] If the execution rule for starting the risk control workflow output is not obtained within the preset time, the user request is responded to.
[0032] Furthermore, it is characterized in that, after responding to the target service request, the method further includes:
[0033] Obtain historical target business requests;
[0034] Counting account data in the associated information of the historical target service requests, the account data including: at least one of the number of unused devices, the number of recharge accounts, and the frequency of login region changes;
[0035] When the account data meets the preset abnormal conditions, a risk control rule cracking prompt is generated.
[0036] In a second aspect, this embodiment provides a risk control device for a target business, the device comprising:
[0037] A target service request acquisition module is used to acquire a target service request issued by a user through a client for a target service;
[0038] A risk control workflow determination module, used to determine the risk control workflow corresponding to the target business based on pre-configured risk control information;
[0039] A correlation information reading module, used to read the correlation information corresponding to the target business request according to the risk control workflow;
[0040] A risk control calculation result acquisition module is used to start the risk control workflow, perform risk control calculation on the associated information corresponding to the target business request, and obtain a risk control calculation result;
[0041] An execution rule determination module, configured to determine an execution rule corresponding to the risk control calculation result according to the risk control rule for the target business in the pre-configured risk control information;
[0042] A response control execution module is used to perform response control on the target service request according to the execution rule.
[0043] In a third aspect, an embodiment of the present application provides an electronic device, which includes a processor, a memory, and a program or instruction stored in the memory and executable on the processor, wherein the program or instruction, when executed by the processor, implements the steps of the method described in the first aspect.
[0044] In a fourth aspect, an embodiment of the present application provides a readable storage medium, on which a program or instruction is stored, and when the program or instruction is executed by a processor, the steps of the method described in the first aspect are implemented.
[0045] In a fifth aspect, an embodiment of the present application provides a chip, comprising a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run a program or instruction to implement the method described in the first aspect.
[0046] In an embodiment of the present application, a target business request issued by a user through a client for a target business is obtained; a risk control workflow corresponding to the target business is determined based on pre-configured risk control information; associated information corresponding to the target business request is read according to the risk control workflow; the risk control workflow is started, and risk control calculations are performed on the associated information corresponding to the target business request to obtain risk control calculation results; based on the risk control rules for the target business in the pre-configured risk control information, an execution rule corresponding to the risk control calculation result is determined; and the target business request is responded to and controlled according to the execution rule. Through the above-mentioned method of risk control of a target business, the identification and processing of malicious behaviors of users can be realized by analyzing the associated information of the target business request, effectively avoiding economic losses caused by malicious behaviors, and being conducive to establishing a good usage environment and maintaining the fairness of the application. BRIEF DESCRIPTION OF THE DRAWINGS
[0047] Figure 1 It is a flowchart of a risk control method for a target business provided in Example 1 of the present application;
[0048] Figure 2 It is a flow chart of a method for controlling risk of recharging provided in Example 1 of the present application;
[0049] Figure 3 This is a flow chart of a risk control method for a target business provided in Example 2 of the present application;
[0050] Figure 4 This is a flow chart of a risk control method for a target business provided in Example 3 of the present application;
[0051] Figure 5 This is a schematic diagram of a matching method for a risk control workflow provided in Example 3 of the present application;
[0052] Figure 6 This is a flow chart of a risk control method for a target business provided in Embodiment 4 of the present application;
[0053] Figure 7 This is a flowchart of a risk control method for a target business provided in Example 5 of the present application;
[0054] Figure 8 This is a flowchart of a risk control method for a target business provided in Example 6 of the present application;
[0055] Fig. 9 It is a flowchart of a method for generating a risk control rule cracking prompt provided in Embodiment 7 of the present application;
[0056] Fig.10 This is a schematic diagram of the structure of a risk control device for a target business provided in Embodiment 8 of the present application;
[0057] Fig.11 It is a structural diagram of an electronic device provided in Example 9 of the present application. DETAILED DESCRIPTION
[0058] In order to make the purpose, technical scheme and advantages of the present application clearer, the specific embodiments of the present application are further described in detail below in conjunction with the accompanying drawings. It is understood that the specific embodiments described herein are only used to explain the present application, rather than to limit the present application. It should also be noted that, for the convenience of description, only the part related to the present application but not all the contents are shown in the accompanying drawings. Before discussing the exemplary embodiments in more detail, it should be mentioned that some exemplary embodiments are described as processes or methods depicted as flow charts. Although the flow chart describes each operation (or step) as a sequential process, many of the operations therein can be implemented in parallel, concurrently or simultaneously. In addition, the order of each operation can be rearranged. The process can be terminated when its operation is completed, but it can also have additional steps not included in the accompanying drawings. The process can correspond to a method, a function, a procedure, a subroutine, a subprogram, etc.
[0059] The following will be combined with the drawings in the embodiments of the present application to clearly describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, rather than all the embodiments. All other embodiments obtained by ordinary technicians in this field based on the embodiments in the present application belong to the scope of protection of this application.
[0060] The terms "first", "second", etc. in the specification and claims of the present application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable under appropriate circumstances, so that the embodiments of the present application can be implemented in an order other than those illustrated or described here, and the objects distinguished by "first", "second", etc. are generally of one type, and the number of objects is not limited. For example, the first object can be one or more. In addition, "and / or" in the specification and claims represents at least one of the connected objects, and the character " / " generally indicates that the objects associated with each other are in an "or" relationship.
[0061] In conjunction with the accompanying drawings, a risk control method, device, equipment and medium for a target business provided by an embodiment of the present application are described in detail through specific embodiments and their application scenarios.
[0062] Embodiment 1
[0063] Figure 1 It is a flowchart of a risk control method for a target business provided in Example 1 of the present application.
[0064] like Figure 1 As shown, the specific steps include:
[0065] S101, obtaining a target service request sent by a user through a client for a target service;
[0066] The application scenario of this solution can be a scenario of identifying and blocking malicious behaviors that occur when users use an application.
[0067] Based on the above scenario, it can be understood that the executor of this scenario can be a risk control decision-making system for identifying and intercepting malicious behavior, or a server or other terminal device running the system, such as a desktop computer, a laptop computer, etc., without making too many restrictions here.
[0068] The client can refer to a program that corresponds to the server and provides local services to customers. Except for some applications that only run locally, the client is generally installed on a common client and needs to cooperate with the server to run.
[0069] The target business can be the functional requirements that the user wants the server to provide, such as the business of registering or logging into the application.
[0070] The target service request can be a request instruction sent by the user to the server to obtain the corresponding functional requirements for the target service. After the server responds to the target service request, it will feed back the processing result of the target service to the client, thereby realizing the corresponding functional requirements.
[0071] The method of obtaining the target service request sent by the user through the client for the target service can be to monitor one or more specific network ports. When the client connects to the port, the server will start to receive the service request sent by the client, and identify and respond to the service request.
[0072] S102: Determine the risk control workflow corresponding to the target business based on pre-configured risk control information;
[0073] The pre-configured risk control information can be pre-determined applications connected to the server that need to identify malicious behavior of users, and set the corresponding risk control workflow for each application as the pre-configured risk control information. Among them, the risk control workflow can be a process for judging the malicious behavior of users, data features that can determine that users have malicious behavior, and judgment rules for determining whether the target business request meets the data features. For example, taking malicious recharge as an example, a risk control workflow is pre-configured to detect whether the recharge request in the game application is a commonly used device. After receiving the user's recharge request, the user's historical login device is obtained to detect whether there is a data feature that the current login device is inconsistent with the historical login device. If so, the recharge request is determined to be a malicious recharge according to the judgment rule.
[0074] A method for determining the risk control workflow corresponding to the target business may be to read the received target business request, obtain the application that sends the target business request, query the application in the pre-configured risk control information, and extract its corresponding risk control workflow.
[0075] S103, reading the associated information corresponding to the target business request according to the risk control workflow;
[0076] The associated information corresponding to the target service request may be the information content related to the current target service request that needs to be obtained in the process of judging the user's malicious behavior according to the workflow. For example, the risk control workflow is to judge whether the user has malicious behavior of charging on behalf of others based on whether the user's recharge device is a common device. The associated information that needs to be obtained may be the device information of the user's current target service request and the historical recharge device information.
[0077] By reading the associated information corresponding to the target business request according to the risk control workflow, after determining the risk control workflow, the judgment rules in the risk control workflow can be identified, the information type required in the judgment rule can be obtained, and in the database storing the business requests, the content consistent with the information type can be obtained as the associated information corresponding to the target business request.
[0078] S104, starting the risk control workflow, performing risk control calculation on the associated information corresponding to the target business request, and obtaining a risk control calculation result;
[0079] The risk control calculation result may be the result of identifying the target business request according to the risk control workflow to determine whether the user has engaged in malicious behavior.
[0080] The method for performing risk control calculation on the associated information corresponding to the target business request can be to obtain the associated information corresponding to the target business request according to the risk control workflow, and match the associated information with the corresponding judgment rules in the risk control workflow. If the associated information meets the requirements of the judgment rules, it is determined that the user has malicious behavior; if the associated information does not meet the requirements of the judgment rules, it is determined that the user has no malicious behavior.
[0081] S105. Determine an execution rule corresponding to the risk control calculation result according to the risk control rule for the target business in the pre-configured risk control information;
[0082] The risk control rules for the target business can be a reference standard for determining which execution rules correspond to different risk control calculation results. Among them, the execution rule can be a treatment measure for a specified risk control calculation result. For example, when the risk control calculation result shows that the user has no malicious behavior, the execution rule is to respond to the target business request issued by the user.
[0083] The method for determining the execution rules corresponding to the risk control calculation results is that after obtaining the risk control calculation results, the risk control rules of the target business recorded in the pre-configured risk control information are read, and the execution rules associated with the content consistent with the risk control calculation results are identified.
[0084] S106: Control the response to the target service request according to the execution rule.
[0085] Response control may be a processing method for a target service request recorded in an execution rule, for example, intercepting a target service request, responding to a target service request, etc.
[0086] The method of controlling the response to the target business request according to the execution rule may be to read the execution rule and run the processing program of the target business request recorded in the execution rule. For example, if the execution rule is to respond to the target business request, the target business request is sent to the corresponding functional module in the server for processing.
[0087] For example, taking game recharge as an example, Figure 2 : is a flow chart of a method for controlling risk of charging provided in Example 1 of the present application, such as Figure 2As shown, the administrator configures the proxy charging features, risk control rules and risk control workflow in advance through the background of the risk control decision system and synchronizes them to the risk control decision system on the server side. When the user opens the game application and performs the recharge operation, the game application located on the client sends the user's recharge request to the server side, and the risk control decision system located on the server side starts to identify the recharge request, selects the corresponding risk control workflow to execute according to the game application that sends the recharge request, reads the associated information type required by the risk control workflow, and the feature service part of the risk control decision system obtains the required feature data from the database according to the associated information type, and feeds it back to the decision service part, which matches the feature data with the pre-configured proxy charging features, and determines whether there is a proxy charging behavior in the current recharge request based on the matching results and risk control rules. If there is a proxy charging behavior, the risk control result can be to intercept the recharge request and prevent virtual props or virtual currency from entering the user's game account; if there is no proxy charging behavior, the risk control result can be to respond to the recharge request and issue virtual props or virtual currency. During the process of the risk control decision system judging the user's request, a timer can be set to obtain the administrator's updated content of at least one of the recharge features, risk control rules and risk control workflows in the background according to a preset period, and synchronize the risk control decision system on the server in a timely manner.
[0088] In an embodiment of the present application, a target business request issued by a user through a client for a target business is obtained; a risk control workflow corresponding to the target business is determined based on pre-configured risk control information; associated information corresponding to the target business request is read according to the risk control workflow; the risk control workflow is started, and risk control calculations are performed on the associated information corresponding to the target business request to obtain risk control calculation results; based on the risk control rules for the target business in the pre-configured risk control information, an execution rule corresponding to the risk control calculation result is determined; and the target business request is responded to and controlled according to the execution rule. Through the above-mentioned method of risk control of a target business, the identification and processing of malicious behaviors of users can be realized by analyzing the associated information of the target business request, effectively avoiding economic losses caused by malicious behaviors, and being conducive to establishing a good usage environment and maintaining the fairness of the application.
[0089] Embodiment 2
[0090] Figure 3It is a flow chart of a risk control method for a target business provided in Example 2 of the present application. This solution makes a better improvement on the above-mentioned embodiment, and the specific improvement is: reading the associated information corresponding to the target business request according to the risk control workflow, including: determining the type of associated information to be obtained according to the risk control workflow, and the associated information type includes: at least one of account information, device information and network address information; obtaining the associated information corresponding to the associated information type in the historical request record database.
[0091] like Figure 3 As shown, specifically including the following:
[0092] S301, obtaining a target service request sent by a user through a client for a target service;
[0093] S302: Determine the risk control workflow corresponding to the target business based on pre-configured risk control information;
[0094] S303: Determine the type of associated information to be obtained according to the risk control workflow, where the type of associated information includes: at least one of account information, device information, and network address information;
[0095] The account information may be the application account information needed to implement the functional requirements in the target business request and the application account information in the record of the historical target business request. For example, in the game recharge business request, the game account to which the virtual currency or virtual props are received.
[0096] Device information may include the name of the device that issued the target service request and related information such as the historical login devices of the current application account.
[0097] The network address information may be the address of the account that sends the target service request.
[0098] Determining the type of associated information that needs to be obtained can be based on the information needed to determine the rules in the risk control workflow. For example, if the risk control workflow needs to identify whether the user's current recharge device is a commonly used device, then the type of associated information that needs to be obtained is determined to be device information.
[0099] S304, acquiring association information corresponding to the association information type in a historical request record database;
[0100] The method of obtaining the associated information in the historical request record database can be that after determining the associated information type, the risk control decision system sends a request for obtaining the associated information to the historical request record database, and identifies and extracts the storage content corresponding to the associated information type in the historical request record database as the associated information. In this process, if it is necessary to obtain the content of multiple associated information types, multiple associated information types can be requested at one time, and the corresponding associated information in the historical request record database can be obtained concurrently. Moreover, after receiving the associated information fed back by the historical request record database, the multiple pieces of associated information can be assembled in a specific format. For example, account information and device information are obtained at the same time in one request, and the associated information fed back by the historical request record database is assembled in the format of account information-device information.
[0101] S305, starting the risk control workflow, performing risk control calculation on the associated information corresponding to the target business request, and obtaining a risk control calculation result;
[0102] S306. Determine an execution rule corresponding to the risk control calculation result according to the risk control rule for the target business in the pre-configured risk control information;
[0103] S307: Control the response to the target service request according to the execution rule.
[0104] The benefit of this arrangement of the solution is that multiple pieces of related information can be concurrently obtained from the historical request record database in one request, saving data acquisition time and helping to improve the response time of the server to business requests issued by users.
[0105] Embodiment 3
[0106] Figure 4 This is a flowchart of a risk control method for a target business provided in Example 3 of the present application. This solution makes a better improvement on the above-mentioned embodiment, and the specific improvement is: determining the risk control workflow corresponding to the target business based on pre-configured risk control information, including: receiving pre-configured risk control information; obtaining an application ID according to the target business request; obtaining the corresponding risk control workflow in the risk control information according to the application ID.
[0107] like Figure 4 As shown, specifically including the following:
[0108] S401, obtaining a target service request sent by a user through a client for a target service;
[0109] S402, receiving pre-configured risk control information;
[0110] The method for receiving pre-controlled risk control information can be that the staff counts the applications that need to be identified for malicious behavior, and sets up corresponding risk control workflows for each application, associates the application with its corresponding risk control workflow, writes it into a designated file as risk control information, and uploads it to the risk control decision system, which receives the risk control information.
[0111] S403, obtaining an application ID according to the target service request;
[0112] The application ID may be an identification code used to distinguish an application.
[0113] The method of obtaining the application ID according to the target business request may be to identify the target business request and extract the application ID from a specified field in the target business request.
[0114] S404, obtaining a corresponding risk control workflow in the risk control information according to the application ID;
[0115] The method of obtaining the corresponding risk control workflow in the risk control information based on the application ID is to identify the content consistent with the current application ID in the risk control information uploaded by the staff, and obtain the information associated with the application ID as the risk control workflow that needs to be executed currently.
[0116] S405. Read the associated information corresponding to the target business request according to the risk control workflow;
[0117] S406: Start the risk control workflow, perform risk control calculation on the associated information corresponding to the target business request, and obtain a risk control calculation result;
[0118] S407, determining an execution rule corresponding to the risk control calculation result according to the risk control rule for the target business in the pre-configured risk control information;
[0119] S408: Control the response to the target service request according to the execution rule.
[0120] For example, taking the game application as an example, Figure 5 Schematic diagram of a matching method for a risk control workflow provided in Example 3 of the present application. Figure 5As shown, after the user sends a game recharge request, the game ID in the recharge request is obtained. If the game ID is 1, it is identified whether the sending device of the current recharge request is the user's frequently logged-in device or frequently recharged device. If it is not a frequently used device, it is determined that the user has engaged in proxy recharge behavior; if the game ID is 2, it is identified whether the recharge account associated with the sending IP of the current recharge request is greater than or equal to 30. If it is greater than or equal to 30, it is determined that the user has engaged in proxy recharge behavior; if the game ID is 3, it is first identified whether the sending device of the current recharge request is the user's frequently logged-in device or frequently recharged device. If it is not a frequently used device, it is determined that the user has engaged in proxy recharge behavior. If it is a frequently used device of the user, it is then identified whether the recharge account associated with the sending IP of the current recharge request is greater than or equal to 30. If it is greater than or equal to 30, it is determined that the user has engaged in proxy recharge behavior.
[0121] The advantage of this setting of the scheme is that it can support the identification and processing of malicious behaviors of multiple applications, and realize personalized customization of the malicious behavior judgment process for different applications, which is conducive to expanding the scope of application of the risk control decision-making system.
[0122] Embodiment 4
[0123] Figure 6 This is a flow chart of a risk control method for a target business provided in Example 4 of the present application. This solution makes better improvements to the above-mentioned embodiment, and the specific improvements are as follows:
[0124] like Figure 6 As shown, specifically including the following:
[0125] S601, obtaining a target service request sent by a user through a client for a target service;
[0126] S602: Determine the risk control workflow corresponding to the target business based on pre-configured risk control information;
[0127] S603, reading the associated information corresponding to the target business request according to the risk control workflow;
[0128] S604, identifying whether the associated information matches the preset judgment condition in the risk control workflow; if not, executing S605; if yes, executing S606;
[0129] The preset judgment condition may be a user malicious behavior judgment standard pre-determined for each risk control workflow. When the associated information corresponding to the target business request meets the preset judgment condition, it can be determined that the user has malicious behavior.
[0130] The method for identifying whether the associated information matches the preset judgment conditions in the risk control workflow can be to obtain the preset judgment conditions corresponding to the current risk control workflow, and match the associated information with the same type of data in the preset judgment conditions. If the matches are consistent, it is determined that the user has malicious behavior; if the matches are inconsistent, it is determined that the user has not engaged in malicious behavior. In this solution, the preset judgment conditions corresponding to different risk control workflows are also different. The preset judgment conditions can be one or more. If there are multiple preset judgment conditions, if the associated information matches any one of the preset judgment conditions, it is determined that the user has engaged in malicious behavior.
[0131] S605: Determine that the risk control calculation result shows that the user does not have any malicious behavior;
[0132] In this solution, when the associated information does not match any of the preset judgment conditions in the risk control workflow, it can be determined that the risk control calculation result is that the user does not have malicious behavior.
[0133] S606: Determine that the risk control calculation result indicates that the user has engaged in malicious behavior;
[0134] In this solution, when the associated information matches any preset judgment condition in the risk control workflow, it can be determined that the risk control calculation result indicates that the user has engaged in malicious behavior.
[0135] S607: Determine an execution rule corresponding to the risk control calculation result according to the risk control rule for the target business in the pre-configured risk control information;
[0136] S608: Control the response to the target service request according to the execution rule.
[0137] The benefit of this arrangement of the present invention is that it is possible to determine whether the user has engaged in malicious behavior based on the matching result of the associated information with the preset judgment conditions, thereby providing a basis for judging malicious behavior and helping to improve the accuracy of judging malicious behavior.
[0138] Embodiment 5
[0139] Figure 7 This is a flow chart of a risk control method for a target business provided in Example 5 of the present application. This solution makes better improvements to the above-mentioned embodiment, and the specific improvements are as follows:
[0140] like Figure 7 As shown, specifically including the following:
[0141] S701, obtaining a target service request sent by a user through a client for a target service;
[0142] S702: Determine the risk control workflow corresponding to the target business based on pre-configured risk control information;
[0143] S703, reading the associated information corresponding to the target business request according to the risk control workflow;
[0144] S704, identifying whether the associated information matches the preset judgment condition in the risk control workflow; if so, executing S705; if not, executing S708;
[0145] S705. Determine that the risk control calculation result indicates that the user has engaged in malicious behavior;
[0146] S706, determining that the execution rule is the first rule;
[0147] The first rule may be a method of handling target business requests with malicious behavior that is pre-specified by the staff in the risk control information. For example, after determining that the user has malicious behavior, the target business request is intercepted, or malicious behavior prompt information is generated and sent to the staff.
[0148] S707, interrupting the response to the target service request;
[0149] The way to interrupt the response of the target service request can be to intercept the target service request and prevent it from being sent to the corresponding function module of the server for processing, or to prevent the corresponding function module of the server from feeding back the response result to the client. For example, if the virtual currency recharge request sent by the user to the server contains a recharge anomaly, the virtual currency will be blocked from being issued to the account.
[0150] S708. Determine that the risk control calculation result shows that the user does not have any malicious behavior;
[0151] S709, determining that the execution rule is the second rule;
[0152] The second rule may be a processing method for target business requests that do not involve malicious behavior that is pre-specified by the staff in the risk control information. For example, after determining that the user does not involve malicious behavior, the server responds to the client in accordance with the conventional processing method for the current target business request.
[0153] S710: Respond to the target service request.
[0154] The method of responding to the target business request may be, after determining to process the target business request according to the second rule, sending the target business request to the corresponding function module in the server, and the function module responds to the target business request according to the pre-set processing rule. For example, for a virtual currency recharge request without any proxy recharge behavior, the risk control decision system sends it to the recharge function module of the server, and the recharge function module issues a specified amount of virtual currency to the corresponding game account according to the specific content of the target business request.
[0155] The advantage of this setting of the scheme is that it can avoid the impact of the risk control decision system on the response effect of the user's normal operation while identifying malicious behavior, which is conducive to ensuring the normal operation of other functions in the application.
[0156] Embodiment 6
[0157] Figure 8 This is a flowchart of a risk control method for a target business provided in Example 6 of the present application. This solution makes a better improvement on the above-mentioned embodiment, and the specific improvement is: after starting the risk control workflow, the method further includes: if the execution rule for starting the output of the risk control workflow is not obtained within a preset time, responding to the user request.
[0158] like Figure 8 As shown, specifically including the following:
[0159] S801, obtaining a target service request sent by a user through a client for a target service;
[0160] S802: Determine the risk control workflow corresponding to the target business based on pre-configured risk control information;
[0161] S803. Read the associated information corresponding to the target business request according to the risk control workflow;
[0162] S804, starting the risk control workflow, performing risk control calculation on the associated information corresponding to the target business request, and obtaining a risk control calculation result;
[0163] S805: If no execution rule for starting the output of the risk control workflow is obtained within a preset time, responding to the user request;
[0164] The preset time may be the response time of the risk control decision system set in advance by the staff. If the risk control decision system fails to feedback the execution rules within the preset time, the target business request issued by the user will be processed in a conventional manner, thereby avoiding affecting the user's experience.
[0165] The way to respond to user requests is to start timing after starting the risk control workflow, and compare the accumulated time with the preset time. If the accumulated time is greater than or equal to the preset time, there is no need to wait for the risk control decision system to give an execution rule, and the target business request can be directly sent to the corresponding functional module on the server for processing.
[0166] S806. Determine an execution rule corresponding to the risk control calculation result according to the risk control rule for the target business in the pre-configured risk control information;
[0167] S807: Control the response to the target service request according to the execution rule.
[0168] The advantage of this setting is that by setting a preset time, the problem of long user request response time reducing the user experience can be avoided, which is conducive to ensuring the stability of other functions of the application.
[0169] Embodiment 7
[0170] Fig. 9 This is a flow chart of the method for generating a risk control rule cracking prompt provided in Example 7 of the present application. This solution makes a better improvement on the above-mentioned embodiment, and the specific improvement is: after responding to the target business request, the method also includes: obtaining historical target business requests; counting the account data in the associated information of the historical target business requests, the account data includes: at least one of the number of uncommon devices, the number of recharge accounts, and the frequency of login area changes; when the account data meets the preset abnormal conditions, a risk control rule cracking prompt is generated.
[0171] like Fig. 9 As shown, specifically including the following:
[0172] S901, obtaining historical target business requests;
[0173] The historical target business request may be a historical request record for the same application account, for example, a historical record of a login request, a virtual currency recharge request, and an achievement acquisition request for the same game account in the game.
[0174] The method for acquiring the historical target business request may be to acquire the application account that needs to be processed in the current business request, and extract the historical target business request related to the application account from the historical request record database.
[0175] S902, counting account data in the associated information of the historical target service request, the account data including: at least one of the number of unused devices, the number of recharge accounts, and the frequency of login region changes;
[0176] The number of uncommon devices can be the number of devices with low usage frequency and number of times in historical target business requests. For example, in historical target business requests, the application account has logged in on three devices a, b, and c, with the number of logins being 1, 97, and 3 respectively. Then, both devices a and c are uncommon devices, and the number of uncommon devices is 2.
[0177] The number of recharge accounts can be the number of accounts that have recharged the current application account in the historical target service requests. For example, in a game application, a user can recharge his own game account or recharge other game accounts as a gift. If a game account has 7 recharge records, and the accounts that recharged it are the current game account, account A, and account B, then the number of recharge accounts is 3.
[0178] The login region change frequency can be the average number of changes in the region where the application account logs in within a specified time period in the historical target business requests. For example, within a week, an application account logs in in City A, City A, City B, City A, and City A, then the login region change frequency is twice a week.
[0179] S903: When the account data meets the preset abnormal conditions, a risk control rule cracking prompt is generated.
[0180] The preset abnormal conditions may be pre-set conditions for determining whether a user has cracked the risk control rules. The preset abnormal conditions may include the upper limit of the number of uncommon devices, the upper limit of the number of recharge accounts, and the maximum frequency of login region changes.
[0181] The method for generating a risk control rule cracking prompt may be to compare the account data with the preset abnormal conditions. When the number of uncommonly used devices exceeds the upper limit of the number of uncommonly used devices, or the number of recharge accounts exceeds the upper limit of the number of recharge accounts, or the login area change frequency exceeds the maximum login area change frequency, if one of the requirements is met, it is determined that the account data meets the preset abnormal conditions. At this time, the account data, the specific content that meets the preset abnormal conditions, and the current target business request are compiled together as a risk control rule cracking prompt and sent to the staff's terminal device to prompt the staff that the user has cracked the risk control rules of the risk control decision system.
[0182] The benefit of setting up this solution is that by analyzing historical target business requests, it is possible to identify users' behaviors of cracking the risk control rules of the risk control decision-making system, which is conducive to timely repairing the rule loopholes in the risk control decision-making system and avoiding greater economic losses.
[0183] Embodiment 8
[0184] Fig.10 It is a structural diagram of the risk control device for the target business provided in Example 8 of the present application.
[0185] like Fig.10 As shown, specifically including the following:
[0186] The target service request acquisition module 1001 is used to acquire a target service request issued by a user through a client for a target service;
[0187] The risk control workflow determination module 1002 is used to determine the risk control workflow corresponding to the target business based on pre-configured risk control information;
[0188] The associated information reading module 1003 is used to read the associated information corresponding to the target business request according to the risk control workflow;
[0189] The risk control calculation result acquisition module 1004 is used to start the risk control workflow, perform risk control calculation on the associated information corresponding to the target business request, and obtain the risk control calculation result;
[0190] An execution rule determination module 1005 is used to determine an execution rule corresponding to the risk control calculation result according to the risk control rule for the target business in the pre-configured risk control information;
[0191] The response control execution module 1006 is used to perform response control on the target service request according to the execution rule.
[0192] In an embodiment of the present application, a target business request acquisition module is used to acquire a target business request issued by a user through a client for a target business; a risk control workflow determination module is used to determine the risk control workflow corresponding to the target business based on pre-configured risk control information; an associated information reading module is used to read the associated information corresponding to the target business request according to the risk control workflow; a risk control calculation result acquisition module is used to start the risk control workflow, perform risk control calculation on the associated information corresponding to the target business request, and obtain the risk control calculation result; an execution rule determination module is used to determine the execution rule corresponding to the risk control calculation result according to the risk control rule for the target business in the pre-configured risk control information; and a response control execution module is used to perform response control on the target business request according to the execution rule. Through the above-mentioned device for risk control of a target business, the identification and processing of malicious behaviors of users can be realized by analyzing the associated information of the target business request, effectively avoiding economic losses caused by malicious behaviors, and being conducive to establishing a good use environment and maintaining the fairness of the application.
[0193] A risk control device for a target business in an embodiment of the present application may be a device, or a component, an integrated circuit, or a chip in a terminal. The device may be a mobile electronic device or a non-mobile electronic device. Exemplarily, the mobile electronic device may be a mobile phone, a tablet computer, a laptop computer, a PDA, an in-vehicle electronic device, a wearable device, an ultra-mobile personal computer (UMPC), a netbook, or a personal digital assistant (PDA), etc., and the non-mobile electronic device may be a server, a network attached storage (NAS), a personal computer (PC), a television (TV), a teller machine or a self-service machine, etc., which is not specifically limited in the embodiment of the present application.
[0194] A device for risk control of a target business in an embodiment of the present application may be a device having an operating system. The operating system may be an Android operating system, an iOS operating system, or other possible operating systems, which are not specifically limited in the embodiment of the present application.
[0195] The device for risk control of a target business provided in the embodiment of the present application can implement each process implemented in the above-mentioned method embodiments, and will not be described again here to avoid repetition.
[0196] Embodiment 9
[0197] like Fig. 9 As shown, an embodiment of the present application also provides an electronic device 900, including a processor 901, a memory 902, and a program or instruction stored in the memory 902 and executable on the processor 901. When the program or instruction is executed by the processor 901, each process of an embodiment of a device for risk control of a target business described above is implemented, and the same technical effect can be achieved. To avoid repetition, it will not be described here.
[0198] It should be noted that the electronic devices in the embodiments of the present application include the mobile electronic devices and non-mobile electronic devices mentioned above.
[0199] Embodiment 10
[0200] An embodiment of the present application also provides a readable storage medium, on which a program or instruction is stored. When the program or instruction is executed by a processor, the various processes of the device embodiment for risk control of the above-mentioned target business are implemented, and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.
[0201] The processor is a processor in the electronic device described in the above embodiment. The readable storage medium includes a computer readable storage medium, such as a computer read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.
[0202] Embodiment 11
[0203] An embodiment of the present application further provides a chip, which includes a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the various processes of the device embodiment for risk control of the above-mentioned target business, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.
[0204] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.
[0205] It should be noted that, in this article, the terms "comprise", "include" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article 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, article or device. In the absence of further restrictions, an element defined by the sentence "comprises one..." does not exclude the presence of other identical elements in the process, method, article or device including the element. In addition, it should be noted that the scope of the method and device in the embodiment of the present application is not limited to performing functions in the order shown or discussed, and may also include performing functions in a substantially simultaneous manner or in reverse order according to the functions involved, for example, the described method may be performed in an order different from that described, and various steps may also be added, omitted, or combined. In addition, the features described with reference to certain examples may be combined in other examples.
[0206] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus a necessary general hardware platform, and of course by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present application, or the part that contributes to the prior art, can be embodied in the form of a computer software product, which is stored in a storage medium (such as ROM / RAM, a disk, or an optical disk), and includes a number of instructions for a terminal (which can be a mobile phone, a computer, a server, or a network device, etc.) to execute the methods described in each embodiment of the present application.
[0207] The embodiments of the present application are described above in conjunction with the accompanying drawings, but the present application is not limited to the above-mentioned specific implementation methods. The above-mentioned specific implementation methods are merely illustrative and not restrictive. Under the guidance of the present application, ordinary technicians in this field can also make many forms without departing from the purpose of the present application and the scope of protection of the claims, all of which are within the protection of the present application.
[0208] The above are only preferred embodiments of the present application and the technical principles used. The present application is not limited to the specific embodiments described herein, and various obvious changes, readjustments and substitutions that can be made by those skilled in the art will not deviate from the scope of protection of the present application. Therefore, although the present application is described in more detail through the above embodiments, the present application is not limited to the above embodiments, and may include more other equivalent embodiments without departing from the concept of the present application, and the scope of the present application is determined by the scope of the claims.
Claims
1. A risk control method for a target business, characterized in that: The method comprises: Obtain a target service request issued by a user through a client for a target service; Determine the risk control workflow corresponding to the target business based on the pre-configured risk control information; Reading the associated information corresponding to the target business request according to the risk control workflow; Starting the risk control workflow, performing risk control calculation on the associated information corresponding to the target business request, and obtaining a risk control calculation result; Determining an execution rule corresponding to the risk control calculation result according to the risk control rule for the target business in the pre-configured risk control information; The target service request is responded to and controlled according to the execution rule.
2. The target business risk control method according to claim 1, characterized in that: Reading the associated information corresponding to the target business request according to the risk control workflow includes: Determining the type of associated information to be obtained according to the risk control workflow, the type of associated information including: at least one of account information, device information, and network address information; The associated information corresponding to the associated information type is obtained.
3. The risk control method for target business according to claim 1, characterized in that: Determining the risk control workflow corresponding to the target business based on the pre-configured risk control information includes: Receive pre-configured risk control information; Obtaining an application ID according to the target business request; Obtain the corresponding risk control workflow from the risk control information according to the application ID.
4. The risk control method for target business according to claim 1, characterized in that: The risk control workflow is started, and risk control calculation is performed on the associated information corresponding to the target business request to obtain a risk control calculation result, including: Matching the associated information with the preset judgment conditions in the risk control workflow; If the match is consistent, the risk control calculation result is determined to be that the user has malicious behavior; If the match is inconsistent, the risk control calculation result is determined to be that the user has not engaged in malicious behavior.
5. The risk control method for target business according to claim 4, characterized in that: Determining, according to the risk control rules for the target business in the pre-configured risk control information, an execution rule corresponding to the risk control calculation result, including: If the risk control calculation result shows that the user has malicious behavior, the first rule is determined to be executed; If the risk control calculation result shows that the user has no malicious behavior, the second rule is determined to be the execution rule; Accordingly, the target service request is controlled in response to the execution rule, including: If the execution rule is the first rule, interrupting the response to the target service request; If the execution rule is the second rule, the target service request is responded to.
6. The risk control method for target business according to claim 1, characterized in that: After starting the risk control workflow, the method further includes: If the execution rule for starting the risk control workflow output is not obtained within the preset time, the user request is responded to.
7. The risk control method for target business according to claim 5, characterized in that: After responding to the target service request, the method further includes: Obtain historical target business requests; Counting account data in the associated information of the historical target service requests, the account data including: at least one of the number of unused devices, the number of recharge accounts, and the frequency of login region changes; When the account data meets the preset abnormal conditions, a risk control rule cracking prompt is generated.
8. A risk control device for a target business, characterized in that: The device comprises: A target service request acquisition module is used to acquire a target service request issued by a user through a client for a target service; A risk control workflow determination module, used to determine the risk control workflow corresponding to the target business based on pre-configured risk control information; A correlation information reading module, used to read the correlation information corresponding to the target business request according to the risk control workflow; A risk control calculation result acquisition module is used to start the risk control workflow, perform risk control calculation on the associated information corresponding to the target business request, and obtain a risk control calculation result; An execution rule determination module, configured to determine an execution rule corresponding to the risk control calculation result according to the risk control rule for the target business in the pre-configured risk control information; A response control execution module is used to perform response control on the target service request according to the execution rule.
9. An electronic device, characterized in that: It includes a processor, a memory, and a program or instruction stored in the memory and executable on the processor, wherein when the program or instruction is executed by the processor, the steps of a risk control method for a target business as described in any one of claims 1 to 7 are implemented.
10. A readable storage medium, characterized in that: The readable storage medium stores a program or instruction, and when the program or instruction is executed by the processor, the steps of a risk control method for a target business as described in any one of claims 1-7 are implemented.
Citation Information
Patent Citations
Business-oriented risk control method and device
CN112651619A
Fraud identification method and device, electronic equipment and computer readable storage medium
CN112819611A
Risk control method, risk processing system and device, server and storage medium
CN114240060A
Risk identification method and device of service request, storage medium and processor
CN115564576A
Method and apparatus for risk management and control, computer apparatus, and storage medium
WO2021073270A1
