CN117349314A - Data screening method, device, equipment and storage medium based on user tag - Google Patents
Data screening method, device, equipment and storage medium based on user tag Download PDFInfo
- Publication number
- CN117349314A CN117349314A CN202311512451.9A CN202311512451A CN117349314A CN 117349314 A CN117349314 A CN 117349314A CN 202311512451 A CN202311512451 A CN 202311512451A CN 117349314 A CN117349314 A CN 117349314A
- Authority
- CN
- China
- Prior art keywords
- tag
- user
- data
- acquiring
- updated
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000012216 screening Methods 0.000 title claims abstract description 94
- 238000000034 method Methods 0.000 title claims abstract description 52
- 230000014509 gene expression Effects 0.000 claims abstract description 53
- 230000006399 behavior Effects 0.000 claims description 33
- 238000004590 computer program Methods 0.000 claims description 17
- 230000002452 interceptive effect Effects 0.000 abstract description 8
- 238000010586 diagram Methods 0.000 description 6
- 238000001914 filtration Methods 0.000 description 6
- 238000013475 authorization Methods 0.000 description 3
- 238000004891 communication Methods 0.000 description 3
- 238000012545 processing Methods 0.000 description 3
- 230000001419 dependent effect Effects 0.000 description 2
- 230000006870 function Effects 0.000 description 2
- 230000000007 visual effect Effects 0.000 description 2
- 238000003491 array Methods 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 235000019800 disodium phosphate Nutrition 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000004044 response Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/24—Querying
- G06F16/242—Query formulation
- G06F16/2433—Query languages
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/24—Querying
- G06F16/245—Query processing
- G06F16/2455—Query execution
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Abstract
The invention discloses a data screening method, a device, equipment and a storage medium based on user labels, wherein the method comprises the following steps: responding to a user data acquisition instruction of a user side, and acquiring user tag configuration data which corresponds to the user data acquisition instruction and has a tag use scene; the user tag configuration data is obtained by correspondingly selecting user tags and entering tag screening conditions on a server; generating a data retrieval expression based on the user tag configuration data; acquiring target user data from a tag library according to the retrieval expression; and sending the target user data to the user terminal. According to the embodiment of the invention, the user tag is selected on the corresponding interactive interface of the user side, the tag screening condition is input and then the user tag is used as tag configuration data, the retrieval expression is automatically generated, and then the target user data is acquired in the tag library of the server, so that the use requirement of the user tag and the difficulty in acquiring the target user data are reduced.
Description
Technical Field
The present invention relates to the field of user portrait technologies, and in particular, to a data screening method, apparatus, device and storage medium based on user labels.
Background
In the development of the internet, various types of applications, such as online shopping applications, information-based applications, etc., are appeared. On the premise of user authorization, the Internet-based application programs can acquire data such as behavior data, user basic data and the like of the application programs used by users, and carefully depict and describe the users based on the behavior data, the user basic data and the like, so that user portraits of the users are obtained.
At present, when an operator screens a target user in user data based on user portrait tags, the user portrait tags are generally set through preliminary screening, and therefore the operator needs to accurately understand the definition of the user portrait tags to set accurate user portrait tags as screening conditions. For example, an operator is required to edit an SQL database query statement based on a tag name corresponding to a user portrait tag, so that target user data corresponding to a target user is obtained by querying in the user data, and the requirement of using professional knowledge of the user tag is high, so that the difficulty of obtaining accurate target user data is high.
Disclosure of Invention
The embodiment of the invention provides a data screening method, a device, equipment and a storage medium based on user labels, which aim to solve the problems that in the prior art, when operators screen target users in user data based on user portrait labels, the operators need to edit SQL database query sentences based on label names corresponding to the user portrait labels, so that the target user data corresponding to the target users are obtained by querying in the user data, the requirement on the use expertise of the user labels is higher, and the difficulty of obtaining accurate target user data is higher.
In a first aspect, an embodiment of the present invention provides a data screening method based on a user tag, including:
responding to a user data acquisition instruction of a user side, and acquiring user tag configuration data which corresponds to the user data acquisition instruction and has a tag use scene; the user tag configuration data is obtained by correspondingly selecting user tags and entering tag screening conditions on a server;
generating a data retrieval expression based on the user tag configuration data;
acquiring target user data from a tag library according to the data retrieval expression;
and sending the target user data to the user terminal.
In a second aspect, an embodiment of the present invention further provides a data filtering device based on a user tag, including:
the configuration data acquisition unit is used for responding to a user data acquisition instruction of a user terminal and acquiring user tag configuration data which corresponds to the user data acquisition instruction and has a tag use scene; the user tag configuration data is obtained by correspondingly selecting user tags and entering tag screening conditions on a server;
an expression generating unit for generating a data retrieval expression based on the user tag configuration data;
The target data acquisition unit is used for acquiring target user data in a tag library according to the data retrieval expression;
and the target data sending unit is used for sending the target user data to the user terminal.
In a third aspect, an embodiment of the present invention further provides a computer device, which includes a memory and a processor, where the memory stores a computer program, and the processor implements the method described in the first aspect when executing the computer program.
In a fourth aspect, embodiments of the present invention also provide a computer readable storage medium storing a computer program comprising program instructions which, when executed by a processor, implement the method of the first aspect.
The embodiment of the invention provides a data screening method, a device, equipment and a storage medium based on user tags, wherein the method comprises the following steps: responding to a user data acquisition instruction of a user side, and acquiring user tag configuration data which corresponds to the user data acquisition instruction and has a tag use scene; the user tag configuration data is obtained by correspondingly selecting user tags and entering tag screening conditions on a server; generating a data retrieval expression based on the user tag configuration data; acquiring target user data from a tag library according to the retrieval expression; and sending the target user data to the user terminal. According to the embodiment of the invention, the user tag is selected on the corresponding interactive interface of the user side, the tag screening condition is input and then the user tag is used as tag configuration data, the retrieval expression is automatically generated, and then the target user data is acquired in the tag library of the server, so that the use requirement of the user tag and the difficulty in acquiring the target user data are reduced.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings required for the description of the embodiments will be briefly described below, and it is obvious that the drawings in the following description are some embodiments of the present invention, and other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
Fig. 1 is a schematic view of an application scenario of a data screening method based on user labels according to an embodiment of the present invention;
fig. 2 is a flow chart of a data screening method based on user labels according to an embodiment of the present invention;
fig. 3 is a schematic sub-flowchart of a data screening method based on a user tag according to an embodiment of the present invention;
fig. 4 is another schematic sub-flowchart of a data screening method based on a user tag according to an embodiment of the present invention;
fig. 5 is a schematic diagram of another sub-flowchart of a data screening method based on a user tag according to an embodiment of the present invention;
FIG. 6 is a schematic block diagram of a user tag-based data screening apparatus according to an embodiment of the present invention;
fig. 7 is a schematic block diagram of a computer device according to an embodiment of the present invention.
Detailed Description
The following description of the embodiments of the present invention will be made clearly and fully with reference to the accompanying drawings, in which it is evident that the embodiments described are some, but not all embodiments of the invention. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention.
It should be understood that the terms "comprises" and "comprising," when used in this specification and the appended claims, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.
It is also to be understood that the terminology used in the description of the invention herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. As used in this specification and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise.
It should be further understood that the term "and/or" as used in the present specification and the appended claims refers to any and all possible combinations of one or more of the associated listed items, and includes such combinations.
Referring to fig. 1 and fig. 2 simultaneously, fig. 1 is a schematic view of a scenario of a data screening method based on a user tag according to an embodiment of the present invention, and fig. 2 is a schematic flow chart of a data screening method based on a user tag according to an embodiment of the present invention. As shown in fig. 1, the data filtering method based on the user tag according to the embodiment of the present invention is applied to a server 10, where the server 10 is communicatively connected to a user terminal 20.
As shown in fig. 2, the method includes the following steps S110 to S140.
S110, responding to a user data acquisition instruction of a user side, and acquiring user tag configuration data which corresponds to the user data acquisition instruction and has a tag use scene.
The user tag configuration data is obtained by correspondingly selecting user tags and entering tag screening conditions on the server.
In this embodiment, the technical scheme is described by using a server as an execution body. The user end used by the operator is in communication connection with the server, and the user end can log in the user data screening system provided by the server, specifically, log in the user data screening system through inputting a user account number password or a scanning code authorization. When an operator needs to set a user tag as one piece of sub-configuration data of the user tag configuration data, at least one user tag can be selected from a plurality of user tags with atomic tag types or derivative tag types which are already set in advance in a tag selection drop-down frame displayed on a corresponding interactive interface of the user data screening system, then a set tag screening condition (such as a tag screening condition is specifically set as a screening time interval, a user age interval and the like) is further input for the selected user tag, and the obtained user tag configuration data can be used for screening user data which has the user tag and meets the tag screening condition in a tag library.
The label use scene corresponding to the user label configuration data is an atomic label or a derivative label, and the derivative label is obtained by combining a plurality of atomic labels. Atomic tags are tag attributes that a user cannot split (e.g., user age, registration time, etc.); the derivative label is a multiple label obtained by combining a plurality of atomic labels. For example, the atomic tags include a behavior attribute tag (refer to an attribute of a behavior feature exhibited by a user in a specific environment, such as a last login APP time, a last access XX page time, etc. may be regarded as a behavior attribute tag), a risk attribute tag (refer to some attribute description of a risk such as a user overdue number of times, etc. a risk attribute tag), a financial attribute tag (refer to a feature attribute or attribute description related to consumption finance, such as a financial attribute tag such as a user quota, etc.), an operation attribute tag (refer to a feature or attribute description exhibited in an operation process, such as an operation attribute tag such as a coupon number, etc.), and a natural attribute tag (refer to a natural attribute tag describing characteristics and attributes of a user, such as a user birthday, a user certificate number, etc.). The derivative tag can be formed by combining a behavior attribute tag such as the last login APP time and an operation attribute tag such as the number of coupons, so as to obtain a derivative tag consisting of two atomic tags such as the last login APP time and the number of coupons.
In one embodiment, step S110 further includes:
if the user data to be updated is detected, determining whether the user data to be updated is of a preset data type; the preset data types comprise a user behavior data type and a user service data type;
if the user data to be updated is determined to be of a preset data type, the user data to be updated is taken as current increment updating data;
acquiring a current tag use scene of the current increment update data;
and if the current tag use scene is determined to be an atomic tag, updating the tag library based on the user data to be updated.
In this embodiment, at least two types of data are updated in a manner of increasing data update when updating the data in the tag library, specifically, a user behavior data type and a user service data type. The user behavior data type data is a specific tag value corresponding to the behavior attribute tag updated to the tag library. The data of the user service data type is updated to a specific tag value corresponding to at least one attribute tag of a financial attribute tag, an operation attribute tag or a natural attribute tag in the tag library, that is, the current tag use scene corresponding to the user service data is possible to be an atomic tag or a derivative tag.
Specifically, when the user data to be updated is determined to be of a preset data type, that is, the user data to be updated is any one of a user behavior data type and a user service data type, the user data to be updated is used as current increment update data. And then acquiring a current tag use scene of the current increment updating data, and if the current tag use scene is determined to be an atomic tag, directly acquiring a tag name corresponding to the user data to be updated and a tag value corresponding to the tag value to update the tag library.
In order to obtain the data source condition of each piece of user tag data in the tag library more clearly, each piece of data in the tag library needs to be stored except for the known tag use scene, and the tag data source corresponding to each piece of data needs to be stored. For example, the user data to be updated is initially stored in the service data table a, and then, when the tag library is updated based on the user data to be updated, the tag data source (i.e. the service data table a) of the user data to be updated also needs to be correspondingly stored in the tag library.
In an embodiment, the updating the tag library based on the user data to be updated includes:
Acquiring a target user entity and a plurality of atom label types corresponding to the user data to be updated;
acquiring target user entity data corresponding to the target user entity from the tag library;
and respectively updating the target user entity data according to the user sub-data to be updated corresponding to each atomic tag type in the atomic tag types in the user data to be updated so as to update the tag library.
In this embodiment, when the tag library is updated with the user data to be updated as current incremental update data, the target user entity corresponding to the user data to be updated (that is, the user data to be updated is to which one or more target users to update the tag value needs to be determined first, that is, a plurality of target user entities to which the user data to be updated is to be updated are acquired) and a plurality of atom tag types to which specific update is to be performed. And after determining the target user entity corresponding to the user data to be updated, acquiring target user entity data which corresponds to the target user entity and is currently stored in a tag library, wherein the target user entity data is the data which needs to be updated. And finally, respectively updating the target user entity data according to the user sub-data to be updated corresponding to each atomic tag type in the plurality of atomic tag types in the user data to be updated so as to update the tag library. Therefore, as long as user data with preset data types is received by the server, the data in the tag library in the server is updated rapidly in an incremental data updating mode, the tag library is not required to be updated in a full data updating mode, and the data updating efficiency is improved.
In an embodiment, after the step of obtaining the current tag usage scenario of the current delta update data, the method further comprises:
if the current tag use scene is determined to be a derivative tag, acquiring a plurality of current atomic tags included in the current tag use scene;
and respectively acquiring corresponding sub-update data from the current increment update data based on the plurality of current atomic tags and updating the tag library.
In this embodiment, when the user data to be updated is of a user service data type, and may be a financial attribute tag, an operation attribute tag or a natural attribute tag, at least two attribute tags are formed, which makes the user data to be updated correspond to derivative tags. In order to quickly update the data in the tag library, the derivative tag corresponding to the user data to be updated can be split into a plurality of current atomic tags, and the value (namely, sub-finer data) of the tag to be updated corresponding to each current atomic tag is obtained. Finally, when the tag library is updated based on the sub-update data corresponding to the current atomic tags, the specific process of updating the tag library based on the user data to be updated may refer to the specific process of updating the tag library under the current tag use scenario of the atomic tags. Therefore, the derivative label does not need to be actively updated, and the label data corresponding to the derivative label can be updated as long as the dependent atomic label is updated.
In one embodiment, step S110 further includes:
if the user data to be updated is detected, and the current tag update data respectively corresponding to a plurality of atomic tags is determined to be included in the user data to be updated, acquiring update priorities respectively corresponding to the atomic tags;
and sequentially updating the tag library by using each atomic tag and the corresponding current tag updating data according to the sequence from high to low of the updating priority corresponding to each atomic tag.
In this embodiment, update priorities corresponding to the plurality of atom labels may also be preset, for example, the behavior attribute label has a first update priority (i.e., the highest update priority), the risk attribute label has a second update priority, the financial attribute label has a third update priority, the operation attribute label has a fourth update priority, and the natural attribute label has a fifth update priority. For example, the user data to be updated includes current tag update data corresponding to a plurality of atomic tags, for example, the current tag update data includes a behavior attribute tag and first current tag update data corresponding to the behavior attribute tag, and further includes a financial attribute tag and second current tag update data corresponding to the financial attribute tag. At this time, the behavior attribute tag and the first current tag update data corresponding to the behavior attribute tag are obtained first, so that the tag value corresponding to the behavior attribute tag of the target user A in the tag library is updated to the first current tag update data. And similarly, acquiring the financial attribute tag and the second current tag updating data corresponding to the financial attribute tag, and updating the value of the tag which is specifically corresponding to the financial attribute tag of the target user A in the tag library into the second current tag updating data. Therefore, based on the setting of the update priorities corresponding to the attribute tags, the method can effectively control the update data of the current tags in the user data to be updated, which is used as incremental data update, to sequentially update the tag library in sequence, and can avoid the problem of massive occupation of server system resources caused by simultaneous tag library update operation.
In one embodiment, as shown in fig. 3, step S110 includes:
s111, acquiring a tag name and a tag screening condition included in the user data acquisition instruction;
s112, acquiring the label use scene corresponding to the user data acquisition instruction, and forming the user label configuration data together with the label name and the label screening condition.
In this embodiment, after the server obtains the user data obtaining instruction, the user data obtaining instruction is parsed to obtain the tag name and the tag screening condition included in the user data obtaining instruction, which are also the tag name and the tag screening condition set on the user data screening system logged in by the user terminal. When the tag name and the tag screening condition are acquired, the tag usage scene corresponding to the user data acquisition instruction is also required to be acquired, and finally the tag configuration data of the user is formed by the tag name, the tag screening condition and the tag usage scene. It can be seen that the user tag configuration data is simply configured by the user based on the visual selection tag (the tag is automatically determined to be an atomic tag type or a derivative tag type after being selected) and the input tag screening condition, and the user is not required to edit the database query statement.
S120, generating a data retrieval expression based on the user tag configuration data.
In this embodiment, after the user tag configuration data is obtained in the server, an operator does not need to manually edit a database query statement, but the server generates a data retrieval expression based on the user tag configuration data, so as to improve the degree of intelligentization of data retrieval.
In one embodiment, as shown in fig. 4, step S120 includes:
s121, acquiring the tag name, the tag screening condition and the tag use scene in the user tag configuration data;
s122, acquiring a first database retrieval sub-expression corresponding to the tag name;
s123, obtaining a second database retrieval sub-expression corresponding to the tag screening condition;
s124, acquiring a third database retrieval sub-expression corresponding to the label use scene;
s125, obtaining the data retrieval expression based on the first database retrieval sub-expression, the second database retrieval sub-expression and the third database retrieval sub-expression.
In this embodiment, after the server obtains the user tag configuration data, the server analyzes the user tag configuration data to obtain the tag name, the tag screening condition and the tag usage scenario included in the user tag configuration data; generating corresponding database retrieval sub-expressions for the 3 parameters respectively, namely generating corresponding first database retrieval sub-expressions for the tag names, generating corresponding second database retrieval sub-expressions for the tag screening conditions, and generating corresponding third database retrieval sub-expressions for the tag usage scenarios; AND finally, combining the first database retrieval sub-expression, the second database retrieval sub-expression AND the third database retrieval sub-expression in an AND relationship to obtain the data retrieval expression for screening target user data from a tag library. Therefore, the data retrieval expression is generated automatically by the server without manual editing, so that the generation efficiency is improved.
S130, acquiring target user data from a tag library according to the data retrieval expression.
In this embodiment, after the data retrieval expression is obtained in the server, the target user data is correspondingly obtained in the tag library in which the tag data is stored in the server, with the data retrieval expression as a retrieval condition, so that the screening process of the target user is rapidly completed.
In one embodiment, as shown in fig. 5, step S130 includes:
s131, acquiring a current target user entity set corresponding to the data retrieval expression from the tag library;
s132, obtaining user entity data corresponding to each current target user entity in the current target user entity set in the tag library to form the target user data.
In this embodiment, when the target user data is obtained in the tag library based on the data retrieval expression, the expressions connected in the AND relationship corresponding to the first database retrieval sub-expression, the second database retrieval sub-expression AND the third database retrieval sub-expression are directly used as retrieval conditions, AND each current target user entity corresponding to the tag name AND the tag screening condition is retrieved first to form a current target user entity set, AND then user entity data corresponding to each current target user entity is obtained to form the target user data. It can be seen that the target user data can be quickly and accurately acquired based on the automatically generated data retrieval expression.
And S140, the target user data is sent to the user terminal.
In this embodiment, after the target user data is obtained in the server, the target user data may be timely sent to the user side, so that the user corresponding to the user side may further use the target user data.
Therefore, in the embodiment of the method, the user tag is selected on the corresponding interactive interface of the user side, the tag screening condition is input and then the user tag is used as tag configuration data, the retrieval expression is automatically generated, and then the target user data is acquired in the tag library of the server, so that the use requirement of the user tag and the difficulty in acquiring the target user data are reduced.
Fig. 6 is a schematic block diagram of a data screening device based on a user tag according to an embodiment of the present invention. As shown in fig. 6, the present invention further provides a data screening device 100 based on a user tag, corresponding to the above data screening method based on a user tag. The user tag based data screening apparatus 100 includes means for performing the above-described user tag based data screening method. Referring to fig. 6, the user tag-based data filtering apparatus 100 includes: a configuration data acquisition unit 110, an expression generation unit 120, a target data acquisition unit 130, and a target data transmission unit 140.
The configuration data obtaining unit 110 is configured to obtain, in response to a user data obtaining instruction of a user terminal, user tag configuration data corresponding to the user data obtaining instruction and having a tag usage scenario.
The user tag configuration data is obtained by correspondingly selecting user tags and entering tag screening conditions on the server.
In this embodiment, the technical scheme is described by using a server as an execution body. The user end used by the operator is in communication connection with the server, and the user end can log in the user data screening system provided by the server, specifically, log in the user data screening system through inputting a user account number password or a scanning code authorization. When an operator needs to set a user tag as one piece of sub-configuration data of the user tag configuration data, at least one user tag can be selected from a plurality of user tags with atomic tag types or derivative tag types which are already set in advance in a tag selection drop-down frame displayed on a corresponding interactive interface of the user data screening system, then a set tag screening condition (such as a tag screening condition is specifically set as a screening time interval, a user age interval and the like) is further input for the selected user tag, and the obtained user tag configuration data can be used for screening user data which has the user tag and meets the tag screening condition in a tag library.
The label use scene corresponding to the user label configuration data is an atomic label or a derivative label, and the derivative label is obtained by combining a plurality of atomic labels. Atomic tags are tag attributes that a user cannot split (e.g., user age, registration time, etc.); the derivative label is a multiple label obtained by combining a plurality of atomic labels. For example, the atomic tags include a behavior attribute tag (refer to an attribute of a behavior feature exhibited by a user in a specific environment, such as a last login APP time, a last access XX page time, etc. may be regarded as a behavior attribute tag), a risk attribute tag (refer to some attribute description of a risk such as a user overdue number of times, etc. a risk attribute tag), a financial attribute tag (refer to a feature attribute or attribute description related to consumption finance, such as a financial attribute tag such as a user quota, etc.), an operation attribute tag (refer to a feature or attribute description exhibited in an operation process, such as an operation attribute tag such as a coupon number, etc.), and a natural attribute tag (refer to a natural attribute tag describing characteristics and attributes of a user, such as a user birthday, a user certificate number, etc.). The derivative tag can be formed by combining a behavior attribute tag such as the last login APP time and an operation attribute tag such as the number of coupons, so as to obtain a derivative tag consisting of two atomic tags such as the last login APP time and the number of coupons.
In one embodiment, the user tag based data filtering apparatus 100 further includes:
the data type judging unit is used for determining whether the user data to be updated is of a preset data type or not if the user data to be updated is detected; the preset data types comprise a user behavior data type and a user service data type;
the incremental data acquisition unit is used for taking the user data to be updated as current incremental update data if the user data to be updated is determined to be of a preset data type;
a current tag usage scenario acquisition unit, configured to acquire a current tag usage scenario of the current incremental update data;
and the first updating control unit is used for updating the tag library based on the user data to be updated if the current tag use scene is determined to be an atomic tag.
In this embodiment, at least two types of data are updated in a manner of increasing data update when updating the data in the tag library, specifically, a user behavior data type and a user service data type. The user behavior data type data is a specific tag value corresponding to the behavior attribute tag updated to the tag library. The data of the user service data type is updated to a specific tag value corresponding to at least one attribute tag of a financial attribute tag, an operation attribute tag or a natural attribute tag in the tag library, that is, the current tag use scene corresponding to the user service data is possible to be an atomic tag or a derivative tag.
Specifically, when the user data to be updated is determined to be of a preset data type, that is, the user data to be updated is any one of a user behavior data type and a user service data type, the user data to be updated is used as current increment update data. And then acquiring a current tag use scene of the current increment updating data, and if the current tag use scene is determined to be an atomic tag, directly acquiring a tag name corresponding to the user data to be updated and a tag value corresponding to the tag value to update the tag library.
In order to obtain the data source condition of each piece of user tag data in the tag library more clearly, each piece of data in the tag library needs to be stored except for the known tag use scene, and the tag data source corresponding to each piece of data needs to be stored. For example, the user data to be updated is initially stored in the service data table a, and then, when the tag library is updated based on the user data to be updated, the tag data source (i.e. the service data table a) of the user data to be updated also needs to be correspondingly stored in the tag library.
In an embodiment, the updating the tag library based on the user data to be updated includes:
Acquiring a target user entity and a plurality of atom label types corresponding to the user data to be updated;
acquiring target user entity data corresponding to the target user entity from the tag library;
and respectively updating the target user entity data according to the user sub-data to be updated corresponding to each atomic tag type in the atomic tag types in the user data to be updated so as to update the tag library.
In this embodiment, when the tag library is updated with the user data to be updated as current incremental update data, the target user entity corresponding to the user data to be updated (that is, the user data to be updated is to which one or more target users to update the tag value needs to be determined first, that is, a plurality of target user entities to which the user data to be updated is to be updated are acquired) and a plurality of atom tag types to which specific update is to be performed. And after determining the target user entity corresponding to the user data to be updated, acquiring target user entity data which corresponds to the target user entity and is currently stored in a tag library, wherein the target user entity data is the data which needs to be updated. And finally, respectively updating the target user entity data according to the user sub-data to be updated corresponding to each atomic tag type in the plurality of atomic tag types in the user data to be updated so as to update the tag library. Therefore, as long as user data with preset data types is received by the server, the data in the tag library in the server is updated rapidly in an incremental data updating mode, the tag library is not required to be updated in a full data updating mode, and the data updating efficiency is improved.
In one embodiment, the user tag based data filtering apparatus 100 further includes:
the current tag splitting unit is used for acquiring a plurality of current atomic tags included in the current tag usage scene if the current tag usage scene is determined to be a derivative tag;
and the second updating control unit is used for respectively acquiring corresponding sub-updating data in the current increment updating data based on the plurality of current atomic tags and updating the tag library.
In this embodiment, when the user data to be updated is of a user service data type, and may be a financial attribute tag, an operation attribute tag or a natural attribute tag, at least two attribute tags are formed, which makes the user data to be updated correspond to derivative tags. In order to quickly update the data in the tag library, the derivative tag corresponding to the user data to be updated can be split into a plurality of current atomic tags, and the value (namely, sub-finer data) of the tag to be updated corresponding to each current atomic tag is obtained. Finally, when the tag library is updated based on the sub-update data corresponding to the current atomic tags, the specific process of updating the tag library based on the user data to be updated may refer to the specific process of updating the tag library under the current tag use scenario of the atomic tags. Therefore, the derivative label does not need to be actively updated, and the label data corresponding to the derivative label can be updated as long as the dependent atomic label is updated.
In one embodiment, the user tag based data filtering apparatus 100 further includes:
the updating priority acquiring unit is used for acquiring the updating priority respectively corresponding to the atomic tags if the user data to be updated is detected and the current tag updating data respectively corresponding to the atomic tags is determined to be included in the user data to be updated;
and the third updating control unit is used for sequentially updating the tag library by each atomic tag and the corresponding current tag updating data according to the sequence from high to low of the updating priority corresponding to each atomic tag.
In this embodiment, update priorities corresponding to the plurality of atom labels may also be preset, for example, the behavior attribute label has a first update priority (i.e., the highest update priority), the risk attribute label has a second update priority, the financial attribute label has a third update priority, the operation attribute label has a fourth update priority, and the natural attribute label has a fifth update priority. For example, the user data to be updated includes current tag update data corresponding to a plurality of atomic tags, for example, the current tag update data includes a behavior attribute tag and first current tag update data corresponding to the behavior attribute tag, and further includes a financial attribute tag and second current tag update data corresponding to the financial attribute tag. At this time, the behavior attribute tag and the first current tag update data corresponding to the behavior attribute tag are obtained first, so that the tag value corresponding to the behavior attribute tag of the target user A in the tag library is updated to the first current tag update data. And similarly, acquiring the financial attribute tag and the second current tag updating data corresponding to the financial attribute tag, and updating the value of the tag which is specifically corresponding to the financial attribute tag of the target user A in the tag library into the second current tag updating data. Therefore, based on the setting of the update priorities corresponding to the attribute tags, the method can effectively control the update data of the current tags in the user data to be updated, which is used as incremental data update, to sequentially update the tag library in sequence, and can avoid the problem of massive occupation of server system resources caused by simultaneous tag library update operation.
In an embodiment, the configuration data acquisition unit 110 is configured to:
acquiring a tag name and a tag screening condition included in the user data acquisition instruction;
and acquiring the label use scene corresponding to the user data acquisition instruction, and forming the user label configuration data together with the label name and the label screening condition.
In this embodiment, after the server obtains the user data obtaining instruction, the user data obtaining instruction is parsed to obtain the tag name and the tag screening condition included in the user data obtaining instruction, which are also the tag name and the tag screening condition set on the user data screening system logged in by the user terminal. When the tag name and the tag screening condition are acquired, the tag usage scene corresponding to the user data acquisition instruction is also required to be acquired, and finally the tag configuration data of the user is formed by the tag name, the tag screening condition and the tag usage scene. It can be seen that the user tag configuration data is simply configured by the user based on the visual selection tag (the tag is automatically determined to be an atomic tag type or a derivative tag type after being selected) and the input tag screening condition, and the user is not required to edit the database query statement.
An expression generating unit 120 for generating a data retrieval expression based on the user tag configuration data.
In this embodiment, after the user tag configuration data is obtained in the server, an operator does not need to manually edit a database query statement, but the server generates a data retrieval expression based on the user tag configuration data, so as to improve the degree of intelligentization of data retrieval.
In an embodiment, the expression generating unit 120 is configured to:
acquiring the tag name, the tag screening condition and the tag use scene in the user tag configuration data;
acquiring a first database retrieval sub-expression corresponding to the tag name;
acquiring a second database retrieval sub-expression corresponding to the tag screening condition;
acquiring a third database retrieval sub-expression corresponding to the label use scene;
and obtaining the data retrieval expression based on the first database retrieval sub-expression, the second database retrieval sub-expression and the third database retrieval sub-expression.
In this embodiment, after the server obtains the user tag configuration data, the server analyzes the user tag configuration data to obtain the tag name, the tag screening condition and the tag usage scenario included in the user tag configuration data; generating corresponding database retrieval sub-expressions for the 3 parameters respectively, namely generating corresponding first database retrieval sub-expressions for the tag names, generating corresponding second database retrieval sub-expressions for the tag screening conditions, and generating corresponding third database retrieval sub-expressions for the tag usage scenarios; AND finally, combining the first database retrieval sub-expression, the second database retrieval sub-expression AND the third database retrieval sub-expression in an AND relationship to obtain the data retrieval expression for screening target user data from a tag library. Therefore, the data retrieval expression is generated automatically by the server without manual editing, so that the generation efficiency is improved.
And a target data acquisition unit 130, configured to acquire target user data in the tag library according to the data retrieval expression.
In this embodiment, after the data retrieval expression is obtained in the server, the target user data is correspondingly obtained in the tag library in which the tag data is stored in the server, with the data retrieval expression as a retrieval condition, so that the screening process of the target user is rapidly completed.
In an embodiment, the target data acquisition unit 130 is configured to:
acquiring a current target user entity set corresponding to the data retrieval expression from the tag library;
and acquiring user entity data corresponding to each current target user entity in the current target user entity set from the tag library to form the target user data.
In this embodiment, when the target user data is obtained in the tag library based on the data retrieval expression, the expressions connected in the AND relationship corresponding to the first database retrieval sub-expression, the second database retrieval sub-expression AND the third database retrieval sub-expression are directly used as retrieval conditions, AND each current target user entity corresponding to the tag name AND the tag screening condition is retrieved first to form a current target user entity set, AND then user entity data corresponding to each current target user entity is obtained to form the target user data. It can be seen that the target user data can be quickly and accurately acquired based on the automatically generated data retrieval expression.
And a target data sending unit 140, configured to send the target user data to the user side.
In this embodiment, after the target user data is obtained in the server, the target user data may be timely sent to the user side, so that the user corresponding to the user side may further use the target user data.
Therefore, in the embodiment of the device, the user tag is selected on the corresponding interactive interface of the user side, the tag screening condition is input and then the user tag is used as tag configuration data, the retrieval expression is automatically generated, and then the target user data is acquired in the tag library of the server, so that the use requirement of the user tag and the difficulty in acquiring the target user data are reduced.
The above-described user tag based data screening apparatus may be implemented in the form of a computer program which is executable on a computer device as shown in fig. 7.
Referring to fig. 7, fig. 7 is a schematic block diagram of a computer device according to an embodiment of the present invention. The computer equipment integrates any data screening device based on the user tag provided by the embodiment of the invention.
With reference to fig. 7, the computer device includes a processor 402, a memory, and a network interface 405, which are connected by a system bus 401, wherein the memory may include a storage medium 403 and an internal memory 404.
The storage medium 403 may store an operating system 4031 and a computer program 4032. The computer program 4032 includes program instructions that, when executed, cause the processor 402 to perform a user tag based data screening method.
The processor 402 is used to provide computing and control capabilities to support the operation of the overall computer device.
The internal memory 404 provides an environment for the execution of a computer program 4032 in the storage medium 403, which computer program 4032, when executed by the processor 402, causes the processor 402 to perform the user tag based data screening method described above.
The network interface 405 is used for network communication with other devices. It will be appreciated by those skilled in the art that the structure shown in FIG. 7 is merely a block diagram of some of the structures associated with the present inventive arrangements and is not limiting of the computer device to which the present inventive arrangements may be applied, and that a particular computer device may include more or fewer components than shown, or may combine some of the components, or have a different arrangement of components.
Wherein the processor 402 is configured to execute a computer program 4032 stored in the memory to implement the steps of:
Responding to a user data acquisition instruction of a user side, and acquiring user tag configuration data which corresponds to the user data acquisition instruction and has a tag use scene; the label use scene corresponding to the user label configuration data is an atomic label or a derivative label, and the derivative label is obtained by combining a plurality of atomic labels; the user tag configuration data are obtained by selecting user tags and entering tag screening conditions on an interactive interface corresponding to a user side by an operation user;
generating a data retrieval expression based on the user tag configuration data;
acquiring target user data from a tag library according to the data retrieval expression;
and sending the target user data to the user terminal.
It should be appreciated that in embodiments of the present invention, the processor 402 may be a central processing unit (Central Processing Unit, CPU), the processor 402 may also be other general purpose processors, digital signal processors (Digital Signal Processor, DSPs), application specific integrated circuits (Application Specific Integrated Circuit, ASICs), off-the-shelf programmable gate arrays (Field-Programmable Gate Array, FPGAs) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, or the like. Wherein the general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
Those skilled in the art will appreciate that all or part of the flow in a method embodying the above described embodiments may be accomplished by computer programs instructing the relevant hardware. The computer program comprises program instructions, and the computer program can be stored in a storage medium, which is a computer readable storage medium. The program instructions are executed by at least one processor in the computer system to implement the flow steps of the embodiments of the method described above.
Accordingly, the present invention also provides a computer-readable storage medium. The computer readable storage medium stores a computer program, wherein the computer program includes program instructions. The program instructions, when executed by the processor, cause the processor to perform the steps of:
responding to a user data acquisition instruction of a user side, and acquiring user tag configuration data which corresponds to the user data acquisition instruction and has a tag use scene; the label use scene corresponding to the user label configuration data is an atomic label or a derivative label, and the derivative label is obtained by combining a plurality of atomic labels; the user tag configuration data are obtained by selecting user tags and entering tag screening conditions on an interactive interface corresponding to a user side by an operation user;
Generating a data retrieval expression based on the user tag configuration data;
acquiring target user data from a tag library according to the data retrieval expression;
and sending the target user data to the user terminal.
The storage medium may be a U-disk, a removable hard disk, a Read-Only Memory (ROM), a magnetic disk, or an optical disk, or other various computer-readable storage media that can store program codes.
Those of ordinary skill in the art will appreciate that the elements and algorithm steps described in connection with the embodiments disclosed herein may be embodied in electronic hardware, in computer software, or in a combination of the two, and that the elements and steps of the examples have been generally described in terms of function in the foregoing description to clearly illustrate the interchangeability of hardware and software. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.
In the several embodiments provided by the present invention, it should be understood that the disclosed apparatus and method may be implemented in other manners. For example, the device embodiments described above are merely illustrative. For example, the division of each unit is only one logic function division, and there may be another division manner in actual implementation. For example, multiple units or components may be combined or may be integrated into another system, or some features may be omitted, or not performed.
The steps in the method of the embodiment of the invention can be sequentially adjusted, combined and deleted according to actual needs. The units in the device of the embodiment of the invention can be combined, divided and deleted according to actual needs. In addition, each functional unit in the embodiments of the present invention may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit.
The integrated unit may be stored in a storage medium if implemented in the form of a software functional unit and sold or used as a stand-alone product. Based on such understanding, the technical solution of the present invention is essentially or a part contributing to the prior art, or all or part of the technical solution may be embodied in the form of a software product stored in a storage medium, comprising several instructions for causing a computer device (which may be a personal computer, a terminal, a network device, etc.) to perform all or part of the steps of the method according to the embodiments of the present invention.
While the invention has been described with reference to certain preferred embodiments, it will be understood by those skilled in the art that various changes and substitutions of equivalents may be made and equivalents will be apparent to those skilled in the art without departing from the scope of the invention. Therefore, the protection scope of the invention is subject to the protection scope of the claims.
Claims (10)
1. A data screening method based on user tags, comprising:
responding to a user data acquisition instruction of a user side, and acquiring user tag configuration data which corresponds to the user data acquisition instruction and has a tag use scene; the user tag configuration data is obtained by correspondingly selecting user tags and entering tag screening conditions on a server;
generating a data retrieval expression based on the user tag configuration data;
acquiring target user data from a tag library according to the data retrieval expression;
and sending the target user data to the user terminal.
2. The method according to claim 1, wherein the label usage scenario corresponding to the user label configuration data is an atomic label or a derivative label, and the derivative label is obtained by combining a plurality of atomic labels;
before the step of responding to the user data acquisition instruction of the user terminal and acquiring the user tag configuration data which corresponds to the user data acquisition instruction and has a tag use scene, the method further comprises:
if the user data to be updated is detected, determining whether the user data to be updated is of a preset data type; the preset data types comprise a user behavior data type and a user service data type;
If the user data to be updated is determined to be of a preset data type, the user data to be updated is taken as current increment updating data;
acquiring a current tag use scene of the current increment update data;
and if the current tag use scene is determined to be an atomic tag, updating the tag library based on the user data to be updated.
3. The method of claim 2, wherein the updating the tag library based on the user data to be updated comprises:
acquiring a target user entity and a plurality of atom label types corresponding to the user data to be updated;
acquiring target user entity data corresponding to the target user entity from the tag library;
and respectively updating the target user entity data according to the user sub-data to be updated corresponding to each atomic tag type in the atomic tag types in the user data to be updated so as to update the tag library.
4. The method of claim 2, wherein after the step of obtaining the current tag usage scenario of the current delta update data, the method further comprises:
if the current tag use scene is determined to be a derivative tag, acquiring a plurality of current atomic tags included in the current tag use scene;
And respectively acquiring corresponding sub-update data from the current increment update data based on the plurality of current atomic tags and updating the tag library.
5. The method of claim 1, wherein the obtaining user tag configuration data corresponding to the user data obtaining instruction and having a tag usage scenario comprises:
acquiring a tag name and a tag screening condition included in the user data acquisition instruction;
and acquiring the label use scene corresponding to the user data acquisition instruction, and forming the user label configuration data together with the label name and the label screening condition.
6. The method of claim 5, wherein generating a data retrieval expression based on the user tag configuration data comprises:
acquiring the tag name, the tag screening condition and the tag use scene in the user tag configuration data;
acquiring a first database retrieval sub-expression corresponding to the tag name;
acquiring a second database retrieval sub-expression corresponding to the tag screening condition;
acquiring a third database retrieval sub-expression corresponding to the label use scene;
And obtaining the data retrieval expression based on the first database retrieval sub-expression, the second database retrieval sub-expression and the third database retrieval sub-expression.
7. The method of claim 1, wherein the obtaining target user data in a tag library according to the data retrieval expression comprises:
acquiring a current target user entity set corresponding to the data retrieval expression from the tag library;
and acquiring user entity data corresponding to each current target user entity in the current target user entity set from the tag library to form the target user data.
8. A user tag-based data screening apparatus, comprising:
the configuration data acquisition unit is used for responding to a user data acquisition instruction of a user terminal and acquiring user tag configuration data which corresponds to the user data acquisition instruction and has a tag use scene; the user tag configuration data is obtained by correspondingly selecting user tags and entering tag screening conditions on a server;
an expression generating unit for generating a data retrieval expression based on the user tag configuration data;
The target data acquisition unit is used for acquiring target user data in a tag library according to the data retrieval expression;
and the target data sending unit is used for sending the target user data to the user terminal.
9. A computer device comprising a memory and a processor, the memory having stored thereon a computer program, the processor implementing the user tag based data screening method according to any of claims 1-7 when the computer program is executed.
10. A computer readable storage medium, characterized in that the computer readable storage medium stores a computer program comprising program instructions which, when executed by a processor, can implement the user tag based data screening method according to any of claims 1-7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311512451.9A CN117349314A (en) | 2023-11-14 | 2023-11-14 | Data screening method, device, equipment and storage medium based on user tag |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311512451.9A CN117349314A (en) | 2023-11-14 | 2023-11-14 | Data screening method, device, equipment and storage medium based on user tag |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN117349314A true CN117349314A (en) | 2024-01-05 |
Family
ID=89361518
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202311512451.9A Pending CN117349314A (en) | 2023-11-14 | 2023-11-14 | Data screening method, device, equipment and storage medium based on user tag |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN117349314A (en) |
-
2023
- 2023-11-14 CN CN202311512451.9A patent/CN117349314A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11799728B2 (en) | Multistage device clustering | |
| US6806890B2 (en) | Generating a graphical user interface from a command syntax for managing multiple computer systems as one computer system | |
| US20180212985A1 (en) | Identifying attack behavior based on scripting language activity | |
| US11755577B1 (en) | Skewing of scheduled search queries | |
| US20090210360A1 (en) | Computing the values of configuration parameters for optimal performance of associated applications | |
| DE112016002120T5 (en) | Development and sales platform for software | |
| US20040205748A1 (en) | System and method for providing service of automated creation of computer software production images | |
| JP4880376B2 (en) | Support apparatus, program, information processing system, and support method | |
| US20180218269A1 (en) | Event forecasting | |
| US8694964B1 (en) | Managing code samples in documentation | |
| US20210383370A1 (en) | Enhanced multi-party user data deletion | |
| US20090119158A1 (en) | Method and device for tracing and locating web services changes during updating process | |
| US9037552B2 (en) | Methods for analyzing a database and devices thereof | |
| US20140244784A1 (en) | Website Impersonation System and Method | |
| US20170346909A1 (en) | Client-side bottleneck analysis using real user monitoring data | |
| US20230015186A1 (en) | Partially typed semantic based query execution optimization | |
| US8346799B1 (en) | Recent content rank adjustment with inverted decay | |
| US8606762B2 (en) | Data quality administration framework | |
| US11429608B2 (en) | Optimizing search of an accelerated data model by enabling emitting of structured and unstructured fields from the data model | |
| US20110246261A1 (en) | User-generated content policy optimization | |
| US11237889B1 (en) | Application infrastructure configuration based on annotated API schemas | |
| CN117349314A (en) | Data screening method, device, equipment and storage medium based on user tag | |
| JP2007219619A (en) | Information management program, device, and method | |
| CN115757995A (en) | Method and device for processing characteristic-free data label, computer equipment and storage medium | |
| US20100274615A1 (en) | Extendable Collaborative Correction Framework |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |