CN113240266A

CN113240266A - Risk management method and device

Info

Publication number: CN113240266A
Application number: CN202110512098.9A
Authority: CN
Inventors: 蔡炫溥; 郑清松; 朱林华; 张臻; 弓思源; 蒋奎; 伍怡新; 丘涌强
Original assignee: Beijing Jingdong Century Trading Co Ltd; Beijing Wodong Tianjun Information Technology Co Ltd
Current assignee: Beijing Jingdong Century Trading Co Ltd; Beijing Wodong Tianjun Information Technology Co Ltd
Priority date: 2021-05-11
Filing date: 2021-05-11
Publication date: 2021-08-10

Abstract

The invention discloses a risk management method and device, and relates to the technical field of computers. One embodiment of the method comprises: receiving a project participation request, and inquiring first project participation information of a corresponding article and second project participation information of a requester to which the article belongs according to an article identifier in the project participation request; acquiring a corresponding verification rule according to the project identification of the project to be participated; the verification rule is used for limiting the number of items participating in the project simultaneously in the online period and limiting the frequency of the items participating in the project of the requester; and carrying out risk verification on the article and the requesting party according to the first project participation information, the second project participation information and the verification rule, and allowing the article to participate in the project to be participated after the verification is determined to be passed. According to the method, the risk check is automatically carried out on the article and the requester, the unified management control of different projects is realized, the check accuracy and efficiency are improved, and repeated subsidy and resource inclination are avoided.

Description

Risk management method and device

Technical Field

The invention relates to the technical field of computers, in particular to a risk management method and device.

Background

In the prior art, a server usually provides a plurality of projects for a partner to join, and meanwhile, the server can subsidize own assets to the partner so as to promote the transaction between the partner and a user. In order to ensure the safety of assets, a server side generally controls risks of each project in three links. Specifically, before the project is on-line, a partner (namely a requester) requesting to join the project and the article are subjected to qualification admission check; and after the project is on-line, identifying the risk of the transaction user, and after the project is off-line, identifying the false transaction.

In the process of implementing the invention, the prior art at least has the following problems:

because the difference between projects is large, a service party can adopt an independent service system to bear the projects during development, so that the unified management control can not be carried out on all the projects; the risk transaction is intercepted only after the project is on line, and the transaction risk is large; the requester and the goods are manually checked, so that the accuracy is low, the efficiency is low, the risk problems of repeated subsidy, resource inclination and the like are easily caused, and the resource waste is caused.

Disclosure of Invention

In view of this, embodiments of the present invention provide a risk management method and apparatus, where parameters of a project participation request are defined as a project identifier, an article identifier, and an online period, and before the project is online, a check rule corresponding to the project identifier may be used to automatically perform risk check on the article and a requester, so as to implement unified management control on different projects, improve check accuracy and efficiency, and avoid repeated subsidies and resource tilt.

To achieve the above object, according to an aspect of an embodiment of the present invention, there is provided a risk management method.

The risk management method of the embodiment of the invention comprises the following steps: receiving a project participation request, and inquiring first project participation information of a corresponding article and second project participation information of a requester to which the article belongs according to an article identifier in the project participation request; the project participation request comprises a project identifier of a project to be participated, the item identifier and an online period; acquiring a corresponding verification rule according to the project identification of the project to be participated; wherein the check rule is used for limiting the number of items participating in the online period and limiting the frequency of items participating in the requester; and performing risk verification on the article and the requester according to the first project participation information, the second project participation information and the verification rule, and allowing the article to participate in the project to be participated after the verification is determined to be passed.

Optionally, the check rule includes a repetition degree rule and a fatigue value rule; the repeatability rule is used for limiting the number of items participating in the online period at the same time; the fatigue value rule is used for limiting the frequency of the requester participating in the project, and comprises setting a threshold value of a fatigue value index; the performing risk verification on the item and the requester according to the first item participation information, the second item participation information and the verification rule includes: according to the first project participation information and the repeatability rule, carrying out the repeatability verification on the article to obtain an repeatability verification result; comparing the fatigue value data in the second item participation information with the threshold value to obtain a fatigue value check result; wherein the fatigue value data is counted according to the fatigue value index.

Optionally, the performing a duplication degree check on the article according to the first item participation information and the duplication degree rule to obtain a duplication degree check result includes: determining the locking state of the article in the online period according to the first project participation information; if the locking state is locked, the repeatability check fails; and if the locking state is unlocked, the repeatability check is passed.

Optionally, the method further comprises: determining that the repeatability of the article passes verification, locking the article when the article is on line or a locking instruction is received, and updating the locking state to be locked; and when the article is off-line, the locking time expires or an unlocking instruction is received, unlocking the article, and updating the locking state to be unlocked.

Optionally, the fatigue value indicator comprises: and setting any one or more of the number of times of the requester participating in the item in the time period, the quantity of the items of the requester participating in the item in the time period, and the subsidy amount of the requester in the time period.

Optionally, the method further comprises: taking the article identification and the requester identification as input parameters, and calling a risk identification service to obtain a risk label of the article and a risk label of the requester; the determining that the check passes includes: the risk label is empty and the risk check passes.

Optionally, the method further comprises: configuring a white list for the items to be participated; wherein the white list comprises one or more of a whitelisted item identifier and a whitelisted requestor identifier, and a whitelisted period; prior to the step of risk-checking the item and the requestor, the method further comprises: judging whether a white list has a white item identifier which is the same as the item identifier or a white requester identifier which is the same as the requester identifier; if a white added article identifier which is the same as the article identifier exists in the white list and the online period belongs to the white added period, determining that the verification is passed; if the white list has a whitening requester identifier which is the same as the requester identifier, and the online period belongs to the whitening period, determining that the verification is passed; the risk checking the item and the requester comprises: if the white list does not have a whitened article identifier which is the same as the article identifier and does not have a whitened requester identifier which is the same as the requester identifier, performing risk verification on the article and the requester; and if the white list has a whitening requester identifier which is the same as the requester identifier, or has a whitening requester identifier which is the same as the requester identifier, but the online period does not belong to the whitening period, performing risk verification on the article and the requester.

Optionally, the method further comprises: receiving an item risk query request, and querying third item participation information of a corresponding target item and fourth item participation information of a target requester to which the target item belongs according to a target item identifier in the item risk query request; the item risk query request comprises an item identifier of an item to be queried, a target item identifier and query time; acquiring a corresponding check rule according to the item identifier of the item to be inquired; wherein the verification rule is used for limiting the number of items simultaneously participated in by the target item in the query time and limiting the frequency of items participated in by the target requester; and performing risk verification on the target requester and the target object according to the third project participation information, the fourth project participation information and the obtained verification rule to obtain risk information of the target object.

Optionally, the method further comprises: receiving a requester risk query request, wherein the requester risk query request comprises an item identifier of the item to be queried and a target requester identifier; and returning risk information obtained by performing risk verification on the target requester.

To achieve the above object, according to another aspect of the embodiments of the present invention, there is provided a risk management device.

The risk management device of the embodiment of the invention comprises: the query module is used for receiving a project participation request, and querying first project participation information of a corresponding project and second project participation information of a requester to which the project belongs according to an article identifier in the project participation request; the project participation request comprises a project identifier of a project to be participated, the item identifier and an online period; the acquisition module is used for acquiring a corresponding check rule according to the project identifier of the project to be participated; wherein the check rule is used for limiting the number of items participating in the online period and limiting the frequency of items participating in the requester; and the checking module is used for carrying out risk checking on the article and the requester according to the first project participation information, the second project participation information and the checking rule, and allowing the article to participate in the project to be participated after the checking is determined to be passed.

Optionally, the check rule includes a repetition degree rule and a fatigue value rule; the repeatability rule is used for limiting the number of items participating in the online period at the same time; the fatigue value rule is used for limiting the frequency of the requester participating in the project, and comprises setting a threshold value of a fatigue value index; the checking module is further configured to perform duplication degree checking on the article according to the first project participation information and the duplication degree rule to obtain a duplication degree checking result; comparing the fatigue value data in the second item participation information with the threshold value to obtain a fatigue value check result; wherein the fatigue value data is counted according to the fatigue value index.

Optionally, the verification module is further configured to determine, according to the first project participation information, a locking state of the article in the online period; if the locking state is locked, the repeatability check fails; and if the locking state is unlocked, the repeatability check is passed.

Optionally, the apparatus further comprises: the locking module is used for determining that the repeatability of the article passes the verification, locking the article when the article is on-line or receives a locking instruction, and updating the locking state to be locked; and when the article is off-line, the locking time expires or an unlocking instruction is received, unlocking the article, and updating the locking state to be unlocked.

Optionally, the apparatus further comprises: the risk identification module is used for taking the article identifier and the requester identifier as entries, calling a risk identification service and obtaining a risk label of the article and a risk label of the requester; the checking module is also used for the risk label is empty and the risk check is passed.

Optionally, the apparatus further comprises: the configuration module is used for configuring a white list for the item to be participated; wherein the white list comprises one or more of a whitelisted item identifier and a whitelisted requestor identifier, and a whitelisted period; the device further comprises: the judging module is used for judging whether a whitened article identifier which is the same as the article identifier exists in the white list or not, or a whitened requester identifier which is the same as the requester identifier exists in the white list; if a white added article identifier which is the same as the article identifier exists in the white list and the online period belongs to the white added period, determining that the verification is passed; if the white list has a whitening requester identifier which is the same as the requester identifier, and the online period belongs to the whitening period, determining that the verification is passed; the checking module is further configured to perform risk checking on the item and the requester if a whited item identifier that is the same as the item identifier does not exist in the white list and a whited requester identifier that is the same as the requester identifier does not exist; and if the white list has a whitening requester identifier which is the same as the requester identifier, or has a whitening requester identifier which is the same as the requester identifier, but the online period does not belong to the whitening period, performing risk verification on the article and the requester.

Optionally, the apparatus further comprises: the first query module is used for receiving an item risk query request, and querying third item participation information of a corresponding target item and fourth item participation information of a target requester to which the target item belongs according to a target item identifier in the item risk query request; the item risk query request comprises an item identifier of an item to be queried, a target item identifier and query time; acquiring a corresponding check rule according to the item identifier of the item to be inquired; wherein the verification rule is used for limiting the number of items simultaneously participated in by the target item in the query time and limiting the frequency of items participated in by the target requester; and performing risk verification on the target requester and the target object according to the third project participation information, the fourth project participation information and the obtained verification rule to obtain risk information of the target object.

Optionally, the apparatus further comprises: the second query module is used for receiving a requester risk query request, wherein the requester risk query request comprises an item identifier of the item to be queried and a target requester identifier; and returning risk information obtained by performing risk verification on the target requester.

To achieve the above object, according to still another aspect of embodiments of the present invention, there is provided an electronic apparatus.

An electronic device of an embodiment of the present invention includes: one or more processors; a storage device, configured to store one or more programs, which when executed by the one or more processors, cause the one or more processors to implement a risk management method according to an embodiment of the present invention.

To achieve the above object, according to still another aspect of embodiments of the present invention, there is provided a computer-readable medium.

A computer-readable medium of an embodiment of the present invention has stored thereon a computer program that, when executed by a processor, implements a risk management method of an embodiment of the present invention.

One embodiment of the above invention has the following advantages or benefits: the parameters of the project participation request are specified as the project identification, the article identification and the online period, and the risk verification can be automatically carried out on the article and the requester by using the verification rule corresponding to the project identification before the project is online, so that the unified management control of different projects is realized, the verification accuracy and efficiency are improved, and repeated subsidy and resource inclination are avoided.

The fatigue value of the requester is defined using a threshold value, preventing the requester from frequently participating in the project resulting in resources being concentrated on the requester. The method and the device have the advantages that the duplication degree check is carried out on the articles based on the locking mechanism, and the same article is prevented from participating in multiple projects to cause repeated subsidy. The locking and unlocking device has the advantages that multiple modes are provided for locking and unlocking the articles, and the flexibility is good. And the fatigue value index is configured, so that the fatigue value of the requester is conveniently checked.

The conventional risk identification, the fatigue value verification and the repeatability verification are carried out together, so that risk interception, repeated subsidy interception and fatigue value overproof interception can be carried out before the project is on-line. By configuring the white list for the project, in the whitening period, risk verification on the articles and the requesting party in the white list is not required. After receiving the risk inquiry request, determining the risk information of the article and the risk information of the requester, so that management personnel can select the article and the requester participating in the project conveniently.

Further effects of the above-mentioned non-conventional alternatives will be described below in connection with the embodiments.

Drawings

The drawings are included to provide a better understanding of the invention and are not to be construed as unduly limiting the invention. Wherein:

fig. 1 is a schematic diagram of the main steps of a risk management method according to a first embodiment of the present invention;

FIG. 2 is a system architecture diagram of a risk management method implementing an embodiment of the invention;

FIG. 3 is a schematic main flow chart of a risk management method according to a second embodiment of the present invention;

FIG. 4 is a schematic diagram of a rule configuration page of an embodiment of the invention;

FIG. 5 is a schematic diagram of a fatigue value rule configuration according to an embodiment of the present invention;

fig. 6 is a schematic main flow chart of a risk management method according to a third embodiment of the present invention;

FIG. 7 is a schematic diagram of an item risk query page of an embodiment of the present invention;

FIG. 8 is a schematic diagram of a requestor risk query page of an embodiment of the present invention;

fig. 9 is a schematic main flow chart of a risk management method according to a fourth embodiment of the present invention;

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

FIG. 11 is an exemplary system architecture diagram in which embodiments of the present invention may be employed;

FIG. 12 is a schematic diagram of a computer apparatus suitable for use in an electronic device to implement an embodiment of the invention.

Detailed Description

Exemplary embodiments of the present invention are described below with reference to the accompanying drawings, in which various details of embodiments of the invention are included to assist understanding, and which are to be considered as merely exemplary. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the invention. Also, descriptions of well-known functions and constructions are omitted in the following description for clarity and conciseness.

Fig. 1 is a schematic diagram of main steps of a risk management method according to a first embodiment of the present invention. As shown in fig. 1, the risk management method according to the embodiment of the present invention mainly includes the following steps:

step S101: receiving a project participation request, and inquiring first project participation information of a corresponding project and second project participation information of a requester to which the project belongs according to an article identifier in the project participation request. The project participation request comprises a project identifier, an article identifier and an online period of the project to be participated. The item identifier is used for uniquely identifying the item, the article identifier is used for uniquely identifying the article, and the online period is the time from the online to the offline of the article. The requester to which the item belongs is the owner of the item prior to the transaction.

After receiving the project participation request, inquiring first project participation information corresponding to the article identification and second project participation information of a requester to which the article belongs from the database. In an embodiment, the first item participation information is used for recording information of item participation items, and may include information of a locking state, a locking time, a locking item, and the like of an item. The second item participation information is used for recording information of the requester participating in the item, and may include fatigue value data such as the number of times of the requester participating in the item, subsidy amount obtained by the requester, and number of items participating in the item in different time dimensions.

Step S102: and acquiring a corresponding verification rule according to the project identifier of the project to be participated. Different projects have different requirements for risk control, so that corresponding verification rules can be configured in advance based on project requirements. After receiving the project participation request, the corresponding verification rule can be obtained according to the project identifier. The validation rules are used to limit the number of items participating in the project simultaneously during the online period, as well as to limit the frequency with which requesters participate in the project.

Step S103: and performing risk verification on the article and the requester according to the first project participation information, the second project participation information and the verification rule, and allowing the article to participate in the project to be participated after the verification is determined to be passed. In an embodiment, the verification rules are divided into a repeatability rule and a fatigue value rule, wherein the repeatability rule is used for limiting the number of items participating in the project simultaneously in the online period, and the fatigue value rule is used for limiting the frequency of the requester participating in the project.

When risk verification is carried out, the duplication degree of the article is verified according to the first project participation information and the duplication degree rule to obtain a duplication degree verification result; and according to the second project participation information and the fatigue value rule, performing fatigue value verification on the requester to obtain a fatigue value verification result. And after the repeatability check and the fatigue value check are passed, allowing the item to participate in the project to be participated.

Fig. 2 is a schematic diagram of a system architecture for implementing the risk management method according to an embodiment of the present invention. As shown in fig. 2, the system for implementing the risk management method in the embodiment of the present invention is composed of a presentation layer, a business layer, a service layer, and a data layer. The display layer is used for realizing interaction between the system and the user. The service layer is used for providing service access service, fatigue value statistical service and risk checking service. The data layer is used for accessing a database, such as MySQL and Redis databases.

The business layer comprises a business access module, an article risk module, a requester risk module and a risk whitening module. The service access module is used for accessing a service system and configuring a check rule. The article risk module is used for carrying out article risk identification, repeatability verification and fatigue value verification. And the requester risk module is used for identifying the risk of the requester and checking the fatigue value. And the risk whitening module is used for adding the designated risk articles and the risk requesting party into a white list.

Fig. 3 is a schematic main flow chart of a risk management method according to a second embodiment of the present invention. As shown in fig. 3, the risk management method according to the embodiment of the present invention is implemented by a risk management system, which includes a front-end page and a background, and mainly includes the following steps:

step S301: and the front-end page sends the configured verification rule to the background. The front-end page provides a rule configuration page, and after the administrator configures the check rule in the page, the front-end page sends the check rule to the background. The check rule includes a repetition degree rule and a fatigue value rule.

The duplication rules are used to limit the number of items participating in the project simultaneously during the online cycle. In an embodiment, the number of items participating in the online period at the same time can be limited to 1, that is, one item can participate in only one item in the online period. The configuration of the repetition rule can be realized on a front-end page or configured in a background.

The fatigue value rule is used to limit the frequency with which requesters participate in the item. In an embodiment, the frequency limitation of the requester participation item is achieved by setting a threshold value 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 item, the number of items the requester participates in the item, the number of times the item parameter item is entered, and the amount of subsidy to the requester for different time dimensions. The time dimension may be years, quarters, months, etc.

The configuration of the fatigue value rule needs to be realized on a rule configuration page of a front-end page. The following describes the arrangement of the fatigue value rule with reference to fig. 4 and 5.

As shown in fig. 4, the rule configuration page includes a project name selection box, an inquiry button, a newly added service fatigue value rule button, and a newly added global fatigue value rule button. After a specific project is selected in the project name selection box, the query button is clicked, and then the threshold value of each fatigue value index configured for the project can be obtained.

For example, the number of annual participation times of the project 1 is 3, the number of annual participation projects sku is 10, the annual subsidy amount is 1 ten-thousand yuan, the number of monthly participation times is 0, the number of monthly participation projects sku is 0, and the monthly subsidy amount is 0 yuan. After the threshold configured for the item is inquired, the threshold can be modified by clicking a modification rule button.

In addition, the rule configuration page further includes a new service scenario button, and new item information may be added by clicking the button, where the item information may include an item identifier, an item name, an item principal, and the like. And the administrator clicks the new service scene button, and after the new item is added, the item name in the item name selection box is correspondingly increased.

If a fatigue value rule needs to be newly added to a certain project, an administrator can select the project on the page, click a newly added service fatigue value rule button and a newly added global fatigue value rule button to realize the configuration of the fatigue value rule.

Taking clicking a newly added service fatigue value rule button as an example, after the front-end page monitors the clicking operation, the fatigue value rule setting page shown in fig. 5 is skipped to. The administrator may select or fill in a specific threshold value for the fatigue value indicator on the page. For example, the number of identical rendezvous does not exceed 5 in 2020. For another example, the amount of the same vended subsidy does not exceed 5000 yuan within 1 month of 2020.

Step S302: and synchronizing the article on-line information of the business system to the background on-line article database. Because the difference between projects is large, a service party can adopt an independent service system to bear the projects during development, and project data (including information of a request party participating in the projects and information of articles) can be stored in a database of each service system. The structure difference of different databases is large, and the data stored in the databases of all the business systems are synchronized to the online article database by unifying the data structures of the project data, so that the integration and unification of the isolated project data are realized, and a data source is provided for the subsequent fatigue value statistics and whitening treatment.

The on-line information of the article can be acquired through the following two ways:

the first method is as follows: defining a Message Queue (MQ) for synchronizing data, when an article is on-line in a service system, sending the article on-line information to the MQ, analyzing the content of the MQ by a background, and writing an analysis result into an article on-line table of an on-line article database. In an embodiment, the item online table includes a service system identifier (such as a service system name), a project identifier, a requester identifier, an item sku (stock keeping unit), an item spu (standard product unit), and an online period.

In an optional embodiment, the background defines the format of the MQ, and when an online article is newly added, information such as an item identifier, sku, an online period and the like is sent to the MQ; when the article online information is changed, sending the changed item identification, sku and the changed online period; and when the article is off-line, sending the original item identification, sku, the original on-line period and the off-line identification.

The second method comprises the following steps: when the service system calls a judgment interface of the background, the background actively scans a table of a database of the service system background for storing online article information, and if the data is determined to be updated, the online article database updates corresponding data. The table scanning means that the background reads the full data of the database at set time intervals, compares the full data with the online article database, and inserts newly added data if the newly added data exist; if the existing data is updated, updating the data; and if the existing data is more than the data of the business system, modifying the state of the excessive articles to be offline.

Step S303: and when the online article database is updated, the background locks the articles and stores the locking data into an article locking state table of the article lock database. In an embodiment, the item lock status table (i.e., the first item information) includes a lock status, a lock period, a lock item, and an item identifier (e.g., a skiid, a spuid). The step is used for automatically locking the articles on line when the articles are on line, wherein the locking state is locked, and the locking period is the article on-line period.

In an optional embodiment, the item may also be manually locked on an item risk query page in the background (that is, an administrator clicks a locking button on the item risk query page to trigger generation of a locking instruction, so as to lock the item). The different locking modes (automatic locking and manual locking) may intersect.

The locking mode is automatic locking, unlocking and locking period changing on an item risk inquiry page cannot be realized, and automatic unlocking can be realized only when the item is offline and synchronized to an online item database or the locking time is due. The locking mode is manually locked, and an unlocking button can be clicked on an article risk inquiry page to realize manual unlocking. The locking mode is manually locked, and a locking time changing button can be clicked on an item risk inquiry page to realize locking period updating.

Step S304: and the business system takes the item identification, the article identification and the online period as the input parameters and calls a judgment interface of the background. The judgment interface is used for verifying whether the articles transmitted by the business system can participate in the corresponding project. The verification content comprises the following steps: whether the risk exists, whether the fatigue value exceeds the standard or not and whether the patch is repeatedly applied or not. And when all the checks pass, judging that the interface returns that the checks pass, otherwise, judging that the returned checks fail.

The service system calls the judgment interface by carrying the project participation request in the call request. The item participation request comprises an item identification, an item identification and an online period. The business system can call the judgment interface in the registration link of the requester and the formal online link of the article. If the interface returns that the verification fails, prompt information that the registration of the requester fails or the article does not pass on the line can be output.

Step S305: and the background checks the risk according to the input parameters input by the service system. The risk check of this step includes a repeatability check and a fatigue value check. The following description will be made separately.

And (3) checking the repeatability: when the service system calls the judgment interface, the judgment interface takes the item identifier, the article identifier and the online period as the input parameters, an article lock database is inquired, and if the online period of the article transmitted by the service system is not in conflict with the locking period of the article by other items, the repeatability check is passed; otherwise, the duplication check fails.

In the embodiment, the locking state of the article in the online period can be inquired, and if the locking state is locked, the repeatability check fails; if the locked state is unlocked, the duplication degree check passes.

For example, item 1 is online in item 1, the online period is 1 month and 1 day to 1 month and 10 days, the background starts to lock the item under the item in 1 month and 1 day, and the locking period is 1 month and 1 day to 1 month and 10 days. If the item 1 is also selected in the item 2, the business system calls the judgment interface to perform duplication check on the item 1 by 5 days to 20 days in 1 month, the item is locked by the item 1 by 1 day to 10 days in 1 month, the on-line period conflicts with the locking period, and the check is returned to fail.

Checking a fatigue value: and synchronizing the online article database to a data mart, associating settlement data of a settlement system, counting fatigue value data of a requester participating in a project according to the fatigue value index, and storing the fatigue value data in a fatigue information table of a fatigue value database. In an embodiment, the fatigue information table includes subsidy amounts, requester participation times, item participation times, and item identifications for different time dimensions.

When the service system calls the judgment interface, the judgment interface takes the item identifier and the requester identifier as reference, the fatigue value data corresponding to the requester is inquired from the fatigue value database, and if the inquired fatigue value data is smaller than the threshold value configured on the rule configuration page, the fatigue value check is passed; otherwise, the fatigue value check fails.

Step S306: and the background takes the article identifier and the requester identifier as the input parameters and calls the risk identification service of the risk identification system. And the background calls the risk identification service by carrying the risk identification request in the call request. The risk identification request includes an item identification and a requestor identification.

Step S307: and the risk identification system returns the risk label corresponding to the article identifier and the risk label corresponding to the requester identifier to the background. And the risk identification service verifies a pre-configured risk strategy in real time based on the access parameters and feeds back a hit risk label. In an embodiment, the risk tag comprises: risk requestors, claim reversal, arbitrage risk, other risk, order exceptions, coupon requestors, arbitrage ticket requestors, and the like.

When the business system calls the judgment interface, the judgment interface calls the risk identification service, and if the returned risk label is empty, the verification is passed; otherwise the check fails.

Step S308: and the background generates a risk checking result and sends the risk checking result to the service system. Here, the risk verification result is obtained according to the duplication verification result and the fatigue value verification result of step S305, and the risk label obtained in step S307. And if the risk label is empty, and the repeatability check and the fatigue value check are all passed, judging that the interface returns that the check is passed, otherwise, judging that the return check is not passed.

It can be understood that the repeatability check and the fatigue value check of step S305, and the risk identification of steps S306 to S307 may be executed in parallel or sequentially, and the execution order of the three is not limited in this embodiment.

The second embodiment integrates the projects distributed in each service system, and unifies the projects to the risk management system to provide the risk management service, thereby realizing the management of each project. Meanwhile, project data of all items are collected in a unified mode, and an online article database is formed and used for automatic allocation management and control.

Fig. 6 is a schematic main flow chart of a risk management method according to a third embodiment of the present invention. As shown in fig. 6, the risk management method according to the embodiment of the present invention is used for performing risk query, so that a manager can select an item and a requester participating in a project. The method specifically comprises the following steps:

step S601: and the front-end page sends the risk inquiry request to the background. In an embodiment, the risk query request may be an item risk query request (for querying risk information of an item) or a requester risk query request (for querying risk information of a requester). For an item risk query request, the request includes an item identification of an item to be queried, a target item identification, and a query time. For a requestor risk query request, the request includes an item identification for an item to be queried and a target requestor identification.

Wherein, the query of the item risk can be realized by an item risk query page shown in fig. 7. As in fig. 7, the item risk query page includes an item name selection box, an item identification input box, and a query button. The administrator can select the item name on the item risk query page, input the skiid and click the query button, and then the item risk query request can be generated.

The requestor risk query may be implemented through a requestor risk query page as shown in fig. 8. As in fig. 8, the requestor risk query page includes an item name selection box, a requestor identification input box, and a query button. The administrator can select the item name on the risk query page of the requester, input the derived, and click the query button, so as to generate the risk query request of the requester.

It is understood that the query operation can be a single query or a batch query.

Step S602: and the background carries out risk verification according to the risk query request. For the item risk query request, the implementation process of the step is as follows: the method comprises the steps of firstly inquiring third project participation information corresponding to a target article and fourth project participation information of a target requester to which the target article belongs according to a target article identifier, then acquiring a corresponding verification rule according to the project identifier of a project to be inquired, and then performing risk verification on the target requester and the target article according to the third project participation information, the fourth project participation information and the acquired verification rule to obtain risk information of the target article.

The third item participation information is used for recording the information of the target item participation item, and may include information of a locking state, a locking time, a locking item, and the like of the target item. The fourth project participation information is used for recording information of the target requester participating in the project, and may include fatigue value data such as the number of times of the target requester participating in the project, subsidy amount obtained by the target requester, and number of items participating in the project in different time dimensions.

When risk verification is carried out, the repeatability of the article needs to be verified according to the participation information of the third project and the repeatability rule, and a repeatability verification result is obtained; and according to the fourth project participation information and the fatigue value rule, performing fatigue value verification on the requester to obtain a fatigue value verification result.

And (4) checking the repeatability, namely judging whether the query time of the target item conflicts with the locking period of other items to the item. And the fatigue value check is to compare the fatigue value data in the fourth item participation information with the threshold value. The process of implementing the duplication degree check and the fatigue value check is referred to step S305, and is not described herein again.

Step S603: and the background sends a risk identification request to the risk identification system. And the background calls the risk identification service by carrying the risk identification request in the call request. In an embodiment, if risk information for an item is queried, the risk identification request may include an item identification; the risk identification request may include a requestor identification if the requestor's risk information is queried.

The steps are 604: and the risk identification system returns the risk label corresponding to the article identifier and the risk label corresponding to the requester identifier to the background. If the risk information of the article is inquired, returning a risk label corresponding to the article identifier; and if the risk information of the requester is inquired, returning a risk label corresponding to the requester identifier.

Step S605: and the background generates a risk query result according to the risk verification result and the risk label and returns the risk query result to the front-end page. If the risk verification result is pass and the risk label is null, the risk query result is pass; if the repeatability check fails, the risk query result comprises repeated item identification and article identification; if the fatigue value verification fails, the risk query result comprises a rule which fails in the fatigue value rules; and if the risk label is not empty, the risk label is included in the risk inquiry result.

Step S606: and the front-end page constructs a primary selected object pool according to the risk query result and sends the primary selected object pool to the service system. And adding the item passing the risk inquiry result into the primary selection item pool.

Step S607: and the business system configures the articles participating in the project according to the primary selected article pool. The specific configuration comprises an article identifier, an item identifier, an online time and the like. Based on the query operation, the articles configured to the project participated by the business system are identified by risks, accord with the verification rule and have lower risks. In an alternative embodiment, the item which does not conform to the check rule and the risk identification fails and the requester (i.e. the risk item and the risk requester) can be prompted through a prompt box.

Fig. 9 is a schematic main flow chart of a risk management method according to a fourth embodiment of the present invention. As shown in fig. 9, the risk management method according to the embodiment of the present invention is used for performing whitening processing on the risk item and the risk requester queried according to the third embodiment, and specifically includes the following steps:

step S901: the service line system sends a whitening request to the front-end page. The whitelisting request may include a risk item requesting to be added to a whitelist, a risk requester, a whitelisting period, a whitelisting reason, and the like.

Step S902: and the front-end page configures a white list according to the whitening request and stores the white list in a whitening database. The front end page inquires the whitening record of the article or the requester through the whitening page, and can perform whitening processing on the article or the requester under specific items.

For example, if an item needs to be whitened, the configuration items are a whitening type (i.e., item whitening), an item identification, an item name, and a whitening period. For example, if a requestor needs to be whitened, the configuration items are a whitening type (i.e., requestor whitening), a requestor identification, a project name, and a whitening period.

Step S903: and the business system takes the item identification, the article identification and the online period as the input parameters and calls a judgment interface of the background. For a specific implementation of this step, refer to step S304, which is not described herein again.

Step S904: and the judgment interface inquires the white list and determines whether the article corresponding to the article identifier is in the whitening period. In an embodiment, the judgment interface may use the item identifier, the article identifier, the requester identifier, and the online time as references to query a white list in the whitening database to determine whether the article corresponding to the article identifier is in the whitening period.

The determination process is as follows: and judging whether the white list has the article identifier or whether a request party identifier corresponding to the article identifier exists, if the white list has the article identifier or the request party identifier and the online period belongs to the whitening period, the article is in the whitening period.

If neither the item identification nor the requestor identification is present in the white list, then the item is not in the whitening cycle. If the white list has the item identifier or the requester identifier but the online period does not belong to the whitening period, the item is not in the whitening period.

Step S904: and the judgment interface generates a risk checking result according to the determination result and sends the risk checking result to the service system. In the whitening period, the item and the requesting party which are added to the white list under the item only return verification pass. In the non-whitening period, the generation process of the risk check result is shown in the second embodiment, and details are not described here.

Fig. 10 is a schematic diagram of the main modules of a risk management device according to an embodiment of the present invention. As shown in fig. 10, a risk management device 1000 according to an embodiment of the present invention mainly includes:

the query module 1001 receives the project participation request, and queries, according to the item identifier in the project participation request, first project participation information of a corresponding item and second project participation information of a requester to which the item belongs. The project participation request comprises a project identifier, an article identifier and an online period of the project to be participated. The item identifier is used for uniquely identifying the item, the article identifier is used for uniquely identifying the article, and the online period is the time from the online to the offline of the article. The requester to which the item belongs is the owner of the item prior to the transaction.

An obtaining module 1002, configured to obtain a corresponding check rule according to the item identifier of the item to be participated. Different projects have different requirements for risk control, so that corresponding verification rules can be configured in advance based on project requirements. After receiving the project participation request, the corresponding verification rule can be obtained according to the project identifier. The validation rules are used to limit the number of items participating in the project simultaneously during the online period, as well as to limit the frequency with which requesters participate in the project.

A checking module 1003, configured to perform risk checking on the item and the requester according to the first item participation information, the second item participation information, and the checking rule, and allow the item to participate in the item to be participated in after the checking is determined to pass. In an embodiment, the verification rules are divided into a repeatability rule and a fatigue value rule, wherein the repeatability rule is used for limiting the number of items participating in the project simultaneously in the online period, and the fatigue value rule is used for limiting the frequency of the requester participating in the project.

In addition, the risk management device 1000 according to the embodiment of the present invention may further include: a locking module, a risk identification module, a configuration module, a determination module, a first query module, and a second query module (not shown in FIG. 10). The locking module is used for determining that the repeatability check of the article passes, locking the article when the article is on line or a locking instruction is received, and updating the locking state to be locked; and when the article is off-line, the locking time expires or an unlocking instruction is received, unlocking the article, and updating the locking state to be unlocked.

And the risk identification module is used for taking the article identifier and the requester identifier as the access parameters, calling a risk identification service, and obtaining the risk label of the article and the risk label of the requester. And the configuration module is used for configuring a white list for the item to be participated.

The judging module is used for judging whether a whitened article identifier which is the same as the article identifier exists in the white list or not, or a whitened requester identifier which is the same as the requester identifier exists in the white list; if a white added article identifier which is the same as the article identifier exists in the white list and the online period belongs to the white added period, determining that the verification is passed; if the white list has a white requesting party identifier which is the same as the requesting party identifier, and the online period belongs to the white adding period, determining that the verification is passed

The first query module is used for receiving an item risk query request, and querying third item participation information of a corresponding target item and fourth item participation information of a target requester to which the target item belongs according to a target item identifier in the item risk query request; the item risk query request comprises an item identifier of an item to be queried, a target item identifier and query time; acquiring a corresponding check rule according to the item identifier of the item to be inquired; wherein the verification rule is used for limiting the number of items simultaneously participated in by the target item in the query time and limiting the frequency of items participated in by the target requester; and performing risk verification on the target requester and the target object according to the third project participation information, the fourth project participation information and the obtained verification rule to obtain risk information of the target object.

The second query module is used for receiving a requester risk query request, wherein the requester risk query request comprises an item identifier of the item to be queried and a target requester identifier; and returning risk information obtained by performing risk verification on the target requester.

From the above description, it can be seen that by specifying the parameters of the project participation request as the project identifier, the article identifier and the online period, the risk verification can be automatically performed on the article and the requester by using the verification rule corresponding to the project identifier before the project is online, so that the unified management control on different projects is realized, the verification accuracy and efficiency are improved, and the repeated subsidy and the resource tilt are avoided.

Fig. 11 shows an exemplary system architecture 1100 to which the risk management method or risk management apparatus of an embodiment of the invention may be applied.

As shown in fig. 11, the system architecture 1100 may include a business server 1101,

networks

1102, 1104, 1106, 1107, front-end pages 1103, backend servers 1105, and a wind control server 1108.

The network 1102 medium to provide a communication link between the service server 1101 and the front end page 1103; network 1104 provides a medium for communication links between front-end pages 1103 and backend servers 1105; the network 1106 provides a medium for communication links between the traffic server 1101 and the backend server 1105; network 1107 is the medium used to provide a communication link between background server 1105 and wind control server 1108. The

networks

1102, 1104, 1106, 1107 may include various connection types, such as wired, wireless communication links, or fiber optic cables, among others.

The business server 1101, front-end page 1103, backend server 1105, and wind control server 1108 may be servers that provide various services. Wherein, the wind control server 1108 is used for risk identification. The backend server 1105 may be a backend management server that processes call requests sent by an administrator using the business server 1101. The background management server can inquire the project participation information, obtain the check rule, carry out risk check and feed back the processing result (such as whether the article is allowed to participate in the project) to the business server.

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 apparatus is generally disposed in the backend server 1105.

It should be understood that the number of terminal devices, networks, and servers in fig. 11 is merely illustrative. There may be any number of terminal devices, networks, and servers, as desired for implementation.

The invention also provides an electronic device and a computer readable medium according to the embodiment of the invention.

The electronic device of the present invention includes: one or more processors; a storage device, configured to store one or more programs, which when executed by the one or more processors, cause the one or more processors to implement a risk management method according to an embodiment of the present invention.

The computer readable medium of the present invention has stored thereon a computer program which, when executed by a processor, implements a risk management method of an embodiment of the present invention.

Referring now to FIG. 12, shown is a block diagram of a computer system 1200 suitable for use in implementing an electronic device of an embodiment of the present invention. The electronic device shown in fig. 12 is only an example, and should not bring any limitation to the functions and the scope of use of the embodiment of the present invention.

As shown in fig. 12, the computer system 1200 includes a Central Processing Unit (CPU)1201, which can perform various appropriate actions and processes in accordance with a program stored in a Read Only Memory (ROM)1202 or a program loaded from a storage section 1208 into a Random Access Memory (RAM) 1203. In the RAM 1203, various programs and data necessary for the operation of the computer system 1200 are also stored. The CPU 1201, ROM 1202, and RAM 1203 are connected to each other by a bus 1204. An input/output (I/O) interface 1205 is also connected to bus 1204.

The following components are connected to the I/O interface 1205: an input section 1206 including a keyboard, a mouse, and the like; an output portion 1207 including a display device such as a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and the like, and a speaker; a storage section 1208 including a hard disk and the like; and a communication section 1209 including a network interface card such as a LAN card, a modem, or the like. The communication section 1209 performs communication processing via a network such as the internet. A driver 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, or the like, is mounted on the drive 1210 as necessary, so that a computer program read out therefrom is mounted into the storage section 1208 as necessary.

In particular, the processes described above with respect to the main step diagrams may be implemented as computer software programs, according to embodiments of the present disclosure. For example, embodiments of the present disclosure include a computer program product comprising a computer program embodied on a computer readable medium, the computer program containing program code for performing the method illustrated in the main step diagram. In such an embodiment, the computer program may be downloaded and installed from a network through the communication section 1209, and/or installed from the removable medium 1211. The computer program performs the above-described functions defined in the system of the present invention when executed by the Central Processing Unit (CPU) 1201.

It should be noted that the computer readable medium shown in the present invention can be a computer readable signal medium or a computer readable storage medium or any combination of the two. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples of the computer readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, 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 disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the present invention, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In the present invention, however, a computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wire, fiber optic cable, RF, etc., or any suitable combination of the foregoing.

The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams or flowchart illustration, and combinations of blocks in the block diagrams or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

The modules described in the embodiments of the present invention may be implemented by software or hardware. The described modules may also be provided in a processor, which may be described as: a processor includes a query module, an acquisition module, and a check module. The names of these modules do not form a limitation on the modules themselves in some cases, for example, the query module may also be described as a "module that receives a project participation request, queries first project participation information of a corresponding project according to an item identifier in the project participation request, and queries second project participation information of a requester to which the project belongs".

As another aspect, the present invention also provides a computer-readable medium that may be contained in the apparatus described in the above embodiments; or may be separate and not incorporated into the device. The computer readable medium carries one or more programs which, when executed by a device, cause the device to comprise: receiving a project participation request, and inquiring first project participation information of a corresponding article and second project participation information of a requester to which the article belongs according to an article identifier in the project participation request; the project participation request comprises a project identifier of a project to be participated, the item identifier and an online period; acquiring a corresponding verification rule according to the project identification of the project to be participated; wherein the check rule is used for limiting the number of items participating in the online period and limiting the frequency of items participating in the requester; and performing risk verification on the article and the requester according to the first project participation information, the second project participation information and the verification rule, and allowing the article to participate in the project to be participated after the verification is determined to be passed.

According to the technical scheme of the embodiment of the invention, the parameters of the project participation request are specified as the project identifier, the article identifier and the online period, so that the risk verification can be automatically carried out on the article and the requester by using the verification rule corresponding to the project identifier before the project is online, the unified management control on different projects is realized, the verification accuracy and efficiency are improved, and the repeated subsidy and the resource inclination are avoided.

The product can execute the method provided by the embodiment of the invention, and has corresponding functional modules and beneficial effects of the execution method. For technical details that are not described in detail in this embodiment, reference may be made to the method provided by the embodiment of the present invention.

The above-described embodiments should not be construed as limiting the scope of the invention. Those skilled in the art will appreciate that various modifications, combinations, sub-combinations, and substitutions can occur, depending on design requirements and other factors. Any modification, equivalent replacement, and improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.

Claims

1. A method of risk management, comprising:

receiving a project participation request, and inquiring first project participation information of a corresponding article and second project participation information of a requester to which the article belongs according to an article identifier in the project participation request; the project participation request comprises a project identifier of a project to be participated, the item identifier and an online period;

acquiring a corresponding verification rule according to the project identification of the project to be participated; wherein the check rule is used for limiting the number of items participating in the online period and limiting the frequency of items participating in the requester;

and performing risk verification on the article and the requester according to the first project participation information, the second project participation information and the verification rule, and allowing the article to participate in the project to be participated after the verification is determined to be passed.

2. The method of claim 1, wherein the verification rules include a repeatability rule and a fatigue value rule; the repeatability rule is used for limiting the number of items participating in the online period at the same time; the fatigue value rule is used for limiting the frequency of the requester participating in the project, and comprises setting a threshold value of a fatigue value index;

the performing risk verification on the item and the requester according to the first item participation information, the second item participation information and the verification rule includes:

according to the first project participation information and the repeatability rule, carrying out the repeatability verification on the article to obtain an repeatability verification result;

comparing the fatigue value data in the second item participation information with the threshold value to obtain a fatigue value check result; wherein the fatigue value data is counted according to the fatigue value index.

3. The method according to claim 2, wherein the performing a duplication degree check on the article according to the first item participation information and the duplication degree rule to obtain a duplication degree check result comprises:

determining the locking state of the article in the online period according to the first project participation information;

if the locking state is locked, the repeatability check fails; and if the locking state is unlocked, the repeatability check is passed.

4. The method of claim 3, further comprising:

determining that the repeatability of the article passes verification, locking the article when the article is on line or a locking instruction is received, and updating the locking state to be locked;

and when the article is off-line, the locking time expires or an unlocking instruction is received, unlocking the article, and updating the locking state to be unlocked.

5. The method of claim 2, wherein the fatigue value indicator comprises: and setting any one or more of the number of times of the requester participating in the item in the time period, the quantity of the items of the requester participating in the item in the time period, and the subsidy amount of the requester in the time period.

6. The method of claim 1, further comprising:

taking the article identification and the requester identification as input parameters, and calling a risk identification service to obtain a risk label of the article and a risk label of the requester;

the determining that the check passes includes: the risk label is empty and the risk check passes.

7. The method of claim 1, further comprising: configuring a white list for the items to be participated; wherein the white list comprises one or more of a whitelisted item identifier and a whitelisted requestor identifier, and a whitelisted period;

prior to the step of risk-checking the item and the requestor, the method further comprises:

judging whether a white list has a white item identifier which is the same as the item identifier or a white requester identifier which is the same as the requester identifier;

if a white added article identifier which is the same as the article identifier exists in the white list and the online period belongs to the white added period, determining that the verification is passed;

if the white list has a whitening requester identifier which is the same as the requester identifier, and the online period belongs to the whitening period, determining that the verification is passed;

the risk checking the item and the requester comprises:

if the white list does not have a whitened article identifier which is the same as the article identifier and does not have a whitened requester identifier which is the same as the requester identifier, performing risk verification on the article and the requester;

and if the white list has a whitening requester identifier which is the same as the requester identifier, or has a whitening requester identifier which is the same as the requester identifier, but the online period does not belong to the whitening period, performing risk verification on the article and the requester.

8. The method according to any one of claims 1 to 7, further comprising:

receiving an item risk query request, and querying third item participation information of a corresponding target item and fourth item participation information of a target requester to which the target item belongs according to a target item identifier in the item risk query request; the item risk query request comprises an item identifier of an item to be queried, a target item identifier and query time;

acquiring a corresponding check rule according to the item identifier of the item to be inquired; wherein the verification rule is used for limiting the number of items simultaneously participated in by the target item in the query time and limiting the frequency of items participated in by the target requester;

and performing risk verification on the target requester and the target object according to the third project participation information, the fourth project participation information and the obtained verification rule to obtain risk information of the target object.

9. The method of claim 8, further comprising:

receiving a requester risk query request, wherein the requester risk query request comprises an item identifier of the item to be queried and a target requester identifier;

and returning risk information obtained by performing risk verification on the target requester.

10. A risk management device, comprising:

the query module is used for receiving a project participation request, and querying first project participation information of a corresponding project and second project participation information of a requester to which the project belongs according to an article identifier in the project participation request; the project participation request comprises a project identifier of a project to be participated, the item identifier and an online period;

the acquisition module is used for acquiring a corresponding check rule according to the project identifier of the project to be participated; wherein the check rule is used for limiting the number of items participating in the online period and limiting the frequency of items participating in the requester;

and the checking module is used for carrying out risk checking on the article and the requester according to the first project participation information, the second project participation information and the checking rule, and allowing the article to participate in the project to be participated after the checking is determined to be passed.

11. An electronic device, comprising:

one or more processors;

a storage device for storing one or more programs,

when executed by the one or more processors, cause the one or more processors to implement the method of any one of claims 1-9.

12. A computer-readable medium, on which a computer program is stored, which, when being executed by a processor, carries out the method according to any one of claims 1-9.