A risk management method and device

Abstract

The present invention discloses a risk management method and device, and relates to the field of computer technology. A specific implementation of the method includes: receiving a project participation request, querying the first project participation information of the corresponding item and the second project participation information of the requesting party to which the item belongs according to the item identification in the project participation request; obtaining the corresponding verification rules according to the project identification of the project to be participated; wherein the verification rules are used to limit the number of projects that the item can participate in at the same time during the online cycle, and to limit the frequency of the requesting party participating in the project; performing risk verification on the item and the requesting party according to the first project participation information, the second project participation information and the verification rules, and allowing the item to participate in the project to be participated after determining that the verification passes. The method automatically performs risk verification on the item and the requesting party, realizes unified management and control of different projects, and at the same time improves the verification accuracy and efficiency, and avoids duplicate subsidies and resource tilt.

Description

Technical Field

[0001] The present invention relates to the field of computer technology, and in particular to a risk management method and device. Background Art

[0002] In the prior art, service providers usually provide a variety of projects for partners to choose to join, and can also subsidize their own assets to partners to facilitate transactions between partners and users. In order to ensure asset security, service providers usually conduct risk control on each project in three links. Specifically, before the project goes online, the partners (i.e., requesters) and items that request to join the project are subject to qualification access verification; after the project goes online, the transaction users are subject to risk identification, and after the project goes offline, false transactions are identified.

[0003] In the process of implementing the present invention, there are at least the following problems in the prior art:

[0004] Due to the large differences between projects, service providers will use independent business systems to carry projects during development, resulting in the inability to uniformly manage and control all projects; risky transactions are intercepted only after the project goes online, resulting in high transaction risks; manual review of requesters and items has low accuracy and efficiency, and is prone to risk issues such as duplicate subsidies and resource imbalance, leading to waste of resources. Summary of the invention

[0005] In view of this, an embodiment of the present invention provides a risk management method and device. By stipulating the parameters of a project participation request as a project ID, an item ID and an online cycle, the verification rules corresponding to the project ID can be used before the project goes online to automatically perform risk verification on the items and the requester, thereby achieving unified management and control of different projects, while improving verification accuracy and efficiency, and avoiding duplicate subsidies and resource tilt.

[0006] To achieve the above objective, according to one aspect of an embodiment of the present invention, a risk management method is provided.

[0007] A risk management method according to an embodiment of the present invention comprises: receiving a project participation request, querying first project participation information of a corresponding item and second project participation information of a requesting party to which the item belongs according to an item identification in the project participation request; wherein the project participation request comprises a project identification of a project to be participated in, the item identification and an online cycle; obtaining corresponding verification rules according to the project identification of the project to be participated in; wherein the verification rules are used to limit the number of projects in which the item can participate simultaneously within the online cycle, and to limit the frequency with which the requesting party can participate in a project; performing risk verification on the item and the requesting party according to the first project participation information, the second project participation information and the verification rules, and allowing the item to participate in the project to be participated in after determining that the verification has passed.

[0008] Optionally, the verification rules include repetition rules and fatigue value rules; the repetition rules are used to limit the number of projects in which the item can participate simultaneously during the online cycle; the fatigue value rules are used to limit the frequency with which the requester can participate in projects, including setting a threshold value for a fatigue value index; the risk verification of the item and the requester based on the first project participation information, the second project participation information and the verification rules includes: performing a repetition verification on the item based on the first project participation information and the repetition rules to obtain a repetition verification result; comparing the fatigue value data in the second project participation information with the threshold to obtain a fatigue value verification result; wherein the fatigue value data is statistically calculated according to the fatigue value index.

[0009] Optionally, the item is subjected to duplication verification based on the first project participation information and the duplication rule to obtain a duplication verification result, including: determining the locking status of the item during the online cycle based on the first project participation information; if the locking status is locked, the duplication verification fails; if the locking status is unlocked, the duplication verification passes.

[0010] Optionally, the method also includes: determining that the duplication check of the item has passed, locking the item when the item is online or a locking instruction is received, and updating the locking state to locked; unlocking the item when the item is offline, the locking time expires, or an unlocking instruction is received, and updating the locking state to unlocked.

[0011] Optionally, the fatigue value indicator includes any one or more of: the number of times the requester participates in the project within a set time period, the number of items for which the requester participates in the project within the time period, and the amount of subsidy to the requester within the time period.

[0012] Optionally, the method further includes: taking the item identifier and the requesting party identifier as input parameters, calling a risk identification service to obtain a risk tag of the item and a risk tag of the requesting party; the determination that the verification is passed includes: the risk tag is empty and the risk verification is passed.

[0013] Optionally, the method further comprises: configuring a whitelist for the project to be participated in; wherein the whitelist comprises one or more of a whitelisted item identifier and a whitelisted requester identifier, and a whitelisting period; before the step of performing risk verification on the item and the requester, the method further comprises: judging whether there is a whitelisted item identifier identical to the item identifier, or a whitelisted requester identifier identical to the requester identifier in the whitelist; if there is a whitelisted item identifier identical to the item identifier in the whitelist, and the online period belongs to the whitelisting period, determining that the verification is passed; if there is a whitelisted item identifier identical to the item identifier in the whitelist, and the online period belongs to the whitelisting period, determining that the verification is passed; if there is a whitelisted item identifier identical to the requester identifier in the whitelist, If there is a whitelisted requester identifier that is the same as the item identifier and the online cycle belongs to the whitelisted period, it is determined that the verification is passed; the risk verification of the item and the requester includes: if there is no whitelisted item identifier that is the same as the item identifier in the whitelist, and there is no whitelisted requester identifier that is the same as the requester identifier, then the risk verification of the item and the requester is performed; if there is a whitelisted requester identifier that is the same as the requester identifier in the whitelist, or there is a whitelisted requester identifier that is the same as the requester identifier, but the online cycle does not belong to the whitelisted period, then the risk verification of the item and the requester is performed.

[0014] Optionally, the method also includes: receiving an item risk query request, and querying the third project participation information of the corresponding target item and the fourth project participation information of the target requester to which the target item belongs according to the target item identifier in the item risk query request; wherein the item risk query request includes the project identifier of the item to be queried, the target item identifier and the query time; according to the project identifier of the item to be queried, obtaining the corresponding verification rule; wherein the verification rule is used to limit the number of projects in which the target item participates simultaneously within the query time, and to limit the frequency of the projects in which the target requester participates; according to the third project participation information, the fourth project participation information and the obtained verification rule, performing risk verification on the target requester and the target item to obtain the risk information of the target item.

[0015] Optionally, the method further includes: receiving a risk query request from a requesting party, wherein the risk query request from the requesting party includes a project identifier of the project to be queried and an identifier of a target requesting party; and returning risk information obtained by performing risk verification on the target requesting party.

[0016] To achieve the above objective, according to another aspect of an embodiment of the present invention, a risk management device is provided.

[0017] A risk management device according to an embodiment of the present invention comprises: a query module, which receives a project participation request, and queries first project participation information of a corresponding item and second project participation information of a requesting party to which the item belongs according to an item identification in the project participation request; wherein the project participation request comprises a project identification of the project to be participated, the item identification and an online cycle; an acquisition module, which is used to acquire corresponding verification rules according to the project identification of the project to be participated; wherein the verification rules are used to limit the number of projects in which the item can participate simultaneously within the online cycle, and to limit the frequency with which the requesting party can participate in projects; a verification module, which is used to perform risk verification on the item and the requesting party according to the first project participation information, the second project participation information and the verification rules, and after determining that the verification passes, allow the item to participate in the project to be participated.

[0018] Optionally, the verification rules include repetition rules and fatigue value rules; the repetition rules are used to limit the number of projects in which the item can participate simultaneously during the online cycle; the fatigue value rules are used to limit the frequency with which the requesting party participates in the project, including setting a threshold value for a fatigue value indicator; the verification module is further used to perform repetition verification on the item according to the first project participation information and the repetition rules to obtain a repetition verification result; the fatigue value data in the second project participation information is compared with the threshold to obtain a fatigue value verification result; wherein the fatigue value data is statistically calculated according to the fatigue value indicator.

[0019] Optionally, the verification module is further used to determine the locking status of the item during the online cycle based on the first project participation information; if the locking status is locked, the duplication check fails; if the locking status is unlocked, the duplication check passes.

[0020] Optionally, the device also includes: a locking module, used to determine whether the duplication check of the item has passed, and when the item is online or a locking instruction is received, the item is locked, and the locking state is updated to locked; when the item is offline, the locking time expires, or an unlocking instruction is received, the item is unlocked, and the locking state is updated to unlocked.

[0021] Optionally, the fatigue value indicator includes any one or more of: the number of times the requester participates in the project within a set time period, the number of items for which the requester participates in the project within the time period, and the amount of subsidy to the requester within the time period.

[0022] Optionally, the device also includes: a risk identification module, which is used to call a risk identification service with the item identification and the requesting party identification as input parameters to obtain the risk tag of the item and the risk tag of the requesting party; the verification module is also used when the risk tag is empty and the risk verification passes.

[0023] Optionally, the device further includes: a configuration module, configured to configure a whitelist for the project to be participated in; wherein the whitelist includes one or more of a whitelisted item identifier and a whitelisted requester identifier, and a whitelisting period; the device further includes: a judgment module, configured to judge whether there is a whitelisted item identifier identical to the item identifier, or a whitelisted requester identifier identical to the requester identifier in the whitelist; if there is a whitelisted item identifier identical to the item identifier in the whitelist, and the online period belongs to the whitelisting period, then it is determined that the verification is passed; if there is a whitelisted item identifier identical to the item identifier in the whitelist, and the online period belongs to the whitelisting period, then it is determined that the verification is passed; if there is a whitelisted item identifier identical to the requester identifier in the whitelist, then it is determined that the verification is passed. The verification module is further used for performing a risk verification on the item and the requester if there is a whitelisted item identifier that is identical to the item identifier and there is no whitelisted requester identifier that is identical to the requester identifier in the whitelist; if there is a whitelisted requester identifier that is identical to the requester identifier in the whitelist, or there is a whitelisted requester identifier that is identical to the requester identifier, but the online cycle does not belong to the whitelisting cycle, performing a risk verification on the item and the requester.

[0024] Optionally, the device also includes: a first query module, used to receive an item risk query request, and query the third project participation information of the corresponding target item and the fourth project participation information of the target requester to which the target item belongs according to the target item identifier in the item risk query request; wherein the item risk query request includes the project identifier of the item to be queried, the target item identifier and the query time; according to the project identifier of the item to be queried, a corresponding verification rule is obtained; wherein the verification rule is used to limit the number of projects in which the target item participates simultaneously within the query time, and to limit the frequency of the projects in which the target requester participates; according to the third project participation information, the fourth project participation information and the obtained verification rule, the target requester and the target item are risk verified to obtain the risk information of the target item.

[0025] Optionally, the device also includes: a second query module, used to receive a risk query request from a requesting party, wherein the risk query request from the requesting party includes a project identifier of the project to be queried and an identifier of a target requesting party; and return risk information obtained by performing risk verification on the target requesting party.

[0026] To achieve the above objective, according to another aspect of an embodiment of the present invention, an electronic device is provided.

[0027] An electronic device according to an embodiment of the present invention comprises: one or more processors; a storage device 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 implement a risk management method according to an embodiment of the present invention.

[0028] To achieve the above objective, according to another aspect of the embodiments of the present invention, a computer readable medium is provided.

[0029] A computer-readable medium according to an embodiment of the present invention stores a computer program, and when the program is executed by a processor, a risk management method according to an embodiment of the present invention is implemented.

[0030] An embodiment of the above invention has the following advantages or beneficial effects: by specifying the parameters of the project participation request as the project ID, item ID and online cycle, the verification rules corresponding to the project ID can be used to automatically perform risk verification on the items and the requester before the project goes online, thereby achieving unified management and control of different projects, while improving verification accuracy and efficiency, and avoiding duplicate subsidies and resource tilt.

[0031] Use thresholds to limit the fatigue value of the requester to prevent the requester from participating in projects frequently, which will lead to the concentration of resources on the requester. Perform duplication check on items based on the lock mechanism to prevent the same item from participating in multiple projects and causing duplicate subsidies. Provide multiple ways to lock and unlock items, with good flexibility. By configuring the fatigue value indicator, it is convenient to check the fatigue value of the requester.

[0032] Combine routine risk identification with fatigue value verification and repetition verification, so that risk interception, repeated subsidy interception and fatigue value exceeding interception can be carried out before the project goes online. By configuring a whitelist for the project, there is no need to conduct risk verification on the items and requesters in the whitelist during the whitelisting cycle. After receiving the risk query request, the risk information of the item and the requester is determined, which makes it easier for managers to select items and requesters to participate in the project.

[0033] The further effects of the above-mentioned non-conventional optional manner will be described below in conjunction with the specific implementation manner. BRIEF DESCRIPTION OF THE DRAWINGS

[0034] The accompanying drawings are used to better understand the present invention and do not constitute an improper limitation of the present invention.

[0035] Figure 1 is a schematic diagram of the main steps of the risk management method according to the first embodiment of the present invention;

[0036] Figure 2 is a schematic diagram of a system architecture for implementing a risk management method according to an embodiment of the present invention;

[0037] Figure 3 This is a schematic diagram of the main process of the risk management method according to the second embodiment of the present invention;

[0038] Figure 4 is a schematic diagram of a rule configuration page of an embodiment of the present invention;

[0039] Figure 5 is a schematic diagram of fatigue value rule configuration according to an embodiment of the present invention;

[0040] Figure 6 This is a schematic diagram of the main process of the risk management method according to the third embodiment of the present invention;

[0041] Figure 7 is a schematic diagram of an item risk query page according to an embodiment of the present invention;

[0042] Figure 8 is a schematic diagram of a requester risk query page according to an embodiment of the present invention;

[0043] Fig. 9 This is a schematic diagram of the main process of the risk management method according to the fourth embodiment of the present invention;

[0044] Fig.10 is a schematic diagram of main modules of a risk management device according to an embodiment of the present invention;

[0045] Fig.11 is an exemplary system architecture diagram to which embodiments of the present invention may be applied;

[0046] Fig.12 It is a schematic diagram of the structure of a computer device suitable for implementing the electronic device of the embodiment of the present invention. DETAILED DESCRIPTION

[0047] The following is a description of exemplary embodiments of the present invention in conjunction with the accompanying drawings, including various details of the embodiments of the present invention to facilitate understanding, which should be considered as merely exemplary. Therefore, it should be recognized by those of ordinary skill in the art that various changes and modifications may be made to the embodiments described herein without departing from the scope and spirit of the present invention. Similarly, for clarity and conciseness, the description of well-known functions and structures is omitted in the following description.

[0048] Figure 1 Schematic diagram of the main steps of the risk management method according to the first embodiment of the present invention. Figure 1 As shown, the risk management method of the embodiment of the present invention mainly includes the following steps:

[0049] Step S101: Receive a project participation request, and query the first project participation information of the corresponding item and the second project participation information of the requesting party to which the item belongs according to the item identification in the project participation request. The project participation request includes the project identification, item identification and online cycle of the project to be participated in. The project identification is used to uniquely identify the project, the item identification is used to uniquely identify the item, and the online cycle is the time from the item being online to being offline. The requesting party to which the item belongs is the owner of the item before the transaction.

[0050] After receiving the project participation request, the first project participation information corresponding to the item identifier and the second project participation information of the requester to which the item belongs are queried from the database. In the embodiment, the first project participation information is used to record the information of the item participating in the project, which may include the locking status, locking time, locking project and other information of the item. The second project participation information is used to record the information of the requester participating in the project, which may include the number of times the requester participates in the project in different time dimensions, the amount of subsidy obtained by the requester, the number of items participating in the project and other fatigue value data.

[0051] Step S102: Obtain the corresponding verification rules according to the project ID of the project to be participated. Different projects have different requirements for risk control, so the corresponding verification rules can be configured in advance based on the project requirements. After receiving the project participation request, the corresponding verification rules can be obtained according to the project ID. The verification rules are used to limit the number of projects that an item can participate in at the same time during the online cycle, and to limit the frequency of the requester's participation in the project.

[0052] Step S103: Based on the first project participation information, the second project participation information and the verification rules, the item and the requester are subjected to risk verification, and after the verification is determined to be passed, the item is allowed to participate in the project to be participated in. In the embodiment, the verification rules are divided into repetition rules and fatigue value rules, wherein the repetition rules are used to limit the number of projects that an item can participate in at the same time during the online cycle, and the fatigue value rules are used to limit the frequency of the requester participating in the project.

[0053] When performing risk verification, the item needs to be verified for duplication according to the first project participation information and duplication rules to obtain duplication verification results; the requester needs to be verified for fatigue value according to the second project participation information and fatigue value rules to obtain fatigue value verification results. After both duplication verification and fatigue value verification are passed, the item is allowed to participate in the project to be participated.

[0054] Figure 2 Schematic diagram of the system architecture for implementing the risk management method of the embodiment of the present invention. Figure 2As shown, the system for implementing the risk management method in the embodiment of the present invention is composed of a display layer, a business layer, a service layer and a data layer. Among them, the display layer is used to realize the interaction between the system and the user. The service layer is used to provide business access services, fatigue value statistics services and risk verification services. The data layer is used to access databases, such as MySQL and Redis databases.

[0055] The business layer includes business access module, item risk module, requester risk module and risk whitelisting module. Among them, the business access module is used to access the business system and configure verification rules. The item risk module is used to identify item risks, perform duplication verification, and perform fatigue value verification. The requester risk module is used to identify requester risks and perform fatigue value verification. The risk whitelisting module is used to add specified risk items and risk requesters to the whitelist.

[0056] Figure 3 Schematic diagram of the main process of the risk management method according to the second embodiment of the present invention. Figure 3 As shown, the risk management method of the embodiment of the present invention is implemented by a risk management system, which includes a front-end page and a back-end, and mainly includes the following steps:

[0057] Step S301: The front-end page sends the configured verification rules to the back-end. The front-end page provides a rule configuration page. After the administrator configures the verification rules on the page, the front-end page sends the verification rules to the back-end. The verification rules include repetition rules and fatigue value rules.

[0058] The duplication rule is used to limit the number of projects that an item can participate in at the same time during the online cycle. In the embodiment, the number of projects that an item can participate in at the same time during the online cycle can be limited to 1, that is, an item can only participate in one project during the online cycle. The configuration of the duplication rule can be implemented on the front-end page or configured in the background.

[0059] The fatigue value rule is used to limit the frequency of the requester's participation in the project. In the embodiment, the frequency limit of the requester's participation in the project is achieved by setting a threshold of the fatigue value indicator. The fatigue value indicator may include any one or more of the number of times the requester participates in the project in different time dimensions, the number of items in the project, the number of item parameter items, and the amount of subsidy to the requester. The time dimension may be year, quarter, month, etc.

[0060] The configuration of fatigue value rules needs to be implemented on the rule configuration page of the front-end page. Figure 4 and Figure 5 The configuration of the fatigue value rule is explained.

[0061] like Figure 4As shown in the figure, the rule configuration page includes a project name selection box, a query button, a new business fatigue value rule button, and a new global fatigue value rule button. After selecting a specific project in the project name selection box, click the query button to obtain the thresholds of each fatigue value indicator configured for the project.

[0062] For example, if the annual participation times of project 1 is 3, the annual participation project sku number is 10, the annual subsidy amount is 10,000 yuan, the monthly participation times is 0, the monthly participation project sku number is 0, and the monthly subsidy amount is 0 yuan. After finding the threshold configured for the project, you can also modify the above threshold by clicking the Modify Rule button.

[0063] In addition, the rule configuration page also includes a new business scenario button. Clicking this button can add project information, which can include project ID, project name, project leader, etc. After the administrator clicks the new business scenario button to add a project, the project name in the project name selection box will also be increased accordingly.

[0064] If you need to add fatigue value rules for a project, the administrator can select the project on this page and click the Add Business Fatigue Value Rule button or the Add Global Fatigue Value Rule button to configure the fatigue value rules.

[0065] Take clicking the button to add a new business fatigue value rule as an example. When the front-end page detects the click operation, it jumps to Figure 5 The fatigue value rule setting page is shown. The administrator can select or fill in the specific threshold of the fatigue value indicator on this page. For example, the number of participations of the same venderid in 2020 shall not exceed 5 times. For another example, the subsidy amount for the same venderid in January 2020 shall not exceed 5,000 yuan.

[0066] Step S302: Synchronize the item online information of the business system to the online item database in the background. Due to the large differences between projects, the service provider will use an independent business system to carry the project during development, and the project data (including the requester information and item information of the project participants) will also be stored in the database of each business system. The structures of different databases vary greatly. This embodiment unifies the data structure of the project data and synchronizes the data stored in the database of each business system to the online item database, thereby realizing the integration and unification of isolated project data and providing a data source for subsequent fatigue value statistics and whitening processing.

[0067] There are two ways to obtain item online information:

[0068] Method 1: define a message queue (MQ) for synchronizing data. When the business system launches an item, the item launch information is sent to MQ. The background parses the content of MQ and writes the parsing result into the item launch table of the online item database. In the embodiment, the item launch table includes the business system identifier (such as the business system name), the project identifier, the requester identifier, the item sku (stock keeping unit), the item spu (standard product unit) and the launch cycle.

[0069] In an optional embodiment, the background defines the format of MQ. When a new item is added online, information such as the item ID, sku, and online cycle is sent to MQ; when the item online information changes, the changed item ID, sku, and changed online cycle are sent; when the item is offline, the original item ID, sku, original online cycle, and offline ID are sent.

[0070] Method 2: When the business system calls the judgment interface of the background, the background will actively scan the database of the business system background that stores the online item information. If it is determined that the data has been updated, the corresponding data will be updated in the online item database. The table scan here means that the background reads the full amount of database data at a set time and compares it with the online item database. If there is new data, the new data will be inserted; if the existing data has been updated, the data will be updated; if the existing data is more than the data in the business system, the status of the extra items will be changed to offline.

[0071] Step S303: When the online item database is updated, the background locks the item and stores the locking data in the item locking status table of the item lock database. In the embodiment, the item locking status table (i.e., the first item information) includes the locking status, locking period, locking item, and item identification (such as skuid, spuid). This step is used to automatically lock the online item when the item is online, the locking status is locked, and the locking period is the online period of the item.

[0072] In an optional embodiment, the item can also be manually locked on the item risk query page in the background (that is, the administrator clicks the lock button on the item risk query page to trigger the generation of a lock instruction to achieve item locking). Different locking methods (automatic locking and manual locking) may have intersections.

[0073] If the lock mode is automatic, you cannot unlock or change the lock period on the item risk query page. It will be automatically unlocked only when the item is offline and synchronized to the online item database or the lock period expires. If the lock mode is manual, you can click the Unlock button on the item risk query page to manually unlock. If the lock mode is manual, you can also click the Change Lock Time button on the item risk query page to update the lock period.

[0074] Step S304: The business system uses the project ID, item ID and online cycle as input parameters and calls the background judgment interface. The judgment interface is used to verify whether the items passed by the business system can participate in the corresponding project. The verification content includes: whether there is a risk, whether the fatigue value exceeds the standard, and whether the subsidy is repeated. If all the above checks are passed, the judgment interface returns the verification passed, otherwise it returns the verification failed.

[0075] The business system calls the judgment interface by carrying a project participation request in the call request. The project participation request includes the project ID, item ID, and online cycle. The business system can call the judgment interface in both the requester registration stage and the item formal online stage. If the judgment interface returns a verification failure, a prompt message indicating that the requester registration failed or the item online failed can be output.

[0076] Step S305: The backend performs risk verification based on the input parameters of the business system. The risk verification in this step includes repetition verification and fatigue value verification. The following will explain them separately.

[0077] Duplicate check: When the business system calls the judgment interface, the judgment interface takes the project ID, item ID and online cycle as input parameters to query the item lock database. If the online cycle of the item transmitted by the business system does not conflict with the locking cycle of the item in other projects, the duplicate check passes; otherwise, the duplicate check fails.

[0078] In the embodiment, the locking status of the item during the online cycle can be queried. If the locking status is locked, the duplication check fails; if the locking status is unlocked, the duplication check passes.

[0079] For example, if item 1 is launched in project 1, and the launch period is from January 1 to January 10, the backend will lock the item under this project from January 1 to January 10. If item 1 is also selected in project 2 and is to be launched from January 5 to January 20, the business system calls the judgment interface to perform duplication check and finds that the item is locked by project 1 from January 1 to 10. The launch period conflicts with the lock period, and the return check fails.

[0080] Fatigue value verification: synchronize the online item database to the data mart, and associate the settlement data of the settlement system, calculate the fatigue value data of the requester participating in the project according to the fatigue value index, and store it in the fatigue information table of the fatigue value database. In the embodiment, the fatigue information table includes the subsidy amount in different time dimensions, the number of participations of the requester, the number of participations of the item, and the project identifier.

[0081] When the business system calls the judgment interface, the judgment interface takes the project ID and the requester ID as input parameters, and queries the fatigue value data of the corresponding requester from the fatigue value database. If the queried fatigue value data is less than the threshold configured on the rule configuration page, the fatigue value check passes; otherwise, the fatigue value check fails.

[0082] Step S306: The backend uses the item ID and the requester ID as input parameters to call the risk identification service of the risk identification system. The backend calls the risk identification service by carrying the risk identification request in the call request. The risk identification request includes the item ID and the requester ID.

[0083] Step S307: The risk identification system returns the risk tag corresponding to the item ID and the risk tag corresponding to the requester ID to the backend. The risk identification service verifies the pre-configured risk strategy in real time based on the input parameters, and feeds back the hit risk tags. In the embodiment, the risk tags include: risk requester, compensation inversion, arbitrage risk, other risks, order abnormality, ticket closing requester, arbitrage ticket requester, etc.

[0084] When the business system calls the judgment interface, the judgment interface calls the risk identification service. If the returned risk tag is empty, the verification passes; otherwise, the verification fails.

[0085] Step S308: The background generates the risk verification result and sends it to the business system. The risk verification result here is obtained based on the repetition verification result and fatigue value verification result of step S305, and the risk tag obtained in step S307. If the risk tag is empty, and the repetition verification and fatigue value verification are all passed, the judgment interface returns the verification passed, otherwise the verification is returned failed.

[0086] It is understandable that the repeatability check and fatigue value check of step S305 and the risk identification of steps S306 and S307 may be executed in parallel or sequentially, and this embodiment does not limit the execution order of the three.

[0087] Example 2 integrates the projects distributed in various business systems and unifies them into the risk management system to provide risk management services, thereby realizing the management of various projects. At the same time, the project data of various projects are uniformly collected and an online item database is formed for automatic allocation and control.

[0088] Figure 6 Schematic diagram of the main process of the risk management method according to the third embodiment of the present invention. Figure 6 As shown, the risk management method of the embodiment of the present invention is used to perform risk query, which is convenient for managers to select items and requesters to participate in the project. Specifically, it includes the following steps:

[0089] Step S601: The front-end page sends the risk query request to the back-end. In the embodiment, the risk query request can be an item risk query request (used to query the risk information of the item) or a requester risk query request (used to query the risk information of the requester). For an item risk query request, the request includes the item ID of the item to be queried, the target item ID and the query time. For a requester risk query request, the request includes the item ID of the item to be queried and the target requester ID.

[0090] Among them, the query of item risk can be done through Figure 7 The item risk query page shown in the figure is implemented. Figure 7 The item risk query page includes an item name selection box, an item ID input box, and a query button. The administrator can select the item name, enter the skuid, and click the query button on the item risk query page to generate an item risk query request.

[0091] The requester risk can be queried through Figure 8 The requester risk query page is implemented as shown. Figure 8 The requester risk query page includes a project name selection box, a requester ID input box, and a query button. The administrator can select a project name on the requester risk query page, enter the venderid, and click the query button to generate a requester risk query request.

[0092] It is understandable that the above query operation can be performed by importing queries individually or in batches.

[0093] Step S602: The background performs risk verification according to the risk query request. For the item risk query request, the implementation process of this step is: first, according to the target item identification, query the third project participation information of the corresponding target item and the fourth project participation information of the target requester to which the target item belongs, then obtain the corresponding verification rule according to the project identification of the item to be queried, and then perform risk verification on the target requester and the target item according to the third project participation information, the fourth project participation information and the obtained verification rule to obtain the risk information of the target item.

[0094] The third project participation information is used to record the information of the target item participating in the project, which may include the target item's lock status, lock time, lock project, etc. The fourth project participation information is used to record the information of the target requester participating in the project, which may include the number of times the target requester participates in the project in different time dimensions, the amount of subsidy received by the target requester, the number of items participating in the project, and other fatigue value data.

[0095] The verification rules of this step are duplication rules and fatigue value rules. When performing risk verification, it is necessary to perform duplication verification on the items according to the third item participation information and duplication rules to obtain the duplication verification result; and perform fatigue value verification on the requesting party according to the fourth item participation information and fatigue value rules to obtain the fatigue value verification result.

[0096] The duplication check is to determine whether the query time of the target item conflicts with the lock period of the item in other items. The fatigue value check is to compare the fatigue value data in the fourth item participation information with the threshold value. The implementation process of the duplication check and fatigue value check is shown in step S305, which will not be repeated here.

[0097] Step S603: The backend sends a risk identification request to the risk identification system. The backend calls the risk identification service by carrying the risk identification request in the call request. In the embodiment, if the risk information of the item is queried, the risk identification request may include the item identification; if the risk information of the requesting party is queried, the risk identification request may include the requesting party identification.

[0098] Step 604: The risk identification system returns the risk tag corresponding to the item identification and the risk tag corresponding to the requester identification to the backend. If the risk information of the item is queried, the risk tag corresponding to the item identification is returned; if the risk information of the requester is queried, the risk tag corresponding to the requester identification is returned.

[0099] Step S605: The backend generates a risk query result based on the risk verification result and the risk tag, and returns it to the frontend page. If the risk verification result is passed and the risk tag is empty, the risk query result is passed; if the repetition verification fails, the risk query result includes the repeated project ID and item ID; if the fatigue value verification fails, the risk query result includes the rules that failed in the fatigue value rules; if the risk tag is not empty, the risk query result includes the risk tag.

[0100] Step S606: The front-end page constructs a preliminary selection item pool according to the risk query result, and sends the preliminary selection item pool to the business system. Items with a risk query result of passing are added to the preliminary selection item pool.

[0101] Step S607: The business system configures the items participating in the project based on the preliminary item pool. The specific configuration includes item identification, project identification, online time, etc. Based on the above query operation, the items configured to participate in the project of the business system can be items that have been identified as risky, meet the verification rules, and are low-risk items. In an optional embodiment, items that do not meet the verification rules and fail to pass the risk identification, and requesters (i.e., risky items, risky requesters) can be prompted through a prompt box.

[0102] Fig. 9 Schematic diagram of the main process of the risk management method according to the fourth embodiment of the present invention. Fig. 9 As shown, the risk management method of the embodiment of the present invention is used to white-mark the risk items and risk requesting parties queried in the third embodiment, and specifically includes the following steps:

[0103] Step S901: The business line system sends a whitelisting request to the front-end page. The whitelisting request may include the risk item requested to be added to the whitelist, the risk requesting party, the whitelisting cycle, the whitelisting reason, etc.

[0104] Step S902: The front page configures a whitelist according to the whitelisting request and stores the whitelist in the whitelisting database. The front page searches for the whitelisting records of the item or requester through the whitelisting page and can whitelist the item or requester under a specific project.

[0105] For example, if you need to whiten an item, the configuration items are whiten type (i.e., item whiten), item ID, project name, and whiten period. For example, if you need to whiten a requester, the configuration items are whiten type (i.e., requester whiten), requester ID, project name, and whiten period.

[0106] Step S903: The business system uses the project ID, item ID and online cycle as input parameters to call the background judgment interface. The specific implementation of this step is shown in step S304, which will not be repeated here.

[0107] Step S904: The judgment interface queries the whitelist to determine whether the item corresponding to the item identifier is in the whitelisting period. In an embodiment, the judgment interface can query the whitelist in the whitelisting database with the project identifier, item identifier, requester identifier and online time as input parameters to determine whether the item corresponding to the item identifier is in the whitelisting period.

[0108] The determination process is as follows: determine whether the item identifier exists in the whitelist or whether there is a requester identifier corresponding to the item identifier. If the item identifier exists in the whitelist or the requester identifier exists, and the online cycle belongs to the whitelisting cycle, then the item is in the whitelisting cycle.

[0109] If neither the item ID nor the requester ID exists in the whitelist, the item is not in the whitelist period. If the item ID or the requester ID exists in the whitelist, but the online period does not belong to the whitelist period, the item is not in the whitelist period.

[0110] Step S904: The judgment interface generates a risk verification result based on the determination result and sends it to the business system. During the whitelisting period, the items and requesting parties added to the whitelist under the project only return verification results. During the non-whitelisting period, the process of generating the risk verification result is described in Example 2, which will not be repeated here.

[0111] Fig.10 Schematic diagram of the main modules of the risk management device according to an embodiment of the present invention. Fig.10 As shown, the risk management device 1000 of the embodiment of the present invention mainly includes:

[0112] The query module 1001 receives a project participation request, and queries the first project participation information of the corresponding item and the second project participation information of the requesting party to which the item belongs according to the item identification in the project participation request. The project participation request includes the project identification, item identification and online cycle of the project to be participated in. The project identification is used to uniquely identify the project, the item identification is used to uniquely identify the item, and the online cycle is the time from the item being online to being offline. The requesting party to which the item belongs is the owner of the item before the transaction.

[0113] After receiving the project participation request, the first project participation information corresponding to the item identifier and the second project participation information of the requester to which the item belongs are queried from the database. In the embodiment, the first project participation information is used to record the information of the item participating in the project, which may include the locking status, locking time, locking project and other information of the item. The second project participation information is used to record the information of the requester participating in the project, which may include the number of times the requester participates in the project in different time dimensions, the amount of subsidy obtained by the requester, the number of items participating in the project and other fatigue value data.

[0114] The acquisition module 1002 is used to acquire the corresponding verification rules according to the project identification of the project to be participated. Different projects have different requirements for risk control, so the corresponding verification rules can be configured in advance based on the project requirements. After receiving the project participation request, the corresponding verification rules can be acquired according to the project identification. The verification rules are used to limit the number of projects that an item can participate in at the same time during the online cycle, and to limit the frequency of the requester participating in the project.

[0115] The verification module 1003 is used to perform risk verification on the item and the requester according to the first project participation information, the second project participation information and the verification rule, and allow the item to participate in the project to be participated in after the verification is determined to be passed. In the embodiment, the verification rules are divided into repetition rules and fatigue value rules, wherein the repetition rule is used to limit the number of projects that the item can participate in at the same time during the online cycle, and the fatigue value rule is used to limit the frequency of the requester participating in the project.

[0116] When performing risk verification, the item needs to be verified for duplication according to the first project participation information and duplication rules to obtain duplication verification results; the requester needs to be verified for fatigue value according to the second project participation information and fatigue value rules to obtain fatigue value verification results. After both duplication verification and fatigue value verification are passed, the item is allowed to participate in the project to be participated.

[0117] In addition, the risk management device 1000 of the embodiment of the present invention may also include: a locking module, a risk identification module, a configuration module, a judgment module, a first query module and a second query module ( Fig.10 The locking module is used to determine that the duplication check of the item has passed, and when the item is online or a locking instruction is received, the item is locked, and the locking state is updated to locked; when the item is offline, the locking time expires, or an unlocking instruction is received, the item is unlocked, and the locking state is updated to unlocked.

[0118] The risk identification module is used to call the risk identification service with the item identification and the requester identification as input parameters to obtain the risk tag of the item and the risk tag of the requester. The configuration module is used to configure a whitelist for the project to be participated in.

[0119] A judgment module is used to judge whether there is a whitened item identifier identical to the item identifier, or a whitened requester identifier identical to the requester identifier in the whitelist; if there is a whitened item identifier identical to the item identifier in the whitelist, and the online cycle belongs to the whitened cycle, then determine that the verification is passed; if there is a whitened requester identifier identical to the requester identifier in the whitelist, and the online cycle belongs to the whitened cycle, then determine that the verification is passed

[0120] The first query module is used to receive an item risk query request, and query the third project participation information of the corresponding target item and the fourth project participation information of the target requester to which the target item belongs according to the target item identifier in the item risk query request; wherein the item risk query request includes the project identifier of the item to be queried, the target item identifier and the query time; according to the project identifier of the item to be queried, the corresponding verification rule is obtained; wherein the verification rule is used to limit the number of projects in which the target item participates at the same time within the query time, and to limit the frequency of the projects in which the target requester participates; according to the third project participation information, the fourth project participation information and the obtained verification rule, the target requester and the target item are subjected to risk verification to obtain the risk information of the target item.

[0121] The second query module is used to receive a risk query request from a requesting party, wherein the risk query request from the requesting party includes a project identifier of the project to be queried and an identifier of a target requesting party; and return risk information obtained by performing risk verification on the target requesting party.

[0122] From the above description, it can be seen that by specifying the parameters of the project participation request as the project ID, item ID and online cycle, the verification rules corresponding to the project ID can be used before the project goes online to automatically perform risk verification on the items and the requester, thereby achieving unified management and control of different projects, while improving verification accuracy and efficiency, and avoiding duplicate subsidies and resource tilt.

[0123] Fig.11 An exemplary system architecture 1100 is shown to which the risk management method or risk management apparatus according to the embodiment of the present invention can be applied.

[0124] like Fig.11 As shown, the system architecture 1100 may include a business server 1101 , networks 1102 , 1104 , 1106 , 1107 , a front-end page 1103 , a back-end server 1105 and a risk control server 1108 .

[0125] The network 1102 is used to provide a medium for the communication link between the business server 1101 and the front-end page 1103; the network 1104 is used to provide a medium for the communication link between the front-end page 1103 and the back-end server 1105; the network 1106 is used to provide a medium for the communication link between the business server 1101 and the back-end server 1105; the network 1107 is used to provide a medium for the communication link between the back-end server 1105 and the risk control server 1108. The networks 1102, 1104, 1106, and 1107 may include various connection types, such as wired, wireless communication links, or optical fiber cables, etc.

[0126] The business server 1101, the front-end page 1103, the back-end server 1105 and the risk control server 1108 may be servers that provide various services. Among them, the risk control server 1108 is used for risk identification. The back-end server 1105 may be a back-end management server that processes the call request sent by the administrator using the business server 1101. The back-end management server can query project participation information, obtain verification rules, perform risk verification, and feedback the processing results (e.g., whether the item is allowed to participate in the project) to the business server.

[0127] It should be noted that the risk management method provided in the embodiment of the present application is generally executed by the backend server 1105 , and accordingly, the risk management device is generally arranged in the backend server 1105 .

[0128] It should be understood that Fig.11 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 implementation requirements.

[0129] According to an embodiment of the present invention, the present invention also provides an electronic device and a computer-readable medium.

[0130] The electronic device of the present invention comprises: one or more processors; a storage device for storing one or more programs, and when the one or more programs are executed by the one or more processors, the one or more processors implement a risk management method of an embodiment of the present invention.

[0131] The computer-readable medium of the present invention stores a computer program thereon, and when the program is executed by a processor, a risk management method of an embodiment of the present invention is implemented.

[0132] Reference below Fig.12 , which shows a schematic diagram of the structure of a computer system 1200 suitable for implementing an electronic device of an embodiment of the present invention. Fig.12 The electronic device shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present invention.

[0133] like Fig.12As shown, the computer system 1200 includes a central processing unit (CPU) 1201, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 1202 or a program loaded from a storage part 1208 into a random access memory (RAM) 1203. In the RAM 1203, various programs and data required for the operation of the computer system 1200 are also stored. The CPU 1201, the ROM 1202, and the RAM 1203 are connected to each other via a bus 1204. An input / output (I / O) interface 1205 is also connected to the bus 1204.

[0134] The following components are connected to the I / O interface 1205: an input section 1206 including a keyboard, a mouse, etc.; an output section 1207 including a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker, etc.; a storage section 1208 including a hard disk, etc.; and a communication section 1209 including a network interface card such as a LAN card, a modem, etc. The communication section 1209 performs communication processing via a network such as the Internet. A drive 1210 is also connected to the I / O interface 1205 as needed. A removable medium 1211, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed on the drive 1210 as needed, so that a computer program read therefrom is installed into the storage section 1208 as needed.

[0135] In particular, according to the embodiments disclosed in the present invention, the process described in the main step diagram above can be implemented as a computer software program. For example, the embodiments disclosed in the present invention include a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program includes a program code for executing the method shown in the main step diagram. In such an embodiment, the computer program can be downloaded and installed from the network through the communication part 1209, and / or installed from the removable medium 1211. When the computer program is executed by the central processing unit (CPU) 1201, the above-mentioned functions defined in the system of the present invention are executed.

[0136] It should be noted that the computer-readable medium shown in the present invention may be a computer-readable signal medium or a computer-readable storage medium or any combination of the above two. The computer-readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, 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), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present invention, a computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in combination with an instruction execution system, device or device. In the present invention, a computer-readable signal medium may include a data signal propagated in a baseband or as part of a carrier wave, which carries a computer-readable program code. This propagated data signal may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. Computer-readable signal media may also be any computer-readable medium other than computer-readable storage media, which may send, propagate or transmit a program for use by or in conjunction with an instruction execution system, apparatus or device. The program code contained on the computer-readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wire, optical cable, RF, etc., or any suitable combination of the above.

[0137] The flow chart and block diagram in the accompanying drawings illustrate the possible architecture, function and operation of the system, method and computer program product according to various embodiments of the present invention. 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.

[0138] The modules involved in the embodiments of the present invention may be implemented in software or hardware. The modules described may also be set in a processor. For example, they may be described as: a processor includes a query module, an acquisition module, and a verification module. The names of these modules do not constitute limitations on the modules themselves in certain cases. For example, the query module may also be described as "a module that receives a project participation request, queries the first project participation information of the corresponding item according to the item identifier in the project participation request, and queries the second project participation information of the requesting party to which the item belongs".

[0139] As another aspect, the present invention also provides a computer-readable medium, which may be included in the device described in the above embodiment; or it may exist independently and not be assembled into the device. The above computer-readable medium carries one or more programs, and when the above one or more programs are executed by a device, the device includes: receiving a project participation request, querying the first project participation information of the corresponding item and the second project participation information of the requesting party to which the item belongs according to the item identification in the project participation request; wherein the project participation request includes the project identification of the project to be participated, the item identification and the online cycle; according to the project identification of the project to be participated, obtaining the corresponding verification rules; wherein the verification rules are used to limit the number of projects that the item can participate in at the same time during the online cycle, and limit the frequency of the requesting party participating in the project; according to the first project participation information, the second project participation information and the verification rules, the item and the requesting party are subjected to risk verification, and after determining that the verification passes, the item is allowed to participate in the project to be participated.

[0140] According to the technical solution of the embodiment of the present invention, by specifying the parameters of the project participation request as the project ID, item ID and online cycle, the verification rules corresponding to the project ID can be used to automatically perform risk verification on the items and the requester before the project goes online, thereby achieving unified management and control of different projects, while improving verification accuracy and efficiency, and avoiding duplicate subsidies and resource tilt.

[0141] The above product can execute the method provided by the embodiment of the present invention, and has the functional modules and beneficial effects corresponding to the execution method. For technical details not described in detail in this embodiment, please refer to the method provided by the embodiment of the present invention.

[0142] The above specific implementations do not constitute a limitation on the protection scope of the present invention. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions may occur depending on design requirements and other factors. Any modification, equivalent substitution and improvement made within the spirit and principle of the present invention shall be included in the protection scope of the present invention.

Claims

1. A risk management method, characterized in that: include: Receive a project participation request, and query first project participation information of the corresponding item and second project participation information of the requesting party to which the item belongs according to the item identifier in the project participation request; wherein the project participation request includes the project identifier of the project to be participated, the item identifier, and the online period; According to the project identifier of the project to be participated in, the corresponding verification rule is obtained; wherein the verification rule is used to limit the number of projects that the item can participate in at the same time during the online cycle, and to limit the frequency of the requesting party participating in the project; According to the first project participation information, the second project participation information and the verification rule, a risk verification is performed on the item and the requesting party, and after it is determined that the verification passes, the item is allowed to participate in the project to be participated in.

2. The method according to claim 1, characterized in that The verification rules include a repetition rule and a fatigue value rule; the repetition rule is used to limit the number of projects that the item can participate in at the same time during the online cycle; the fatigue value rule is used to limit the frequency of the requester participating in the project, including setting a threshold value of the fatigue value indicator; The performing risk verification on the item and the requesting party according to the first project participation information, the second project participation information and the verification rule includes: Performing duplication verification on the item according to the first project participation information and the duplication rule to obtain a duplication verification result; The fatigue value data in the second project participation information is compared with the threshold to obtain a fatigue value verification result; wherein the fatigue value data is statistically calculated according to the fatigue value index.

3. The method according to claim 2, characterized in that The performing duplication check on the item according to the first project participation information and the duplication rule to obtain a duplication check result includes: Determining, according to the first project participation information, a locking status of the item in the online cycle; If the locking state is locked, the repeatability check fails; if the locking state is unlocked, the repeatability check passes.

4. The method according to claim 3, characterized in that The method further comprises: Determining that the duplication check of the item passes, locking the item when the item goes online or receives a locking instruction, and updating the locking state to locked; When the item is offline, the locking time expires, or an unlocking instruction is received, the item is unlocked and the locking state is updated to unlocked.

5. The method according to claim 2, characterized in that: The fatigue value indicator includes any one or more of: the number of times the requester participates in the project within a set time period, the number of items the requester participates in the project within the time period, and the amount of subsidy to the requester within the time period.

6. The method according to claim 1, characterized in that The method further comprises: Using the item identifier and the requester identifier as input parameters, calling the risk identification service to obtain the risk tag of the item and the risk tag of the requester; The determining that the verification is passed includes: the risk tag is empty and the risk verification is passed.

7. The method according to claim 1, characterized in that The method further comprises: configuring a whitelist for the project to be participated in; wherein the whitelist comprises one or more of a whitelist item identifier and a whitelist requester identifier, and a whitelist period; Before the step of performing risk verification on the item and the requesting party, the method further includes: Determine whether there is a whitelisted item identifier that is identical to the item identifier, or a whitelisted requester identifier that is identical to the requester identifier in the whitelist; If there is a whitelisted item identifier that is identical to the item identifier in the whitelist, and the online period belongs to the whitelisted period, determining that the verification is passed; If there is a whitelist requesting party identifier that is the same as the requesting party identifier in the whitelist, and the online period belongs to the whitelist period, determining that the verification is passed; The risk verification of the item and the requesting party includes: If there is no whitened item identifier identical to the item identifier in the whitelist, and there is no whitened requester identifier identical to the requester identifier, then risk verification is performed on the item and the requester; If there is a whitelisted requesting party identifier that is identical to the requesting party identifier in the whitelist, or there is a whitelisted requesting party identifier that is identical to the requesting party identifier but the online period does not belong to the whitelisting period, a risk check is performed on the item and the requesting party.

8. The method according to any one of claims 1 to 7, characterized in that: The method further comprises: receiving an item risk query request, and querying, according to a target item identifier in the item risk query request, third project participation information of the corresponding target item and fourth project participation information of the target requester to which the target item belongs; wherein the item risk query request includes a project identifier of the item to be queried, a target item identifier, and a query time; According to the project identifier of the project to be queried, a corresponding verification rule is obtained; wherein the verification rule is used to limit the number of projects that the target item can participate in at the same time within the query time, and to limit the frequency of the projects that the target requester can participate in; According to the third project participation information, the fourth project participation information and the obtained verification rule, risk verification is performed on the target requester and the target item to obtain risk information of the target item.

9. The method according to claim 8, characterized in that The method further comprises: Receiving a risk query request from a requesting party, wherein the risk query request from the requesting party includes a project identifier of the project to be queried and a target requesting party identifier; Return the risk information obtained by performing risk verification on the target requester.

10. A risk management device, characterized in that: include: A query module receives a project participation request, and queries the first project participation information of the corresponding item and the second project participation information of the requesting party to which the item belongs according to the item identifier in the project participation request; wherein the project participation request includes the project identifier of the project to be participated, the item identifier and the online period; An acquisition module, used for acquiring corresponding verification rules according to the project identifier of the project to be participated in; wherein the verification rules are used to limit the number of projects that the item can participate in at the same time during the online cycle, and to limit the frequency of the requester participating in the project; A verification module is used to perform risk verification on the item and the requesting party according to the first project participation information, the second project participation information and the verification rule, and allow the item to participate in the project to be participated in after determining that the verification passes.

11. An electronic device, characterized in that: include: 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 implement the method according to any one of claims 1 to 9.

12. A computer readable medium having a computer program stored thereon, characterized in that: When the program is executed by a processor, the method according to any one of claims 1 to 9 is implemented.

Images