CN111784119A - Risk control strategy migration method, strategy package generation method and device - Google Patents

Abstract

This specification provides a risk control strategy migration method, a strategy package generation method, and an apparatus. The migration method first obtains a risk control strategy package generated by a strategy provider. The risk control strategy package includes multiple strategy information and index relationship information between the multiple strategy information. Then, based on the index relationship information, the multiple strategy information is imported into the target risk control system to run the target strategy rule in the target risk control system and control the risk of the target type.

Description

Risk control strategy migration method, strategy package generation method and device

technical field

The embodiments of this specification relate to the technical field of risk control, and in particular, to a method for migrating a risk control strategy, a method for generating a strategy package, and an apparatus.

Background technique

With the development of Internet technology, more and more businesses can be processed online, such as transfers and payments, which greatly facilitates the work and life of users. However, while enjoying the convenience, it also faces various risks, which also puts forward high requirements for the risk control system of the network business platform. It is necessary to deploy a large number of risk control policy rules in the risk control system. In order to deal with the risks that may exist in the process of business processing.

SUMMARY OF THE INVENTION

The embodiments of this specification provide a method for migrating a risk control strategy, a method for generating a strategy package, and an apparatus.

In a first aspect, an embodiment of this specification provides a method for migrating a risk control strategy, including: acquiring a risk control strategy package, where the risk control strategy package includes: a plurality of strategy information and an index relationship between the plurality of strategy information information, the multiple policy information includes target policy rules, variables configured by the target policy rules, and parameters configured by the variables; according to the index relationship information, the multiple policy information is imported into the target risk control system, to run the target policy rule in the target risk control system.

In a second aspect, the embodiments of this specification provide a method for generating a risk control strategy package, which is used to generate the risk control strategy package described in the method for migrating a risk control strategy provided in the first aspect. The method includes: in response to a policy package generation instruction triggered by a user, determining a target policy rule in the first risk control system, where the target policy rule is used to identify the risk of the target type; based on a preset data blood relationship information database, obtain The index relationship information of the target policy rule; according to the index relationship information, determine the configuration information of the target policy rule, the configuration information includes: the variable configured by the target policy rule and the parameter configured by the variable; The target policy rule, the configuration information of the target policy rule, and the index relationship information are derived from the first risk control system to generate the risk control policy package, which is used to import the second risk control policy package. The risk control system controls the risk of the target type.

In a third aspect, the embodiments of this specification provide a method for migrating a risk control strategy, including: in response to a strategy package generation instruction triggered by a user, determining a target strategy rule in the first risk control system, where the target strategy rule is used to identify The risk of the target type; based on the preset data blood relationship information database, the index relationship information of the target policy rule is obtained, and according to the index relationship information, the configuration information of the target policy rule is determined, and the configuration information includes: The variable configured by the target policy rule and the parameter configured by the variable; the target policy rule, the configuration information of the target policy rule and the index relationship information are derived from the first risk control system to generate a risk control system. strategy package; in response to the strategy package import instruction triggered by the user, according to the index relationship information in the risk control strategy package, import the target strategy rule and the configuration information of the target strategy rule into the second risk control system , to run the target policy rule in the second risk control system.

In a fourth aspect, an embodiment of this specification provides an apparatus for migrating a risk control strategy, including: an acquisition module configured to acquire a risk control strategy package, where the risk control strategy package includes: a plurality of strategy information and the plurality of strategy information The index relationship information between them, the multiple policy information includes target policy rules, variables configured by the target policy rules, and parameters configured by the variables; an import module is used to import the multiple policy information according to the index relationship information. Each policy information is imported into the target risk control system to run the target policy rules in the target risk control system.

In a fifth aspect, the embodiments of this specification provide a device for generating a risk control strategy package, which is used to generate the risk control strategy package described in the method for migrating a risk control strategy provided in the first aspect. The device includes: a rule determination module , for determining the target policy rule in the first risk control system in response to the policy package generation instruction triggered by the user, and the target policy rule is used to identify the risk of the target type; the relationship information acquisition module is used for based on preset data. A blood relationship information base, to obtain the index relationship information of the target policy rule; a configuration information acquisition module, configured to determine the configuration information of the target policy rule according to the index relationship information, and the configuration information includes: the target policy rule The configured variable and the parameter configured by the variable; the export module is used to export the target policy rule, the configuration information of the target policy rule and the index relationship information from the first risk control system, and generate the The risk control strategy package is used to import the second risk control system to prevent and control the risk of the target type.

In a sixth aspect, the embodiments of this specification provide an apparatus for migrating a risk control strategy, including: a strategy package export module, configured to determine a target strategy rule in the first risk control system in response to a strategy package generation instruction triggered by a user, so that the The target policy rule is used to identify the risk of the target type; based on a preset data lineage information database, the index relationship information of the target policy rule is obtained, and according to the index relationship information, the configuration information of the target policy rule is determined, The configuration information includes: the variable configured by the target policy rule and the parameter configured by the variable; Export in the system to generate a risk control strategy package; a strategy package import module is used to, in response to a strategy package import instruction triggered by the user, according to the index relationship information in the risk control strategy package, import the target strategy rules and all The configuration information of the target policy rule is imported into the second risk control system to run the target policy rule in the second risk control system.

In a seventh aspect, the embodiments of this specification provide an electronic device, including: a memory, a processor, and a computer program stored in the memory and running on the processor, the processor implementing the above-mentioned first program when the processor executes the program Steps of the method for migrating a risk control strategy provided by the aspect, the method for generating a strategy package provided by the second aspect, or the method for migrating the risk control strategy provided by the third aspect.

In an eighth aspect, the embodiments of this specification provide a computer-readable storage medium on which a computer program is stored, and when the program is executed by a processor, implements the risk control strategy migration method provided in the first aspect, and the method provided in the second aspect. The steps of the strategy package generation method or the risk control strategy migration method provided by the third aspect.

In the method for generating a risk control strategy package provided by an embodiment of this specification, a target strategy rule is determined from a first risk control system, and then based on a preset data lineage information database, the index relationship information of the target strategy rule is obtained, and then based on the index relationship information, determine the configuration information of the target policy rules, and then package the target policy rules, the configuration information of the target policy rules, and their index relationship information together into a risk control policy package, which can be quickly exported from the risk control system. In this way, the policy rules, the configuration information of the policy rules, and the index relationship information can exist together as an independent file, and can be transferred out of the system, which is conducive to realizing the cross-system application of the risk control policy rules.

Further, in the method for migrating a risk control strategy provided by an embodiment of this specification, by acquiring a risk control strategy package, the risk control strategy package includes a plurality of strategy information and index relationship information between the plurality of strategy information, and the plurality of strategy information includes The target policy rule, the variable configured by the target policy rule, and the parameter configured by the variable, and then according to the index relationship information, the above-mentioned multiple policy information is imported into the target risk control system, so as to run the target policy rule in the target risk control system, Risk control of the target type of risk. By importing the risk control strategy package, which is separated from the original risk control system and exists as an independent file, into the target risk control system, the cross-system application of the risk control strategy rules is effectively realized, and the user can quickly complete the risk control within 1 day. The introduction of the strategy package does not require the participation of professionals with risk operation experience, which effectively improves the deployment efficiency of risk control strategies and reduces labor costs.

Description of drawings

FIG. 1 is a schematic diagram of an application scenario provided by an embodiment of this specification;

FIG. 2 is a flowchart of a method for generating a risk control strategy package according to the first aspect of the embodiment of the present specification;

FIG. 3 is a schematic diagram of a layer-by-layer dependency relationship of a policy rule provided by the first aspect of the embodiment of the present specification;

4 is a flowchart of a method for migrating a risk control strategy according to the second aspect of the embodiment of the present specification;

FIG. 5 is a flowchart of a method for migrating a risk control strategy provided by the third aspect of the embodiment of the present specification;

6 is a block diagram of a module of an apparatus for generating a risk control strategy package provided by the fourth aspect of the embodiment of the present specification;

FIG. 7 is a block diagram of a module of an apparatus for migrating a risk control strategy provided by the fifth aspect of the embodiment of the present specification;

8 is a block diagram of a module of an apparatus for migrating a risk control strategy provided by the sixth aspect of the embodiment of the present specification;

FIG. 9 is a schematic structural diagram of an electronic device according to a seventh aspect of an embodiment of the present specification.

Detailed ways

With the increasing diversification of network services, the requirements for risk control systems are getting higher and higher, and a large number of risk control strategies need to be configured to identify various risks and ensure the normal operation of business systems. However, for some small network platforms, it is impossible to invest a lot of manpower and financial resources to develop their own risk control engines, and they need to purchase relevant risk control products from third-party platforms. Considering that the buyer's early risk operation capability after purchasing the product is relatively weak, in order to help the buyer quickly start the risk operation, the product side will dispatch professionals with risk operation experience to deploy the risk control strategy for the buyer. As the risk control strategy is a refined risk operation configuration, there are many layers of information, and the layer-by-layer verification and dependencies are complex. The deployment of the risk control strategy needs to rely on professionals, which consumes about 10-20 person-days (that is, one person does 10-20 person-days). working days), low efficiency, high labor costs, and inability to serve multiple buyers at the same time.

In view of this, the embodiments of this specification provide a method for generating a risk control strategy package, by determining the target strategy rule from the first risk control system, and then obtaining the index relationship information of the target strategy rule based on a preset data lineage information database. According to the obtained index relationship information, determine the configuration information of this target policy rule, including: the variable of the target policy rule configuration and the parameter of the variable configuration, then the above-mentioned target policy rule, the configuration information of the target policy rule and the index relationship information Export from the first risk control system to generate a risk control strategy package. In this way, the risk control strategy package can be independently applied to other second risk control systems different from the first risk control system to prevent and control the risks of target types in the second risk control system.

Further, the embodiments of this specification also provide a method for migrating a risk control strategy. By first acquiring a risk control strategy package, the risk control strategy package includes: a plurality of strategy information and index relationship information between the plurality of strategy information. The multiple policy information includes target policy rules, variables configured by the target policy rules, and parameters configured by the variables, and the target policy rules are used to identify the risk of the target type; then, according to the index relationship information, import the above multiple policy information into the target The risk control system runs the target policy rules in the risk control policy package in the target risk control system to prevent and control the risks of the target type.

With the method for generating a risk control policy package provided by the embodiments of this specification, a policy rule of a certain risk type can be made into a policy package and quickly derived from the risk control system, so that the policy rule, the configuration information of the policy rule and the index of the policy rule The relationship information exists together as an independent file, and can be migrated between multiple independent systems without the system, which is conducive to the realization of cross-system application of risk control policy rules. Further, through the risk control strategy migration method provided in the embodiments of this specification, the risk control strategy package that is separated from the original risk control system is imported into the target risk control system, so as to realize the cross-system application of the risk control strategy rules. In this way, the risk control strategy package of the corresponding risk type can be exported according to the user's needs and provided to the user. The user can quickly complete the import of the risk control strategy package within one person-day (that is, one person within one working day) without risk. The participation of professionals with operational experience can effectively improve the deployment efficiency of risk control strategies and reduce labor costs. In addition, the same risk control strategy package can be provided to multiple different users, helping multiple users to deploy risk control strategies at the same time, improving deployment efficiency.

It should be noted that the risk control strategy package proposed in the embodiments of this specification is an executable strategy rule used for risk identification, and a set of information such as variables, accumulated strategies, and parameters that the strategy rules depend on. The risk control strategy package can exist and transfer separately from the risk control system, and exists in the form of an independent file. The blood relationship information refers to the associated index information of each layer of information in the policy package, which can express the index calling relationship between policy rules, variables, and other information.

FIG. 1 shows a schematic diagram of an exemplary application scenario provided by an embodiment of this specification. In FIG. 1 , the strategy provider 100 is configured with a first risk control system and a risk control strategy package generation device, and the risk control strategy package generation device is used to implement the wind control strategy package generation method provided by the embodiments of this specification in the following first aspect. The strategy The demand side 101 is configured with a second wind control system and a wind control strategy migration device, and the wind control strategy migration device is used to implement the wind control strategy migration method provided by the embodiments of this specification in the following second aspect. The first wind control system and the second wind control system are different and independent wind control systems. Target policy rules are deployed in the first risk control system to identify the risks of target types. The policy provider 100 can, through the configured risk control policy package generating device, be triggered by relevant personnel from the first risk control system. Export the risk control policy package of the target policy rule, which is used to deploy the target policy rule in other risk control systems. For example, as shown in FIG. 1 , if the policy provider 100 provides the exported risk control policy package to the policy demander 101 in need, the policy demander 101 can import the risk control policy package into the second via the risk control policy migration device. The risk control system enables the target policy rules in the risk control policy package to run online in the second risk control system 101 to prevent the risk of the target type.

It should be noted that, in the embodiment of this specification, the policy provider 100 and the policy demander 101 are different devices, for example, a server or a terminal device. In addition, the policy provider can provide the generated risk control policy package to one or more different policy demanders. The number of policy demanders shown in FIG. 1 is for illustration only, and can be determined according to the actual application scenario. limit.

In order to better understand the technical solutions provided by the embodiments of the present specification, the technical solutions of the embodiments of the present specification will be described in detail below with reference to the accompanying drawings and specific embodiments. The detailed description of the technical solutions of the embodiments is not a limitation on the technical solutions of the present specification, and the embodiments of the present specification and the technical features in the embodiments may be combined with each other under the condition of no conflict.

In a first aspect, FIG. 2 shows a flowchart of a method for generating a risk control strategy package provided by an embodiment of this specification. The method for generating a risk control policy package is applied to a policy provider, please refer to FIG. 2 , and the method may at least include the following steps S200 to S206 .

Step S200, in response to a policy package generation instruction triggered by the user, determine a target policy rule in the first risk control system, where the target policy rule is used to identify the risk of the target type.

After the user, that is, the operator of the first risk control system, executes the operation for triggering the strategy package generation instruction, the strategy package generation process from steps S200 to S206 can be started. For example, in an application scenario, an export button for triggering the policy package generation instruction may be displayed on the user interface preconfigured in the policy provider, and the user clicks the export button to trigger the policy package generation instruction. Of course, in other embodiments of this specification, the policy package generation instruction may also be triggered in other ways, which is not limited here.

Before generating the risk control policy package, you need to determine the target policy rules. The target policy rule is the policy rule that needs to generate the risk control policy package. Policy rules (Rule) are rules that run in the risk control system to identify risks. They are usually composed of comparators and variables. For example, a policy rule is that if account A has logged in more than M times in a day, account A will be determined. There is a risk.

In the embodiments of this specification, there are various implementations for determining the target policy rule, and three exemplary implementations are mainly listed below for description.

First, the user can select a policy rule in the policy rule base of the first risk control system, and use the policy rule selected by the user as the target policy rule.

Second, the user can enter the risk type, that is, the target type, on the user interface preconfigured in the policy provider, query the policy rule matching the risk type in the first risk control system, and use the matching policy rule as the target policy rule. Alternatively, there are multiple matching policy rules, and the user can select one or more of them as the target policy rule. It should be noted that, if there are multiple target policy rules determined, a corresponding risk control policy package may be separately generated for each target policy rule.

Third, the policy provider can receive the risk control policy request sent by the policy demander online, and the risk control policy request includes information such as the identity information of the control policy demander and the risk type. After identifying the risk control policy request, the policy provider can create a policy package generation task based on the risk control policy request, and display it in the task list on the pre-configured user interface. The task list may include not only the strategy package generation task, but also the status of the strategy package generation task. For example, the status type may include completed, unprocessed, and being processed. In this way, the user can know the completion status of each task through the task list, and select an unprocessed task to trigger a policy package generation instruction for the task. Take the risk type contained in the task as the target type, match the risk type corresponding to the policy rule in the system, use the matched policy rule as the target policy rule, generate the corresponding risk control policy package, and feed it back to the policy demand side. Also, update the status of the task in the task list to Completed.

Step S202 , based on a preset data lineage information database, obtain the index relationship information of the target policy rule.

In the process of using policy rules to identify risks, the calculation of policy rules needs to determine the configuration information of the policy rules first. It can be understood that the configuration information of the policy rule may include: variables configured by the policy rule and parameters configured by the variables. Among them, the parameters are used to encapsulate the attribute data sent by the upstream system. To calculate policy rules, it is necessary to calculate the values of these configuration information layer by layer to calculate the final policy rules to give risk control decisions. For example, a policy rule is: when user ID="123", the user is considered to be a whitelisted user, then the variable configured in the policy rule is: user ID, and the parameter configured in this variable is the parameter passed in from the upstream system The user ID value parsed from the attribute data.

Of course, in addition to the above-mentioned basic information, the configuration information of the policy rule may also include other information, which needs to be determined according to the specific policy rule. For example, in an application scenario, the configuration information of the target policy rule includes, in addition to the variables configured by the policy rule and parameters configured by the variables, the cumulative policy configured by the variable, and the variables and parameters configured by the cumulative policy. In the embodiment of this specification, the accumulation strategy is used to count the historical behavior data of the user. For example, statistics of user history login time details, etc.

FIG. 3 shows a schematic diagram of an exemplary layer-by-layer dependency relationship between a policy rule and its configuration information. As shown in Figure 3, the policy rule (Rule) depends on the variable (Variable), the variable (Variable) depends on the parameter (Parameter) and the accumulation policy (velocity), and the accumulation policy (velocity) depends on the parameter and the variable. Of course, the layer-by-layer dependency shown in FIG. 3 is only for illustration, and the specific layer-by-layer dependency needs to be determined according to the actual target policy rules.

For example, a policy rule determines that the user is an inactive user when the number of logins in seven days is 0. Then, the variable configured in this policy rule is: the number of logins of the user in seven days, and the variable is configured with a cumulative policy of: Count the details of the user's historical login time, and configure the parameter: user ID. After the user ID is passed in from the upstream system, the user ID can be passed into the cumulative policy information level configured by the policy rule, trigger the cumulative policy to query the historical login time details of the user ID, calculate the number of logins for the user ID within seven days, and then calculate the result. Assign values to the above variables, and then the policy rules can be calculated to give risk control decisions.

For another example, if a policy rule needs to count the number of logins of users in area S in one day, the variables configured in the policy rule include: variable V1: area S, and variable V2: the number of logins of users in area S in one day. Among them, the variable V2 is configured with an accumulation strategy used to count the details of the user's historical login time in the area S, and the accumulation strategy depends on the variable V1, that is, the accumulation strategy is configured with preconditions, that is, if the If the current region of the user ID is in region S, the cumulative policy statistics will be triggered. If the current region of the incoming user ID is not in region S, the cumulative policy statistics will not be triggered. Calculate the number of login times of users in area S in one day based on the statistical result of the accumulated policy, and assign it to the variable V2 to calculate the final policy rule.

It can be understood that there is an index relationship between the policy rules and the configuration information of the policy rules. For example, policy rule R depends on variable 1 and variable 2, variable 2 depends on parameter P and accumulation policy T, and accumulation policy T depends on variable 1 and parameter P, then, from the top policy rule R to the bottom parameter P The layer-by-layer dependency relationship of each information level is the index relationship information of the policy rule.

In order to facilitate obtaining the index relationship information of the policy rules included in the first risk control system, a data lineage information database may be pre-configured for the policy rules in the first risk control system. Specifically, when the information of the policy rule is created layer by layer, an index association relationship, that is, a blood relationship, can be constructed for it, and the constructed index association relationship and the identification information of the policy rule can be correspondingly stored in the data blood relationship information database. In this way, the data lineage information database stores the index relationship information of each policy rule in the first risk control system, so that in the process of generating the policy package, after the target policy rule is determined, the target can be searched and obtained from the data lineage information database. The index relationship information of the policy rule, and then the following step S204 is performed.

Step S204: Determine the configuration information of the target policy rule according to the index relationship information.

According to the index relationship information of the target policy rule, the information of each information level on which the target policy rule is calculated can be sorted out, that is, the configuration information of the target policy rule, which can include the variables configured by the target policy rule, the parameters configured by the variable, and the accumulation policy. , as well as the variables and parameters of the cumulative policy configuration, etc.

Step S206, exporting the target policy rule, the configuration information of the target policy rule and the index relationship information from the first risk control system to generate a risk control policy package, and the risk control policy package is used to import the risk of the second risk control system to the target type control.

After determining the target policy rule and the configuration information of the target policy rule, package and export these information together with the index relationship information of the target policy rule, and then a complete risk control policy package can be generated. The risk control strategy package is an independent file that can be imported into the second risk control system, so that the target strategy rules in the risk control strategy package can be run in the second risk control system to identify the risks of the target type.

It can be understood that if there is a sequential dependency relationship between the policy rules and the configuration information of the policy rules, they must be created layer by layer according to the dependency relationship when deploying the policy rules to ensure the normal operation of the policy rules. The index relationship information contained in the risk control policy package can play the role of checking and sorting the imported information when importing the policy package, so as to ensure that the import of policy rules and configuration information of policy rules can be completed with one file.

The method for generating a risk control policy package provided by the embodiments of this specification can make policy rules into policy packages and quickly export them from the risk control system, so that policy rules, configuration information of policy rules, and index relationship information can be regarded as an independent file. It exists and can be migrated between multiple independent systems without the system, which is conducive to realizing the cross-system application of risk control policy rules and improving the deployment efficiency of risk control policies.

In the second aspect, FIG. 4 shows a flowchart of a method for migrating a risk control strategy provided by an embodiment of the present specification. The risk control policy migration method is applied to the policy demand side, please refer to FIG. 4 , the method may at least include the following steps S400 to S402.

Step S400, obtaining a risk control strategy package, where the risk control strategy package includes: a plurality of strategy information and index relationship information between the plurality of strategy information, where the plurality of strategy information includes a target strategy rule, a variable configured by the target strategy rule, and a variable Configured parameters.

In the embodiments of this specification, the risk control system that needs to deploy target policy rules is the target risk control system, and the risk control policy package is derived from other risk control systems different from the target risk control system. For example, the risk control strategy package can be obtained offline by the relevant personnel at the strategy demand side from the strategy provider side, and then uploaded to the target risk control system, or the strategy provider side can also generate the corresponding risk control strategy requirements according to the risk control strategy requirements sent by the strategy demand side. After creating the risk control strategy package, it will be fed back to the strategy demand side online, and then uploaded to the target risk control system by the relevant personnel, which is not limited here. For the specific generation process of the risk control strategy package, reference may be made to the content of the method embodiment provided in the first aspect, and details are not described herein again.

For example, in an application scenario, the policy demand side requests help from the policy provider side when encountering risks; the policy operator at the policy provider side derives the risk control policy package according to the corresponding risk type and according to the policy package generation method provided in the first aspect above. , and then deliver the risk control strategy package as a solution to the strategy demand side; the relevant personnel on the strategy demand side can import the risk control strategy package into the target risk control system, so that the target strategy rules can be run online to prevent corresponding risks.

During the specific implementation process, relevant personnel who manage the target risk control system, such as operators, may also be referred to as users of the target risk control system, and can select one or more risk control strategy packages to upload to the target risk control system. For example, one or more risk control strategy packages can be selected locally, and then click the preset Last button to upload the selected risk control strategy packages.

In an optional embodiment, the above process of obtaining the risk control strategy package may include: verifying the file format of the risk control strategy package selected by the user; if the verification passes, uploading the risk control strategy package, and uploading the The risk control strategy package is uploaded to the pre-configured intermediate storage location, and the policy information contained in the risk control strategy package is waiting to be further created to the target risk control system; if the verification fails, the risk control strategy package cannot be uploaded. It is understandable that the file format of the risk control strategy package should be the inherent format that the risk control strategy package is generated and packaged. If the file format does not meet the requirements, it means that the risk control strategy package has errors and cannot pass the verification.

In an optional embodiment, the above process of obtaining the risk control strategy package may include: creating an import task based on the uploaded risk control strategy package, and presetting multiple policy information in the risk control strategy package into the import In the task, it is in a state to be created; if the import instruction for triggering the opening of the import task is monitored, the following step S402 is performed, and the configuration information of the target policy rule and the target policy rule, that is, the variable and variable configuration of the target policy rule configuration All parameters, etc., are created into the target risk control system to complete the layer-by-layer creation of the policy package information to ensure the normal operation of the target policy rules in the target risk control system.

In step S402, according to the index relationship information, import the above-mentioned multiple policy information into the target risk control system, so as to run the target policy rules in the target risk control system.

It can be understood that the target policy rules are used to identify risks of target types, and the operation of the target policy rules needs to rely on multiple information levels. Taking the target policy rules in the risk control policy package and the configuration information of the target policy rules as policy information, the risk control policy package includes multiple policy information and index relationship information between these policy information.

In one embodiment, the configuration information of the target policy rule may include: variables configured by the target policy rule and parameters configured by the variables. In this case, the above-mentioned multiple policy information includes target policy rules, variables and parameters in the risk control policy package. In another embodiment, the configuration information of the target policy rule may include: variables configured by the target policy rule, parameters configured by the variables and the cumulative policy, and variables and parameters configured by the cumulative policy. At this time, the above-mentioned multiple policy information includes target policy rules, variables, accumulation policies and parameters in the risk control policy package. It is understandable that if these pieces of information have sequential dependencies of mutual calls, they need to be created layer by layer according to the dependencies to ensure the normal operation of the target policy rules.

In the embodiment of the present specification, the risk control strategy package is also packaged with index relationship information for reflecting the index relationship between the above-mentioned multiple policy information, that is, the index relationship from the target policy rule level to the parameter level.

Therefore, according to the index relationship information in the risk control strategy package, it is possible to specify the calling sequence of each information level involved in running the target strategy rule to identify risks, so as to create layer by layer.

In an optional embodiment of this specification, the process of importing the risk control strategy package and migrating the risk control strategy realizes the verification of the index relationship in the target risk control system while importing data, which improves the deployment efficiency of the risk control strategy. Specifically, the above process of importing multiple policy information into the target risk control system according to the index relationship information may include: determining, according to the index relationship information contained in the risk control policy package, which policy information in the risk control policy package depends on. Pre-information; for each policy information, an import step is performed, and the import step includes: detecting whether the pre-information of the policy information has taken effect in the target risk control system, and if so, creating the policy information in the target risk control system, If not, it is determined that the import of the policy information has failed, and a failure prompt message is displayed. It should be noted that each policy information in the risk control policy package depends on pre-information. For example, the pre-information that the target policy rule depends on is variable information, and the pre-information that variable depends on is parameter information, or parameter information and cumulative information. The policy information and the pre-parameter-dependent pre-information can be business data such as account ID data transmitted by the upstream business system.

Specifically, to detect whether the pre-information of the strategy information to be imported has taken effect in the target risk control system can detect whether the pre-information has been released online in the target risk control system. It has already taken effect in the target risk control system, that is, it is already running in the target risk control system. If it has not been released online, it is determined that the pre-information has not yet taken effect in the target risk control system. Of course, in the specific implementation process, other implementations may be used according to actual application scenarios to determine whether the pre-information has taken effect in the target risk control system, which is not limited here.

For example, it is assumed that the target policy rule in the risk control policy package obtained in step S400 is that if users in area S log in more than N times a day, it is determined that users in area S have X type of risk. The policy information included in the risk control policy package may include: the above target policy rules; variable V1: area S, variable V2: the number of logins of users in area S in one day; cumulative policy T: count the historical login time of users in area S Details; Parameter P1: User ID, Parameter P2: Area ID. The pre-information of the target policy rule includes: variable V1 and variable V2, the pre-information of variable V1 may be: parameter P2, and the pre-information of variable V2 includes: the above-mentioned accumulation strategy T and parameter P1; The setting information may include: variable V1 and parameter P1; the pre-information of parameter P1 may be: user ID data passed in by the upstream system; the pre-information of parameter P2 may be: area identification data passed in by the upstream system. For each policy information, it is necessary to detect that its pre-information has taken effect in the target risk control system before completing the import, and create the policy information in the target risk control system.

Further, in order to facilitate the user to monitor the import completion of the risk control strategy package, in an optional embodiment of this specification, the above-mentioned risk control strategy migration method further includes: if all the strategy information in the risk control strategy package is imported and completed, it is completed. Created in the target system, a prompt message indicating that the import of the risk control policy package is completed will be displayed. For example, the task status list can be displayed on the user interface preconfigured in the policy demand side, and the task status list of the created import task can be displayed in the task status list. The task status can include non-importing status, importing status, and importing completed status. When it is monitored that all the policy information in the risk control policy package has been imported, the task status of the corresponding importing task is updated from the importing status to the importing status, as Indicates the prompt information indicating that the import of the risk control policy package is completed. Alternatively, the task status can also be displayed in the form of a progress bar. When it is monitored that all policy information in the risk control strategy package has been imported, the progress bar is completed and displays words such as “finish” indicating completion, which is used to indicate the risk control strategy. A message indicating that the package import is complete.

After all the strategy information in the risk control strategy package is imported, that is, after all the strategy information in the risk control strategy package is created in the target risk control system, the target strategy rules can be formally implemented to prevent and control risks online. Through the risk control strategy migration method provided in the embodiments of this specification, users can import the risk control strategy package in the system with one key, without the participation of professionals with risk operation experience, which effectively improves the deployment efficiency of risk control strategies and reduces manpower cost.

In addition, in an optional embodiment of this specification, if one or more policy information fails to be imported in the risk control policy package during an import process, the policy information that fails to be imported may be imported again, so that It can upload and import multiple times at one time, which further improves the migration efficiency of risk control strategies. Specifically, the above process of importing multiple policy information into the target risk control system according to the index relationship information may further include: if there is a policy information import failure in the above multiple policy information, for the policy information that failed to be imported, re-import the policy information. Perform the above import steps until all policy information in the risk control policy package is imported into the target risk control system.

Specifically, for the policy information that fails to be imported, the user can prompt to resolve the pre-dependency of the policy information according to the failure reason. For example, the reason for the import failure of a certain policy information is that the pre-reliance information it depends on has not been released online. Import the policy information after waiting for the pre-information it depends on to be released and online. Of course, in addition to the reason why the pre-dependency does not take effect, in the actual application scenario, there may be other reasons for import failure, such as network abnormality, etc., after the user can deal with the failure reasons according to the prompt, the import failure policy information can be processed again. import.

After the user solves the problem that causes the policy information import failure, the user can trigger the import instruction corresponding to the risk control policy package again, so that the above import steps are performed again for the policy information in the risk control policy package that has not been successfully imported. For example, the user can click the import button on the pre-configured user interface to trigger the import instruction for the created import task, and start the import process of the policy information in the risk control policy package under the import task, and the import is over. After that, if there is policy information that has not been successfully imported under the import task, after solving the problem that caused the import failure of policy information, the user can click the above import button again to import the policy information that was not successfully imported again until the import task is completed. All the following policy information has been imported successfully, and the creation is completed.

Of course, in other embodiments of this specification, if the import of policy information in the risk control strategy package fails, it is determined that the import of the entire risk control strategy package fails, and the import is ended, that is, the current risk control strategy migration process is ended.

The risk control strategy migration method provided by the embodiments of this specification effectively realizes the cross-system application of the risk control strategy rules by importing the risk control strategy package that is separated from the original risk control system and exists as an independent file into the target risk control system. In addition, users can quickly complete the import of the risk control strategy package within one person day, without the participation of professionals with risk operation experience, which effectively improves the deployment efficiency of risk control strategies and reduces labor costs.

In a third aspect, FIG. 5 shows a flowchart of a method for migrating a risk control strategy provided by an embodiment of the present specification. The risk control policy migration method is applied to a policy migration end, and the policy migration end is a device used to provide services for migrating risk control policy rules between different risk control systems. Referring to FIG. 5 , the method may include at least the following steps S500 to S506.

Step S500, in response to a policy package generation instruction triggered by the user, determine a target policy rule in the first risk control system, where the target policy rule is used to identify the risk of the target type.

Step S502, based on the preset data blood relationship information database, obtain the index relationship information of the target policy rule, and according to the index relationship information, determine the configuration information of the target policy rule, the configuration information includes: the variable configured by the target policy rule and the variable configuration parameter.

Step S504, the target policy rule, the configuration information of the target policy rule and the index relationship information are derived from the first risk control system to generate a risk control policy package.

Step S506, in response to the policy package import instruction triggered by the user, import the target policy rule and the configuration information of the target policy rule into the second risk control system according to the index relationship information in the risk control policy package, so that the second risk control system Run the target policy rule in .

It should be noted that the implementation process of step S500 to step S504 is similar to the implementation process of step S200 to step S206 provided in the first aspect. For details, please refer to the corresponding description of the embodiment provided in the first aspect, which will not be repeated here. . The implementation process of step S506 is similar to the implementation process of step S402 provided in the foregoing second aspect, and for details, reference may be made to the corresponding description of the embodiments provided in the foregoing first aspect, which will not be repeated here.

It can be understood that the user in step S500 and step S506 is a user who has the authority to export the policy package from the first risk control system and import the policy package to the second risk control system, for example, the first risk control system or the user. The operator of the second risk control system with the above-mentioned authority may also be a third-party operator with the above-mentioned authority. In step S506, the user can trigger the policy package import instruction by clicking a preconfigured import button or other trigger operations, which is not limited here.

In a fourth aspect, based on the same inventive concept as the method for generating a risk control strategy package provided by the embodiments of the first aspect, the embodiments of this specification further provide an apparatus for generating a risk control strategy package. As shown in FIG. 6 , the device 60 for generating the risk control strategy package includes:

The rule determination module 61 is used to determine the target policy rule in the first risk control system in response to the policy package generation instruction triggered by the user, and the target policy rule is used to identify the risk of the target type; the relationship information acquisition module 62 is used for Based on the preset data lineage information database, the index relationship information of the target policy rule is acquired; the configuration information acquisition module 63 is configured to determine the configuration information of the target policy rule according to the index relationship information, and the configuration information includes : the variable configured by the target policy rule and the parameter configured by the variable; the export module 64 is used to convert the target policy rule, the configuration information of the target policy rule and the index relationship information from the first wind The risk control strategy package is generated, and the risk control strategy package is used to import the second risk control system to prevent and control the risk of the target type.

In an optional embodiment, the above-mentioned configuration information further includes an accumulation policy configured by the variable and variables and parameters configured by the accumulation policy, and the accumulation policy is used to count historical behavior data of the user.

It should be noted that, in the device 60 for generating a risk control strategy package provided in the embodiment of this specification, the specific manner in which each module performs operations has been described in detail in the method embodiment provided in the first aspect, and the specific implementation process can refer to The method embodiments provided in the first aspect above will not be described in detail here.

In the fifth aspect, based on the same inventive concept as the wind control strategy migration method provided by the embodiments of the second aspect, the embodiments of this specification further provide a wind control strategy migration device. As shown in FIG. 7 , the risk control strategy migration device 70 includes:

The obtaining module 71 is configured to obtain a risk control strategy package, where the risk control strategy package includes: a plurality of strategy information and index relationship information between the plurality of strategy information, the plurality of strategy information including target strategy rules, all The variable configured by the target policy rule and the parameter configured by the variable; the import module 72 is used to import the plurality of policy information into the target risk control system according to the index relationship information, so as to be stored in the target risk control system. Run the target policy rule in .

In an optional embodiment, the importing module 72 includes: a determining sub-module 721, configured to determine, according to the index relationship information, pre-information on which each policy information in the risk control policy package depends; first The import sub-module 722 is configured to perform an import step for each policy information, and the import step includes: detecting whether the pre-information of the policy information has taken effect in the target risk control system; The policy information is created in the target risk control system, if not, it is determined that the import of the policy information fails, and a failure prompt message is displayed.

In an optional embodiment, the importing module 72 further includes: a second importing sub-module 723, configured to, if there is a policy information import failure in the plurality of policy information, for the policy information that fails to import, again The importing step is performed until all policy information in the risk control policy package is imported into the target risk control system.

In an optional embodiment, the above-mentioned risk control strategy migration device 70 further includes: a prompt module 73, configured to display a message indicating that the risk control strategy package has been imported if all the strategy information in the risk control strategy package is imported. The prompt message that the import of the policy package is completed.

In an optional embodiment, the above obtaining module 71 includes: a format verification sub-module 711, which is used to verify the file format of the risk control strategy package selected by the user, and if the verification is passed, upload the wind control strategy package. control strategy package.

In an optional embodiment, the above obtaining module 71 includes: a task creation sub-module 712, configured to create an import task based on the uploaded risk control strategy package, and convert the multiple strategies in the risk control strategy package The information is all preset into the import task; the instruction monitoring sub-module 713 is configured to execute the according to the index relationship information, if an import command for triggering the opening of the import task is detected, Steps for importing policy information into the target risk control system.

In an optional embodiment, the above-mentioned risk control strategy package is generated according to the following steps: in response to a strategy package generation instruction triggered by a user, determining a target strategy rule in the first risk control system; based on a preset data lineage information base, to obtain the index relationship information of the target policy rule; according to the index relationship information, determine the configuration information of the target policy rule, the configuration information includes: the variable configured by the target policy rule and the variable configuration The parameters of the target policy rule, the configuration information of the target policy rule and the index relationship information are derived from the first risk control system to generate the risk control policy package.

In an optional embodiment, the above-mentioned configuration information further includes an accumulation policy configured by the variable and variables and parameters configured by the accumulation policy, and the accumulation policy is used to count historical behavior data of the user.

It should be noted that, in the wind control strategy migration device 70 provided in the embodiment of this specification, the specific manner in which each module performs operations has been described in detail in the method embodiment provided in the second aspect above, and the specific implementation process may refer to the above The method embodiments provided by the second aspect will not be described in detail here.

In the sixth aspect, based on the same inventive concept as the risk control strategy migration method provided by the embodiments of the third aspect, the embodiments of this specification also provide a risk control strategy migration device, which runs on the policy migration end, and the policy migration end is used for A device that provides services for migrating risk control policy rules between different risk control systems. As shown in FIG. 8 , the risk control strategy migration device 80 includes:

The strategy package export module 81 is used to determine the target strategy rule in the first risk control system in response to the strategy package generation instruction triggered by the user, and the target strategy rule is used to identify the risk of the target type; based on the preset data blood relationship information library, obtain the index relationship information of the target policy rule, and determine the configuration information of the target policy rule according to the index relationship information, the configuration information includes: the variable configured by the target policy rule and the variable configuration parameters; export the target policy rule, the configuration information of the target policy rule and the index relationship information from the first risk control system to generate a risk control policy package;

The policy package import module 82 is configured to import both the target policy rule and the configuration information of the target policy rule according to the index relationship information in the risk control policy package in response to the policy package import instruction triggered by the user A second risk control system to run the target policy rule in the second risk control system.

It should be noted that, in the wind control strategy migration device 80 provided by the embodiments of this specification, the specific manners of performing operations of each module have been described in detail in the method embodiments provided in the third aspect, and the specific implementation process can refer to the above The method embodiments provided by the third aspect will not be described in detail here.

In a seventh aspect, based on the same inventive concept as the foregoing embodiments, the embodiments of the present specification further provide an electronic device. As shown in FIG. 9 , the electronic device includes a memory 904, one or more processors 902, and a computer program stored in the memory 904 and executable on the processor 902. When the processor 902 executes the program, the aforementioned first aspect is implemented Steps of any embodiment of the provided wind control strategy package generation method, steps of any embodiment of the wind control strategy migration method provided in the second aspect above, or any of the risk control strategy migration methods provided in the third aspect above Example steps.

9, the bus architecture (represented by bus 900), bus 900 may include any number of interconnected buses and bridges, bus 900 will include one or more processors represented by processor 902 and memory 904 The various circuits of the memory are linked together. The bus 900 may also link together various other circuits, such as peripherals, voltage regulators, and power management circuits, etc., which are well known in the art and, therefore, will not be described further herein. Bus interface 905 provides an interface between bus 900 and receiver 901 and transmitter 903 . Receiver 901 and transmitter 903 may be the same element, a transceiver, providing a means for communicating with various other devices over a transmission medium. The processor 902 is responsible for managing the bus 900 and general processing, while the memory 904 may be used to store data used by the processor 902 in performing operations.

It can be understood that the structure shown in FIG. 9 is only for illustration, and the electronic device provided by the embodiments of the present specification may further include more or less components than those shown in FIG. 9 , or have different configurations from those shown in FIG. 9 . . Each component shown in FIG. 9 may be implemented in hardware, software, or a combination thereof.

In an eighth aspect, based on the same inventive concept as the foregoing embodiments, the embodiments of the present specification further provide a computer-readable storage medium on which a computer program is stored, and when the program is executed by a processor, realizes the above-mentioned first aspect. Steps of any embodiment of the wind control strategy package generation method, steps of any embodiment of the wind control strategy migration method provided in the second aspect above, or any implementation of the risk control strategy migration method provided in the third aspect above example steps.

It should be noted that the various embodiments in this specification are described in a progressive manner, and each embodiment focuses on the differences from other embodiments. For the same and similar parts among the various embodiments, refer to each other Can.

The foregoing describes specific embodiments of the present specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims can be performed in an order different from that in the embodiments and still achieve desirable results. Additionally, the processes depicted in the figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

The specification is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the specification. It will be understood that each flow and/or block in the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to the processor of a general purpose computer, special purpose computer, embedded processor or other programmable data processing device to produce a machine such that the instructions executed by the processor of the computer or other programmable data processing device produce A device that implements the functions specified in a flow or flow of a flowchart and/or a block or blocks of a block diagram.

These computer program instructions may also be stored in a computer readable memory capable of directing a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer readable memory result in an article of manufacture comprising the instruction apparatus, the instructions The device implements the functions specified in the flow or flows of the flowcharts and/or the block or blocks of the block diagrams.

These computer program instructions can also be loaded on a computer or other programmable data processing device to cause a series of operational steps to be performed on the computer or other programmable device to produce a computer-implemented process such that The instructions provide steps for implementing the functions specified in the flow or blocks of the flowcharts and/or the block or blocks of the block diagrams.

While the preferred embodiments of this specification have been described, additional changes and modifications to these embodiments may occur to those skilled in the art once the basic inventive concepts are known. Therefore, the appended claims are intended to be construed to include the preferred embodiment and all changes and modifications that fall within the scope of this specification.

Obviously, those skilled in the art can make various changes and modifications to this specification without departing from the spirit and scope of this specification. Thus, provided that these modifications and variations of the present specification fall within the scope of the claims of the present specification and technical equivalents thereof, the present specification is also intended to include these modifications and variations.

Claims (24)

1. A risk control strategy migration method, comprising: Obtain a risk control policy package, where the risk control policy package includes: multiple policy information and index relationship information between the multiple policy information, where the multiple policy information includes target policy rules, and the target policy rules configured variables and parameters configured by said variables; According to the index relationship information, the plurality of policy information is imported into the target risk control system, so as to run the target policy rule in the target risk control system. 2. The method according to claim 1, wherein importing the plurality of policy information into a target risk control system according to the index relationship information, comprising: According to the index relationship information, determine the pre-information on which each policy information in the risk control policy package depends; For each strategy information, an importing step is performed, and the importing step includes: detecting whether the pre-information of the strategy information has taken effect in the target risk control system, and if so, in the target risk control system Create the policy information, if not, it is determined that the import of the policy information fails, and a failure prompt message is displayed. 3. The method according to claim 2, wherein according to the index relationship information, importing the plurality of policy information into a target risk control system, further comprising: If there is a strategy information import failure in the plurality of strategy information, the import step is performed again for the strategy information that failed to import, until all the strategy information in the risk control strategy package is imported into the target risk control system. 4. The method of claim 1, further comprising: If all the policy information in the risk control strategy package has been imported, a prompt message indicating that the import of the risk control strategy package is complete is displayed. 5. The method according to claim 1, said obtaining a risk control strategy package, comprising: The file format of the risk control strategy package selected by the user is verified, and if the verification is passed, the risk control strategy package is uploaded. 6. The method according to claim 1, said obtaining a risk control strategy package, comprising: Create an import task based on the uploaded risk control strategy package, and preset the multiple policy information in the risk control strategy package into the import task; If an import instruction for triggering the opening of the import task is detected, the step of importing the plurality of policy information into the target risk control system according to the index relationship information is performed. 7. The method according to claim 1, wherein the risk control strategy package is generated according to the following steps: In response to the policy package generation instruction triggered by the user, determine the target policy rule in the first risk control system; Obtain the index relationship information of the target policy rule based on a preset data lineage information database; According to the index relationship information, the configuration information of the target policy rule is determined, and the configuration information includes: a variable configured by the target policy rule and a parameter configured by the variable; The target policy rule, the configuration information of the target policy rule and the index relationship information are derived from the first risk control system to generate the risk control policy package. 8 . The method according to claim 7 , wherein the configuration information further comprises a cumulative strategy configured by the variable and variables and parameters configured by the cumulative strategy, the cumulative strategy being used to count historical behavior data of users. 9 . 9. A method for generating a risk control strategy package, for generating the risk control strategy package according to any one of claims 1-6, the method comprising: In response to the policy package generation instruction triggered by the user, determine a target policy rule in the first risk control system, where the target policy rule is used to identify the risk of the target type; Obtain the index relationship information of the target policy rule based on a preset data lineage information database; According to the index relationship information, the configuration information of the target policy rule is determined, and the configuration information includes: a variable configured by the target policy rule and a parameter configured by the variable; The target policy rule, the configuration information of the target policy rule, and the index relationship information are derived from the first risk control system to generate the risk control policy package, which is used to import the first risk control policy package. The second risk control system controls the risk of the target type. 10 . The method according to claim 9 , wherein the configuration information further comprises a cumulative strategy configured by the variable and variables and parameters configured by the cumulative strategy, the cumulative strategy being used to count historical behavior data of users. 11 . 11. A method for migrating a risk control strategy, comprising: In response to the policy package generation instruction triggered by the user, determine a target policy rule in the first risk control system, where the target policy rule is used to identify the risk of the target type; Based on a preset data lineage information database, the index relationship information of the target policy rule is obtained, and according to the index relationship information, the configuration information of the target policy rule is determined, and the configuration information includes: the target policy rule configuration The variables of and the parameters configured by the variables; Deriving the target policy rule, the configuration information of the target policy rule and the index relationship information from the first risk control system to generate a risk control policy package; In response to the policy package import instruction triggered by the user, according to the index relationship information in the risk control policy package, both the target policy rule and the configuration information of the target policy rule are imported into the second risk control system, so as to be in the second risk control system. The target policy rule is run in the second risk control system. 12. A risk control strategy migration device, comprising: an obtaining module, configured to obtain a risk control strategy package, where the risk control strategy package includes: a plurality of strategy information and index relationship information between the plurality of strategy information, the plurality of strategy information including target strategy rules, the Variables configured by the target policy rule and parameters configured by the variables; The import module is configured to import the plurality of policy information into the target risk control system according to the index relationship information, so as to run the target policy rules in the target risk control system. 13. The apparatus of claim 12, the import module comprising: A determination submodule, configured to determine the pre-information on which each policy information in the risk control policy package depends, according to the index relationship information; The first import sub-module is configured to perform an import step for each policy information, and the import step includes: detecting whether the pre-information of the policy information has taken effect in the target risk control system, and if so, then The policy information is created in the target risk control system, if not, it is determined that the import of the policy information fails, and a failure prompt message is displayed. 14. The apparatus of claim 13, the import module further comprising: The second importing sub-module is configured to perform the importing step again for the policy information that fails to import if the policy information fails to be imported in the plurality of policy information, until all the policy information in the risk control policy package is Import the target risk control system. 15. The apparatus of claim 12, further comprising: A prompt module, configured to display prompt information indicating that the import of the risk control strategy package is completed if all the policy information in the risk control strategy package is imported. 16. The apparatus of claim 12, the acquisition module comprising: The format verification sub-module is used to verify the file format of the risk control strategy package selected by the user, and if the verification is passed, upload the risk control strategy package. 17. The apparatus of claim 12, the acquisition module comprising: a task creation submodule, used for creating an import task based on the uploaded risk control strategy package, and presetting the plurality of strategy information in the risk control strategy package into the import task; The instruction monitoring sub-module is configured to execute the step of importing the plurality of policy information into the target risk control system according to the index relationship information if an import instruction for triggering the opening of the import task is monitored. 18. The device according to claim 12, wherein the risk control strategy package is generated according to the following steps: In response to the policy package generation instruction triggered by the user, determine the target policy rule in the first risk control system; Obtain the index relationship information of the target policy rule based on a preset data lineage information database; According to the index relationship information, the configuration information of the target policy rule is determined, and the configuration information includes: a variable configured by the target policy rule and a parameter configured by the variable; The target policy rule, the configuration information of the target policy rule and the index relationship information are derived from the first risk control system to generate the risk control policy package. 19. The apparatus according to claim 18, wherein the configuration information further comprises a cumulative strategy configured by the variable and variables and parameters configured by the cumulative strategy, the cumulative strategy being used to count historical behavior data of users. 20. A device for generating a risk control strategy package for generating the risk control strategy package according to any one of claims 1-6, the device comprising: a rule determination module, configured to determine a target policy rule in the first risk control system in response to a policy package generation instruction triggered by a user, where the target policy rule is used to identify the risk of the target type; A relationship information acquisition module, configured to acquire the index relationship information of the target policy rule based on a preset data blood relationship information database; a configuration information acquisition module, configured to determine configuration information of the target policy rule according to the index relationship information, where the configuration information includes: a variable configured by the target policy rule and a parameter configured by the variable; An export module, configured to export the target policy rule, the configuration information of the target policy rule and the index relationship information from the first risk control system to generate the risk control policy package, the risk control policy The package is used to import the second risk control system to prevent and control the risk of the target type. 21. The apparatus according to claim 20, wherein the configuration information further comprises a cumulative strategy configured by the variable and variables and parameters configured by the cumulative strategy, the cumulative strategy being used to count historical behavior data of users. 22. A risk control strategy migration device, comprising: The policy package export module is used to determine the target policy rule in the first risk control system in response to the policy package generation instruction triggered by the user, and the target policy rule is used to identify the risk of the target type; based on the preset data blood relationship information database , obtain the index relationship information of the target policy rule, and determine the configuration information of the target policy rule according to the index relationship information, the configuration information includes: the variable configured by the target policy rule and the variable configured by the variable parameters; exporting the target policy rule, the configuration information of the target policy rule and the index relationship information from the first risk control system to generate a risk control policy package; The policy package import module is used to import the target policy rule and the configuration information of the target policy rule into the first step according to the index relationship information in the risk control policy package in response to the policy package import instruction triggered by the user. A second risk control system to run the target policy rule in the second risk control system. 23. An electronic device comprising: a memory, a processor and a computer program stored on the memory and executable on the processor, the processor implementing the program described in any one of claims 1-11 when the processor executes the program steps of the method. 24. A computer-readable storage medium having stored thereon a computer program which, when executed by a processor, implements the steps of the method of any one of claims 1-11.

Images