Task allocating method and device and terminal device

[0021] Example 1:

[0022] figure 1 A schematic diagram of the implementation flow of a task issuing method provided by the present application is shown, and the details are as follows:

[0023] Step S11, receiving the task issuing request sent by the user, and determining whether the user has the right to obtain the task according to the task issuing request;

[0024] In the embodiment provided by the present application, when receiving a task issuing request sent by a user, the task issuing system firstly determines whether the user has the authority to acquire a task. Specifically, after receiving the task issuing request, the task issuing system calls the ID information of the user contained in the task issuing request, and then judges whether the user has been authorized by the task issuing system according to the ID information. When the user is authorized by the task issuing system, it is determined that the user has the right to acquire the task; wherein, the ID information refers to the ID information of the smart terminal used by the user to send the task sending request.

[0025] For example, when a task issuing system in a telemarketing department receives a task issuing request sent by a business person, it first obtains the ID information of the smart terminal used by the business person to send the task issuing request according to the task issuing request, and then determines Whether the ID information has been successfully registered in the task issuing system of the telemarketing department, if the ID information has been successfully registered, it means that the task issuing system of the telemarketing department has authorized the business personnel to obtain through the intelligent terminal and will make a call to it. The customer's information, wherein the customer's information includes the customer's phone number.

[0026] Optionally, before receiving the task issuance request sent by the user, and judging whether the user has the right to acquire the task according to the task issuance request, the method includes:

[0027] Acquire the returned issued tasks, and store the returned issued tasks and unprocessed tasks in the to-be-issued task list as tasks to be issued in the current cycle.

[0028] In the embodiment provided by this application, the task issuing system pre-stores the tasks to be issued, and when storing the tasks to be issued, counts the issued tasks returned in the previous cycle, and compares the returned issued tasks with the unprocessed tasks. Common storage forms the tasks to be issued in the current cycle. Wherein, the returned issued tasks refer to tasks that need to be processed again after being processed in the previous cycle or several previous cycles; for example, the returned issued tasks when recommending a commodity to a customer in a telemarketing system may include: After the last call to the customer, the customer who appears in the call result needs to be considered, no answer, agreed to go to handle, temporarily not needed, etc. The customer who needs to call the customer again. For different dialing results, the interval time of the next reflow can be set to different times. A task management column is set during storage, and the task management column includes a task data list, a holding task list, a to-be-processed task list, and a processing times list; wherein, the data stored in the shown task data list includes the corresponding data of each task. Customer information; the number of tasks held by each business person is stored in the task list; the number of tasks to be processed and related information are stored in the task list to be processed, and the tasks to be processed need to be processed again after processing. The number of tasks and the number of unprocessed tasks; the number of times each task has been processed and the information of the business personnel who process the task each time are stored in the list of processing times. Optionally, when the task to be processed is stored, it can be preliminarily classified and screened, for example, the tasks that meet the preset conditions in the tasks that need to be processed again are stored corresponding to their last processing personnel, so as to facilitate the processing again. It is issued to the same handler.

[0029] For example, in the task issuing system of the telemarketing department, the information of new customers who need to make calls to them in the current working day and the information of customers who need to make calls to them again are counted, and all of them are regarded as the information to be called on the current working day. Task. Store the customer's information in each pending call in the task data list, store the total number of tasks to be dialed and other information in the pending task list, and store the information about the customer's The number of customers who have not made calls to customers is stored in the holding task list, so that tasks can be sent to business personnel according to their task holdings, and the number of calls made to users in each pending call task Stored in a list of processing times.

[0030] Preferably, the determining whether the user has the right to acquire the task according to the task issuing request includes:

[0031] Verifying whether the user is an authorized user according to the task issuing request;

[0032] verifying the user's task holdings when the user is an authorized user;

[0033] When the task holding amount of the user is less than the preset value, it is determined that the user has the right to acquire the task.

[0034] In the embodiment provided in this application, when judging whether a user has the right to acquire a task, first obtain user information according to a task sending request to determine whether the user is an authorized user, and if the user is an authorized user, determine whether the user is an authorized user. The number of tasks currently held. At this time, the number of tasks held by the user stored in the held task list is called to determine whether the number of tasks held by the user is less than the preset value. If If it is less than the preset value, it is determined that the user has the right to obtain the task. Optionally, the preset value can be set according to user needs, for example, the telemarketing department can set the preset value to 1 or 5 or other values ​​in order to improve the work enthusiasm of the business personnel.

[0035] For example, when the telemarketing department sets the preset value to 1, the task issuing system determines whether the business personnel has the right to obtain customer information from the task issuing system according to the task issuing request sent by the business personnel to make calls to the customer. The business person is an authorized user, then obtain the number of customers currently held by the business person who have not made calls recorded in the holding task list. If the number is 0, that is, less than the preset value of 1, it is determined that the business personnel can obtain tasks from the task issuing system.

[0036] Step S12, when the user has the right to obtain tasks, obtain a list of tasks to be issued;

[0037] In the embodiment provided by the present application, when the user has the right to obtain tasks from the task sending system, the list of tasks to be issued is called to obtain the number of tasks to be processed stored therein. If the number of tasks to be processed is greater than the preset tasks amount, it means that the task issuing system can continue to send tasks to the user, wherein the preset task amount may be 1, or may be other values.

[0038]Optionally, when the number of tasks to be processed is less than the preset task amount, the tasks that have been processed in the current cycle and need to be processed again are acquired, and are stored in the task issuing system as new tasks to be processed.

[0039] Step S13, calling a preset number of tasks to be released in the list of tasks to be released, and sending the called tasks to be released to the user.

[0040] In the embodiment provided by the present application, if a sufficient number of tasks to be processed are stored in the task distribution system, a preset number of tasks are retrieved from the system, and the invoked tasks to be processed are distributed to the user. Wherein, the preset number may be 1. Optionally, when invoking a preset number of tasks to be issued, the tasks to be issued may be called in the form of random calls, or the tasks to be issued may be called according to a preset calling rule; First-come, first-served rules, balanced matching rules, etc.

[0041] Wherein, when the first-come-first-served rule is adopted, the part with low processing difficulty factor (high success rate) and/or unprocessed tasks among the issued tasks that have been issued back can be preferentially called, and issued to the users who apply first. . Classify the returned tasks in advance. For example, according to the result of the last call, classify the call result as the customer needs to consider and agree to go to the task as the task with low difficulty factor, and classify the call result as unanswered and temporarily not needed. It is classified as a task with a high degree of difficulty. At the same time, a specific difficulty coefficient value can be given for each classification.

[0042] When the balanced collocation rule is adopted, the reflowed tasks that have been issued are statistically classified in advance, and a specific difficulty coefficient value is given to each classification, and the unprocessed tasks are classified into task categories with low difficulty coefficients. Combining the issued tasks with low difficulty coefficients, the issued tasks with high difficulty coefficients, and the unprocessed tasks, when calling the pending tasks to be issued to the same user, obtain the pending tasks that have been received by the current user. The average value of the processing difficulty coefficient of the task, and then the task to be processed with an appropriate difficulty coefficient is called and issued to the current user. At this time, historical data can also be counted to obtain the average processing time and average success rate of tasks with the same difficulty coefficient value. When assigning tasks, the processing time and success rate of completed tasks in this period are counted, and compared with the average processing time and average success rate. In order to achieve incentives for users who complete tasks efficiently. When the user's processing time is lower than the average processing time and the success rate is higher than the average success rate, the ratio of the returned tasks and unprocessed tasks with low difficulty coefficients can be increased, so that the average difficulty coefficient of the issued tasks is low. The average value of the difficulty factor of tasks completed in this period. Or, according to the historical task processing data, set a benchmark task difficulty coefficient value for the user. When the user's processing time is lower than the average processing time and the success rate is higher than the average success rate for a period of time, priority can be given to sending a task lower than this value. The task to be issued with the set difficulty coefficient value, so as to motivate users who complete the task efficiently.

[0043] Preferably, invoking a preset number of tasks to be issued in the task list to be issued, and sending the called tasks to be issued to the user, includes:

[0044] Query the number of tasks in the to-be-issued task list;

[0045] When the number of tasks is not less than the preset task amount, randomly calling a preset number of tasks to be issued in the task list to be issued, and sending the called tasks to be issued to the user;

[0046] The number of tasks in the to-be-issued task list and the task holdings of the user are updated.

[0047] Specifically, when a task is issued to a user, the number of tasks recorded in the list of tasks to be issued is firstly queried, and when the number of tasks is not less than the preset task amount, a preset number of tasks to be processed are called from it to be issued to the user. describe the user and update the user's task holdings. Wherein, the preset task amount is not less than the preset number.

[0048] Optionally, after the called task to be processed is issued to the user, the storage information of the held task list and the to-be-processed task list is updated, that is, the stored information in the held task list has been held by the user. The number of unprocessed tasks is increased by the preset number, while the data information corresponding to the preset number of tasks to be processed is increased, and the number of tasks to be processed stored in the list of tasks to be processed is reduced by the A preset number, and at the same time delete the data information corresponding to the preset number of tasks to be processed. After the to-be-processed tasks are issued to the users, the number of the to-be-processed tasks in the to-be-processed task list and the related data information of the to-be-processed tasks can be reduced in time, so as to avoid issuing the same to-be-processed tasks to multiple users.

[0049] For example, the task issuing system in the telemarketing department sets the number of customer information to be dialed to each business person to be 1 each time. If the current task list to be issued is queried, there are 10 customer information records that need to be dialed. , then call one and issue it to the salesperson, then increase the number of tasks held by the salesperson by 1, and decrease the number of customer information recorded in the task list to be issued by 1.

[0050] Preferably, after invoking a preset number of tasks to be issued in the task list to be issued, and sending the called tasks to be issued to the user, the method includes:

[0051] Receive the processing result of the task to be issued by the user, and update the task holding amount of the user.

[0052] Specifically, after receiving the to-be-issued task, the user processes the to-be-issued task according to the task requirements, and sends the processing result to the task issuing system. After receiving the processing result, the task issuing system adds the held task list to the The number of tasks held by the user is reduced by the number of completed tasks processed. At the same time, the processing times of the corresponding task in the processing times list is increased by 1. Since the number of pending tasks held by the user is less than the preset value, the user has the right to obtain the pending tasks from the task sending system again. Therefore, after the user has processed the current task, the number of tasks held by the user is reduced and the processing is completed. The number of tasks so that the user can obtain pending tasks from the task issuing system again. For tasks that do not need to be processed after the last processing, the data related to the task in the task data list is deleted.

[0053] For example, in the task distribution system of the telemarketing department, after a business person makes a call to a certain customer, he feeds back the call result to the task distribution system, and increases the recorded number of calls made by the customer by 1; Call, delete the relevant information of the customer in the task data list; reduce the number of tasks held by the business person by 1.

[0054] In the embodiment provided by this application, the task issuing system, when receiving a task issuing request sent by a user, firstly determines whether the user has the right to obtain a task from it, and only when the user has finished processing the task and the current task holding amount is less than the preset value. It is determined that the user has the right to continue to obtain tasks, and when the user has the right to obtain tasks, a preset number of tasks are called from the to-be-issued task list to be distributed to the user; it avoids assigning tasks to the user in a fixed way in the existing task allocation method. The user's situation improves the user's enthusiasm for processing tasks.

[0055] Embodiment 2:

[0056] Corresponding to the task issuing method described in the above embodiment, figure 2 A structural block diagram of a task issuing apparatus provided by an embodiment of the present invention is shown. For convenience of description, only the part related to the embodiment of the present invention is shown.

[0057] refer to figure 2 , the task issuing device includes: a issuing request receiving unit 21, an acquiring unit 22, and a calling unit 23, wherein:

[0058] The issuing request receiving unit 21 is configured to receive a task issuing request sent by a user, and determine whether the user has the right to acquire a task according to the task issuing request;

[0059] In the embodiment provided by the present application, when receiving a task issuing request sent by a user, the task issuing system firstly determines whether the user has the authority to acquire a task. Specifically, after receiving the task issuing request, the task issuing system calls the ID information of the user contained in the task issuing request, and then judges whether the user has been authorized by the task issuing system according to the ID information. When the user is authorized by the task issuing system, it is determined that the user has the right to acquire the task; wherein, the ID information refers to the ID information of the smart terminal used by the user to send the task sending request.

[0060] For example, when a task issuing system in a telemarketing department receives a task issuing request sent by a business person, it first obtains the ID information of the smart terminal used by the business person to send the task issuing request according to the task issuing request, and then determines Whether the ID information has been successfully registered in the task issuing system of the telemarketing department, if the ID information has been successfully registered, then the task issuing system of the telemarketing department has been described, and the authorized business personnel will be called through the intelligent terminal. Information of the customer of the phone, wherein the customer's information includes the customer's phone number.

[0061] Optionally, the task issuing device further includes:

[0062] The storage unit is configured to acquire the returned issued tasks, and store the returned issued tasks and unprocessed tasks in the to-be-issued task list as the tasks to be issued in the current cycle.

[0063] In the embodiment provided by this application, the task issuing system pre-stores the tasks to be issued, and when storing the tasks to be issued, counts the issued tasks that need to be returned in the previous cycle, and compares the returned issued tasks with the unprocessed tasks. The tasks are stored together to form the tasks to be issued in the current cycle. Wherein, the returned issued tasks refer to tasks that need to be processed again after being processed in the previous cycle or several previous cycles; for example, the returned issued tasks when recommending a commodity to a customer in a telemarketing system may include: After the last call to the customer, the customer who appears in the call result needs to be considered, no answer, agreed to go to handle, temporarily not needed, etc. The customer who needs to call the customer again. For different dialing results, the interval time of the next reflow can be set to different times. A task management column is set during storage, and the task management column includes a task data list, a holding task list, a to-be-processed task list, and a processing times list; wherein, the data stored in the shown task data list includes the corresponding data of each task. Customer information; the number of tasks held by each business person is stored in the task list; the number of tasks to be processed and related information are stored in the task list to be processed, and the tasks to be processed need to be processed again after processing. The number of tasks and the number of unprocessed tasks; the number of times each task has been processed and the information of the business personnel who process the task each time are stored in the list of processing times. Optionally, when the task to be processed is stored, it can be preliminarily classified and screened, for example, the tasks that meet the preset conditions in the tasks that need to be processed again are stored corresponding to their last processing personnel, so as to facilitate the processing again. It is issued to the same handler.

[0064] For example, in the task issuing system of the telemarketing department, the information of new customers who need to make calls to them in the current working day and the information of customers who need to make calls to them again are counted, and all of them are regarded as the information to be called on the current working day. Task. Store the customer's information in each pending call in the task data list, store the total number of tasks to be dialed and other information in the pending task list, and store the information about the customer's The number of customers who have not made calls to customers is stored in the holding task list, so that tasks can be sent to business personnel according to their task holdings. The number of times is stored in a list of processing times.

[0065] Preferably, the issuing request receiving unit includes:

[0066] a first verification module, configured to verify whether the user is an authorized user according to the task issuance request;

[0067] a second verification module, configured to verify the task holdings of the user when the user is an authorized user;

[0068] A determination module, configured to determine that the user has the right to acquire the task when the task holding amount of the user is less than a preset value.

[0069] In the embodiment provided in this application, when judging whether a user has the right to acquire a task, first obtain user information according to a task sending request to determine whether the user is an authorized user, and if the user is an authorized user, determine whether the user is an authorized user. The number of tasks currently held. At this time, the number of tasks held by the user stored in the held task list is called to determine whether the number of tasks held by the user is less than the preset value. If If it is less than the preset value, it is determined that the user has the right to obtain the task. Optionally, the preset value can be set according to user needs, for example, the telemarketing department can set the preset value to 1 or 5 or other values ​​in order to improve the work enthusiasm of the business personnel.

[0070] For example, when the telemarketing department sets the preset value to 1, the task issuing system determines whether the business personnel has the right to obtain customer information from the task issuing system according to the task issuing request sent by the business personnel to make calls to the customer. The business person is an authorized user, then obtain the number of customers currently held by the business person who have not made calls recorded in the holding task list. If the number is 0, that is, less than the preset value of 1, it is determined that the business personnel can obtain tasks from the task issuing system.

[0071] an obtaining unit 22, configured to obtain a list of tasks to be issued when the user has the right to obtain tasks;

[0072] In the embodiment provided by the present application, when the user has the right to obtain tasks from the task sending system, the list of tasks to be issued is called to obtain the number of tasks to be processed stored therein. If the number of tasks to be processed is greater than the preset tasks amount, it means that the task issuing system can continue to send tasks to the user, wherein the preset task amount may be 1, or may be other values.

[0073] Optionally, when the number of tasks to be processed is less than the preset task amount, the tasks that have been processed in the current cycle and need to be processed again are acquired, and are stored in the task issuing system as new tasks to be processed.

[0074] The calling unit 23 is configured to call a preset number of tasks to be released in the list of tasks to be released, and send the called tasks to be released to the user.

[0075] In the embodiment provided by the present application, if a sufficient number of tasks to be processed are stored in the task distribution system, a preset number of tasks are retrieved from the system, and the invoked tasks to be processed are distributed to the user. Wherein, the preset number may be 1.

[0076] Optionally, when invoking a preset number of tasks to be issued, the tasks to be issued may be called in the form of random calls, or the tasks to be issued may be called according to a preset calling rule; First-come, first-served rules, balanced matching rules, etc.

[0077] Wherein, when the first-come-first-served rule is adopted, the part with low processing difficulty factor (high success rate) and/or unprocessed tasks among the issued tasks that have been issued back can be preferentially called, and issued to the users who apply first. . Classify the returned tasks in advance. For example, according to the result of the last call, classify the call result as the customer needs to consider and agree to go to the task as the task with low difficulty factor, and classify the call result as unanswered and temporarily not needed. It is classified as a task with a high degree of difficulty. At the same time, a specific difficulty coefficient value can be given for each classification.

[0078] When the balanced collocation rule is adopted, the reflowed tasks that have been issued are statistically classified in advance, and a specific difficulty coefficient value is given to each classification, and the unprocessed tasks are classified into task categories with low difficulty coefficients. Combining the issued tasks with low difficulty coefficients, the issued tasks with high difficulty coefficients, and the unprocessed tasks, when calling the pending tasks to be issued to the same user, obtain the pending tasks that have been received by the current user. The average value of the processing difficulty coefficient of the task, and then the task to be processed with an appropriate difficulty coefficient is called and issued to the current user. At this time, historical data can also be counted to obtain the average processing time and average success rate of tasks with the same difficulty coefficient value. When assigning tasks, the processing time and success rate of completed tasks in this period are counted, and compared with the average processing time and average success rate. In order to achieve incentives for users who complete tasks efficiently. When the user's processing time is lower than the average processing time and the success rate is higher than the average success rate, the ratio of the returned tasks and unprocessed tasks with low difficulty coefficients can be increased, so that the average difficulty coefficient of the issued tasks is low. The average value of the difficulty factor of tasks completed in this period. Or, according to the historical task processing data, set a benchmark task difficulty coefficient value for the user. When the user's processing time is lower than the average processing time and the success rate is higher than the average success rate for a period of time, priority can be given to sending a task lower than this value. The task to be issued with the set difficulty coefficient value, so as to motivate users who complete the task efficiently.

[0079] Preferably, the calling unit includes:

[0080] A quantity query module, used for querying the number of tasks in the to-be-issued task list;

[0081] a distribution module, configured to randomly call a preset number of tasks to be distributed in the list of tasks to be distributed when the number of tasks is not less than a preset task amount, and distribute the called tasks to be distributed to the user;

[0082] An update module, configured to update the number of tasks in the to-be-issued task list and the task holding amount of the user.

[0083] Specifically, when a task is issued to a user, the number of tasks recorded in the list of tasks to be issued is firstly queried, and when the number of tasks is not less than the preset task amount, a preset number of tasks to be processed are called from it to be issued to the user. describe the user and update the user's task holdings. Wherein, the preset task amount is not less than the preset number.

[0084] Optionally, after the called task to be processed is issued to the user, the storage information of the held task list and the to-be-processed task list is updated, that is, the stored information in the held task list has been held by the user. The number of unprocessed tasks is increased by the preset number, while the data information corresponding to the preset number of tasks to be processed is increased, and the number of tasks to be processed stored in the list of tasks to be processed is reduced by the A preset number, and at the same time delete the data information corresponding to the preset number of tasks to be processed. After the to-be-processed tasks are issued to the users, the number of the to-be-processed tasks in the to-be-processed task list and the related data information of the to-be-processed tasks can be reduced in time, so as to avoid issuing the same to-be-processed tasks to multiple users.

[0085] For example, the task issuing system in the telemarketing department sets the number of customer information to be dialed to each business person to be 1 each time. If the current task list to be issued is queried, there are 10 customer information records that need to be dialed. , then call one and issue it to the salesperson, then increase the number of tasks held by the salesperson by 1, and decrease the number of customer information recorded in the task list to be issued by 1.

[0086] Optionally, the task issuing device further includes:

[0087] The processing result receiving unit is configured to receive the processing result of the task to be issued by the user, and update the task holding amount of the user.

[0088] It should be understood that the size of the sequence numbers of the steps in the above embodiments does not mean the sequence of execution, and the execution sequence of each process should be determined by its functions and internal logic, and should not constitute any limitation to the implementation process of the embodiments of the present invention.

[0089] Specifically, after receiving the to-be-issued task, the user processes the to-be-issued task according to the task requirements, and sends the processing result to the task issuing system. After receiving the processing result, the task issuing system adds the held task list to the The number of tasks held by the user is reduced by the number of completed tasks processed. At the same time, the processing times of the corresponding task in the processing times list is increased by 1. Since the number of pending tasks held by the user is less than the preset value, the user has the right to obtain the pending tasks from the task sending system again. Therefore, after the user has processed the current task, the number of tasks held by the user is reduced and the processing is completed. The number of tasks so that the user can obtain pending tasks from the task issuing system again. For tasks that do not need to be processed after the last processing, the data related to the task in the task data list is deleted.

[0090] For example, in the task distribution system of the telemarketing department, after a business person makes a call to a certain customer, he feeds back the call result to the task distribution system, and increases the recorded number of calls made by the customer by 1; Call, delete the relevant information of the customer in the task data list; reduce the number of tasks held by the business person by 1.

[0091] In the embodiment provided by this application, the task issuing system, when receiving a task issuing request sent by a user, firstly determines whether the user has the right to obtain a task from it, and only when the user has finished processing the task and the current task holding amount is less than the preset value. It is determined that the user has the right to continue to obtain tasks, and when the user has the right to obtain tasks, a preset number of tasks are called from the to-be-issued task list to be distributed to the user; it avoids assigning tasks to the user in a fixed way in the existing task allocation method. The user's situation improves the user's enthusiasm for processing tasks.

[0092] Embodiment three:

[0093] image 3 It is a schematic diagram of a terminal device provided by an embodiment of the present invention. like image 3 As shown, the terminal device 3 in this embodiment includes: a processor 30 , a memory 31 , and a computer program 32 stored in the memory 31 and running on the processor 30 . When the processor 30 executes the computer program 32, the steps in each of the above-mentioned embodiments of the task issuing method are implemented, for example, figure 1 Steps S11 to S13 are shown. Alternatively, when the processor 30 executes the computer program 32, the functions of the modules/units in the foregoing device embodiments are implemented, for example, figure 2 The functions of units 21 to 23 are shown.

[0094] Exemplarily, the computer program 32 can be divided into one or more modules/units, and the one or more modules/units are stored in the memory 31 and executed by the processor 30 to complete the this invention. The one or more modules/units may be a series of computer program instruction segments capable of performing specific functions, and the instruction segments are used to describe the execution process of the computer program 32 in the terminal device 3 . For example, the computer program 32 can be divided into an issuing request receiving unit, an acquiring unit, and a calling unit, and the specific functions of each unit are as follows:

[0095] an issuance request receiving unit, configured to receive a task issuance request sent by a user, and determine whether the user has the right to acquire a task according to the task issuance request;

[0096] Further, the issuing request receiving unit includes:

[0097] a first verification module, configured to verify whether the user is an authorized user according to the task issuance request;

[0098] a second verification module, configured to verify the task holdings of the user when the user is an authorized user;

[0099] A determination module, configured to determine that the user has the right to acquire the task when the task holding amount of the user is less than a preset value.

[0100] an acquiring unit, configured to acquire a list of tasks to be issued when the user has the right to acquire tasks;

[0101]The calling unit is configured to call a preset number of tasks to be released in the list of tasks to be released, and send the called tasks to be released to the user.

[0102] Further, the calling unit includes:

[0103] A quantity query module, used for querying the number of tasks in the to-be-issued task list;

[0104] a distribution module, configured to randomly call a preset number of tasks to be distributed in the list of tasks to be distributed when the number of tasks is not less than a preset task amount, and distribute the called tasks to be distributed to the user;

[0105] An update module, configured to update the number of tasks in the to-be-issued task list and the task holding amount of the user.

[0106] Further, the task issuing device also includes:

[0107] The storage unit is configured to acquire the returned issued tasks, and store the returned issued tasks and unprocessed tasks in the to-be-issued task list as the tasks to be issued in the current cycle.

[0108] Further, the task issuing device also includes:

[0109] The processing result receiving unit is configured to receive the processing result of the task to be issued by the user, and update the task holding amount of the user.

[0110] The terminal device 3 may be a computing device such as a desktop computer, a notebook, a palmtop computer, and a cloud server. The terminal device may include, but is not limited to, the processor 30 and the memory 31 . Those skilled in the art can understand that, image 3 It is only an example of the terminal device 3, and does not constitute a limitation on the terminal device 3. It may include more or less components than shown in the figure, or combine some components, or different components. For example, the terminal device may also include Input and output devices, network access devices, buses, etc.

[0111] The so-called processor 30 may be a central processing unit (Central Processing Unit, CPU), and may also be other general-purpose processors, digital signal processors (Digital Signal Processors, DSP), application specific integrated circuits (Application Specific Integrated Circuit, ASIC), Off-the-shelf programmable gate array (Field-Programmable Gate Array, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, and the like. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.

[0112] The memory 31 may be an internal storage unit of the terminal device 3 , such as a hard disk or a memory of the terminal device 3 . The memory 31 may also be an external storage device of the terminal device 3, such as a plug-in hard disk equipped on the terminal device 3, a smart memory card (Smart Media Card, SMC), a secure digital (Secure Digital, SD) card, flash card (Flash Card) and so on. Further, the memory 31 may also include both an internal storage unit of the terminal device 3 and an external storage device. The memory 31 is used to store the computer program and other programs and data required by the terminal device. The memory 31 can also be used to temporarily store data that has been output or will be output. Those skilled in the art can clearly understand that, for the convenience and simplicity of description, only the division of the above-mentioned functional units and modules is used as an example. Module completion, that is, dividing the internal structure of the device into different functional units or modules to complete all or part of the functions described above. Each functional unit and module in the embodiment may be integrated in one processing unit, or each unit may exist physically alone, or two or more units may be integrated in one unit, and the above-mentioned integrated units may adopt hardware. It can also be realized in the form of software functional units. In addition, the specific names of the functional units and modules are only for the convenience of distinguishing from each other, and are not used to limit the protection scope of the present application. For the specific working processes of the units and modules in the above-mentioned system, reference may be made to the corresponding processes in the foregoing method embodiments, which will not be repeated here.