Detailed Description
Hereinafter, embodiments of the present application will be described with reference to the accompanying drawings. It should be understood that the description is only illustrative and is not intended to limit the scope of the application. In the following detailed description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the embodiments of the application. It may be evident, however, that one or more embodiments may be practiced without these specific details. In addition, in the following description, descriptions of well-known structures and techniques are omitted so as not to unnecessarily obscure the present application.
The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. The terms "comprises," "comprising," and/or the like, as used herein, specify the presence of stated features, steps, operations, and/or components, but do not preclude the presence or addition of one or more other features, steps, operations, or components.
All terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art unless otherwise defined. It should be noted that the terms used herein should be construed to have meanings consistent with the context of the present specification and should not be construed in an idealized or overly formal manner.
Where information is used that is similar to the expression "at least one of A, B and C, etc." it is generally understood in the sense one having skill in the art would understand the expression (e.g., "a system having at least one of A, B and C" would include, but is not limited to, a system having a alone, B alone, C alone, a and B with a and C, B and C with B, and/or A, B, C, etc.).
In the implementation of the embodiment of the present application, it is found that, with the rapid development of deep learning technology, a large neural network model (hereinafter referred to as a large model) has become the core of various applications. The large model not only has excellent performance in the field of natural language processing, but also has remarkable success in the fields of computer vision, voice recognition, recommendation systems and the like. In the process of application of large models in many subdivision areas, various different scenarios exist, such as a large model dialogue, an agent dialogue, a workflow dialogue, a back-end service (Model Context Protocol Server, MCP SERVER) dialogue, a custom service dialogue, evaluation of large model capability, and evaluation of model service capability.
For the evaluation of large model capability and the evaluation of model service capability, comprehensive evaluation of systems in various aspects of accuracy, efficiency, robustness, interpretability, diversity, generalization capability and the like is required. Thus, in contrast testing of large models or model services, a single assessment task may contain sub-tasks for each of multiple large models or model services in order to make an intuitive contrast assessment of the large models and model services. In a specific software engineering implementation process, when a plurality of subtask interfaces are called to be created, the parameter data of the creation subtask can be checked in detail. When the parameter data of the subtasks are used, the structured data more accords with the application scene of the program, wherein the structured data comprises multiple aspects of parameter structured access, storage, data processing and the like. However, in terms of parameter data verification, various data transmission and verification processes can be generated due to various different scenes, and especially, parameter data aiming at model service parameter data and various plug-ins are more various, and the parameter data needs to be verified one by one at an interface layer to ensure stable and safe operation of the service, and the work is complicated. If the parameter data is abnormal, the abnormal position and content need to be precisely positioned, so that the user can be helped to adjust the parameter data.
In view of the above, an embodiment of the present application provides a task item creation method, including determining task information including a task object set in response to a creation request of a target task, and in the case where it is determined that the task information meets a predetermined format requirement, for any one of the task object set, verifying parameters of the task object based on a parameter model matched with the object type in the case where the object type of the task object is a predetermined type, the parameter model being generated based on a verification rule matched with the object type, and in the case where it is determined that the parameters of any one of the task object set pass, performing a structural process on the task information, and recording a target task item of the target task in a database based on the task information of the structural process.
FIG. 1 illustrates an application scenario diagram of a task item creation method, a task item query method, an apparatus, a device, a medium, and a program product according to an embodiment of the present application.
As shown in fig. 1, an application scenario 100 according to this embodiment may include a terminal device 101, a server device 102, and a database 103. The terminal device 101 and the server device 102, and the database 103 may provide media of a communication link through a network. The network may include various connection types, such as wired, wireless communication links, or fiber optic cables, among others.
A user may interact with the server device 102 via a network using the terminal device 101 to receive or send messages, etc. Various communication client applications, such as shopping class applications, web browser applications, search class applications, instant messaging tools, mailbox clients, social platform software, etc., may be assembled on the terminal device 101 (by way of example only).
The terminal device 101 may be a variety of electronic devices having a display screen and supporting web browsing, including but not limited to smartphones, tablets, laptop and desktop computers, and the like.
The server device 102 may include a server, workstation, or other type of computer device. The server may be a server providing various services, such as a background management server (merely an example) providing support for a website browsed by the user using the terminal device 101. The background management server may analyze and process the received data such as the user request, and feed back the processing result (e.g., the web page, information, or data obtained or generated according to the user request) to the terminal device.
Database 103 may be used to store data and server device 102 may store data in database 103 or query database 103 for data based on a received user request.
It should be noted that, the task item creation method provided by the embodiment of the present application may be generally executed by the server device 102. Accordingly, the task item creation device provided by the embodiment of the present application may be generally disposed in the server device 102. The task item creation method provided by the embodiment of the present application may also be performed by a server device or a server device cluster that is different from the server device 102 and is capable of communicating with the terminal device 101 and/or the server device 102. Accordingly, the task item creation apparatus provided by the embodiment of the present application may also be provided in a server device or a server device cluster that is different from the server device 102 and is capable of communicating with the terminal device 101 and/or the server device 102.
It should be understood that the number of terminal devices, server devices and databases in fig. 1 is merely illustrative. There may be any number of terminal devices, server devices, and databases, as desired for implementation.
The task item creation method of the application embodiment will be described in detail below with reference to fig. 2 to 4 based on the scenario described in fig. 1.
FIG. 2 illustrates a flow chart of a task item creation method according to an embodiment of the present application.
As shown in FIG. 2, the task item creation method of this embodiment includes operations S210-S240.
In operation S210, task information is determined in response to a creation request of a target task.
In operation S220, in the case that the task information meets the predetermined format requirement, for any task object in the task object set, the parameters of the task object are verified based on the parameter model matched with the object type in the case that the object type of the task object is the predetermined type.
In operation S230, in a case where it is determined that the parameter of any one of the task objects in the task object set passes the verification, the task information is structured.
In operation S240, a target task item of a target task is recorded in a database based on the structured task information.
In this embodiment, the target tasks may include, but are not limited to, assessment tasks, dialog tasks, and the like. The evaluation task may include, for example, model performance evaluation. The performance evaluation for the model may be, for example, a model evaluation and/or a model service evaluation, etc.
The creation request may include a name of the target task, a description of the target task, and the like.
The task information may include a set of task objects. Different target tasks and corresponding task objects are different. The task object and the data associated with the task object may be determined based on the name of the target task and the description of the target task.
For example, for model performance evaluation tasks, task objects may be models and/or services. For conversational tasks, task objects may be models, services, agents, workflows, etc. The set of task objects may include a plurality of task objects and parameters for each of the plurality of task objects.
The predetermined format requirements may be format requirements in terms of structure, content, representation, etc., for the task object. For example, for a model, the predetermined format requirements may include, but are not limited to, model structure definitions, model parameter representations, and model file formats, among others. The model structure defines a format such as input, output, internal parameters, layer structure, etc. that specifies the model. Model parameters represent, for example, a storage format of model parameters. The model file format is a save format of model files, etc. For services, the predefined format requirements may include, but are not limited to, service interface definitions, service protocol specifications, and the like. The service interface defines format requirements such as input parameters, output results, calling modes, etc. of the specified service.
The predetermined format requirements may also include mandatory format requirements, etc.
The predetermined type may be preset. The parametric model may be generated based on a verification rule that matches the object type. Each of the predetermined types maps a parametric model. Verification may include, but is not limited to, type checking, scope checking, and the like.
The parameters of the task object may include, for example, model parameters and/or service parameters. Model parameters such as model unique identifiers, model names, graphical representations of models, etc. Service parameters such as service configuration parameters, interface parameters, security parameters, etc.
The verification rules may include types of verification parameters, data constraints of the verification parameters, and the like. For example, the type of verification parameter is such as integer, string, list, structure, union, etc. The data limit of the checking parameters includes the maximum and minimum value of shaping checking, the length of the character string checking character string, the format of the character string, the checking of the content of the character string, the length of the list checking list, the format of the data element, the content of the data element and the like. A combination is understood to be a combination of different types.
The verification rules matched with the model may include, for example, but are not limited to, type verification rules of the model structure, type verification rules of the model input, type verification rules of the model output, type verification rules of the model training parameters, type verification rules of the model application, and the like.
For example, for a type of parameter of a task object, it is checked whether the parameter value of the task object under the type is within an allowable range, and/or it is determined whether a dependency relationship between a plurality of parameters is satisfied, such as whether the presence of some parameters depends on the presence of other parameters, and/or whether values between parameters agree, such as whether a start time and an end time are reasonable, or the like.
And if the parameters of any task object in the task object set pass the verification, carrying out structural processing on the task information. The structuring process may be a process of mapping parameters and parameter values of each of the plurality of task objects. And if the parameter verification of the task object in the task object set fails, carrying out abnormal reminding.
According to the embodiment of the application, in parameter verification based on the matching of the object types with the parameter model, the parameter model is generated based on the verification rule matched with the object types, so that corresponding rules can be flexibly applied to verify different types of task objects, parameters of various task objects can be effectively checked, unnecessary processing steps and labor cost are reduced, the speed and efficiency of data processing are improved, and the condition that verification is inaccurate or cannot be performed due to different object types is avoided.
FIG. 3 shows a schematic diagram of generating a parametric model according to an embodiment of the application.
As shown in fig. 3, a target parameter template 302 matching the object type may be determined from a pre-configured parameter template library 301.
The parameter template library 301 may include a plurality of parameter templates, which may include a plurality of fields for different object types.
For example, the plurality of fields may include, for example, but not limited to, model assessment task names, model types, model parameters, and the like, for the object type being model. Model parameters may include, for example, but are not limited to, model names, model unique identifiers, model superparameters, such as top_k, top_ p, temperature, and the like. The plurality of fields may include, for example, but not limited to, model service assessment task name, service type, and service parameters, etc., for the object type to be serviced. The service parameters may be, for example, a service name, a service base web address, keys required to access the service, a version of a model associated with the service, etc.
Based on constraints on the target fields in the target parameter template 302, a verification rule 303 is determined that matches the object type. A parametric model 304 is generated from the target parametric template 302 and the verification rules 303 matching the object type.
For example, the constraint on model names may be a combination of strings and text. The check rule 303 may be a value corresponding to a model name field, a rule that needs to conform to a combination of a character string and text, or the like. The constraint on the key required to access the service may be in the format of a string and length X, etc. The verification rule 303 may be a value corresponding to a key field required for accessing a service, a rule that needs to conform to a string format and a string length, and the like.
The target parameter templates are screened from the parameter template library, and the verification rule is determined based on constraint conditions on fields in the target parameter templates, so that the accuracy and consistency of data processing can be improved, and task information is ensured to meet expected formats and requirements. In addition, the task item creation process can be standardized, errors and abnormal conditions are reduced, the data quality is improved, and reliable basis is provided for subsequent analysis and decision. In addition, the stability and maintainability of the system can be enhanced, the problem can be positioned and solved quickly, the system is suitable for different service scene requirements, and the expandability is strong.
According to an embodiment of the present application, the structuring of the task information with respect to operation S230 shown in fig. 2 described above may include an operation of assigning a variable of a predetermined structure using the task information.
Illustratively, the predetermined structure may be a predefined structured structure, for example, a variable name, a variable type, or the like may be predefined.
The task information may also include data associated with the task object.
The data associated with the task object may be assigned to the corresponding variable of the predetermined structure on a field-by-field basis.
For example, when the data associated with the task object is assigned one by one according to a predetermined structure, data type conversion and data format conversion, such as list and structure data structuring into character string data, are required for data storage. Such as strings, JSON data, are structured into structural data for data manipulation. The strings are split into lists.
Based on the preset structure body, the task information is utilized to assign the variables of the preset structure body, so that the accuracy and consistency of data can be ensured, the operation flow is standardized, and the quality and reliability of the data are improved.
FIG. 4 illustrates a flow chart of a task item creation method according to another embodiment of the application.
According to another embodiment of the present application, as shown in fig. 4, the task item creation method may include operations S401 to S407.
In operation S401, it is determined whether the task information meets a predetermined format requirement. In case it is determined that the task information does not meet the predetermined format requirement, operation S402 is performed. In the case where it is determined that the task information meets the predetermined format requirement, operation S404 is performed.
In operation S402, a first exception class is generated.
In operation S403, the first exception class is processed to obtain a first error response.
In operation S404, it is determined whether the object type of the task object is a predetermined type. In case it is determined that the object type of the task object is not a predetermined type, operation S406 is performed. In case that it is determined that the object type of the task object is a predetermined type, operation S405 is performed.
In operation S405, parameters of a task object are verified based on a parameter model matched with the object type.
In operation S406, a second exception class is generated.
In operation S407, the second exception class is processed to obtain a second error response.
In this embodiment, the first exception class is generated when the task information does not meet the predetermined format requirement by capturing a statement in the code during execution of the code. The abnormal format of the first abnormal class can be analyzed, and the specific reason for generating the abnormal format is determined. According to the specific reason of abnormal format generation, a first error response containing format error information is constructed.
The second exception class is generated when the object type of the task object is not a predetermined type by capturing statements in the code during execution of the code. The abnormality type, the abnormality message and the context information of the occurrence of the abnormality of the second abnormality class may be parsed to determine the specific cause of the occurrence of the second abnormality. And constructing a second error response containing error information according to the specific reason of the second abnormality.
Note that, the operations S404 to S407 are operations for any task object in the task object set. Since the judgment is made for the object type of each task object, the abnormal condition of which object type of the specific task object is not the predetermined type can be accurately positioned, thereby ensuring the stability of the system and the user experience. Under the condition that the format is determined to be not abnormal, the parameter model is further matched for parameter accurate verification, so that the parameters are ensured to be correct in format, and the requirements of rules are met in terms of semantics and business logic, thereby being beneficial to improving the accuracy and reliability of data and preventing system faults or business faults and the like caused by parameter errors.
According to another embodiment of the present application, the task item creation method may further include an operation of determining an abnormal parameter of the target task object in the case where it is determined that the parameter verification of the target task object exists in the task object set is not passed, in addition to the operations S210 to S240 shown in fig. 2. Error information including an anomaly parameter is generated.
In the embodiment of the present application, the abnormal parameter may be a parameter that does not conform to the verification rule. The error information of the abnormal parameter may include a specific cause or the like that does not conform to the verification rule.
Because the abnormal parameters of the target task object are determined and error information comprising the abnormal parameters is generated, the problem can be accurately positioned, particularly, aiming at the conditions of complex parameter data structure, various formats and complex parameter verification logic, the abnormal prompt can be focused, the convenience of problem detection is improved, the abnormal can be conveniently and rapidly detected and repaired, the stability and the robustness of the system are improved, and meanwhile, personalized error prompt is provided for a user, and the user experience is enhanced.
According to yet another embodiment of the present application, the predetermined structure may further comprise a nested structure. The nested structure body comprises different fields with the grades from small to large or from large to small, and the fields have dependency relations. After the task information is structured, if it is determined that the structured task information is a nested structure, the structured task information may be checked again, and if variables of each level in the nested structure pass the verification, a target task item of the target task may be recorded in the database.
For example, for task information of the structuring process of the nested structure, the numerical value range of the variable of each level and/or comma distinguishing character string conversion operation of the variable of each level into a list and the dependency relationship of the variable between adjacent levels can be recursively verified based on the verification rule, the variable of verification failure and error information thereof are recorded, and the error information list is returned.
Because the second accurate verification is carried out on the aimed nested structure body, the correctness of each nested field can be more carefully checked, and the integrity and the accuracy of complex data are ensured. The method not only can improve the data quality, but also can enhance the robustness of the system, is beneficial to quickly positioning potential errors and optimizes the processing efficiency of complex business processes.
According to an embodiment of the present application, for operation S240 shown in fig. 2 described above, recording the target task item of the target task in the database based on the task information of the structuring process may include converting the task information of the structuring process into the serialization information and recording in the database.
The structured data is converted into the universal serialization format, so that the data sharing between different programming languages and platforms can be facilitated, and the data exchange between different systems or services can be facilitated.
Based on the task item creation method, the application also provides a task item query method. The task item query method will be described in detail below with reference to fig. 5.
FIG. 5 illustrates a flow chart of a task item query method according to an embodiment of the application.
As shown in FIG. 5, the task item query method may include operation S510.
In response to the query request for the task to be queried, a target task item matching the query request is queried from the database in operation S510.
In this embodiment, the database may include a plurality of task items corresponding to a plurality of tasks, respectively. Any one of the plurality of task items of the plurality of tasks is created according to the task item creation method described above. Reference may be made to the above description for a task item creation method, and this will not be repeated.
The task to be queried may include, but is not limited to, an assessment task, a dialogue task, and the like. The target task may or may not be identical to the target task described above.
The query request may include a query field, format requirements, etc.
For example, a field type may be determined from the query field, and then task items belonging to the field type may be matched from the database based on the field type, resulting in a target task item.
Because the task items are created in the database in advance, the query request for the query task can accurately and quickly query the target task item.
FIG. 6 illustrates a flow chart of a task item query method according to another embodiment of the application.
In the process of implementing the embodiment of the application, it is also found that when the data query is performed, the field information of the task item in the database is defined in advance, and when the task item is returned, if a field needs to be newly added in the structure of the task item, but the field does not exist in the database, the structure of the database needs to be changed, however, the structure of the database needs to be changed, the existing application may be affected, the code and interrupt service need to be comprehensively updated, and the performance is reduced, such as table locking, blocking, index reconstruction and the like.
Based on this, as shown in fig. 6, in this embodiment, the task item query method may include operations S601 to S604.
In operation S601, it is determined whether a task item matching a task to be queried is available using a task name field in a plurality of fields. In a case where it is determined that a task item matching the task to be queried cannot be obtained using the task name field of the plurality of fields, operations S602 to S604 are performed. In case it is determined that a task item matching the task to be queried is available using the task name field of the plurality of fields, operation S604 is performed.
In operation S602, a homonymous variable corresponding to a virtual field is added in a predetermined structure.
In operation S603, assignment is performed on the homonymous variables based on the task information of the target task, to obtain a target structure.
In operation S604, a target task item matching the query request is obtained.
In the embodiment of the application, the target task item matched with the query request can be obtained based on the variable in the target structure body.
The preset structural body corresponds to the variable names and types in the database one by one, so that the task item creation operation can be completed according to the variable names and types in the task item creation process.
In special cases, the query needs to return more data to meet the functional needs, and can be processed using the form of virtual fields, where virtual fields need to be added to the data table of the database, and homonymous variables need to be added to the predetermined structure. In the process of data query, virtual fields of a data table are treated as standard fields of the data table, and the variables with the same names are assigned according to task information of a target task.
For example, for a model performance evaluation task, a data table for the model and a data table for the service may be created by the task item creation method described above. The detailed information of the model is contained in the data table of the model, and comprises specific information such as a unique model identifier, a model name, a model appearance design and the like, the detailed data of the model can be obtained only by associating the unique model identifier in the data table of the service, and the detailed data of the model can be associated and inquired in the form of virtual fields in the data table of the service.
Because the task item matched with the task to be queried cannot be obtained by utilizing the task name field in the fields, namely, under a specific scene, by adding the homonymous variable corresponding to the virtual field in the preset structure body, the virtual field can be used for transmitting and using additional data under the condition of not changing the database structure, the query flexibility is enhanced, and the data model can be conveniently expanded under the specific scene.
In the process of realizing the embodiment of the application, the method and the device also find that, because the serialized data is stored in the database to facilitate data sharing between different programming languages and platforms or data exchange between different systems or services, and the like, the target task item matched with the query request is obtained based on the variable in the target structure body, and the method and the device can comprise the operations of determining the target variable matched with the query request from the variable in the target structure body, and serializing the value of the target variable into a preset format to obtain the target task item.
For example, the model structure and model parameters with the model unique identifier of 123 are queried, the variables of the model unique identifier, the model structure and the model parameters can be found from the structural body, and after the model unique identifier of 123 is verified, the variables are serialized into a predetermined format, so as to obtain the target task item containing the model structure and the model parameters.
The value of the target variable is advantageously stored in a file or transmitted to other programs via a network, due to serialization of the value into a predetermined format.
By the embodiment of the application, the software engineering code can be operated and used more safely, stably and quickly.
Based on the task item creation method, the application also provides a task item creation device. The device will be described in detail below in connection with fig. 7.
Fig. 7 shows a block diagram of a task item creation device according to an embodiment of the present application.
As shown in fig. 7, the task item creation device 700 of this embodiment includes a determination module 710, a verification module 720, a processing module 730, and a recording module 740.
The determining module 710 is configured to determine task information, including a set of task objects, in response to a creation request of a target task. In an embodiment, the determining module 710 may be configured to perform the operation S210 described above, which is not described herein.
The verification module 720 is configured to, when determining that the task information meets the predetermined format requirement, verify, for any task object in the task object set, a parameter of the task object based on a parameter model matched with the object type when the object type of the task object is a predetermined type, where the parameter model is generated based on a verification rule matched with the object type. In an embodiment, the verification module 720 may be configured to perform the operation S220 described above, which is not described herein.
The processing module 730 is configured to perform a structuring process on the task information when it is determined that the parameter of any task object in the task object set passes the verification. In an embodiment, the processing module 730 may be configured to perform the operation S230 described above, which is not described herein.
The recording module 740 is configured to record a target task item of a target task in the database based on the task information of the structuring process. In an embodiment, the recording module 740 may be configured to perform the operation S240 described above, which is not described herein.
According to an embodiment of the present application, the task item creation device 700 further includes a template determination module, a rule determination module, and a model generation module. The template determining module is used for determining a target parameter template matched with the object type from a pre-configured parameter template library, the parameter template library comprises a plurality of parameter templates, the parameter templates aim at different object types, and the parameter templates comprise a plurality of fields. The rule determining module is used for determining a verification rule matched with the object type based on constraint conditions of the target field in the target parameter template. The model generation module is used for generating a parameter model according to the target parameter template and the verification rule matched with the object type.
According to the embodiment of the application, the task information is structured, and the task information can be used for assigning the variable of the preset structure body based on the preset structure body.
According to an embodiment of the present application, the task item creation device 700 further includes a first exception module, a first processing module, a second exception module, and a second processing module. The first exception module is used for generating a first exception class under the condition that the task information is determined to be not in accordance with the predetermined format requirement. The first processing module is used for processing the first exception class to obtain a first error response. The second exception module is configured to generate, for any task object in the task object set, a second exception class if it is determined that the task information meets a predetermined format requirement and if an object type of the any task object is not a predetermined type. And the second processing module is used for processing the second abnormal class to obtain a second error response.
According to an embodiment of the present application, the task item creation device 700 further includes an abnormal parameter determination module and an information generation module. The abnormal parameter determining module is used for determining abnormal parameters of the target task object under the condition that the parameter verification of the target task object exists in the task object set and is not passed. The information generation module is used for generating error information comprising abnormal parameters.
Any of the determination module 710, the verification module 720, the processing module 730, and the recording module 740 may be combined in one module to be implemented, or any of the modules may be split into a plurality of modules according to an embodiment of the present application. Or at least some of the functionality of one or more of the modules may be combined with, and implemented in, at least some of the functionality of other modules. At least one of the determination module 710, the verification module 720, the processing module 730, and the recording module 740 may be implemented at least in part as hardware circuitry, such as a Field Programmable Gate Array (FPGA), a Programmable Logic Array (PLA), a system on a chip, a system on a substrate, a system on a package, an Application Specific Integrated Circuit (ASIC), or as hardware or firmware in any other reasonable manner of integrating or packaging the circuitry, or as any one of or a suitable combination of any of the three. Or at least one of the determination module 710, the verification module 720, the processing module 730, and the logging module 740 may be at least partially implemented as a computer program module which, when executed, may perform the corresponding functions.
Based on the task item query method, the application also provides a task item query device. The device will be described in detail below in connection with fig. 8.
FIG. 8 shows a block diagram of a task item querying device, according to an embodiment of the application.
As shown in FIG. 8, the task item querying device 800 of this embodiment includes a query module 810.
The query module 810 is configured to query, in response to a query request for a task to be queried, a target task item matching the query request from a database, where the database includes a plurality of task items corresponding to a plurality of tasks, respectively, where any one of the plurality of task items of the plurality of tasks is created according to the method described above. In an embodiment, the query module 810 may be configured to perform the operation S510 described above, which is not described herein.
According to an embodiment of the present application, the task item has a predetermined structure form, and the predetermined structure includes a plurality of fields. The task item query device 800 further includes a variable adding module, an assigning module, and a task item obtaining module. The variable adding module is used for adding the homonymy variable corresponding to the virtual field in the preset structure body under the condition that the task name field in the multiple fields is not used for obtaining the task item matched with the task to be queried. The assignment module is used for assigning the same name variable based on the task information of the target task to obtain a target structure body. The task item obtaining module is used for obtaining a target task item matched with the query request based on the variable in the target structure body.
According to an embodiment of the application, a target task item matching a query request is obtained based on variables in a target structure, including determining a target variable matching the query request from the variables in the target structure. And serializing the values of the target variables into a preset format to obtain the target task item.
Any of the multiple modules in query module 810 may be combined in one module or any of the modules may be split into multiple modules, according to embodiments of the present application. Or at least some of the functionality of one or more of the modules may be combined with, and implemented in, at least some of the functionality of other modules. According to embodiments of the application, at least one of the query modules 810 may be implemented at least in part as a hardware circuit, such as a Field Programmable Gate Array (FPGA), a Programmable Logic Array (PLA), a system-on-chip, a system-on-a-substrate, a system-on-a-package, an Application Specific Integrated Circuit (ASIC), or as hardware or firmware in any other reasonable manner of integrating or packaging the circuit, or as any one of or a suitable combination of any of three implementations of software, hardware, and firmware. Or at least one of the query modules 810 may be at least partially implemented as a computer program module that, when executed, performs the corresponding function.
FIG. 9 illustrates a block diagram of an electronic device suitable for implementing a task item creation method and a task item query method in accordance with an embodiment of the present application.
As shown in fig. 9, an electronic device 900 according to an embodiment of the present application includes a processor 901 that can perform various appropriate actions and processes according to a program stored in a Read Only Memory (ROM) 902 or a program loaded from a storage section 908 into a Random Access Memory (RAM) 903. The processor 901 may include, for example, a general purpose microprocessor (e.g., a CPU), an instruction set processor and/or an associated chipset and/or a special purpose microprocessor (e.g., an Application Specific Integrated Circuit (ASIC)), or the like. Processor 901 may also include on-board memory for caching purposes. Processor 901 may include a single processing unit or multiple processing units for performing the different actions of the method flows according to embodiments of the application.
In the RAM 903, various programs and data necessary for the operation of the electronic device 900 are stored. The processor 901, the ROM 902, and the RAM 903 are connected to each other by a bus 904. The processor 901 performs various operations of the method flow according to an embodiment of the present application by executing programs in the ROM 902 and/or the RAM 903. Note that the program may be stored in one or more memories other than the ROM 902 and the RAM 903. The processor 901 may also perform various operations of the method flow according to embodiments of the present application by executing programs stored in one or more memories.
According to an embodiment of the application, the electronic device 900 may also include an input/output (I/O) interface 905, the input/output (I/O) interface 905 also being connected to the bus 904. The electronic device 900 may also include one or more of an input portion 906 including a keyboard, a mouse, etc., an output portion 907 including a display such as a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), etc., and a speaker, etc., a storage portion 908 including a hard disk, etc., and a communication portion 909 including a network interface card such as a LAN card, a modem, etc., connected to an input/output (I/O) interface 905. The communication section 909 performs communication processing via a network such as the internet. The drive 910 is also connected to an input/output (I/O) interface 905 as needed. Removable media 911 such as magnetic disks, optical disks, magneto-optical disks, semiconductor memories, and the like are assembled on the drive 910 as needed so that a computer program read therefrom is assembled into the storage section 908 as needed.
The present application also provides a computer-readable storage medium that may be included in the apparatus/device/system described in the above embodiments, or may exist alone without being assembled into the apparatus/device/system. The computer-readable storage medium carries one or more programs which, when executed, implement methods in accordance with embodiments of the present application.
According to embodiments of the application, the computer-readable storage medium may be a non-volatile computer-readable storage medium, which may include, for example, but is not limited to, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. For example, according to embodiments of the application, the computer-readable storage medium may include ROM 902 and/or RAM 903 and/or one or more memories other than ROM 902 and RAM 903 described above.
Embodiments of the present application also include a computer program product comprising a computer program containing program code for performing the method shown in the flowcharts. The program code means for causing a computer system to carry out the methods provided by embodiments of the present application when the computer program product is run on the computer system.
The above-described functions defined in the system/apparatus of the embodiment of the present application are performed when the computer program is executed by the processor 901. The systems, apparatus, modules, units, etc. described above may be implemented by computer program modules according to embodiments of the application.
In one embodiment, the computer program may be based on a tangible storage medium such as an optical storage device, a magnetic storage device, or the like. In another embodiment, the computer program may also be transmitted, distributed, and downloaded and assembled from the removable media 911 via the communication section 909, as signals on a network medium. The computer program may comprise program code that is transmitted using any appropriate network medium, including but not limited to wireless, wireline, etc., or any suitable combination of the preceding.
In such an embodiment, the computer program may be downloaded and assembled from the network via the communication portion 909 and/or assembled from the removable medium 911. The above-described functions defined in the system of the embodiment of the present application are performed when the computer program is executed by the processor 901. The systems, devices, apparatus, modules, units, etc. described above may be implemented by computer program modules according to embodiments of the application.
According to embodiments of the present application, program code for carrying out computer programs provided by embodiments of the present application may be written in any combination of one or more programming languages, and in particular, such computer programs may be implemented in high-level procedural and/or object-oriented programming languages, and/or in assembly/machine languages. Programming languages include, but are not limited to, such as Java, c++, python, "C" or similar programming languages. The program code may execute entirely on the user's computing device, partly on the user's device, partly on a remote computing device, or entirely on the remote computing device or server. In the case of remote computing devices, the remote computing device may be connected to the user computing device through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computing device (e.g., connected via the Internet using an Internet service provider).
The flowcharts and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present application. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams or flowchart illustration, and combinations of blocks in the block diagrams or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
Those skilled in the art will appreciate that the features recited in the various embodiments of the application can be combined and/or combined in a variety of ways, even if such combinations or combinations are not explicitly recited in the present application. In particular, the features described in the various embodiments of the application may be combined and/or combined in various ways without departing from the spirit and teachings of the application. All such combinations and/or combinations fall within the scope of the application.
The embodiments of the present application are described above. These examples are for illustrative purposes only and are not intended to limit the scope of the present application. Although the embodiments are described above separately, this does not mean that the measures in the embodiments cannot be used advantageously in combination. Various alternatives and modifications can be made by those skilled in the art without departing from the scope of the application, and such alternatives and modifications are intended to fall within the scope of the application.