Label preposition data query method and device, electronic equipment and readable storage medium

Abstract

This application discloses a method, apparatus, electronic device, and readable storage medium for querying tag-based pre-data, applied in the field of user profiling technology. The tag-based pre-data query method includes: obtaining data query information from a tag data query page; determining whether a corresponding tag data index exists based on the query tag corresponding to the data query information; and if so, displaying the tag-based pre-data corresponding to the tag data index on the tag data query page. The tag-based pre-data is used to generate user tags. This application solves the technical problem of low efficiency in user tag production.

Description

Technical Field

[0001] This application relates to the field of user profiling technology, and in particular to a method, apparatus, electronic device, and readable storage medium for querying tag-based pre-data. Background Technology

[0002] With the continuous development of the mobile internet, user profiling based on big data technology has been widely used in various industries to provide users with more targeted services. The generation of user profiles and user tags are inextricably linked. To produce user tags, the user profiling system needs to find the corresponding data. Currently, data analysts usually perform this data querying to generate corresponding user tags. However, because there are multiple sub-processes in the user tag generation process that require querying this data, the staff in these sub-processes can only consult the relevant data analysts when they need to query this data. This results in excessive communication costs in the user tag production process, and therefore, the current efficiency of user tag production is low. Summary of the Invention

[0003] The main purpose of this application is to provide a method, apparatus, electronic device and readable storage medium for querying tag front-end data, aiming to solve the technical problem of low production efficiency of user tags in the prior art.

[0004] To achieve the above objectives, this application provides a method for querying tag-pre-data, the method comprising:

[0005] Obtain data query information on the tag data query page;

[0006] Based on the query tags corresponding to the data query information, determine whether a corresponding tag data index exists;

[0007] If so, the tag preceding data corresponding to the tag data index will be displayed according to the tag data query page, wherein the tag preceding data is used to generate user tags.

[0008] To achieve the above objectives, this application also provides a tag-pre-data query device, the tag-pre-data query device comprising:

[0009] The acquisition module is used to retrieve data query information from the tag data query page;

[0010] The determination module is used to determine whether a corresponding tag data index exists based on the query tag corresponding to the data query information;

[0011] The display module is used to display the tag preceding data corresponding to the tag data index according to the tag data query page if the tag is true, wherein the tag preceding data is used to generate user tags.

[0012] This application also provides an electronic device, the electronic device comprising: a memory, a processor, and a program of the tag pre-data query method stored in the memory and executable on the processor, wherein when the program of the tag pre-data query method is executed by the processor, it can implement the steps of the tag pre-data query method as described above.

[0013] This application also provides a computer-readable storage medium storing a program for implementing a tag-pre-data query method, wherein when the program for the tag-pre-data query method is executed by a processor, it implements the steps of the tag-pre-data query method as described above.

[0014] This application also provides a computer program product, including a computer program that, when executed by a processor, implements the steps of the tag-pre-data query method described above.

[0015] This application provides a method, apparatus, electronic device, and readable storage medium for querying tag-pre-data. Specifically, it involves obtaining data query information from a tag data query page; then, based on the query tag corresponding to the data query information, determining whether a corresponding tag data index exists; and if so, displaying the tag-pre-data corresponding to the tag data index on the tag data query page. The tag-pre-data is used to produce user tags. Since the tag data index accurately indexes the tag-pre-data, obtaining the data query information on the tag data query page allows for the display of the tag-pre-data corresponding to the query tag after finding the tag data index. This achieves the goal of automatically displaying the tag-pre-data corresponding to the data query information through simple human-computer interaction in the tag production process, rather than requiring consultation with a data analyst to obtain the tag-pre-data for user tag production. Therefore, it overcomes the technical deficiency of excessive communication costs caused by relying solely on data analysts to query tag-pre-data during user tag production, thus improving the efficiency of user tag production. Attached Figure Description

[0016] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

[0017] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, for those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0018] Figure 1 This is a flowchart illustrating the first embodiment of the tag pre-data query method of this application;

[0019] Figure 2 This is a schematic diagram of the overall architecture of the tag-preceding data query method in this application;

[0020] Figure 3 This is a flowchart illustrating the second embodiment of the tag pre-data query method of this application;

[0021] Figure 4 This is a schematic diagram of an embodiment of the label pre-data query device of this application;

[0022] Figure 5 This is a schematic diagram of the device structure of the hardware operating environment involved in the tag-pre-data query method in this application embodiment.

[0023] The purpose, features, and advantages of this application will be further explained in conjunction with the embodiments and with reference to the accompanying drawings. Detailed Implementation

[0024] To make the above-mentioned objects, features, and advantages of the present invention more apparent and understandable, the technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0025] Example 1

[0026] First, it should be understood that a user profile is a tagged user model abstracted from information such as user attributes, preferences, lifestyle habits, and behaviors. Among these, user tags are the core element of a user profile, and their production process is receiving increasing attention. Currently, for most user profile systems, user tags are usually produced manually. However, if it is necessary to use or query the pre-existing data used to produce user tags, it can only be done by consulting data analysts. In other words, querying the pre-existing data for producing user tags has a certain threshold. Therefore, the user tag production process involves excessive communication costs, resulting in low efficiency in user tag production. Thus, there is an urgent need for a method to reduce the limitations of querying the pre-existing data for producing user tags.

[0027] This application provides a method for querying tag-pre-data. In the first embodiment of this application's tag-pre-data query method, refer to... Figure 1 The tag-based pre-data query method includes:

[0028] Step S10: Obtain data query information from the tag data query page;

[0029] Step S20: Determine whether a corresponding tag data index exists based on the query tags corresponding to the data query information;

[0030] In this embodiment, it should be noted that the tag pre-data query method is applied to a smart terminal, which can be a computer, personal PC, or mobile phone, etc. The tag pre-data is the pre-data for generating user tags, used to generate user tags. The user tags are the tag pre-data generated by the user in the user profiling system. After analysis and refinement, adjectives with differentiated characteristics are generated, which reflect the specific behaviors of the user in specific scenarios through the platform. The user profiling system refines all user behavior data into visualized information that supports business implementation, such as "individualistic," "laid-back," and "academic high achiever," etc. Since user tags have very high timeliness requirements, operators often use the pre-data for generating user tags when generating user tags, which requires frequent communication with data analysts. The essence of this solution is to transform the process of communicating and querying tag pre-data between people into a human-computer interaction process, thereby reducing the query threshold and improving the query efficiency, and thus improving the efficiency of user tag production.

[0031] Additionally, it should be noted that the tag-preceding data includes tag index data and tag detail data. The tag index data is used to characterize the tag-preceding data corresponding to the tag detail data, and the tag detail data is used to characterize the specific data required to generate user tags. Through the tag index data, the tag detail data under that data can be further obtained. Tag detail data indexed by the same tag index data has strong thematic relevance. For example, assuming that the angles for characterizing a user profile include "region," "age," and "gender," the tag detail data indexed by the same tag index data could be "the consumption patterns of men aged 18-22." The tag detail data contains information such as MAC address, UID (User Identification), and date. The tag-preceding data query method can be used in digital marketing and DMP (Data Management Platform). In practical application areas such as platform (data management platform) and advertising, the data query information is used to query tag-related data, specifically text data query information or voice data query information, etc. The tag data query page is a visual starting page for querying the tag-related data. The tag data query page is used to receive the data query information, specifically keywords entered by the user or keywords automatically obtained according to system tasks, etc. For example, in one feasible approach, assuming the practical application area is the smart TV OTT industry, there is tag-related data such as TV user parameters, user TV usage data, and TV viewing data. In this case, if the user profiling system has already generated a user tag of "annual VIP purchase count", the user can enter data query information on the tag data query page to query the tag-related data that generated the user tag. The data query information can specifically be keywords such as "purchase", "VIP", and "annual". There can be one or more keywords. When there are multiple keywords, the user can distinguish them using commas or spaces, or they can choose not to distinguish them.

[0032] Additionally, it should be noted that the query tag is used to define the data query information, specifically the information tag of the data query information. It can be one or more. For example, in one feasible implementation, assuming the data query information is "ABC", the query tag can be "d" which corresponds to "ABC", or it can be "a" which corresponds to "A" and "b" which corresponds to "BC". The tag data index is used to index the tag preceding data. When there is a tag data index corresponding to the tag preceding data, the corresponding tag preceding data can be queried.

[0033] As an example, steps S10 to S20 include: obtaining data query information input by the user on the tag data query page; matching the data query information with corresponding query tags according to preset tag matching rules, and detecting whether there is a tag data index corresponding to the query tag.

[0034] The step of determining whether a corresponding tag data index exists based on the query tag corresponding to the data query information includes:

[0035] Step A10: According to the preset word segmentation rules, the data query information is segmented into words to obtain data query word segments;

[0036] Step A20: Extract the query tags corresponding to the data query word segmentation;

[0037] Step A30: Based on the query tag, query the preset tag index mapping table to see if there is a corresponding data index table identifier;

[0038] Step A40: If yes, then it is determined that a tag data index corresponding to the query tag exists;

[0039] Step A50: If not, then it is determined that there is no tag data index corresponding to the query tag.

[0040] In this embodiment, it should be noted that since the data query information entered by the user may have multiple interpretations, the preset tag matching rules cannot accurately reflect the user's query intent. For example, in one feasible approach, assuming the data query information entered by the user on the tag data query page is "member status details", then the user may want to query "member status", "status details", or "member status details", etc. Therefore, after obtaining the query tags through preset word segmentation rules, the obtained query tags are matched, and the tag data indexes corresponding to the tag preceding data that may match the user's query intent are queried. The preset word segmentation rules can be obtained through a preset word segmenter. The preset word segmenter can be IKAnalyzer, Ansj, or Mmseg4j, etc. The preset tag index mapping table is used to store the mapping relationship between the query tags and the data index table identifier. The data index table identifier is the table index of the tag data index table and is used to identify the uniqueness of the tag data index table. Specifically, it can be identified by "mac". The tag data index table is used to store the tag detail data. The tag detail data stored in the tag data index table has an upper limit value, which is set by the operators. In one feasible implementation, the tag detail data in the tag data index table is 500 records.

[0041] Additionally, it should be noted that when storing tag detail data, in order to unify the table index of the data index table, the data index table will be uniformly formatted. That is, the table name, table description information (custom tags), and table field information (device ID, tag value, and date) will be defined. Thus, when the tag preceding data queried by the user is tag detail data, the field information corresponding to the tag detail data can be displayed.

[0042] As an example, steps A10 to A50 include: segmenting the data query information using a preset word segmenter to obtain the data query word segments; extracting tags from the data query word segments based on a preset tag extraction model to obtain the query tags, wherein the preset tag extraction model is a deep neural network model trained using sample data corresponding to the query tags; using the query tags as indexes, querying the preset tag index mapping table to see if a data index identifier corresponding to the query tags exists; if a data index identifier corresponding to the query tags exists in the preset tag index mapping table, then it is determined that a tag data index corresponding to the query tags exists; if it does not exist in the preset tag index mapping table, then it is determined that a tag data index corresponding to the query tags does not exist.

[0043] In one feasible approach, after a user constructs a data index table, they set corresponding query tags based on the data index table identifier corresponding to the tag data index table, and establish a preset tag index mapping table based on the correspondence between the data index table identifier and the query tags.

[0044] Prior to the step of displaying the tag preceding data corresponding to the tag data index based on the tag data query page, the tag preceding data query method further includes:

[0045] Step B10: Determine the corresponding tag data index table based on the data index table identifier;

[0046] Step B20: Determine the tag index data corresponding to the queried tag based on the index table name of the tag data index table;

[0047] Step B30: Obtain the tag detail data corresponding to the tag data index from the tag data index table;

[0048] Step B40: The tag index data and the tag detail data are used together as the tag pre-data.

[0049] In this embodiment, it should be noted that the tag data index table is a data source table that identifies the tag detail data. Through the tag data index table, tag index data and tag detail data related to the user's tags can be determined, that is, the tag pre-data is obtained. Therefore, in order for users to input data query information, the corresponding tag pre-data can be directly displayed on the tag data query page. The user profiling system needs to establish an overall architecture for the tag pre-data. In one feasible approach, refer to... Figure 2 , Figure 2 To illustrate the overall architecture of the tag-pre-data, the overall architecture includes a data display layer, a data query layer, a data index layer, and a raw data layer. The data display layer is used to visually display the tag-pre-data, specifically the tag index data and tag detail data. The data query layer is used to convert data query information into query tags, specifically by performing pre-indexing work on the tag-pre-data. The data index layer is used to index the tag-pre-data corresponding to the data query information through a tag data index table. The raw data layer is used to identify the source of the tag detail data. The tag index data is stored in other storage spaces outside the tag data index table.

[0050] As an example, steps B10 to B40 include: obtaining the tag data index table corresponding to the data index table identifier; querying the data index of the tag index data corresponding to the index table name in a preset table name index mapping table using the index table name of the tag data index table as an index, and then obtaining the tag index data corresponding to the data index of the tag index data, wherein the preset table name index mapping table is used to store the mapping relationship between the table name of the tag data index table and the data index of the tag index data. For example, in one implementable method, assuming the table name of the tag data index table is "dmp_db.auto_crowd_0000", and the data index of the tag data index corresponding to this table name is "0", then the tag index data can be indexed based on "0", wherein the number of tag index data corresponds to the number of tables in the tag data mapping table; obtaining the tag detail data corresponding to the tag data index in the tag data index table, wherein all tag detail data stored in the tag data index table are obtained; and using the tag index data and the tag detail data together as the tag pre-data.

[0051] The step of determining the corresponding tag data index table based on the data index table identifier includes:

[0052] Step C10: Detect the identifier type of the data index table identifier;

[0053] Step C20: If the data index table identifier is an attribute data index table identifier, then the tag data index table is determined to be a tag attribute data index table;

[0054] Step C30: If the data index table identifier is a behavior data index table identifier, then the tag data index table is determined to be a tag behavior data index table;

[0055] Step C40: If the data index table identifier is a warehouse data index table identifier, then the tag data index table is determined to be a tag warehouse data index table.

[0056] In this embodiment, it should be noted that, since the data sources of the tag detail data are different, specifically, they are divided into tag detail data from the data warehouse, tag detail data constructed by users based on user attributes, and tag detail data constructed by users based on user behavior. Therefore, the tag warehouse data index table is used to indicate that all tag detail data stored in the tag data index table originates from the data warehouse; the tag behavior data index table is used to indicate that all tag detail data stored in the tag data index table originates from user behavior data; and the tag attribute data index table is used to indicate that all tag detail data stored in the tag data index table originates from user attribute data. The user attribute data is data constructed based on user behavior for generating user tags, and the user behavior data is data constructed based on user attributes for generating user tags. For example, in one implementable method, when uniformly formatting the data index table, a "Type" is set to distinguish different types of tag data index tables. "1" corresponds to the tag attribute data index table, "2" corresponds to the tag behavior data index table, and "3" corresponds to the tag warehouse data index table. Each type of table can be set with a preset number of tables.

[0057] Step S30: If yes, then based on the tag data query page, display the tag pre-data corresponding to the tag data index, wherein the tag pre-data is used to generate user tags.

[0058] As an example, step S30 includes: displaying the tag index data and the corresponding tag detail data corresponding to the tag data index on the tag data query page, wherein the tag detail data corresponding to the tag index data is displayed sequentially. For example, in one implementable method, the tag index data includes "M", "N", and "F", wherein the tag detail data corresponding to "M" includes "m1" and "m2", the tag detail data corresponding to "N" includes "n", and the tag detail data corresponding to "F" includes "f1", "f2", and "f3", then "M", "m1", "m2", "N", "n", "F", "f1", "f2", and "f3" are displayed sequentially from top to bottom on the tag data query page.

[0059] Prior to the step of obtaining data query information on the tag data query page, the tag pre-data query method further includes:

[0060] Step D10: Obtain index configuration information from the index configuration page, and establish a tag data index table based on the index configuration information;

[0061] Step D20: Check whether the tag data index table has been successfully established;

[0062] Step D30: If the tag data index table is successfully established, then the tag data index corresponding to the tag data index table is established, and it is checked whether the tag data index is successfully established.

[0063] Step D40: If the tag data index is successfully established, the tag detail data is stored in the tag data index table according to the correspondence between the tag data index and the tag detail data.

[0064] In this embodiment, it should be noted that the index configuration page is a visual page for configuring the data index of the tag pre-data. The index configuration information is used to configure the data index of the tag pre-data. The index configuration information includes configuration information for configuring the table index of the tag data index table and configuration information for configuring the data index of the tag index data. The former specifically includes relevant information such as table name, table description, table fields, and table type, while the latter specifically includes data field information, data lineage information, theme information, and theme domain information. When the creation of the tag data index or any index in the tag data index table fails, a creation failure prompt message will be returned on the index configuration page to inform the user that the creation of the corresponding index has failed.

[0065] As an example, steps D10 to D40 include: obtaining index configuration information on the index configuration page, and establishing a tag data index table based on the index configuration information; detecting whether the tag data index table has been successfully established based on a first establishment prompt message; if the first establishment prompt message is not received, it is detected that the tag data index table has been successfully established, and then a tag data index corresponding to the tag data index table is established, and it is detected whether the tag data index has been successfully established based on a second establishment prompt message, wherein the first establishment prompt message is used to prompt the user that the establishment of the tag data index table failed, and the second establishment prompt message is used to prompt the user that the establishment of the data index corresponding to the tag index data failed, and the tag data index is a data index of the tag index data; if the second establishment prompt message is not received, the tag data index has been successfully established, and then the tag detail data is stored in the tag data index table according to the correspondence between the tag data index and the tag detail data.

[0066] The index configuration information includes first index configuration information and second index configuration information. The step of establishing a tag data index table based on the index configuration information includes:

[0067] Step E10: If the index configuration information is the first index configuration information, then establish the tag data index table based on the first index configuration information;

[0068] Step E20: If the index configuration information is the second index configuration information, then obtain the preset index table name;

[0069] Step E30: Based on the preset index table name and the second index configuration information, establish the tag data index table.

[0070] In this embodiment, it should be noted that, since the tag attribute data index table and the tag behavior data index table need to be created by the user when creating the tag data index table, the names of the tag attribute data index table and the tag behavior data index table are set by the user. However, when creating the tag warehouse data index table, it can be kept consistent with the database name and table name of the data warehouse, thereby improving the efficiency of creating the tag data index table. Therefore, the first index configuration information is used to characterize the index configuration information corresponding to the tag attribute data index table or the tag behavior data index table, and the second index configuration information is used to characterize the index configuration information corresponding to the tag warehouse data index table.

[0071] As an example, steps E10 to E30 include: if the index configuration information is the first index configuration information, then based on the first index configuration information input by the user, establishing the tag attribute data index table or the tag behavior data index table; if the index configuration information is the second index configuration information, then obtaining a preset index table name, wherein the preset index table name is used to represent the table name of the preset data warehouse; and based on the second index configuration information input by the user and the preset index table name, establishing the tag warehouse data index table.

[0072] This application provides a method for querying tag-pre-data. Specifically, it involves obtaining data query information from a tag data query page; then, based on the query tag corresponding to the data query information, determining whether a corresponding tag data index exists; and if so, displaying the tag-pre-data corresponding to the tag data index on the tag data query page. This tag-pre-data is used to generate user tags. Since the tag data index accurately indexes the tag-pre-data, obtaining the data query information on the tag data query page allows for the display of the tag-pre-data corresponding to the query tag after finding the corresponding tag data index. This achieves the goal of automatically displaying the tag-pre-data corresponding to the data query information through simple human-computer interaction in the tag production process, rather than requiring consultation with a data analyst to obtain the tag-pre-data for user tag production. Therefore, it overcomes the technical deficiency of excessive communication costs caused by relying solely on data analysts to query tag-pre-data during user tag production, thus improving the efficiency of user tag production.

[0073] Example 2

[0074] Furthermore, referring to Figure 3 In another embodiment of this application, content that is the same as or similar to that in Embodiment 1 described above can be referred to the above description and will not be repeated hereafter. Based on this, the step of controlling the target device to execute the interface operation corresponding to the interface operation content includes:

[0075] Step F10: Display the tag index data on the tag data query page, and detect whether there is a detailed data query instruction on the tag data query page;

[0076] If so, in step F20, the corresponding detailed data query page will pop up according to the detailed data query instruction.

[0077] Step F30: Display the tag detail data on the detail data query page.

[0078] In this embodiment, it should be noted that when both tag index data and tag detail data are displayed on the tag data query page, that is, all the tag-related data is displayed on the tag data query page, the tag-related data that users need to query may differ depending on their needs. For example, a user may only need to query the tag index data or may need to precisely query the tag detail data. If all the tag-related data is displayed on the tag data query page, it is not conducive to users performing precise queries, and due to the large amount of data, it will increase the difficulty of users' visual query work. Therefore, by setting the tag data query page to only query the tag index data, users can jump to the detail data query page by the table name of the tag data index table corresponding to the tag index data. The detail data query page is used to display a preset number of tag detail data stored in the tag data index table. Therefore, displaying the tag index data through the tag data query page and the tag detail data through the detail data query page can improve the user's query efficiency.

[0079] As an example, steps F10 to F30 include: displaying the tag index data on the tag data query page, and detecting whether a detailed data query instruction exists on the tag data query page, wherein the detailed data query instruction is specifically a detailed data query instruction controlled by the user via voice or key; if the detailed data query instruction is detected, a detailed data query page corresponding to the detailed data query instruction pops up, wherein, in one implementable manner, the detailed data query instruction can be triggered by clicking the index table name of the tag data index table corresponding to the tag index data; and displaying the tag detailed data on the detailed data query page.

[0080] This application provides a method for displaying tag-pre-query data. Specifically, it displays tag index data on the tag data query page and detects whether a detailed data query instruction exists on the tag data query page. If so, it pops up a corresponding detailed data query page based on the detailed data query instruction, and displays the tag detailed data on the detailed data query page. Compared to displaying all tag-pre-query data on the tag data query page, this application, based on the index relationship between tag index data and tag detailed data, displays tag index data and tag detailed data separately on different query pages. This achieves the goal of concisely and accurately displaying tag-pre-query data that meets the user's query needs, rather than displaying all tag-pre-query data on the same page for every query performed by the user. Therefore, it lays the foundation for improving the efficiency of user tag generation.

[0081] Example 3

[0082] This application also provides a tag-pre-data query device, referring to... Figure 4 The tag-based pre-data query device includes:

[0083] Module 101 is used to obtain data query information from the tag data query page;

[0084] The determining module 102 is used to determine whether a corresponding tag data index exists based on the query tag corresponding to the data query information;

[0085] The display module 103 is used to display the tag preceding data corresponding to the tag data index according to the tag data query page if the tag is true, wherein the tag preceding data is used to generate user tags.

[0086] Optionally, the determining module 102 is further configured to:

[0087] The data query information is segmented according to preset word segmentation rules to obtain data query word segments;

[0088] Extract the query tags corresponding to the word segmentation of the data;

[0089] Based on the query tag, check in the preset tag index mapping table whether there is a corresponding data index table identifier;

[0090] If so, then it is determined that a tag data index corresponding to the queried tag exists;

[0091] If not, then it is determined that there is no tag data index corresponding to the query tag.

[0092] Optionally, the tag-pre-data query device is further used for:

[0093] Based on the data index table identifier, determine the corresponding tag data index table;

[0094] Based on the index table name of the tag data index table, determine the tag index data corresponding to the queried tag;

[0095] Obtain the tag detail data corresponding to the tag data index from the tag data index table;

[0096] The tag index data and the tag detail data are used together as the tag pre-data.

[0097] Optionally, the tag-pre-data query device is further used for:

[0098] Detect the identifier type of the data index table identifier;

[0099] If the data index table identifier is an attribute data index table identifier, then the tag data index table is determined to be a tag attribute data index table;

[0100] If the data index table identifier is a behavior data index table identifier, then the tag data index table is determined to be a tag behavior data index table;

[0101] If the data index table identifier is the warehouse data index table identifier, then the tag data index table is determined to be the tag warehouse data index table.

[0102] Optionally, the display module 103 is further configured to:

[0103] The tag index data is displayed on the tag data query page, and the existence of a detailed data query instruction is detected on the tag data query page.

[0104] If so, the corresponding detailed data query page will pop up according to the detailed data query instruction;

[0105] The tag details data is displayed on the details data query page.

[0106] Optionally, the tag-pre-data query device is further used for:

[0107] Obtain index configuration information from the index configuration page, and create a tag data index table based on the index configuration information;

[0108] Check whether the tag data index table has been successfully created;

[0109] If the tag data index table is successfully established, then the tag data index corresponding to the tag data index table is established, and it is checked whether the tag data index is successfully established.

[0110] If the tag data index is successfully established, the tag detail data is stored in the tag data index table according to the correspondence between the tag data index and the tag detail data.

[0111] Optionally, the index configuration information includes first index configuration information and second index configuration information, and the tag-pre-data query device is further used for:

[0112] If the index configuration information is the first index configuration information, then the tag data index table is established based on the first index configuration information;

[0113] If the index configuration information is the second index configuration information, then obtain the preset index table name;

[0114] The tag data index table is established based on the preset index table name and the second index configuration information.

[0115] The tag-before-data query device provided by this invention, employing the tag-before-data query method in the above embodiments, solves the technical problem of low production efficiency of user tags. Compared with the prior art, the beneficial effects of the tag-before-data query device provided by this invention are the same as those of the tag-before-data query method provided in the above embodiments, and other technical features in this tag-before-data query device are the same as those disclosed in the methods of the above embodiments, and will not be repeated here.

[0116] Example 4

[0117] This invention provides an electronic device, which includes: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, which are executed by the at least one processor to enable the at least one processor to perform the tag-pre-data query method in Embodiment 1 above.

[0118] The following is for reference. Figure 5 The diagram illustrates a structural schematic of an electronic device suitable for implementing embodiments of the present disclosure. The electronic devices in the embodiments of the present disclosure may include, but are not limited to, mobile terminals such as mobile phones, laptops, digital broadcast receivers, PDAs (personal digital assistants), PADs (tablet computers), PMPs (portable multimedia players), in-vehicle terminals (e.g., in-vehicle navigation terminals), and fixed terminals such as digital TVs and desktop computers. Figure 5 The electronic device shown is merely an example and should not be construed as limiting the functionality and scope of the embodiments disclosed herein.

[0119] like Figure 5 As shown, the electronic device may include a processing unit 1001 (e.g., a central processing unit, a graphics processor, etc.) that can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 1002 or a program loaded from a storage device 1003 into a random access memory (RAM) 1004. The RAM 1004 also stores various programs and data required for the operation of the electronic device. The processing unit 1001, ROM 1002, and RAM 1004 are interconnected via a bus 1005. An input / output (I / O) interface 1006 is also connected to the bus.

[0120] Typically, the following systems can be connected to I / O interface 1006: input devices 1007 including, for example, touchscreens, touchpads, keyboards, mice, image sensors, microphones, accelerometers, gyroscopes, etc.; output devices 1008 including, for example, liquid crystal displays (LCDs), speakers, vibrators, etc.; storage devices 1003 including, for example, magnetic tapes, hard disks, etc.; and communication devices 1009. The communication devices allow electronic devices to communicate wirelessly or wiredly with other devices to exchange data. Although electronic devices with various systems are shown in the figures, it should be understood that it is not required to implement or possess all the systems shown. More or fewer systems may be implemented alternatively.

[0121] In particular, according to embodiments of this disclosure, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments of this disclosure include a computer program product comprising a computer program carried on a computer-readable medium, the computer program containing program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via communication device 1009, or installed from storage device 1003, or installed from ROM 1002. When the computer program is executed by processing device 1001, it performs the functions defined in the methods of embodiments of this disclosure.

[0122] The electronic device provided by this invention, employing the tag pre-data query method in the above embodiments, solves the technical problem of low production efficiency of user tags. Compared with the prior art, the beneficial effects of the electronic device provided by the embodiments of this invention are the same as those of the tag pre-data query method provided in the above embodiments, and other technical features of this electronic device are the same as those disclosed in the methods of the above embodiments, and will not be repeated here.

[0123] It should be understood that various parts of this disclosure can be implemented using hardware, software, firmware, or a combination thereof. In the description of the above embodiments, specific features, structures, materials, or characteristics may be combined in any suitable manner in one or more embodiments or examples.

[0124] The above description is merely a specific embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the technical scope disclosed in the present invention should be included within the scope of protection of the present invention. Therefore, the scope of protection of the present invention should be determined by the scope of the claims.

[0125] Example 5

[0126] This embodiment provides a computer-readable storage medium having computer-readable program instructions stored thereon, which are used to execute the tag-pre-data query method in the above embodiment.

[0127] The computer-readable storage medium provided in this embodiment of the invention may be, for example, a USB flash drive, but is not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device, or any combination thereof. More specific examples of a computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof. In this embodiment, the computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, system, or device. The program code contained on the computer-readable storage medium may be transmitted using any suitable medium, including but not limited to: wires, optical cables, RF (radio frequency), etc., or any suitable combination thereof.

[0128] The aforementioned computer-readable storage medium may be included in an electronic device or may exist independently without being assembled into an electronic device.

[0129] The aforementioned computer-readable storage medium carries one or more programs that, when executed by an electronic device, cause the electronic device to: determine whether a corresponding tag data index exists based on the query tag corresponding to the data query information; if so, display the tag pre-data corresponding to the tag data index based on the tag data query page, wherein the tag pre-data is used to generate user tags.

[0130] Computer program code for performing the operations of this disclosure can be written in one or more programming languages ​​or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, and C++, and conventional procedural programming languages ​​such as the "C" language or similar programming languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer can be connected to the user's computer via any type of network—including a local area network (LAN) or a wide area network (WAN)—or can be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0131] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of the present invention. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0132] The modules described in the embodiments of this disclosure can be implemented in software or hardware. The names of the modules do not necessarily limit the functionality of the unit itself.

[0133] The computer-readable storage medium provided by this invention stores computer-readable program instructions for executing the above-described tag pre-data query method, thus solving the technical problem of low production efficiency of user tags. Compared with the prior art, the beneficial effects of the computer-readable storage medium provided in the embodiments of this invention are the same as the beneficial effects of the tag pre-data query method provided in the above-described embodiments, and will not be repeated here.

[0134] Example 6

[0135] This application also provides a computer program product, including a computer program that, when executed by a processor, implements the steps of the tag-pre-data query method described above.

[0136] The computer program product provided in this application solves the technical problem of low production efficiency of user tags. Compared with the prior art, the beneficial effects of the computer program product provided in the embodiments of this invention are the same as the beneficial effects of the tag pre-data query method provided in the above embodiments, and will not be repeated here.

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

Claims

1. A method of querying label prep data, the method comprising: The label preposition data query method comprises the following steps: In the label data query page, data query information is obtained, wherein, before the step of obtaining the data query information in the label data query page, the label preposition data query method further comprises the following steps: In the index configuration page, index configuration information is obtained, and a label data index table is established according to the index configuration information, wherein the index configuration information comprises configuration information of a table index of the label data index table and configuration information of a data index of label index data, the configuration information of the table index comprises a table name, a table description, a table field and a table type, the configuration information of the data index comprises data field information, data blood relation information, theme information and theme domain information; whether the label data index table is successfully established is detected; if the label data index table is successfully established, a label data index corresponding to the label data index table is established, and whether the label data index is successfully established is detected; if the label data index is successfully established, the label detail data is stored into the label data index table according to the correspondence between the label data index and the label detail data, wherein the index configuration information comprises first index configuration information and second index configuration information, the first index configuration information is used to represent index configuration information corresponding to a label attribute data index table or a label behavior data index table, the second index configuration information is used to represent index configuration information corresponding to a label warehouse data index table, and the step of establishing the label data index table according to the index configuration information comprises the following steps: if the index configuration information is the first index configuration information, the label data index table is established according to the first index configuration information; if the index configuration information is the second index configuration information, a preset index table name is obtained; the label data index table is established according to the preset index table name and the second index configuration information; According to the query label corresponding to the data query information, it is determined whether there is corresponding label data index; If yes, the label preposition data corresponding to the label data index is displayed according to the label data query page, wherein the label preposition data is used to produce user labels.

2. The method of claim 1, wherein the tag pre-data query is a query for a tag pre-data of a tag. The step of determining whether there is corresponding label data index according to the query label corresponding to the data query information comprises the following steps: According to a preset word segmentation rule, the data query information is segmented to obtain data query words; The query label corresponding to the data query words is extracted; According to the query label, it is inquired whether there is a corresponding data index table identifier in a preset label index mapping table; If yes, it is determined that there is label data index corresponding to the query label; If no, it is determined that there is no label data index corresponding to the query label.

3. The method of claim 2, wherein the tag pre-data query is a query for a tag pre-data of a tag. Before the step of displaying the label preposition data corresponding to the label data index according to the label data query page, wherein the label preposition data is used to produce user labels, the label preposition data query method further comprises the following steps: According to the data index table identifier, the corresponding label data index table is determined. According to the index table name of the label data index table, determine the label index data corresponding to the query label; Obtain the label detail data corresponding to the label data index in the label data index table; The label index data and the label detail data are used as the label preposition data.

4. The tag-based pre-data query method as described in claim 3, characterized in that, The step of determining the corresponding label data index table according to the data index table identifier includes: Detect the identifier type of the data index table identifier; If the data index table identifier is an attribute data index table identifier, determine that the label data index table is a label attribute data index table; If the data index table identifier is a behavior data index table identifier, determine that the label data index table is a label behavior data index table; If the data index table identifier is a warehouse data index table identifier, determine that the label data index table is a label warehouse data index table.

5. The method of claim 1, wherein the tag pre-data query is a query for a tag pre-data of a tag. The label preposition data includes label index data and label detail data, The step of displaying the label preposition data corresponding to the label data index according to the label data query page includes: Display the label index data on the label data query page, and detect whether there is a detail data query instruction on the label data query page; If yes, according to the detail data query instruction, pop up the corresponding detail data query page; Display the label detail data on the detail data query page.

6. A label prep data query apparatus, characterized by, The label preposition data query device includes: An acquisition module is configured to acquire data query information on a label data query page, wherein, before the step of acquiring data query information on the label data query page, the label preposition data query method further includes: The index configuration information includes configuration information of table indexes of the label data index table and configuration information of data indexes of label index data, the configuration information of the table indexes includes table name, table description, table field and table type, and the configuration information of the data indexes includes data field information, data blood relation information, theme information and theme domain information; it is detected whether the label data index table is successfully established; if the label data index table is successfully established, label data indexes corresponding to the label data index table are established, and it is detected whether the label data indexes are successfully established; if the label data indexes are successfully established, the label detail data is stored into the label data index table according to a corresponding relationship between the label data indexes and the label detail data, wherein the index configuration information includes first index configuration information and second index configuration information, the first index configuration information is used to represent index configuration information corresponding to configuration of a label attribute data index table or a label behavior data index table, the second index configuration information is used to represent index configuration information corresponding to configuration of a label warehouse data index table, and the step of establishing the label data index table according to the index configuration information includes: if the index configuration information is the first index configuration information, the label data index table is established according to the first index configuration information; and if the index configuration information is the second index configuration information, a preset index table name is acquired; the label data index table is established according to the preset index table name and the second index configuration information; The determining module is configured to determine, according to the query label corresponding to the data query information, whether there is corresponding label data index; The display module is configured to, if yes, display label preposition data corresponding to the label data index according to the label data query page, wherein the label preposition data is used to produce a user label.

7. An electronic device, comprising: The electronic device comprises: at least one processor; and a memory connected with the at least one processor in communication; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to perform the steps of the label preposition data query method in any one of claims 1 to 5.

8. A computer-readable storage medium, characterized in that, The computer readable storage medium stores a program for implementing a label preposition data query method, and the program is executed by a processor to implement the steps of the label preposition data query method in any one of claims 1 to 5.

Images