Blacklist management method, device, electronic device and storage medium
By obtaining business scenarios and user attribute data and calculating label scores, the problem of inflexible blacklist division is solved, and the flexible division and real-time blacklist are realized, reducing the complaint rate.
Patent Information
- Application Number
- CN202410139813.2
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2024-01-31
- Publication Date
- 2024-11-01
- Estimated Expiration
- 2044-01-31
AI Technical Summary
In the prior art, blacklist division is not flexible enough. Once a user is marked as a blacklist, he cannot participate in any business of the system and cannot distinguish and optimize according to specific scenarios.
By obtaining the business scenario, user's to be selected tags and user attribute data, selecting valid tags, calculating tag scores, determining whether the user is on the blacklist based on the scene scores, adding scene attributes and tag attributes, and achieving flexible division of the blacklist.
It improves the flexibility of blacklist division, determines whether users are on the blacklist for specific scenarios, reduces the complaint rate, and realizes the real-time and accuracy of blacklist data.
Smart Images

Figure CN117874311B_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of big data technology, and in particular to a blacklist management method, device, electronic device and storage medium. Background Art
[0002] Users are the foundation of business systems. User behavior affects the normal operation of business to a certain extent. Therefore, some specific users, such as employees with complaints or employees of competitor companies, need to be specially marked to block some data of such users. Most business systems will add these users to the blacklist, thereby blocking blacklist users in some scenarios to reduce complaints and optimize user experience.
[0003] In most systems, a module is usually set up to manage blacklist users. The usual practice is to provide a background management page for business personnel to manually fill in blacklist user data. Although this method can meet basic needs, it also has some problems: regardless of any business scenario, users who join the blacklist system must be in one of the black and white situations. As a result, once the user is on the blacklist, he cannot participate in any business of the system, and the blacklist division is not flexible enough. Summary of the invention
[0004] The present application provides a blacklist management method, device, electronic device and storage medium to solve the problem that blacklist division is not flexible enough.
[0005] In a first aspect, the present application provides a blacklist management method, the method comprising: obtaining a business scenario, a user's candidate tags, and user attribute data corresponding to each candidate tag; selecting at least one valid tag corresponding to the business scenario from the candidate tags; determining a tag score of the valid tag based on the user attribute data corresponding to the valid tag; adding up multiple tag scores corresponding to the business scenario to obtain a scenario score of the business scenario; and determining whether the user is on the blacklist based on the scenario score.
[0006] Optionally, selecting at least one valid tag corresponding to the business scenario from the tags to be selected includes: selecting at least one target tag corresponding to the business scenario from the tags to be selected; determining user attribute data corresponding to the target tag, wherein the user attribute data includes the last modification time of the data; if it is determined according to the last modification time that the data is currently in the effective period, then determining that the target tag is a valid tag.
[0007] Optionally, determining the tag score of the valid tag based on the user attribute data corresponding to the valid tag includes: determining the user attribute data corresponding to the valid tag, and a preset attribute score corresponding to each piece of user attribute data; multiplying the attribute score of each piece of the user attribute data to obtain the tag score of the valid tag.
[0008] Optionally, determining whether the user is in the blacklist according to the scenario score includes: if the scenario score is a positive number, determining that the user is in the blacklist; if the scenario score is a negative number, determining that the user is in the whitelist.
[0009] Optionally, after determining that the user is in the blacklist, the method further includes: determining the score range of the scenario score; determining the suspicion level corresponding to the user based on the correspondence between the preset score range and the suspicion level, wherein the suspicion level is divided into: confirmed, highly suspected, severely suspected, and low suspected.
[0010] Optionally, the user attribute data includes: weight, type of list, and last modification time.
[0011] Optionally, the method also includes: obtaining user attribute data, wherein the user attribute data is unlabeled; if it is determined that the user is currently within the effective period based on the last modification time in the user attribute data, and if it is determined that the user is already on the blacklist based on the type of user already on the list in the user attribute data, then it is determined that the user is on the blacklist.
[0012] In the second aspect, the present application provides a blacklist management device, which includes: an acquisition module, used to obtain business scenarios, user's candidate tags and user attribute data corresponding to each candidate tag; a selection module, used to select at least one valid tag corresponding to the business scenario from the candidate tags; a first determination module, used to determine the tag score of the valid tag based on the user attribute data corresponding to the valid tag; an acquisition module, used to add multiple tag scores corresponding to the business scenario to obtain the scenario score of the business scenario; a second determination module, used to determine whether the user is on the blacklist based on the scenario score.
[0013] In a third aspect, the present application provides an electronic device, comprising: at least one communication interface; at least one bus connected to the at least one communication interface; at least one processor connected to the at least one bus; at least one memory connected to the at least one bus, wherein the processor is configured to:
[0014] Obtain business scenarios, user's candidate tags, and user attribute data corresponding to each candidate tag; select at least one valid tag corresponding to the business scenario from the candidate tags; determine the tag score of the valid tag according to the user attribute data corresponding to the valid tag; add up multiple tag scores corresponding to the business scenario to obtain the scenario score of the business scenario; determine whether the user is on the blacklist according to the scenario score.
[0015] In a fourth aspect, the present application further provides a computer storage medium storing computer executable instructions, wherein the computer executable instructions are used to execute the blacklist management method described in any one of the above items of the present application.
[0016] The above technical solution provided by the embodiment of the present application has the following advantages compared with the prior art: on the basis of the user blacklist, scene attributes, label attributes and other user attribute data are added, and the label score is first obtained through the user attribute label, and then the label scores of different labels are added to determine whether the user in the scene is in the blacklist. In this way, for a specific scenario, the users in the blacklist of the scenario are obtained. The blacklist data in the present application takes the specific scenario into consideration to ensure the flexibility of blacklist division. BRIEF DESCRIPTION OF THE DRAWINGS
[0017] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the invention and, together with the description, serve to explain the principles of the invention.
[0018] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, for ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.
[0019] One or more embodiments are exemplarily described by pictures in the corresponding drawings, and these exemplified descriptions do not constitute limitations on the embodiments. Elements with the same reference numerals in the drawings represent similar elements, and unless otherwise stated, the figures in the drawings do not constitute proportional limitations.
[0020] Figure 1 A flow chart of a blacklist management method provided in an embodiment of the present application;
[0021] Figure 2 A schematic diagram of the structure of a blacklist management device provided in an embodiment of the present application;
[0022] Figure 3 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION
[0023] In order to make the purpose, technical solution and advantages of the embodiments of the present application clearer, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of this application.
[0024] The disclosure below provides many different embodiments or examples to implement different structures of the present invention. In order to simplify the disclosure of the present invention, the parts and settings of specific examples are described below. Of course, they are only examples, and the purpose is not to limit the present invention. In addition, the present invention can repeat reference numbers and / or letters in different examples. This repetition is for the purpose of simplification and clarity, and does not itself indicate the relationship between the various embodiments and / or settings discussed.
[0025] This application provides a blacklist management method, which is applied to a server to improve the flexibility of blacklist division, such as Figure 1 As shown, the method includes:
[0026] Step 101: Obtain the business scenario, the user's candidate tags, and the user attribute data corresponding to each candidate tag.
[0027] The business process provides an API interface, through which the user can add business scenarios, user's candidate tags and user attribute data corresponding to each candidate tag in the business process. These data can also be pre-built and saved by the user in the background page in advance. Add tag attributes and scenario attributes based on the user blacklist, and provide interfaces and page functions for real-time marking and batch processing.
[0028] Each business scenario corresponds to at least one tag, and the number of tags to be selected by the user can be one or more. For example, the business scenario includes scenario 1 and scenario 2, scenario 1 corresponds to tags 1, 2, and 3, and scenario 2 corresponds to tags 1, 3, and 4.
[0029] In addition to the callable identifier, user attribute data also includes weight, type of list, and the last modification time of the data.
[0030] Specifically, the weights are divided into low, general, and high. The types of users in the list are divided into blacklist and whitelist. Last modification time: In a specific business process, a user is not permanently blocked. If the blocking scenario to which the user belongs has ended, the user should be released from the blacklist scenario, thereby removing the blacklist mark of this scenario. The last modification time can be used to determine whether the user is currently in the effective period or outside the effective period.
[0031] The user sends a request to the server, which includes the business scenario, the user's candidate tags, and the user attribute data corresponding to each candidate tag. The server executes steps 102 to 105 according to the request.
[0032] Step 102: Select at least one valid tag corresponding to the business scenario from the tags to be selected.
[0033] The user can have multiple tags to be selected, but not every tag to be selected is required by the business scenario, and the tags to be selected include tags within the effective period and tags outside the effective period. Tags outside the effective period are invalid. Only tags required by the business scenario and within the effective period can be called valid tags. Therefore, it is necessary to select at least one valid tag corresponding to the business scenario from the tags to be selected. The specific selection steps will be described below and will not be repeated here.
[0034] Step 103: Determine the tag score of the valid tag according to the user attribute data corresponding to the valid tag.
[0035] A valid tag corresponds to certain user attribute data. The corresponding relationship here is set in advance by the user and stored in the database. The server can directly obtain the user attribute data corresponding to the valid tag from the database, and then calculate the tag score of the valid tag based on the attribute score corresponding to the user attribute data.
[0036] Exemplarily, the user attribute data includes weight, type of the user already on the list, and the last modification time of the data. The attribute score of each user attribute data is multiplied to obtain the label score of the valid label.
[0037] The attribute scores of user attributes are as follows.
[0038] Weight: "Low" is assigned a score of 1, "Normal" is assigned a score of 5, and "High" is assigned a score of 10;
[0039] Already in the list type: "Black" is assigned a score of 1, "White" is assigned a score of -1;
[0040] Last modification time: The latest modification time is scored as 5, and other times are scored as 2.
[0041] For example, if the user binds the following two tags:
[0042] Tag a: During the effective period, the weight is high, the list type is blacklist, and the last modification time is 2023-10-09.
[0043] Tag b: During the effective period, the weight is low, the list type is whitelist, and the last modification time is 2023-10-10.
[0044] The label score of label a = high weight 10*blacklist 1*other time 2=20, and the weighted value of label b = low weight 1*whitelist (-1)*latest modification time 5=-5.
[0045] Step 104: Add up the multiple tag scores corresponding to the business scenarios to obtain the scenario score of the business scenario.
[0046] The tag scores of the valid tags corresponding to the business scenario are added together to obtain the scenario score of the business scenario.
[0047] For example, if the scene corresponds to label a and label b, the sum of the label values is 15.
[0048] Step 105: Determine whether the user is on the blacklist based on the scenario score.
[0049] If the scenario score is positive, the user is determined to be in the blacklist; if the scenario score is negative, the user is determined to be in the whitelist. After the server determines the blacklist result, it feeds the result back to the user.
[0050] In this application, scenario attributes, label attributes and other user attribute data are added on the basis of the user blacklist. The label score is first obtained through the user attribute label, and then the label scores of different labels are added to determine whether the user in the scenario is on the blacklist. In this way, for a specific scenario, the users in the blacklist of the scenario are obtained. The blacklist data in this application takes into account the specific scenarios to ensure the flexibility of blacklist division.
[0051] For example, blacklist user A is bound to the following four tags in sequence:
[0052] Tag a: During the effective period, the weight is high, the list type is blacklist, and the last modification time is 2023-10-09.
[0053] Tag b: During the effective period, the weight is low, the list type is whitelist, and the last modification time is 2023-10-10.
[0054] Tag c: During the effective period, the weight is normal, the list type is whitelist, and the last modification time is 2023-10-15.
[0055] Tag d: The effective time has not yet arrived, the weight is high, the list type is blacklist, and the last modification time is 2023-11-03.
[0056] Scenario 1: When only tag a is added, this user is blacklisted.
[0057] Scenario 2: Tags a and b exist, the weighted value of tag a is: 10*1*2=20, the weighted value of tag b is 1*(-1)*5=-5, and the sum of the weighted values of the tags is 15. This data is a blacklist. That is, although the user has certain behaviors that can be judged as a normal user (i.e., a whitelist), it still needs to be processed as a blacklist because it was previously judged as a deterministic blacklist in some scenarios.
[0058] Scenario 3: Tags a, b, and c exist. The weighted value of tag a is 10*1*2=20, the weighted value of tag b is 1*(-1)*2=-2, and the weighted value of tag c is 5*(-1)*5=-25. The sum of the weighted values is -7. This user is on the whitelist.
[0059] Scenario 4: Tags a, b, c, and d exist, but tag d is not effective. The weighted calculation is the same as that in Scenario 3. This user is still on the whitelist.
[0060] Scenario 5: Tags a, b, c, and d exist, and tag d is in effect. The weight of tag a is 10*1*2=20, the weight of tag b is 1*(-1)*2=-2, the weight of tag c is 5*(-1)*2=-10, and the weight of tag d is 10*1*5=50. The final value is 58, and this user is on the blacklist. In the current scenario, if the weight of tag d is changed to normal or low, the user is also on the blacklist according to the calculation. The reason is that in the actual usage scenario, the last effective tag means the user's relatively new behavior, which will have a greater impact on the calculation result.
[0061] The above calculations are applied in common scenarios. There are also special cases as follows: In scenario 3, the user has been classified as a whitelist after multiple label calculations, but the scenario or business marked with label a still needs to do some special operations on this user. You can add the filter condition of label a in the request data. In this way, the user is still blacklisted in scenarios that require special processing, and the user has been classified as normal in other common scenarios.
[0062] Users in the blacklist can also be divided into different suspicion levels. Specifically, the score range of the scenario score can be determined. According to the correspondence between the preset score range and the suspicion level, the suspicion level corresponding to the user can be determined. The suspicion level is divided into: confirmed, highly suspected, severely suspected, and low suspected. The above suspicion content can be determined according to the specific scenario, such as suspected competitor employees or suspected complaining employees. This makes it easier to further divide users and clarify user levels, so as to facilitate the subsequent execution of different operations on users of different levels.
[0063] As an optional implementation, selecting at least one valid tag corresponding to a business scenario from the tags to be selected includes: selecting at least one target tag corresponding to the business scenario from the tags to be selected; determining user attribute data corresponding to the target tag, wherein the user attribute data includes the last modification time of the data; if it is determined based on the last modification time that the data is currently in the effective period, then determining that the target tag is a valid tag.
[0064] There are multiple tags to be selected, but not all of them belong to the business scenario. Therefore, it is necessary to select the target tag that meets the business scenario, and then determine the user attribute data corresponding to the target tag. The user attribute data includes the last modification time of the data. The last modification time can be used to determine whether the data is currently in the effective period. If it is outside the effective period, the tag is invalid and needs to be discarded; if it is in the effective period, the tag is valid.
[0065] As an optional implementation, the method also includes: obtaining user attribute data, wherein the user attribute data is unlabeled; if it is determined that the user is currently within the effective period based on the last modification time in the user attribute data, and if it is determined that the user is already on the blacklist based on the type of user already on the list in the user attribute data, then it is determined that the user is on the blacklist.
[0066] For user attribute data without tags, the blacklist result is returned based on the user attribute data. If the list type is black and the time period is valid, the user is determined to be in the blacklist.
[0067] In this application, the user configures blacklist tags according to different business scenarios, and calculates the sum of multiple tags when calling, thereby ultimately achieving the effect of placing users in different blacklists for different scenarios.
[0068] After this application was put into use, the frequency of modification of blacklist data increased significantly, indicating that there are many scenarios for real-time modification in actual processes. At the same time, since users can be assigned values for different businesses and processes, the accuracy of blacklist data is improved and the complaint rate is reduced.
[0069] In addition, in the prior art, the addition and modification of blacklist data needs to be manually processed in the background, which takes up manpower costs and causes duplication of work. The present application realizes the automatic modification of blacklist data, saving manpower and time.
[0070] The data generated in the prior art is lagging, and it takes a long time from judging blacklist users to data collection and then to sorting and entering, which affects the user experience. In this application, the caller marks the final modification time in the user attribute data in real time according to the specific scenario, and can immediately obtain the blacklist data belonging to the current business, ensuring the real-time nature of the blacklist data.
[0071] Based on the same technical concept, the present application provides a blacklist management device, such as Figure 2 As shown, the device comprises:
[0072] Acquisition module 201, used to acquire business scenarios, user's candidate tags and user attribute data corresponding to each candidate tag;
[0073] A selection module 202 is used to select at least one valid tag corresponding to the business scenario from the tags to be selected;
[0074] A first determination module 203, configured to determine a tag score of a valid tag according to user attribute data corresponding to the valid tag;
[0075] An obtaining module 204 is used to add up the multiple tag scores corresponding to the business scenario to obtain a scenario score of the business scenario;
[0076] The second determination module 205 is used to determine whether the user is in the blacklist according to the scenario score.
[0077] Optionally, the selection module 202 is used to:
[0078] Select at least one target tag corresponding to the business scenario from the candidate tags;
[0079] Determine user attribute data corresponding to the target tag, wherein the user attribute data includes the last modification time of the data;
[0080] If it is determined according to the last modification time that the current time is within the data validity period, the target tag is determined to be a valid tag.
[0081] Optionally, the first determining module 203 is used to:
[0082] Determine the user attribute data corresponding to the valid tag, and the preset attribute score corresponding to each piece of user attribute data;
[0083] Multiply the attribute scores of each user's attribute data to obtain the label score of the effective label.
[0084] Optionally, the second determining module 205 is used to:
[0085] If the scenario score is a positive number, it is determined that the user is in the blacklist;
[0086] If the scenario score is negative, it is determined that the user is in the whitelist.
[0087] Optionally, the device is also used for:
[0088] Determine the score range in which the scenario score falls;
[0089] The corresponding degree of suspicion of the user is determined according to the correspondence between the preset score range and the degree of suspicion, wherein the degree of suspicion is divided into: certain, highly suspected, severely suspected, and low suspected.
[0090] Optionally, the user attribute data includes: weight, type of list, and last modification time.
[0091] Optionally, the device is also used for:
[0092] Obtain user attribute data, wherein the user attribute data does not have a label;
[0093] If it is determined that the user is currently in the effective period according to the last modification time in the user attribute data, and the user is determined to be in the blacklist according to the type of the user already in the list in the user attribute data, then it is determined that the user is in the blacklist.
[0094] like Figure 3 As shown, an embodiment of the present application provides an electronic device, including a processor 301, a communication interface 302, a memory 303 and a communication bus 304, wherein the processor 301, the communication interface 302, and the memory 303 communicate with each other through the communication bus 304.
[0095] The memory 303 is used to store computer programs.
[0096] In one embodiment of the present application, the processor 301 is used to implement the blacklist management method provided by any one of the aforementioned method embodiments when executing the program stored in the memory 303, including:
[0097] Obtain the business scenario, the user's candidate tags, and the user attribute data corresponding to each candidate tag; select at least one valid tag corresponding to the business scenario from the candidate tags; determine the tag score of the valid tag based on the user attribute data corresponding to the valid tag; add up the multiple tag scores corresponding to the business scenario to obtain the scenario score of the business scenario; determine whether the user is on the blacklist based on the scenario score.
[0098] Optionally, selecting at least one valid tag corresponding to the business scenario from the tags to be selected includes: selecting at least one target tag corresponding to the business scenario from the tags to be selected; determining user attribute data corresponding to the target tag, wherein the user attribute data includes the last modification time of the data; if it is determined according to the last modification time that the data is currently in the effective period, then determining that the target tag is a valid tag.
[0099] Optionally, determining the tag score of the valid tag based on the user attribute data corresponding to the valid tag includes: determining the user attribute data corresponding to the valid tag, and a preset attribute score corresponding to each piece of user attribute data; and multiplying the attribute score of each user attribute data to obtain the tag score of the valid tag.
[0100] Optionally, determining whether the user is in the blacklist according to the scenario score includes: if the scenario score is a positive number, determining that the user is in the blacklist; if the scenario score is a negative number, determining that the user is in the whitelist.
[0101] Optionally, after determining that the user is on the blacklist, the method also includes: determining the score range of the scene score; determining the suspicion level corresponding to the user based on the correspondence between the preset score range and the suspicion level, wherein the suspicion level is divided into: confirmed, highly suspected, severely suspected, and low suspected.
[0102] Optionally, the user attribute data includes: weight, type of list, and last modification time.
[0103] Optionally, the method also includes: obtaining user attribute data, wherein the user attribute data is unlabeled; if it is determined that the user is currently within the effective period based on the last modification time in the user attribute data, and the user is determined to be on the blacklist based on the type of user already on the list in the user attribute data, then it is determined that the user is on the blacklist.
[0104] An embodiment of the present application also provides a computer-readable storage medium on which a computer program is stored. When the computer program is executed by a processor, the steps of the blacklist management method provided in any of the aforementioned method embodiments are implemented.
[0105] The device embodiments described above are merely illustrative, wherein the units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
[0106] Through the description of the above implementation methods, those skilled in the art can clearly understand that each implementation method can be implemented by means of software plus a general hardware platform, and of course, by hardware. Based on this understanding, the above technical solution is essentially or the part that contributes to the relevant technology can be embodied in the form of a software product, and the computer software product can be stored in a computer-readable storage medium, such as ROM / RAM, a disk, an optical disk, etc., including a number of instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to execute the methods described in each embodiment or some parts of the embodiments.
[0107] It should be understood that the terms used herein are only for the purpose of describing specific example embodiments and are not intended to be limiting. Unless the context clearly indicates otherwise, the singular forms "one", "an" and "said" as used herein may also be meant to include plural forms. The terms "include", "comprise", "contain", and "have" are inclusive, and therefore specify the existence of stated features, steps, operations, elements and / or parts, but do not exclude the existence or addition of one or more other features, steps, operations, elements, parts, and / or combinations thereof. The method steps, processes, and operations described herein are not interpreted as necessarily requiring them to be performed in the specific order described or illustrated, unless the execution order is clearly indicated. It should also be understood that additional or alternative steps may be used.
[0108] The foregoing is merely a specific embodiment of the present invention, which enables those skilled in the art to understand or implement the present invention. Various modifications to these embodiments will be apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the present invention. Therefore, the present invention will not be limited to the embodiments shown herein, but rather to the widest scope consistent with the principles and novel features claimed herein.
Claims
1. A blacklist management method, characterized in that: The method comprises: Obtaining a business scenario, a user's candidate tags, and user attribute data corresponding to each candidate tag, wherein the user has multiple candidate tags; Select at least one valid tag corresponding to the business scenario from the tags to be selected; Determining a tag score of the valid tag according to the user attribute data corresponding to the valid tag; Adding up the multiple tag scores corresponding to the business scenario to obtain a scenario score of the business scenario; Determining whether the user is on a blacklist according to the scenario score; Among them, selecting at least one valid tag corresponding to the business scenario from the candidate tags includes: Selecting at least one target tag corresponding to the business scenario from the candidate tags; Determine user attribute data corresponding to the target tag, wherein the user attribute data includes the last modification time of the data; If it is determined according to the last modification time that the current time is within the data validity period, then the target tag is determined to be a valid tag; Wherein, determining the tag score of the valid tag according to the user attribute data corresponding to the valid tag includes: Determine the user attribute data corresponding to the valid tag, and the preset attribute score corresponding to each piece of user attribute data; Multiplying the attribute scores of each of the user attribute data to obtain the tag score of the valid tag; Wherein, the method further comprises: Acquire user attribute data, wherein the user attribute data is unlabeled; If it is determined that the user is currently in the effective period according to the last modification time in the user attribute data, and if it is determined that the user is already in the blacklist according to the type of the user already in the list in the user attribute data, then it is determined that the user is in the blacklist.
2. The method according to claim 1, characterized in that Determining whether the user is on the blacklist according to the scenario score includes: If the scenario score is a positive number, it is determined that the user is in the blacklist; If the scenario score is a negative number, it is determined that the user is in the whitelist.
3. The method according to claim 2, characterized in that After determining that the user is in the blacklist, the method further includes: Determine a score range within which the scenario score falls; The suspicion degree corresponding to the user is determined according to the correspondence between the preset score range and the suspicion degree, wherein the suspicion degree is divided into: certain, highly suspected, severely suspected, and low suspected.
4. The method according to claim 1, characterized in that The user attribute data includes: weight, type of user already on the list, and last modification time.
5. A blacklist management device, characterized in that: The device comprises: An acquisition module is used to acquire a business scenario, a user's candidate tags, and user attribute data corresponding to each candidate tag, wherein the user has multiple candidate tags; A selection module, used to select at least one valid tag corresponding to the business scenario from the tags to be selected; A first determination module, configured to determine a tag score of the valid tag according to user attribute data corresponding to the valid tag; An obtaining module, used for adding up the multiple tag scores corresponding to the business scenario to obtain the scenario score of the business scenario; A second determination module, configured to determine whether the user is on a blacklist according to the scenario score; Wherein, the selection module is used for: Selecting at least one target tag corresponding to the business scenario from the candidate tags; Determine user attribute data corresponding to the target tag, wherein the user attribute data includes the last modification time of the data; If it is determined according to the last modification time that the current time is within the data validity period, then the target tag is determined to be a valid tag; Wherein, the first determining module is used for: Determine the user attribute data corresponding to the valid tag, and the preset attribute score corresponding to each piece of user attribute data; Multiplying the attribute scores of each of the user attribute data to obtain the tag score of the valid tag; Wherein, the device is also used for: Acquire user attribute data, wherein the user attribute data is unlabeled; If it is determined that the user is currently in the effective period according to the last modification time in the user attribute data, and if it is determined that the user is already in the blacklist according to the type of the user already in the list in the user attribute data, then it is determined that the user is in the blacklist.
6. An electronic device, characterized in that: It includes a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory communicate with each other through the communication bus; Memory, used to store computer programs; A processor, for implementing any of the methods described in claims 1-4 when executing a program stored in a memory.
7. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the method according to any one of claims 1 to 4 is implemented.
