CN108615136B

CN108615136B - Task flow control method and system

Info

Publication number: CN108615136B
Application number: CN201611148272.1A
Authority: CN
Inventors: 杨建平; 商云涛; 贾丽琼; 熊兴玉
Original assignee: Sinosoft Co ltd; Development & Research Center Of China Geological Survey Bureau
Current assignee: Sinosoft Co ltd; Development & Research Center Of China Geological Survey Bureau
Priority date: 2016-12-13
Filing date: 2016-12-13
Publication date: 2022-04-19
Anticipated expiration: 2036-12-13
Also published as: CN108615136A

Abstract

The present disclosure relates to a method and a system for controlling a task flow, wherein the system comprises: the task module is used for acquiring a task flow control request and generating a task loading instruction; the metadata management module is used for receiving and loading the initial task according to the task loading instruction and acquiring task description information of the initial task from the task resource module; according to the task description information, a task type, a task step relation and a related step list of the task to be executed are constructed and returned to the task module; the step module is used for receiving the initialization step instruction from the task module, constructing and executing each step of the task to be executed according to the initialization step instruction; and the task resource module is used for storing the task description information and saving and/or updating each step and task state in the process of executing the task to be executed. The system solves the problem that the flow control of the traditional workflow products must be fixed, and when the sequence of each step in a task or the like changes, the task flow does not need to be reconfigured and the task flow control system does not need to be restarted.

Description

Task flow control method and system

Technical Field

The present disclosure relates to the field of task flow control technologies, and in particular, to a task flow control method and system.

Background

Workflow (Workflow) refers to "automation of a portion or the whole of a business process in a computer application environment". The method is an abstract and general description of the workflow and the business rules among the operation steps of the workflow. In computers, workflows are part of Computer Supported Collaborative Work (CSCW).

Workflow technology originated from research work in the mid-1970's office automation field, but the workflow thought should have emerged earlier, and the idea of workflow automation using information technology was clearly expressed by Fritz Nordsieck in 1968. The work related to workflow in the 1970 s included: the prototype system SCOOP developed by Michael D. Zisman, the university of Pennsylvania, the OfficeTalk series test system developed by Clarence A. Ellis and Gary J. Nutt et al, the research center of Schleparoalto, and the "monitoring software failure reporting" program on the ARPANET developed by Anatol Holt and Paul Cashman. The systems developed by SCOOP, official and anatool Holt all employ some variant of Petri nets for flow modeling. Among them, SCOOP and Officetalk systems, not only mark the beginning of workflow technology, but are also the earliest office automation systems.

In the 1970 s people were full of intense optimistic emotions on workflow technology, and researchers generally believed that new technology could bring about dramatic improvements in office efficiency, yet this desire eventually fell to the forefront. People observe the phenomenon that a successful organization often creatively breaks the standard office flow at a proper time; the introduction of workflow technology enables people to only obey a fixed flow, which ultimately leads to low office efficiency and people's discomfort to the technology. The technical reasons for workflow technology failure in the 1970 s included: the use of personal computers in offices has not been socially accepted, network technology is not widespread, and developers have not been able to understand the requirements and drawbacks of groupware technology.

The development of commercial systems containing workflow features began between 1983 and 1985, with early commercial systems mainly coming from the image processing and email fields. Image processing many times requires the circulation and tracking of images, and the workflow just meets the requirement; the enhanced email system also adopts the idea of workflow to improve the original point-to-point email flow into the flow according to a certain flow. Only a few of these early workflow systems have achieved success.

After the 1990 s, the related technical conditions became mature, and the development and research of the workflow system entered a new trend. It was investigated that there were over 200 software claims to support workflow management or possess workflow features by 1995. Workflow technology is used in the telecommunications industry, software engineering, manufacturing, financial, banking, scientific testing, health care, shipping and office automation.

In 8 months 1993, the workflow management alliance (WfMC), an industry organization for workflow technology standardization, was established. In 1994, the workflow management alliance released a workflow reference model for interoperation between workflow management systems and successively established a series of industry standards.

Academic research on workflow technology is also active, many prototype systems are developed in laboratories, and a large number of papers are written after people discuss workflow technology from various aspects such as workflow models, architectures, transactions, adaptability, exceptions, security, language, formalization, correctness verification, resource management, development process, and the like.

Despite the advances made in workflow technology, the theoretical basis has not been sufficiently studied. The existing workflow management system cannot be compared with a database management system in terms of function, reliability and robustness.

After 2000, with the rise of Web services, various standardization organizations have established Web services standards related to workflow technologies, such as XLANG, WSFL (WSFL is a language formulated by IBM and used for describing Web services flows), and so on. In 2002, 8, IBM, Microsoft, and others have submitted and published BPEL (Business Process Execution Language) specifications for corporate enterprises.

Currently, popular workflow products include open source workflows such as JBPM (Java Business Process Management) and activity (one of Android components), and commercial versions of workflow products such as IBM and microsoft. An activity workflow product can be adopted to solve the task flow control problem. The conventional workflow products which can be used for task flow control are mainly realized based on a fixed auditing flow, and the flow control must be fixed, so that the use requirements are difficult to meet.

Disclosure of Invention

In view of this, the present disclosure provides a method and a system for task flow control.

According to an aspect of the present disclosure, there is provided a task flow control system including:

the task module is used for acquiring a task flow control request and generating a task loading instruction;

the metadata management module is used for receiving the task loading instruction from the task module, loading an initial task according to the task loading instruction, and acquiring task description information of the initial task from a task resource module; constructing a task type, a task step relation and a related step list of the task to be executed according to the task description information; returning the task type, the task step relation and the related step list to the task module;

the step module is used for receiving an initialization step instruction from the task module, wherein the initialization step instruction comprises the task description information, the task type, the task step relation and a related step list, and each step of the task to be executed is constructed and executed according to the initialization step instruction;

and the task resource module is used for storing the task description information and saving and/or updating each step and task state of each task to be executed in the process of executing each step of the task to be executed.

In a possible implementation manner, the metadata management module is further configured to obtain task description information of the initial task from the task resource module when the task flow control request is a request for executing a next task, a request for suspending a task, a request for completing a task, or a request for changing a task, where the task description information includes task basic information, a task state, a task type, and step information.

In a possible implementation manner, the metadata management module is further configured to create task description information of the initial task when the task flow control request is a task creation request, where the task description information includes task basic information, a task state, a task type, and step information, and send the task description information of the initial task to the task resource module for storage.

In a possible implementation manner, the metadata management module is further configured to reconstruct the task and send task description information of the reconstructed task to the task resource module for storage when the task flow control request is the task change request; and returning task description information of the reconstructed task to the task module; and the task module is also used for controlling the cycle execution of the reconstructed task according to the task description information of the reconstructed task.

In one possible implementation, the system further includes: and the file/piece data transmission module is used for controlling data transmission, copying or distribution among the steps of the executed task in the process of executing the task.

In one possible implementation, the system further includes: and the task batch management module is used for calling corresponding tasks from the task module according to the task batch request and executing the called tasks in batches.

In one possible implementation, the system further includes: and the task service interface is used for returning the step corresponding to the task to be executed to the step module after receiving the step calling request sent by the step module in the process of constructing the task to be executed by the step module.

According to another aspect of the present disclosure, there is provided a task flow control method including:

the task module acquires a task flow control request and generates a task loading instruction;

the metadata management module receives the task loading instruction from the task module, loads an initial task according to the task loading instruction, and acquires task description information of the initial task from a task resource module; constructing a task type, a task step relation and a related step list of the task to be executed according to the task description information; returning the task type, the task step relation and the related step list to the task module;

the step module receives an initialization step instruction from the task module, wherein the initialization step instruction comprises the task description information, the task type, the task step relation and a related step list, and each step of the task to be executed is constructed and executed according to the initialization step instruction;

and the task resource module stores the task description information and saves and/or updates each step and task state of each task to be executed in the process of executing each step of the task to be executed.

In a possible implementation manner, when the task flow control request is a request for executing a next task, a request for suspending a task, a request for completing a task, or a request for changing a task, the metadata management module obtains task description information of the initial task from the task resource module, where the task description information includes task basic information, a task state, a task type, and step information.

In a possible implementation manner, in a case that the task flow control request is a request for creating a task, the metadata management module creates task description information of the initial task, where the task description information includes task basic information, a task state, a task type, and step information, and sends the task description information of the initial task to the task resource module for storage.

In a possible implementation manner, in the case that the task flow control request is the task change request, the metadata management module reconstructs task information and sends task description information of the reconstructed task to the task resource module for storage; and returning task description information of the reconstructed task to the task module; and the task module controls the cycle execution of the reconstructed task according to the task description information of the reconstructed task.

In one possible implementation, the method further includes: the file/piece data transmission module controls data transmission, copying or distribution among steps of the executed task in the process of executing the task.

In one possible implementation, the method further includes: and the task batch management module calls corresponding tasks from the task module according to the task batch request and executes the called tasks in batches.

In one possible implementation, the method further includes: and in the process of constructing the task to be executed by the step module, the task service interface returns the step corresponding to the task to be executed to the step module after receiving the step calling request sent by the step module.

According to another aspect of the present disclosure, there is provided a non-transitory computer-readable storage medium having instructions therein, which when executed by a processor of a terminal and/or a server, enable the terminal and/or the server to perform a task flow control method, the method including: the task module acquires a task flow control request and generates a task loading instruction;

The task flow control method and the task flow control system solve the problem that the conventional workflow product flow control needs to be fixed, and can directly update the task without reconfiguring the task flow or restarting the task flow control system when the task is changed or the sequence of each step in the task is changed.

Other features and aspects of the present disclosure will become apparent from the following detailed description of exemplary embodiments, which proceeds with reference to the accompanying drawings.

Drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate exemplary embodiments, features, and aspects of the disclosure and, together with the description, serve to explain the principles of the disclosure.

FIG. 1 shows a schematic diagram of a task flow control system according to an embodiment of the present disclosure;

FIG. 2 shows a schematic diagram of an example of a task flow control system according to an embodiment of the present disclosure;

FIG. 3 illustrates a block diagram of an example of a task flow control system according to an embodiment of the present disclosure;

FIG. 4 illustrates a flow diagram of a task flow control method according to an embodiment of the present disclosure;

FIG. 5 illustrates a flowchart of a task flow control method executing a next task according to an embodiment of the present disclosure;

FIG. 6 illustrates a flow diagram of a task flow control method aborting a task according to an embodiment of the present disclosure;

FIG. 7 illustrates a flow diagram of a task flow control method suspending tasks according to an embodiment of the present disclosure;

FIG. 8 illustrates a flow diagram of a task flow control method completing a task according to an embodiment of the present disclosure;

FIG. 9 illustrates a flow diagram of a task flow control method creating a task according to an embodiment of the present disclosure;

FIG. 10 illustrates a flow diagram of a task change by a task flow control method according to an embodiment of the present disclosure;

FIG. 11 is a block diagram illustrating a task flow control device according to an exemplary embodiment.

Detailed Description

Various exemplary embodiments, features and aspects of the present disclosure will be described in detail below with reference to the accompanying drawings. In the drawings, like reference numbers can indicate functionally identical or similar elements. While the various aspects of the embodiments are presented in drawings, the drawings are not necessarily drawn to scale unless specifically indicated.

The word "exemplary" is used exclusively herein to mean "serving as an example, embodiment, or illustration. Any embodiment described herein as "exemplary" is not necessarily to be construed as preferred or advantageous over other embodiments.

Furthermore, in the following detailed description, numerous specific details are set forth in order to provide a better understanding of the present disclosure. It will be understood by those skilled in the art that the present disclosure may be practiced without some of these specific details. In some instances, methods, means, elements and circuits that are well known to those skilled in the art have not been described in detail so as not to obscure the present disclosure.

In the geological survey industry, geological information related to geological survey needs to be subjected to secret-related cleaning, and the geological information can comprise data such as pictures, documents, maps and geological structure charts. And the local secret-related cleaning refers to the process of carrying out secret-related point marking on geological information related to geological survey. In addition, in the labeling process, the labeling of the confidential points needs to be audited, such as self-checking, mutual inspection, spot inspection and the like, so as to ensure the accuracy of the labeling of the geological information confidential points.

At present, an activity workflow product can be adopted to solve the problem of flow control of a secret-related cleaning task. The conventional workflow products which can be used for adjusting secret-related cleaning are mainly realized based on a fixed auditing process, and the control of the auditing process of geological information secret-related points must be fixed. However, the uncertainty of the self-checking, mutual-checking and sampling-checking processes in the auditing process is large. For example: in the operation process, the change of the flow sequence such as self-checking, mutual inspection, sampling inspection and the like and the change of task steps in the flow exist. The existing work flow products are difficult to meet the use requirements of secret cleaning.

Example 1

Fig. 1 shows a schematic diagram of a task flow control system according to an embodiment of the present disclosure, and as shown in fig. 1, the system may include a task module 101, a metadata management module 102, a step module 103, and a task resource module 104.

The task module 101 is used for acquiring a task flow control request and generating a task loading instruction;

in this embodiment, the task flow control request may include a execute next task request, an abort task request, a pause task request, a complete task request, a change task request, a create task request, and a change task request.

The metadata management module 102 is configured to receive the task loading instruction from the task module, load an initial task according to the task loading instruction, and obtain task description information of the initial task from a task resource module; constructing a task type, a task step relation and a related step list of the task to be executed according to the task description information; and returning the task type, the task step relation and the related step list to the task module.

A step module 103, configured to receive an initialization step instruction from the task module 101, where the initialization step instruction includes the task description information, the task type, the task step relationship, and a related step list, and construct and execute each step of the task to be executed according to the initialization step instruction.

And the task resource module 104 is configured to store the task description information, and store and/or update each step and task state of each to-be-executed task in the process of executing each step of the to-be-executed task.

In a possible implementation manner, the metadata management module 102 is further configured to acquire task description information of the initial task from the task resource module 104 when the task flow control request is a request for executing a next task, a request for suspending a task, a request for completing a task, or a request for changing a task, where the task description information includes basic task information, a task state, a task type, and step information.

In a possible implementation manner, the metadata management module 102 is further configured to create task description information of the initial task when the task flow control request is a task creation request, where the task description information includes task basic information, a task state, a task type, and step information, and send the task description information of the initial task to the task resource module 104 for storage.

In a possible implementation manner, the metadata management module 102 is further configured to reconstruct the task and send task description information of the reconstructed task to the task resource module for storage when the task flow control request is the task change request; and returns task description information of the reconstructed task to the task module 101. The task module 101 is further configured to control the cycle execution of the reconstructed task according to the task description information of the reconstructed task.

In a possible implementation manner, the system further includes: and a file/piece data transmission module 105 for controlling data transmission, copying or distribution between steps of the executed task in the process of executing the task.

In a possible implementation manner, the system further includes: and the task batch management module 106 is configured to call the corresponding tasks from the task module according to the task batch request, and execute the called tasks in batches.

In a possible implementation manner, the system further includes: and the task service interface 107 is configured to, in the process of constructing the to-be-executed task by the step module, return the step corresponding to the to-be-executed task to the step module after receiving the step invocation request sent by the step module.

It should be noted that, although the task flow control system is described above by taking embodiment 1 as an example, those skilled in the art will understand that the present disclosure should not be limited thereto. In fact, the user can flexibly set each functional module according to personal preference and/or actual application scene as long as the technical scheme of the disclosure is met.

The task flow control system provided by the disclosure solves the problem that the conventional workflow product flow control needs to be fixed, and can directly update the task without reconfiguring the task flow or restarting the task flow control system when the task is changed or the sequence of each step in the task is changed.

Example 2

FIG. 2 shows a schematic diagram of an example of a task flow control system according to an embodiment of the present disclosure. FIG. 3 shows a block diagram of an example of a task flow control system according to an embodiment of the present disclosure. In this embodiment, a task flow control system is described by taking a task flow engine in a confidential task cleaning system as an example. The security-related task can be a task for adjusting security and cleaning.

As shown in fig. 2, the task flow engine may include: a task engine 201, a metadata management engine 202, a step engine 203, a task resource engine 204, a file/piece data transmission engine 205, a task batch management engine 206 and a task related services interface 207.

A plurality of Task processing classes (tasks) may be included in the Task engine 201 (see description of the Task module 101 in the above embodiment). The task engine 201 is responsible for controlling task processes, including creating tasks, executing next tasks, completing tasks, suspending tasks and other related process controls; and the task loading instruction is used for acquiring and generating a task loading instruction according to the task flow control request.

In this embodiment, the task flow control request is issued by the developer. As shown in fig. 3, the Task (Task) consists of at least one Step (Step). The steps are the most basic unit of the task flow, and the tasks consist of different steps so as to complete different types of tasks. The step of locally scheduling the task related to the secret clearance may include, for example, a step of issuing, a step of self-checking, a step of mutual checking, and a step of spot checking. The task engine 201 is responsible for running between different steps, including creation, suspension, continuation of a task, and execution of a next task.

The metadata management engine 202 (see description of the metadata management module 102 in the above embodiment) may obtain the task description information (TaskMeta). The metadata management engine 202 is responsible for storing basic information of tasks such as self-checking, mutual checking and sampling checking in the auditing process, storing and reading the basic information of steps corresponding to the tasks and the execution sequence of the task flow, and providing a related access interface of a data resource library. The functions and operations of the metadata management engine 202 may include: acquiring a task loading instruction from a task engine 201, loading an initial task according to the task loading instruction, and acquiring task description information of the initial task from a task resource engine 204; constructing a task type, a task step relation, a related step list and the like of the task to be executed according to the task description information; and returning the task type, the task step relationship, the related step list and the like to the task engine 201.

In this embodiment, as shown in fig. 3, the metadata management engine 202 is configured to obtain task description information of a task, where the task description information may include: task basic information (TaskBaseInfo), task state information (List < TaskStatus >), task type flow relation basic information (List < TaskType >), task type-to-task relationship (List < TaskTypeHopsMeta >), step-to-step relationship (List < TaskStepHopsMeta >), step metadata (List < StepMeta >), and the like. The metadata management engine 202 is responsible for basic construction of steps, including the step sequence among the steps and construction of data transmission channels, and returns the steps to the task engine 201 to complete the operation of the corresponding task.

A task step plug-in (stepplug) may be included in step engine 203 (see description of step module 103 in the above embodiment). The step engine 203 is configured to receive an initialization step instruction from the task engine 201, where the initialization step instruction includes task description information, a task type, a task step relationship, and a related step list, and constructs and cyclically executes steps of a task to be executed according to the initialization step instruction. Constructing steps corresponding to each task according to the basic information of the task, such as: step engine 203 may construct steps corresponding to the tasks to be executed: step 1, step 2 and step 3. The steps are the most basic units of the confidential task flow, one task flow is composed of a plurality of steps, and the composition and the execution sequence of the steps are controlled through a task flow engine.

In this embodiment, as shown in fig. 3, the steps may include a step process class (StepInterface), step description information (StepDataInterface), and a step process data interface (stepmainterface). The step processing class StepInterface is responsible for the operation of each step; step description information StepDataInterface is responsible for configuration and management of basic task data of task parameters, and is basic information of a local-level file and a local-level file; the step processing data interface StepMetaInterface is the basic metadata information of the step. The step processing data interface StepMetaInterface comprises basic parameter information such as a sending step, a self-checking step, a sampling step and a mutual checking step, wherein the basic parameter information comprises relevant information of step codes, a process, a task and a batch number. For example: step 1(Step _1) includes the basic metadata (stepmetadata _1) of Step 1 and the basic information (StepData _1) of the file/piece of Step 1. Step 2(Step _2) includes the basic metadata (stepmetadata _2) of Step 2 and the basic information (StepData _2) of the file/piece of Step 2.

A task resource library (taskdatabaserepetition) may be included in the task resource engine 204 (see description of the task resource module 104 in the above embodiment). The task resource engine 204 is responsible for the persistence of basic information of tasks, steps and the like, and provides storage and query of the basic information related to the tasks and the steps.

In this embodiment, as shown in fig. 3, the task resource engine 204 may include a resource library hierarchy, which is responsible for storing the execution information of the tasks and steps at each stage. The resource library may include a task resource library (task repository) and a step resource library (steprelation), and the task resource library is responsible for saving and reading basic information of the task. The step resource library is responsible for reading and storing the basic information of the steps. The task resource engine 204 may also include: < < interface > > (RepositoryCreateTaskRenameTask). The task resource engine 204 is also used to record data generated during the execution of the steps. The task resource engine 204 may also include a task information type (task database repoxystore delete) including a task basic information type (task database repoxystore delete), a task state type

(database reoxystrobyttaskstausdelegate) and step basic information type (database reoxystrobetstepdegate).

A data set (TransDataSet) may be included in the file/item data transfer engine 205 (see description of the file/item data transfer module 105 in the above embodiment). The file/piece data transmission engine 205 is responsible for data transmission between task steps, and data copying and distributing work between steps.

In this embodiment, as shown in fig. 3, the file/piece data transmission engine 205 may include a data set (TransDataSet) as a set of inter-step data transmission, the data set is a bidirectional list of data security, and the data set is composed of an Input (Input) part and an Output (Output) part, and is respectively responsible for inputting and outputting data of a step. The data set may be obtained from a profile data class (DataArchive) and an item data class (DataFile). File/piece data transfer engine 205 may also include an interface, namely, < < interface > > data set (TaskDataSet), which may include functions such as getData () and setData ().

A task batch class (TaskBatch) may be included within the task batch management engine 206 (see description of the task batch management module 105 in the embodiments above). The task batch management engine 206 is responsible for batch execution of tasks based on the task engine 201.

The task service interface 207 (see the description of the task service interface 107 in the above embodiment) includes a plurality of task function interfaces (TaskService). The task service interface 207 is responsible for providing relevant function interfaces for the task, and the function interfaces may include a task creation interface, an execution interface, a query interface, a pause interface and a delivery interface. The steps corresponding to the tasks can be stored in different functional interfaces, so that the step engine 203 can directly acquire the steps corresponding to the tasks to be executed, and the time for creating the steps is saved.

In a possible implementation manner, in a case that the task flow control request is any one of a request for executing a next task, a request for suspending a task, a request for completing a task, and a request for changing a task, the metadata management engine 202 acquires task description information of an initial task from the task resource engine 204, where the task description information includes task basic information, a task state, a task type, and step information.

In a possible implementation manner, in a case that the task flow control request is a create task request, the metadata management engine 202 creates task description information of an initial task, where the task description information includes task basic information, a task state, a task type, and step information, and sends the task description information of the initial task to the task resource engine 204 for storage.

In a possible implementation manner, in a case that the task flow control request is the task change request, the metadata management engine 202 reconstructs task information and sends task description information of the reconstructed task to the task resource model engine 204 for storage; and returns the task description information of the reconstructed task to the task modeling engine 201, so that the task engine 201 controls the loop execution of the reconstructed task according to the task description information of the reconstructed task.

The task flow control system provided by the disclosure solves the problem that the conventional workflow product flow control needs to be fixed, and can be directly updated when a task changes or the sequence of each step in the task changes, without reconfiguring the task flow or restarting the task flow control system. And. The task flow control of self-checking, spot inspection and mutual inspection of the secret-related cleaning system in the secret-related point marking is achieved, and the automatic control and the manual control of the task flow are combined. And providing related interfaces for the change of the subsequent self-checking, sampling checking and mutual checking process tasks, and providing related data query interfaces for the statistics of the task processes.

Example 3

Fig. 4 shows a flowchart of a task flow control method according to an embodiment of the present disclosure, as shown in fig. 4, the method includes:

and step 11, the task module acquires the task flow control request and generates a task loading instruction.

Step 12, the metadata management module receives the task loading instruction from the task module, loads an initial task according to the task loading instruction, and acquires task description information of the initial task from a task resource module; constructing a task type, a task step relation and a related step list of the task to be executed according to the task description information; and returning the task type, the task step relation and the related step list to the task module.

Step 13, the step module receives an initialization step instruction from the task module, wherein the initialization step instruction comprises the task description information, the task type, the task step relation and a related step list, and each step of the task to be executed is constructed and executed according to the initialization step instruction;

and step 14, storing the task description information by using a task resource module, and saving and/or updating each step and task state of each task to be executed in the process of executing each step of the task to be executed.

In one possible implementation, the method further includes: and under the condition that the task flow control request is a task request for executing a next step, a task request for stopping, a task request for suspending, a task request for completing or a task request for changing, the metadata management module acquires task description information of the initial task from the task resource module, wherein the task description information comprises task basic information, task state, task type and step information.

Fig. 5 is a flowchart illustrating a task flow control method according to an embodiment of the present disclosure to execute a next task, and as shown in fig. 5, constructing a flow to execute the next task includes:

in step S101, a Task engine (an example of a Task module) may include a plurality of Task processing classes (tasks). The task engine obtains a request (e.g., DONext (DataSet)) issued by the user to perform the next task. The user may be a developer, etc.

In step S102, the task engine generates a task loading instruction (e.g., loadtaskemeta (Data)) according to the request for executing the next task, and sends the task loading instruction to the metadata management engine (an example of a task module).

In step S103, the metadata management engine may load task description information (TaskMeta). For example, the metadata management engine sends a request (for example: loadtasskbaseinfo ()) for loading task basic information to a task resource engine (an example of a task resource module) according to a task load instruction.

Step S103', the task resource engine returns the basic information of the task (such as TaskBaseInfo) to the metadata management engine according to the request of loading the basic information of the task. The task resource engine may include a task resource repository (taskdatabasereproducibility) that stores task description information.

Step S104, the metadata management engine sends a task state loading request (for example: loadTaskStatus ()) to the task resource engine according to the task loading instruction.

Step S104', the task resource engine returns task state (for example: TaskStatus) to the metadata management engine according to the request of loading the task basic information.

Step S105, the metadata management engine sends a task state type loading and task step basic information request (such as loadTaskTypessAndsteps ()) to the task resource engine according to the task loading instruction.

And step S105', the task resource engine returns the task type and the step information to the metadata management engine according to the request for loading the task basic information.

And step S106, the metadata management engine constructs the task type of the task and the relation of the corresponding step.

In step S107, the metadata management engine constructs an execution list and executes the operation.

And step S108, the metadata management engine returns task description information, task types, step relationships and execution lists to the task engine.

In step S109, the task engine generates an initialization step command (e.g., stepplug. dofinish ()/stepplug. start), and transmits it to the step engine.

Step S110, a step engine (an example of a step module) may include a task step plug-in (stepplug). And the step engine constructs and circularly executes each step of the task according to the initialization step instruction.

Step S111, the step engine sends the updating step and the task state to the task resource engine.

And step S111', after the task resource engine updates the step and the task state, returning an update result to the step engine.

In step S112, data transmission between steps is performed by the file/piece data transmission engine (an example of a file/piece data transmission module) under the control of the task engine. A data set (TransDataSet) may be included in the file/file data transfer engine.

Fig. 6 is a flowchart illustrating a task flow control method according to an embodiment of the present disclosure, where as shown in fig. 6, constructing an abort task flow includes:

in step S201, a Task engine (an example of a Task module) may include a plurality of Task processing classes (tasks). An abort task request (e.g., DONext (DataSet)) from a user is obtained. The users may include developers, etc.

In step S202, the task engine generates a task loading instruction (e.g., loadtaskemeta (Data)) according to the task suspension request, and sends the task loading instruction to the metadata management engine (an example of a task module).

In step S203, the metadata management engine may load task description information (TaskMeta). For example, the metadata management engine sends a request (for example: loadtasskbaseinfo ()) for loading task basic information to a task resource engine (an example of a task resource module) according to a task load instruction.

In step S203', the task resource engine requests to return the basic information of the task (for example, TaskBaseInfo) to the metadata management engine according to the loaded basic information of the task. The task resource engine may include a task resource repository (taskdatabasereproducibility) that stores task description information.

In step S204, the metadata management engine sends a task state loading request (e.g., loadTaskStatus ()) to the task resource engine according to the task loading instruction.

Step S204', the task resource engine returns the task state (for example: TaskStatus) to the metadata management engine according to the request of loading the task basic information.

In step S205, the metadata management engine sends a task state type and task step basic information request (for example, loadtasktependandsteps ()) to the task resource engine according to the task load instruction.

And step S205', the task resource engine returns the task type and step information to the metadata management engine according to the request for loading the task basic information.

Step S206, the metadata management engine constructs the task type of the task and the relation of the corresponding step.

In step S207, the metadata management engine constructs an abort list and performs operations.

Step S208, the metadata management engine returns task description information, task types, step relationships and execution lists to the task engine.

In step S209, the task engine generates an initialization step command (e.g., stepplug.stop ()) and sends it to the step engine.

Step S210, a step engine (an example of a step module) may include a task step plug-in (stepplug). And the step engine constructs and circularly executes each step of the task according to the initialization step instruction.

Step S211, the step engine sends the update step and the task state to the task resource engine.

In step S211', after the task resource engine updates the step and the task state, the update result is returned to the step engine.

In step S212, data transmission between steps is performed by the file/piece data transmission engine (an example of a file/piece data transmission module) under the control of the task engine. A data set (TransDataSet) may be included in the file/file data transfer engine.

Fig. 7 is a flowchart illustrating a task flow control method according to an embodiment of the present disclosure, and as shown in fig. 7, constructing a suspended task flow includes:

in step S301, a Task engine (an example of a Task module) may include a plurality of Task processing classes (tasks). A pause task request (e.g., doNext) from a user is obtained. The users may include developers, etc.

In step S302, the task engine generates a task load instruction (e.g., loadtaskemeta (Data)) according to the suspend task request, and sends the task load instruction to the metadata management engine (an example of a task module).

In step S303, the metadata management engine may load task description information (TaskMeta). For example, the metadata management engine sends a request (for example: loadtasskbaseinfo ()) for loading task basic information to a task resource engine (an example of a task resource module) according to a task load instruction.

Step S303', the task resource engine returns the basic information of the task (for example, TaskBaseInfo) to the metadata management engine according to the request for loading the basic information of the task. The task resource engine may include a task resource repository (taskdatabasereproducibility) that stores task description information.

In step S304, the metadata management engine sends a task state loading request (e.g., loadTaskStatus ()) to the task resource engine according to the task loading instruction.

In step S304', the task resource engine returns a task status (e.g., TaskStatus) to the metadata management engine according to the request for loading the task basic information.

In step S305, the metadata management engine sends a task state type and task step basic information request (for example, loadtasktependaps ()) to the task resource engine according to the task load instruction.

And step S305', the task resource engine returns the task type and step information to the metadata management engine according to the request for loading the task basic information.

Step S306, the metadata management engine constructs the task type of the task and the relation of the corresponding step.

In step S307, the metadata management engine constructs a pause list and performs operations.

Step S308, the metadata management engine returns task description information, task types, step relationships and execution lists to the task engine.

In step S309, the task engine generates an initialization step command (e.g., stepplug. pause ()) and sends it to the step engine.

Step 310, a step engine (an example of a step module) may include a task step plug-in (stepplug). And the step engine constructs and circularly executes each step of the task according to the initialization step instruction.

Step S311, the step engine sends the update step and the task state to the task resource engine.

Step S311', after the task resource engine updates the step and the task state, an update result is returned to the step engine.

In step S312, data transmission between steps is performed by the file/piece data transmission engine (an example of a file/piece data transmission module) under the control of the task engine. A data set (TransDataSet) may be included in the file/file data transfer engine.

Fig. 8 is a flowchart illustrating a task completion flow of a task flow control method according to an embodiment of the present disclosure, and as shown in fig. 8, constructing a task completion flow includes:

in step S401, a Task engine (an example of a Task module) may include a plurality of Task processing classes (tasks). And acquiring a task execution completion request (such as a DONext (DataSet)) sent by a user. The users may include developers, etc.

In step S402, the task engine generates a task load instruction (e.g., loadtaskemeta (Data)) according to the task completion request, and sends the task load instruction to the metadata management engine (an example of a task module).

In step S403, the metadata management engine may load task description information (TaskMeta). For example, the metadata management engine sends a request (for example: loadtasskbaseinfo ()) for loading task basic information to a task resource engine (an example of a task resource module) according to a task load instruction.

In step S403', the task resource engine requests to return the basic task information (e.g., TaskBaseInfo) to the metadata management engine according to the loaded basic task information. The task resource engine may include a task resource repository (taskdatabasereproducibility) that stores task description information.

In step S404, the metadata management engine sends a task state loading request (e.g., loadTaskStatus ()) to the task resource engine according to the task loading instruction.

In step S404', the task resource engine returns a task status (e.g., TaskStatus) to the metadata management engine according to the request for loading the task basic information.

Step S405, the metadata management engine sends a task state type loading and task step basic information request (for example: loadTaskTypessAndsteps ()) to the task resource engine according to the task loading instruction.

And step S405', the task resource engine returns the task type and step information to the metadata management engine according to the request for loading the task basic information.

Step S406, the metadata management engine constructs the task type of the task and the relationship of the corresponding step.

In step S407, the metadata management engine builds a completion list and performs operations.

Step S408, the metadata management engine returns task description information, task types, step relationships and execution lists to the task engine.

In step S409, the task engine generates an initialization step instruction (e.g., stepplug. dofinish ()) and sends it to the step engine.

Step S410, a step engine (an example of a step module) may include a task step plug-in (stepplug). And the step engine constructs and circularly executes each step of the task according to the initialization step instruction.

Step S411, the step engine sends the updating step and the task state to the task resource engine.

In step S411', after the task resource engine updates the step and the task state, the update result is returned to the step engine.

In step S412, data transmission between steps is performed by the file/piece data transmission engine (an example of a file/piece data transmission module) under the control of the task engine. A data set (TransDataSet) may be included in the file/file data transfer engine.

In one possible implementation, the method further includes: and under the condition that the task flow control request is a task creation request, the metadata management module is also used for creating task description information of the initial task, wherein the task description information comprises task basic information, task state, task type and step information, and the task description information of the initial task is sent to the task resource module for storage.

Fig. 9 is a flowchart illustrating a task creation process according to an embodiment of the present disclosure, and as shown in fig. 9, constructing a task creation process includes:

in step S501, a Task engine (an example of a Task module) may include a plurality of Task processing classes (tasks). The creation task request (for example: Data) sent by the user is obtained. The users may include developers, etc.

In step S502, the task engine generates a task load instruction (e.g., loadtaskemeta (Data)) according to the create task request, and sends the task load instruction to the metadata management engine (an example of a task module).

In step S503, the metadata management engine may create task description information (TaskMeta). For example, the metadata management engine constructs basic information (for example: buildTaskBaseInfo ()) of the task according to the task load instruction.

In step S504, the metadata management engine builds a task state (e.g., buildTaskSstus ()) according to the task load instruction.

In step S505, the metadata management engine constructs a task type and a task type relationship (for example, buildTaskTypes ()) according to the task load instruction.

In step S506, the metadata management engine constructs a task step (i.e., a step) and a relationship between task steps (e.g., buildStepMetas ()) according to the task load instruction.

In step S507, the metadata management engine sends a save task request (e.g., SaveTaskBaseInfo ()) to a task resource engine (an example of a task resource module).

In step S507', the task resource engine saves the task according to the task saving request, and returns a task ID to the metadata management engine, where the task ID may include a storage location of the task. The task resource engine may include a task resource repository (taskdatabasereproducibility) that stores task description information.

At step S508, the metadata management engine sends a save task state request (e.g., SaveTaskBaseStatus ()) to the task resource engine.

Step S508', the task resource engine saves the task state according to the save task state request, and returns a save result to the metadata management engine.

In step S509, the metadata management engine sends a save task type request (e.g., SaveTaskBaseInfo (List < TaskType >, List < TaskTypeHopsMeta >) to the task resource engine.

In step S509', the task resource engine requests to save the task type according to the save task type, and returns a save result to the metadata management engine.

In step S510, the metadata management engine returns task description information to the task engine.

In step S511, the task engine generates an initialization step command (e.g., stepplug. init ()) and sends it to the step engine.

Step S512, a task step plug-in (stepplug-in) may be included in the step engine (an example of the step module). And the step engine constructs and circularly executes each step of the task according to the initialization step instruction.

In step S513, the step engine sends the step data to the task resource engine.

In step S513', the task resource engine returns the save state to the step engine after saving the step data.

In step S514, data transmission between steps is performed through a file/piece data transmission engine (an example of a file/piece data transmission module) under the control of the task engine. A data set (TransDataSet) may be included in the file/file data transfer engine.

In one possible implementation, the method further includes: under the condition that the task flow control request is the task changing request, the metadata management module is also used for reconstructing the task and sending task description information of the reconstructed task to the task resource module for storage; and returning task description information of the reconstructed task to the task module; and the task module is also used for controlling the cycle execution of the reconstructed task according to the task description information of the reconstructed task.

Fig. 10 is a flowchart illustrating a task change by the task flow control method according to an embodiment of the disclosure, and as shown in fig. 10, constructing a task change flow includes:

in step S601, a Task engine (an example of a Task module) may include a plurality of Task processing classes (tasks). A change task request (e.g., DONext (DataSet)) from a user is obtained. The users may include developers, etc.

In step S602, the task engine generates a task loading instruction (e.g., loadtaskemeta (Data)) according to the task change request, and sends the task loading instruction to the metadata management engine (an example of a task module).

In step S603, the metadata management engine may load the task description information (TaskMeta). For example, the metadata management engine sends a request (for example: loadtasskbaseinfo ()) for loading task basic information to a task resource engine (an example of a task resource module) according to a task load instruction.

Step S603', the task resource engine requests to return the basic information of the task (for example, TaskBaseInfo) to the metadata management engine according to the loaded basic information of the task. The task resource engine may include a task resource repository (taskdatabasereproducibility) that stores task description information.

In step S604, the metadata management engine sends a task state loading request (e.g., loadTaskStatus ()) to the task resource engine according to the task loading instruction.

In step S604', the task resource engine returns a task status (e.g., TaskStatus) to the metadata management engine according to the request for loading the task basic information.

In step S605, the metadata management engine sends a task state type and a task step request (for example, loadtasktepseasndsteps ()) to the task resource engine according to the task load instruction.

Step S605', the task resource engine returns the task type and step information to the metadata management engine according to the request for loading the basic task information.

Step S606, the metadata management engine constructs the task type of the task and the relation of the corresponding step.

In step S607, the metadata management engine builds a completion list.

Step S608, the metadata management engine returns the task description information, the task type, and the step relationship to the task engine.

In step S609, the task engine generates an initialization step command (e.g., stepplug. change ()) and sends it to the step engine.

Step S610, a task step plug-in (stepplug-in) may be included in the step engine (an example of the step module). And the step engine constructs and circularly executes each step of the task according to the initialization step instruction.

Step S611, the step engine sends the update step and the task state to the task resource engine.

Step S611', after the task resource engine updates the step and the task state, an update result is returned to the step engine.

In step S612, data transmission between steps is performed through a file/piece data transmission engine (an example of a file/piece data transmission module) under the control of the task engine. A data set (TransDataSet) may be included in the file/file data transfer engine.

In step S613, the metadata management engine reconstructs the task information (e.g., rebaldtask ()) according to the task load instruction.

In step S614, the metadata management engine sends a save task request (e.g., SaveTaskBaseInfo ()) to the task resource engine.

And step S614', the task resource engine stores the task according to the task storage request and returns the task ID to the metadata management engine.

In step S615, the metadata management engine sends a save task state request (e.g., SaveTaskBaseStatus ()) to the task resource engine.

And step S615', the task resource engine stores the task state according to the task state storage request and returns a storage result to the metadata management engine.

In step S616, the metadata management engine sends a save task type request (e.g., SaveTaskBaseInfo (List < TaskType >, List < TaskTypeHopsMeta >) to the task resource engine.

In step S616', the task resource engine requests to save the task type according to the save task type, and returns the save result to the metadata management engine.

In step S617, the metadata management engine returns the task description information to the task engine.

In step S618, the task engine generates an initialization step command (e.g., stepplug. init ()) and sends it to the step engine.

And step S619, the step engine constructs and executes each step of the task in a circulating mode according to the initialization step instruction.

Step S620, the step engine sends the step data to the task resource engine.

In step S620', the task resource engine returns the save state to the step engine after saving the step data.

Step S621, under the control of the task engine, performs data transmission between steps through the file/piece data transmission engine.

In one possible implementation, the method further includes: the file/piece data transmission module is used for controlling data transmission, copying or distribution among all steps of the executed task in the process of executing the task.

In one possible implementation, the method further includes: and the task batch management module is used for calling corresponding tasks from the task module according to the task batch request and executing the called tasks in batches.

In one possible implementation, the method further includes: and the task service interface is used for returning the step corresponding to the task to be executed to the step module after receiving the step calling request sent by the step module in the process of constructing the task to be executed by the step module.

The task flow control method provided by the disclosure solves the problem that the conventional workflow product flow control needs to be fixed, and can be directly updated when a task changes or the sequence of each step in the task changes, without reconfiguring a task flow or restarting a task flow control system. And. The task flow control of self-checking, spot inspection and mutual inspection of the secret-related cleaning system in the secret-related point marking is achieved, and the automatic control and the manual control of the task flow are combined. And providing related interfaces for the change of the subsequent self-checking, sampling checking and mutual checking process tasks, and providing related data query interfaces for the statistics of the task processes.

Example 4

FIG. 11 is a block diagram illustrating a task flow control device 1900 according to an exemplary embodiment. For example, the apparatus 1900 may be provided as a server. Referring to FIG. 11, the device 1900 includes a processing component 1922 further including one or more processors and memory resources, represented by memory 1932, for storing instructions, e.g., applications, executable by the processing component 1922. The application programs stored in memory 1932 may include one or more modules that each correspond to a set of instructions. Further, the processing component 1922 is configured to execute instructions to perform the task flow control method described above.

The device 1900 may also include a power component 1926 configured to perform power management of the device 1900, a wired or wireless network interface 1950 configured to connect the device 1900 to a network, and an input/output (I/O) interface 1958. The device 1900 may operate based on an operating system stored in memory 1932, such as Windows Server, Mac OS XTM, UnixTM, LinuxTM, FreeBSDTM, or the like.

In an exemplary embodiment, a non-transitory computer readable storage medium is also provided that includes instructions, such as the memory 1932 that includes instructions, which are executable by the processing component 1922 of the apparatus 1900 to perform the above-described method.

The present disclosure may be systems, methods, and/or computer program products. The computer program product may include a computer-readable storage medium having computer-readable program instructions embodied thereon for causing a processor to implement various aspects of the present disclosure.

The computer readable storage medium may be a tangible device that can hold and store the instructions for use by the instruction execution device. The computer readable storage medium may be, for example, but not limited to, an electronic memory device, a magnetic memory device, an optical memory device, an electromagnetic memory device, a semiconductor memory device, or any suitable combination of the foregoing. More specific examples (a non-exhaustive list) of the computer readable storage medium would include the following: 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 Static Random Access Memory (SRAM), a portable compact disc read-only memory (CD-ROM), a Digital Versatile Disc (DVD), a memory stick, a floppy disk, a mechanical coding device, such as punch cards or in-groove projection structures having instructions stored thereon, and any suitable combination of the foregoing. Computer-readable storage media as used herein is not to be construed as transitory signals per se, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through a waveguide or other transmission medium (e.g., optical pulses through a fiber optic cable), or electrical signals transmitted through electrical wires.

The computer-readable program instructions described herein may be downloaded from a computer-readable storage medium to a respective computing/processing device, or to an external computer or external storage device via a network, such as the internet, a local area network, a wide area network, and/or a wireless network. The network may include copper transmission cables, fiber optic transmission, wireless transmission, routers, firewalls, switches, gateway computers and/or edge servers. The network adapter card or network interface in each computing/processing device receives computer-readable program instructions from the network and forwards the computer-readable program instructions for storage in a computer-readable storage medium in the respective computing/processing device.

The computer program instructions for carrying out operations of the present disclosure may be assembler instructions, Instruction Set Architecture (ISA) instructions, machine-related instructions, microcode, firmware instructions, state setting data, or source or object code written in any combination of one or more programming languages, including an object oriented programming language such as Smalltalk, C + + or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The computer-readable program instructions may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet service provider). In some embodiments, the electronic circuitry that can execute the computer-readable program instructions implements aspects of the present disclosure by utilizing the state information of the computer-readable program instructions to personalize the electronic circuitry, such as a programmable logic circuit, a Field Programmable Gate Array (FPGA), or a Programmable Logic Array (PLA).

Various aspects of the present disclosure are described herein with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the disclosure. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer-readable program instructions.

These computer-readable program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks. These computer-readable program instructions may also be stored in a computer-readable storage medium that can direct a computer, programmable data processing apparatus, and/or other devices to function in a particular manner, such that the computer-readable medium storing the instructions comprises an article of manufacture including instructions which implement the function/act specified in the flowchart and/or block diagram block or blocks.

The computer readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus or other devices to produce a computer implemented process such that the instructions which execute on the computer, other programmable apparatus or other devices implement the functions/acts specified in the flowchart and/or block diagram block or blocks.

The flowchart 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 disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of instructions, which comprises one or more executable instructions for implementing the specified logical function(s). 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 and/or flowchart illustration, and combinations of blocks in the block diagrams and/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.

Having described embodiments of the present disclosure, the foregoing description is intended to be exemplary, not exhaustive, and not limited to the disclosed embodiments. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the described embodiments. The terms used herein were chosen in order to best explain the principles of the embodiments, the practical application, or technical improvements to the techniques in the marketplace, or to enable others of ordinary skill in the art to understand the embodiments disclosed herein.

Claims

1. A task flow control system, comprising:

the task module is used for acquiring a task flow control request and generating a task loading instruction, wherein the task flow control request comprises a task request for executing the next step, a task request for suspending, a task request for completing, a task request for changing and a task request for creating;

the metadata management module is used for receiving the task loading instruction from the task module, loading an initial task according to the task loading instruction, creating task description information of the initial task under the condition that the task flow control request is a task creation request, wherein the task description information comprises task basic information, task state, task type and step information, and sending the task description information of the initial task to the task resource module for storage; under the condition that the task flow control request is a task request for executing a next step, a task request is stopped, a task request is suspended, a task request is completed or a task request is changed, task description information of the initial task is obtained from a task resource module; constructing a task type, a task step relation and a related step list of the task to be executed according to the task description information; returning the task type, the task step relation and the related step list to the task module;

2. The system of claim 1,

the metadata management module is further configured to reconstruct the task and send task description information of the reconstructed task to the task resource module for storage when the task flow control request is the task change request; and returning task description information of the reconstructed task to the task module;

and the task module is also used for controlling the cycle execution of the reconstructed task according to the task description information of the reconstructed task.

3. The system of claim 1, further comprising:

and the file/piece data transmission module is used for controlling data transmission, copying or distribution among the steps of the executed task in the process of executing the task.

4. The system of claim 1, further comprising:

and the task batch management module is used for calling corresponding tasks from the task module according to the task batch request and executing the called tasks in batches.

5. The system of claim 1, further comprising:

and the task service interface is used for returning the step corresponding to the task to be executed to the step module after receiving the step calling request sent by the step module in the process of constructing the task to be executed by the step module.

6. A task flow control method is characterized by comprising the following steps:

the task module acquires a task flow control request and generates a task loading instruction, wherein the task flow control request comprises a task request for executing the next step, a task request for suspending, a task request for completing, a task request for changing and a task request for creating;

the metadata management module receives the task loading instruction from the task module, loads an initial task according to the task loading instruction, creates task description information of the initial task under the condition that the task flow control request is a task creation request, wherein the task description information comprises task basic information, task state, task type and step information, and sends the task description information of the initial task to the task resource module for storage; under the condition that the task flow control request is a task request for executing a next step, a task request is stopped, a task request is suspended, a task request is completed or a task request is changed, the metadata management module acquires task description information of the initial task from a task resource module; constructing a task type, a task step relation and a related step list of the task to be executed according to the task description information; returning the task type, the task step relation and the related step list to the task module;

7. The method of claim 6,

under the condition that the task flow control request is the task changing request, the metadata management module reconstructs task information and sends task description information of the reconstructed task to the task resource module for storage; and returning task description information of the reconstructed task to the task module;

and the task module controls the cycle execution of the reconstructed task according to the task description information of the reconstructed task.

8. The method of claim 6, further comprising:

the file/piece data transmission module controls data transmission, copying or distribution among steps of the executed task in the process of executing the task.

9. The method of claim 6, further comprising:

and the task batch management module calls corresponding tasks from the task module according to the task batch request and executes the called tasks in batches.

10. The method of claim 6, further comprising:

and in the process of constructing the task to be executed by the step module, the task service interface returns the step corresponding to the task to be executed to the step module after receiving the step calling request sent by the step module.