CN113706109B

CN113706109B - Task processing method and device

Info

Publication number: CN113706109B
Application number: CN202110998625.1A
Authority: CN
Inventors: 言语
Original assignee: Shanghai Bilibili Technology Co Ltd
Current assignee: Shanghai Bilibili Technology Co Ltd
Priority date: 2021-08-27
Filing date: 2021-08-27
Publication date: 2024-05-14
Anticipated expiration: 2041-08-27
Also published as: CN113706109A

Abstract

The application provides a task processing method and a task processing device, wherein the task processing method comprises the following steps: receiving a task creation request submitted by a task request terminal; creating and issuing a target task based on task information carried in the task creation request, wherein at least two task participants contained in the task information belong to different task fields; the method comprises the steps that task votes submitted by a statistics voting terminal aiming at a published target task are counted, and an initial task execution result of the target task is determined based on task voting statistics results; and under the condition that the initial task execution result is that the task execution is successful, sending task participation information to each task participant. The task voting of the target task based on statistics is realized, the task effect is predicted, and the task foreground of the target task is determined by the task participant according to the prediction result, so that the target participant determines whether to continue to implement the target task based on the task foreground, and the safety of implementing the target task is ensured.

Description

Task processing method and device

Technical Field

The application relates to the technical field of data processing, in particular to a task processing method. The application also relates to a task processing device, a computing device and a computer readable storage medium.

Background

Collaboration refers to a joint action or manner of interaction between individuals, groups of individuals, or groups of individuals to achieve a common goal. In a practical scenario, when two or more partners decide to cooperate, the cooperation flow is completely closed. Because the partner does not disclose the process of pre-cooperation, the user cannot learn the cooperation content or participate in the cooperation process before the cooperation product obtained through cooperation appears.

Disclosure of Invention

In view of this, the embodiment of the application provides a task processing method. The application also relates to a task processing device, a computing device and a computer readable storage medium, which are used for solving the defects that users cannot participate in the cooperation before the cooperation and cannot predict the cooperation effect in the prior art.

According to a first aspect of an embodiment of the present application, there is provided a task processing method, including:

Receiving a task creation request submitted by a task request terminal;

Creating and issuing a target task based on task information carried in the task creation request, wherein at least two task participants contained in the task information belong to different task fields;

The method comprises the steps that task votes submitted by a statistics voting terminal aiming at a published target task are counted, and an initial task execution result of the target task is determined based on task voting statistics results;

and under the condition that the initial task execution result is that the task execution is successful, sending task participation information to each task participant.

According to a second aspect of an embodiment of the present application, there is provided a task processing device including:

the receiving module is configured to receive a task creation request submitted by a task request terminal;

The issuing module is configured to establish a target task and issue the target task based on task information carried in the task establishing request, wherein at least two task participants contained in the task information belong to different task fields;

the statistics module is configured to count task votes submitted by the voting terminal for the issued target task and determine an initial task execution result of the target task based on the task voting statistics result;

And the sending module is configured to send task participation information to each task participant when the initial task execution result is that the task execution is successful.

According to a third aspect of embodiments of the present application, there is provided a computing device comprising a memory, a processor and computer instructions stored on the memory and executable on the processor, the processor implementing the steps of the task processing method when executing the computer instructions.

According to a fourth aspect of embodiments of the present application, there is provided a computer readable storage medium storing computer instructions which, when executed by a processor, implement the steps of the task processing method.

According to the task processing method provided by the application, the task creation request submitted by the task request terminal is received, and the target task is created and issued based on the task information carried in the task creation request, wherein at least two task participants contained in the task information belong to different service fields, so that the issue of the target task participated by the task participants not belonging to the same service field is realized. And then counting task votes submitted by the voting terminal aiming at the issued target task, determining an initial task execution result of the target task based on the task voting counting result, enabling a user to participate in the target task by issuing the target task, counting task votes of the user on the target task, realizing interaction between the user and the target task, and predicting the cooperation effect of the target task according to the counting result, and sending task participation information to each task participant under the condition that the task execution result is successful in executing the initial task, thereby realizing task prospect of the target task to be determined by the task participant according to the prediction result, so that the task participant can determine whether to continue to implement the target task based on the task prospect, and ensuring the success of the target task.

Drawings

FIG. 1 is a flow chart of a task processing method according to an embodiment of the present application;

FIG. 2 is a schematic diagram of a user task in a task processing method according to an embodiment of the present application;

FIG. 3 is a schematic diagram of a target task in a task processing method according to an embodiment of the present application;

FIG. 4 is a process flow diagram of a task processing method applied to a collaboration scenario according to an embodiment of the present application;

FIG. 5 is a schematic diagram of a collaborative proposal in a task processing method according to an embodiment of the present application;

FIG. 6 is a schematic diagram of a task processing device according to an embodiment of the present application;

FIG. 7 is a block diagram of a computing device according to one embodiment of the application.

Detailed Description

In the following description, numerous specific details are set forth in order to provide a thorough understanding of the present application. The present application may be embodied in many other forms than those herein described, and those skilled in the art will readily appreciate that the present application may be similarly embodied without departing from the spirit or essential characteristics thereof, and therefore the present application is not limited to the specific embodiments disclosed below.

The terminology used in the one or more embodiments of the application is for the purpose of describing particular embodiments only and is not intended to be limiting of the one or more embodiments of the application. As used in one or more embodiments of the application and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used in one or more embodiments of the present application refers to and encompasses any or all possible combinations of one or more of the associated listed items.

It should be understood that, although the terms first, second, etc. may be used in one or more embodiments of the application to describe various information, these information should not be limited by these terms. These terms are only used to distinguish one type of information from another. For example, a first may also be referred to as a second, and similarly, a second may also be referred to as a first, without departing from the scope of one or more embodiments of the application. The word "if" as used herein may be interpreted as "at … …" or "at … …" or "in response to a determination" depending on the context.

First, terms related to one or more embodiments of the present application will be explained.

UP master (uplink): refers to a person uploading video and audio files at a video website, forum, ftp site.

In the present application, a task processing method is provided, and the present application relates to a task processing device, a computing device, and a computer-readable storage medium, which are described in detail in the following embodiments one by one.

In a practical scenario, the collaboration flow is completely closed because when two or more collaborators decide to collaborate. I.e., the partner does not disclose the process of pre-collaboration, the user cannot participate in the collaboration process. The influence of cooperation on the public can only be generated after the cooperation products (such as cooperation works or cooperation products) are online, and the cooperation effect cannot be predicted in advance, so that a certain obstruction is caused to the scale and interactivity of the cooperation. Further, since the cooperators belong to different fields, the risk of the cooperation is greater, and thus, the prediction requirement on the cooperation prospect is greater.

In view of the above, the task processing method provided by the application realizes that users participate in the task processing method in a target task mode before cooperation, influences the public in a target task interaction mode, predicts the cooperation effect of the target task through the statistical result, assists the task participants to determine the cooperation prospect according to the prediction result, and cooperates based on the cooperation prospect, so that the success of cooperation is more ensured.

Fig. 1 shows a flowchart of a task processing method according to an embodiment of the present application, which specifically includes the following steps:

step 102: and receiving a task creation request submitted by the task request terminal.

The task request terminal refers to a terminal device that requests to create a target task, and in practical application, a task requester (a task participant that requests to create the target task) may submit a task creation request through the terminal device, where the terminal device may be an intelligent device such as a mobile phone, a tablet computer, or a desktop computer, and is not limited herein. Accordingly, the task creation request refers to a request for creating a target task, in practical application, a task requester inputs corresponding task information through a task template provided by a platform (a video platform, a music platform, a game platform, a live broadcast platform and the like) running in a task request terminal, and submits a creation request (i.e., a task creation request) for the target task based on the task information. The target task is a proposal which is proposed by a pointer to task assumptions (such as task objects, task forms or ideas) among task participants involved in the task.

In practical applications, some task participants perform task processing, mostly based on task assumptions achieved between the task participants. But before a task product, such as a movie work, a music work, an advertisement work, etc., or a task product is made available, it is not determined whether the user likes the task. I.e. it is not clear whether the user supports or does not support the task performed between these task participants. Therefore, the reverberation of the user after the task work or the task product is presented by the task participant cannot be accurately predicted, i.e. the task effect cannot be accurately predicted.

According to the embodiment of the application, through the mode of issuing the target task, the suggestion of the user on the target task is firstly solicited, and then based on the suggestion of the user, whether to formally start the task or in which mode to perform the task is determined, so that the condition that the user is unsatisfied with the task effect can be avoided to a great extent; the influence of the task can be released in advance by releasing the target task.

Taking the target task as a collaborative proposal as an example: and receiving a submitted collaborative proposal creation request 1 from the UP master A through the task request terminal video platform A.

Step 104: and creating a target task based on the task information carried in the task creation request and issuing the target task.

At least two task participants contained in the task information belong to different service fields.

Specifically, on the basis of the above received task creation request, it is necessary to create a target task based on the task information carried in the task creation request. The task information includes information of a task participant of the target task, and may further include information related to the task, such as a task target, task details, and the like, which is not limited herein. And considering that if only the target task is created, but the user cannot see the target task, the attitude or suggestion of the user to the target task cannot be known, and therefore the created target task also needs to be issued on the basis of creating the target task.

The task participant may be a brand, factory, public institution, group, star, etc., and is not limited herein; the number of task participants may be two or more, and at least two of the task participants belong to different business domains. For example, one task participant is an enterprise, another task participant is a star, both belong to different business fields, or one business participant is a teacher engaged in the education industry, and another task participant is a star engaged in the entertainment industry, both also belong to different business fields.

In practical applications, the task information provided by the task requester may be information in the form of text, picture, audio and/or video, etc., so that the display form of the created target task may also be various, for example, the target task may be displayed in the form of video, or in the form of picture and text, or in the form of audio, which is not limited herein.

The publishing of the created target task on the basis of creating the target task means that the target task is published through a network, and in practical application, the publishing of the target task in a popup window in an application program of a client, or the publishing of the target task through a webpage, etc., are not limited herein.

In specific implementation, considering that the release modes which can be adopted for releasing the target task may be various, and different target tasks may have different release requirements, in order to ensure the flexibility of the release modes of the target task, the release modes can be preconfigured according to actual needs, and then the target task is released according to the configured release modes, and the embodiment of the application is realized by adopting the following specific modes:

Creating a target task based on task information carried in the task creation request;

and publishing the target task according to a pre-configured publishing mode.

The publishing mode can be understood as a publishing channel, can be preconfigured for a single task, can be preconfigured for tasks with specific attributes, can be set for all created tasks, can be preconfigured by a task requester, and can be preconfigured by a platform, and is not limited herein. In practical application, the target task is published according to a pre-configured publishing mode, so that the publishing requirement of a task requester on the target task can be met.

Along the above example, upon receiving the collaborative proposal creation request 1, proposal information carried in the collaborative proposal creation request 1 includes: partner (UP main a and star B), details of the partner (the presentation of the details is video), options of the partner (support of the partner and opposition to the options of the partner). Creating a collaborative proposal 1 based on the proposal information, wherein proposal content of the collaborative proposal 1 comprises an UP main A and a star B, collaboration details, support collaboration options and anti-collaboration options, and further comprises quotation for attracting a user to discuss the collaborative proposal 1: "how you expect to see the immortal combination", and then the created collaborative proposal 1 is distributed according to the distribution mode set by the user: release is performed in a popup window format in video applications.

In sum, after the target task is created, the target task is published according to a pre-configured publishing mode, so that the pre-setting of the publishing mode is realized, and the flexibility and diversity of publishing are increased.

Further, in order to further increase diversity of the publishing modes, one of the publishing modes may be selected, or a mode of combining the publishing modes may be adopted to publish the target task, and in the embodiment of the present application, the following 4 modes or a combination of the 4 modes are specifically adopted to implement:

1) And publishing the target task on the active page of the target application.

The target application may be an application or a platform where the user submits the task creation request, and in addition, the target application may also be an application or a platform different from the application where the user submits the task creation request, which is not limited herein. Accordingly, an active page refers to a page that displays an activity. The target task is displayed on the activity page, namely the target task is displayed as an activity which can be participated by a user.

Along with the above example, on the basis of creating the collaborative proposal 1 described above, an active page of the video application is determined, and the release of the collaborative proposal 1 is completed by updating the active page based on the collaborative proposal 1. When the client opens the APP, the active page containing the collaborative proposal 1 is displayed on the opening page, so that a user can conveniently enter the active page and participate in the discussion of the collaborative proposal 1 and the selection of supporting or not supporting the collaborative proposal 1.

2) And publishing the target task on a homepage of a task participant.

Wherein the task participants refer to the cooperative objects involved in the target task. For example, if the target task is a proposal for the UP master a and the star B to cooperate, the UP master a and the star B are both task participants of the target task. Accordingly, the homepage may be understood as a page of a task participant that presents published information in a target application (which may be any application, without limitation herein), and may be accessed by other users.

Along the above example, on the basis of the above creation of the collaborative proposal 1, the homepage corresponding to the UP main a is determined. And issues the collaborative proposal 1 by updating it to the home page of the UP main a in the video application. After release, after the client enters the homepage of the UP master A, the user can watch the cooperative proposal 1 in the homepage and participate in the discussion of the cooperative proposal 1 and the selection of supporting or not supporting the cooperative proposal 1.

3) And publishing the target task in a display area pointed by a target navigation bar in the target application.

The display area pointed by the target navigation bar can be understood as an interface area navigated after clicking a certain navigation bar, in practical application, one or more display areas corresponding to the navigation bars can display the issued target task, and the navigation bar used for displaying the target task in the corresponding display area is the target navigation bar.

Along with the above example, on the basis of creating the collaborative proposal 1, determining the target navigation bar corresponding to the collaborative proposal 1 and the display area pointed to by the target navigation bar, and publishing the collaborative proposal 1 by updating the collaborative proposal 1 to the display area corresponding to the target navigation bar in the video application. After release, when the client clicks the target navigation bar, the loaded collaborative proposal 1 is added into a typesetting template corresponding to the target navigation bar, a display interface containing the collaborative proposal 1 is generated, a user can conveniently select to watch the collaborative proposal 1 in the display interface, and the user participates in the discussion of the collaborative proposal 1 and the selection of supporting or not supporting the collaborative proposal 1.

4) And under the condition that a published task set corresponding to a task participant in the target task is not empty, completing the publication of the target task by updating the published tasks in the published task set based on the target task.

The published task set refers to a set formed by tasks (published tasks) which are published by any task participant. In practical applications, tasks issued by the same task participant are generally issued on the same page or in the same way, so that the issuing of the target task can be completed by updating the newly created target task to the issued task.

Along the above example, on the basis of creating the collaborative proposal 1, it is determined that the collaborative proposal that the UP master a has issued includes 3 collaborative proposals, and these 3 collaborative proposals are issued in the same popup window in the target application, so that adding the collaborative proposal 1 to these 3 collaborative proposals, the collaborative proposal 1 will issue in the popup window as well. After release, the user can view the 4 collaborative proposals in turn when viewing the popup window, and participate in the discussion of each collaborative proposal and the selection of supporting or not supporting each collaborative proposal.

In summary, the target task is released in the active page, the homepage of the task participant, the display area pointed by the target navigation bar and/or the released task, so that the exposure of the target task is increased, and the flexibility of releasing the target task is also increased.

In practical application, considering that if a task requester submits a target task without obtaining agreements of other task participants, but other task participants in the target task do not know or agree with the proposal, and cannot cooperate, after the target task is created, the target task can be reissued after obtaining agreements of other task participants on the target task, and the embodiment of the application is implemented in the following manner:

The target task is sent to a target task participation terminal of the target task;

and under the condition that an approval instruction submitted by the target task participation terminal aiming at the target task is received, issuing the target task.

The target task participants of the target task specifically refer to at least one task participant except the task requesting party in the task participants of the target task. Correspondingly, the consent instruction refers to an instruction for identifying the target task, and in practical application, the consent instruction submitted by the target task participant for the target task is received, which indicates that the target task participant agrees with the proposal content in the target task.

Along with the above example, on the basis of creating the cooperation proposal 1, the cooperation proposal 1 is transmitted to the star B, and when receiving the approval instruction submitted by the star B for the cooperation proposal 1, the cooperation proposal 1 is issued.

In conclusion, under the condition that an approval instruction submitted by a target task participant to the target task is received, the target task is reissued, and the effectiveness of the target task is ensured.

In particular, since numerous tasks may have been published in the platform, if these published tasks (published tasks) are presented at various locations, users that are not interested in this portion of content may have to filter this information themselves while browsing the page. The user interested in the part of the content needs to find the issued task everywhere and then watch the issued task, so that the issued task can be displayed to the user in a list form for facilitating the user to watch and process the part of the information, and the embodiment of the application is realized in the following way:

receiving a watching request submitted by a browsing terminal aiming at a published task;

responding to the watching request, and sending a task list corresponding to the issued task to the browsing terminal; the issued tasks in the task list are displayed in sequence according to the operation instructions received by the browsing terminal.

The browsing terminal refers to terminal equipment used by a browsing user who browses the published tasks. The task list refers to a list containing at least two published tasks. Correspondingly, the operation instruction received by the browsing terminal comprises an operation instruction which supports or does not support processing of the issued task submitted by the browsing user through the browsing terminal, and in practical application, after the browsing user sends a viewing request to the server by clicking a viewing control corresponding to the issued task displayed in the browsing terminal, the server receives the viewing request, and responds to the viewing request, sends a task list to the browsing terminal, so that the browsing user can browse or process the issued task in the task list sequentially. Specifically, after the browsing user clicks the support or objection option on the first published task displayed in the task list, the second published task in the task list is displayed to the browsing user.

In addition, the published tasks contained in the task list can be selected according to the attribute information/history behavior and other information of the browsing user, namely, the published task creation task list with higher relevancy of the browsing user is selected, so that the exposure rate of different published tasks is improved, and the processing interest of the user on the published tasks is improved. In the implementation, which content is more interested by the browsing user can be determined according to the historical behavior analysis of the browsing user, and then the similarity calculation is performed on the keywords related to the part of content and the keywords in the published tasks, so that the relevance is determined.

Assume that: the task list is a proposal list composed of published cooperation proposals, the proposal list comprises 3 published cooperation proposals, wherein the cooperation proposal 1 is the first published cooperation proposal in the proposal list, when any user clicks a support cooperation option or an anti-cooperation option on the cooperation proposal 1 through a browsing terminal, the user indicates that the user finishes processing the cooperation proposal 1, the next published cooperation proposal in the proposal list is displayed to the user, so that the user can watch and continuously watch or process the published cooperation proposal, and the user can rapidly finish watching and processing all the published cooperation proposals in the proposal list by the pushing.

It should be noted that, the browsing user may also close or view the task list, so that the user may choose not to view or process the published proposal.

In sum, when the browsing user views the published tasks through the browsing terminal, the browsing user can browse and process the published tasks in the published list in sequence, and the processing efficiency of the browsing user on the published tasks is improved. And the browsing of the published tasks by the browsing user is facilitated.

In practical application, after issuing a target task, some users may not agree with the target task, and consider that other tasks such as the target task is better are present, so that in order to enable the users to freely express their views on the target task, the users may be allowed to submit the tasks considered to be better on the basis of the target task, and the embodiment of the present application is implemented in the following manner:

Receiving a user task submitted by a user terminal aiming at the target task;

And publishing the user task according to a user publishing mode corresponding to the target task.

The user terminal may be any terminal device used by a user, and is not limited herein. Accordingly, the user task refers to a task of changing suggestions proposed by the user for contents such as a task participant or a task participation mode in the target task on the basis of the target task.

In the implementation, because the user task and the target task have an association relationship, in order to enable other users to see the target task and see the corresponding user task, the user task can be issued according to the user issuing mode corresponding to the target task. The user publishing mode is a publishing mode set by a pointer to the user task, and specifically, due to the association relationship, the user publishing mode is generally the same as or similar to the publishing mode of the target task so as to display the user task in an area near the target task.

Along the above example, the user U1 is received for the user cooperation proposal 1 of the cooperation proposal 1, and the user U1 cooperation proposal 1 suggests cooperation by the UP master a and the UP master C. When the user distribution method is an area immediately below the distribution method of the collaborative proposal 1, the user collaborative proposal 1 is distributed immediately below the collaborative proposal 1.

In summary, after the target task is released, the user task submitted by the user aiming at the target task is received and released, so that the task participants and other users can know the target task except the target task, the interestingness of the target task is increased, and the cooperative ideas of the task participants on the target task are expanded.

Based on the above-mentioned user task publishing, if it is only published, it is impossible for other users or task participants to compare the user task with the target task, so that a voting interface for the user task can be provided, so that the cooperative effect of the user task is further predicted based on voting information.

Counting user votes submitted by a user voting terminal aiming at the user tasks;

And updating and releasing the user tasks and the user task sequencing list based on the statistical result.

The user voting terminal refers to terminal equipment used by any user when voting on a user task. Accordingly, user votes include support votes submitted for the user task (e.g., favorites votes representing support, endorsements, support information, etc.), and may also include anti-votes submitted for the user task (e.g., unsupported votes representing anti-slip, anti-slip information, etc.).

After each user vote submitted by a user is received, statistics is performed on the user vote (such as counting the number of votes supported in the user vote), and the user task is updated according to the statistics result, so that the task participant and the user can know the support and/or objection of other users to the user task.

Further, the user task ordering list is updated based on the statistical result, where the user task ordering list refers to a list generated according to the ordering result after the user tasks are ordered based on the support votes or the objections votes, and in practical application, the user tasks with the highest support votes in a preset number (such as 3, 10, etc.) can be displayed in the list.

Along the above example, on the basis of issuing the user cooperation proposal 1, the support vote or the objection vote submitted by the user voting terminal to the user cooperation proposal 1 is received. When the current support vote of the user cooperation proposal 1 is 200, the support vote 200 is issued as a statistical result in the proposal room. And according to the statistical result, the 15 user cooperation proposals are reordered according to the number of support votes of the 15 user cooperation proposals corresponding to the cooperation proposal 1. Specifically, as shown in fig. 2, in the case that the user collaborative proposal with the number of supporting votes being in the top 5 is shown in the high-vote proposal list (i.e., the user task list), the high-vote proposal list is updated based on the reordered result, wherein the number of people second a motion in fig. 2 represents the number of people submitting supporting votes, and if the user wants to submit the user collaborative proposal for the collaborative proposal 1, the user can select the "me proposal" control in the extreme proposal room to submit a new user collaborative proposal based on the collaborative proposal 1.

In summary, on the basis of issuing user tasks, user votes for the user tasks are received and counted, statistical results are issued, and a user task list is updated and issued again based on the statistical results, so that the participation of users is improved through proposal and voting, and the user tasks of target tasks are ordered and displayed by each user through updating and issuing the user task list, so that the proposal of the task participants for the user liking is clear at a glance, and the adjustment of the target tasks corresponding to the voting results is facilitated.

On the basis of publishing the user task, although the user or the task participant can see the user task, the user or the task participant still cannot conveniently discuss the user task and friends, so that a user task sharing mode can be adopted, and the convenience and easiness in discussing the user task among users are improved.

Receiving a sharing instruction submitted for an issued user task, wherein the sharing instruction carries user information and user task information;

and determining the user task based on the user task information and sending the user task to a sharing user corresponding to the user information.

The sharing instruction refers to an instruction for indicating to share the user task, and in practical application, the sharing instruction carries user information and user task information corresponding to the target task. Specifically, the user information refers to user information of the shared user, such as a user name, a user identifier, a user sharing manner, and the like. The user task information refers to information that can uniquely identify a user task, such as a proposal name or a proposal identifier.

Along the above example, on the basis that the user cooperation proposal 1 is to be issued, a sharing instruction of the user U3 to the user cooperation proposal 1 is received, where the sharing instruction carries a user identifier "U4" and a proposal identifier "user cooperation proposal 1". Based on the user identification "U4", the user U4 is determined as a shared user, and based on the "user cooperation proposal 1", the user cooperation proposal 1 is determined and acquired, and the user cooperation proposal 1 is sent to the user U4.

In summary, the user tasks are shared, so that users can conveniently discuss based on the user tasks, the favorite user tasks can be conveniently shared with other people, the support of other users on the user tasks is obtained, and the interactivity among users is enhanced.

Step 106: and counting task votes submitted by the voting terminal aiming at the issued target task, and determining an initial task execution result of the target task based on the task voting statistical result.

Specifically, on the basis of the release of the target task, if the user only sees the target task or cannot support or not support the target task, a voting interface or a voting option for submitting the task vote for the target task is provided for the voting terminal, so that the user can vote for the target task, and an initial task execution result of the target task is determined based on the statistics results of the task votes.

The voting terminal is terminal equipment used by a user for voting the target task by the pointer; accordingly, task votes may include support votes (e.g., votes representing support, acceptance, or liking of the target task) and anti-votes (e.g., votes representing anti-objection, non-acceptance, or disliking of the target task), neutral votes, and the like, without limitation. Accordingly, the task voting statistical result refers to a result obtained by counting the number of votes (such as supporting votes and/or anti-votes) of at least one type of votes in the task votes of the target task after the votes are cut off. Accordingly, the initial task execution result refers to an initial intention of implementing the target task, and specifically, the initial task support result may include success of task execution and failure of task execution. The successful execution of the task indicates that the initial execution of the target task is decided to continue to implement the target task, and the failure of the task execution indicates that the initial execution of the target task is decided to not continue to implement the target task. In practical applications, the initial task execution result is not the final result, which indicates that it is possible to change the execution result of the target task, or change or adjust the task content in the target task based on other information.

In practice, statistics of task votes for a target task may be triggered each time a task vote submitted by a user for the target task is received, or at intervals (e.g., 5 minutes).

Along the above example, on the basis of issuing the collaborative proposal 1, the support votes submitted by the user U5 for the collaborative proposal 1 are received, statistics is performed on the support number of the support votes of the collaborative proposal 1 in real time based on the received support votes, the statistical result is obtained to be that the support number reaches 80% of the preset support vote number, and the support vote number of the collaborative proposal 1 is updated according to the real-time statistical result, so that other users can conveniently know the support and objection conditions for the collaborative proposal 1, and the other users can make support or non-support votes according to the information.

Specifically, as shown in fig. 3, the published collaborative proposal 1 is shown in a video manner, and the video content includes a detailed description of the collaborative proposal 1 by the UP main a and the star B. And two options are provided to the user based on the collaboration offer 1: support the collaboration option and objection the collaboration option. In addition, the percentage between the number of votes supported by the collaborative proposal 1 and the preset number of votes supported is displayed in a progress bar manner, and the display progress of the progress bar reflects the support degree of the collaborative proposal 1 by the user. After the voting is finished, if the percentage does not reach the threshold value, which indicates that the cooperation is performed before Jing Jiaocha of the cooperation proposal 1, the initial cooperation result of the cooperation proposal 1 is confirmed as the cooperation failure; if the percentage reaches the threshold value, the initial cooperation result of the cooperation proposal 1 is confirmed as successful cooperation, wherein the cooperation prospect of the cooperation proposal 1 is good.

In the specific implementation, considering that if the voting cut-off condition is not set, the target task is continuously voted, even if the task voting statistical result is obtained, the voting cut-off condition has no reference value, so that in order to ensure the accuracy of the initial task execution result, a reasonable voting cut-off condition, namely, a task end condition needs to be set for the target task, and the embodiment of the application further comprises:

detecting whether the target task meets a task ending condition;

If yes, the step of determining the initial task execution result of the target task based on the task voting statistical result is executed.

Specifically, on the basis of the statistics task voting, a task ending condition is preset for the target task, and under the condition that the target task meets the task ending condition, the task execution is indicated to be completed, and the initial task execution result of the target task is directly determined based on the statistics result.

In practical application, considering that the quality of the task end condition setting directly affects the quality of the prediction of the effect of the job, in order to ensure the accuracy of the prediction of the effect of the job, the embodiment of the application can set the task end condition in the following 3 modes:

1) And counting the number of votes supporting the votes in the task votes to reach the preset number of supporting the votes.

The preset number of support votes refers to the preset number of support votes, and when the method is implemented, the number of support votes in the task votes for the target task reaches the preset number of support votes, which indicates that enough users support the target task. In this case, the initial task execution result of the target task may be directly determined based on the task voting statistical result.

2) And counting the number of the votes of the task votes to reach the preset number of votes.

The preset voting number refers to the voting number of task votes, and when the voting number of the task votes reaches the preset voting number in specific implementation, the preset voting number indicates that enough users see the target task and expresses the supporting or non-supporting attitude of the target task. In this case, the initial task execution result of the target task may be directly determined based on the task vote statistical result.

3) The release time length of releasing the target task meets the preset time length.

The preset duration refers to the preset longest voting time, and when the release duration satisfies the preset duration, the preset duration indicates that the target task has been voted for a long enough time, and in this case, the initial task execution result of the target task may also be directly determined based on the task voting statistical result.

In summary, by setting the task ending condition, the task participant may obtain analysis information for the target task, such as whether there are a sufficient number of users supporting the target task, or whether the user's attention to the target task is sufficient, so as to more accurately determine the initial task execution result of the target task.

In specific implementation, after the task is finished, whether the implementation of the target task is to be continued is determined according to the task voting statistical result, so how to determine whether the implementation of the target task is to be continued based on the statistical result is critical to the prediction of the task effect, and in order to improve the accuracy of the task effect prediction, the embodiment of the application is realized in the following manner:

judging whether the counted number of the votes supporting the votes in the task votes reaches the preset supporting number of the votes;

If yes, indicating that the number of votes supporting the target task reaches the expectation, and determining that the initial task execution result of the target task is successful task execution;

If not, indicating that the number of votes supporting the target task does not reach the expectation, and determining the initial task execution result of the target task as the task execution failure.

Along with the above example, under the condition that the release duration of the cooperative proposal 1 in the video application reaches the preset duration for 30 days, counting the number of the supporting information in the task vote of the cooperative proposal 1 to be 6 ten thousand, judging whether the number of the supporting information in the task vote of the cooperative proposal 1 reaches 5 ten thousand, if so, determining that the initial task execution result of the cooperative proposal 1 is successful.

In summary, whether to continue to implement the target task is determined by judging whether the number of votes for supporting the target task is enough, so that after the task works are presented after the task is implemented, enough user groups are supported, and in this case, the initial task execution result of the target task is determined to be successful in task execution, and good task effect is ensured after the target task is executed.

Step 108: and under the condition that the initial task execution result is that the task execution is successful, sending task participation information to each task participant.

Specifically, if the initial task execution result is that the task execution is successful, if no task participant feeds back the result, the target task may be continuously implemented, and in order to ensure the validity of the initial task execution result, the user is required to feed back the result, so that task participation information is sent to each task participant.

The task participation information refers to information that a task participant notifying a target task participates in the target task, and may also be understood as notification reminding for an initial task execution result.

On the basis of sending task participation information to each task participant, further, determining a target task execution result of a target task according to feedback information submitted by the task participant for the task participation information, and further comprising:

and determining a target task execution result of the target task based on feedback information submitted by each task participation terminal aiming at the task participation information.

The feedback information is feedback information indicating whether the initial task execution result of the target task is agreed or not. In practical application, if each task participant agrees with the initial task execution result to indicate that the target task is met, determining that the target task execution result of the target task is successful task execution; if any task participant does not agree with the initial task execution result, that is, feedback is not performed on the task participation information, or the task participation information is returned with disagreement information, which indicates that the target task is not satisfied, determining that the target task execution result of the target task is a task execution failure.

Along the above example, when it is determined that the initial task execution result of the cooperative proposal 1 is successful task execution, the task participation information for the cooperative proposal 1 is sent to the UP main a and the star B, and when both feedback information for the task participation information is received, it is determined that the target task execution result of the cooperative proposal 1 is successful task execution.

In conclusion, based on feedback information submitted by each task participant to the task participation information, the target task execution result of the target task is determined, so that the effectiveness of the target task execution result is ensured, and the rights and interests of the task participants are further ensured.

Under the condition that the execution result of the target task is that the task execution is successful, if the task progress is not externally published during the subsequent implementation of the target task, the expectation of a user on the target task is easily lost, so that the task progress is required to be published so as to generate continuous influence on the user.

Issuing a task progress notification based on the target task under the condition that the target task execution result is that the task execution is successful;

receiving progress information submitted by a task participation terminal aiming at the task progress notification;

And changing and issuing the task progress notification based on the progress information.

The task progress notification refers to a notification indicating the task progress, and specifically, the task progress notification may include the progress of completed tasks, the progress of incomplete tasks, and/or the percentage of the task progress. In practical application, in order to enable the task progress in the task progress notification to be updated in time, progress information submitted by the task progress notification can be changed and issued based on any task participant. The user concerned with the target task can also know the cooperation progress of the change in time.

Along the above example, when it is determined that the target task execution result of the collaborative proposal 1 is successful in task execution, a task progress notification is issued based on the collaborative proposal 1, and the task progress notification specifically includes 3 progress: the method comprises the steps of determining a subject, completing production and appearing, and starting the task progress notification release, wherein the task progress is empty, and the progress information submitted by the UP main A or the Star B for the task progress notification is received as follows: when the material is determined, the task progress in the task progress notification is changed to the determined material, and the task progress notification after the change is issued.

In summary, when the target task execution result is that the task execution is successful, the task progress notification is issued based on the target task, and the issued task progress notification is updated based on the progress information submitted by the task participant, so that the user focusing on the target task can timely acquire the changed task progress based on the task progress notification, and the participation of the user in the target task implementation process is increased.

In practical application, although the task progress notification is issued, the user may not notice the task progress notification, and may miss the time of the appearance of the task work/product, so that after the task work/product is appeared, the user who focuses on the target task can be reminded, and the embodiment of the application is realized in the following manner:

Receiving a reservation request submitted by a reservation terminal through the task progress notification;

Based on the reservation request, establishing a reservation association relationship between a reservation user corresponding to the reservation terminal and the target task;

feeding back a reservation success reminder to the reservation terminal;

And sending a task completion reminder to a reservation user with reservation association relation with the target task under the condition that the task progress in the task progress notification is changed to completion.

The reservation terminal refers to terminal equipment for submitting a reservation request, and accordingly, the reservation request refers to an appearance reservation request of a task work/product of a target task. The user of the reservation terminal (i.e. the user submitting the reservation request) is the reservation user. In practical application, a direct reservation association relation between a reservation user and a target task is required to be established, so that the user can accurately know which users submit reservation requests, the reservation association relation is established, the reservation user is indicated to reserve successfully, and a reservation success prompt is fed back to the reservation user. Specifically, the reservation success alert may include an information representation indicating that the reservation was successful.

Based on the above, when the task progress in the task progress notification is changed to completion, it is indicated that the task work/product has been made available, and a collaboration completion reminder is sent to all reservation users who establish an association relationship with the target task, so as to remind the reservation users to pay attention to the task work/product that has been made available.

Along the above example, receiving a reservation request submitted by a user U6 for task progress notification through a reservation terminal, establishing a reservation association relationship between the user U6 and the cooperation proposal 1 based on the reservation request, returning a reservation success reminder to the reservation terminal, and sending a cooperation completion reminder to a reservation user having a reservation association relationship with the cooperation proposal 1, including the user U6, under the condition that the cooperation progress change is completed: "the collaborative work corresponding to collaborative proposal 1 has been made, please click on the link to jump to the collaborative work".

In summary, when the task progress is changed to completion, a task completion reminder is sent to the reservation user, so that the reservation user pays attention to the appearing task works/products in time.

In summary, by receiving a task creation request submitted by a task request terminal, creating and publishing a target task based on task information carried in the task creation request, wherein at least two task participants included in the task information belong to different service fields, and publishing of target tasks participated by task participants not belonging to the same service field is achieved. And then counting task votes submitted by the voting terminal aiming at the issued target task, determining an initial task execution result of the target task based on the task voting counting result, enabling a user to participate in the target task by issuing the target task, counting task votes of the user on the target task, realizing interaction between the user and the target task, and predicting the cooperation effect of the target task according to the counting result, and sending task participation information to each task participant under the condition that the task execution result is successful in executing the initial task, thereby realizing task prospect of the target task to be determined by the task participant according to the prediction result, so that the task participant can determine whether to continue to implement the target task based on the task prospect, and ensuring the success of the target task.

The task processing method provided by the application is further described below by taking the application of the task processing method in a cooperation scene as an example with reference to fig. 4. Fig. 4 shows a process flow chart of a task processing method applied to a collaboration scenario according to an embodiment of the present application, which specifically includes the following steps:

step 402: and receiving a collaborative proposal creation request submitted by the collaborative request terminal.

Specifically, the cooperation request terminal is a terminal device used by a task requester, the task requester is a brand side b1, and a cooperation proposal creation request 2 which is submitted by the brand side b1 through the cooperation request terminal and cooperates with a star small U is received, wherein the brand side b1 and the star small U are cooperation parties in different service fields.

Step 404: and creating the collaborative proposal based on proposal information carried in the collaborative proposal creation request.

Specifically, the collaborative proposal 2 is created based on the collaborative proposal creation request 2 submitted by the brand party b 1.

Step 406: the collaborative proposal is sent to a target collaborative party of the collaborative proposal.

Specifically, the collaborative proposal 2 is sent to the star small U.

Step 408: and when receiving an agreement instruction submitted by the target partner for the cooperation proposal, issuing the cooperation proposal on an active page of the target application.

Specifically, when receiving the consent instruction submitted by the star U to the collaborative proposal 2, the collaborative proposal 2 is also published in the activity of the video application, specifically, the published collaborative proposal 2 is shown in fig. 5 (a), and the activity page in fig. 5 (a) includes: "what is you expecting to see the immortal combination? "title and video presentation of the collaborative proposal 2.

Step 410: the statistical voting terminal performs proposal voting aiming at the issued collaborative proposal.

Specifically, as shown in fig. 5 (a), the active page further includes two proposal options for the collaborative proposal 2 provided for the user: "support collaboration" and "counter collaboration". Conditions for starting collaboration: "10 ten thousand people can open the cooperation.

The method comprises the steps of receiving support votes submitted by users for support cooperative options corresponding to the cooperative proposal through a voting terminal or anti-votes submitted for the cooperative options, counting the number of the support votes submitted for the cooperative proposal 2 to be 8 thousands and the number of the anti-votes to be 6 thousands, wherein when the number of the support votes is 10 thousands in the case of preset starting cooperation, the whole progress bar represents the total number of the preset support votes to be 10 thousands, and when the number of the support votes is 8 thousands, the current progress bar of the number of the support votes reaches 80%.

In practical application, as shown in fig. 5 (b), the user may also click "+ create a fantasy combination" control under the active page to submit the user collaboration proposal that the user wants to see, and specifically, the current proposal room includes: the user cooperation proposal a, the user cooperation proposal b, the user cooperation proposal c and the user cooperation proposal d, and the voting control for each user cooperation proposal can vote for the user favorite user cooperation proposal.

Step 412: judging whether the number of support votes for supporting the votes in the counted proposal votes reaches the preset number of support votes or not under the condition that the number of votes for counting the proposal votes reaches the preset number of votes;

If yes, indicating that the number of support votes supporting the collaborative proposal is expected, then the following step 414 is performed;

If not, the number of support votes supporting the cooperation proposal does not reach the expectation, and the initial cooperation result of the cooperation proposal is determined to be the cooperation failure.

Specifically, in the continuous statistics process, if the sum of the number of support votes and the number of countervotes of the collaborative proposal 2 reaches 13 ten thousand (the preset number of votes), the number of support votes of the collaborative proposal 2 is counted to reach 10 ten thousand, and step 414 is executed.

Wherein 13 ten thousand is a preset number of votes, which also represents the number of persons participating in voting on the composite proposal 2. 10 ten thousand is a preset number of support votes, which indicates the number of people supporting the collaborative proposal 2, and specifically, the two values may be preset by the brand party b1 or the star U.

Step 414: and determining the initial cooperation result of the cooperation proposal as successful cooperation.

Specifically, the initial cooperation result of the cooperation proposal 2 is determined as successful cooperation.

Step 416: and sending the cooperation participation information to each partner in the cooperation proposal.

Specifically, the cooperation participation information for the cooperation proposal 2 is transmitted to the brand party b1 and the star U.

Step 418: and determining a target cooperation result of the cooperation proposal based on feedback information submitted by each partner for the cooperation participation information.

Specifically, when feedback information of the cooperation participation information for the cooperation proposal 2 is transmitted to the brand party b1 and the star U, the final cooperation result of the cooperation proposal 2 is determined to be successful.

Assuming that feedback information of any partner for the cooperation participation information of the cooperation proposal 2 is refusal, determining that the final cooperation result of the cooperation proposal 2 is a cooperation failure.

Step 420: and under the condition that the target cooperation result is that the cooperation is successful, issuing a cooperation progress notification based on the cooperation proposal.

Specifically, in the case where the final cooperation result of the cooperation proposal 2 is that the cooperation is successful, a cooperation progress notification is issued based on the cooperation proposal 2, the cooperation progress notification including, as shown in fig. 5 (c): 3 schedules: the materials, the manufacturing completion and the appearance are determined.

Step 422: and receiving progress information submitted by the partner for the cooperation progress notification.

In practical application, the partner may be any one partner.

Specifically, the progress information submitted by the receiving brand party b1 for the cooperation progress notification is the completion of the production.

Step 424: and changing and issuing the synthesis progress notification based on the progress information.

Specifically, based on progress information: after the completion of the production, the progress notification of the cooperation is updated and released, and the released progress notification of the cooperation is as shown in fig. 5 (c), and the updated progress of the cooperation reaches 80% of the whole progress of the cooperation.

Step 426: and receiving a reservation request submitted by the reservation terminal based on the cooperation progress notification.

Specifically, as shown in fig. 5 (c), the collaboration progress notification page further includes a reservation control, and a reservation request submitted by a reservation user via a reservation terminal based on the reservation control corresponding to the collaboration progress notification is received.

Step 428: and establishing a reservation association relationship between the reservation user corresponding to the reservation terminal and the cooperation proposal based on the reservation request.

Specifically, based on the reservation request, a reservation association relationship between the reservation user's reddish and the collaborative proposal 2 is established.

Step 430: and feeding back a reservation success reminder to the reservation terminal.

Specifically, on the basis of establishing the reservation association relationship, a reservation success reminder is returned to the reservation terminal.

Step 432: and when the cooperation progress change in the cooperation progress notification is completed, sending a cooperation completion prompt to a reservation user with a reservation association relationship with the cooperation proposal.

Specifically, in the case where the cooperation progress change in the cooperation vertex notification is made, a cooperation completion reminder is sent to all users who submit reservation requests for the task progress notification (including the reservation users in reddish).

In summary, on the basis of submitting the request for creating the collaborative proposal, the collaborative proposal is created and issued, so that the user selects whether the issued collaborative proposal is supported or not, when the number of supporters of the collaborative proposal reaches the number of supporters set by brands or stars U, the platform Fang Duige acts as both parties to send out the information of collaborative participation, thereby facilitating the collaboration, ensuring the accuracy of predicting the collaborative effect and ensuring the effectiveness of the collaboration.

Corresponding to the method embodiment, the present application further provides a task processing device embodiment, and fig. 6 shows a schematic structural diagram of a task processing device according to an embodiment of the present application. As shown in fig. 6, the apparatus includes:

a receiving module 602, configured to receive a task creation request submitted by a task request terminal;

the publishing module 604 is configured to create and publish a target task based on task information carried in the task creation request, wherein at least two task participants contained in the task information belong to different task fields;

A statistics module 606 configured to count task votes submitted by the voting terminal for the issued target task, and determine an initial task execution result of the target task based on the task vote statistics result;

And the sending module 608 is configured to send task participation information to each task participant in the case that the initial task execution result is that the task execution is successful.

The statistics module 606 is further configured to:

If yes, determining that the initial task execution result of the target task is successful task execution;

If not, determining the initial task execution result of the target task as the task execution failure.

Optionally, the task processing device further includes:

and the determining result module is configured to determine a target task execution result of the target task based on feedback information submitted by each task participation terminal aiming at the task participation information.

Optionally, the task processing device further includes:

The sending notification module is configured to issue a task progress notification based on the target task when the target task execution result is that the task execution is successful;

the receiving information module is configured to receive progress information submitted by the task participation terminal aiming at the task progress notification;

And the notification release module is configured to change and release the task progress notification based on the progress information.

Optionally, the task processing device further includes:

The receiving instruction module is configured to receive a reservation request submitted by the reservation terminal through the task progress notification;

The establishing module is configured to establish reservation association relation between a reservation user corresponding to the reservation terminal and the target task based on the reservation request;

the feedback module is configured to feed back reservation success reminding to the reservation terminal;

and the sending reminding module is configured to send a task completion reminding to a reservation user with reservation association relation with the target task under the condition that the task progress in the task progress notification is changed to be completed.

Optionally, the publishing module 604 includes:

The creation sub-module is configured to create a target task based on task information carried in the task creation request;

and the issuing sub-module is configured to issue the target task according to a pre-configured issuing mode.

Optionally, the publishing sub-module is further configured to:

Publishing the target task on an active page of a target application; and/or

Publishing the target task on a homepage of a task participant; and/or

Publishing the target task in a display area pointed by a target navigation bar in the target application; and/or

And under the condition that a published task set corresponding to a task participant in the target task is not empty, completing the publication of the target task by updating the published tasks in the published task set based on the target task.

Optionally, the publishing module 604 is further configured to:

Optionally, the task processing device further includes:

the receiving task module is configured to receive a user task submitted by a user terminal aiming at the target task;

and the user task issuing module is configured to issue the user task according to a user issuing mode corresponding to the target task.

Optionally, the task processing device further includes:

the statistics voting module is configured to count user votes submitted by the user voting terminal for the user tasks;

And the updating module is configured to update and release the user tasks and the user task ordering list based on the statistical result.

Optionally, the task processing device further includes:

the sharing instruction receiving module is configured to receive a sharing instruction submitted for an issued user task, wherein the sharing instruction carries user information and user task information;

And the sending task module is configured to determine the user task based on the user task information and send the user task to the sharing user corresponding to the user information.

Optionally, the task processing device further includes:

The detection module is configured to detect whether the target task meets a task ending condition;

if yes, a statistics module 606 is run, the statistics module 606 is configured to execute the initial task execution result step of determining the target task based on the task voting statistics.

Optionally, the task end condition includes:

counting the number of votes supporting the votes in the task votes to reach the preset number of supporting the votes; or (b)

Counting the number of votes of the task votes to reach a preset number of votes; or (b)

The release time length of releasing the target task meets the preset time length.

Optionally, the task processing device further includes:

the receiving request module is configured to receive a viewing request submitted by the browsing terminal aiming at the issued task;

the sending list module is configured to respond to the watching request and send a task list corresponding to the issued task to the browsing terminal; the issued tasks in the task list are displayed in sequence according to the operation instructions received by the browsing terminal.

The above is a schematic solution of a task processing device of the present embodiment. It should be noted that, the technical solution of the task processing device and the technical solution of the task processing method belong to the same concept, and details of the technical solution of the task processing device, which are not described in detail, can be referred to the description of the technical solution of the task processing method.

Fig. 7 illustrates a block diagram of a computing device 700 provided in accordance with one embodiment of the present description. The components of computing device 700 include, but are not limited to, memory 710 and processor 720. Processor 720 is coupled to memory 710 via bus 730, and database 750 is used to store data.

Computing device 700 also includes access device 740, access device 740 enabling computing device 700 to communicate via one or more networks 760. Examples of such networks include the Public Switched Telephone Network (PSTN), a Local Area Network (LAN), a Wide Area Network (WAN), a Personal Area Network (PAN), or a combination of communication networks such as the internet. The access device 740 may include one or more of any type of network interface, wired or wireless (e.g., a Network Interface Card (NIC)), such as an IEEE802.11 Wireless Local Area Network (WLAN) wireless interface, a worldwide interoperability for microwave access (Wi-MAX) interface, an ethernet interface, a Universal Serial Bus (USB) interface, a cellular network interface, a bluetooth interface, a Near Field Communication (NFC) interface, and so forth.

In one embodiment of the present description, the above-described components of computing device 700, as well as other components not shown in FIG. 7, may also be connected to each other, such as by a bus. It should be understood that the block diagram of the computing device illustrated in FIG. 7 is for exemplary purposes only and is not intended to limit the scope of the present description. Those skilled in the art may add or replace other components as desired.

Computing device 700 may be any type of stationary or mobile computing device including a mobile computer or mobile computing device (e.g., tablet, personal digital assistant, laptop, notebook, netbook, etc.), mobile phone (e.g., smart phone), wearable computing device (e.g., smart watch, smart glasses, etc.), or other type of mobile device, or a stationary computing device such as a desktop computer or PC. Computing device 700 may also be a mobile or stationary server.

Wherein the processor 720 is configured to implement the steps of the task processing method when executing the computer instructions.

The foregoing is a schematic illustration of a computing device of this embodiment. It should be noted that, the technical solution of the computing device and the technical solution of the task processing method belong to the same concept, and details of the technical solution of the computing device, which are not described in detail, can be referred to the description of the technical solution of the task processing method.

An embodiment of the present application also provides a computer-readable storage medium storing computer instructions which, when executed by a processor, implement the steps of the task processing method as described above.

The above is an exemplary version of a computer-readable storage medium of the present embodiment. It should be noted that, the technical solution of the storage medium and the technical solution of the task processing method belong to the same concept, and details of the technical solution of the storage medium which are not described in detail can be referred to the description of the technical solution of the task processing method.

The foregoing describes certain embodiments of the present application. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims can be performed in a different order than in the embodiments and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

The computer instructions include computer program code that may be in source code form, object code form, executable file or some intermediate form, etc. The computer readable medium may include: any entity or device capable of carrying the computer program code, a recording medium, a U disk, a removable hard disk, a magnetic disk, an optical disk, a computer Memory, a Read-Only Memory (ROM), a random access Memory (RAM, random Access Memory), an electrical carrier signal, a telecommunications signal, a software distribution medium, and so forth. It should be noted that the computer readable medium contains content that can be appropriately scaled according to the requirements of jurisdictions in which such content is subject to legislation and patent practice, such as in certain jurisdictions in which such content is subject to legislation and patent practice, the computer readable medium does not include electrical carrier signals and telecommunication signals.

It should be noted that, for the sake of simplicity of description, the foregoing method embodiments are all expressed as a series of combinations of actions, but it should be understood by those skilled in the art that the present application is not limited by the order of actions described, as some steps may be performed in other order or simultaneously in accordance with the present application. Further, those skilled in the art will appreciate that the embodiments described in the specification are all preferred embodiments, and that the acts and modules referred to are not necessarily all required for the present application.

In the foregoing embodiments, the descriptions of the embodiments are emphasized, and for parts of one embodiment that are not described in detail, reference may be made to the related descriptions of other embodiments.

The preferred embodiments of the application disclosed above are intended only to assist in the explanation of the application. Alternative embodiments are not intended to be exhaustive or to limit the application to the precise form disclosed. Obviously, many modifications and variations are possible in light of the above teaching. The embodiments were chosen and described in order to best explain the principles of the application and the practical application, to thereby enable others skilled in the art to best understand and utilize the application. The application is limited only by the claims and the full scope and equivalents thereof.

Claims

1. A method of task processing, comprising:

Receiving a task creation request submitted by a task request terminal;

creating a target task based on task information carried in the task creation request; the target task is sent to a target task participation terminal of the target task;

Issuing the target task under the condition that an approval instruction submitted by the target task participation terminal for the target task is received, wherein at least two task participants contained in the task information belong to different service fields;

2. The task processing method according to claim 1, wherein the determining an initial task execution result of the target task based on the task voting statistics includes:

3. The task processing method according to claim 2, further comprising, after the task participation information is transmitted to each task participant:

4. A task processing method according to claim 3, further comprising, after determining a target task execution result of the target task:

5. The task processing method according to claim 4, further comprising, after the task progress notification is issued based on the target task:

receiving a reservation request submitted by a reservation terminal based on the task progress notification;

feeding back a reservation success reminder to the reservation terminal;

6. The task processing method according to claim 1, wherein the creating and issuing the target task based on the task information carried in the task creation request includes:

and publishing the target task according to a pre-configured publishing mode.

7. The task processing method according to claim 6, wherein the publishing the target task according to a pre-configured publishing mode includes:

Publishing the target task on an active page of a target application; and/or

Publishing the target task on a homepage of a task participant; and/or

8. The task processing method according to claim 1, further comprising, after the creating and issuing the target task based on the task information carried in the task creation request:

Receiving a user task submitted by a user terminal aiming at the target task;

9. The task processing method according to claim 8, wherein after the user task is published according to the user publishing mode corresponding to the target task, further comprising:

10. The task processing method according to claim 8, wherein after the user task is published according to the user publishing mode corresponding to the target task, further comprising:

11. The task processing method according to claim 1, further comprising, before determining an initial task execution result of the target task based on the task voting statistics:

detecting whether the target task meets a task ending condition;

if yes, executing the step of determining the initial task execution result of the target task based on the task voting statistical result.

12. The task processing method according to claim 11, characterized in that the task end condition includes:

13. The task processing method according to claim 1, further comprising, after the creating and issuing the target task based on the task information carried in the task creation request:

14. A task processing device, comprising:

The publishing module is configured to create a target task based on task information carried in the task creation request; the target task is sent to a target task participation terminal of the target task; issuing the target task under the condition that an approval instruction submitted by the target task participation terminal for the target task is received, wherein at least two task participants contained in the task information belong to different service fields;

15. A computing device comprising a memory, a processor, and computer instructions stored on the memory and executable on the processor, wherein the processor, when executing the computer instructions, performs the steps of the method of any one of claims 1-13.

16. A computer readable storage medium storing computer instructions which, when executed by a processor, implement the steps of the method of any one of claims 1-13.