Blacklist comparison methods, apparatus, equipment and computer-readable storage media

Abstract

The application discloses a black list comparison method, device and equipment and a computer readable storage medium, and the method comprises the following steps: when a comparison instruction is received, user information and product system information corresponding to the comparison instruction are acquired, and it is inquired whether the user information exists in a black list according to the user information and the product system information; if the user information exists in the black list, a target reason code corresponding to the user information is determined according to the product system information; and the target reason code is input into a rule engine to determine whether a user corresponding to the user information is rejected. If it is determined that the user information exists in the black list, the target reason code corresponding to the user information is determined according to the product system information, and the target reason code is input into the rule engine to determine whether the user corresponding to the user information is rejected, so that the practicability of the black list comparison method is improved.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of financial technology, and in particular to a blacklist comparison method, device, equipment and computer readable storage medium. BACKGROUND

[0002] The current blacklist comparison method can only use the same comparison rule for all product system nodes, and can only perform simple full-field plaintext comparison on the primary key field of the blacklist, such as the ID number and mobile phone number. However, different products or different system nodes of the same product have different blacklists that need to be rejected. The current blacklist comparison method cannot flexibly use different blacklist comparison rules for different products or different system nodes of the same product, resulting in low practicality of the blacklist comparison method. Therefore, how to improve the practicality of the blacklist comparison method is a problem that needs to be solved. SUMMARY

[0003] The main purpose of the present application is to provide a blacklist comparison method, device, equipment and computer readable storage medium, which aims to solve the problem of how to improve the generalization of the model.

[0004] To achieve the above purpose, the present application provides a blacklist comparison method, which comprises the following steps:

[0005] When receiving a comparison instruction, the user information and product system information corresponding to the comparison instruction are obtained, and it is determined whether the user information exists in the blacklist according to the user information and the product system information;

[0006] If the user information exists in the blacklist, the target reason code corresponding to the user information is determined according to the product system information;

[0007] The target reason code is input into a rule engine to determine whether to reject the user corresponding to the user information.

[0008] Preferably, the step of determining whether the user information exists in the blacklist according to the user information and the product system information comprises:

[0009] The comparison rule is determined according to the product system information, and a query request is generated according to the comparison rule and the user information;

[0010] It is determined whether the user information exists in the blacklist according to the query request.

[0011] Preferably, the step of generating a query request according to the comparison rule and the user information comprises:

[0012] According to the comparison rule, a query primary key is determined in the user information, and the query primary key is preprocessed to generate a query request.

[0013] Preferably, the step of determining the target reason code corresponding to the user information according to the product system information comprises:

[0014] The reason code set corresponding to the user information in the blacklist is obtained, and a preset configuration table is determined according to the product system information.

[0015] The reason code set is screened according to the preset configuration table to determine the target reason code corresponding to the user information.

[0016] Preferably, the step of screening the reason code set according to the preset configuration table to determine the target reason code corresponding to the user information comprises:

[0017] According to the preset configuration table, a rejection reason code and a non-rejection reason code are determined, and each reason code in the reason code set is compared with the rejection reason code and the non-rejection reason code respectively.

[0018] If it is determined that there is no reason code in the reason code set that is the same as the rejection reason code, a reason code in the reason code set that is the same as the non-rejection reason code is taken as the target reason code corresponding to the user information.

[0019] If it is determined that there is a reason code in the reason code set that is the same as the rejection reason code, the user corresponding to the user information is rejected.

[0020] Preferably, the step of inputting the target reason code into a rule engine to determine whether to reject the user corresponding to the user information comprises:

[0021] The target reason code is input into a rule engine, the target reason code is judged by the rule engine according to a preset business rule, and whether to reject the user corresponding to the user information is determined based on the judgment result.

[0022] Preferably, when the comparison instruction is received, the user information and the product system information corresponding to the comparison instruction are obtained, and before the step of querying whether the user information exists in the blacklist according to the user information and the product system information, the blacklist comparison method further comprises:

[0023] The product system information corresponding to the accessed product or system is obtained, and the product system information is set, the comparison rule, the rejection reason code and the preset business rule corresponding to the product or the system.

[0024] In addition, to achieve the above object, the application further provides a blacklist comparison device, which comprises:

[0025] A query module is configured to, when receiving a comparison instruction, acquire user information and product system information corresponding to the comparison instruction, and query whether the user information exists in a blacklist according to the user information and the product system information.

[0026] A determination module is configured to, if the user information exists in the blacklist, determine a target reason code corresponding to the user information according to the product system information.

[0027] An input module is configured to input the target reason code into a rule engine to determine whether to reject a user corresponding to the user information.

[0028] Preferably, the query module is further configured to:

[0029] determine a comparison rule according to the product system information, and generate a query request according to the comparison rule and the user information;

[0030] query whether the user information exists in the blacklist according to the query request.

[0031] Preferably, the query module further comprises a generation module configured to:

[0032] determine a query primary key in the user information according to the comparison rule, and perform preset processing on the query primary key to generate a query request.

[0033] Preferably, the determination module further comprises a screening module configured to:

[0034] acquire a reason code set corresponding to the user information in the blacklist, and determine a preset configuration table according to the product system information;

[0035] screen the reason code set according to the preset configuration table to determine the target reason code corresponding to the user information.

[0036] Preferably, the screening module is further configured to:

[0037] determine a rejection reason code and a non-rejection reason code according to the preset configuration table, compare each reason code in the reason code set with the rejection reason code and the non-rejection reason code respectively;

[0038] if it is determined that there is no reason code identical to the rejection reason code in the reason code set, take a reason code identical to the non-rejection reason code in the reason code set as the target reason code corresponding to the user information;

[0039] If it is determined that there exists a reason code in the set of reason codes that is the same as the rejection reason code, then the user corresponding to the user information is rejected.

[0040] Preferably, the input module is further configured to:

[0041] The target reason code is input into the rule engine, which then judges the target reason code according to preset business rules and determines whether to reject the user corresponding to the user information based on the judgment result.

[0042] Preferably, the query module further includes a setting module, the setting module being used for:

[0043] Obtain the product system information corresponding to the accessed product or system, and set the comparison rules, rejection reason codes, and preset business rules corresponding to the product or system.

[0044] In addition, to achieve the above objectives, the present invention also provides a blacklist comparison device, the blacklist comparison device comprising: a memory, a processor, and a blacklist comparison program stored in the memory and executable on the processor, wherein the blacklist comparison program, when executed by the processor, implements the steps of the blacklist comparison method as described above.

[0045] In addition, to achieve the above objectives, the present invention also provides a computer-readable storage medium storing a blacklist comparison program, wherein the blacklist comparison program, when executed by a processor, implements the steps of the blacklist comparison method as described above.

[0046] The blacklist comparison method proposed in this invention, upon receiving a comparison instruction, acquires the user information and product system information corresponding to the instruction, and queries whether the user information exists in the blacklist based on the user information and product system information. If the user information exists in the blacklist, a target reason code corresponding to the user information is determined based on the product system information. The target reason code is then input into a rule engine to determine whether to reject the user corresponding to the user information. This invention improves the practicality of the blacklist comparison method by determining the target reason code based on the product system information and inputting it into the rule engine if the user information is found to exist in the blacklist. Attached Figure Description

[0047] Figure 1 This is a schematic diagram of the device structure of the hardware operating environment involved in the embodiments of the present invention;

[0048] Figure 2This is a flowchart illustrating the first embodiment of the blacklist comparison method of the present invention;

[0049] The realization of the objective of this invention, its functional features and advantages will be further explained with reference to the accompanying drawings through a series of embodiments. Detailed Implementation

[0050] It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.

[0051] like Figure 1 As shown, Figure 1 This is a schematic diagram of the device structure of the hardware operating environment involved in the embodiments of the present invention.

[0052] The device in this embodiment of the invention can be a PC or a server.

[0053] like Figure 1 As shown, the device may include: a processor 1001, such as a CPU; a network interface 1004; a user interface 1003; a memory 1005; and a communication bus 1002. The communication bus 1002 is used to enable communication between these components. The user interface 1003 may include a display screen or an input unit such as a keyboard; optionally, the user interface 1003 may also include a standard wired interface or a wireless interface. The network interface 1004 may optionally include a standard wired interface or a wireless interface (such as a Wi-Fi interface). The memory 1005 may be high-speed RAM or non-volatile memory, such as a disk drive. Optionally, the memory 1005 may also be a storage device independent of the aforementioned processor 1001.

[0054] Those skilled in the art will understand that Figure 1 The device structure shown does not constitute a limitation on the device and may include more or fewer components than shown, or combine certain components, or have different component arrangements.

[0055] like Figure 1 As shown, the memory 1005, which serves as a computer storage medium, may include an operating system, a network communication module, a user interface module, and a blacklist comparison program.

[0056] The operating system is a program that manages and controls the portable blacklist comparison device and software resources, and supports the operation of the network communication module, user interface module, blacklist comparison program and other programs or software; the network communication module is used to manage and control the network interface 1002; the user interface module is used to manage and control the user interface 1003.

[0057] exist Figure 1In the blacklist comparison device shown, the blacklist comparison device calls the blacklist comparison program stored in the memory 1005 through the processor 1001 and executes the operations in the various embodiments of the blacklist comparison method described below.

[0058] Based on the above hardware structure, an embodiment of the blacklist comparison method of the present invention is proposed.

[0059] Reference Figure 2 , Figure 2 This is a flowchart illustrating the first embodiment of the blacklist comparison method of the present invention. The method includes:

[0060] Step S10: Upon receiving a comparison instruction, obtain the user information and product system information corresponding to the comparison instruction, and query whether the user information exists in the blacklist based on the user information and the product system information;

[0061] Step S20: If the user information exists in the blacklist, then determine the target reason code corresponding to the user information based on the product system information;

[0062] Step S30: Input the target reason code into the rule engine to determine whether to reject the user corresponding to the user information.

[0063] This embodiment of the blacklist comparison method is applied to the blacklist comparison device of a fintech institution. The risk prediction blacklist comparison device can be a terminal or a PC. This blacklist comparison device can determine different blacklist comparison rules based on different application products or different application systems and blacklists. For ease of description, a blacklist comparison device is used as an example. When the blacklist comparison device receives a comparison instruction, it obtains the user information and product system information corresponding to the comparison instruction, determines the comparison rules based on the product system information, and generates a query request based on the comparison rules and user information. The query request is used to check whether the user information exists in the blacklist. If the blacklist comparison device determines that the user information exists in the blacklist, it obtains the set of reason codes corresponding to the user information in the blacklist, determines a preset configuration table based on the product system information, filters the set of reason codes based on the preset configuration table, and determines the target reason code corresponding to the user information. The blacklist comparison device inputs the target reason code into the rule engine to determine whether to reject the user corresponding to the user information. It should be noted that user information may include: the user's ID card number, mobile phone number, name, and channel ID, etc.; product system information refers to the information corresponding to different application products or application systems, which can be used to distinguish different application products or application systems; reason code refers to the reason code for a user being included in the blacklist, used to distinguish different types of blacklists; the rule engine is a component embedded in the application that separates business decisions from the application code and uses predefined semantic modules to write business decisions. When receiving data input, it interprets the business rules and makes business decisions based on the business rules.

[0064] The blacklist comparison method in this embodiment, upon receiving a comparison instruction, acquires the user information and product system information corresponding to the instruction, and queries the blacklist to see if the user information exists. If the user information exists in the blacklist, the target reason code corresponding to the user information is determined based on the product system information. The target reason code is then input into the rule engine to determine whether to reject the user corresponding to the user information. This invention, by determining the target reason code based on the product system information and inputting it into the rule engine to determine whether to reject the user corresponding to the user information, allows for flexible application of different blacklist comparison rules for different products or different system nodes of the same product, thereby improving the practicality of the blacklist comparison method.

[0065] The following will provide a detailed explanation of each step:

[0066] Step S10: Upon receiving a comparison instruction, obtain the user information and product system information corresponding to the comparison instruction, and query whether the user information exists in the blacklist based on the user information and the product system information;

[0067] In this embodiment, different application products or application systems are connected to the blacklist comparison device. When each application product or application system detects user login or registration information, it obtains the user information corresponding to that user, generates a comparison instruction based on the user information and its own product system information, and sends the comparison instruction to the blacklist comparison device. When the blacklist comparison device receives the comparison instruction, it obtains the user information and product system information corresponding to the comparison instruction, and queries whether user information exists in the blacklist based on the user information and product system information. It can be understood that the blacklist is formed when multiple different application products or application systems add users to the blacklist. Due to different business needs, the encoding of the data corresponding to the user being identified as blacklisted by different application products or application systems is also different. Therefore, it is necessary to combine the product system information to determine the corresponding comparison rules, and then query the data with different encodings in the blacklist according to the comparison rules, so as to determine whether user information exists in the blacklist, which can maximize the effective use of the original list.

[0068] Specifically, the step of querying whether the user information exists in the blacklist based on the user information and the product system information includes:

[0069] Step a: Determine the comparison rules based on the product system information, and generate a query request based on the comparison rules and the user information;

[0070] In this step, the blacklist comparison device determines the comparison rules based on the product system information. Based on these rules, it determines the query primary key in the user information and performs preset processing on the query primary key to generate a query request. In one embodiment, the blacklist comparison device obtains and determines the corresponding comparison rules based on the product system information. Based on the comparison information, it determines one or more of the following as the query primary key in the user information: ID card number, mobile phone number, name, and channel ID. It then performs preset processing on the query primary key according to the corresponding comparison rules and generates a query request based on the preset query primary key. It should be noted that the comparison rules correspond one-to-one with the product system information; that is, different application products or systems have different comparison rules.

[0071] Further, step a includes:

[0072] According to the comparison rules, the query primary key is determined in the user information, and the query primary key is preset to generate a query request.

[0073] In this step, the blacklist comparison device determines the query primary key in the user information according to the comparison rules, and performs preset processing on the query primary key to generate a query request. In one embodiment, if the blacklist comparison device determines the comparison rule based on the product system information to be a comparison rule that configures the mask of a specified field of the user information, that is, sets the mask start position / mask length, such as configuring ID card number: 10 / 4, which means that the mask start position is the 10th digit of the ID card and the mask length is 4 digits, that is, the 10th to 13th digits of the ID card number are replaced with a mask, and the query request is generated based on the masked ID card number. The blacklist comparison device generates a query request based on the following criteria: If the blacklist comparison device determines the comparison rule based on the product system information to be a multi-field mask configuration for user information (i.e., setting multiple mask start positions / mask lengths, such as configuring ID card numbers as 4 / 2, 10 / 4, where the 4th to 5th digits and the 10th to 13th digits of the ID card number are replaced with a mask), a query request is generated based on the masked ID card number. If the blacklist comparison device determines the comparison rule based on the product system information to be a reverse mask configuration for user information (i.e., configuring mask lengths from the last digit of the specified field backwards), a query request is generated based on the masked ID card number. For example, the reverse configuration of the ID card number: 1 / 4, means masking the last four digits of the ID card number (digits 15 to 18), and generating a query request based on the masked ID card number. If the blacklist comparison device determines the comparison rule based on the product system information to be a multi-field combination comparison of user information, that is, selecting the fields to be matched, such as configuring name + ID card number, it represents the name and ID card number of the customer being queried, and generating a query request based on name + ID card number. If the blacklist comparison device determines the comparison rule based on the product system information to be an MD5 format encryption configuration of user information, that is, encrypting the information of the specified fields with MD5, such as configuring the ID card number to be encrypted with MD5 format, and generating a query request based on the encrypted ID card number. It can be understood that the user information such as mobile phone number, name, and channel ID can also be configured with specified field masking, multi-field masking, reverse masking, multi-field combination comparison configuration, and MD5 format encryption configuration, and then a query request can be generated. The above comparison rules can also be combined according to specific situations to obtain different comparison rules. It should be noted that in addition to the above comparison rules, there are other comparison rules, which will not be elaborated here.

[0074] Step b: Query whether the user information exists in the blacklist according to the query request.

[0075] In this step, the blacklist comparison device queries whether user information exists in the blacklist based on the query request. In one embodiment, if the blacklist comparison device determines the comparison rule based on the product system information to be a comparison rule that masks the specified fields of user information, and replaces the 10th to 13th digits of the ID card number in the user information with a mask, and generates a query request based on the masked ID card number, the blacklist comparison device compares the data in the blacklist with the masked ID card number in the query request. If there is data in the blacklist that corresponds to the same masked ID card number, then it is determined that user information exists in the blacklist. It can be understood that different comparison rules generate different query requests, and different query requests are compared with data of different codes in the blacklist to determine whether user information exists in the blacklist.

[0076] Furthermore, if the blacklist comparison device queries the blacklist based on the query request and determines that the user information does not exist in the blacklist, it can be understood that the user corresponding to the user information is not on the blacklist, and the user can be allowed to log in or register for the corresponding application product or application system.

[0077] Step S20: If the user information exists in the blacklist, then determine the target reason code corresponding to the user information based on the product system information;

[0078] In this embodiment, the blacklist comparison device queries the blacklist according to the query request, determines that the user information exists in the blacklist, and then determines the target reason code corresponding to the user information according to the product system information. In one embodiment, the blacklist comparison device obtains the set of reason codes corresponding to the user information in the blacklist and determines a preset configuration table according to the product system information; it determines the rejection reason code and the non-rejection reason code according to the preset configuration table, compares each reason code in the reason code set with the rejection reason code and the non-rejection reason code respectively, and determines the target reason code corresponding to the user information or rejects the user corresponding to the user information according to the comparison result.

[0079] Specifically, the steps for determining the target reason code corresponding to the user information based on the product system information include:

[0080] Step c: Obtain the set of reason codes corresponding to the user information in the blacklist, and determine the preset configuration table based on the product system information;

[0081] In this step, when the blacklist comparison device determines that the user information exists in the blacklist, it obtains the set of reason codes corresponding to the user information in the blacklist and determines the preset configuration table based on the product system information. It can be understood that the blacklist contains user information of multiple different users and the corresponding set of reason codes. Different application products or systems contain different preset configuration tables, which include the rejection reason code and the non-rejection reason code of the corresponding application product or system.

[0082] Step d: Filter the set of reason codes according to the preset configuration table to determine the target reason code corresponding to the user information.

[0083] In this step, after the blacklist comparison device determines the preset configuration table based on the product system information, it filters each reason code in the reason code set according to the preset configuration table to determine the target reason code corresponding to the user information. In one embodiment, the blacklist comparison device determines the rejection reason code and non-rejection reason code of the application product or system corresponding to the product system information according to the preset configuration table, and compares each reason code in the reason code set with the rejection reason code and the non-rejection reason code respectively. If it is determined that there is no reason code in the reason code set that is the same as the rejection reason code, then the reason code in the reason code set that is the same as the non-rejection reason code is used as the target reason code corresponding to the user information.

[0084] Further, step d includes:

[0085] Step d1: Determine the rejection reason code and the non-rejection reason code according to the preset configuration table, and compare each reason code in the reason code set with the rejection reason code and the non-rejection reason code respectively;

[0086] In this step, the blacklist comparison device determines the rejection reason code and non-rejection reason code for the corresponding application product or system based on a preset configuration table. Each reason code in the set is then compared with both the rejection reason code and the non-rejection reason code. For example, if the blacklist comparison device determines that the rejection reason code for the corresponding application product or system is for serious dishonesty and the non-rejection reason code is for general dishonesty, then each reason code in the set is compared with both the rejection reason code for serious dishonesty and the non-rejection reason code for general dishonesty. It is understood that there can be multiple rejection reason codes and only one non-rejection reason code, depending on the specific circumstances of the corresponding application product or system.

[0087] Step d2: If it is determined that there is no reason code in the reason code set that is the same as the rejection reason code, then the reason code in the reason code set that is the same as the non-rejection reason code is used as the target reason code corresponding to the user information.

[0088] In this step, the blacklist comparison device compares each reason code in the reason code set with the rejection reason code and the non-rejection reason code respectively. If the comparison result shows that there is no reason code in the reason code set that is the same as the rejection reason code, then the reason code in the reason code set that is the same as the non-rejection reason code is used as the target reason code corresponding to the user information. For example, if the rejection reason code of an application product or system is serious dishonesty and the non-rejection reason code is general dishonesty, the blacklist comparison device first compares each reason code in the reason code set with the rejection reason code for serious dishonesty. If it is determined that there is no reason code in the reason code set that is the same as the rejection reason code for serious dishonesty, then the user corresponding to the user information is not rejected. Then, each reason code in the reason code set is compared with the non-rejection reason code for general dishonesty, and the reason code in the reason code set that is the same as the non-rejection reason code for general dishonesty is used as the target reason code corresponding to the user information.

[0089] Step d3: If it is determined that there is a reason code in the reason code set that is the same as the rejection reason code, then the user corresponding to the user information is rejected.

[0090] In this step, the blacklist comparison device compares each reason code in the reason code set with the rejection reason code and the non-rejection reason code respectively. If the comparison result shows that there is a reason code in the reason code set that is the same as the rejection reason code, then the user corresponding to the user information is rejected. For example, if the rejection reason code of an application product or system is serious dishonesty and the non-rejection reason code is general dishonesty, the blacklist comparison device first compares each reason code in the reason code set with the rejection reason code for serious dishonesty. If it is determined that there is a reason code in the reason code set that is the same as the rejection reason code for serious dishonesty, then the user corresponding to the user information is directly rejected from logging in or registering, without needing to compare each reason code in the reason code set with the non-rejection reason code for general dishonesty.

[0091] Step S30: Input the target reason code into the rule engine to determine whether to reject the user corresponding to the user information.

[0092] In this embodiment, the blacklist comparison device inputs the target reason code into the rule engine, which then determines whether the target reason code meets the actual needs of the corresponding application product or system, and thus decides whether to reject the user corresponding to the user information.

[0093] Specifically, step S30 includes:

[0094] Step e: Input the target reason code into the rule engine, and the rule engine judges the target reason code according to the preset business rules, and determines whether to reject the user corresponding to the user information based on the judgment result.

[0095] In this step, the blacklist comparison device inputs the target reason code into the rule engine. The rule engine then judges the target reason code according to its preset business rules and determines whether to reject the user corresponding to the user information based on the judgment result. For example, if the target reason code is "general credit default," and the preset business rule in the rule engine is that only small-amount loans are available with low credit requirements, then the target reason code for "general credit default" can be accepted, and therefore the user corresponding to the user information will not be rejected, allowing the user to log in or register. However, if the preset business rule in the rule engine is that only large-amount loans are available with high credit requirements, then the target reason code for "general credit default" cannot be accepted, and therefore the user corresponding to the user information will be rejected, preventing the user from logging in or registering.

[0096] When the blacklist comparison device in this embodiment receives a comparison instruction, it acquires the user information and product system information corresponding to the comparison instruction, determines the comparison rules based on the product system information, and generates a query request based on the comparison rules and user information. The device then queries whether the user information exists in the blacklist based on the query request. If the blacklist comparison device determines that user information exists in the blacklist, it acquires the set of reason codes corresponding to the user information in the blacklist, determines a preset configuration table based on the product system information, filters the set of reason codes based on the preset configuration table, and determines the target reason code corresponding to the user information. The blacklist comparison device inputs the target reason code into the rule engine to determine whether to reject the user corresponding to the user information. This invention, by determining that user information exists in the blacklist based on the product system information, determines the target reason code corresponding to the user information and inputs the target reason code into the rule engine to determine whether to reject the user corresponding to the user information, can flexibly apply different blacklist comparison rules to different products or different system nodes of the same product, thereby improving the practicality of the blacklist comparison method.

[0097] Furthermore, based on the first embodiment of the blacklist comparison method of the present invention, a second embodiment of the blacklist comparison method of the present invention is proposed.

[0098] The second embodiment of the blacklist comparison method differs from the first embodiment in that it includes the following steps before step S10:

[0099] Step f: Obtain product system information corresponding to the accessed product or system, and set the comparison rules, rejection reason codes, and preset business rules corresponding to the product or system based on the product system information.

[0100] In this embodiment, since different application products or application systems have different actual needs, it is necessary to set corresponding comparison rules, rejection reason codes, and preset business rules according to different application products or application systems. When different application products or application systems access the blacklist comparison device, the blacklist comparison device obtains the corresponding product system information and sets the comparison rules, rejection reason codes, and preset business rules corresponding to different application products or application systems based on the product system information. Alternatively, relevant business personnel can set the comparison rules, rejection reason codes, and preset business rules corresponding to different application products or application systems in the blacklist comparison device's backend according to the product system information.

[0101] The blacklist comparison device in this embodiment obtains product system information corresponding to the accessed product or system, and sets comparison rules, rejection reason codes, and preset business rules for the corresponding product or system. This helps to flexibly apply different blacklist comparison rules to different products or different system nodes of the same product, improving the practicality of the blacklist comparison method.

[0102] The present invention also provides a blacklist comparison device. The blacklist comparison device of the present invention includes:

[0103] The query module is used to obtain the user information and product system information corresponding to the comparison instruction when a comparison instruction is received, and to query whether the user information exists in the blacklist based on the user information and the product system information;

[0104] The determination module is used to determine the target reason code corresponding to the user information based on the product system information if the user information exists in the blacklist.

[0105] The input module is used to input the target reason code into the rule engine to determine whether to reject the user corresponding to the user information.

[0106] Preferably, the query module is further used for:

[0107] The comparison rules are determined based on the product system information, and a query request is generated based on the comparison rules and the user information.

[0108] The query request is used to check whether the user information exists in the blacklist.

[0109] Preferably, the query module further includes a generation module, which is used for:

[0110] According to the comparison rules, the query primary key is determined in the user information, and the query primary key is preset to generate a query request.

[0111] Preferably, the determining module further includes a filtering module, the filtering module being used for:

[0112] Obtain the set of reason codes corresponding to the user information in the blacklist, and determine the preset configuration table based on the product system information;

[0113] The set of reason codes is filtered according to the preset configuration table to determine the target reason code corresponding to the user information.

[0114] Preferably, the filtering module is further configured to:

[0115] The rejection reason code and the non-rejection reason code are determined according to the preset configuration table, and each reason code in the reason code set is compared with the rejection reason code and the non-rejection reason code respectively;

[0116] If it is determined that there is no reason code in the reason code set that is the same as the rejection reason code, then the reason code in the reason code set that is the same as the non-rejection reason code is used as the target reason code corresponding to the user information;

[0117] If it is determined that there exists a reason code in the set of reason codes that is the same as the rejection reason code, then the user corresponding to the user information is rejected.

[0118] Preferably, the input module is further configured to:

[0119] The target reason code is input into the rule engine, which then judges the target reason code according to preset business rules and determines whether to reject the user corresponding to the user information based on the judgment result.

[0120] Preferably, the query module further includes a setting module, the setting module being used for:

[0121] Obtain the product system information corresponding to the accessed product or system, and set the comparison rules, rejection reason codes, and preset business rules corresponding to the product or system.

[0122] The present invention also provides a blacklist comparison device.

[0123] The blacklist comparison device of the present invention includes: a memory, a processor, and a blacklist comparison program stored in the memory and executable on the processor. When the blacklist comparison program is executed by the processor, it implements the steps of the blacklist comparison method as described above.

[0124] The method implemented when the blacklist comparison program running on the processor is executed can be referred to in various embodiments of the blacklist comparison method of the present invention, and will not be repeated here.

[0125] The present invention also provides a computer-readable storage medium.

[0126] The present invention provides a computer-readable storage medium storing a blacklist comparison program, which, when executed by a processor, implements the steps of the blacklist comparison method described above.

[0127] The method implemented when the blacklist comparison program running on the processor is executed can be referred to in various embodiments of the blacklist comparison method of the present invention, and will not be repeated here.

[0128] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or system that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or system. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or system that includes that element.

[0129] The sequence numbers of the above embodiments of the present invention are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.

[0130] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of the present invention, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) as described above, and includes several instructions to cause a terminal device (which may be a mobile phone, computer, server, or network device, etc.) to execute the methods described in the various embodiments of the present invention.

[0131] The above are merely preferred embodiments of the present invention and do not limit the patent scope of the present invention. Any equivalent structural or procedural transformations made based on the content of the present invention's specification and drawings, or direct or indirect applications in other related technical fields, are similarly included within the patent protection scope of the present invention.

Claims

1. A blacklist comparison method, characterized by, The blacklist comparison method comprises the following steps: Upon receiving the comparison instruction, obtaining user information and product system information corresponding to the comparison instruction, and querying whether the user information exists in the blacklist according to the user information and the product system information; Before the step of obtaining user information and product system information corresponding to the comparison instruction upon receiving the comparison instruction, and querying whether the user information exists in the blacklist according to the user information and the product system information, the blacklist comparison method further comprises: Obtaining product system information corresponding to the accessed product or system, and setting comparison rules, rejection reason codes, and preset business rules corresponding to the product or the system according to the product system information; The step of querying whether the user information exists in the blacklist according to the user information and the product system information comprises: Determining comparison rules according to the product system information, and generating a query request according to the comparison rules and the user information; The step of generating a query request according to the comparison rules and the user information comprises: Determining a query primary key in the user information according to the comparison rules, and performing preset processing on the query primary key to generate a query request; The step of generating a query request according to the comparison rules and the user information comprises: If the comparison rules are specified field mask configuration rules, determining the query primary key of the user information through the specified field mask configuration rules, and generating a query request according to the query primary key; If the comparison rules are multi-field mask configuration rules, determining the query primary key of the user information through the multi-field mask configuration rules, and generating a query request according to the query primary key; If the comparison rules are reverse mask configuration rules, determining the query primary key of the user information through the reverse mask configuration rules, and generating a query request according to the query primary key; If the comparison rules are multi-field combination configuration rules, determining the query primary key of the user information through the multi-field combination configuration rules, and generating a query request according to the query primary key; Querying whether the user information exists in the blacklist according to the query request; If the user information exists in the blacklist, determining a target reason code corresponding to the user information according to the product system information; The step of determining a target reason code corresponding to the user information according to the product system information comprises: Obtaining a reason code set corresponding to the user information in the blacklist, and determining a preset configuration table according to the product system information; Filtering the reason code set according to the preset configuration table to determine the target reason code corresponding to the user information; Inputting the target reason code into a rule engine to determine whether to reject the user corresponding to the user information; The step of inputting the target reason code into a rule engine to determine whether to reject the user corresponding to the user information comprises: The target cause code is input into a rule engine, the target cause code is judged according to preset business rules through the rule engine, and it is determined whether to reject the user corresponding to the user information based on a judgment result.

2. The black list comparison method of claim 1, wherein, The step of screening the cause code set according to the preset configuration table to determine the target cause code corresponding to the user information comprises: determining a rejection cause code and a non-rejection cause code according to the preset configuration table, comparing each cause code in the cause code set with the rejection cause code and the non-rejection cause code respectively; if it is determined that there is no cause code same as the rejection cause code in the cause code set, taking the cause code same as the non-rejection cause code in the cause code set as the target cause code corresponding to the user information; if it is determined that there is a cause code same as the rejection cause code in the cause code set, rejecting the user corresponding to the user information.

3. A blacklist comparison apparatus, characterized by, The black list comparison device comprises: A query module is configured to, upon receiving a comparison instruction, acquire user information and product system information corresponding to the comparison instruction, and query whether the user information exists in a black list according to the user information and the product system information. The query module is further configured to acquire product system information corresponding to an accessed product or system, and set comparison rules, rejection cause codes, and preset business rules corresponding to the product or the system according to the product system information. Comparison rules are determined according to the product system information, and a query request is generated according to the comparison rules and the user information. According to the comparison rules, a query primary key is determined in the user information, and the query primary key is preprocessed to generate a query request. If the comparison rules are specified field mask configuration rules, the query primary key of the user information is determined through the specified field mask configuration rules, and a query request is generated according to the query primary key. If the comparison rules are multi-field mask configuration rules, the query primary key of the user information is determined through the multi-field mask configuration rules, and a query request is generated according to the query primary key. If the comparison rules are reverse mask configuration rules, the query primary key of the user information is determined through the reverse mask configuration rules, and a query request is generated according to the query primary key. If the comparison rules are multi-field combination configuration rules, the query primary key of the user information is determined through the multi-field combination configuration rules, and a query request is generated according to the query primary key. It is determined whether the user information exists in the black list according to the query request. A determination module is configured to, if the user information exists in the black list, determine a target cause code corresponding to the user information according to the product system information. The step of determining the target cause code corresponding to the user information according to the product system information comprises: acquiring a cause code set corresponding to the user information in the black list, and determining a preset configuration table according to the product system information; screening the cause code set according to the preset configuration table to determine the target cause code corresponding to the user information. The input module is configured to input the target reason code into a rule engine to determine whether to reject a user corresponding to the user information. The step of inputting the target reason code into the rule engine to determine whether to reject the user corresponding to the user information comprises: The target reason code is input into the rule engine, and the rule engine is used to judge the target reason code according to a preset business rule, and determine whether to reject the user corresponding to the user information based on a judgment result.

4. A blacklist comparison device, characterized by, The blacklist comparison device comprises a memory, a processor, and a blacklist comparison program stored in the memory and executable on the processor. When the blacklist comparison program is executed by the processor, the steps of the blacklist comparison method according to any one of claims 1 to 2 are implemented.

5. A computer readable storage medium, characterized in that, The computer readable storage medium stores a blacklist comparison program. When the blacklist comparison program is executed by the processor, the steps of the blacklist comparison method according to any one of claims 1 to 2 are implemented.

Images