Risk control method, device, equipment, medium and program product

Abstract

The invention provides a risk control method which can be applied to the technical field of information security or the field of finance. The risk control method comprises the steps of obtaining a first operation instruction; and performing risk control on the first operation instruction based on risk control parameters, the risk control parameters including an operation counting parameter and an operation state parameter, the execution risk control on the first operation instruction comprises the following steps: adjusting the operation counting parameter and the operation state parameter based on the execution condition of the operation instruction at the current time point, and keeping the number of the operation instructions being executed in the current process to be less than or equal to 1. The invention further provides a risk control device and equipment, a storage medium and a program product.

Description

Technical Field

[0001] The present disclosure relates to the field of information security technology, and in particular, to a risk control method, device, equipment, medium and program product. Background Art

[0002] With the rapid replacement of Internet technology, online business has flourished, and a large number of fields with high risk control management requirements, including banking business, have also transferred a large number of businesses to mobile terminals for processing. Due to the continuous and rapid update of mobile terminals and application versions, there is often a poor match between the terminal and the application version, resulting in a scenario where the transaction interface is stuck and unresponsive due to a certain operation during the transaction. At this time, if the user clicks repeatedly, it is possible that invalid operation instructions will be sent multiple times before the previous process ends. If the system repeats the processing at this time, it will cause a serious waste of computing resources, resulting in the risk of terminal stuck and unresponsiveness. In addition, if the user accidentally clicks to the next interface at the moment when the stuck ends and the interface switches to trigger a certain function, it is easy to have the risk of misoperation, and the transaction risk increases. Summary of the invention

[0003] In view of the above problems, the present disclosure provides a risk control method, apparatus, device, medium and program product.

[0004] According to the first aspect of the present disclosure, a risk control method is provided, comprising: obtaining a first operation instruction; and performing execution risk control on the first operation instruction based on risk control parameters, wherein the risk control parameters include an operation count parameter and an operation status parameter, wherein the execution risk control on the first operation instruction comprises: adjusting the operation count parameter and the operation status parameter based on the execution status of the operation instruction at a current point in time, so as to keep the number of operation instructions being executed by the current process less than or equal to 1.

[0005] According to an embodiment of the present disclosure, the operation count parameter and the operation status parameter are adjusted based on the execution status of the operation instruction at the current point in time to keep the number of operation instructions being executed by the current process less than or equal to 1, including: judging whether there is a second operation instruction being executed based on the operation status parameter; and when there is no second operation instruction being executed, judging the number of operation executions based on the operation count parameter, wherein when the number of operation executions is not zero, increasing the value of the operation count parameter, recording the first operation instruction, and uploading the first operation instruction to the server.

[0006] According to an embodiment of the present disclosure, when the number of execution times of the operation behavior is zero, the first operation instruction is executed and the operation state parameter is changed.

[0007] According to an embodiment of the present disclosure, when there is a second operation instruction being executed, the method includes: waiting for the operation execution time, recording the first operation instruction, and uploading the first operation instruction to a server.

[0008] According to an embodiment of the present disclosure, the execution risk control of the first operation instruction also includes: determining whether the first operation instruction is a repeated operation instruction; and when the first operation instruction is a repeated operation instruction, waiting for the operation execution time, recording the first operation instruction, and uploading the first operation instruction to the server.

[0009] According to an embodiment of the present disclosure, the determining whether the first operation instruction is a repeated operation instruction includes: determining whether the first operation instruction is the first operation of the current process based on a transaction source variable and a transaction information variable; wherein, when the first operation instruction is not the first operation of the current process, the method further includes: determining whether the first operation instruction is a homogeneous operation with a previous operation based on a transaction information variable; wherein, when the first operation instruction is a homogeneous operation with a previous operation, the method further includes: determining whether the first operation instruction is a repeated operation with a previous operation based on the operation information variable, wherein the transaction source variable is used to determine the user source of the transaction, the transaction information variable is used to determine the operation behavior of the transaction, and the operation information variable is used to determine the terminal control element of the current operation behavior, wherein the operation information of the previous operation is obtained from the system pre-stored information.

[0010] According to an embodiment of the present disclosure, the transaction information variable includes at least an operation time point, and the determining whether the first operation instruction is the first operation of the current process based on the transaction source variable and the transaction information variable includes: determining whether the first operation instruction and the previous operation are from the same user based on the transaction source variable; when the first operation instruction and the previous operation are from the same user, calculating the time interval between the first operation instruction and the previous operation based on the operation time point of the first operation instruction and the operation time point of the previous operation; determining whether the time interval between the first operation instruction and the previous operation is less than a first threshold; and when the time interval between the first operation instruction and the previous operation is less than the first threshold, determining that the first operation instruction is not the first operation of the current process.

[0011] According to an embodiment of the present disclosure, the transaction information variable includes multiple operation dimensions, and the judging whether the first operation instruction is a homogeneous operation with the previous operation based on the transaction information variable includes: judging the matching degree between each operation dimension of the first operation instruction and each operation dimension of the previous operation; and when the matching degree between each operation dimension of the first operation instruction and each operation dimension of the previous operation reaches a preset value, judging that the first operation instruction is a homogeneous operation with the previous operation.

[0012] According to an embodiment of the present disclosure, the operation information variable includes multiple control dimensions, and the judging whether the first operation instruction is a repeated operation with the previous operation based on the operation information variable includes: calculating the similarity between the terminal control element of the first operation instruction and the terminal control element of the previous operation based on the multiple control dimensions; and when the similarity between the terminal control element of the first operation instruction and the terminal control element of the previous operation reaches a second threshold, judging that the first operation instruction is a repeated operation with the previous operation.

[0013] According to an embodiment of the present disclosure, the similarity between the terminal control elements of the first operation instruction and the terminal control elements of the previous operation is calculated based on the multiple control dimensions, including: calculating the similarity of the terminal control elements based on the element similarity of each control dimension and the element weight of each control dimension, wherein the method for calculating the element similarity of the i-th control dimension includes: calculating the element similarity between the i-th control dimension of the first operation instruction and the i-th control dimension of the previous operation of the current process based on a preset similarity algorithm.

[0014] According to an embodiment of the present disclosure, the transaction source variable includes at least two of the terminal model, the terminal system type, and the application version; and / or, the transaction information variable includes at least two of the operation type, the operation timing, the number of terminal contacts, and the operation mode; and / or, the operation information variable includes at least the contact coordinate position, and the operation information variable also includes at least two of the number of terminal contacts, contact contact pressure, contact contact time, contact control times, and contact sliding distance.

[0015] According to an embodiment of the present disclosure, when the operation information variable includes a touch point coordinate position, the touch point coordinate position has the highest control dimension element weight.

[0016] According to an embodiment of the present disclosure, the method also includes: checking the terminal computing resource occupancy rate and the application communication signal strength; and when the terminal computing resource occupancy rate and the application communication signal strength both meet preset standard values, judging whether there is a second operation instruction currently being executed based on the operation status parameters.

[0017] According to an embodiment of the present disclosure, the method further includes: checking whether the operation instruction being executed by the current process is executed successfully, and if the execution is successful, resetting the operation count parameter and the operation status parameter.

[0018] According to an embodiment of the present disclosure, if the execution is unsuccessful, the method further includes: continuing to process the operation instruction being executed by the current process; and increasing the value of the operation count parameter.

[0019] According to an embodiment of the present disclosure, the method further includes: determining whether the operation count parameter is greater than or equal to a fourth threshold; when the operation count parameter is greater than or equal to the fourth threshold, recording the current operation instruction, and uploading the current operation instruction to a server.

[0020] According to an embodiment of the present disclosure, the method further includes: when the user exits the current process, recording the current operation instruction, and uploading the current operation instruction to the server.

[0021] The second aspect of the present disclosure provides a risk control device, including: an acquisition module, configured to acquire a first operation instruction; and a risk control module, configured to perform execution risk control on the first operation instruction based on risk control parameters, wherein the risk control parameters include an operation count parameter and an operation status parameter, wherein the execution risk control on the first operation instruction includes: adjusting the operation count parameter and the operation status parameter based on the execution status of the operation instruction at a current point in time, and keeping the number of operation instructions being executed by the current process less than or equal to 1.

[0022] A third aspect of the present disclosure provides an electronic device, comprising: one or more processors; and a memory for storing one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors execute the above-mentioned risk control method.

[0023] The fourth aspect of the present disclosure further provides a computer-readable storage medium having executable instructions stored thereon, which, when executed by a processor, causes the processor to execute the above-mentioned risk control method.

[0024] The fifth aspect of the present disclosure also provides a computer program product, including a computer program, which implements the above-mentioned risk control method when executed by a processor. BRIEF DESCRIPTION OF THE DRAWINGS

[0025] The above contents and other objects, features and advantages of the present disclosure will become more apparent through the following description of the embodiments of the present disclosure with reference to the accompanying drawings, in which:

[0026] Figure 1 The application scenario diagram of the risk control method, apparatus, device, medium and program product according to the embodiments of the present disclosure is schematically shown.

[0027] Figure 2 The flowchart of the risk control method according to the embodiment of the present disclosure is schematically shown.

[0028] Figure 3The flowchart schematically shows a method for adjusting the operation count parameter and the operation status parameter based on the execution status of the operation instruction at the current time point according to an embodiment of the present disclosure to keep the number of operation instructions being executed by the current process less than or equal to 1.

[0029] Figure 4 The flowchart of the method for processing the first operation instruction of a repeated operation according to an embodiment of the present disclosure is schematically shown.

[0030] Figure 5 The flowchart of the method for determining whether the first operation instruction is a repeated operation instruction according to an embodiment of the present disclosure is schematically shown.

[0031] Figure 6 The flowchart of the method for first operation judgment according to an embodiment of the present disclosure is schematically shown.

[0032] Figure 7 The flowchart of the method for determining homogeneous operations according to an embodiment of the present disclosure is schematically shown.

[0033] Figure 8 The flowchart of the method for repeated operation judgment according to an embodiment of the present disclosure is schematically shown.

[0034] Fig. 9 A flowchart of a method for calculating the similarity between a terminal control element of a first operation instruction and a terminal control element of a previous operation according to some specific embodiments of the present disclosure is schematically shown.

[0035] Fig.10 A flowchart of a method for calculating the element similarity of the i-th control dimension according to some specific embodiments of the present disclosure is schematically shown.

[0036] Fig.11 The flowchart of the method for checking the supply status of environmental resources according to an embodiment of the present disclosure is schematically shown.

[0037] Fig.12 The flowchart of the method for resetting the operation count parameter and the operation state parameter according to the embodiment of the present disclosure is schematically shown.

[0038] Fig.13 The flowchart schematically shows a method for suspending the execution of an operation instruction when a trigger condition is met according to an embodiment of the present disclosure.

[0039] Fig.14 The flowchart schematically shows a method for processing sudden process termination according to an embodiment of the present disclosure.

[0040] Fig.15 A flowchart of a risk control method according to a specific example of an embodiment of the present disclosure is exemplified.

[0041] Fig.16 The structural block diagram of the risk control device according to the embodiment of the present disclosure is schematically shown.

[0042] Fig.17 A block diagram of an electronic device suitable for implementing a risk control method according to an embodiment of the present disclosure is schematically shown. DETAILED DESCRIPTION

[0043] Hereinafter, embodiments of the present disclosure will be described with reference to the accompanying drawings. However, it should be understood that these descriptions are exemplary only and are not intended to limit the scope of the present disclosure. In the following detailed description, for ease of explanation, many specific details are set forth to provide a comprehensive understanding of the embodiments of the present disclosure. However, it is apparent that one or more embodiments may also be implemented without these specific details. In addition, in the following description, descriptions of known structures and technologies are omitted to avoid unnecessary confusion of the concepts of the present disclosure.

[0044] The terms used herein are only for describing specific embodiments and are not intended to limit the present disclosure. The terms "comprise", "include", etc. used herein indicate the existence of the features, steps, operations and / or components, but do not exclude the existence or addition of one or more other features, steps, operations or components.

[0045] All terms (including technical and scientific terms) used herein have the meanings commonly understood by those skilled in the art, unless otherwise defined. It should be noted that the terms used herein should be interpreted as having a meaning consistent with the context of this specification, and should not be interpreted in an idealized or overly rigid manner.

[0046] When using expressions such as "at least one of A, B, and C, etc.", they should generally be interpreted according to the meaning of the expression commonly understood by those skilled in the art (for example, "a system having at least one of A, B, and C" should include but is not limited to a system having A alone, B alone, C alone, A and B, A and C, B and C, and / or A, B, C, etc.).

[0047] With the rapid replacement of Internet technology, online business has flourished. A large number of areas with high risk control requirements, including banking business, have also transferred a large number of businesses to mobile terminals for processing. Due to the continuous and rapid update of mobile terminals and application versions, there is often a situation where the terminal and application version are not well matched. For example, there are many brands of mobile terminals, rich models, and fast iteration speed. At the same time, bank clients are continuously updated, resulting in business scenarios where various mobile terminals with different performance are combined with new and old bank clients. In particular, mobile phones with poor performance are installed with new versions of bank clients with higher performance requirements, resulting in a scenario where the transaction interface is stuck and unresponsive due to a certain operation during the transaction. At this time, if the user lacks patience and clicks repeatedly, it is possible that invalid operation instructions will be sent multiple times before the previous process ends. At this time, if the system repeats the processing, it will cause a serious waste of computing resources, resulting in the risk of terminal stuck and unresponsiveness. In addition, if the user accidentally clicks to the next interface at the moment when the stuck ends and the interface switches to trigger a certain function, it is easy to have the risk of misoperation and increase the transaction risk.

[0048] Based on the above-mentioned problems existing in the prior art, an embodiment of the present disclosure provides a risk control method, including: obtaining a first operation instruction; and performing execution risk control on the first operation instruction based on risk control parameters, wherein the risk control parameters include an operation count parameter and an operation status parameter, wherein the execution risk control on the first operation instruction includes: adjusting the operation count parameter and the operation status parameter based on the execution status of the operation instruction at the current time point, so as to keep the number of operation instructions being executed by the current process less than or equal to |.

[0049] The embodiment of the present disclosure uses operation count parameters and operation status parameters to control the execution of operation instructions, improves the accuracy of user operation capture by controlling the number of operation instructions being executed by the current process, and reduces system pressure and the risk of false touches. The method of the embodiment of the present disclosure is particularly suitable for processing high-risk services in a low-performance state of a mobile phone.

[0050] In the technical solution of the present invention, the user information (including but not limited to user personal information, user image information, user device information, such as location information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved are all information and data authorized by the user or fully authorized by all parties, and the collection, storage, use, processing, transmission, provision, disclosure and application of relevant data comply with the relevant laws, regulations and standards of relevant countries and regions, take necessary confidentiality measures, do not violate public order and good morals, and provide corresponding operation entrances for users to choose to authorize or refuse.

[0051] It should be noted that the risk control methods, devices, equipment, media and program products provided in the embodiments of the present disclosure can be used in the field of computer technology for risk control, such as terminal misoperation control, and can also be used in various fields outside the field of computer technology, such as the financial field, etc. The application fields of the risk control methods, devices, equipment, media and program products provided by the present disclosure are not limited.

[0052] Figure 1 The application scenario diagram of the risk control method, apparatus, device, medium and program product according to the embodiments of the present disclosure is schematically shown.

[0053] like Figure 1 As shown, the application scenario 100 according to this embodiment may include terminal devices 101, 102, 103, a network 104 and a server 105. The network 104 is used to provide a medium for a communication link between the terminal devices 101, 102, 103 and the server 105. The network 104 may include various connection types, such as wired, wireless communication links or optical fiber cables, etc.

[0054] Users can use terminal devices 101, 102, 103 to interact with server 105 through network 104 to receive or send messages, etc. Various communication client applications can be installed on terminal devices 101, 102, 103, such as shopping applications, web browser applications, search applications, instant messaging tools, email clients, social platform software, etc. (only examples).

[0055] The terminal devices 101, 102, 103 may be various electronic devices having a display screen and supporting web browsing, including but not limited to smart phones, tablet computers, laptop computers, desktop computers, and the like.

[0056] The server 105 may be a server that provides various services, such as a background management server (only an example) that provides support for websites browsed by users using the terminal devices 101, 102, and 103. The background management server may analyze and process the received data such as user requests, and feed back the processing results (such as web pages, information, or data obtained or generated according to user requests) to the terminal device.

[0057] It should be noted that the risk control method provided in the embodiment of the present disclosure can generally be executed by the server 105. Accordingly, the risk control device provided in the embodiment of the present disclosure can generally be set in the server 105. The risk control method provided in the embodiment of the present disclosure can also be executed by a server or server cluster that is different from the server 105 and can communicate with the terminal devices 101, 102, 103 and / or the server 105. Accordingly, the risk control device provided in the embodiment of the present disclosure can also be set in a server or server cluster that is different from the server 105 and can communicate with the terminal devices 101, 102, 103 and / or the server 105.

[0058] It should be understood that Figure 1 The number of terminal devices, networks and servers in the embodiment is only for illustration. Any number of terminal devices, networks and servers may be provided according to the implementation requirements.

[0059] The following will be based on Figure 1 The scene described by Figure 2 to Figure 15 The risk control method of the disclosed embodiment is described in detail.

[0060] Figure 2 The flowchart of the risk control method according to the embodiment of the present disclosure is schematically shown.

[0061] like Figure 2 As shown, the risk control method of this embodiment includes operations S210 to S220, and the risk control method can be executed by the server 105.

[0062] In operation S210, a first operation instruction is acquired.

[0063] In operation S220, execution risk control is performed on the first operation instruction based on risk control parameters, wherein the risk control parameters include an operation count parameter and an operation state parameter.

[0064] According to an embodiment of the present disclosure, the execution risk control of the first operation instruction includes: adjusting the operation count parameter and the operation status parameter based on the execution status of the operation instruction at the current time point, and keeping the number of operation instructions being executed by the current process less than or equal to 1. Among them, the first operation instruction can be derived from the instruction sent when the user operates the terminal to conduct a transaction. The risk control parameter can be a preset variable type and initialized after each process is processed. The initialization value can be preset based on expert experience. For example, an initialization variable clickCount (operation count) can be defined, and the initialization value is set to 0, and the value indicates the number of operations performed by the customer at the current time point. Define an initialization variable isProcessing (whether it is being processed), which indicates the current processing status of the application, and the subsequent process determines the occupancy of the application through this value. And set the initialization value to false, and the value indicates whether an operation instruction is currently being processed (where true means the instruction is being processed, and false means no instruction is being processed).

[0065] Among them, the operation count parameter can be used to determine the number of operation instructions that the current process has received. The operation status parameter can be used to determine whether there is an operation instruction currently being processed. By adjusting the values ​​of the operation count parameter and the operation status parameter, keeping the number of operation instructions being executed by the current process less than or equal to 1, it can be ensured that the next operation instruction is processed only after each valid instruction is processed, thereby ensuring the stability of system operation, reducing the waste of computing resources, and avoiding the risks of system overload, freeze, user mis-touch, etc. that may be caused by the execution of invalid operation instructions.

[0066] Figure 3 The flowchart schematically shows a method for adjusting the operation count parameter and the operation status parameter based on the execution status of the operation instruction at the current time point according to an embodiment of the present disclosure to keep the number of operation instructions being executed by the current process less than or equal to 1.

[0067] like Figure 3 As shown, this embodiment adjusts the operation count parameter and the operation state parameter based on the execution status of the operation instruction at the current time point, and the method of keeping the number of operation instructions being executed by the current process less than or equal to 1 includes at least operations S310 to S330.

[0068] In operation S310, it is determined whether there is a second operation instruction being executed currently based on the operation state parameter.

[0069] When there is no second operation instruction being executed, operation S320 is performed.

[0070] In operation S320, the number of times the operation is executed is determined based on the operation count parameter. When the number of times the operation is executed is not zero, operation S330 is performed.

[0071] In operation S330, the value of the operation count parameter is increased, the first operation instruction is recorded, and the first operation instruction is uploaded to the server.

[0072] According to an embodiment of the present disclosure, when the operation status parameter shows that there is no second operation instruction being executed, it can be further determined whether the current operation execution count is zero. If it is not zero, it means that there is a user operation at the current time point and the instruction is yet to be executed. At this time, the first operation instruction is an invalid instruction that is sent repeatedly and does not need to be executed to reduce the risk of transportation. Furthermore, the value of the operation count parameter can be increased based on the received invalid instruction that is sent repeatedly, that is, the first operation instruction to record the number of operations. By increasing the value of the operation count parameter, it can be further determined in subsequent user operations whether the operation instruction sent by the user is an invalid instruction and whether it needs to be executed. In addition, the first operation instruction can be uploaded to the server for filing for use in case of disputes. It can be understood that the first operation instruction uploaded to the server and other operation instructions will not be executed.

[0073] It can be understood that when the number of execution times of the operation behavior is zero, operation S340 is executed.

[0074] In operation S340, the first operation instruction is executed to change the operation state parameter.

[0075] When the number of times the operation behavior is executed is also zero, it means that there is no valid instruction being processed in the current process. At this time, the first operation instruction can be processed immediately. At the same time, the operation state parameter is changed. For example, the value of isProcessing is changed from false to true for subsequent processing.

[0076] Further, when there is a second operation instruction being executed, operation S350 may be performed.

[0077] In operation S350, wait for the operation execution time, record the first operation instruction, and upload the first operation instruction to the server.

[0078] According to an embodiment of the present disclosure, when other instructions in the process are not processed, the system needs to wait. The operation execution time can be preset based on expert experience. It is understandable that different operation execution times can be preset for different operation types.

[0079] According to some embodiments of the present disclosure, it is also possible to determine whether the first operation instruction is a repeated operation. Among them, the repeated operation usually occurs when the previous process has been processed and has not yet entered the next process. For example, the previous process has been processed, but due to the poor match between the client version and the terminal performance or the old terminal is in a low-performance state, the user does not know that the previous process has been processed. If the user continues to process the user's invalid operation instructions, it is easy to cause a waste of computing resources and the risk of user accidental touch. For example, the next process suddenly jumps, and the user's invalid operation triggers the error processing of the next process.

[0080] Figure 4 The flowchart of the method for processing the first operation instruction of a repeated operation according to an embodiment of the present disclosure is schematically shown.

[0081] like Figure 4 As shown, the method for processing the first operation instruction of the repeated operation in this embodiment includes operations S410 to S420.

[0082] In operation S410, it is determined whether the first operation instruction is a repeated operation instruction.

[0083] When the first operation instruction is a repeat operation instruction, operation S420 is performed.

[0084] In operation S420, wait for the operation execution time, record the first operation instruction, and upload the first operation instruction to the server.

[0085] According to an embodiment of the present disclosure, when the first operation instruction is a repeated operation instruction, the first operation instruction is not executed, and the first operation instruction can be uploaded to the server for filing in preparation for dispute resolution, thereby reducing transaction risks.

[0086] In some specific embodiments of the present disclosure, the determination of whether the first operation instruction is a repeated operation instruction may be performed before entering the main processing flow. For example, operation S410 may be performed before operation S310.

[0087] Figure 5 The flowchart of the method for determining whether the first operation instruction is a repeated operation instruction according to an embodiment of the present disclosure is schematically shown.

[0088] like Figure 5 As shown, the method for determining whether the first operation instruction is a repeated operation instruction in this embodiment at least includes operations S510 to S530.

[0089] In operation S510, it is determined whether the first operation instruction is the first operation of the current process based on the transaction source variable and the transaction information variable.

[0090] When the first operation instruction is not the first operation of the current process, operation S520 is performed.

[0091] In operation S520, it is determined whether the first operation instruction is a homogeneous operation with the previous operation based on the transaction information variable.

[0092] When the first operation instruction and the previous operation are homogeneous operations, operation S530 is performed.

[0093] In operation S530, it is determined based on the operation information variable whether the first operation instruction is a repeated operation with respect to a previous operation.

[0094] According to the embodiment of the present disclosure, whether the first operation instruction is a repeated operation instruction is accurately confirmed based on the first operation judgment - homogeneous operation judgment - repeated operation judgment. In some specific embodiments, it can be first determined whether the first operation instruction is the first operation of the current process. If it is not the first operation, it can be determined whether it is a homogeneous operation with the previous operation by comparing the similarities and differences between the key operation information of the current operation instruction and the previous operation. When the current operation instruction and the previous operation are homogeneous operations, it is further determined whether the current operation and the previous operation are repeated operations by comparing the operation details of the current operation and the previous operation. Among them, the operation information of the previous operation can be the operation information of any operation before the first operation instruction is received after the previous process ends. By confirming whether the first operation instruction is a repeated operation instruction in three stages, the accurate capture of user needs can be further achieved. Further, the last operation information is obtained from the system pre-stored information. It can be understood that several variables can be pre-set and defined in the application to store the relevant information of the last operation, and all subsequent operations of the user on the client. It can be recorded and stored according to the dimensions of each variable, and used for subsequent steps to obtain and judge and compare. In the embodiment of the present disclosure, the variables can mainly include transaction source variables and transaction information variables. The transaction source variable is used to determine the user source of the transaction, the transaction information variable is used to determine the operation behavior of the transaction, and the operation information variable is used to determine the terminal control element of the current operation behavior. The operation behavior of the transaction may include the basic operation elements for executing the transaction, and the terminal control element may include the specific operation details in the operation behavior.

[0095] In some specific embodiments, the transaction source variable includes at least two of the terminal model, the terminal system type, and the application version; and / or, the transaction information variable includes at least two of the operation type, the operation time point, the number of terminal contacts, and the operation mode; and / or, the operation information variable includes at least the contact coordinate position, and the operation information variable also includes at least two of the number of terminal contacts, contact contact pressure, contact contact time, contact control times, and contact sliding distance. In some specific examples, the terminal model can be a mobile phone model, for example, it can include but not limited to common mobile phone brands such as Apple, Xiaomi, Huawei, etc., and the terminal system type can include but not limited to common mobile phone system types on the market, such as iOS, Android, smartisanOS, etc. The application version can include but not limited to mobile client versions, such as XX Bank 1.0 Client, XX Bank 2.0 Client, etc. The operation type can be a common operation type of a mobile terminal, for example, but not limited to click, zoom in, zoom out, slide, etc. The number of terminal contacts can be the number of contacts that a user contacts with the device when operating a mobile terminal, for example, but not limited to single-finger operation, double-finger operation, etc. The operation mode may include the way in which a user contacts the device when operating the mobile terminal, for example, including but not limited to long pressing, pressing hard, double clicking, single clicking, triple clicking, etc.

[0096] According to an embodiment of the present disclosure, before obtaining the operation information of the last operation, a step of obtaining the user's consent or authorization may also be included. For example, before executing operation S510, a request to obtain the user's operation information of the last operation may be issued to the user. When the user agrees or authorizes that the operation information of the last operation may be obtained, the operation S510 is executed.

[0097] It can be understood that when the first operation instruction belongs to the first operation of the current process, or the first operation instruction is not a homogeneous operation of the previous operation, or the first operation instruction is not a repeated operation of the previous operation, the first operation instruction is not a repeated operation instruction. At this time, the risk control processing of the next round of process can be entered.

[0098] Figure 6 The flowchart of the method for first operation judgment according to an embodiment of the present disclosure is schematically shown.

[0099] like Figure 6 As shown, the method for determining the first operation in this embodiment at least includes operations S610 to S640.

[0100] In operation S610, it is determined based on the transaction source variable whether the first operation instruction and the last operation are from the same user.

[0101] When the first operation instruction and the last operation are from the same user, operation S620 is performed.

[0102] In operation S620, a time interval between the first operation instruction and the last operation is calculated based on the operation time point of the first operation instruction and the operation time point of the last operation.

[0103] In operation S630, it is determined whether the time interval between the first operation instruction and the last operation is less than a first threshold.

[0104] When the time interval between the first operation instruction and the last operation is less than the first threshold, operation S640 is performed.

[0105] In operation S640, it is determined whether the first operation instruction is not the first operation of the current process.

[0106] According to the embodiments of the present disclosure, when a user performs an operation, the program automatically obtains the transaction source variable. For example, when the terminal is a mobile phone, the mobile phone model, mobile phone system, client version, etc. can be obtained for comparison to determine whether it is the operation of the same user. Furthermore, it is possible to preferentially judge whether it is the first operation by the operation time information in the transaction information variable. In some preferred embodiments, if the operation time of the first operation instruction is not on the same day as the last operation time or the interval is long, it is considered to be the first operation and not a repeated operation. Among them, the interval time can be set as the first threshold, and whether the first operation instruction is the first operation is determined by comparing whether the time interval between the first operation instruction and the last operation is less than the first threshold.

[0107] Figure 7 The flowchart of the method for determining homogeneous operations according to an embodiment of the present disclosure is schematically shown.

[0108] like Figure 7 As shown, the method for determining the first operation in this embodiment at least includes operations S710 to S720.

[0109] In operation S710, the matching degree between each operation dimension of the first operation instruction and each operation dimension of the previous operation is determined.

[0110] In operation S720, when the matching degree between each operation dimension of the first operation instruction and each operation dimension of the previous operation reaches a preset value, it is determined that the first operation instruction and the previous operation are homogeneous operations.

[0111] According to an embodiment of the present disclosure, a homogeneous operation means that the first operation instruction and the previous operation are the same type of operation. As mentioned above, the transaction information variable may include multiple operation dimensions. Therefore, it is possible to determine whether the two are homogeneous operations based on the matching degree of the first operation instruction and the information of each dimension of the previous operation. In some specific embodiments, it is possible to determine whether the two are homogeneous operations by determining the matching degree of the operation type, operation timing, number of terminal contacts, and operation mode of the two. Specifically, the matching degree value can be calculated through the operation dimension information, and when the matching degree reaches a preset value, it is determined that the two are homogeneous operations.

[0112] In a specific example, the matching degree can be calculated by the assignment method. For example, the operation type, the number of terminal contacts, and the operation mode in each operation dimension are set to 0 or 1. When the two have the same information in one of the above dimensions, the corresponding matching degree calculation parameter is counted as 1, and if they are different, it is counted as 0. Further, the transaction information variable can also include the operation time point, and the value of the operation time point interval between the two can be calculated. When the value is less than or equal to the preset matching degree calculation threshold, the corresponding matching degree calculation parameter is counted as 1, and when it is greater than the preset matching degree calculation threshold, the corresponding matching degree calculation parameter is counted as 0. Further, the matching degree calculation parameters of each operation dimension are summed. When the sum value is greater than the set value, it is considered that the matching degree reaches the preset value, and it is judged that the first operation instruction and the previous operation belong to homogeneous operations. Among them, the set value can be set based on expert experience, for example, it can be set to be the same as the number of operation dimensions. For example, when the above-mentioned operation time point, operation type, number of terminal contacts, and operation mode are used for calculation, the set value can be 4, so that the two operations are judged to be homogeneous operations only when the two operations are almost the same.

[0113] Figure 8 The flowchart of the method for repeated operation judgment according to an embodiment of the present disclosure is schematically shown.

[0114] like Figure 8 As shown, the repeated operation determination method of this embodiment at least includes operations S810 to S820.

[0115] In operation S810, similarities between terminal control elements of the first operation instruction and terminal control elements of a previous operation are calculated based on the multiple control dimensions.

[0116] In operation S820, when the similarity between the terminal control element of the first operation instruction and the terminal control element of the previous operation reaches a second threshold, it is determined that the first operation instruction and the previous operation are repeated operations.

[0117] According to an embodiment of the present disclosure, the similarity of the terminal control elements may be further calculated to determine whether the first operation instruction is a repeated operation with the previous operation.

[0118] Fig. 9 A flowchart of a method for calculating the similarity between a terminal control element of a first operation instruction and a terminal control element of a previous operation according to some specific embodiments of the present disclosure is schematically shown.

[0119] like Fig. 9 As shown, the method of calculating the similarity between the terminal control element of the first operation instruction and the terminal control element of the last operation in this specific embodiment at least includes operation S910.

[0120] In operation S910, similarities of the terminal control elements are calculated based on element similarities of each control dimension and element weights of each control dimension.

[0121] According to an embodiment of the present disclosure, when calculating the similarity of terminal control elements, the element weights of each control dimension can be preset to be the same or different. It is understood that, preferably, the element weights of each control dimension can be preset to be different to achieve accurate capture and determination of user control behavior.

[0122] further, Fig.10 A flowchart of a method for calculating the element similarity of the i-th control dimension according to some specific embodiments of the present disclosure is schematically shown.

[0123] like Fig.10 As shown, the method for calculating the element similarity of the i-th control dimension in this specific embodiment includes operation S9101.

[0124] In operation S9101, the element similarity between the ith control dimension of the first operation instruction and the ith control dimension of the last operation of the current process is calculated based on a preset similarity algorithm. The preset similarity algorithm may include a common similarity algorithm.

[0125] In a specific example, the number of terminal contacts, the coordinate position of the contact points, the number of touch clicks, the size of the contact pressure, the length of contact contact time, and the value of the sliding distance when the operation mode is a sliding operation can be compared between the first operation instruction and the last operation. Because even for the same operation, there will be slight differences in the information of each control dimension. Therefore, a similarity threshold can be set to define the accuracy of judging repeated operations. For example, if the similarity threshold is 80%, then the similarity between this operation and the last operation calculated in the above-mentioned dimensional information is greater than or equal to 80%, then it is considered to be a repeated operation. In a specific example, when calculating the similarity, the scores of the first operation instruction terminal control element and the last operation terminal control element can be calculated based on the weight of the control dimension and the specific assigned scores of each control dimension. The similarity is further calculated based on the scores of the two.

[0126] In some embodiments, when the operation information variable includes the touch point coordinate position, the touch point coordinate position has the highest control dimension element weight. It can be understood that when the user repeats the operation, it often occurs in a short period of time, and the coordinate position of the user and the terminal device operated by the user has a small probability of shifting. Furthermore, the probability of the touch point coordinate position shifting is extremely small.

[0127] According to an embodiment of the present disclosure, before entering into the judgment of whether there is a second operation instruction being executed in the embodiment of the present disclosure, the environmental resource supply status may also be checked to confirm whether there is sufficient environmental resource supply to execute the operation instruction.

[0128] Fig.11 The flowchart of the method for checking the supply status of environmental resources according to an embodiment of the present disclosure is schematically shown.

[0129] like Fig.11 As shown, the method for checking the supply status of environmental resources in this embodiment includes operations S1110 to S1120.

[0130] In operation S1110, the terminal computing resource occupancy rate and the application communication signal strength are checked.

[0131] When both the terminal computing resource occupancy rate and the application communication signal strength meet the preset standard values, operation S1120 is performed.

[0132] In operation S1120, it is determined whether there is a second operation instruction currently being executed based on the operation state parameter.

[0133] According to an embodiment of the present disclosure, before processing an operation instruction, the terminal computing resource occupancy rate and the application communication signal strength can be checked to determine whether the requirements are met. Among them, the order of checking the terminal computing resource occupancy rate and the application communication signal strength can be set randomly. Among them, a typical application communication signal strength may include a network signal strength, and a typical terminal computing resource occupancy rate may include a mobile phone CPU and memory occupancy rate. When the terminal computing resource occupancy rate and the application communication signal strength do not meet the preset standard values, for example, the signal strength is insufficient or the mobile phone CPU and memory occupancy rates exceed the set thresholds, the operation instruction is not executed and a certain time is waited. Among them, the operation time waiting for execution can be equivalent to the instruction execution time, and its specific duration can be customized based on actual needs.

[0134] According to an embodiment of the present disclosure, a check may also be performed after each instruction is executed to ensure the integrity and stability of the system.

[0135] Fig.12The flowchart of the method for resetting the operation count parameter and the operation state parameter according to the embodiment of the present disclosure is schematically shown.

[0136] like Fig.12 As shown, the method for checking after each instruction execution in this embodiment at least includes operations S1210 to S1220.

[0137] In operation S1210, it is checked whether the operation instruction being executed by the current process is executed successfully.

[0138] If the execution is successful, execute operation S1220.

[0139] In operation S1220, the operation count parameter and the operation state parameter are reset.

[0140] According to an embodiment of the present disclosure, if the operation instruction being executed by the current process is executed successfully, the operation count parameter and the operation state parameter can be reset to restore the initial value, thereby achieving risk control for the next operation instruction.

[0141] It can be understood that if the operation instruction being executed by the current process is not executed successfully, operations S1230 to S1240 can be executed.

[0142] In operation S1230, the operation instruction being executed by the current process continues to be processed.

[0143] In operation S1240, the value of the operation count parameter is increased.

[0144] According to an embodiment of the present disclosure, when an operation instruction is not successfully executed, the instruction can be executed again, and the value of the operation count parameter can be increased to terminate the execution of the operation instruction when a trigger condition is reached, thereby avoiding excessive consumption of computing resources.

[0145] Fig.13 The flowchart schematically shows a method for suspending the execution of an operation instruction when a trigger condition is met according to an embodiment of the present disclosure.

[0146] like Fig.13 As shown, the method for terminating the execution of an operation instruction when a trigger condition is met in this embodiment at least includes operations S1310 to S1320.

[0147] In operation S1310, it is determined whether the operation count parameter is greater than or equal to a fourth threshold.

[0148] When the operation count parameter is greater than or equal to the fourth threshold, operation S1320 is performed.

[0149] In operation S1320, the current operation instruction is recorded and uploaded to the server.

[0150] According to an embodiment of the present disclosure, a fourth threshold value can be customized. When the operation count parameter reaches the fourth threshold value, it is considered that the terminal computing resources are fully loaded, for example, performance problems or freezes occur, and subsequent operation instructions will no longer be processed, but only the operation instructions will be recorded and uploaded for filing.

[0151] It can be understood that when the operation count parameter is less than the fourth threshold and there is an operation instruction being executed, operation S1330 can be performed.

[0152] In operation S1330, the operation count parameter continues to be increased.

[0153] Understandably, Fig.13 The method described above may not be limited to determining whether the trigger condition for terminating the execution of the operation instruction is met. The determination of whether the operation count parameter reaches the fourth threshold value may be performed independently.

[0154] The risk control method according to the embodiment of the present disclosure may further include a processing method when the process ends.

[0155] Fig.14 The flowchart schematically shows a method for processing sudden process termination according to an embodiment of the present disclosure.

[0156] like Fig.14 As shown, the method for processing sudden process termination of this embodiment includes operation S1410.

[0157] In operation S1410, when the user exits the current process, the current operation instruction is recorded and uploaded to the server.

[0158] According to an embodiment of the present disclosure, the user exiting the current process may include the user client switching other applications or clearing background processes during the process of performing an operation instruction, that is, the process is suddenly terminated. At this time, switching other applications or clearing background processes is counted as other operations. At this time, other instructions are no longer processed, only the current operation instruction is recorded, and the current operation instruction is uploaded to the server.

[0159] The following combination Fig.15 The following example is only an example of a risk control method of a specific example of an embodiment of the present disclosure. It should be noted that the following example is only an example of a solution to enable those skilled in the art to fully understand the embodiment of the present disclosure, and does not constitute a specific limitation of the present disclosure.

[0160] like Fig.15This example provides a background judgment and control logic for risk control, which can be placed in any business process involving mobile clients, and performs real-time judgment in parallel with the execution thread of the business program. It uses an infinite loop technical solution to judge and control the execution of operation instructions and repeated operations of customers. In the main process, the two variables clickCount (operation count) and isProcessing (whether it is being processed) are preset to represent the current operation status of the customer and the current processing status of the program. When the customer has a new operation, that is, the program receives a new instruction, it is used to obtain the number of customer operation behaviors at a specific time point and the occupancy of the background program. When the number of operations is too large or the background program is occupied, thread control is performed to help the background program avoid high-pressure processing of high-concurrency operations at the same time. Among them, the judgment logic of whether the customer operation is a repeated operation is also added, which is used for preprocessing before the above main process, and preferentially filters out the customer's repeated and invalid operations, reducing the processing pressure of subsequent steps.

[0161] The specific steps and rules are as follows:

[0162] 1. Preset variable: used to introduce a numerical value to represent the customer's current operating status. The subsequent process determines the number of customer behaviors through this value.

[0163] Define an initialization variable clickCount (operation count) and set the original value to 0. The value represents the number of operations performed by the customer at the current time.

[0164] 2. Preset variables: used to introduce a numerical value to indicate the current processing status of the program. Subsequent processes use this value to determine the occupancy of the program.

[0165] Define an initialization variable isProcessing (is it being processed) and set the original value to false. The value indicates whether an operation instruction is currently being processed (true means the instruction is being processed, false means no instruction is being processed).

[0166] 3. Pre-judgment: Before entering the main process, filter out repeated and invalid operations of customers to reduce the processing pressure of subsequent steps, and judge the network signal strength and memory usage to determine the running conditions of the program.

[0167] When the customer performs an operation on the mobile client, an infinite loop is entered.

[0168] 3.1. (This step is involved only when a new instruction is encountered again and a new loop is entered after the overall process is completed. It is not involved when entering for the first time.) After the overall process completes the processing of the previous operation instruction, determine whether the same operation instruction that appears again is a repeated operation. If so, execute step A and no other instructions will be processed at this time; if not, proceed to the next step.

[0169] The method for determining whether the same operation that occurs again is a repeated operation is as follows:

[0170] Defining variables

[0171] Pre-set and define several variables in the program to store the relevant information of the last operation, and record and store all subsequent operations of the customer on the client according to the dimensions of each variable, which will be used for acquisition and judgment comparison in the following steps. There are two aspects of variables. On the one hand, there are variables that determine the source of the transaction, which can be subdivided according to actual needs, such as mobile phone models (Apple, Xiaomi, Huawei, etc.), mobile phone systems (iOS, Android, smartisanOS, etc.), client versions (XX Bank 1.0 Client, XX Bank 2.0 Client, etc.), which are used to determine whether the same customer is operating at a specific time; on the other hand, there are variables that determine the information of the last transaction, which can be subdivided according to actual needs, such as

[0172] The last operation type (click, slide, etc.): lastOperation:={};

[0173] The last touch point number (single-finger operation, double-finger operation): lastTouchPoints = [];

[0174] The last operation time point: lastTimestamp = null;

[0175] The last operation (long press, hard press, etc.) lastActions = [].

[0176] 3.1.2. First operation judgment

[0177] When a customer makes an operation, the program automatically obtains the variables of the transaction source (mobile phone model, mobile phone system, client version, etc.) for comparison to determine whether it is the same customer's operation:

[0178] If not, there is no need to make the following judgment.

[0179] If so, the program automatically obtains the variables of the last transaction information (the last operation type, number of contact points, operation time, operation behavior, etc.) for comparison, and first determines whether it is the first operation based on the operation time information. If it is not the same day as the last operation time or the interval is long, it is considered to be the first operation, not a repeated operation, and directly goes to step 3.2.

[0180] 3.1.3. Homogeneous operation judgment

[0181] If the time interval between the last operation and the last operation is short, continue to compare the operation type, number of contact points, operation time point, and operation behavior to determine whether this operation is the same as the last one. If the various dimensional information is different from the last operation or the difference is large, it is considered to be a non-homogeneous operation and not a repeated operation, and go directly to step 3.2.

[0182] 3.1.4. Repeated operation judgment

[0183] If the dimensional information of the operation is similar to that of the last operation, the operation is judged whether it is repeated. Specifically, the number of touch points, contact point coordinates, number of clicks, pressing force, pressing time, sliding distance and other information of the operation are compared between the operation and the last operation. Since there are slight differences in the dimensional information even for the same operation, a threshold is required to define the accuracy of repeated operation judgment. For example, if the threshold is 80%, the similarity between the operation and the last operation calculated in the above dimensional information is greater than 80%, which is considered a repeated operation. Step A is executed and no instructions are processed at this time.

[0184] 3.2. Before processing an operation instruction, it is necessary to check the network signal strength. If the signal strength is not enough, go to step 6, which is equivalent to processing an operation instruction and waiting for a certain period of time.

[0185] 3.3. Before processing an operation instruction, it is necessary to check the CPU and memory usage of the mobile phone. If it exceeds the set threshold (the bank can define it according to actual needs), go to step 6, which is equivalent to processing an operation instruction and waiting for a certain period of time.

[0186] 4. The program occupancy status is determined by the variable isProcessing (whether it is being processed), that is, whether isProcessing is true, that is, whether an operation instruction is being processed. If it is true, go to step 6; if it is false, go to step 5.

[0187] 5. If it is false, that is, no operation instruction is being processed, the number of customer operation behaviors is determined by clickCount (operation count), that is, whether clickCount is 0. If it is 0, go to step 5.1; if it is not 0, go to step 5.2.

[0188] 5.1. If it is 0, it means that the customer clicks for the first time, then the instruction will be processed immediately, and isProcessing will be set to true, and no other instructions will be processed subsequently.

[0189] 5.2. If it is not 0, execute step B and then step A. No other instructions will be processed at this time.

[0190] 6. If it is true, that is, the operation instruction is being processed, then wait for a certain period of time (which the bank can define according to actual needs). During the waiting period, no other operation instructions will be processed, and step A will be executed.

[0191] 7. Check whether the currently processed operation instruction has been successfully executed.

[0192] 8. If the instruction is executed successfully, return to step 1 and step 2 to reset the values ​​of clickCount and isProcessing, and start receiving and executing subsequent operation instructions; if the instruction fails to be executed, continue to process the same instruction, execute step B at the same time, and enter step 7 to continue to determine whether the instruction is executed successfully.

[0193] 9. (This step is a synchronous and parallel thread outside the overall process) Determine whether the clickCount value has reached a set threshold (the bank can define it according to actual needs). If so, it is considered that the mobile phone has performance problems or is stuck, and subsequent operation instructions will no longer be processed, and step A will be executed. At this time, no instructions will be processed; if not, go to step 10.

[0194] 10. If not, and the customer performs other operations, you only need to increase the value of clickCount.

[0195] 11. (This step is a synchronous and parallel thread outside the overall process) If the customer switches to other applications or clears background processes during the operation instruction, it will be counted as other operations and step A will be executed. No other instructions will be processed at this time.

[0196] Among them, step A is: do not perform other operations and record other operation instructions and upload them to the bank server for record keeping in case of disputes.

[0197] Step B is: increase the value of clickCount.

[0198] Based on the above risk control method, the present disclosure also provides a risk control device. Fig.15 The device is described in detail.

[0199] Fig.16 The structural block diagram of the risk control device according to the embodiment of the present disclosure is schematically shown.

[0200] like Fig.16 As shown, the risk control device 1600 of this embodiment includes an acquisition module 1610 and a risk control module 1620 .

[0201] The acquisition module 1610 is configured to acquire a first operation instruction.

[0202] The risk control module 1620 is configured to perform execution risk control on the first operation instruction based on risk control parameters, wherein the risk control parameters include an operation count parameter and an operation state parameter. The execution risk control on the first operation instruction includes adjusting the operation count parameter and the operation state parameter based on the execution status of the operation instruction at the current time point, so as to keep the number of operation instructions being executed by the current process less than or equal to 1.

[0203] According to an embodiment of the present disclosure, the acquisition module 1610 and the risk control module 1620 can be combined in one module, or one of the modules can be split into multiple modules. Alternatively, at least part of the functions of one or more of these modules can be combined with at least part of the functions of other modules and implemented in one module. According to an embodiment of the present disclosure, at least one of the acquisition module 1610 and the risk control module 1620 can be at least partially implemented as a hardware circuit, such as a field programmable gate array (FPGA), a programmable logic array (PLA), a system on a chip, a system on a substrate, a system on a package, an application-specific integrated circuit (ASIC), or can be implemented by hardware or firmware such as any other reasonable way of integrating or packaging the circuit, or implemented in any one of the three implementation methods of software, hardware and firmware or in any appropriate combination of any of them. Alternatively, at least one of the acquisition module 1610 and the risk control module 1620 can be at least partially implemented as a computer program module, and when the computer program module is run, the corresponding function can be performed.

[0204] Fig.17 A block diagram of an electronic device suitable for implementing a risk control method according to an embodiment of the present disclosure is schematically shown.

[0205] like Fig.17 As shown, the electronic device 900 according to an embodiment of the present disclosure includes a processor 901, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 902 or a program loaded from a storage part 908 into a random access memory (RAM) 903. The processor 901 may include, for example, a general-purpose microprocessor (e.g., a CPU), an instruction set processor and / or a related chipset and / or a special-purpose microprocessor (e.g., an application-specific integrated circuit (ASIC)), etc. The processor 901 may also include an onboard memory for caching purposes. The processor 901 may include a single processing unit or multiple processing units for performing different actions of the method flow according to an embodiment of the present disclosure.

[0206] In RAM 903, various programs and data required for the operation of electronic device 900 are stored. Processor 901, ROM 902 and RAM 903 are connected to each other via bus 904. Processor 901 performs various operations of the method flow according to the embodiment of the present disclosure by executing the program in ROM 902 and / or RAM 903. It should be noted that the program can also be stored in one or more memories other than ROM 902 and RAM 903. Processor 901 can also perform various operations of the method flow according to the embodiment of the present disclosure by executing the program stored in the one or more memories.

[0207] According to an embodiment of the present disclosure, the electronic device 900 may further include an input / output (I / O) interface 905, which is also connected to the bus 904. The electronic device 900 may further include one or more of the following components connected to the I / O interface 905: an input portion 906 including a keyboard, a mouse, etc.; an output portion 907 including a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker, etc.; a storage portion 908 including a hard disk, etc.; and a communication portion 909 including a network interface card such as a LAN card, a modem, etc. The communication portion 909 performs communication processing via a network such as the Internet. A drive 910 is also connected to the I / O interface 905 as needed. A removable medium 911, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed on the drive 910 as needed, so that a computer program read therefrom is installed into the storage portion 908 as needed.

[0208] The present disclosure also provides a computer-readable storage medium, which may be included in the device / apparatus / system described in the above embodiments; or may exist independently without being assembled into the device / apparatus / system. The above computer-readable storage medium carries one or more programs, and when the above one or more programs are executed, the method according to the embodiment of the present disclosure is implemented.

[0209] According to an embodiment of the present disclosure, a computer-readable storage medium may be a non-volatile computer-readable storage medium, for example, may include but is not limited to: a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination thereof. In the present disclosure, a computer-readable storage medium may be any tangible medium containing or storing a program, which may be used by or in combination with an instruction execution system, an apparatus, or a device. For example, according to an embodiment of the present disclosure, a computer-readable storage medium may include the ROM 902 and / or RAM 903 described above and / or one or more memories other than ROM 902 and RAM 903.

[0210] The embodiment of the present disclosure also includes a computer program product, which includes a computer program, and the computer program contains program code for executing the method shown in the flowchart. When the computer program product is run in a computer system, the program code is used to enable the computer system to implement the item recommendation method provided by the embodiment of the present disclosure.

[0211] The above functions defined in the system / device of the embodiment of the present disclosure are performed when the computer program is executed by the processor 901. According to the embodiment of the present disclosure, the system, device, module, unit, etc. described above can be implemented by a computer program module.

[0212] In one embodiment, the computer program may be based on a tangible storage medium such as an optical storage device, a magnetic storage device, etc. In another embodiment, the computer program may also be transmitted and distributed in the form of a signal on a network medium, and downloaded and installed through the communication part 909, and / or installed from a removable medium 911. The program code contained in the computer program may be transmitted using any appropriate network medium, including but not limited to: wireless, wired, etc., or any suitable combination of the above.

[0213] In such an embodiment, the computer program can be downloaded and installed from the network through the communication part 909, and / or installed from the removable medium 911. When the computer program is executed by the processor 901, the above functions defined in the system of the embodiment of the present disclosure are performed. According to the embodiment of the present disclosure, the system, device, means, module, unit, etc. described above can be implemented by a computer program module.

[0214] According to an embodiment of the present disclosure, the program code for executing the computer program provided by the embodiment of the present disclosure can be written in any combination of one or more programming languages. Specifically, these computing programs can be implemented using high-level process and / or object-oriented programming languages, and / or assembly / machine languages. Programming languages ​​include, but are not limited to, Java, C++, python, "C" language or similar programming languages. The program code can be executed entirely on the user computing device, partially on the user device, partially on the remote computing device, or entirely on the remote computing device or server. In the case of a remote computing device, the remote computing device can be connected to the user computing device through any type of network, including a local area network (LAN) or a wide area network (WAN), or can be connected to an external computing device (for example, using an Internet service provider to connect through the Internet).

[0215] The flow charts and block diagrams in the accompanying drawings illustrate the possible architecture, functions and operations of the systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each box in the flow chart or block diagram can represent a module, a program segment, or a part of a code, and the above-mentioned module, program segment, or a part of a code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a different order from the order marked in the accompanying drawings. For example, two boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram or flow chart, and the combination of the boxes in the block diagram or flow chart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0216] It will be appreciated by those skilled in the art that the features described in the various embodiments and / or claims of the present disclosure may be combined and / or combined in a variety of ways, even if such combinations and / or combinations are not explicitly described in the present disclosure. In particular, the features described in the various embodiments and / or claims of the present disclosure may be combined and / or combined in a variety of ways without departing from the spirit and teachings of the present disclosure. All of these combinations and / or combinations fall within the scope of the present disclosure.

[0217] The embodiments of the present disclosure are described above. However, these embodiments are only for illustrative purposes and are not intended to limit the scope of the present disclosure. Although the embodiments are described above separately, this does not mean that the measures in the various embodiments cannot be used in combination to advantage. The scope of the present disclosure is defined by the attached claims and their equivalents. Without departing from the scope of the present disclosure, those skilled in the art may make a variety of substitutions and modifications, which should all fall within the scope of the present disclosure.

Claims

1. A risk control method, characterized in that: include: Obtaining a first operation instruction; as well as performing execution risk control on the first operation instruction based on risk control parameters, wherein the risk control parameters include an operation count parameter and an operation state parameter, The performing of execution risk control on the first operation instruction includes: The operation count parameter and the operation status parameter are adjusted based on the execution status of the operation instruction at the current time point, so as to keep the number of operation instructions being executed by the current process less than or equal to 1.

2. According to the method of claim 1, the adjusting the operation count parameter and the operation status parameter based on the execution status of the operation instruction at the current time point to keep the number of operation instructions being executed by the current process less than or equal to 1 comprises: Determining whether there is a second operation instruction currently being executed based on the operation status parameter; as well as When there is no second operation instruction being executed, determining the number of times the operation is executed based on the operation count parameter, When the number of executions of the operation is not zero, the value of the operation count parameter is increased, the first operation instruction is recorded, and the first operation instruction is uploaded to the server.

3. The method according to claim 2, wherein: When the number of executions of the operation behavior is zero, the first operation instruction is executed to change the operation state parameter.

4. The method according to claim 2, wherein: When there is a second operation instruction being executed, the method includes: Waiting for the operation execution time, recording the first operation instruction, and uploading the first operation instruction to the server.

5. The method according to claim 1 or 2, wherein: The performing execution risk control on the first operation instruction further includes: determining whether the first operation instruction is a repeated operation instruction; and When the first operation instruction is a repeated operation instruction, wait for the operation execution time, record the first operation instruction, and upload the first operation instruction to the server.

6. The method according to claim 5, wherein: The determining whether the first operation instruction is a repeated operation instruction comprises: Determining whether the first operation instruction is the first operation of the current process based on the transaction source variable and the transaction information variable; Wherein, when the first operation instruction is not the first operation of the current process, the method further includes: Determining whether the first operation instruction is a homogeneous operation with the previous operation based on the transaction information variable; Wherein, when the first operation instruction and the previous operation are homogeneous operations, the method further includes: Based on the operation information variable, it is determined whether the first operation instruction is a repeated operation with the previous operation, The transaction source variable is used to determine the user source of the transaction, the transaction information variable is used to determine the operation behavior of the transaction, and the operation information variable is used to determine the terminal control element of the current operation behavior. The operation information of the last operation is obtained from system pre-stored information.

7. The method according to claim 6, wherein: The transaction information variable at least includes an operation time point, and the determining whether the first operation instruction is the first operation of the current process based on the transaction source variable and the transaction information variable includes: Determining whether the first operation instruction and the last operation are from the same user based on the transaction source variable; When the first operation instruction and the last operation are from the same user, calculating the time interval between the first operation instruction and the last operation based on the operation time point of the first operation instruction and the operation time point of the last operation; Determining whether the time interval between the first operation instruction and the last operation is less than a first threshold; and When the time interval between the first operation instruction and the last operation is less than a first threshold, it is determined that the first operation instruction is not the first operation of the current process.

8. The method according to claim 6, wherein: The transaction information variable includes multiple operation dimensions, and judging whether the first operation instruction is a homogeneous operation with the previous operation based on the transaction information variable includes: Determining the matching degree between each operation dimension of the first operation instruction and each operation dimension of the previous operation; and When the matching degree between each operation dimension of the first operation instruction and each operation dimension of the previous operation reaches a preset value, it is determined that the first operation instruction and the previous operation are homogeneous operations.

9. The method according to claim 6, wherein: The operation information variable includes multiple control dimensions, and judging whether the first operation instruction is a repeated operation with the previous operation based on the operation information variable includes: Calculating the similarity between the terminal control element of the first operation instruction and the terminal control element of the last operation based on the multiple control dimensions; and When the similarity between the terminal control element of the first operation instruction and the terminal control element of the previous operation reaches a second threshold, it is determined that the first operation instruction and the previous operation are repeated operations.

10. The method according to claim 9, wherein: The calculating, based on the multiple control dimensions, the similarity between the terminal control element of the first operation instruction and the terminal control element of the last operation includes: The similarity of the terminal control elements is calculated based on the element similarity of each control dimension and the element weight of each control dimension, Among them, the calculation method of the element similarity of the i-th control dimension includes: The element similarity between the i-th control dimension of the first operation instruction and the i-th control dimension of the previous operation of the current process is calculated based on a preset similarity algorithm.

11. The method according to claim 6, wherein: The transaction source variables include at least two of the terminal model, terminal system type, and application version; and / or, the transaction information variables include at least two of the operation type, operation timing, number of terminal contacts, and operation mode; and / or, the operation information variables include at least the contact coordinate position, and the operation information variables also include at least two of the number of terminal contacts, contact contact pressure, contact contact time, number of contact controls, and contact sliding distance.

12. The method according to claim 10 or 11, wherein: When the operation information variable includes a touch point coordinate position, the touch point coordinate position has the highest control dimension element weight.

13. The method according to claim 2, wherein: The method further comprises: Check terminal computing resource utilization and application communication signal strength; and When both the terminal computing resource occupancy rate and the application communication signal strength meet preset standard values, it is determined whether there is a second operation instruction currently being executed based on the operation state parameter.

14. The method according to claim 1 or 2, wherein: The method further comprises: Check whether the operation instruction being executed by the current process is executed successfully. If the execution is successful, the operation count parameter and the operation status parameter are reset.

15. The method according to claim 14, wherein: If the execution is unsuccessful, the method further comprises: Continue to process the operation instruction being executed by the current process; Increments the value of the operation count parameter.

16. The method according to claim 2, wherein: The method further comprises: determining whether the operation count parameter is greater than or equal to a fourth threshold, When the operation count parameter is greater than or equal to a fourth threshold, the current operation instruction is recorded and uploaded to a server.

17. The method according to claim 2, wherein: The method further comprises: When the user exits the current process, the current operation instruction is recorded and uploaded to the server.

18. A risk control device, characterized in that: include: An acquisition module, configured to acquire a first operation instruction; as well as a risk control module, configured to perform execution risk control on the first operation instruction based on risk control parameters, wherein the risk control parameters include an operation count parameter and an operation state parameter, The performing of execution risk control on the first operation instruction includes: The operation count parameter and the operation status parameter are adjusted based on the execution status of the operation instruction at the current time point, so as to keep the number of operation instructions being executed by the current process less than or equal to 1.

19. An electronic device comprising: one or more processors; a storage device for storing one or more programs, When the one or more programs are executed by the one or more processors, the one or more processors are enabled to execute the method according to any one of claims 1 to 17.

20. A computer-readable storage medium having executable instructions stored thereon, which, when executed by a processor, causes the processor to perform the method according to any one of claims 1 to 17.

Images