CN114819490A - Task release method, device, device and storage medium - Google Patents

Abstract

The invention relates to the technical field of internet and discloses a task issuing method, a device, equipment and a storage medium. The method comprises the steps of obtaining an initial task issued by a task issuing party, splitting the initial task through a preset splitting rule to obtain a plurality of subtasks, distributing the plurality of subtasks to different task processing parties so that the task processing party processes the plurality of subtasks and feeds back a plurality of subtask processing results, splicing the plurality of subtask processing results through a preset splicing rule to obtain a target task processing result, and feeding back the target task processing result to the task issuing party. Compared with the prior art that a task receiver directly receives a task initiated by a task initiator, the method can improve the flexibility during task allocation and reduce the expansion difficulty.

Description

Task release method, device, device and storage medium

technical field

The present invention relates to the field of Internet technologies, and in particular, to a task issuing method, apparatus, device and storage medium.

Background technique

With the rapid development of the Internet, many task relationships that were previously maintained by manpower can now be managed on the Internet only through different logics. With the continuous updating of application technologies, more and more specific task relationship maintenance programs It has also sprung up like mushrooms after a rain, such as the mature human resource management system, ERP system, project management system, etc. are all representatives of them. The existing task splitting mode is generally a mode in which the task initiator initiates a task, and then one or more order receivers receive the task and complete it, and obtain the task revenue from it. This mode is commonly used by traditional task publishing platforms. mode, but this mode can only support 2 levels, is not flexible enough and difficult to expand, and cannot be used in other business scenarios.

The above content is only used to assist the understanding of the technical solutions of the present invention, and does not mean that the above content is the prior art.

SUMMARY OF THE INVENTION

The main purpose of the present invention is to provide a task issuing method, device, device and storage medium, which aims to solve the technical problems of low flexibility and difficult expansion in task allocation in the prior art.

To achieve the above object, the present invention provides a task issuing method, the task issuing method includes:

Acquiring the initial task issued by the task issuer, and splitting the initial task through preset splitting rules to obtain multiple subtasks;

Allocating the multiple subtasks to different task processors, so that the task processor processes the multiple subtasks and feeds back the processing results of the multiple subtasks;

The processing results of the multiple subtasks are spliced through a preset splicing rule to obtain the processing result of the target task, and the processing result of the target task is fed back to the task issuer.

Optionally, the step of obtaining the initial task issued by the task issuer, and splitting the initial task by using preset splitting rules to obtain multiple subtasks specifically includes:

Obtaining the initial task issued by the task issuer and the task type corresponding to the initial task, and selecting a target splitting rule from preset splitting rules according to the task type;

Splitting the initial task according to the target splitting rule to obtain a plurality of initial subtasks;

Determine the split state of each initial subtask according to the attribute information of each initial subtask;

According to the split state, the initial subtasks are split according to the target splitting rule to obtain a plurality of subtasks.

Optionally, the step of splitting the initial subtasks through the target splitting rule according to the splitting state to obtain multiple subtasks specifically includes:

Splitting the initial subtasks according to the splitting state and using the target splitting rule to obtain a plurality of split initial subtasks;

Return to the step of determining the split state of each initial subtask according to the attribute information of each initial subtask, until the attribute information of each split initial subtask satisfies the preset condition, and multiple subtasks are obtained.

Optionally, the step of allocating the multiple subtasks to different task processors, so that the task processor processes the multiple subtasks and feeds back the processing results of the multiple subtasks, specifically includes:

Allocating the multiple subtasks to different task handlers, and constructing a mapping relationship between each task handler and each subtask;

Determine all subtasks corresponding to each task processor according to the mapping relationship;

Acquire task processing requirement information corresponding to all subtasks, so that each task processor processes all subtasks according to the task processing requirement information and feeds back processing results of multiple subtasks.

Optionally, the acquiring task processing requirement information corresponding to all subtasks, so that each task processor processes all subtasks according to the task processing requirement information and feeds back the processing results of multiple subtasks. steps, including:

Obtain task processing requirement information corresponding to all subtasks and resource information corresponding to the task issuer;

Send the task processing request information and the resource information to the task processors corresponding to all the subtasks, so that the task processors can The task is processed and the processing results of multiple subtasks are fed back.

Optionally, the step of splicing the processing results of the multiple sub-tasks by using preset splicing rules to obtain the processing results of the target tasks, and feeding back the processing results of the target tasks to the task issuer specifically includes:

Obtain the number of results corresponding to the processing results of the multiple subtasks, and obtain the number of tasks corresponding to the multiple subtasks;

When the number of results and the number of tasks meet the preset number condition, the processing results of the multiple subtasks are spliced through a preset splicing rule to obtain the processing result of the target task, and the processing result of the target task is fed back to the the task issuer.

Optionally, after the step of acquiring the number of results corresponding to the processing results of the multiple subtasks and acquiring the number of tasks corresponding to the multiple subtasks, the method further includes:

When the number of results and the number of tasks do not meet the preset number condition, obtain the target task processor and the target subtask that do not feed back the subtask processing result;

Sending prompt information to the target task processor, so that the target task processor processes the target subtask according to the prompt information and feeds back the processed subtask processing result;

The processed sub-task processing result and the multiple sub-task processing results are spliced through a preset splicing rule to obtain a target task processing result, and the target task processing result is fed back to the task issuer.

In addition, in order to achieve the above object, the present invention also proposes a task issuing device, the task issuing device includes:

The task splitting module is used to obtain the initial task issued by the task issuer, and split the initial task according to the preset splitting rules to obtain a plurality of subtasks;

a result feedback module, configured to assign the multiple subtasks to different task processors, so that the task processor processes the multiple subtasks and feeds back the processing results of the multiple subtasks;

The task splicing module is used for splicing the processing results of the multiple sub-tasks by using a preset splicing rule to obtain the processing results of the target tasks, and feeding back the processing results of the target tasks to the task issuer.

In addition, in order to achieve the above object, the present invention also proposes a task issuing device, the task issuing device includes: a memory, a processor and a task issuing program stored in the memory and running on the processor, The task issuer is configured to implement the task issue method as described above.

In addition, in order to achieve the above object, the present invention also provides a storage medium, where a task issuing program is stored, and when the task issuing program is executed by a processor, the above-mentioned task issuing method is implemented.

The present invention obtains the initial task issued by the task issuer, splits the initial task through preset splitting rules, obtains multiple sub-tasks, and then assigns the multiple sub-tasks to different task processors, so that the task processors can Multiple subtasks are processed and the processing results of the multiple subtasks are fed back, and then the processing results of the multiple subtasks are spliced through preset splicing rules to obtain the processing results of the target task, and the processing results of the target task are fed back to the task issuer. The invention obtains multiple subtasks by splitting the initial task according to preset splitting rules, then the task processor processes the multiple subtasks and feeds back the processing results of the multiple subtasks, and then splices the processing results of the multiple subtasks to obtain As for the target task processing result, compared with the existing task orderer directly receiving the task initiated by the task initiator, the above-mentioned method of the present invention can improve the flexibility in task allocation and reduce the difficulty of expansion.

Description of drawings

FIG. 1 is a schematic structural diagram of a task issuing device of a hardware operating environment according to an embodiment of the present invention;

FIG. 2 is a schematic flowchart of a first embodiment of a task issuing method according to the present invention;

3 is a schematic flowchart of a second embodiment of a task issuing method according to the present invention;

4 is a schematic flowchart of a third embodiment of a task issuing method according to the present invention;

FIG. 5 is a structural block diagram of a first embodiment of a task issuing apparatus according to the present invention.

The realization, functional characteristics and advantages of the present invention will be further described with reference to the accompanying drawings in conjunction with the embodiments.

Detailed ways

It should be understood that the specific embodiments described herein are only used to explain the present invention, but not to limit the present invention.

Referring to FIG. 1 , FIG. 1 is a schematic structural diagram of a task issuing device of a hardware operating environment according to an embodiment of the present invention.

As shown in FIG. 1 , the task issuing device may include: a processor 1001 , such as a central processing unit (Central Processing Unit, CPU), a communication bus 1002 , a user interface 1003 , a network interface 1004 , and a memory 1005 . Among them, the communication bus 1002 is used to realize the connection and communication between these components. The user interface 1003 may include a display screen (Display), an input unit such as a keyboard (Keyboard), and the optional user interface 1003 may also include a standard wired interface and a wireless interface. Optionally, the network interface 1004 may include a standard wired interface and a wireless interface (eg, a wireless-fidelity (Wireless-Fidelity, Wi-Fi) interface). The memory 1005 may be a high-speed random access memory (Random Access Memory, RAM), or a stable non-volatile memory (Non-Volatile Memory, NVM), such as a disk memory. Optionally, the memory 1005 may also be a storage device independent of the aforementioned processor 1001 .

Those skilled in the art can understand that the structure shown in FIG. 1 does not constitute a limitation on the task issuing device, and may include more or less components than the one shown, or combine some components, or arrange different components.

As shown in FIG. 1 , the memory 1005 as a storage medium may include an operating system, a network communication module, a user interface module and a task issuing program.

In the task issuing device shown in FIG. 1, the network interface 1004 is mainly used for data communication with the network server; the user interface 1003 is mainly used for data interaction with the user; the processor 1001 and the memory 1005 in the task issuing device of the present invention may be Set in a task issuing device, the task issuing device invokes the task issuing program stored in the memory 1005 through the processor 1001, and executes the task issuing method provided by the embodiment of the present invention.

An embodiment of the present invention provides a task publishing method. Referring to FIG. 2 , FIG. 2 is a schematic flowchart of the first embodiment of the task publishing method according to the present invention.

In this embodiment, the task publishing method includes the following steps:

Step S10: obtaining the initial task issued by the task issuer, and splitting the initial task through preset splitting rules to obtain a plurality of subtasks;

It should be noted that the execution body of this embodiment may be the above-mentioned task issuing device with network communication and program running functions, or may be other devices capable of implementing the same or similar functions, such as a server, which is not specifically described in this embodiment. limit.

It is understandable that the task issuer refers to the party that issues the task, and the initial task refers to the task that the task issuer publishes on the server and needs to be processed. It may also be other tasks, which are not specifically limited in this embodiment.

It should be understood that the preset splitting rule refers to a preset rule for splitting tasks, which can split an initial task, and split an initial task into multiple subtasks with similar particles, that is, each Subtasks are similar in size and hierarchy.

Step S20: Allocating the multiple subtasks to different task processing parties, so that the task processing party processes the multiple subtasks and feeds back the processing results of the multiple subtasks;

It should be noted that the task processor refers to the party that processes the tasks according to the requirements. The task processor can choose the task to be processed by itself. The number of tasks can be one or more. make specific restrictions.

Understandably, the subtask processing result refers to the processing result obtained after the task processor completes the received subtask.

Step S30 : splicing the processing results of the multiple subtasks by using a preset splicing rule to obtain the processing result of the target task, and feeding back the processing result of the target task to the task issuing party.

It should be noted that the preset splicing rule refers to a preset rule for splicing processing results of multiple subtasks, and the rule can combine the processing results of multiple subtasks into a processing result of a target task.

In a specific implementation, after obtaining the sub-task processing results fed back by each task processor, since the task issuer only needs to obtain the results corresponding to the released tasks, this embodiment can combine the processing results of multiple sub-tasks into one target task for processing As a result, the target task processing result is fed back to the task issuer.

In this embodiment, the initial task released by the task issuer is obtained, and the initial task is divided by preset splitting rules to obtain multiple sub-tasks, and then the multiple sub-tasks are allocated to different task processors, so that the task processor Process multiple subtasks and feed back the processing results of the multiple subtasks, and then splicing the processing results of the multiple subtasks through preset splicing rules to obtain the processing results of the target task, and feed back the processing results of the target task to the task issuer. In this embodiment, multiple subtasks are obtained by splitting the initial task according to the preset splitting rules, and then the task processor processes the multiple subtasks and feeds back the processing results of the multiple subtasks, and then splices the processing results of the multiple subtasks, To obtain the target task processing result, compared with the existing task orderer directly receiving the task initiated by the task initiator, the above method of this embodiment can improve the flexibility in task allocation and reduce the difficulty of expansion.

Referring to FIG. 3 , FIG. 3 is a schematic flowchart of a second embodiment of a task publishing method according to the present invention.

Based on the above-mentioned first embodiment, in this embodiment, the step S10 includes:

Step S101: obtaining an initial task issued by a task issuer and a task type corresponding to the initial task, and selecting a target splitting rule from preset splitting rules according to the task type;

It should be noted that the task type refers to the type corresponding to the initial task, for example, the click type and the search type, which are not specifically limited in this embodiment.

It is understandable that the preset splitting rules can include multiple splitting rules, and the splitting rules corresponding to each task type are different. For example, when the task type is click type, the splitting rule can be configured as the first One subtask is one click, and the second subtask is three clicks. The specific number of clicks can be determined according to the total number of clicks required by the initial task and the number of task handlers to be assigned, which is not specifically limited in this embodiment.

Step S102: splitting the initial task through the target splitting rule to obtain a plurality of initial subtasks;

It should be understood that the splitting rules corresponding to each task type are the same, but the configured parameters may change with the changes of the initial task parameters. For example, when the task type is click type, the initial task is to click 30 times. , at this time, the initial task can be divided into 10 sub-tasks, each sub-task needs to be clicked 3 times, or the initial task can be divided into 15 sub-tasks, each sub-task needs to be clicked 2 times. The splitting of tasks can be set according to the actual situation.

Step S103: Determine the split state of each initial subtask according to the attribute information of each initial subtask;

It should be noted that the split state refers to a state in which each initial subtask is currently in a state where the split can be continued or cannot be continued. The attribute information refers to the information such as the size and level corresponding to the initial subtask.

In the specific implementation, taking the click type as an example, the number of clicks of the minimum subtask set by the system can be obtained in advance. If the number of clicks of the minimum subtask is one, it means that the number of clicks of the subtask cannot be less than one. When the subtask is clicked 3 times, it means that the split state is that it can continue to be split; when the initial subtask is clicked once, it means that the split state is not able to continue to be split.

Step S104: Splitting the initial subtasks according to the splitting state through the target splitting rule to obtain a plurality of subtasks.

It is understandable that, when the split state of an initial subtask is that the splitting can be continued, the initial subtask can be split continuously through the target splitting rule at this time.

Further, in this embodiment, the step S104 includes: splitting the initial subtasks according to the splitting state and using the target splitting rule to obtain a plurality of split initial subtasks; Return to the step of determining the split state of each initial subtask according to the attribute information of each initial subtask, until the attribute information of each split initial subtask satisfies the preset condition, and multiple subtasks are obtained.

It should be noted that the preset condition is the condition that the attributes of the pre-set minimum subtask need to meet, which can be set according to the actual situation. For example, the number of clicks of the minimum subtask is 1, and only one task processor The processing may also be set to other conditions, which are not specifically limited in this embodiment.

It is understandable that only when the attribute information of each subtask after splitting satisfies the preset conditions, it means that the initial task splitting issued by the task issuer is completed, and all the subtasks obtained at this time are finally obtained in this embodiment. of multiple subtasks.

In the specific implementation, after the initial task is split once, it is necessary to obtain the split state of the sub-task after the split. When there is a sub-task that can be further split, the sub-task needs to be split. Then obtain the split status of the subtasks after the second split, until all the subtasks can no longer be split, at this time, obtain all the subtasks that currently exist.

In this embodiment, the initial task issued by the task issuer and the task type corresponding to the initial task are obtained, and the target splitting rule is selected from the preset splitting rules according to the task type, and then the initial task is split according to the target splitting rule. Then, according to the attribute information of each initial subtask, determine the split state of each initial subtask, and then split each initial subtask according to the split state through the target splitting rules to obtain multiple subtasks. Task. In this embodiment, the target splitting rule is selected according to the task type corresponding to the initial task, the initial task is split according to the target splitting rule, and whether the subtasks need to be split again is determined according to the splitting status of each subtask. Multiple subtasks, so that the split subtasks have more levels and improve flexibility.

Referring to FIG. 4 , FIG. 4 is a schematic flowchart of a third embodiment of a task publishing method according to the present invention.

Based on the foregoing embodiments, in this embodiment, the step S20 includes:

Step S201: assigning the multiple subtasks to different task handlers, and constructing a mapping relationship between each task handler and each subtask;

It is understandable that the task processor can choose the sub-task to be completed by itself according to actual needs, which may be one or multiple. The mapping relationship may include a task handler corresponding to each subtask.

Step S202: Determine all subtasks corresponding to each task handler according to the mapping relationship;

Step S203: Obtain task processing requirement information corresponding to all subtasks, so that each task processor processes all subtasks according to the task processing requirement information and feeds back processing results of multiple subtasks.

It should be noted that the task processing request information may include relevant information on how to process subtasks, such as how many times to click, what type of data to search, etc., which is not specifically limited in this embodiment.

It should be understood that the subtask processing result refers to the result returned after the task processor completes the corresponding subtask, for example, click to complete, the content of the data to be searched, and so on.

Further, in order to accurately determine the subtask processing result, in this embodiment, the step S203 includes: acquiring task processing requirement information corresponding to all subtasks and resource information corresponding to the task issuer; The processing request information and the resource information are sent to the task handlers corresponding to all the subtasks, so that the task handlers process all the subtasks according to the task processing request information and the resource information. Feedback the processing results of multiple subtasks.

It is understandable that the resource information may include account information corresponding to the task issuer, identity information, etc., which is not specifically limited in this embodiment.

In the specific implementation, the task processor can process the subtasks according to the task processing requirement information, and then can know the task issuer according to the resource information, so as to contact the task issuer according to the requirements, and then process according to the task processing requirement information.

In this embodiment, multiple subtasks are allocated to different task processors, and a mapping relationship between each task processor and each subtask is constructed, and then all subtasks corresponding to each task processor are determined according to the mapping relationship, and then all subtasks corresponding to each task are obtained. The task processing requirement information, so that each task processor processes all subtasks according to the task processing requirement information and feeds back processing results of multiple subtasks. In this embodiment, by acquiring task processing requirement information corresponding to all subtasks, each task processor can process all subtasks according to the task processing requirement information, thereby making the subtask processing result more accurate.

Further, in this embodiment, the step S30 includes:

Step S301: Obtain the number of results corresponding to the processing results of the multiple subtasks, and obtain the number of tasks corresponding to the multiple subtasks;

Step S302: When the number of results and the number of tasks meet the preset number condition, splicing the processing results of the multiple sub-tasks through preset splicing rules to obtain the processing results of the target tasks, and combine the processing results of the target tasks. Feedback to the task issuer.

It should be noted that, in this embodiment, the preset number condition means that the number of results and the number of tasks are the same.

It is understandable that the preset splicing rules also need to be determined according to the task type of the initial task, and the splicing rules corresponding to each task type are different. For example: when the task type is a search type, the splicing rule is to directly combine all The subtask processing results are merged into one target task processing result, and the splicing rules corresponding to other task types can also be set by themselves according to the actual situation, which is not specifically limited in this embodiment.

It should be understood that when the number of results and the number of tasks are the same, it means that each subtask has been processed and the corresponding subtask task processing results are fed back. At this time, it is only necessary to splicing all the subtask processing results to obtain the target. Task processing result.

Further, in this embodiment, after step S301, the steps include: when the number of results and the number of tasks do not meet the preset number condition, acquiring the target task processor and the target subtask of the unfeedback subtask processing result; Send prompt information to the target task processor, so that the target task processor processes the target subtask according to the prompt information and feeds back the processed subtask processing result; The processed subtask processing result and the multiple subtask processing results are spliced to obtain a target task processing result, and the target task processing result is fed back to the task issuer.

It is understandable that when the number of results and the number of tasks are not the same, it means that there may be subtasks that have not been processed by the task processor. At this time, it is necessary to obtain subtasks that have not been processed by the task processor, that is, subtasks that have not been fed back. For the target subtask of the processing result, it is also necessary to obtain the target task handler corresponding to the target subtask.

It should be understood that when the target task processor that does not feed back the subtask processing results is obtained, it is necessary to send prompt information to the target task processor, and the prompt information may include the target subtask, the task information corresponding to the target subtask, and the task release. The resource information corresponding to the person, etc., may also include other information, which is not specifically limited in this embodiment.

In the specific implementation, the target task processor can process the target subtask according to the prompt information, then feed back the processed subtask processing results, and then splicing the processed subtask processing results with the multiple subtask processing results to obtain a The target task processing results are then fed back to the task publisher.

In this embodiment, by acquiring the number of results corresponding to the processing results of multiple subtasks, and acquiring the number of tasks corresponding to the multiple subtasks, when the number of results and the number of tasks satisfy the preset number condition, the processing results of the multiple subtasks are processed by preset splicing rules. Splicing, obtain the target task processing results, and feed back the target task processing results to the task publisher. This embodiment determines whether the task processor has processed all subtasks by judging whether the number of results and the number of tasks meet the preset number condition, so that the subtask processing results can be obtained more accurately and fed back to the task issuer, thereby improving flexibility.

In addition, an embodiment of the present invention further provides a storage medium, where a task issuing program is stored thereon, and when the task issuing program is executed by a processor, the above-described task issuing method is implemented.

Referring to FIG. 5, FIG. 5 is a structural block diagram of a first embodiment of a task issuing apparatus according to the present invention.

As shown in FIG. 5 , the task issuing device proposed by the embodiment of the present invention includes:

The task splitting module 10 is used for acquiring the initial task issued by the task issuer, and splitting the initial task according to the preset splitting rules to obtain a plurality of subtasks;

a result feedback module 20, configured to assign the multiple subtasks to different task processors, so that the task processor processes the multiple subtasks and feeds back the processing results of the multiple subtasks;

The task splicing module 30 is configured to splicing the processing results of the multiple sub-tasks according to a preset splicing rule, to obtain the processing results of the target tasks, and feeding back the processing results of the target tasks to the task issuing party.

In this embodiment, the initial task released by the task issuer is obtained, and the initial task is divided by preset splitting rules to obtain multiple sub-tasks, and then the multiple sub-tasks are allocated to different task processors, so that the task processor Process multiple subtasks and feed back the processing results of the multiple subtasks, and then splicing the processing results of the multiple subtasks through preset splicing rules to obtain the processing results of the target task, and feed back the processing results of the target task to the task issuer. In this embodiment, multiple subtasks are obtained by splitting the initial task according to the preset splitting rules, and then the task processor processes the multiple subtasks and feeds back the processing results of the multiple subtasks, and then splices the processing results of the multiple subtasks, To obtain the target task processing result, compared with the existing task orderer directly receiving the task initiated by the task initiator, the above method of this embodiment can improve the flexibility in task allocation and reduce the difficulty of expansion.

Based on the above-mentioned first embodiment of the task issuing apparatus of the present invention, a second embodiment of the task issuing apparatus of the present invention is proposed.

In this embodiment, the task splitting module 10 is further configured to acquire an initial task issued by a task issuer and a task type corresponding to the initial task, and select a target from preset splitting rules according to the task type splitting rules; splitting the initial task according to the target splitting rule to obtain a plurality of initial subtasks; determining the splitting state of each initial subtask according to the attribute information of each initial subtask; according to the In the split state, each initial subtask is split according to the target splitting rule to obtain a plurality of subtasks.

Further, the task splitting module 10 is further configured to split the initial subtasks through the target splitting rule according to the splitting state, and obtain a plurality of split initial subtasks; return The step of determining the split state of each initial subtask according to the attribute information of each initial subtask, until the attribute information of each split initial subtask satisfies a preset condition, and multiple subtasks are obtained.

Further, the result feedback module 20 is further configured to assign the multiple subtasks to different task handlers, and construct a mapping relationship between each task handler and each subtask; determine each task process according to the mapping relationship All subtasks corresponding to the party; obtain task processing requirement information corresponding to all subtasks, so that each task processor can process all subtasks according to the task processing requirement information and feed back multiple subtask processing results .

Further, the result feedback module 20 is further configured to acquire task processing requirement information corresponding to all subtasks and resource information corresponding to the task issuer; send the task processing requirement information and the resource information to Task processors corresponding to all subtasks, so that each task processor processes all subtasks according to the task processing requirement information and the resource information and feeds back processing results of multiple subtasks.

Further, the task splicing module 30 is also used to obtain the number of results corresponding to the processing results of the multiple subtasks, and obtain the number of tasks corresponding to the multiple subtasks; When the quantity condition is set, the processing results of the multiple subtasks are spliced through a preset splicing rule to obtain the processing result of the target task, and the processing result of the target task is fed back to the task issuer.

Further, the task splicing module 30 is also used to obtain the target task processor and the target subtask that do not feed back the subtask processing results when the number of results and the number of tasks do not meet the preset number condition; The target task processor sends prompt information, so that the target task processor processes the target subtask according to the prompt information and feeds back the processed subtask processing result; The subtask processing result of the subtask and the multiple subtask processing results are spliced to obtain the target task processing result, and the target task processing result is fed back to the task issuer.

For other embodiments or specific implementation manners of the task issuing apparatus of the present invention, reference may be made to the foregoing method embodiments, and details are not described herein again.

It should be noted that, herein, the terms "comprising", "comprising" or any other variation thereof are intended to encompass non-exclusive inclusion, such that a process, method, article or system comprising a series of elements includes not only those elements, It also includes other elements not expressly listed or inherent to such a process, method, article or system. Without further limitation, an element qualified by the phrase "comprising a..." does not preclude the presence of additional identical elements in the process, method, article or system that includes the element.

The above-mentioned serial numbers of the embodiments of the present invention are only for description, and do not represent the advantages or disadvantages of the embodiments.

From the description of the above embodiments, those skilled in the art can clearly understand that the method of the above embodiment can be implemented by means of software plus a necessary general hardware platform, and of course can also be implemented by hardware, but in many cases the former is better implementation. Based on this understanding, the technical solutions of the present invention can be embodied in the form of software products that are essentially or contribute to the prior art, and the computer software products are stored in a storage medium (such as read-only memory/random access). memory, magnetic disk, optical disk), including several instructions to make a terminal device (which may be a mobile phone, a computer, a server, or a network device, etc.) execute the methods described in the various embodiments of the present invention.

The above are only preferred embodiments of the present invention, and are not intended to limit the scope of the present invention. Any equivalent structure or equivalent process transformation made by using the contents of the description and drawings of the present invention, or directly or indirectly applied in other related technical fields , are similarly included in the scope of patent protection of the present invention.

Claims (10)

1. a task issuing method, is characterized in that, described task issuing method comprises: Acquiring the initial task issued by the task issuer, and splitting the initial task through preset splitting rules to obtain multiple subtasks; Allocating the multiple subtasks to different task processors, so that the task processor processes the multiple subtasks and feeds back the processing results of the multiple subtasks; The processing results of the multiple subtasks are spliced through a preset splicing rule to obtain the processing result of the target task, and the processing result of the target task is fed back to the task issuer. 2. The task issuing method according to claim 1, wherein the initial task issued by the task issuer is obtained, and the initial task is split by a preset splitting rule to obtain a plurality of subtasks. , including: Obtain the initial task issued by the task issuer and the task type corresponding to the initial task, and select a target splitting rule from preset splitting rules according to the task type; Splitting the initial task according to the target splitting rule to obtain a plurality of initial subtasks; Determine the split state of each initial subtask according to the attribute information of each initial subtask; According to the split state, the initial subtasks are split through the target splitting rule to obtain a plurality of subtasks. 3. task issuing method as claimed in claim 2, is characterized in that, described each initial subtask is split by described target splitting rule according to described split state, the step that obtains a plurality of subtasks, Specifically include: Splitting the initial subtasks according to the splitting state and using the target splitting rule to obtain a plurality of split initial subtasks; Return to the step of determining the split state of each initial subtask according to the attribute information of each initial subtask, until the attribute information of each split initial subtask satisfies the preset condition, and multiple subtasks are obtained. 4. The task issuing method according to claim 1, wherein the multiple subtasks are allocated to different task processing parties, so that the task processing party processes the multiple subtasks and provides feedback The steps for processing results of multiple subtasks include: Allocating the multiple subtasks to different task handlers, and constructing a mapping relationship between each task handler and each subtask; Determine all subtasks corresponding to each task processor according to the mapping relationship; Acquire task processing requirement information corresponding to all subtasks, so that each task processor processes all subtasks according to the task processing requirement information and feeds back processing results of multiple subtasks. 5. The task issuing method according to claim 4, wherein the acquiring task processing requirement information corresponding to all the subtasks, so that each task processor can The steps of processing all subtasks and feeding back the processing results of multiple subtasks include: Obtain task processing requirement information corresponding to all subtasks and resource information corresponding to the task issuer; Send the task processing request information and the resource information to the task processors corresponding to all the subtasks, so that the task processors can The task is processed and the processing results of multiple subtasks are fed back. 6. task issuing method as claimed in claim 1 is characterized in that, described a plurality of subtask processing results are spliced by preset splicing rule, obtain target task processing result, and described target task processing result is fed back The steps for the task issuer specifically include: Obtain the number of results corresponding to the processing results of the multiple subtasks, and obtain the number of tasks corresponding to the multiple subtasks; When the number of results and the number of tasks meet the preset number condition, the processing results of the multiple subtasks are spliced through a preset splicing rule to obtain the processing result of the target task, and the processing result of the target task is fed back to the the task issuer. 7. The task issuing method according to claim 6, characterized in that, after the step of obtaining the corresponding result quantities of the multiple subtask processing results, and obtaining the task quantity corresponding to the multiple subtasks, the method further comprises: When the number of results and the number of tasks do not meet the preset number condition, obtain the target task processor and the target subtask that do not feed back the subtask processing result; Sending prompt information to the target task processor, so that the target task processor processes the target subtask according to the prompt information and feeds back the processed subtask processing result; The processed sub-task processing result and the multiple sub-task processing results are spliced through a preset splicing rule to obtain a target task processing result, and the target task processing result is fed back to the task issuer. 8. A task issuing device, wherein the task issuing device comprises: The task splitting module is used to obtain the initial task issued by the task issuer, and split the initial task according to the preset splitting rules to obtain a plurality of subtasks; a result feedback module, configured to assign the multiple subtasks to different task processors, so that the task processor processes the multiple subtasks and feeds back the processing results of the multiple subtasks; The task splicing module is used for splicing the processing results of the multiple sub-tasks by using a preset splicing rule to obtain the processing results of the target tasks, and feeding back the processing results of the target tasks to the task issuer. 9. A task issuing device, characterized in that the task issuing device comprises: a memory, a processor and a task issuing program stored on the memory and running on the processor, the task issuing program configuring In order to realize the task issuing method according to any one of claims 1 to 7. 10 . A storage medium, wherein a task issuing program is stored on the storage medium, and when the task issuing program is executed by a processor, the task issuing method according to any one of claims 1 to 7 is implemented.

Images