Data processing method and device

Abstract

The invention discloses a data processing method and device. Label configuration information of a user is obtained, the label configuration information comprises a target data set and at least one piece of label rule information, an executable code is generated according to the label rule information, and the target data set is processed according to the executable code to obtain a label of the target data set. And generating label result set data according to the label of the target data set and sending the label result set data to the user terminal. Therefore, the operation difficulty of labeling can be reduced, and the efficiency and accuracy of labeling can be improved.

Description

Technical Field

[0001] This invention relates to the field of data processing technology, and in particular to a data processing method and apparatus. Background Technology

[0002] With the rapid development of data processing technology, data tagging, as an important part of data processing, is of great significance for improving the accuracy and efficiency of data processing.

[0003] In existing technologies, data tagging is mainly done manually or through automation. Manual tagging is inefficient and requires significant time and manpower. While automated tagging can improve efficiency to some extent, changes in tagging requirements necessitate manual updates to data processing scripts or program code, involving a series of modifications and tests—a process that is not only time-consuming but also prone to errors. Summary of the Invention

[0004] In view of this, the purpose of this invention is to provide a data processing method and apparatus that can reduce the difficulty of tagging operations and improve the efficiency and accuracy of tagging.

[0005] In a first aspect, embodiments of the present invention provide a data processing method, the method comprising:

[0006] Obtain the user's tag configuration information, which includes the target dataset and at least one tag rule information;

[0007] Executable code is generated based on the label rule information;

[0008] The target dataset is processed according to the executable code to obtain the labels of the target dataset;

[0009] A label result set data is generated based on the labels of the target dataset and sent to the user terminal. The label result set data includes the labels corresponding to each target dataset.

[0010] In some embodiments, the tag rule information includes one or more tag rule groups, each tag rule group including condition field information and output field information. The condition field information includes one or more of the following: condition field name, condition field description, condition function, and condition content. The condition function is the relationship between the condition field name and / or the condition field description and the condition content. The output field information includes tags.

[0011] In some embodiments, the label rule information includes text information.

[0012] In some embodiments, generating executable code based on the tag rule information includes:

[0013] Semantic information is obtained from the text information using a pre-trained language model;

[0014] Based on the logical structure of the predetermined tag rules, one or more tag rule groups are generated according to the semantic information. Each tag rule group includes condition field information and output field information. The condition field information includes one or more of the following: condition field name, condition field description, condition function, and condition content. The condition function is the relationship between the condition field name and / or the condition field description and the condition content. The output field information includes tags.

[0015] The executable code is generated based on the tag rule group.

[0016] In some embodiments, the label configuration information further includes a strategy type, which includes a first strategy and a second strategy;

[0017] Wherein, in response to the strategy type being the first strategy, the tag configuration information further includes the priority number corresponding to each tag rule group; in response to the strategy type being the second strategy, the tag configuration information includes the priority number corresponding to each tag rule group, or the tag configuration information does not include the priority number corresponding to each tag rule group.

[0018] In some embodiments, processing the target dataset according to the executable code to obtain the labels of the target dataset includes:

[0019] In response to the strategy type being the first strategy, the target dataset is processed sequentially according to the priority number corresponding to each label rule group until the labels of the target dataset are obtained.

[0020] In some embodiments, processing the target dataset according to the executable code to obtain the labels of the target dataset includes:

[0021] In response to the strategy type being the second strategy, each of the label rule groups is processed on the target dataset to obtain the labels of the target dataset.

[0022] In some embodiments, the label configuration information may also include fallback selection information.

[0023] In some embodiments, processing the target dataset according to the executable code to obtain the labels of the target dataset includes:

[0024] In response to the fallback selection information being fallback, and when the target dataset's label is not obtained through the executable code, the label is determined to be a predefined label;

[0025] When the fallback selection information is "no fallback" and the target dataset is not obtained through the executable code, the label is determined to be empty.

[0026] Secondly, embodiments of the present invention provide a data processing method, the method comprising:

[0027] The label configuration information input by the user is obtained through the label configuration interface. The label configuration information includes the target dataset and at least one label rule information.

[0028] Send the tag configuration information to the server;

[0029] The system receives label result set data sent by the server, which includes labels corresponding to each target dataset.

[0030] In some embodiments, obtaining the tag configuration information input by the user through the tag configuration interface includes:

[0031] The first configuration interface is displayed, which includes an input dataset acquisition area, an input data item acquisition area, and an output field acquisition area.

[0032] The target dataset input by the user is obtained through the input dataset acquisition region;

[0033] Based on the target dataset, determine the corresponding candidate data items;

[0034] The input data item selected by the user is obtained through the input data item acquisition area, wherein the input data item is at least one candidate data item selected by the user;

[0035] The candidate output fields input by the user are obtained through the output field acquisition area.

[0036] In some embodiments, the first configuration interface further includes a fallback selection area;

[0037] The step of obtaining the tag configuration information input by the user through the tag configuration interface further includes:

[0038] The user's input of the fallback selection information is obtained through the fallback selection area.

[0039] In some embodiments, the first configuration interface further includes a label strategy selection area;

[0040] The step of obtaining the tag configuration information input by the user through the tag configuration interface further includes:

[0041] The user-selected strategy type is obtained through the label strategy selection area, and the strategy type includes a first strategy and a second strategy.

[0042] In some embodiments, the first configuration interface further includes an interface layout selection area;

[0043] The step of obtaining the tag configuration information input by the user through the tag configuration interface further includes:

[0044] The user-selected interface layout is obtained through the interface layout selection area. The interface layout includes a simplified version and a smart version.

[0045] In some embodiments, obtaining the tag configuration information input by the user through the tag configuration interface further includes:

[0046] The first confirmation information, including the interface layout, is received by the user through the first configuration interface.

[0047] In response to the simplified interface layout, the user will be redirected to the second configuration interface.

[0048] In response to the interface layout being set to the smart version, the user is redirected to the third configuration interface.

[0049] In some embodiments, the first confirmation information further includes input data items and candidate output fields;

[0050] The step of obtaining the tag configuration information input by the user through the tag configuration interface further includes:

[0051] The second configuration interface is displayed, which includes a condition field information input area and an output field information input area.

[0052] The condition field information input area is used to obtain the condition field information input by the user. The condition field information includes one or more of the following: condition field name, condition field description, condition function, and condition content. The condition field name and / or condition field description are the input data items selected by the user. The condition function is the relationship between the condition field name and / or condition field description selected by the user and the condition content.

[0053] The output field information input by the user is obtained through the output field information input area. The output field information includes labels, which are candidate output fields selected by the user.

[0054] In some embodiments, obtaining the tag configuration information input by the user through the tag configuration interface further includes:

[0055] A third configuration interface is displayed, which includes a text information input area;

[0056] The text information input by the user is obtained through the text information input area.

[0057] In some embodiments, the second configuration interface or the third configuration interface further includes a priority number input area;

[0058] The step of obtaining the tag configuration information input by the user through the tag configuration interface further includes:

[0059] Obtain the priority number entered by the user through the priority number input area.

[0060] In some embodiments, the method further includes:

[0061] Receive preview information sent by the server;

[0062] The preview information will display the various tag rule groups.

[0063] Thirdly, embodiments of the present invention provide a data processing apparatus, the apparatus comprising:

[0064] A configuration information acquisition unit is used to acquire the user's tag configuration information, wherein the tag configuration information includes a target dataset and at least one tag rule information;

[0065] A code generation unit is used to generate executable code based on the tag rule information;

[0066] A tag acquisition unit is used to process the target dataset according to the executable code to obtain the tags of the target dataset;

[0067] The data sending unit is used to generate a tag result set data based on the tags of the target dataset and send it to the user terminal. The tag result set data includes the tags corresponding to each target dataset.

[0068] Fourthly, embodiments of the present invention provide a data processing apparatus, the apparatus comprising:

[0069] The configuration information input unit is used to obtain the label configuration information input by the user through the label configuration interface. The label configuration information includes the target dataset and at least one label rule information.

[0070] A configuration information sending unit is used to send the tag configuration information to the server;

[0071] The data receiving unit is used to receive the label result set data sent by the server, wherein the label result set data includes the labels corresponding to each target dataset.

[0072] Fifthly, embodiments of the present invention provide an electronic device, including a memory and a processor, wherein the memory is used to store one or more computer program instructions, wherein the one or more computer program instructions are executed by the processor to implement the methods as described in the first and second aspects.

[0073] Sixthly, embodiments of the present invention provide a computer program product comprising a computer program, wherein when the computer program is run on a computer, the computer performs the methods described in the first and second aspects above.

[0074] In a seventh aspect, embodiments of the present invention provide a computer-readable storage medium having stored thereon computer program instructions that, when executed by a processor, implement the methods described in the first and second aspects.

[0075] The technical solution of this invention obtains the user's tag configuration information, including a target dataset and at least one tag rule information. Executable code is generated based on the tag rule information. The executable code processes the target dataset to obtain its tags. A tag result set is generated based on the tags in the target dataset and sent to the user's terminal. This reduces the difficulty of tagging and improves its efficiency and accuracy. Attached Figure Description

[0076] The above and other objects, features and advantages of the present invention will become clearer from the following description of embodiments of the invention with reference to the accompanying drawings, in which:

[0077] Figure 1 This is a schematic diagram of a data processing system according to an embodiment of the present invention;

[0078] Figure 2 This is a flowchart of data interaction according to an embodiment of the present invention;

[0079] Figure 3 This is a schematic diagram of the first configuration interface according to an embodiment of the present invention;

[0080] Figure 4 This is a schematic diagram of the first configuration interface according to another embodiment of the present invention;

[0081] Figure 5 This is a schematic diagram of the second configuration interface according to an embodiment of the present invention;

[0082] Figure 6 This is a schematic diagram of the third configuration interface according to an embodiment of the present invention;

[0083] Figure 7 This is a flowchart illustrating the generation of executable code according to an embodiment of the present invention;

[0084] Figure 8 This is a schematic diagram of a preview interface of an embodiment of the present invention;

[0085] Figure 9 This is a schematic diagram of a data processing system according to another embodiment of the present invention;

[0086] Figure 10 This is a flowchart of a server data processing method according to an embodiment of the present invention;

[0087] Figure 11 This is a flowchart of a data processing method for a user terminal according to an embodiment of the present invention;

[0088] Figure 12 This is a schematic diagram of a server data processing device according to an embodiment of the present invention;

[0089] Figure 13 This is a schematic diagram of a data processing device for a user terminal according to an embodiment of the present invention;

[0090] Figure 14 This is a schematic diagram of an electronic device according to an embodiment of the present invention. Detailed Implementation

[0091] The present invention is described below based on embodiments, but the invention is not limited to these embodiments. In the detailed description of the invention below, certain specific details are described in detail. Those skilled in the art will fully understand the invention even without these details. To avoid obscuring the essence of the invention, well-known methods, processes, flows, elements, and circuits are not described in detail.

[0092] Furthermore, those skilled in the art should understand that the accompanying drawings provided herein are for illustrative purposes only and are not necessarily drawn to scale.

[0093] Unless the context explicitly requires it, words such as "including" or "contains" throughout the application documents should be interpreted as including rather than exclusive or exhaustive; that is, meaning "including but not limited to".

[0094] In the description of this invention, it should be understood that the terms "first," "second," etc., are used for descriptive purposes only and should not be construed as indicating or implying relative importance. Furthermore, in the description of this invention, unless otherwise stated, "a plurality of" means two or more.

[0095] Figure 1 This is a schematic diagram of a data processing system according to an embodiment of the present invention. Figure 1As shown, the data processing system of this embodiment includes a server 1, a user terminal 2, and a database 3. The server 1 and user terminal 2 are connected by a communication connection, and the server 1 and database 3 are also connected by a communication connection.

[0096] User terminal 2 is the terminal device used by the user, which can be a laptop, desktop computer, tablet computer, mobile phone or other terminal device with data processing function.

[0097] Server 1 can be a single server or a server cluster consisting of multiple servers.

[0098] Database 3 is used to store data. The target dataset described in this embodiment of the invention is the data stored in the database.

[0099] In this embodiment, when a user needs to tag data in database 3, they access the service program provided by server 1 through various software programs, apps, web pages, mini-programs, etc. on their user terminal. Through this service program, they enter the tag configuration interface, input tag configuration information, and send it to server 1. After receiving the tag configuration information, server 1 generates a tag result set based on the tag configuration information and sends it to user terminal 2 for display.

[0100] In this context, labels refer to descriptive tags or classifications assigned to data items during data processing, machine learning, and data analysis. These labels are typically used to identify data characteristics (e.g., in sentiment analysis, comment text might be labeled "positive," "neutral," or "negative"), categories (e.g., emails might be labeled "spam" or "normal"), or states (e.g., valid data and invalid data).

[0101] This invention, in its embodiments, acquires a user's tag configuration information, including a target dataset and at least one tag rule. Based on the tag rule information, executable code is generated. This executable code processes the target dataset to obtain its tags. Finally, a tag result set is generated based on the tags and sent to the user's terminal. This reduces the complexity of tagging operations and improves the efficiency and accuracy of tagging.

[0102] Figure 2 This is a flowchart of data interaction in an embodiment of the present invention. Figure 2 The data interaction between server 1 and user terminal 2 is illustrated, specifically including the following steps:

[0103] Step S101: Display the first configuration interface.

[0104] In this embodiment, the user terminal displays a first configuration interface. Specifically, when a user needs to tag data, they can access the service program provided by server 1 through various software programs, apps, web pages, mini-programs, etc., and after completing registration and login, they can access the first configuration interface.

[0105] Step S102: Obtain the target dataset.

[0106] Step S103: Obtain the input data items.

[0107] Step S104: Obtain candidate output fields.

[0108] Step S105: Obtain fallback selection information.

[0109] Step S106: Obtain the strategy type.

[0110] Step S107: Obtain the interface layout.

[0111] For steps S101-S107 above, this embodiment of the invention configures the tagging environment based on a first configuration interface. The tagging environment includes information such as the target dataset, input data items, candidate output fields, fallback selection information, strategy type, and interface layout.

[0112] Specifically, Figure 3 This is a schematic diagram of the first configuration interface according to an embodiment of the present invention. Figure 3 As shown, the first configuration interface includes input dataset acquisition area A1, fallback selection area A2, input data item acquisition area A3, output field acquisition area A4, label strategy selection area A5, and interface layout selection area A6.

[0113] The input dataset acquisition area A1 is used to acquire the target dataset input by the user. Specifically, the input dataset acquisition area A1 includes a label identifier input box, a label name input box, and a label data source table input box. The label identifier and label name input boxes are used to input the label identifier and label name for this task, for subsequent viewing, modification, and other operations. The data source table input box is used to acquire the target dataset input by the user; this embodiment of the invention uses data from a table in a database as an example for illustration. Figure 3 As shown, the data source table input box includes two parts: the first part is for entering the database name, and the second part is for the user to enter the table name. That is, the target dataset in this embodiment of the invention includes both the database name and the table name. It should be noted that the target dataset in this embodiment of the invention refers to the dataset used for labeling. This data refers to the raw data before processing and labeling, typically existing in text, two-dimensional tables, or other forms.

[0114] The fallback selection area A2 is used to obtain the fallback selection information input by the user. When the data does not conform to the labeling rules, if no fallback is provided, the output label will be empty; if a fallback is provided, the output label will be the predefined label. Therefore, the user can choose whether to provide a fallback option based on their actual needs.

[0115] The input data item acquisition area A3 is used to acquire the input data items selected by the user. Input data items refer to the data items used for labeling; these are the raw data before processing and labeling, typically existing as a field in a two-dimensional table or other forms. Specifically, after the user inputs the target dataset, the user terminal sends the target dataset to the server. The server retrieves the metadata information from the target dataset and obtains candidate data items for the user to select, i.e., which fields will generate labels. The server sends the obtained candidate data items to the user terminal. The user can select one or more candidate data items through the input box in the input data item acquisition area A3; these selected candidate data items are the input data items in this embodiment of the invention. Metadata describes data and can provide information and context for other data, making it easier for users to understand, organize, and manage data. Metadata can include various information about the data, such as its source, format, content, structure, creation time, modification time, author, usage restrictions, etc. Further, the input data item includes a condition field name and a condition field description, where the condition field name is the field of the metadata selected by the user, and the condition field description is the user's description of the metadata.

[0116] The output field acquisition area A4 is used to acquire one or more candidate output fields input by the user. Candidate output fields include the label information that the user needs to output. Specifically, each candidate output field includes an output field name and an output field description. The output field name is the field input by the user, and the output field description is the user's description of the output field name.

[0117] The tag strategy selection area A5 is used to obtain the strategy type selected by the user. The strategy types include a first strategy and a second strategy. The first strategy is "stop when found," meaning that if the user has configured multiple tag rule groups, each tag rule group is executed sequentially. If a tag is obtained through a certain tag rule group, subsequent tag rule groups are not executed. In other words, the final tag obtained actually corresponds to only one tag rule group. The second strategy is "find until no more can be found," meaning that if the user has configured multiple tag rule groups, each tag rule group needs to be executed. The final tag obtained includes tags corresponding to all tag rule groups that meet the conditions.

[0118] The interface layout selection area A6 is used to obtain the interface layout selected by the user, which includes a simplified version and a smart version. Since different users have different capabilities, this embodiment of the invention provides two interface layouts for different users, corresponding to the second configuration interface and the third configuration interface described below.

[0119] Figure 4 This is a schematic diagram of the first configuration interface of another embodiment of the present invention. Figure 3 The first configuration interface shown is the interface when no information is entered. Figure 4 The first configuration interface shown is the interface after inputting information. For example... Figure 4 As shown, in the input dataset acquisition area A1, the label identifier is tag_xx, the label name is xx label, and the label data source table is (datax, tablex), where datax is the database name and tablex is the table name.

[0120] In the fallback selection area A2, selecting "Yes" means that the fallback option has been selected.

[0121] In the input data item acquisition area A3, four input data items were selected. The condition field names for the four input data items are source_name, category_name, account_name, and description, respectively, with corresponding descriptions of source, category, adjustment name, and summary. Each input data item also has a corresponding delete control, allowing users to delete that item. Furthermore, the input data item acquisition area A3 also includes add controls, such as "Add Condition Field," to allow users to add more input data items.

[0122] In the output field acquisition area A4, two candidate output fields were entered. The output field names for the two candidate output fields are `entertain_type` and `supplier_type`, and their corresponding output field descriptions are "Entertainment Category" and "Supply Category," respectively. Each candidate output field also has a corresponding delete control, allowing users to delete that candidate output field. Furthermore, the output field acquisition area A4 also includes an add control, such as "Add Output Field," to allow users to add more candidate output fields.

[0123] In the label strategy selection area A5, the first strategy, namely "stop when found", was selected.

[0124] In the interface layout selection area A6, I selected the minimalist version.

[0125] Therefore, the tagging environment can be configured based on the first configuration interface. The tagging environment includes information such as the target dataset, input data items, candidate output fields, fallback selection information, strategy type, and interface layout.

[0126] Step S108: Display the second configuration interface.

[0127] In this embodiment, after configuring through the first configuration interface, clicking "Next" will cause the user terminal to receive the first confirmation information input by the user. The first confirmation information includes information such as the target dataset, input data items, candidate output fields, fallback selection information, strategy type, and interface layout.

[0128] If the interface layout is the simplified version, proceed to the second configuration interface and go to steps S108-S109. If the interface layout is the smart version, proceed to the third configuration interface and go to steps S110-S111.

[0129] Step S109: Obtain condition field information and output field information.

[0130] For steps S108-S109, Figure 5 This is a schematic diagram of the second configuration interface according to an embodiment of the present invention. For example... Figure 5 As shown, the second configuration interface includes a condition field information input area B1, an output field information input area B2, and a priority number input area B3.

[0131] The condition field information input area B1 acquires the condition field information input by the user, which includes the selection field, condition function, and condition content. The selection field input box is used to select the condition field name and / or condition field description. Figure 5 This example illustrates how to display both the description and name of a condition field simultaneously, with the condition field name displayed in parentheses after the description. The input box for a selected field allows users to choose information from... Figure 4 The input data item acquisition area A3 retrieves the condition field name and / or condition field description corresponding to the configured input data item. The condition field name and / or condition field description are the input data items selected by the user. The condition function represents the relationship between the user-selected condition field name and / or condition field description and the condition content, such as equal to, containing, etc.

[0132] exist Figure 5 In the input area B1, there are three condition fields. Each condition field includes a selection field, a condition function, and a condition content. The meanings of the three condition fields can be interpreted as follows:

[0133] The source (source_name) is the X1 system;

[0134] Change the name (account_name) to X2 service;

[0135] The description includes X3 Company.

[0136] By default, the logical relationship between the three condition fields is "AND", meaning that if a piece of data meets all three condition fields, then the condition is true.

[0137] In some embodiments, the logical relationship between multiple condition field information can be set by the user, and the specific implementation method will not be described in detail in this embodiment of the invention.

[0138] In addition, each condition field has a corresponding delete control, which allows you to delete the corresponding condition field. Furthermore, the condition field input area B1 also includes add controls, such as "Add Condition Field," which allows you to add more condition fields.

[0139] The output field information input area B2 is used to obtain output field information input by the user. The output field information includes labels, which are candidate output fields selected by the user. Specifically, the "Select Field" input box in the output field information input area B2 is used to select the output field name and / or output field description. Figure 5 The example shown below illustrates how to display both output field names. The "Select Field" input box allows you to choose the output field name from... Figure 4 The output field name is obtained from the candidate output fields configured in area A4.

[0140] exist Figure 5 In the output field information input area B2, there are two output field information, each of which includes a selection field and an output result. The output result is the label in this embodiment of the invention. The two output field information can be interpreted as follows:

[0141] entertain_type outputs Y1;

[0142] The supplier_type output is Y2.

[0143] In addition, each output field has a corresponding delete control, which allows you to delete the corresponding output field. Furthermore, the output field input area B2 also includes add controls, such as "Add Condition Field," which allows you to add more output field information.

[0144] Therefore, a tag rule group can be generated using the aforementioned condition field information and output field information. The tag rule group includes condition field information and output field information. The condition field information includes one or more of the following: condition field name, condition field description, condition function, and condition content. The condition function is the relationship between the condition field name and / or condition field description and the condition content. The output field information includes tags.

[0145] Figure 5 The tag rule group of the illustrated embodiment can be interpreted as follows: if the source of the data (source_name) is system X1, the adjusted name (account_name) is business X2, and the description contains company X3, then entertain_type outputs Y1, and supplier_type outputs Y2.

[0146] The priority number input area B3 is used to obtain the priority number entered by the user. The priority number determines the execution order of multiple tag rule groups. Furthermore, if the strategy type is the first strategy, the priority number input area B3 is required; if the strategy type is the second strategy, the priority number input area B3 is optional.

[0147] In some embodiments, the second configuration interface also includes a tag rule group adding control, such as... Figure 5 When the "Add Next Group" option is triggered, the interface for adding the next tag rule group will appear, allowing you to add multiple tag rule groups.

[0148] In some embodiments, the second configuration interface also includes a completion control, such as... Figure 5 When the "Complete" button is triggered, proceed to step S112.

[0149] Step S110: Display the third configuration interface.

[0150] In this embodiment, after configuring through the first configuration interface, clicking "Next" will cause the user terminal to receive the first confirmation information input by the user. The first confirmation information includes information such as the target dataset, input data items, candidate output fields, fallback selection information, strategy type, and interface layout.

[0151] If the interface layout is set to the smart version, then proceed to the third configuration interface and enter steps S110-S111.

[0152] Step S111: Obtain text information.

[0153] In this embodiment, the text information input by the user is obtained through a third configuration interface.

[0154] Specifically, Figure 6 This is a schematic diagram of the third configuration interface according to an embodiment of the present invention. For example... Figure 6 As shown, the third configuration interface of this embodiment of the invention includes a text information input area C1 and a priority number input area C2.

[0155] The text input area C1 is used to obtain text information input by the user. The text information is a description of the tag rules, for example, "Users with 300 orders per year are key users". In this tag rule, the condition is "300 orders per year" and the tag is "key user".

[0156] The priority number input area C2 is used to obtain the priority number entered by the user. The priority number determines the execution order of multiple tag rule groups. Furthermore, if the strategy type is the first strategy, the priority number input area C2 is required; if the strategy type is the second strategy, the priority number input area C2 is optional.

[0157] In some embodiments, the third configuration interface also includes a tag rule group adding control, such as... Figure 6 When the "Add Next Group" option is triggered, the interface for adding the next tag rule group will appear, allowing you to add multiple tag rule groups.

[0158] In some embodiments, the third configuration interface also includes a completion control, such as Figure 6 When the "Complete" button is triggered, proceed to step S112.

[0159] Step S112: Generate tag configuration information.

[0160] In this embodiment, the user terminal generates tag configuration information based on the information input through the configuration interface. The tag configuration information includes the target dataset and at least one tag rule information.

[0161] The target dataset consists of the database name and table name entered by the user through the first configuration interface.

[0162] In one optional implementation, the tag rule information includes one or more tag rule groups, each of which includes condition field information and output field information input through the second configuration interface. The condition field information includes one or more of the following: condition field name, condition field description, condition function, and condition content. The condition function is the relationship between the condition field name and / or the condition field description and the condition content. The output field information includes tags.

[0163] In another alternative implementation, the label rule information includes text information input through a third configuration interface.

[0164] In some embodiments, the label configuration information further includes a policy type, which includes a first policy and a second policy.

[0165] In some embodiments, the label configuration information may also include fallback selection information.

[0166] Step S113: Send tag configuration information.

[0167] In this embodiment, the user terminal sends tag configuration information to the server.

[0168] Step S114: Generate executable code.

[0169] In this embodiment, the server generates executable code based on the tag rule information.

[0170] In some embodiments, the executable code is SQL (Structured Query Language). SQL is a database language with multiple functions such as data manipulation and data definition. This language has interactive features and can provide great convenience to users. Database management systems should make full use of SQL to improve the working quality and efficiency of computer application systems.

[0171] In one optional implementation, the tag rule information includes one or more tag rule groups. Each tag rule group includes condition field information and output field information input through the second configuration interface. The condition field information includes one or more of the following: condition field name, condition field description, condition function, and condition content. The condition function is the relationship between the condition field name and / or condition field description and the condition content. The output field information includes tags. In other words, the tag rule information conforms to a predetermined template format, and the conditions, fields, and logic are directly obtainable. The server selects an appropriate SQL statement type, such as SELECT, INSERT, UPDATE, DELETE, etc., and fills the relevant information into the corresponding positions of the SQL statement, thereby automatically generating executable code.

[0172] In another optional implementation, the tag rule information includes text information input through a third configuration interface. For text information, the process for generating executable code is as follows: Figure 7 As shown, it includes the following steps:

[0173] Step S1141: Obtain semantic information based on the text information using a pre-trained language model.

[0174] In this embodiment, the text information does not conform to the predetermined template format and its meaning is abstract. Therefore, the server obtains semantic information based on the text information through a pre-trained language model.

[0175] The pre-trained language model can be implemented using the BERT (Bidirectional Encoder Representations from Transformers) model. BERT acquires text information, segments the text information into individual words, and based on the word vectors of these words, the BERT model can better understand the semantics and structure of the input text information.

[0176] Step S1142: Based on the logical structure of the predetermined tag rules, generate one or more tag rule groups according to the semantic information.

[0177] In this embodiment, semantic information corresponding to the text information is output based on a pre-trained language model. A set of tag rules with a logical structure conforming to predetermined tag rules is generated based on this semantic information. More specifically, query requirements are obtained based on the semantic information, and all query conditions, such as equal to, not equal to, greater than, less than, and contain relationships, are extracted from these requirements. Field names in the query conditions are mapped to actual column names in the database, and these conditions are organized according to logical relationships (such as AND and OR) to form a set of tag rules.

[0178] Each of the tag rule groups includes condition field information and output field information. The condition field information includes one or more of the following: condition field name, condition field description, condition function, and condition content. The condition function is the relationship between the condition field name and / or the condition field description and the condition content. The output field information includes tags.

[0179] Step S1143: Generate the executable code according to the tag rule group.

[0180] In this embodiment, an appropriate SQL statement type, such as SELECT, INSERT, UPDATE, DELETE, etc., is selected according to the query requirements, and the parsed and abstracted query conditions are filled into the corresponding positions of the SQL statement, thereby automatically generating executable code.

[0181] Step S115: Obtain the labels of the target dataset.

[0182] In this embodiment, the server processes the target dataset according to the executable code to obtain the label of the target dataset.

[0183] Specifically, the server passes the executable code to Spark (a big data processing engine) for execution to obtain the labels of the target dataset. Spark is a fast, general-purpose, and scalable memory-based big data analytics engine that can execute SQL queries. Spark supports data querying and analysis using SQL, allowing SQL queries to be run directly on Spark, similar to traditional relational databases, and is suitable for tasks such as data analysis and report generation.

[0184] In some embodiments, the label configuration information further includes fallback selection information. When the fallback selection information is fallback and no labels for the target dataset are obtained through the executable code, the label is determined to be a predetermined label. When the fallback selection information is no fallback and no labels for the target dataset are obtained through the executable code, the label is determined to be empty.

[0185] Step S116: Generate the label result set data.

[0186] In this embodiment, the server generates a label result set data based on the labels of the target dataset and sends it to the user terminal. The label result set data includes the labels corresponding to each target dataset.

[0187] For example, suppose the target dataset is an evaluation table containing multiple evaluation entries. If a user wants to analyze and obtain evaluation information related to "service speed issues" and "price issues," then after configuring the tag information, the server processes each of the multiple evaluation entries in the evaluation table to obtain the tags for each evaluation entry regarding "service speed issues" and "price issues."

[0188] Step S117: Send the tag result set data.

[0189] In this embodiment, the server sends the tag result set data to the user terminal.

[0190] Step S118: Display the label result set data.

[0191] In this embodiment, the user terminal displays the tag result set data.

[0192] In some embodiments, users can also preview and modify the configured tag configuration information.

[0193] Specifically, after the user enters relevant information through the second or third configuration interface, clicking the "Complete" control will take them to the preview interface. Alternatively, a "Preview" control can be set on the user terminal's display interface; triggering the "Preview" control will take them to the preview interface. The "Preview" control can be placed in various locations on different interfaces; this embodiment of the invention does not impose any restrictions on this. The user terminal receives preview information sent by the server and displays various tag rule groups based on the preview information.

[0194] Figure 8 This is a schematic diagram of a preview interface of an embodiment of the present invention. For example... Figure 8 As shown, the preview interface of this embodiment of the invention includes a table header and a tag rule group. The table header includes a priority number, a condition field, an output field, and an operation. The condition field includes the condition field name, condition field description, condition function, and condition content; the output field includes the output field name, output field description, and output result. If a "find until it can't be found" strategy is adopted, the priority number can be omitted.

[0195] Figure 8 The preview interface includes five tag rule groups, which correspond to priority numbers 1-5 respectively. The content with priority number 1 is shown in detail.

[0196] In addition, each tag rule group has corresponding operation controls, including "Edit" and "Copy" controls. Clicking "Edit" allows you to modify the tag rule group, and clicking "Copy" allows you to copy the tag rule group.

[0197] The system of this invention allows business personnel to directly define and update data labeling rules, reducing the workload of R&D personnel and improving response speed and efficiency. Through the combination of a rule engine and a feedback mechanism, it achieves efficient, flexible, and scalable data processing, providing strong support for the rapid development of data processing.

[0198] Furthermore, tiered subscription services can be offered based on different user groups. Basic services might only include basic tagging functionality, while more advanced services can include more features such as advanced analytics, automated report generation, and seamless integration with other systems. This tiered strategy can meet diverse needs.

[0199] In terms of security, embodiments of the present invention embed coloring information in the data labeling result data to perform system security detection through the coloring information.

[0200] Figure 9 This is a schematic diagram of a data processing system according to another embodiment of the present invention. Figure 9The data processing system shown is a software or hardware module that implements the above data processing method, specifically including a user interface L1, a system application layer L2, a basic service layer L3, a basic component layer L4, a metadata interaction layer L5, and a security and authentication management layer L6.

[0201] The user interface L1 is the front-end, primarily used for data input and selection, tag configuration, tag strategy selection, and ultimately for previewing and optimizing the tag result set. Users interact directly with the system through this interface.

[0202] The system application layer (L2) is responsible for core business logic processing, including a rule parsing module and a natural language processing module. The rule parsing module performs semantic parsing of the rules and generates dynamic SQL. The natural language processing module is responsible for entity recognition (such as word segmentation and text classification) and also generates dynamic SQL. Finally, the rule execution module is responsible for executing these rules, including OLAP (Online Analytical Processing) and OLTP (Online Transaction Processing) operations.

[0203] The basic service layer (L3) provides support services for system operation, including front-end services, storage services, messaging services, data services, and data type selection. This layer ensures that all modules of the system can reliably and efficiently perform data storage, communication, and operations, supporting upper-layer business logic processing and user interaction.

[0204] The foundational component layer L4 consists of key technology components, including RDS (Relational Database Service), Doris (Distributed Analytical Database), Spark (Big Data Processing Engine), and a scheduling system. This layer provides the underlying technical support for the system's core functions, ensuring efficient execution of data processing, analysis, and task scheduling.

[0205] The metadata exchange layer L5 is responsible for managing and coordinating the exchange of metadata between various modules in the system. It ensures that each module can obtain the necessary metadata information during data selection, rule configuration, and execution to support precise data processing and analysis operations.

[0206] The Security and Authentication Management Layer (L6) is responsible for ensuring system security and legitimate user access rights. It includes user authentication, access control, data encryption, and other security measures to prevent unauthorized access and data breaches, thus ensuring overall system security.

[0207] This invention, in its embodiments, acquires a user's tag configuration information, including a target dataset and at least one tag rule. Based on the tag rule information, executable code is generated. This executable code processes the target dataset to obtain its tags. Finally, a tag result set is generated based on the tags and sent to the user's terminal. This reduces the complexity of tagging operations and improves the efficiency and accuracy of tagging.

[0208] Figure 10 This is a flowchart of a server data processing method according to an embodiment of the present invention. Figure 10 As shown, the data processing method of this embodiment of the invention includes the following steps:

[0209] Step S210: Obtain the user's tag configuration information, which includes the target dataset and at least one tag rule information.

[0210] Step S220: Generate executable code based on the tag rule information.

[0211] Step S230: Process the target dataset according to the executable code to obtain the label of the target dataset.

[0212] Step S240: Generate a label result set data based on the labels of the target dataset and send it to the user terminal. The label result set data includes the labels corresponding to each target dataset.

[0213] In some embodiments, the tag rule information includes one or more tag rule groups, each tag rule group including condition field information and output field information. The condition field information includes one or more of the following: condition field name, condition field description, condition function, and condition content. The condition function is the relationship between the condition field name and / or the condition field description and the condition content. The output field information includes tags.

[0214] In some embodiments, the label rule information includes text information.

[0215] In some embodiments, generating executable code based on the tag rule information includes:

[0216] Semantic information is obtained from the text information using a pre-trained language model;

[0217] Based on the logical structure of the predetermined tag rules, one or more tag rule groups are generated according to the semantic information. Each tag rule group includes condition field information and output field information. The condition field information includes one or more of the following: condition field name, condition field description, condition function, and condition content. The condition function is the relationship between the condition field name and / or the condition field description and the condition content. The output field information includes tags.

[0218] The executable code is generated based on the tag rule group.

[0219] In some embodiments, the label configuration information further includes a strategy type, which includes a first strategy and a second strategy;

[0220] Wherein, in response to the strategy type being the first strategy, the tag configuration information further includes the priority number corresponding to each tag rule group; in response to the strategy type being the second strategy, the tag configuration information includes the priority number corresponding to each tag rule group, or the tag configuration information does not include the priority number corresponding to each tag rule group.

[0221] In some embodiments, processing the target dataset according to the executable code to obtain the labels of the target dataset includes:

[0222] In response to the strategy type being the first strategy, the target dataset is processed sequentially according to the priority number corresponding to each label rule group until the labels of the target dataset are obtained.

[0223] In some embodiments, processing the target dataset according to the executable code to obtain the labels of the target dataset includes:

[0224] In response to the strategy type being the second strategy, each of the label rule groups is processed on the target dataset to obtain the labels of the target dataset.

[0225] In some embodiments, the label configuration information may also include fallback selection information.

[0226] In some embodiments, processing the target dataset according to the executable code to obtain the labels of the target dataset includes:

[0227] In response to the fallback selection information being fallback, and when the target dataset's label is not obtained through the executable code, the label is determined to be a predefined label;

[0228] When the fallback selection information is "no fallback" and the target dataset is not obtained through the executable code, the label is determined to be empty.

[0229] This invention, in its embodiments, acquires a user's tag configuration information, including a target dataset and at least one tag rule. Based on the tag rule information, executable code is generated. This executable code processes the target dataset to obtain its tags. Finally, a tag result set is generated based on the tags and sent to the user's terminal. This reduces the complexity of tagging operations and improves the efficiency and accuracy of tagging.

[0230] Figure 11 This is a flowchart of a data processing method for a user terminal according to an embodiment of the present invention. Figure 11 As shown, the data processing method of this embodiment of the invention includes the following steps:

[0231] Step S310: Obtain the tag configuration information input by the user through the tag configuration interface. The tag configuration information includes the target dataset and at least one tag rule information.

[0232] Step S320: Send the tag configuration information to the server.

[0233] Step S330: Receive the label result set data sent by the server, wherein the label result set data includes the labels corresponding to each target dataset.

[0234] In some embodiments, obtaining the tag configuration information input by the user through the tag configuration interface includes:

[0235] The first configuration interface is displayed, which includes an input dataset acquisition area, an input data item acquisition area, and an output field acquisition area.

[0236] The target dataset input by the user is obtained through the input dataset acquisition region;

[0237] Based on the target dataset, determine the corresponding candidate data items;

[0238] The input data item selected by the user is obtained through the input data item acquisition area, wherein the input data item is at least one candidate data item selected by the user;

[0239] The candidate output fields input by the user are obtained through the output field acquisition area.

[0240] In some embodiments, the first configuration interface further includes a fallback selection area;

[0241] The step of obtaining the tag configuration information input by the user through the tag configuration interface further includes:

[0242] The user's input of the fallback selection information is obtained through the fallback selection area.

[0243] In some embodiments, the first configuration interface further includes a label strategy selection area;

[0244] The step of obtaining the tag configuration information input by the user through the tag configuration interface further includes:

[0245] The user-selected strategy type is obtained through the label strategy selection area, and the strategy type includes a first strategy and a second strategy.

[0246] In some embodiments, the first configuration interface further includes an interface layout selection area;

[0247] The step of obtaining the tag configuration information input by the user through the tag configuration interface further includes:

[0248] The user-selected interface layout is obtained through the interface layout selection area. The interface layout includes a simplified version and a smart version.

[0249] In some embodiments, obtaining the tag configuration information input by the user through the tag configuration interface further includes:

[0250] The first confirmation information, including the interface layout, is received by the user through the first configuration interface.

[0251] In response to the simplified interface layout, the user will be redirected to the second configuration interface.

[0252] In response to the interface layout being set to the smart version, the user is redirected to the third configuration interface.

[0253] In some embodiments, the first confirmation information further includes input data items and candidate output fields;

[0254] The step of obtaining the tag configuration information input by the user through the tag configuration interface further includes:

[0255] The second configuration interface is displayed, which includes a condition field information input area and an output field information input area.

[0256] The condition field information input area is used to obtain the condition field information input by the user. The condition field information includes one or more of the following: condition field name, condition field description, condition function, and condition content. The condition field name and / or condition field description are the input data items selected by the user. The condition function is the relationship between the condition field name and / or condition field description selected by the user and the condition content.

[0257] The output field information input by the user is obtained through the output field information input area. The output field information includes labels, which are candidate output fields selected by the user.

[0258] In some embodiments, obtaining the tag configuration information input by the user through the tag configuration interface further includes:

[0259] A third configuration interface is displayed, which includes a text information input area;

[0260] The text information input by the user is obtained through the text information input area.

[0261] In some embodiments, the second configuration interface or the third configuration interface further includes a priority number input area;

[0262] The step of obtaining the tag configuration information input by the user through the tag configuration interface further includes:

[0263] Obtain the priority number entered by the user through the priority number input area.

[0264] In some embodiments, the method further includes:

[0265] Receive preview information sent by the server;

[0266] The preview information will display the various tag rule groups.

[0267] This invention, in its embodiments, acquires a user's tag configuration information, including a target dataset and at least one tag rule. Based on the tag rule information, executable code is generated. This executable code processes the target dataset to obtain its tags. Finally, a tag result set is generated based on the tags and sent to the user's terminal. This reduces the complexity of tagging operations and improves the efficiency and accuracy of tagging.

[0268] Figure 12 This is a schematic diagram of a server data processing device according to an embodiment of the present invention. Figure 12As shown, the data processing apparatus of this embodiment includes a configuration information acquisition unit 121, a code generation unit 122, a tag acquisition unit 123, and a data sending unit 124. The configuration information acquisition unit 121 acquires the user's tag configuration information, which includes a target dataset and at least one tag rule. The code generation unit 122 generates executable code based on the tag rule information. The tag acquisition unit 123 processes the target dataset according to the executable code to obtain tags for the target dataset. The data sending unit 124 generates tag result set data based on the tags of the target dataset and sends it to the user terminal; the tag result set data includes tags corresponding to each target dataset.

[0269] In some embodiments, the tag rule information includes one or more tag rule groups, each tag rule group including condition field information and output field information. The condition field information includes one or more of the following: condition field name, condition field description, condition function, and condition content. The condition function is the relationship between the condition field name and / or the condition field description and the condition content. The output field information includes tags.

[0270] In some embodiments, the label rule information includes text information.

[0271] In some embodiments, the code generation unit includes:

[0272] The semantic information acquisition subunit is used to acquire semantic information based on the text information through a pre-trained language model.

[0273] A tag rule group generation subunit is used to generate one or more tag rule groups based on the semantic information according to the logical structure of the predetermined tag rules. Each tag rule group includes condition field information and output field information. The condition field information includes one or more of the following: condition field name, condition field description, condition function, and condition content. The condition function is the relationship between the condition field name and / or the condition field description and the condition content. The output field information includes tags.

[0274] The code generation subunit is used to generate the executable code according to the tag rule group.

[0275] In some embodiments, the label configuration information further includes a strategy type, which includes a first strategy and a second strategy;

[0276] Wherein, in response to the strategy type being the first strategy, the tag configuration information further includes the priority number corresponding to each tag rule group; in response to the strategy type being the second strategy, the tag configuration information includes the priority number corresponding to each tag rule group, or the tag configuration information does not include the priority number corresponding to each tag rule group.

[0277] In some embodiments, the tag acquisition unit is used for:

[0278] In response to the strategy type being the first strategy, the target dataset is processed sequentially according to the priority number corresponding to each label rule group until the labels of the target dataset are obtained.

[0279] In some embodiments, the tag acquisition unit is used for:

[0280] In response to the strategy type being the second strategy, each of the label rule groups is processed on the target dataset to obtain the labels of the target dataset.

[0281] In some embodiments, the label configuration information may also include fallback selection information.

[0282] In some embodiments, the tag acquisition unit is used for:

[0283] In response to the fallback selection information being fallback, and when the target dataset's label is not obtained through the executable code, the label is determined to be a predefined label;

[0284] When the fallback selection information is "no fallback" and the target dataset is not obtained through the executable code, the label is determined to be empty.

[0285] This invention, in its embodiments, acquires a user's tag configuration information, including a target dataset and at least one tag rule. Based on the tag rule information, executable code is generated. This executable code processes the target dataset to obtain its tags. Finally, a tag result set is generated based on the tags and sent to the user's terminal. This reduces the complexity of tagging operations and improves the efficiency and accuracy of tagging.

[0286] Figure 13 This is a schematic diagram of a data processing device for a user terminal according to an embodiment of the present invention. Figure 13As shown, the data processing device of this embodiment includes a configuration information input unit 131, a configuration information sending unit 132, and a data receiving unit 133. The configuration information input unit 131 is used to obtain tag configuration information input by a user through a tag configuration interface. The tag configuration information includes target datasets and at least one tag rule. The configuration information sending unit 132 is used to send the tag configuration information to a server. The data receiving unit 133 is used to receive tag result set data sent by the server. The tag result set data includes tags corresponding to each target dataset.

[0287] In some embodiments, the configuration information input unit is used for:

[0288] The first configuration interface is displayed, which includes an input dataset acquisition area, an input data item acquisition area, and an output field acquisition area.

[0289] The target dataset input by the user is obtained through the input dataset acquisition region;

[0290] Based on the target dataset, determine the corresponding candidate data items;

[0291] The input data item selected by the user is obtained through the input data item acquisition area, wherein the input data item is at least one candidate data item selected by the user;

[0292] The candidate output fields input by the user are obtained through the output field acquisition area.

[0293] In some embodiments, the first configuration interface further includes a fallback selection area;

[0294] The configuration information input unit is further used for:

[0295] The user's input of the fallback selection information is obtained through the fallback selection area.

[0296] In some embodiments, the first configuration interface further includes a label strategy selection area;

[0297] The configuration information input unit is further used for:

[0298] The user-selected strategy type is obtained through the label strategy selection area, and the strategy type includes a first strategy and a second strategy.

[0299] In some embodiments, the first configuration interface further includes an interface layout selection area;

[0300] The configuration information input unit is further used for:

[0301] The user-selected interface layout is obtained through the interface layout selection area. The interface layout includes a simplified version and a smart version.

[0302] In some embodiments, the configuration information input unit is further configured to:

[0303] The first confirmation information, including the interface layout, is received by the user through the first configuration interface.

[0304] In response to the simplified interface layout, the user will be redirected to the second configuration interface.

[0305] In response to the interface layout being set to the smart version, the user is redirected to the third configuration interface.

[0306] In some embodiments, the first confirmation information further includes input data items and candidate output fields;

[0307] The configuration information input unit is further used for:

[0308] The second configuration interface is displayed, which includes a condition field information input area and an output field information input area.

[0309] The condition field information input area is used to obtain the condition field information input by the user. The condition field information includes one or more of the following: condition field name, condition field description, condition function, and condition content. The condition field name and / or condition field description are the input data items selected by the user. The condition function is the relationship between the condition field name and / or condition field description selected by the user and the condition content.

[0310] The output field information input by the user is obtained through the output field information input area. The output field information includes labels, which are candidate output fields selected by the user.

[0311] In some embodiments, the configuration information input unit is further configured to:

[0312] A third configuration interface is displayed, which includes a text information input area;

[0313] The text information input by the user is obtained through the text information input area.

[0314] In some embodiments, the second configuration interface or the third configuration interface further includes a priority number input area;

[0315] The configuration information input unit is further used for:

[0316] Obtain the priority number entered by the user through the priority number input area.

[0317] In some embodiments, the apparatus further includes:

[0318] A preview information receiving unit is used to receive preview information sent by the server;

[0319] The preview information display unit is used to display each tag rule group based on the preview information.

[0320] This invention, in its embodiments, acquires a user's tag configuration information, including a target dataset and at least one tag rule. Based on the tag rule information, executable code is generated. This executable code processes the target dataset to obtain its tags. Finally, a tag result set is generated based on the tags and sent to the user's terminal. This reduces the complexity of tagging operations and improves the efficiency and accuracy of tagging.

[0321] Figure 14 This is a schematic diagram of an electronic device according to an embodiment of the present invention. Figure 14 The illustrated electronic device is a general-purpose data processing device, comprising a general-purpose computer hardware architecture, including at least a processor 141 and a memory 142. The processor 141 and memory 142 are connected via a bus 143. The memory 142 is adapted to store instructions or programs executable by the processor 141. The processor 141 can be a standalone microprocessor or a collection of one or more microprocessors. Thus, the processor 141 executes the instructions stored in the memory 142, thereby performing the method flow of the embodiments of the present invention as described above to process data and control other devices. The bus 143 connects the aforementioned components together, and also connects these components to a display controller 144, a display device, and an input / output (I / O) device 145. The input / output (I / O) device 145 can be a mouse, keyboard, modem, network interface, touch input device, motion-sensing input device, printer, and other devices known in the art. Typically, the input / output device 145 is connected to the system via an input / output (I / O) controller 146.

[0322] Those skilled in the art will understand that embodiments of the present invention can be provided as methods, apparatus (devices), or computer program products. Therefore, the present invention can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present invention can be implemented as a computer program product on one or more computer-readable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0323] This invention is described with reference to flowchart illustrations of methods, apparatus (devices), and computer program products according to embodiments of this application. It should be understood that each step in the flowchart can be implemented by computer program instructions.

[0324] These computer program instructions may be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including an instruction means, the implementation process of which is described in the instruction means. Figure 1 The function specified in one or more processes.

[0325] These computer program instructions may also be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing device to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing device, produce instructions for implementing processes. Figure 1 A device for a function specified in one or more processes.

[0326] The solutions described in this specification and embodiments, if involving the processing of personal information, will be processed only under the premise of having a legal basis (such as obtaining the consent of the personal information subject, or being necessary for the performance of a contract), and will only be processed within the scope stipulated or agreed upon. A user's refusal to process personal information beyond what is necessary for basic functions will not affect the user's use of basic functions.

[0327] The above description is merely a preferred embodiment of the present invention and is not intended to limit the invention. For those skilled in the art, the present invention can be modified and varied in various ways. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principle of the present invention should be included within the scope of protection of the present invention.

Claims

1. A data processing method, characterized by, The method comprises: acquiring label configuration information of a user, the label configuration information comprising a target data set and at least one label rule information; generating executable code according to the label rule information; processing the target data set according to the executable code to obtain a label of the target data set; generating a label result set data according to the label of the target data set and sending the label result set data to a user terminal, the label result set data comprising a label corresponding to each target data set.

2. The method of claim 1, wherein, The label rule information comprises one or more label rule groups, each label rule group comprising condition field information and output field information, the condition field information comprising one or more of a condition field name, a condition field description, a condition function, and a condition content, the condition function being a relationship between the condition field name and / or the condition field description and the condition content, and the output field information comprising a label.

3. The method of claim 1, wherein, The label rule information comprises text information.

4. The method of claim 3, wherein, The generation of the executable code according to the label rule information comprises: acquiring semantic information from the text information by using a pre-trained language model; generating one or more label rule groups according to the semantic information based on a predetermined logical structure of a label rule, each label rule group comprising condition field information and output field information, the condition field information comprising one or more of a condition field name, a condition field description, a condition function, and a condition content, the condition function being a relationship between the condition field name and / or the condition field description and the condition content, and the output field information comprising a label; generating the executable code according to the label rule groups.

5. The method according to claim 2 or 4, characterized in that, The label configuration information further comprises a policy type, the policy type comprising a first policy and a second policy; wherein, in response to the policy type being the first policy, the label configuration information further comprises a priority sequence number corresponding to each label rule group; and in response to the policy type being the second policy, the label configuration information comprises a priority sequence number corresponding to each label rule group, or the label configuration information does not comprise a priority sequence number corresponding to each label rule group.

6. The method of claim 5, wherein, The processing of the target data set according to the executable code to obtain a label of the target data set comprises: in response to the policy type being the first policy, processing the target data set in sequence according to the priority sequence number corresponding to each label rule group until the label of the target data set is obtained.

7. The method of claim 5, wherein, The processing of the target data set according to the executable code to obtain a label of the target data set comprises: in response to the policy type being the second policy, processing the target data set by each label rule group to obtain the label of the target data set.

8. The method of claim 1, wherein, The label configuration information further comprises a bottom-up selection information.

9. The method of claim 8, wherein, The processing of the target data set according to the executable code to obtain a label of the target data set comprises: in response to the bottom-up selection information being bottom-up and the label of the target data set not being obtained by using the executable code, determining the label to be a predetermined label. In response to the bottom selection information being not bottomed and the label of the target data set not being acquired through the executable code, it is determined that the label is empty.

10. A data processing method, characterized by, The method comprises: acquiring label configuration information input by a user through a label configuration interface, the label configuration information comprising a target data set and at least one label rule information; sending the label configuration information to a server; receiving label result set data sent by the server, the label result set data comprising labels corresponding to respective target data sets.

11. The method of claim 10, wherein, The label configuration information input by the user through the label configuration interface comprises: displaying a first configuration interface, the first configuration interface comprising an input data set acquisition area, an input data item acquisition area and an output field acquisition area; acquiring a target data set input by a user through the input data set acquisition area; determining a corresponding candidate data item according to the target data set; acquiring an input data item selected by a user through the input data item acquisition area, the input data item being at least one candidate data item selected by the user; acquiring a candidate output field input by a user through the output field acquisition area.

12. The method of claim 11, wherein, The first configuration interface further comprises a bottom selection area; wherein the label configuration information input by the user through the label configuration interface further comprises: acquiring bottom selection information input by a user through the bottom selection area.

13. The method of claim 11, wherein, The first configuration interface further comprises a label strategy selection area; wherein the label configuration information input by the user through the label configuration interface further comprises: acquiring a strategy type selected by a user through the label strategy selection area, the strategy type comprising a first strategy and a second strategy.

14. The method of claim 11, wherein, The first configuration interface further comprises an interface version selection area; wherein the label configuration information input by the user through the label configuration interface further comprises: acquiring an interface version selected by a user through the interface version selection area, the interface version comprising a simple version and a smart version.

15. The method of claim 11, wherein, The label configuration information input by the user through the label configuration interface further comprises: receiving first confirmation information input by a user through the first configuration interface, the first confirmation information comprising an interface version; in response to the interface version being the simple version, jumping to a second configuration interface; in response to the interface version being the smart version, jumping to a third configuration interface.

16. The method of claim 15, wherein, The first confirmation information further comprises an input data item and a candidate output field; wherein the label configuration information input by the user through the label configuration interface further comprises: displaying a second configuration interface, the second configuration interface comprising a condition field information input area and an output field information input area; acquiring condition field information input by a user through the condition field information input area, the condition field information comprising one or more of a condition field name, a condition field description, a condition function and a condition content, the condition field name and / or the condition field description being the input data item selected by the user, the condition function being a relationship between the condition field name and / or the condition field description and the condition content selected by the user; The output field information input area obtains the output field information input by the user, and the output field information includes a label selected by the user as a candidate output field.

17. The method of claim 15, wherein, The label configuration information input by the user through the label configuration interface further includes: The third configuration interface includes a text information input area. The text information input area obtains the text information input by the user.

18. The method of claim 15, wherein, The second configuration interface or the third configuration interface further includes a priority number input area. The label configuration information input by the user through the label configuration interface further includes: The priority number input area obtains the priority number input by the user.

19. The method of claim 16, wherein, The method further includes: Receiving the preview information sent by the server; According to the preview information, each label rule group is displayed.

20. A data processing apparatus, characterized in that, The device includes: A configuration information obtaining unit is configured to obtain label configuration information of a user, and the label configuration information includes a target data set and at least one label rule information; A code generating unit is configured to generate executable code according to the label rule information; A label obtaining unit is configured to process the target data set according to the executable code to obtain labels of the target data set; A data sending unit is configured to generate label result set data according to the labels of the target data set and send the label result set data to a user terminal, and the label result set data includes labels corresponding to each target data set.

21. A data processing apparatus, characterized in that, The device includes: A configuration information input unit is configured to obtain label configuration information input by a user through a label configuration interface, and the label configuration information includes a target data set and at least one label rule information; A configuration information sending unit is configured to send the label configuration information to a server; A data receiving unit is configured to receive label result set data sent by the server, and the label result set data includes labels corresponding to each target data set.

22. An electronic device comprising a memory and a processor, wherein the processor is configured to: The memory is configured to store one or more computer program instructions, and the one or more computer program instructions are executed by the processor to implement the method in any one of claims 1-19.

23. A computer program product comprising a computer program, characterized in that, When the computer program runs on the computer, the computer executes the method in any one of claims 1-19.

24. A computer readable storage medium having stored thereon computer program instructions, wherein, The computer program instructions, when executed by the processor, implement the method in any one of claims 1-19. The computer program instructions, when executed by the processor, implement the method in any one of claims 1-19.

Images