A method and device for obtaining a label

Abstract

The present invention relates to the field of financial technology (Fintech), and discloses a method and device for obtaining a label, the method comprising: a label authorization system receives a label acquisition request sent by a user, the label acquisition request includes a user authority identifier and a label master identifier obtained in advance from the label authorization system; the user authority identifier is determined by the label authorization system according to the business scenario used by the user identifier and the label group, the label master indicated by the label master identifier has at least one label describing the label master, the label authorization system determines the authorized label group corresponding to the user authority identifier, and the label authorization system sends the label with the label master identifier in the authorized label group to the user. The present invention divides the authority of the label according to the business scenario to realize the authority control when obtaining the label across businesses, so that the label acquisition is more efficient and the security of the label acquisition is improved.

Description

Technical Field

[0001] The present invention relates to the technical field of financial technology (Fintech), and in particular to a method and device for obtaining a label. Background Art

[0002] With the development of computer technology, more and more technologies (such as blockchain, cloud computing or big data) are being applied in the financial field. The traditional financial industry is gradually transforming into financial technology, and big data technology is no exception. However, due to the security and real-time requirements of the financial and payment industries, higher requirements are also placed on big data technology.

[0003] In the era of big data, user information is flooding the Internet. Each specific information of a user is abstracted into a tag, and these tags are used to concretize the user image, so as to provide users with targeted services. With the substantial increase in the number of tags, the authority control of tags has become an urgent problem to be solved.

[0004] At present, the existing technology mainly takes the following steps:

[0005] The above solution designs a corresponding interface for each atomic service, so that the atomic services have a certain degree of independence and are decoupled from each other, thereby making the management of atomic services more efficient and convenient.

[0006] Optionally, before obtaining the task execution request, the method further includes:

[0007] Receiving a registration request for the target atomic service;

[0008] Step 1: User logs in and receives user permission information and access request;

[0009] Step 2: Call the tag class in the tag, which matches the user permission information with the preset permission information to generate a boolean value;

[0010] Step 3: The tag class returns a boolean value;

[0011] Step 4: Determine whether the Boolean value is true or false. If it is true, execute step 5; if it is false, execute step 6;

[0012] Step 5: Display the label content and end;

[0013] Step 6: Hide the label content and finish.

[0014] The above scheme discloses the matching process of a tag of a specific user. It can be seen that the existing permission control method is to set different tag permissions for users with different permissions. For example, users with Class A permissions correspond to Class A tags, and users with Class B permissions correspond to Class B permissions. In this case, control is only performed from the user's perspective, but the dimension of this permission control is very single, and in some specific systems or products, permission control based only on the user's perspective will result in excessive permissions for some users. Obviously, the existing scheme has low security for tag permission control. Summary of the invention

[0015] The present application provides a method and device for acquiring tags, so as to solve the problem of how to acquire tags efficiently and safely.

[0016] In a first aspect, an embodiment of the present application provides a method for obtaining a tag, comprising:

[0017] The tag authorization system receives a tag acquisition request sent by a user; the tag acquisition request includes a user authority identifier and a tag master identifier obtained in advance from the tag authorization system; the user authority identifier is determined by the tag authorization system according to the user identifier and the business scenario used by the tag group; the tag master indicated by the tag master identifier has at least one tag describing the tag master;

[0018] The tag authorization system determines the authorized tag group corresponding to the user authority identifier;

[0019] The tag authorization system sends the tag with the tag primary identifier in the authorized tag group to the user.

[0020] The above scheme divides the permissions of tags according to business scenarios to achieve permission control when obtaining tags across businesses. It determines the user permission identifier based on the actual scenario and user identifier, and then obtains the corresponding tag based on the user permission identifier, making tag acquisition more efficient and improving the security of tag acquisition.

[0021] Optionally, the tag acquisition request also includes a user identifier;

[0022] The tag authorization system determines the authorized tag group corresponding to the user authority identifier, including:

[0023] The tag authorization system determines an authorized tag group that matches the user identifier and the user authority identifier from the tag authorization record.

[0024] The above scheme, by adding a user identifier, prevents only users with the user authority identifier from obtaining tags, ensures that only legitimate users can use these tags, and determines the corresponding authorized tag group based on the user authority identifier, making tag acquisition more efficient.

[0025] Optionally, before the tag authorization system receives the tag acquisition request sent by the user, the system further includes:

[0026] The label authorization system receives a label authorization request sent by the user, wherein the label authorization request includes a user identifier, a label group for which authorization is requested, and a business scenario used by the label group;

[0027] The label authorization system receives the authorization result sent by the approval system based on the label authorization request and records the authorization result; the authorization result is used to indicate whether the user is allowed to use the label group applied for authorization in the business scenario used by the applied label group.

[0028] The above solution approves the tag group that the user applies for authorization before the tag is obtained, which improves the security of tag acquisition. At the same time, it integrates multiple business scenarios through the approval system to improve the efficiency of tag acquisition.

[0029] Optionally, the method further includes:

[0030] The label authorization system records the label acquisition request sent by the user, thereby forming an acquisition record of the user.

[0031] The above scheme forms an acquisition record so that each user's tag acquisition request can be traced, thereby improving the security of tag acquisition.

[0032] Optionally, after forming the acquisition record of the user, the method further includes:

[0033] For any tag owner in the acquisition record of the user, determine the frequency of the user acquiring the tag of the tag owner; if the frequency of the user acquiring the tag of the tag owner is greater than a first threshold, determine that the user is a suspected out-of-stock object; or

[0034] According to a first ratio of the number of label owners involved in the label acquisition request of the user within a first set period of time in the acquisition record of the user to the total number of label owners in the label authorization system; if the first ratio is greater than a second threshold value, the user is determined to be a suspected out-of-stock object; or

[0035] A second ratio of the number of label owners involved in labels sent to the user within a second set period of time according to the user's acquisition record to the total number of label owners in the label authorization system; if the second ratio is greater than a third threshold, the user is determined to be a suspected out-of-stock object;

[0036] Execute permission deletion operations based on suspected out-of-database objects.

[0037] The above solution improves the security of tag permission management by judging whether the user is a suspected out-of-stock object from different dimensions.

[0038] Optionally, after forming the acquisition record of the user, the method further includes:

[0039] The tag authorization system obtains pricing information sent by the pricing system, wherein the pricing information includes a pricing identifier, a user authority identifier, and a tag group identifier;

[0040] Generate billing information based on the pricing information and the user's acquisition record;

[0041] The bill information is sent to the pricing system; wherein the pricing system is used to settle accounts with the user.

[0042] The above solution realizes the integrated service of label acquisition and label pricing by generating bill information according to pricing information and the user's acquisition record and sending the bill information to the pricing system.

[0043] Optionally, the tag authorization system receives a tag acquisition request sent by a user, including:

[0044] The label authorization system receives a label acquisition request sent by a user through a label acquisition interface;

[0045] After the tag authorization system receives the tag acquisition request sent by the user, and before the tag authorization system determines the authorized tag group corresponding to the user's authority identifier, the method further includes:

[0046] It is determined that the field information of the tag acquisition request complies with the interface rule of the tag acquisition interface.

[0047] The above solution implements API interface permission control by receiving the tag acquisition request sent by the user through the tag acquisition interface.

[0048] In a second aspect, an embodiment of the present application provides a device for acquiring a tag, the device comprising:

[0049] An acquisition module is used to receive a tag acquisition request sent by a user; the tag acquisition request includes a user authority identifier and a tag master identifier obtained in advance from the tag authorization system; the user authority identifier is determined by the tag authorization system according to the user identifier and the business scenario used by the tag group; the tag master indicated by the tag master identifier has at least one tag describing the tag master;

[0050] A processing module, used to determine the authorized tag group corresponding to the user authority identifier;

[0051] The processing module is further configured to send the tag with the tag primary identifier in the authorized tag group to the user.

[0052] Optionally, the tag acquisition request also includes a user identifier;

[0053] The processing module is specifically used for:

[0054] An authorized tag group that matches the user identifier and the user authority identifier is determined from the tag authorization record.

[0055] Optionally, the acquisition module is further used for:

[0056] Before the label authorization system receives the label acquisition request sent by the user, it receives a label authorization request sent by the user, wherein the label authorization request includes a user identifier, a label group for which authorization is applied, and a business scenario used by the label group;

[0057] Based on the tag authorization request, an authorization result sent by the approval system is received and the authorization result is recorded; the authorization result is used to indicate whether the user is allowed to use the tag group applied for authorization in the business scenario used by the tag group applied for.

[0058] Optionally, the processing module is further used for:

[0059] The tag acquisition request sent by the user is recorded, thereby forming an acquisition record of the user.

[0060] Optionally, the processing module is further used for:

[0061] After forming the acquisition record of the user, for any tag owner in the acquisition record of the user, determine the frequency of the user acquiring the tag of the tag owner; if the frequency of the user acquiring the tag of the tag owner is greater than a first threshold, determine that the user is a suspected out-of-stock object; or

[0062] According to a first ratio of the number of label owners involved in the label acquisition request of the user within a first set period of time in the acquisition record of the user to the total number of label owners in the label authorization system; if the first ratio is greater than a second threshold value, the user is determined to be a suspected out-of-stock object; or

[0063] A second ratio of the number of label owners involved in labels sent to the user within a second set period of time according to the user's acquisition record to the total number of label owners in the label authorization system; if the second ratio is greater than a third threshold, the user is determined to be a suspected out-of-stock object;

[0064] Execute permission deletion operations based on suspected out-of-database objects.

[0065] Optionally, the processing module is further used for:

[0066] After forming the acquisition record of the user, obtaining pricing information sent by the pricing system, the pricing information including a pricing identifier, a user authority identifier, and a tag group identifier;

[0067] Generate billing information based on the pricing information and the user's acquisition record;

[0068] The bill information is sent to the pricing system; wherein the pricing system is used to settle accounts with the user.

[0069] Optionally, the acquisition module is specifically used for:

[0070] Receive a label acquisition request sent by a user through a label acquisition interface;

[0071] The acquisition module is specifically used for:

[0072] After the tag authorization system receives the tag acquisition request sent by the user, before the tag authorization system determines the authorized tag group corresponding to the user's authority identifier, it determines that the field information of the tag acquisition request complies with the interface rules of the tag acquisition interface.

[0073] Accordingly, an embodiment of the present invention further provides a computing device, including:

[0074] A memory for storing program instructions;

[0075] The processor is used to call the program instructions stored in the memory and execute the above-mentioned atomic service scheduling method according to the obtained program.

[0076] Correspondingly, an embodiment of the present invention further provides a computer-readable non-volatile storage medium, including computer-readable instructions. When a computer reads and executes the computer-readable instructions, the computer executes the above-mentioned atomic service scheduling method. BRIEF DESCRIPTION OF THE DRAWINGS

[0077] In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings required for use in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0078] Figure 1 A system framework of a tag acquisition method provided by an embodiment of the present invention;

[0079] Figure 2 A flowchart of a method for obtaining a tag provided by an embodiment of the present invention;

[0080] Figure 3 A flowchart of a method for obtaining a tag provided by an embodiment of the present invention;

[0081] Figure 4 A flowchart of a method for obtaining a tag provided by an embodiment of the present invention;

[0082] Figure 5 A schematic diagram of the structure of a device for acquiring a tag provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0083] In order to make the purpose, technical scheme and advantages of the present invention clearer, the present invention will be further described in detail below with reference to the accompanying drawings. Obviously, the described embodiments are only part of the embodiments of the present invention, rather than all the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0084] First, some terms in the present application are explained so as to be understood by those skilled in the art.

[0085] API: Application Programming Interface, application program interface, provided to other systems for calling to obtain corresponding data or corresponding functions.

[0086] Tags: Usually highly refined feature identifiers defined by humans, such as age, gender, region, interests, etc. These tag sets can abstract the overall information of a tag owner.

[0087] For example, for groups such as "people", features such as "male" and "female" can be abstracted and summarized as "gender", and "gender" is a label. For another example, for objects such as "mobile phones", features such as "Snapdragon 835" and "Snapdragon 845" can be abstracted and summarized as "mobile phone processors", and "mobile phone processors" is a label.

[0088] Tag group: Group tags. Tags of the same category or tags generated by the same business scenario are grouped together.

[0089] Data governance: Determine the compliance of data, whether certain data can be authorized for use in a certain product, or whether certain data can be applied in a certain scenario.

[0090] Pricing system: Price data, collect data usage information, and charge for data value-added services.

[0091] The embodiment of the present invention provides a method for obtaining a tag. The method for obtaining a tag provided by the embodiment of the present invention can be applied to Figure 1 In the system architecture shown, the system architecture includes a user 100 , a label authorization system 200 , a pricing system 300 and an approval system 400 .

[0092] The tag authorization system 200 is used to receive a tag authorization request sent by the user 100 and a tag acquisition request sent by the user 100, and determine the authorized tag group corresponding to the user 100 authority identifier;

[0093] It should be noted that the tag authorization system 200 is also used to send the tags with the tag master identifier in the authorized tag group to the user 100. The tag authorization system 200 is also used to record the tag acquisition request sent by the user, thereby forming the acquisition record of the user.

[0094] Specifically, the pricing system 300 is used to send pricing information to the label authorization system 200 and receive billing information returned by the label authorization system 200 so that the pricing system 300 settles the bill with the user 100 .

[0095] In the embodiment of the present application, the approval system 400 is used to send the authorization result to the label authorization system 200.

[0096] Based on the system architecture shown above, Figure 2 A flowchart corresponding to a method for obtaining a tag provided in an embodiment of the present invention is shown in FIG. Figure 2 As shown, the method includes:

[0097] Step 201: The tag authorization system receives a tag acquisition request sent by a user.

[0098] It should be noted that the tag acquisition request includes the user authority identifier and the tag master identifier; the user authority identifier is determined by the tag authorization system based on the user identifier and the business scenario used by the tag group; the tag master indicated by the tag master identifier has at least one tag that describes the tag master.

[0099] Specifically: obtain the ID of each user and the business scenario corresponding to each tag group;

[0100] A unique user authority identifier is generated for each user identifier and the business scenario used by each tag group, thereby obtaining unique user authority identifiers for various different user identifiers in various scenarios.

[0101] Furthermore, the tag acquisition request also includes a user identifier.

[0102] Step 202: The tag authorization system determines the authorized tag group corresponding to the user's authority identifier.

[0103] Step 203: the tag authorization system sends the tags with the tag master identifier in the authorized tag group to the user.

[0104] Before step 201, the present application provides Figure 3 The method flow of obtaining labels is shown.

[0105] like Figure 3 As shown:

[0106] Step 301: The tag authorization system receives a tag authorization request sent by a user.

[0107] It should be noted that the tag authorization request includes the user ID, the tag group for which authorization is requested, and the business scenario in which the tag group is used;

[0108] Step 302: The label authorization system receives the authorization result sent by the approval system and records the authorization result.

[0109] In the embodiment of the present application, the authorization result is used to indicate whether the user is permitted to use the tag group for which authorization is requested in the business scenario in which the tag group is used.

[0110] The premise of the method for obtaining labels provided in the embodiment of the present application is to implement data labeling for each business scenario and then import it into the label library.

[0111] It should be noted that the tag owner identifier can be an ID card, mobile phone number, device number, etc., which can identify a specific tag owner.

[0112] Furthermore, each tag belongs to a tag group, and each tag group belongs to one or more business scenarios.

[0113] For example, label group 1 includes user A in the loan scenario, and label group 2 includes user A in the borrowing scenario. In one possible implementation, label group 3 is generated due to the combined effect of the loan scenario and the borrowing scenario on user A. At this time, label group 3 belongs to both the loan scenario and the borrowing scenario.

[0114] In the embodiment of the present application, an application form is submitted to the approval system, and after data governance, comprehensive assessment of the business scenario and approval, configuration information is sent to the tag authorization system. In one possible implementation, the tag authorization system includes a tag authorization record, and the approval system configures the configuration information into the tag authorization record of the tag authorization system. The tag authorization system periodically obtains data from the tag authorization record.

[0115] Specifically, when a user needs to obtain a label, he needs to first send a label authorization request to the approval system. In a possible implementation, the label authorization request may be sent in the form of an application form.

[0116] Furthermore, the user shall explain the background, purpose and reason for using the tag in the tag authorization request. The approval system shall conduct a comprehensive assessment based on data governance, business scenarios, etc. It shall determine whether the tag group applied for authorization and the authorization of the tag group for use in this business scenario are compliant and reasonable. If the approval system rejects, it means that the tag authorization request is not approved and the process ends; if the approval system approves the tag authorization request, the approval system will assign a unique user authority identifier to the user, and register the user authority identifier, the authorized tag group list, and the approval system order number in the tag authorization record of the tag authorization system as the authorization result.

[0117] In a possible implementation, after the approval system obtains the tag authorization request, it displays or activates the interface between the tag authorization system and the approval system, and sends the authorization result through the interface between the tag authorization system and the approval system, so that the tag authorization system receives the authorization result of the approval system.

[0118] In another possible implementation, after the approval system obtains the tag authorization request, it activates the authorization phase of the tag authorization system, thereby receiving the authorization result of the approval system in the authorization phase.

[0119] The above scheme establishes a connection with the approval system only after receiving a tag authorization request. If no tag authorization request is received, the interface cannot be displayed or activated, and the authorization link cannot be activated. This prevents cross-system to the approval system without tag authorization. This not only ensures stricter cross-system permission control, but also prevents repeated calls to the approval system when the aforementioned operations do not meet the requirements, thereby reducing invalid operations.

[0120] In a possible implementation, the tag authorization record may be in the form of Table 1. Table 1 includes fields involved in the tag authorization record, namely: user authority identifier, user identifier, user business scenario, tag group, tag group meaning, business scenario used by the tag group, tag group status, and update time.

[0121] It should be noted that the user authority identifier is assigned to a certain user business scenario and corresponds to the user identifier. For example, the user authority identifier WB0001 corresponds to the user business scenario E anti-fraud authorized tag group is tag group BZ0101.

[0122] Further, as shown in Table 1, when an authorized tag group is added, the status is valid, and when an authorized tag group is deleted, the status is invalid. The update time records the time when the tag group is modified or added.

[0123] For example, as shown in Table 1, when the user's business scenario is the business E anti-fraud scenario, the corresponding user ID is 100, and the user applies for the user authority ID WB0001 to access the label groups BZ0101 and BZ0201. These two label groups are generated by the data processing of the business scenarios business A and business B respectively. The label authorization request has been approved by the approval system. The specific approval opinions are in the approval system orders corresponding to the approval system order numbers IM0001 and IM0002.

[0124] Table 1

[0125]

[0126] For another example, as shown in Table 1, when the user's business scenario is business F anti-money laundering, the corresponding user ID is 101, and the user applies for user authority ID WB0002 to access label group BZ0102. Label group BZ0102 is generated by data processing of business scenario business B. The label authorization request has been approved by the approval system. The specific approval opinion is in the approval system order corresponding to the approval system order number IM0003.

[0127] Furthermore, in a possible implementation, the user identifier is a subsystem number that uniquely corresponds to a subsystem, and the subsystem number is included when obtaining tags across businesses through an API, thereby effectively implementing permission isolation for business scenarios used by the tag group.

[0128] It should be noted that the business scenario used by the tag group is the business affiliation of the tag group, that is, the tags in the tag group are based on the data in which business scenario.

[0129] In the embodiment of the present application, the approval system number is a unique number generated by the approval system when the tag authorization request is passed. This number has a traceability function for the authority control when obtaining the tag, and the data corresponding to the approval system number permanently records the entire process of authorizing the tag group applying for authorization to the user.

[0130] From the above content, it can be seen that tag group permissions can be added through tag authorization records, and tag groups can be deleted by recording the status field as invalid.

[0131] Furthermore, in the embodiment of the present application, the tag authorization system records the correspondence between all tags and tag groups and updates it regularly.

[0132] For example, the relationship table between tags and tag groups can be shown in Table 2:

[0133] Table 2

[0134] Label Tag Group Label meaning bzbh10001 BZ0101 Online lending industry bzbh10002 BZ0101 Live broadcast industry bzbh10003 BZ0101 Gaming Industry bzbh20001 BZ0201 Phone model bzbh20002 BZ0102 Province and city bzbh20003 BZ0301 physical education

[0135] It can be seen from the above content that the tag group BZ0101 includes tags bzbh10001, bzbh10002, and bzbh10003. The tag group BZ0201 includes bzbh20001.

[0136] In step 201, the tag authorization system receives a tag acquisition request sent by a user through a tag acquisition interface;

[0137] Further, after step 201 and before step 202, it is determined whether the field information of the tag acquisition request complies with the interface rules of the tag acquisition interface.

[0138] Specifically, after the API provided by the tag authorization system receives a tag acquisition request, it first verifies the legitimacy of the data. For example, whether the field information including the user ID: 100, the user authority ID: WB0001 and the tag master ID USERID: USER001 is empty. If there are empty fields, it returns that the user input parameters are illegal.

[0139] In an embodiment of the present application, if the field information of the tag acquisition request is not empty, then the user identifier and the user authority identifier are used to query Table 1 of the above content. If there is no record, it is returned to the user that the tag acquisition request is illegal and the user authority identifier and the user identifier do not match.

[0140] In step 202, the tag authorization system determines an authorized tag group that matches the user identifier and the user authority identifier from the tag authorization record.

[0141] For example, the user business scenario is the business E anti-fraud scenario, the corresponding user ID is 100, and the corresponding user authority ID is WB0001. When the user requests the tag of the tag master corresponding to the tag master ID: USER001, the user uses the parameters including the user ID: 100, the user authority ID: WB0001, and the tag master ID USERID: USER001 to call the API provided by the tag authorization system.

[0142] In one possible manner, according to the tag owner identifier, such as USERID: USER001, the tag authorization system is queried for all tags of the tag owner, for example, the tags found are bzbh10001, bzbh10002, bzbh20001, and bzbh20003.

[0143] Next, the tag authorization system obtains the authorized tag groups BZ0101 and BZ0201 according to the anti-fraud scenario of business E in Table 1, and then obtains the corresponding tags from Table 2 according to the tag groups.

[0144] Based on this, the authorized tags corresponding to the tag acquisition request are bzbh10001, bzbh10002, bzbh10003, and bzbh20001.

[0145] Furthermore, all the tags of the queried tag owner (bzbh10001, bzbh10002, bzbh20001, bzbh20003) are compared with the obtained authorized tags (bzbh10001, bzbh10002, bzbh10003, bzbh20001), and the unauthorized bzbh20003 tag is deleted. Then the tag list of the corresponding tag owner returned to the user through the API is bzbh10001, bzbh10002 and bzbh20001.

[0146] In another possible implementation, the tag authorization system obtains the authorized tags corresponding to Table 2 according to the authorized tag groups BZ0101 and BZ0201 corresponding to the anti-fraud scenario of business E in Table 1, and the obtained authorized tags are bzbh10001, bzbh10002, bzbh10003 and bzbh20001. The tag authorization system queries the tag library according to the authorized tag list and the tag master identifier, and deletes the tags that are not in the tag authority list. Then the tag list obtained by the tag authorization system from the tag library is bzbh10001, bzbh10002 and bzbh20001, and then the tag authorization system returns the list to the user.

[0147] In an embodiment of the present application, the label authorization system records the label acquisition request sent by the user, thereby forming the user's acquisition record.

[0148] In one possible implementation, the tag authorization system will record the above-mentioned tag acquisition flow into the acquisition record, and the record content includes the user ID, the user authority ID assigned by the approval system, the tag master ID, the query time, the success or failure flag, the returned tag group, the discarded tag group and other information.

[0149] Furthermore, after forming the user's acquisition record, in a possible implementation, the tag authorization system sends the number of tag masters obtained by each user through the API every minute, and obtains the change curve of the number reported by the user every minute according to the user's authority identifier.

[0150] For example, the number of calls per minute corresponding to the user's permission identification is very stable and large. From 0:00 to 24:00, the number obtained per minute has been in the range of 55 to 65. This situation continues for N days. In this case, it is necessary to determine whether the user is delisting.

[0151] Specifically, for any tag owner in the user's acquisition record, the frequency of the user acquiring the tag of the tag owner is determined; if the frequency of the user acquiring the tag of the tag owner is greater than a first threshold, the user is determined to be a suspected out-of-stock object.

[0152] For example, the tag authorization system sets an alarm threshold, such as 3 days. If the call volume per minute is between 55 and 65, an alarm will be issued to indicate that a user is trying to delist, and the user's permission identifier can be listed as a suspicious delisting object.

[0153] Furthermore, when the frequency of the user acquiring the tag owner's tag remains at a relatively high value and does not fluctuate significantly over time, the user's authority identifier can be listed as a suspicious out-of-stock object.

[0154] Specifically, based on a first ratio of the number of label owners involved in the label acquisition request of the user within a first set time period in the user's acquisition record to the total number of label owners in the label authorization system; if the first ratio is greater than a second threshold, the user is determined to be a suspected out-of-stock object.

[0155] In a possible implementation, the number of tag main identifiers requested in N days corresponding to the user's authority identifier and the tag main identifier in the tag library that are the same as the tag main identifier, as a percentage of the total number of tag main identifiers in the tag authorization system is rateA. For example, the number of tag main identifiers requested in 3 days corresponding to the user's authority identifier is 400, the number of tag main identifiers that are the same as the tag main identifier in the tag library is 300, and the total number of tag main identifiers in the tag authorization system is 600. The calculated rateA is 0.5. If rateA is greater than a set threshold value, such as 0.4, it can be listed as a suspected out-of-stock object.

[0156] Specifically, based on the user's acquisition record, a second ratio of the number of tag owners involved in the tags sent to the user within the second set time period to the total number of tag owners in the tag authorization system is determined; if the second ratio is greater than a third threshold, the user is determined to be a suspected out-of-stock object.

[0157] In a possible implementation, the ratio of the number of tag masters returned with tags in the tag master identifiers requested within N days corresponding to the user's authority identifier to the number of tag masters in the tag library is rateB. For example, the number of tag masters returned with tags in the tag master identifiers requested within 5 days corresponding to the user's authority identifier is 500, and the number of tag masters in the tag library is 700. The calculated rateB is 0.71. If rateB is greater than a set threshold value, such as 0.5, it is listed as a suspected out-of-library object.

[0158] It should be noted that the above three examples are used to judge whether the user is a suspected out-of-stock object from three different dimensions. The judgment can also be made based on different proportions of the three dimensions. This application does not make any specific limitations on this.

[0159] Further, when the user's permission identifier is listed as a suspected out-of-stock object, the access rights corresponding to the user's permission identifier can be deleted according to the actual situation. In a possible implementation, after approval by the approval system, the permission configuration authorized to the user's permission identifier is invalidated.

[0160] The above solution analyzes the user's recent tag acquisition request to determine whether the user is a suspected out-of-stock object. The permission corresponding to the user's permission identifier of the suspected out-of-stock object is deactivated, thereby improving the security of tag acquisition.

[0161] Further, after the user's acquisition record is formed, specifically, the present application provides the following Figure 4 The method flow of obtaining labels is shown.

[0162] like Figure 4 As shown:

[0163] Step 401: The label authorization system obtains pricing information sent by the pricing system.

[0164] It should be noted that the pricing information includes a pricing identifier, a user authority identifier, and a tag group identifier.

[0165] Step 402, generating billing information based on the pricing information and the user's acquisition record.

[0166] Step 403: Send the bill information to the pricing system.

[0167] It should be noted that the pricing system is used to settle accounts with users.

[0168] In the embodiment of the present application, when a tag group is authorized to a user on the approval system, a unique pricing ID will be generated, and the pricing ID will be synchronized to the pricing system. The pricing system will record information such as the pricing ID, tag group, business scenario to which the tag group belongs, the user of the tag group, and the billing method.

[0169] In one possible implementation, the tag authorization system will generate a document with the previous day's acquisition records every morning and transmit it to the pricing system. The pricing system will generate a corresponding expense list based on the pricing information and acquisition records corresponding to the pricing ID, and report it to the business scenarios and users to which the tag group belongs. The pricing system will then perform the corresponding fee settlement.

[0170] It should be noted that different tag groups may have different pricing methods, and the same tag group may have different pricing methods when authorized to different users. For example, when tag group 1 of business scenario A is used by user E, the corresponding pricing method is 1, when tag group 1 of business scenario A is used by user F, the corresponding pricing method is 2, and when tag group 1 of business scenario D is used by user E, the corresponding pricing method is 3.

[0171] In the above scheme, the tag authorization system synchronizes the pricing ID of the tag group from the pricing system and obtains the records and pricing information, generates the corresponding billing information, and sends the billing information to the pricing system, which settles the fees with each user, thus realizing the integration of tag pricing and payment in the tag acquisition process.

[0172] Based on the same inventive concept, Figure 5An apparatus for acquiring a tag provided by an embodiment of the present invention is exemplarily shown, and the apparatus may be a process of a method for acquiring a tag.

[0173] The device for obtaining a label includes:

[0174] The acquisition module 501 is used to receive a tag acquisition request sent by a user; the tag acquisition request includes a user authority identifier and a tag master identifier obtained in advance from the tag authorization system; the user authority identifier is determined by the tag authorization system according to the user identifier and the business scenario used by the tag group; the tag master indicated by the tag master identifier has at least one tag describing the tag master;

[0175] Processing module 502, used to determine the authorized tag group corresponding to the user authority identifier;

[0176] The processing module 502 is further configured to send the tag with the tag primary identifier in the authorized tag group to the user.

[0177] Optionally, the tag acquisition request also includes a user identifier;

[0178] The processing module 502 is specifically used for:

[0179] An authorized tag group that matches the user identifier and the user authority identifier is determined from the tag authorization record.

[0180] Optionally, the acquisition module 501 is further used for:

[0181] Before the label authorization system receives the label acquisition request sent by the user, it receives a label authorization request sent by the user, wherein the label authorization request includes a user identifier, a label group for which authorization is applied, and a business scenario used by the label group;

[0182] Based on the tag authorization request, an authorization result sent by the approval system is received and the authorization result is recorded; the authorization result is used to indicate whether the user is allowed to use the tag group applied for authorization in the business scenario used by the tag group applied for.

[0183] Optionally, the processing module 502 is further used for:

[0184] The tag acquisition request sent by the user is recorded, thereby forming an acquisition record of the user.

[0185] Optionally, the processing module 502 is further used for:

[0186] After forming the acquisition record of the user, for any tag owner in the acquisition record of the user, determine the frequency of the user acquiring the tag of the tag owner; if the frequency of the user acquiring the tag of the tag owner is greater than a first threshold, determine that the user is a suspected out-of-stock object; or

[0187] According to a first ratio of the number of label owners involved in the label acquisition request of the user within a first set period of time in the acquisition record of the user to the total number of label owners in the label authorization system; if the first ratio is greater than a second threshold value, the user is determined to be a suspected out-of-stock object; or

[0188] A second ratio of the number of label owners involved in labels sent to the user within a second set period of time according to the user's acquisition record to the total number of label owners in the label authorization system; if the second ratio is greater than a third threshold, the user is determined to be a suspected out-of-stock object;

[0189] Execute permission deletion operations based on suspected out-of-database objects.

[0190] Optionally, the processing module 502 is further used for:

[0191] After forming the acquisition record of the user, obtaining pricing information sent by the pricing system, the pricing information including a pricing identifier, a user authority identifier, and a tag group identifier;

[0192] Generate billing information based on the pricing information and the user's acquisition record;

[0193] The bill information is sent to the pricing system; wherein the pricing system is used to settle accounts with the user.

[0194] Optionally, the acquisition module 501 is specifically used for:

[0195] Receive a label acquisition request sent by a user through a label acquisition interface;

[0196] The acquisition module 501 is specifically used for:

[0197] After the tag authorization system receives the tag acquisition request sent by the user, before the tag authorization system determines the authorized tag group corresponding to the user's authority identifier, it determines that the field information of the tag acquisition request complies with the interface rules of the tag acquisition interface.

[0198] The present invention is described with reference to flowcharts and / or block diagrams of methods, devices (systems), and computer program products according to embodiments of the present invention. It should be understood that each process and / or block in the flowchart and / or block diagram, as well as the combination of processes and / or blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0199] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0200] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0201] Although the preferred embodiments of the present invention have been described, those skilled in the art may make other changes and modifications to these embodiments once they have learned the basic creative concept. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments and all changes and modifications that fall within the scope of the present invention.

[0202] Obviously, those skilled in the art can make various changes and modifications to the present invention without departing from the spirit and scope of the present invention. Thus, if these modifications and variations of the present invention fall within the scope of the claims of the present invention and their equivalents, the present invention is also intended to include these modifications and variations.

Claims

1. A method for obtaining a label, characterized in that: The method comprises: The tag authorization system receives a tag acquisition request sent by a user; the tag acquisition request includes a user authority identifier and a tag master identifier obtained in advance from the tag authorization system; the user authority identifier is determined by the tag authorization system according to the user identifier and the business scenario used by the tag group; the tag master indicated by the tag master identifier has at least one tag describing the tag master; The tag authorization system determines the authorized tag group corresponding to the user authority identifier; The tag authorization system sends the tag with the tag primary identifier in the authorized tag group to the user; The label authorization system receives a label acquisition request sent by a user through a label acquisition interface; Before the label authorization system receives the label acquisition request sent by the user, it also includes: The tag authorization system receives a tag authorization request sent by the user; the tag authorization system receives an authorization result sent by the approval system based on the tag authorization request and records the authorization result in a tag authorization record; after the tag authorization system receives a tag acquisition request sent by the user, before the tag authorization system determines the authorized tag group corresponding to the user's authority identifier, the method further includes: Determine that the field information of the tag acquisition request complies with the interface rules of the tag acquisition interface, wherein the interface rules include: Verify the legitimacy of the data and determine whether the field information in the tag acquisition request is empty, wherein the field information at least includes a user identifier, a user authority identifier, and a tag master identifier; If both are not empty, query the tag authorization record in the tag authorization system according to the user ID and the user authority ID; The tag authorization record includes the user authority identifier, user identifier, user business scenario, tag group and approval system order number; the approval system order number is a unique order number generated when the approval system passes the tag authorization request; If the tag authorization record exists, the tag acquisition request is legal.

2. The method according to claim 1, characterized in that The tag acquisition request also includes a user identifier; The tag authorization system determines the authorized tag group corresponding to the user authority identifier, including: The tag authorization system determines an authorized tag group that matches the user identifier and the user authority identifier from the tag authorization record.

3. The method according to claim 1, characterized in that The tag authorization request includes the user identification, the tag group for which authorization is requested, and the business scenario used by the tag group; The authorization result is used to indicate whether the user is permitted to use the tag group for which authorization is applied in the business scenario in which the tag group is used.

4. The method according to claim 1, characterized in that The method further comprises: The label authorization system records the label acquisition request sent by the user, thereby forming an acquisition record of the user.

5. The method according to claim 4, characterized in that After forming the acquisition record of the user, the method further includes: For any tag owner in the acquisition record of the user, determine the frequency of the user acquiring the tag of the tag owner; if the frequency of the user acquiring the tag of the tag owner is greater than a first threshold, determine that the user is a suspected out-of-stock object; or According to a first ratio of the number of label owners involved in the label acquisition request of the user within a first set period of time in the acquisition record of the user to the total number of label owners in the label authorization system; if the first ratio is greater than a second threshold value, the user is determined to be a suspected out-of-stock object; or A second ratio of the number of label owners involved in labels sent to the user within a second set period of time according to the user's acquisition record to the total number of label owners in the label authorization system; if the second ratio is greater than a third threshold, the user is determined to be a suspected out-of-stock object; Execute permission deletion operations based on suspected out-of-database objects.

6. The method according to claim 4, characterized in that After forming the acquisition record of the user, the method further includes: The tag authorization system obtains pricing information sent by the pricing system, wherein the pricing information includes a pricing identifier, a user authority identifier, and a tag group identifier; Generate billing information based on the pricing information and the user's acquisition record; The bill information is sent to the pricing system; wherein the pricing system is used to settle accounts with the user.

7. A device for obtaining a label, characterized in that: include: The acquisition module is used to receive a tag acquisition request sent by a user; the tag acquisition request includes a user authority identifier and a tag master identifier; The user authority identifier is determined by the device for obtaining the tag according to the user identifier and the business scenario used by the tag group; the tag owner indicated by the tag owner identifier has at least one tag describing the tag owner; each tag belongs to a tag group, and each tag group belongs to one or more business scenarios; A processing module, used to determine the authorized tag group corresponding to the user authority identifier; The processing module is further used to send the tag with the tag primary identifier in the authorized tag group to the user; The acquisition module receives a label acquisition request sent by a user through a label acquisition interface; The acquisition module is also used for: Before the acquisition module receives the tag acquisition request sent by the user, receiving a tag authorization request sent by the user; receiving an authorization result sent by the approval system based on the tag authorization request and recording the authorization result in a tag authorization record; The acquisition module is specifically used for: After the acquisition module receives the tag acquisition request sent by the user, before the processing module determines the authorized tag group corresponding to the user's authority identifier, it is determined that the field information of the tag acquisition request complies with the interface rules of the tag acquisition interface, and the interface rules include: Verify the legitimacy of the data and determine whether the field information in the tag acquisition request is empty, wherein the field information at least includes a user identifier, a user authority identifier, and a tag master identifier; If both are not empty, query the tag authorization record in the device for obtaining the tag according to the user identifier and the user authority identifier; The tag authorization record includes the user authority identifier, user identifier, user business scenario, tag group and approval system order number; the approval system order number is a unique order number generated when the approval system passes the tag authorization request; If there is a tag authorization record, the tag acquisition request is legal.

8. A computing device, characterized in that include: A memory for storing program instructions; A processor, configured to call the program instructions stored in the memory, and execute the method according to any one of claims 1 to 6 according to the obtained program.

9. A computer-readable non-volatile storage medium, characterized in that: The method comprises computer-readable instructions, and when a computer reads and executes the computer-readable instructions, the computer is caused to execute the method according to any one of claims 1 to 6.

Images