CN111984882A

CN111984882A - Data processing method, system and equipment

Info

Publication number: CN111984882A
Application number: CN201910431087.0A
Authority: CN
Inventors: 李孟杰; 陈金玉
Original assignee: Alibaba Group Holding Ltd
Current assignee: Alibaba Group Holding Ltd
Priority date: 2019-05-22
Filing date: 2019-05-22
Publication date: 2020-11-24

Abstract

The embodiment of the application provides a data processing method, a system and equipment. The method comprises the following steps: in response to an event of using a model creation scheme triggered by a user, determining a target model to be used in the creation scheme; acquiring configuration information; and generating a label processing scheme according to the target model and the configuration information. According to the technical scheme provided by the embodiment of the application, a user can use the existing model to complete the creation of the label processing scheme on the premise of not knowing the bottom label processing logic, and the whole process is simple, convenient and efficient.

Description

Data processing method, system and equipment

Technical Field

The present application relates to the field of computer technologies, and in particular, to a data processing method, system, and device.

Background

In the big data era, the market competition environment, marketing strategies and service modes of the traditional internet industry are changed while the data show sea quantification, diversification and value change. How to acquire and screen out valuable information from mass data is a great challenge for internet enterprises. The tag construction is performed on the mass data, and the mass data is displayed in the form of tags, so that the method is an effective solution for solving the above challenges.

In some cases, the constructed label cannot meet the use requirement, and the existing label needs to be processed again. For example, time-interval statistics is carried out on the transaction time tag of a certain commodity; thus, business personnel can make marketing plans and the like based on statistical results. At present, the requirement of label reprocessing on the technical capability of service personnel is high, and the label reprocessing not only needs to have certain code compiling capability, but also needs to pay attention to the service; in addition, the conventional label reprocessing process is inefficient.

Disclosure of Invention

Embodiments of the present application provide a data processing method, system, and device that can solve or partially solve the problems in the prior art.

In one embodiment of the present application, a data processing method is provided. The method comprises the following steps:

in response to an event of using a model creation scheme triggered by a user, determining a target model to be used in the creation scheme;

acquiring configuration information;

and generating a label processing scheme according to the target model and the configuration information.

In another embodiment of the present application, a data processing method is provided. The method comprises the following steps:

generating an executable program according to the label processing scheme; wherein the tag handling scheme is generated based on a model and configuration information;

Scheduling the executable program to process the label to obtain a corresponding processing result;

and adding the processing result to an output table corresponding to the label processing scheme.

In yet another embodiment of the present application, a data processing method is provided. The method comprises the following steps:

responding to a model creating event triggered by a user, and acquiring creating information and attribute information generated in the model creating event;

and generating a model for creating a label processing scheme based on the creation information and the attribute information.

In yet another embodiment of the present application, a data processing system is also provided. The system comprises:

the system comprises a first client, a second client and a third client, wherein the first client is used for responding to an event of using a model creation scheme triggered by a user and determining a target model to be used in the creation scheme; acquiring configuration information; generating a label processing scheme according to the target model and the configuration information; sending the label processing scheme to a server;

the server is used for generating an executable program according to the label processing scheme; scheduling the executable program to process the label to obtain a processing result; and adding the processing result to an output table corresponding to the label processing scheme.

the second client is used for responding to a model creating event triggered by a user and acquiring creating information and attribute information generated in the model creating event; generating a model for creating a label processing scheme according to the creation information and the attribute information;

and the server is used for storing the model generated by the second client so as to send the target model specified by the request to the calling party when a calling request exists.

In another embodiment of the present application, a data processing method is also provided. The method comprises the following steps:

responding to a selection event triggered by a user aiming at least one model, and displaying a configuration page corresponding to a target model selected from the selection event;

responding to a configuration event triggered by a user on the configuration page, and displaying configuration information generated in the configuration event;

and responding to a submission event triggered by a user on the configuration page, and displaying response information after a submission operation is performed on a tag processing scheme generated based on the target model and the configuration information.

Responding to a creation event triggered by a user on a model creation interface, and displaying creation information and attribute information;

and responding to a confirmation event triggered by a user, and displaying a page element corresponding to the model generated based on the creation information and the attribute information in a model management page.

In yet another embodiment of the present application, a client device is also provided. The client device includes a memory and a processor, wherein,

the memory is used for storing programs;

the processor, coupled with the memory, to execute the program stored in the memory to:

acquiring configuration information;

In yet another embodiment of the present application, a processing device is also provided. The processing device includes a memory and a processor, wherein,

the memory is used for storing programs;

According to the technical scheme, the user can complete the creation of the label processing scheme on the premise of not knowing the underlying physical label processing logic by using the existing model, the whole process is simple, convenient and efficient, and the efficiency of subsequent label processing is improved.

According to the technical scheme provided by the other embodiment of the application, after the label processing scheme constructed by using the model is submitted, the executable program can be generated according to the label processing scheme; then the executable program is scheduled to realize the processing of the label, and the label processing efficiency is high.

In the technical solution provided by another embodiment of the present application, a model for creating a tag processing scheme is generated based on the creation information and the attribute information; the label processing scheme can be created conveniently by using the created model, so that the creation process of the label processing scheme is simpler and more efficient, and the efficiency of subsequent label processing is improved.

Drawings

In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly described below, and it is obvious that the drawings in the following description are some embodiments of the present application, and other drawings can be obtained by those skilled in the art without creative efforts.

Fig. 1 is a schematic flow chart of a data processing method according to an embodiment of the present application;

FIG. 2 illustrates an exemplary diagram of a selection model window;

FIG. 3 is a diagram illustrating a specific example of a configuration interface;

fig. 4 is a schematic flowchart of a data processing method according to another embodiment of the present application;

fig. 5 is a schematic flowchart of a data processing method according to another embodiment of the present application;

FIG. 6 is a diagram illustrating a specific example of a model creation interface;

FIG. 7 is a block diagram of a data processing system according to an embodiment of the present application;

FIG. 8 is a schematic diagram illustrating a process flow of model creation according to an embodiment of the present application;

FIG. 9 is a schematic diagram illustrating a process for creating a tag processing scheme according to an embodiment of the present application;

FIG. 10 is a schematic diagram illustrating a process for submitting a tag processing scheme according to an embodiment of the present application;

fig. 11 is a schematic flowchart of a data processing method according to another embodiment of the present application;

FIG. 12 is a diagram illustrating a specific example of a model management page;

fig. 13 is a schematic flowchart of a data processing method according to another embodiment of the present application;

fig. 14 is a schematic structural diagram of a data processing apparatus according to an embodiment of the present application;

fig. 15 is a schematic structural diagram of a data processing apparatus according to another embodiment of the present application;

Fig. 16 is a schematic structural diagram of a data processing apparatus according to yet another embodiment of the present application;

fig. 17 is a schematic structural diagram of a client device according to an embodiment of the present application.

Detailed Description

Before describing the technical solutions provided in the embodiments of the present application, the terms referred to herein will be briefly described.

Labeling: is a characteristic attribute of an entity or relationship, which can be either a description of the entity or relationship or a metric attribute of the entity or relationship. The entities or the relationship among the entities are characterized through the labels, and the characteristics of the entities are reflected from multiple angles. For example, when the commodity is carved, the angles include the commodity brand, the commodity name, the place of production, the transaction time, the transaction amount, the commodity characteristics and the like. The entity is a commodity, and the corresponding label is called a commodity label.

Entity: refers to objects or things that exist in the real world in a guest and can be distinguished from each other.

The relationship is as follows: a connection between two or more entities; the entities do not exist independently, and the related entities of a certain entity have great influence and reference value on the index. For example, order 1 is placed by customer a, and the association between entity customer a and entity order 1, i.e., that order 1 belongs to customer a.

Physical table: a table, entity or relationship stored in a data source may be associated with multiple physical tables. The data of the physical table can be modeled into an OLT model by using corresponding tools in the prior art. The OLT model is a logical abstraction for modeling data of a physical table, wherein O represents Object and is used for representing an entity in the physical world, such as a vehicle, an article and the like; l represents Link and is used for representing the association relation among a plurality of entities, such as vehicles owned by people, articles purchased by people and the like; t represents an attribute (which may be understood as a tag) of an entity or relationship, such as the time, place, etc. at which a person purchases a certain vehicle. The corresponding tool in the above mentioned prior art may be an existing smart label product, which displays data in the form of a label by marking and modeling the data (i.e. user data stored in a physical table of the data source).

Here, it should be noted that: the processing object of the tag processing scheme mentioned in the embodiment provided by the application is a tag obtained by marking data in a data source by a tool (such as an intelligent tag product) in the prior art. The label processing scheme reprocesses the labels to obtain processing results meeting specific requirements, such as derivative labels or statistical results. For example, an example of statistical results obtained from reprocessing a label is: and carrying out time-interval statistics on the commodity transaction time labels to count the transaction amount of the commodities in each time interval. Example of reprocessing a label to obtain a derivative label: comparing the transaction amount tag of the item with a set amount; and (4) obtaining the derivative label of the good product above the set amount.

SQL: structured Query Language, a Structured Query Language, is a database Query and programming Language.

TQL: tag query language, a statement consisting of an entity or relationship and a tag, written in a form similar to SQL, where the entity or relationship is similar to a table in SQL and the tag is similar to a field in the SQL table.

In the prior art, a service person needs to have a strong code editing capability to process an existing label again, and if the service person needs to have basic skills of SQL to write a processing logic program meeting specific requirements. If the coding capability of the service personnel is weak, more time is spent on learning and testing; the label processing efficiency is low. In addition, when a new label is required to be processed, business personnel are required to rewrite corresponding processing logic programs, and the reuse rate of the existing programs is low.

Therefore, the method and the device provide a preset number of models, and in the process of creating the label processing scheme, code compiling is not needed, and the creation of the label processing scheme can be completed by directly utilizing the pre-created models; business personnel only need pay attention to the label processing requirement, the method is simple and efficient, and the pre-written model has certain reusability.

In order to make the technical solutions better understood by those skilled in the art, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application.

In some of the flows described in the specification, claims, and above-described figures of the present application, a number of operations are included that occur in a particular order, which operations may be performed out of order or in parallel as they occur herein. The sequence numbers of the operations, e.g., 101, 102, etc., are used merely to distinguish between the various operations, and do not represent any order of execution per se. Additionally, the flows may include more or fewer operations, and the operations may be performed sequentially or in parallel. It should be noted that, the descriptions of "first", "second", etc. in this document are used for distinguishing different messages, devices, modules, etc., and do not represent a sequential order, nor limit the types of "first" and "second" to be different. In addition, the embodiments described below are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.

Fig. 1 shows a schematic flow chart of a data processing method according to an embodiment of the present application. The execution subject of the method provided by the embodiment can be a client. The client may be hardware integrated on the terminal and having an embedded program, may also be application software installed in the terminal, and may also be tool software embedded in an operating system of the terminal, which is not limited in this embodiment of the present application. The terminal can be any terminal device including a mobile phone, a tablet Personal computer, a Personal Digital Assistant (PDA), a Point of Sales (POS), a vehicle-mounted computer, an intelligent wearable device, and the like. Specifically, as shown in fig. 1, the method includes:

101. in response to a user-triggered event using the model creation schema, a target model to be used in creating the schema is determined.

102. Configuration information is obtained.

103. And generating a label processing scheme according to the target model and the configuration information.

In the foregoing 101, a user may trigger the event by clicking a corresponding control (e.g., "use a model to create a scenario" control) on the client-side interactive interface and selecting a target model to be used; or the user triggers the event by emitting a corresponding indication voice (e.g., "use the model creation scheme"); etc., which are not particularly limited in this embodiment.

Taking the interactive interface shown in fig. 2 as an example, after the user passes through the corresponding control on the client-side interactive interface, the selection window shown in fig. 2 is displayed. The user can select the model which is required to be used by the user, such as the "quantile model", in the selection box corresponding to the "selection model". The user may also set a "project name" for the newly created tag handling project in the window shown in fig. 2 when the project is created.

In 102, the target model may include, but is not limited to: at least one of a tag variable, a function variable, an input parameter variable, a scheduling attribute, a binding object variable, and the like.

In an implementation solution, the "acquiring configuration information" in the above-mentioned step 102 may include at least one of the following steps:

1021. responding to a tag selection event triggered by a user aiming at a tag list, and configuring a tag variable in the target model as a selected target tag in the tag selection event;

1022. responding to a function selection event triggered by a user for at least one candidate function, and configuring a function variable in the target model as a selected target function in the function selection event;

1023. configuring input variables in the target model as user input parameters;

1024. Acquiring a scheduling attribute configured by a user; and

1025. and responding to a processing result binding object setting event triggered by a user, and configuring a binding object variable in the target model as a target object set in the binding object setting event.

In an implementation technical solution, the "tag list" in 1021 may be obtained by the following steps:

acquiring a data source;

based on the data source, the list of tags is determined.

The tag list may be a tag list corresponding to an entity, or a tag list corresponding to a relationship. The data source may be selected by the user or may be a default data source of the system. The data source may be a database or a big data computing service, etc. In specific implementation, a specific tool (such as an intelligent label product) in the prior art can be utilized to model data of a physical table in a data source to obtain an OLT model, wherein O represents an entity; l characterizes relationships, T characterizes tags (i.e., attributes of an entity or relationship); according to the OLT model, an entity and a label list corresponding to the entity or a relation and a label list corresponding to the relation can be obtained.

In addition, at least one candidate function in the above 1022 may be a selectable value pre-configured in the target model and selectable by a user. I.e. during the creation of the object model, the function variables in the object model have been configured with the selectable values (i.e. the at least one candidate function). Therefore, when the user sets the function variable, the function variable may be directly selected from at least one candidate function preconfigured in the target model.

1023, the input parameters can be set by the user. Referring to one example shown in FIG. 3, "industry parameters" are input parameters.

In 1024 above, the scheduling attributes may include, but are not limited to: one-time scheduling and periodic scheduling.

In the above 1025, the target object selected by the user may specifically be an entity selected by the user and a tag list corresponding to the entity, or a relationship and a tag list corresponding to the relationship. The tag list contains at least one tag.

Referring to the example shown in FIG. 3, a user may configure variables in the target model through the configuration interface shown in FIG. 3. A user can drag one tag in the source tag area to an input box corresponding to an input index in the parameter setting area; or double-clicking a label in the source label area, wherein the label is displayed in the input box corresponding to the input index. At this time, the label scalar quantity representing the target model (i.e. the quantile index model) is configured as "practitioner count (cyrs)". The user can input corresponding parameters in the input box corresponding to the input variables (i.e. the industry codes in the figure), and the configuration of the input variables can be completed. In the example shown in fig. 3, the fractional order model has two function variables, which are: a calculation function and a divisor function. The calculation function has a default function, such as "avg"; if the user finds it appropriate and does not need to reconfigure, the configuration action can be performed without aiming at the calculation function; if the user feels that the reconfiguration is needed, the user can click a V-shaped window in the input box corresponding to the calculation function, and then at least one candidate function can be seen; from which the user may select a function to configure the calculation function. Similarly, the divisor function has a default function, such as "STDDEV"; if the user finds it appropriate and does not need to be reconfigured, the divisor function is not configured; if the user feels that the divider function needs to be reconfigured, the user can click a V-shaped window in the input box corresponding to the divider function, and then at least one candidate function can be seen; the user may select one of the functions from which to configure the divisor function. With continued reference to FIG. 3, the user may complete the configuration of the binding object variables in zone 1 of FIG. 3.

The configuration of the scheduling attributes is not shown in the interface shown in fig. 3. In specific implementation, the configuration interface may be configured with a configuration item of the scheduling attribute, such as a control corresponding to one-time scheduling, a control corresponding to periodic scheduling, and the like. The user may configure the scheduling attributes by selecting the corresponding control. If the user selects the control corresponding to the periodic scheduling, the user needs to set the periodic time length, for example, the periodic time length is executed once a day.

In 103, the model can be simply understood as: a general expression mode obtained by abstracting similar tag processing logic; it may be one or a set of solution formulas, a process flow comprising one or more sequentially performed steps, etc. The model comprises variables and attributes which can be correspondingly configured by a user based on actual tag processing requirements, and the user can obtain a corresponding tag processing scheme after completing the configuration of the variables and the attributes. In addition, the tag processing scheme in this embodiment is used to process the tag to obtain a corresponding processing result.

Several expressions of the model will be illustrated separately below.

Expression mode one, model is one or a group of formulas

In the case of a formula, such as the model is expressed as f (x, y) or f (x, y, z), etc.; wherein x, y and z in brackets are variables of the model. In the case of a set of equations, e.g. a model can be expressed as

The second expression and the model are a processing flow comprising one or more further orderly performed steps, for example, the model comprises the following processing steps:

subtracting the date type label and the current time;

judging the grade corresponding to the date type label according to the subtraction processing result;

and generating a corresponding derivative label based on the judged grade.

Each of the above expressions may be implemented in a computer programming language, such as TQL, tag query statement, as mentioned above.

According to the technical scheme, a user can complete the creation of the label processing scheme on the premise of not knowing the underlying physical label processing logic by using the existing model, the whole process is simple, convenient and efficient, and the efficiency of subsequent label processing is improved.

Further, the method provided by this embodiment may further include the following steps:

104. and responding to a test request event triggered by a user aiming at the label processing scheme, testing the label processing scheme, and outputting a test result as a basis for judging whether the label processing scheme meets a preset requirement.

Referring to the example shown in fig. 3, a user may trigger a test request event triggered for the tag processing scheme by touching a "test" control on the interface.

The purpose of testing the label processing scheme is to inspect whether the target model and the configuration information selected by the scheme meet the actual label processing requirements. Wherein the above-mentioned "preset requirement" can be understood as: the actual tag processing requirements. In a specific embodiment, if the label processing scheme is determined to meet the preset requirement based on the test result, the label processing scheme is indicated to have a submission condition and can be executed to perform corresponding processing on the label; otherwise, the user does not have the submitting condition, and needs to modify the configuration information or reselect the target model and perform corresponding configuration again.

The process of testing the label processing scheme may be understood as the following process: taking at least one sample label as an input of a label processing scheme, and executing the label processing scheme to obtain a corresponding processing result; obtaining a test result by comparing the processing result with a sample result; if the comparison processing result is the same as the sample result, the test result can be the information of 'test passing', and after the user sees the information of 'test passing', the user can trigger a submitting event by clicking a 'submitting' control on the interactive interface or sending a 'submitting' voice and the like; if the comparison processing result is different from the sample result, the test result can be information of 'test failed', and the user can select to reselect the target model or reconfigure the model variables after seeing the information of 'test failed'. Or, the processing result obtained by the label processing scheme is the test result, and the user can automatically judge whether the label processing scheme has the submission condition by checking the processing result.

For example, the tag processing scheme is to extract the transaction time of a certain commodity and then count the transaction amount of the commodity in each time period. At this time, in the process of testing the label processing scheme, a sample label list (i.e. a time list) can be used as the input of the label processing scheme, the label processing scheme is executed to obtain the transaction amount in each designated time period, and the obtained transaction amount in each designated time period is output as the test result; whether the label processing scheme has the submission condition can be judged according to the test result.

105. and responding to a submission event triggered by a user aiming at the label processing scheme, and generating an executable program according to the label processing scheme.

106. And scheduling the executable program based on the scheduling attribute of the label processing scheme, and processing the executable program by using the label to obtain a corresponding processing result.

107. And adding the processing result to an output table corresponding to the label processing scheme.

In an implementation solution, the above 105 "generating an executable program according to the tag processing scheme" may include the following steps:

1051. Testing the label processing scheme;

1052. and under the condition that the label processing scheme passes the test, analyzing the label processing scheme to generate the executable program.

Wherein 1051 "testing the tag processing scheme" may comprise at least one of the following steps:

s11, detecting a target model used by the label processing scheme;

s12, detecting at least one variable in the label processing scheme;

and S13, testing the connectivity of the label processing scheme and the data source.

In a specific embodiment, the variables included in the tag processing scheme include at least one of: tag variables, input variables, and function variables. Accordingly, the step S12 of "detecting at least one variable in the tag processing scheme" may specifically include at least one of the following steps:

carrying out validity detection on a target label configured for the label variable;

carrying out validity detection on the parameters configured for the input variables;

and detecting whether the target function configured for the function variable is a registration function.

Here, it should be noted that: the validity detection process of the target label and the parameters is not specifically limited in the embodiment; the legal detection rules can be set according to actual requirements, if the target label accords with the legal detection rules corresponding to the label, the detection is passed, otherwise, the detection is not passed. Similarly, if the parameter conforms to the legal detection rule corresponding to the parameter, the detection is passed, otherwise, the detection is not passed. In addition, the registration function can be understood as: a pre-stored, selectable function.

108. binding the output table with a target object if the tag handling scheme is configured with the target object. In particular implementation, the target object may include: an entity and a label corresponding to the entity, or a relationship and a label corresponding to the relationship.

Fig. 4 is a schematic flowchart illustrating a data processing method according to another embodiment of the present application. The execution subject of the method provided by this embodiment may be a client or a server. The client may be hardware integrated on the terminal and having an embedded program, may also be application software installed in the terminal, and may also be tool software embedded in an operating system of the terminal, which is not limited in this embodiment of the present application. The terminal can be any terminal device including a mobile phone, a tablet Personal computer, a Personal Digital Assistant (PDA), a Point of Sales (POS), a vehicle-mounted computer, an intelligent wearable device, and the like. The server may be: the system comprises an entity server, a virtual server deployed on a server group, a cloud and the like. Specifically, as shown in fig. 4, the method includes:

201. An executable program is generated according to the tag handling scheme.

Wherein the tag handling scheme is generated based on a model and configuration information.

202. And scheduling the executable program to process the label to obtain a corresponding processing result.

203. And adding the processing result to an output table corresponding to the label processing scheme.

Here, it should be noted that: the generation of the tag processing scheme may refer to the scheme provided in the embodiment shown in fig. 1, and this embodiment is not described again.

In the above 201, "generating an executable program according to the tag processing scheme" may be implemented by the following method:

2011. and testing the label processing scheme.

2012. And under the condition that the label processing scheme passes the test, analyzing the label processing scheme to generate the executable program.

In addition, it should be noted that: the above step 201 may be performed after an event of submitting the tag handling scheme is monitored. For example, an event that a user triggers submission of the tag processing scheme is monitored, or after a request for submitting the tag processing scheme is received, which is sent by a client, an executable program is generated according to the tag processing scheme.

In 202, the executable program may be scheduled based on a scheduling attribute of the tag handling scheme. The scheduling attribute may include: one-time scheduling, periodic scheduling, etc. If the label is scheduled once, generating a disposable label processing task; if scheduled periodically, a tag processing task is generated every time a period expires.

In 203, the output table may be specifically created for the tag processing scheme after the tag processing scheme is successfully submitted, and is used to store the processing result obtained after the tag processing.

According to the technical scheme provided by the embodiment, after the label processing scheme constructed by using the model is submitted, the executable program can be generated according to the label processing scheme; then the executable program is scheduled to realize the processing of the label, and the label processing efficiency is high.

204. binding the output table with a target object if the tag handling scheme is configured with the target object.

Specifically, the target object includes: an entity and a label corresponding to the entity, or a relationship and a label corresponding to the relationship.

Fig. 5 is a flow chart illustrating a data processing method according to another embodiment of the present application. The execution subject of the illustrated method provided by the present embodiment may be a client. The client may be hardware integrated on the terminal and having an embedded program, may also be application software installed in the terminal, and may also be tool software embedded in an operating system of the terminal, which is not limited in this embodiment of the present application. The terminal can be any terminal device including a mobile phone, a tablet Personal computer, a Personal Digital Assistant (PDA), a Point of Sales (POS), a vehicle-mounted computer, an intelligent wearable device, and the like. Specifically, as shown in fig. 5, the method includes:

301. and responding to a model creating event triggered by a user, and acquiring creating information and attribute information generated in the model creating event.

302. And generating a model for creating a label processing scheme based on the creation information and the attribute information.

In a specific implementation, the creation information in 301 may be a program written in a computing language (e.g., TQL) and input or input by a user. Referring to the example shown in FIG. 6, a user may write a program within the "TQL edit" box; or the user imports the program stored locally or in the external device into the edit box. For example, the step 301 of "acquiring creation information and attribute information" may include:

3011. Acquiring the creation information input or imported by a user;

3012. determining at least one object needing attribute setting according to the creation information;

3013. and acquiring attribute information respectively set for the at least one object by the user.

Taking creating information as an example of a program written using a computing language (such as TQL), the 3012 step may specifically be: analyzing the program to obtain at least one object (namely a variable in the program); the parsed objects may be displayed in the "model setup" area shown in FIG. 6. Therefore, the user can set each object (also called variable) in the 'model setting' area. Before the program is parsed, the creation information may be tested. That is, the step 3012 "determining at least one object to be subjected to attribute setting according to the creation information" may specifically include the following steps:

testing the creation information;

and under the condition that the creation information passes the test, analyzing the creation information to analyze the at least one object.

In a specific implementation scheme, the "testing the creation information" may specifically include:

S1, acquiring a label list and a function list;

s2, responding to a label selection event triggered by the user aiming at the label list, and acquiring a first label selected by the user;

s3, responding to a function selection event triggered by the user aiming at the function list, and acquiring a first function selected by the user;

s4, responding to a test request triggered by the user aiming at the creation information, and testing the creation information based on the first label and the target function.

It is added here that, when the creation information is a program written using a computer language, the testing of the creation information may include: and checking the grammar of the creation information. The syntax verification of the program written in the computer language may be implemented by referring to the prior art, which is not specifically limited in this embodiment.

Further, the aforementioned 3013, acquiring the attribute information respectively set by the user for the at least one object may include at least one of the following steps:

in response to a tag selection event triggered by a user aiming at a tag list, setting at least one tag selected by the user as a selectable value of a tag variable corresponding to a first object in the creation information;

Responding to a function selection event triggered by a user aiming at a function list, and setting at least one function selected by the user as a selectable value of a function variable in the creation information corresponding to a second object;

and acquiring at least one input parameter input by a user, and setting the at least one input parameter as a selectable value of an input variable corresponding to the third object in the creation information.

In a specific implementation, a tag selected by the user may be set as a default value of the first object corresponding to the tag variable in the creation information, where the default value may be one of selectable values of the first object.

Similarly, a function selected by the user may be set as a default value of the function variable in the creation information corresponding to the second object, where the default value may be one of the selectable values of the second object.

Similarly, an input parameter input by the user may be set as a default value of the input variable in the creation information corresponding to the third object, and the default value may be one of selectable values of the third object.

In the technical solution provided in this embodiment, a model for creating a tag processing scheme is generated based on the creation information and the attribute information; the label processing scheme can be created conveniently by using the created model, so that the creation process of the label processing scheme is simpler and more efficient, and the efficiency of subsequent label processing is improved.

305. and acquiring a model identification input by a user aiming at the model.

306. And acquiring description information which is input by a user and is related to the model.

307. Associating at least one of the model identification and the description information with the model.

Wherein the description information includes at least one of: description text, description image, description audio, description video.

The model identification here can be understood simply as: model names set for the models, for example, as shown in fig. 6, the user can input model identifications within the "model names" of the "basic information". The description information associated with the model may include, but is not limited to: the method for using the model, the service scene to which the model can be adapted, the label processing logic of the model, the configuration description of how to perform the model and the like.

Further, the method provided by this embodiment may further include at least one of the following steps:

deleting the model in response to a deletion event triggered by a user for the model;

setting a state of the model to an available state in response to a user-triggered state setting event for the model;

Setting the state of the model to an unavailable state in response to a user setting event triggered by the model;

and updating the model based on the editing content generated in the editing event in response to the editing event triggered by the user for the model.

The above-mentioned available states can be understood as: a state that can be used to create a tag handling scheme; accordingly, the unusable state can be understood as: cannot be used to create a state of the tag handling scheme.

The above editing contents may include, but are not limited to: modifying the configuration information, reselecting the target model, and performing corresponding configuration again.

Fig. 7 is a schematic structural diagram of a data processing system according to an embodiment of the present application. As shown in fig. 7, the data processing system includes: a first client 401 and a server 402. Wherein the content of the first and second substances,

a first client 401, configured to determine, in response to an event triggered by a user to use a model creation scheme, a target model to be used in the creation scheme; acquiring configuration information; generating a label processing scheme according to the target model and the configuration information, wherein the label processing scheme is used for processing labels to obtain corresponding processing results; sending the label processing scheme to a server;

The server 402 is used for generating an executable program according to the label processing scheme; scheduling the executable program to process the label to obtain a processing result; and adding the processing result to an output table corresponding to the label processing scheme.

Here, it should be noted that: the first client may be hardware integrated on the terminal and having an embedded program, may also be application software installed in the terminal, and may also be tool software embedded in an operating system of the terminal, which is not limited in this embodiment of the application. The terminal can be any terminal device including a mobile phone, a tablet Personal computer, a Personal Digital Assistant (PDA), a Point of Sales (POS), a vehicle-mounted computer, an intelligent wearable device, and the like. The server may be a physical server, a virtual server deployed on a server cluster, a cloud, and so on.

Further, the server is further configured to store at least one model for creating a tag processing scheme; the client is also used for responding to an event of using the model creation scheme triggered by the user and acquiring a target model to be used in the creation scheme from the server.

Here, it should be noted that: at least one model used for creating the tag processing scheme and stored in the server side can be uploaded to the server side after being customized by a user through a corresponding client side. That is, as shown in fig. 7, the data processing system provided by the present application includes a second client 403 and a server 402. Wherein the content of the first and second substances,

a second client 403, configured to, in response to a model creation event triggered by a user, obtain creation information and attribute information generated in the model creation event; generating a model for creating a label processing scheme according to the creation information and the attribute information;

Wherein the caller may be the first client 401 in the system.

Further, the system provided in this embodiment may further include:

a first client 401, configured to, in response to an event triggered by a user to use a model creation scheme, obtain, from the server, a target model to be used in the creation scheme; acquiring configuration information; and generating a label processing scheme according to the target model and the configuration information, and processing the label to obtain a corresponding processing result.

Here, it should be noted that: for specific implementation functions of each constituent unit, such as the server, the first client, and the second client, in the data processing system of this embodiment, reference may be made to corresponding contents in each of the above embodiments, and details are not described here.

For convenience of understanding, the system provided in this embodiment is nested into a specific application scenario, and the second client 403 can be simply understood as: and the client at the technician side can complete the creation and maintenance (such as modification, deletion, release and the like) of the model through the functions provided by the corresponding client. The first client 401 may be simply understood as: and at the client side of the service personnel, the service personnel can select the model created and released by the technical personnel to create the label processing scheme required by the service personnel through the function provided by the corresponding client side. The server 402 can be simply understood as: through a hardware server, a virtual server or a cloud end and the like connected with a technician side client and a service personnel side client through a network, after a technician creates and issues a model through the corresponding client, the service personnel can inquire the model through the corresponding client, and after the service personnel selects the model through the corresponding client, a label processing scheme can be created based on the model. The business personnel side client can download the model to a local generation label processing scheme and then submit the scheme to the server so as to enable the server to perform a corresponding label processing process; or the service personnel side client can upload the configuration information of the model configuration of the user to the server side, and the server side generates the label processing scheme based on the model and the configuration information.

According to the technical scheme provided by the embodiment of the application, high-level technicians with both business experience and data processing capacity abstract similar label processing logic to form a universal model; the business person creates a label processing scheme using the model. The label processing scheme created by the service personnel can generate a label processing task, and the processing result can be continuously recycled, so that the continuous production of the label is realized. In specific implementation, the labels to be processed can be obtained based on the big data computing service tool and the capability of the data resource platform for marking and generating the labels.

The technical scheme provided by the embodiment comprises three parts:

a first part: creating a model

As shown in fig. 8, the method comprises the following steps:

the first step is as follows: selecting a data source, and determining an entity and a tag list corresponding to the entity or a relationship and a tag list corresponding to the relationship based on the data source;

the second step is that: selecting a label according to the label list;

the third step: selecting a UDF function according to the UDF list;

the fourth step: testing a program input or imported by a user; the test is passed, and the step five is entered; otherwise, the user modifies or re-imports the program and tests again.

The fifth step: and analyzing the program to obtain a label variable, a function variable and an input variable.

And a sixth step: selecting default values and selectable values for configuring tag variables from a tag list;

the seventh step: selecting default values and optional values of configuration function variables from the UDF list;

eighth step: default and selectable values for configuration input variables, etc.

The ninth step: and generating and storing the model based on the program and the attribute information configured for each variable.

After the model creation is completed, operations of updating, publishing, offline, deleting and the like can be performed. The model may be used to create a tag handling scheme after release. The released model can be subjected to offline operation again, and the offline target model cannot be used for creating the label processing scheme.

A second part: creation of label processing scheme

As shown in fig. 9, the method includes:

the first step is as follows: selecting a target model;

the second step is that: selecting a data source, and determining an entity and a tag list corresponding to the entity or a relationship and a tag list corresponding to the relationship according to the data source;

the third step: selecting a first tag to configure a tag variable in the target model as the first tag according to a tag list;

The fourth step: selecting a first UDF function according to the UDF function list to configure the function variable in the target model into the first UDF function;

the fifth step: configuring input variables in the target model.

And a sixth step: generating a label processing scheme based on the target model and the configuration information of each variable; testing the label processing scheme; the test is passed, and the seventh step is entered; if the test fails, returning to the third step to re-configure the variables;

the seventh step: under the condition of the requirement of binding objects, configuring target objects to be bound for the processing result of the label processing scheme;

eighth step: configuring scheduling attributes for the label processing scheme;

the ninth step: saving the tag handling scheme to wait for submission.

And a third part: label processing scheme submission

As shown in fig. 10, the method comprises the following steps:

the first step is as follows: and detecting the label processing scheme, wherein the detection is carried out by entering a second step.

The second step is that: and analyzing the tag processing scheme, generating executable SQL and creating an output table.

The third step: and if the tag processing scheme is configured with a target object to be bound, binding the output table with the target object.

The fourth step: if the scheduling attribute is periodic scheduling, configuring a scheduling period and an execution variable, generating a periodic workflow jar packet, executing the periodic workflow scheduling and adding an execution result to an output table; and if the scheduling attribute is one-time scheduling, configuring one-time tasks, generating one-time workflow jar packets, executing the one-time workflow scheduling and adding an execution result to an output table.

The following embodiments will explain the technical solutions provided by the embodiments of the present application from the perspective of interface display and interface operation.

Fig. 11 shows a flowchart of a data processing method according to an embodiment of the present application. The execution subject of the method provided by this embodiment may be a client. Specifically, as shown in fig. 11, the method includes:

501. and responding to a selection event triggered by a user aiming at least one model, and displaying a configuration page corresponding to the target model selected from the selection event.

502. And responding to a configuration event triggered on the configuration page by a user, and displaying the configuration information generated in the configuration event.

503. And responding to a submission event triggered by a user on the configuration page, and displaying response information after a submission operation is performed on a tag processing scheme generated based on the target model and the configuration information.

In the above 501, referring to fig. 2, after the user selects an "x" model "(e.g., a quantile model), the configuration page shown in fig. 3 can be displayed on the interface.

In 502, referring to fig. 3, the user may drag or double-click, and use a selected tab in the left tab list as configuration information of a tab variable in the target model. Specifically, in this step 502, "displaying configuration information generated in the configuration event in response to the configuration event triggered by the user on the configuration page" may specifically include:

Responding to a data source selection event triggered on the configuration page by a user, and displaying an identifier of a selected target data source in the data source selection event;

displaying a tag list determined according to the target data source;

responding to a tag selection event triggered by a user aiming at the tag list, and displaying a target tag selected from the tag selection event in a tag configuration display area of the configuration page;

responding to a configuration event triggered by a user aiming at an input parameter, and displaying a parameter input by the user in a parameter display area of the configuration page;

displaying at least one candidate function in response to a function selection event triggered by a user within the function box;

and in response to a function selection event triggered by a user for the at least one candidate function, displaying a selected target function in the function selection event in a function display area of the configuration page.

Before 503, the method may further include the following steps:

503' in response to a test event triggered by the user on the configuration page, displaying the test result as a basis for determining whether the label processing scheme is submittable.

The user is provided with a test function, so that a technician can check the created information to ensure that the subsequently submitted target model is accurate and error-free.

The "response information" in 503 may specifically be: and submitting success prompt information or failure prompt information and the like.

504. displaying description information related to the target model on the configuration page;

Fig. 13 is a flowchart illustrating a data processing method according to an embodiment of the present application. The execution subject of the method provided by this embodiment may be a client. Specifically, as shown in fig. 13, the data processing method includes:

601. and displaying the creation information and the attribute information in response to a creation event triggered by a user on the model creation interface.

602. And responding to a confirmation event triggered by a user, and displaying a page element corresponding to the model generated based on the creation information and the attribute information in a model management page.

In an implementation solution, the "displaying creation information and attribute information" in 601 above may include the following steps:

6011. displaying the creation information;

6012. responding to a test request triggered by a user aiming at the creation information, testing the creation information, and displaying at least one object needing attribute setting determined based on the creation information under the condition that the creation information passes the test;

6013. And in response to the attribute setting event triggered by the user aiming at the at least one object, showing the attribute information respectively set for the at least one object.

Referring to fig. 12, after clicking the "new model" control on the interface, the user can enter the model creation interface shown in fig. 6. In a specific implementation, the creation information generated in the creation event may be a program input or imported by the user in, for example, a "TQL edit" area in the interface shown in fig. 6.

In the 6012, "in response to a test request triggered by a user for the creation information, the creation information is tested, and when the creation information passes the test, at least one object to be subjected to attribute setting determined based on the creation information is displayed," may be implemented by:

displaying an identifier of a selected target data source in response to a data source selection event triggered by a user on the model creation interface;

displaying a tag list determined according to the target data source;

responding to a label selection event triggered by a user aiming at the label list, and displaying a selected first label;

displaying at least one candidate function;

Presenting the selected first function in response to a function selection event triggered by a user for the at least one candidate function;

and responding to a test request triggered by a user aiming at the creation information, testing the creation information according to the first label and the first function, and displaying at least one object which is determined based on the creation information and needs to be subjected to attribute setting under the condition that the test is passed.

Further, the method provided by this embodiment further includes at least one of the following steps:

603. displaying a management control associated with the target model in the model management page; wherein the management control comprises: deleting at least one of the control, the editing control and the state modification control;

604. in the model management page, the number of times the object model is used to create a tag handling solution is shown.

Referring to fig. 12, each model is correspondingly provided with a management control, and when a management user dials the state modification control (i.e., the release state control in fig. 12) to the open state, the state of the model is in the available state, so that the label processing scheme creating user can view the model through the client. If the administrative user dials the state modification control (i.e., the publish state control in fig. 12) to the closed state, the state of the model is in the unavailable state. If the model is deleted or in an unavailable state, the label processing scheme creating user cannot see the model through the client, and therefore cannot use the model. The user can modify the model by editing the control.

Fig. 14 shows a data processing apparatus according to an embodiment of the present application. The device includes: a determination module 11, an acquisition module 12 and a first generation module 13. The determining module 11 is configured to determine, in response to a user-triggered event using a model creation scheme, a target model to be used in the creation scheme; the obtaining module 12 is configured to obtain configuration information; the first generating module 13 is configured to generate a label processing scheme according to the target model and the configuration information.

Further, the obtaining module 12 further has at least one function of:

responding to a tag selection event triggered by a user aiming at a tag list, and configuring a tag variable in the target model as a selected target tag in the tag selection event;

responding to a function selection event triggered by a user for at least one candidate function, and configuring a function variable in the target model as a selected target function in the function selection event;

Configuring input variables in the target model as user input parameters;

acquiring a scheduling attribute configured by a user; and

and responding to a processing result binding object setting event triggered by a user, and configuring a binding object variable in the target model as a target object set in the binding object setting event.

Further, the obtaining module 12 is further configured to: acquiring a data source; based on the data source, the list of tags is determined.

Further, the data processing apparatus provided in this embodiment further includes: and a testing module. The test module is used for responding to a test request event triggered by a user aiming at the label processing scheme, testing the label processing scheme and outputting a test result as a basis for judging whether the label processing scheme meets a preset requirement.

Further, the data processing apparatus provided in this embodiment may further include:

the second generation module is used for responding to a submission event triggered by a user aiming at the label processing scheme and generating an executable program according to the label processing scheme;

the scheduling module is used for scheduling the executable program based on the scheduling attribute of the label processing scheme so as to process the label to obtain a corresponding processing result;

And the adding module is used for adding the processing result to the output table corresponding to the label processing scheme.

Further, the second generating module is further configured to:

testing the label processing scheme;

and under the condition that the label processing scheme passes the test, analyzing the label processing scheme to generate the executable program.

Further, the second generating module further has at least one detecting function of:

detecting a target model used by the label processing scheme;

detecting at least one variable in the tag handling scheme;

and testing the connectivity of the tag processing scheme and a data source.

Further, the variables included in the tag processing scheme include at least one of: tag variables, input variables, and function variables. Correspondingly, the second generating module further has at least one of the following detecting functions:

Further, the data processing apparatus provided in this embodiment may further include a binding module. The binding module is used for binding the output table with a target object under the condition that the tag processing scheme is configured with the target object.

Further, the target object includes: an entity and a label corresponding to the entity, or a relationship and a label corresponding to the relationship.

Here, it should be noted that: the data processing apparatus provided in the foregoing embodiments may implement the technical solutions described in the foregoing method embodiments, and the specific implementation principle of each module or unit may refer to the corresponding content in the foregoing method embodiments, which is not described herein again.

Fig. 15 shows a data processing apparatus according to still another embodiment of the present application. The data processing apparatus includes: a generation module 21, a scheduling module 22 and an adding module 23. The generating module 21 is configured to generate an executable program according to a tag processing scheme; wherein the tag handling scheme is generated based on a model and configuration information. The scheduling module 22 is configured to schedule the executable program so as to process the tag to obtain a corresponding processing result. The adding module 23 is configured to add the processing result to an output table corresponding to the tag processing scheme.

Further, the generating module 21 is further configured to:

testing the label processing scheme;

Fig. 16 is a schematic structural diagram of a data processing apparatus according to yet another embodiment of the present application. As shown, the data processing apparatus includes: an acquisition module 31 and a generation module 32. The acquiring module 31 is configured to acquire, in response to a model creation event triggered by a user, creation information and attribute information generated in the model creation event; the generating module 32 is configured to generate a model for creating a label processing scheme based on the creating information and the attribute information.

Further, the obtaining module 31 is further configured to:

acquiring the creation information input or imported by a user;

determining at least one object needing attribute setting according to the creation information;

and acquiring attribute information respectively set for the at least one object by the user.

Further, the obtaining module 31 may be further configured to:

testing the creation information;

Still further, the obtaining module 31 is further configured to:

acquiring a tag list and a function list;

responding to a tag selection event triggered by a user aiming at the tag list, and acquiring a first tag selected by the user;

responding to a function selection event triggered by a user aiming at the function list, and acquiring a first function selected by the user;

And responding to a test request triggered by a user aiming at the creation information, and testing the creation information based on the first label and the target function.

Further, the obtaining module 31 further has at least one function of:

Further, the data processing apparatus provided in this embodiment may further include an association module; the association module is configured to:

obtaining a model identification input by a user aiming at the model;

acquiring description information which is input by a user and is related to the model;

associating at least one of the model identification and the description information with the model;

Further, the data processing apparatus provided in this embodiment may further include a management module. The management module has at least one of the following functions:

Fig. 17 shows a schematic structural diagram of a client device according to an embodiment of the present application. As shown, the client device includes a memory 41 and a processor 42, wherein,

The memory 41 is used for storing programs;

the processor 42, coupled to the memory 41, is configured to execute the program stored in the memory 41 to:

acquiring configuration information;

and generating a label processing scheme according to the target model and the configuration information, and processing the label to obtain a corresponding processing result.

The memory 41 described above may be configured to store other various data to support operations on the client device. Examples of such data include instructions for any application or method operating on the client device. The memory 41 may be implemented by any type or combination of volatile or non-volatile memory devices, such as Static Random Access Memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic or optical disks.

The processor 42 may also implement other functions besides the above functions when executing the program in the memory 41, which may be specifically referred to the description of the foregoing embodiments.

Further, as shown in fig. 17, the client device further includes: a display 44, a power supply component 45, an audio component 46, and the like. Only some of the components are shown schematically in fig. 17, and the client device is not meant to include only the components shown in fig. 17.

The application further provides a processing device. The structure of the processing device provided in this embodiment is similar to that of the client device described above, and is shown in fig. 17. The processing device includes a memory and a processor, wherein,

the memory is used for storing programs;

When the processor executes the program in the memory, the processor may implement other functions in addition to the above functions, which may be specifically referred to the description of the foregoing embodiments.

The application further provides a client device. The structure of the client device provided in this embodiment is similar to that of the client device described above, and is shown in fig. 17. The client device includes a memory and a processor, wherein,

the memory is used for storing programs;

Accordingly, the present application further provides a computer-readable storage medium storing a computer program, where the computer program can implement the steps or functions of the data processing method provided in the foregoing embodiments when executed by a computer.

The above-described embodiments of the apparatus are merely illustrative, and the units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the present embodiment. One of ordinary skill in the art can understand and implement it without inventive effort.

Through the above description of the embodiments, those skilled in the art will clearly understand that each embodiment can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware. With this understanding in mind, the above-described technical solutions may be embodied in the form of a software product, which can be stored in a computer-readable storage medium such as ROM/RAM, magnetic disk, optical disk, etc., and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to execute the methods described in the embodiments or some parts of the embodiments.

Finally, it should be noted that: the above embodiments are only used to illustrate the technical solutions of the present application, and not to limit the same; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; and such modifications or substitutions do not depart from the spirit and scope of the corresponding technical solutions in the embodiments of the present application.

Claims

1. A data processing method, comprising:

acquiring configuration information;

2. The method of claim 1, wherein obtaining configuration information comprises at least one of:

configuring input variables in the target model as user input parameters;

acquiring a scheduling attribute configured by a user; and

3. The method of claim 2, further comprising:

Acquiring a data source;

based on the data source, the list of tags is determined.

4. The method of any of claims 1 to 3, further comprising:

and responding to a test request event triggered by a user aiming at the label processing scheme, testing the label processing scheme, and outputting a test result as a basis for judging whether the label processing scheme meets a preset requirement.

5. The method of any of claims 1 to 3, further comprising:

responding to a submission event triggered by a user aiming at the tag processing scheme, and generating an executable program according to the tag processing scheme;

scheduling the executable program based on the scheduling attribute of the label processing scheme so as to process the label to obtain a corresponding processing result;

6. The method of claim 5, wherein generating an executable program according to the tag handling scheme comprises:

testing the label processing scheme;

7. The method of claim 6, wherein testing the label processing scheme comprises at least one of the following steps:

detecting a target model used by the label processing scheme;

detecting at least one variable in the tag handling scheme;

and testing the connectivity of the tag processing scheme and a data source.

8. The method of claim 7, wherein the variables included in the tag handling scheme comprise at least one of: label variables, input variables and function variables; and

detecting at least one variable in the tag handling scheme, comprising at least one of:

9. The method of claim 5, further comprising:

binding the output table with a target object if the tag handling scheme is configured with the target object.

10. The method of claim 9, wherein the target object comprises: an entity and a label corresponding to the entity, or a relationship and a label corresponding to the relationship.

11. A data processing method, comprising:

12. The method of claim 11, wherein generating an executable program according to the tag handling scheme comprises:

testing the label processing scheme;

13. The method of claim 11 or 12, further comprising:

14. A data processing method, comprising:

15. The method of claim 14, wherein obtaining creation information and attribute information comprises:

acquiring the creation information input or imported by a user;

16. The method of claim 15, wherein determining at least one object for which attribute setting is required according to the creation information comprises:

testing the creation information;

17. The method of claim 16, wherein testing the creation information comprises:

acquiring a tag list and a function list;

18. The method according to any one of claims 15 to 17, wherein obtaining attribute information respectively set for the at least one object by a user comprises at least one of the following steps:

19. The method of any one of claims 14 to 17, further comprising:

obtaining a model identification input by a user aiming at the model;

20. The method according to any one of claims 14 to 17, further comprising at least one of the steps of:

21. A data processing system, comprising:

22. The system of claim 21,

the server is also used for storing at least one model used for creating a label processing scheme;

the first client is also used for responding to an event of using the model creation scheme triggered by the user and acquiring a target model to be used in the creation scheme from the server.

23. A data processing system, comprising:

24. The system of claim 23, further comprising:

the system comprises a first client, a second client and a third client, wherein the first client is used for responding to an event of using a model creation scheme triggered by a user and acquiring a target model to be used in the creation scheme from a server; acquiring configuration information; and generating a label processing scheme according to the target model and the configuration information.

25. A data processing method, comprising:

26. The method of claim 25, wherein in response to a configuration event triggered by a user on the configuration page, displaying configuration information generated in the configuration event comprises:

displaying a tag list determined according to the target data source;

27. The method of claim 25 or 26, wherein before displaying response information after performing a submit operation on a tag handling scheme generated based on the target model and the configuration information in response to a submit event triggered by a user on the configuration page, further comprising:

and responding to a test event triggered by a user on the configuration page, and displaying a test result as a basis for judging whether the tag processing scheme can be submitted.

28. The method of claim 25 or 26, further comprising:

displaying description information related to the target model on the configuration page;

29. A data processing method, comprising:

30. The method of claim 29, wherein displaying the creation information and the attribute information comprises:

displaying the creation information;

responding to a test request triggered by a user aiming at the creation information, testing the creation information, and displaying at least one object needing attribute setting determined based on the creation information under the condition that the creation information passes the test;

and in response to the attribute setting event triggered by the user aiming at the at least one object, showing the attribute information respectively set for the at least one object.

31. The method of claim 30, wherein in response to a test request triggered by a user for the creation information, in a case that the creation information is tested and the creation information passes the test, displaying at least one object to be subjected to attribute setting determined based on the creation information, comprises:

displaying a tag list determined according to the target data source;

displaying at least one candidate function;

32. The method according to any one of claims 29 to 31, further comprising at least one of the following steps:

displaying a management control associated with the target model in the model management page; wherein the management control comprises: deleting at least one of the control, the editing control and the state modification control;

in the model management page, the number of times the object model is used to create a tag handling solution is shown.

33. A client device comprising a memory and a processor, wherein,

the memory is used for storing programs;

acquiring configuration information;

34. A processing device comprising a memory and a processor, wherein,

the memory is used for storing programs;

35. A client device comprising a memory and a processor, wherein,

The memory is used for storing programs;