WO2019019687A1 - Task allocating method and device, terminal device and storage medium - Google Patents

Task allocating method and device, terminal device and storage medium Download PDF

Info

Publication number
WO2019019687A1
WO2019019687A1 PCT/CN2018/081420 CN2018081420W WO2019019687A1 WO 2019019687 A1 WO2019019687 A1 WO 2019019687A1 CN 2018081420 W CN2018081420 W CN 2018081420W WO 2019019687 A1 WO2019019687 A1 WO 2019019687A1
Authority
WO
WIPO (PCT)
Prior art keywords
task
processed
list
user id
instruction
Prior art date
Application number
PCT/CN2018/081420
Other languages
French (fr)
Chinese (zh)
Inventor
周鹏
杨克森
Original Assignee
平安科技(深圳)有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority to CN201710627510.5A priority Critical patent/CN107832901A/en
Priority to CN201710627510.5 priority
Application filed by 平安科技(深圳)有限公司 filed Critical 平安科技(深圳)有限公司
Publication of WO2019019687A1 publication Critical patent/WO2019019687A1/en

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06QDATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00Administration; Management
    • G06Q10/06Resources, workflows, human or project management, e.g. organising, planning, scheduling or allocating time, human or machine resources; Enterprise planning; Organisational models
    • G06Q10/063Operations research or analysis
    • G06Q10/0631Resource planning, allocation or scheduling for a business operation
    • G06Q10/06311Scheduling, planning or task assignment for a person or group
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06QDATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00Administration; Management
    • G06Q10/06Resources, workflows, human or project management, e.g. organising, planning, scheduling or allocating time, human or machine resources; Enterprise planning; Organisational models
    • G06Q10/063Operations research or analysis
    • G06Q10/0631Resource planning, allocation or scheduling for a business operation
    • G06Q10/06315Needs-based resource requirements planning or analysis

Abstract

The present application discloses a task assignment method, device, terminal device and storage medium. The task assignment method includes: acquiring a task assignment instruction, the task assignment instruction includes a user ID; acquiring a to-be-processed task list based on the task assignment instruction, and the to-be-processed task list includes all pending tasks that can be allocated to the user corresponding to the user ID; Whether the task assignment instruction is the first assignment instruction for the day corresponding to the user ID; if the task assignment instruction is not the first assignment instruction for the day corresponding to the user ID, the first task assignment list is obtained from the to-be-processed task list, and the first task assignment list is obtained. The user corresponding to the user ID is sent to the user ID; wherein the first task allocation list includes at least one to-be-processed task, and the number of the to-be-processed tasks in the first task allocation list is the newly added task amount. This task assignment method is efficient and low cost when assigning tasks.

Description

Task assignment method, device, terminal device and storage medium

The present application is based on the Chinese Patent Application No. 201710627510.5, entitled "Task Assignment Method, Apparatus, Terminal Equipment and Storage Medium", which is filed on July 28, 2017, and claims priority.

Technical field

The present application relates to the field of information processing, and in particular, to a task allocation method, apparatus, terminal device, and storage medium.

Background technique

There are one or more case management systems in financial institutions such as banks, securities and insurance. The case management system manages related cases handled by financial institutions. Each case is divided into multiple pending tasks according to its processing flow. If the insurance institution has a claims management system, all claims cases in the insurance institution can be managed through the claims management system. Each claim case can be divided into multiple pending tasks according to its processing flow, wherein the pending tasks include Not limited to claims processing, claims first trial, claims review and claims compensation. In the traditional case management system, each time a processor is assigned a task to be processed, the processing personnel need to manually input a task assignment instruction to allocate the pending task of the relevant case to the processing personnel, and the processing personnel in each task assignment process to be processed. Can only wait, can no longer handle other cases, easy to waste time, resulting in high task time cost. Moreover, at the peak of the case processing, special staff members are also required to arrange the tasks to be processed according to the roles, institutions and capabilities of the processing personnel, resulting in higher labor costs for task assignment.

Summary of the invention

The embodiment of the present application provides a task allocation method, device, terminal device, and storage medium to solve the problem of high time cost of task allocation in the current case management system.

In a first aspect, an embodiment of the present application provides a task allocation method, including:

Obtaining a task allocation instruction, the task assignment instruction including a user ID;

Acquiring, according to the task assignment instruction, a to-be-processed task list, where the to-be-processed task list includes all pending tasks that can be allocated to the user corresponding to the user ID;

Determining whether the task assignment instruction is the first allocation instruction of the day corresponding to the user ID;

If the task assignment instruction is not the first time allocation instruction for the day corresponding to the user ID, obtaining a first task assignment list from the to-be-processed task list, and sending the first task assignment list to the user ID corresponding to the user ID user;

The first task allocation list includes at least one of the to-be-processed tasks, and the number of the to-be-processed tasks in the first task allocation list is a newly added task amount.

In a second aspect, an embodiment of the present application provides a task distribution apparatus, including:

An instruction obtaining module, configured to acquire a task allocation instruction, where the task allocation instruction includes a user ID;

a task list obtaining module, configured to acquire a to-be-processed task list based on the task allocation instruction, where the to-be-processed task list includes all pending tasks that can be allocated to the user corresponding to the user ID;

The instruction determining module is configured to determine whether the task allocation instruction is the first allocation instruction of the day corresponding to the user ID;

a first task obtaining module, configured to acquire a first task allocation list from the to-be-processed task list when the task assignment instruction is not allocated for the first time corresponding to the user ID, and obtain the first task allocation list The first task assignment list includes at least one of the to-be-processed tasks, and the number of the to-be-processed tasks in the first task assignment list is a new task amount.

In a third aspect, an embodiment of the present application provides a terminal device, including a memory, a processor, and computer readable instructions stored in the memory and executable on the processor, where the processor executes the computer The following steps are implemented when reading the instruction:

Obtaining a task allocation instruction, the task assignment instruction including a user ID;

Acquiring, according to the task assignment instruction, a to-be-processed task list, where the to-be-processed task list includes all pending tasks that can be allocated to the user corresponding to the user ID;

Determining whether the task assignment instruction is the first allocation instruction of the day corresponding to the user ID;

If the task assignment instruction is not the first time allocation instruction for the day corresponding to the user ID, obtaining a first task assignment list from the to-be-processed task list, and sending the first task assignment list to the user ID corresponding to the user ID user;

The first task allocation list includes at least one of the to-be-processed tasks, and the number of the to-be-processed tasks in the first task allocation list is a newly added task amount.

A fourth aspect, one or more non-transitory readable storage medium storing computer readable instructions, when executed by one or more processors, characterized in that said one or more The processor performs the following steps:

Obtaining a task allocation instruction, the task assignment instruction including a user ID;

Acquiring, according to the task assignment instruction, a to-be-processed task list, where the to-be-processed task list includes all pending tasks that can be allocated to the user corresponding to the user ID;

Determining whether the task assignment instruction is the first allocation instruction of the day corresponding to the user ID;

If the task assignment instruction is not the first time allocation instruction for the day corresponding to the user ID, obtaining a first task assignment list from the to-be-processed task list, and sending the first task assignment list to the user ID corresponding to the user ID user;

The first task allocation list includes at least one of the to-be-processed tasks, and the number of the to-be-processed tasks in the first task allocation list is a newly added task amount.

Details of one or more embodiments of the present application are set forth in the accompanying drawings and description below. Other features and advantages of the present invention will be apparent from the description, drawings and claims.

DRAWINGS

In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings used in the description of the embodiments of the present application will be briefly described below. It is obvious that the drawings in the following description are only some embodiments of the present application. Other drawings may also be obtained from those of ordinary skill in the art based on these drawings without the inventive labor.

1 is a flowchart of a task assignment method in Embodiment 1 of the present application;

Figure 2 is a specific flow chart of step S20 of Figure 1;

Figure 3 is a specific flow chart of step S50 of Figure 1;

Figure 4 is a specific flow chart of step S52 of Figure 3;

5 is a specific flowchart of step S60 in the task assignment method in Embodiment 1 of the present application;

6 is a schematic diagram of a task distribution device in Embodiment 2 of the present application;

FIG. 7 is a schematic diagram of a terminal device provided in Embodiment 4 of the present application.

Detailed ways

The technical solutions in the embodiments of the present application are clearly and completely described in the following with reference to the drawings in the embodiments of the present application. It is obvious that the described embodiments are a part of the embodiments of the present application, and not all of the embodiments. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments of the present application without departing from the inventive scope are the scope of the present application.

Example 1

FIG. 1 shows a flow chart of a task assignment method in this embodiment. The task assignment method can be applied to a case management system in a financial institution such as a bank, a securities, an insurance, etc., and is used to allocate a task to be processed corresponding to a case to a different processing person for processing, and the degree of automation is high, which is beneficial to improving task assignment efficiency. , saving task allocation time. In this embodiment, the case management system may be a claims management system of the insurance institution.

Any case management system includes a server and a client connected to the server via a network. Specifically, the server is provided with a database or a server connected to the database, and the database includes but is not limited to a database such as a MySQL database or an Oracle database. The database is provided with a case library for storing case information, a user library for storing user information, and an associated library for storing related information.

In this embodiment, the client may be a terminal such as a PC or a tablet, and the client may communicate with the server through a wireless network such as WIFI, 3G, 4G, and 5G or a wired network to implement data transmission. Specifically, the user who handles the case logs in the user interface through the client, inputs a control command, and sends the control command to the server, so that the server can perform the corresponding operation based on the control instruction.

As shown in FIG. 1 , the task allocation method provided in this embodiment includes the following steps:

S10: Acquire a task assignment instruction, where the task assignment instruction includes a user ID.

The task assignment instruction is an instruction for controlling the server to allocate a task to be processed to the user. Specifically, the user logs in to the case management system through the client, and the user needs to input the user ID when logging in, so that the to-be-processed task to be processed by the user corresponding to the user ID is displayed in the display interface of the client. The user can click the corresponding "task assignment" button in the display interface of the client, so that the client inputs a task assignment instruction to the server, so that the server acquires the task assignment instruction. It can be understood that the task assignment instruction can be automatically triggered by a program preset by the user, or can be manually triggered by the user. S20: Obtain a to-be-processed task list based on the task allocation instruction, where the to-be-processed task list includes all pending tasks that can be assigned to the user corresponding to the user ID.

S21: Determine the user attribute based on the user ID in the task assignment instruction.

The server may query user attributes such as the department, user position, and user rank of the user based on the user ID in the task assignment instruction. Specifically, the database query statement may be executed in the user library, and the database query statement performs the query filtering by using the user ID as the field to be searched, thereby determining the user attribute, and the operation process is simple and convenient.

S22: Determine, according to the user attribute, a task attribute that can be assigned to the to-be-processed task processed by the user corresponding to the user ID.

The server may query the association information based on the user attribute acquired in step S21 to determine a task attribute associated with the user attribute as a task attribute of the to-be-processed task that can be assigned to the user corresponding to the user ID. Specifically, the database query statement may be executed in the association library, and the database query statement performs the query filtering by using the user attribute as the field to be searched, thereby obtaining the task attribute, and the operation process is simple and convenient.

S23: Obtain a list of pending tasks based on all pending tasks that are the same as the task attributes.

The server may query and acquire all the case information in the case library that is the same as the task attribute based on the task attribute acquired in step S22, and select all the tasks whose case status is “pending status” from all the case information as all pending tasks, based on all The pending task forms a list of pending tasks. Specifically, the database query statement may be executed in the case library, and the database query statement performs query screening by using the task attribute and the case status as the field to be searched, thereby obtaining a list of pending tasks, and the operation process is simple and convenient.

S30: Determine whether the task assignment instruction is the first allocation instruction of the day corresponding to the user ID.

The first allocation instruction of the day refers to the first task allocation instruction acquired by the server on the same day; that is, the first allocation instruction of the day corresponding to the user ID refers to the first task allocation instruction including the user ID acquired by the server on the same day. Each time the server obtains a task assignment instruction, the log file is used to record the acquisition time and user ID of the task assignment instruction, so as to determine whether the task assignment instruction is the same day.

S40: If the task assignment instruction is the first allocation instruction of the day corresponding to the user ID, the second task allocation list is obtained from the to-be-processed task list, and the second task allocation list is sent to the user corresponding to the user ID; wherein, the second task The distribution list includes at least one pending task, and the number of pending tasks in the second task allocation list is a preset minimum amount of tasks.

S50: If the task assignment instruction is not the first time allocation instruction corresponding to the user ID, the first task assignment list is obtained from the to-be-processed task list, and the first task assignment list is sent to the user corresponding to the user ID; The task allocation list includes at least one pending task, and the number of pending tasks in the first task allocation list is the newly added task amount.

In a specific implementation, as shown in FIG. 3, in step S50, obtaining the first task allocation list from the to-be-processed task list specifically includes the following steps:

S51: Acquire a current amount of the to-be-processed task corresponding to the user ID based on the task allocation instruction.

The current pending task volume refers to the amount of tasks that have been assigned to the user corresponding to the user ID but the user has not completed the processing, that is, the case status of all pending tasks assigned to the user ID on the day of the case management system is “in-process status”. The amount of tasks. In this embodiment, the server counts all the task quantities in the second task allocation list corresponding to the user ID that are currently in the process status as the current pending task quantity, or the second data corresponding to the current user ID. The task allocation list and the first task allocation list all the task quantities whose case status is "Processing Status" as the current amount of pending tasks.

S52: Determine a processable task amount corresponding to the user ID based on the acquisition time of the task assignment instruction.

In a specific embodiment, as shown in FIG. 4, in step S52, determining the amount of the processable task corresponding to the user ID based on the acquisition time of the task assignment instruction specifically includes the following steps:

S521: Determine the remaining working time of the day based on the acquisition time of the task allocation instruction.

In this embodiment, if the acquisition time of the task assignment instruction is after the rest time, the rest time of the day is not required to be deducted; if the acquisition time of the task assignment instruction is before the rest time, the current remaining work time is deducted. Break time.

S522: Determine a unit task processing time of the to-be-processed task based on the acquisition time of the task assignment instruction and the acquisition time of the previous task assignment instruction.

The unit task processing time refers to the time required to complete the processing of a pending task. The user can input a task completion instruction after the task to be processed is completed, and trigger a task assignment instruction based on the task completion instruction.

S523: Determine the amount of the workable task corresponding to the user ID based on the remaining working time of the day and the unit task processing time.

Since the remaining working time of the day is the effective working time of the user on the day, and the unit task processing time is the time required to complete the processing of a pending task, dividing the remaining working time of the day by the unit task processing time, the quotient of the two is Determined as the amount of workable tasks corresponding to the user ID.

In step S521-S523, by calculating the remaining working time and the unit task processing time of the day, and determining the user-processable task amount, so as to allocate the task to the user reasonably, the task assigned to the user corresponding to the user ID can be avoided. As a result, the user cannot process the corresponding pending tasks in time to form a backlog of pending tasks, thereby causing the customer to have less satisfaction with the service of the financial institution; and also avoiding too small a task assigned to the user, resulting in processing efficiency of the pending task. Lower.

S53: Determine the amount of new tasks based on the current amount of tasks to be processed and the amount of tasks that can be processed.

The current amount of tasks to be processed is the amount of tasks that have been allocated to the user but not processed, and the amount of tasks that can be processed by the user corresponding to the user ID can be processed by calculating the amount of tasks that can be processed and the amount of tasks to be processed. The difference is determined to determine the amount of new tasks that can be reassigned to the user corresponding to the ID.

S54: Select a to-be-processed task that is consistent with the number of newly added tasks from the to-be-processed task list to obtain a first task allocation list.

In step S51 - step S54, the current task to be processed and the amount of processable tasks corresponding to the user ID are determined by the acquisition time of the task assignment instruction, and the new task amount is determined based on the current task volume to be processed and the amount of the processable task. Selecting, from the to-be-processed task list, a set of pending tasks that is consistent with the number of newly added tasks, as the first task allocation list, and assigning the first task allocation list to the user corresponding to the user ID, so that the user corresponding to the user ID is When the task to be processed is processed based on the first task allocation list, the task processing efficiency can be ensured, and the overdue backlog of the pending task can be avoided.

In a specific implementation, before the step S50, that is, before the first task allocation list is obtained from the to-be-processed task list, the task assignment method further includes the step S60: determining whether to continue assigning the to-be-processed task to the user corresponding to the user ID. . As shown in FIG. 5, step S60 specifically includes the following steps:

S61: Acquire an upper limit control instruction, where the upper limit control instruction includes a user ID and a task allocation upper limit amount.

The task allocation upper limit is a user-defined maximum value used to control the task management system to allocate pending tasks on the same day. In this embodiment, the user clicks the "upper limit control" button in the display page of the client, enters the task allocation upper limit amount in the control page that is entered later, and then clicks the "submit" button to send an upper limit control command to the server, Cause the server to obtain the upper limit control instruction.

S62: Acquire, according to the task allocation instruction, the current to-be-processed task amount corresponding to the user ID and the currently completed task amount.

In this embodiment, the database query statement is executed in the database, and the user ID and the date are the same day, and the user status is “in-process status” and “complete processing status” as the search field for query and screening, so that the current ID corresponding to the user ID can be determined. Process the amount of tasks and the amount of tasks currently completed.

S63: Acquire the current total task amount based on the current task volume to be processed and the currently completed task volume.

The current task total is the sum of the current pending task amount corresponding to the user ID and the currently completed task amount, that is, the current total task amount is the sum of all pending tasks assigned to the user corresponding to the user ID on the day of the case management system. .

S64: Determine whether the current total task amount is less than the task allocation upper limit amount.

Specifically, by comparing and determining the total amount of the current task corresponding to the user ID and the size of the task allocation upper limit, it is determined whether the user corresponding to the user ID needs to be assigned a new pending task again to achieve a reasonable allocation.

S65: If the current task total is less than the task allocation upper limit quantity, execute the first task allocation list from the to-be-processed task list.

Specifically, if the total number of current tasks corresponding to the user ID is smaller than the task allocation upper limit corresponding to the user ID, the number of pending tasks that are currently allocated to the user corresponding to the user ID is not up to the user corresponding to the user ID. The maximum value of the task to be processed enables the case management system to continue to assign the pending task to the user, and to perform the step of obtaining the first task allocation list from the to-be-processed task list (ie, performing step S50).

S66: If the current total task is not less than the task allocation upper limit, stop assigning the pending task to the user corresponding to the user ID.

In step S61-S66, the current task totals corresponding to all the pending tasks assigned to the user corresponding to the user ID are obtained by calculation, and the current task total and the task allocation upper limit value are compared to determine whether the user ID needs to be corresponding. The user continues to allocate the pending tasks to ensure the reasonable allocation of the tasks, and avoids the task of assigning the tasks to be processed to the user corresponding to the user ID is too heavy, resulting in a backlog of pending tasks and affecting the customer's service satisfaction with the financial institution. degree.

It should be understood that the size of the sequence of the steps in the above embodiments does not mean that the order of execution is performed. The order of execution of each process should be determined by its function and internal logic, and should not be construed as limiting the implementation process of the embodiments of the present application.

Example 2

Fig. 6 is a block diagram showing the principle of the task assignment apparatus corresponding to the task assignment method in the first embodiment. As shown in FIG. 6, the task distribution apparatus includes an instruction acquisition module 10, a task list acquisition module 20, an instruction determination module 30, a first task acquisition module 50, a second task acquisition module 40, and a task assignment determination module 60. The implementation functions of the instruction acquisition module 10, the task list acquisition module 20, the instruction determination module 30, the first task acquisition module 50, the second task acquisition module 40, and the task assignment determination module 60 respectively correspond to the task assignment method in Embodiment 1. Steps S10, S20, S30, S50, S40, and S60 are in one-to-one correspondence. To avoid redundancy, the present embodiment will not be described in detail.

The instruction acquisition module 10 is configured to acquire a task assignment instruction, where the task assignment instruction includes a user ID.

The task list obtaining module 20 is configured to obtain a to-be-processed task list based on the task allocation instruction, where the to-be-processed task list includes all pending tasks that can be assigned to the user corresponding to the user ID.

The command determining module 30 is configured to determine whether the task allocation instruction is the first allocation instruction of the day corresponding to the user ID.

The first task obtaining module 50 is configured to obtain a first task allocation list from the to-be-processed task list when the task allocation instruction is not allocated for the first time corresponding to the user ID, and send the first task allocation list to the user ID corresponding to the user ID User.

The first task allocation list includes at least one to-be-processed task, and the number of to-be-processed tasks in the first task allocation list is a newly added task amount.

Preferably, the second task obtaining module 40 is configured to obtain a second task allocation list from the to-be-processed task list when the task allocation instruction is the first time allocation instruction corresponding to the user ID, and send the second task allocation list to the user. The user corresponding to the ID.

The second task allocation list includes at least one to-be-processed task, and the number of to-be-processed tasks in the second task allocation list is a preset minimum task amount.

Preferably, the first task acquisition module 50 includes a current task amount acquisition unit 51, a processable task amount acquisition unit 52, a new task amount acquisition unit 53, and a task assignment list acquisition unit 54.

The current task quantity obtaining unit 51 is configured to acquire a current task quantity to be processed corresponding to the user ID based on the task allocation instruction.

The processable amount acquisition unit 52 is configured to determine a processable task amount corresponding to the user ID based on the acquisition time of the task assignment instruction.

The newly added task amount obtaining unit 53 is configured to determine the newly added task amount based on the current task amount to be processed and the amount of the processable task;

The task assignment list obtaining unit 54 is configured to select a to-be-processed task that is consistent with the number of newly added task quantities from the to-be-processed task list to obtain a first task assignment list.

Preferably, the processable task amount acquisition unit 52 includes a remaining time determination unit 521, a unit time determination unit 522, and a task amount determination sub-unit 523.

The remaining time determination sub-unit 521 is configured to determine the remaining work time of the day based on the acquisition time of the task assignment instruction.

The unit time determining sub-unit 522 is configured to determine the unit task processing time of the task to be processed based on the acquisition time of the task assignment instruction and the acquisition time of the previous task assignment instruction.

The task amount determining sub-unit 523 is configured to determine a processable task amount corresponding to the user ID based on the remaining working time of the day and the unit task processing time.

Preferably, the task assignment device further includes a task assignment determination module 60 for determining whether to continue assigning the task to be processed to the user corresponding to the user ID. The task assignment determination module 60 includes an upper limit control instruction acquisition unit 61, a first current task acquisition unit 62, a second current task acquisition unit 63, a task determination unit 64, a first processing unit 65, and a second processing unit 66.

The upper limit control instruction acquiring unit 61 is configured to acquire an upper limit control instruction, and the upper limit control instruction includes a user ID and a task allocation upper limit amount.

The first current task obtaining unit 62 is configured to acquire, according to the task assignment instruction, the current to-be-processed task amount and the currently completed task amount corresponding to the user ID.

The second current task quantity obtaining unit 63 is configured to obtain the current task total amount based on the current task quantity to be processed and the currently completed task quantity.

The task amount determining unit 64 is configured to determine whether the current task total amount is less than the task allocation upper limit amount.

The first processing unit 65 is configured to: when the current task total amount is less than the task allocation upper limit amount, execute the first task allocation list from the to-be-processed task list.

The second processing unit 66 is configured to stop assigning the to-be-processed task to the user corresponding to the user ID when the current task total amount is not less than the task allocation upper limit amount.

Preferably, the task list acquisition module 20 includes a user attribute determination unit 21, a task attribute determination unit 22, and a to-be-processed task acquisition unit 23.

The user attribute determining unit 21 is configured to determine the user attribute based on the user ID in the task assignment instruction.

The task attribute determining unit 22 is configured to determine, according to the user attribute, a task attribute that can be assigned to the task to be processed processed by the user corresponding to the user ID.

The to-be-processed task obtaining unit 23 is configured to obtain a to-be-processed task list based on all pending tasks that are the same as the task attribute.

Example 3

The embodiment provides one or more non-volatile readable storage media having computer readable instructions that, when executed by one or more processors, cause the one or more processors to perform The steps of the task assignment method in Embodiment 1 are not repeated here to avoid repetition. Alternatively, when the computer readable instructions are executed by the processor, the functions of the modules/units in the task distribution apparatus in Embodiment 2 are implemented. To avoid repetition, details are not described herein again.

It will be understood that one or more non-volatile readable storage media storing computer readable instructions may comprise: any entity or device capable of carrying the computer readable instructions, a recording medium, a USB flash drive, a mobile hard drive, a magnetic Discs, optical discs, computer memories, Read-Only Memory (ROM), Random Access Memory (RAM), electrical carrier signals, and telecommunications signals.

Example 4

FIG. 7 is a schematic diagram of a terminal device according to an embodiment of the present application. As shown in FIG. 7, the terminal device 70 of this embodiment includes a processor 71, a memory 72, and computer readable instructions 73 stored in the memory 72 and operable on the processor 71. When the processor 71 executes the computer readable instructions 73, the steps S10-S60 in the task assignment method in the above-described Embodiment 1 are implemented. Alternatively, when the processor 71 executes the computer readable instructions 73, the functions of the modules/units in the foregoing device embodiments are implemented, such as the instruction acquisition module 10, the task list acquisition module 20, the instruction determination module 30, and the first task shown in FIG. The functions of the acquisition module 50, the second task acquisition module 40, and the task assignment determination module 60 are obtained.

The embodiments described above are only used to explain the technical solutions of the present application, and are not limited thereto. Although the present application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that the technical solutions described in the foregoing embodiments may be modified or equivalently substituted for some of the technical features. Modifications or substitutions do not depart from the spirit and scope of the technical solutions of the embodiments of the present application, and should be included in the scope of the present application.

Claims (20)

  1. A task assignment method, comprising:
    Obtaining a task allocation instruction, the task assignment instruction including a user ID;
    Acquiring, according to the task assignment instruction, a to-be-processed task list, where the to-be-processed task list includes all pending tasks that can be allocated to the user corresponding to the user ID;
    Determining whether the task assignment instruction is the first allocation instruction of the day corresponding to the user ID;
    If the task assignment instruction is not the first time allocation instruction for the day corresponding to the user ID, obtaining a first task assignment list from the to-be-processed task list, and sending the first task assignment list to the user ID corresponding to the user ID user;
    The first task allocation list includes at least one of the to-be-processed tasks, and the number of the to-be-processed tasks in the first task allocation list is a newly added task amount.
  2. The task assignment method according to claim 1, wherein the determining whether the task assignment instruction is the first assignment instruction for the day corresponding to the user ID, and further comprising:
    And if the task assignment instruction is the first allocation instruction of the day corresponding to the user ID, acquiring a second task allocation list from the to-be-processed task list, and sending the second task allocation list to the user corresponding to the user ID ;
    The second task allocation list includes at least one to-be-processed task, and the number of the to-be-processed tasks in the second task allocation list is a preset minimum task amount.
  3. The task assignment method according to claim 1, wherein the obtaining the first task assignment list from the to-be-processed task list comprises:
    Obtaining a current amount of the to-be-processed task corresponding to the user ID based on the task assignment instruction;
    Determining a manageable task amount corresponding to the user ID based on an acquisition time of the task assignment instruction;
    Determining the newly added task amount based on the current to-be-processed task amount and the processable task amount;
    And selecting, from the to-be-processed task list, the to-be-processed task that is consistent with the quantity of the newly added task, to obtain the first task allocation list.
  4. The task assignment method according to claim 3, wherein the determining the amount of the processable task corresponding to the user ID based on the acquisition time of the task assignment instruction comprises:
    Determining the remaining working time of the day based on the acquisition time of the task assignment instruction;
    Determining a unit task processing time of the to-be-processed task based on an acquisition time of the task assignment instruction and an acquisition time of a previous task assignment instruction;
    Based on the remaining work time of the day and the unit task processing time, the amount of manageable tasks corresponding to the user ID is determined.
  5. The task assignment method according to claim 1, wherein the obtaining the first task assignment list from the to-be-processed task list further includes:
    Obtaining an upper limit control instruction, the upper limit control instruction including a user ID and a task allocation upper limit amount;
    Obtaining, according to the task assignment instruction, a current to-be-processed task amount corresponding to the user ID and a currently completed task amount;
    Obtaining a current total task amount based on the current to-be-processed task amount and the currently completed task amount;
    Determining whether the total amount of the current task is less than the task allocation upper limit amount;
    And if the current task total amount is less than the task allocation upper limit amount, performing obtaining a first task allocation list from the to-be-processed task list;
    If the total amount of the current task is not less than the task allocation upper limit, the user corresponding to the user ID is stopped from being allocated the to-be-processed task.
  6. The task assignment method according to claim 1, wherein the obtaining a task list to be processed based on the task assignment instruction comprises:
    Determining a user attribute based on a user ID in the task assignment instruction;
    Determining, according to the user attribute, a task attribute of the to-be-processed task that can be allocated to a user corresponding to the user ID;
    The to-be-processed task list is obtained based on all the pending tasks that are the same as the task attributes.
  7. A task distribution device, comprising:
    An instruction obtaining module, configured to acquire a task allocation instruction, where the task allocation instruction includes a user ID;
    a task list obtaining module, configured to acquire a to-be-processed task list based on the task allocation instruction, where the to-be-processed task list includes all pending tasks that can be allocated to the user corresponding to the user ID;
    The instruction determining module is configured to determine whether the task allocation instruction is the first allocation instruction of the day corresponding to the user ID;
    a first task obtaining module, configured to acquire a first task allocation list from the to-be-processed task list when the task assignment instruction is not allocated for the first time corresponding to the user ID, and obtain the first task allocation list Sending to the user corresponding to the user ID;
    The first task allocation list includes at least one of the to-be-processed tasks, and the number of the to-be-processed tasks in the first task allocation list is a newly added task amount.
  8. The task distribution device according to claim 7, wherein the task distribution device further comprises:
    a second task obtaining module, configured to acquire a second task allocation list from the to-be-processed task list when the task allocation instruction is the first time allocation instruction corresponding to the user ID, and send the second task allocation list Giving the user corresponding to the user ID;
    The second task allocation list includes at least one to-be-processed task, and the number of the to-be-processed tasks in the second task allocation list is a preset minimum task amount.
  9. A terminal device comprising a memory, a processor, and computer readable instructions stored in the memory and operable on the processor, wherein the processor executes the computer readable instructions as follows step:
    Obtaining a task allocation instruction, the task assignment instruction including a user ID;
    Acquiring, according to the task assignment instruction, a to-be-processed task list, where the to-be-processed task list includes all pending tasks that can be allocated to the user corresponding to the user ID;
    Determining whether the task assignment instruction is the first allocation instruction of the day corresponding to the user ID;
    If the task assignment instruction is not the first time allocation instruction for the day corresponding to the user ID, obtaining a first task assignment list from the to-be-processed task list, and sending the first task assignment list to the user ID corresponding to the user ID user;
    The first task allocation list includes at least one of the to-be-processed tasks, and the number of the to-be-processed tasks in the first task allocation list is a newly added task amount.
  10. The terminal device according to claim 9, wherein after said step of determining whether said task assignment instruction is the first time allocation instruction on the day corresponding to the user ID, said processor executes said computer readable instruction Implement the following steps:
    And if the task assignment instruction is the first allocation instruction of the day corresponding to the user ID, acquiring a second task allocation list from the to-be-processed task list, and sending the second task allocation list to the user corresponding to the user ID ;
    The second task allocation list includes at least one to-be-processed task, and the number of the to-be-processed tasks in the second task allocation list is a preset minimum task amount.
  11. The terminal device according to claim 9, wherein the obtaining the first task allocation list from the to-be-processed task list comprises:
    Obtaining a current amount of the to-be-processed task corresponding to the user ID based on the task assignment instruction;
    Determining a manageable task amount corresponding to the user ID based on an acquisition time of the task assignment instruction;
    Determining the newly added task amount based on the current to-be-processed task amount and the processable task amount;
    And selecting, from the to-be-processed task list, the to-be-processed task that is consistent with the quantity of the newly added task, to obtain the first task allocation list.
  12. The terminal device according to claim 11, wherein the determining the amount of the processable task corresponding to the user ID based on the acquisition time of the task assignment instruction comprises:
    Determining the remaining working time of the day based on the acquisition time of the task assignment instruction;
    Determining a unit task processing time of the to-be-processed task based on an acquisition time of the task assignment instruction and an acquisition time of a previous task assignment instruction;
    A processable task amount corresponding to the user ID is determined based on the remaining work time of the day and the unit task processing time.
  13. The terminal device according to claim 9, wherein the determining the amount of the processable task corresponding to the user ID based on the acquisition time of the task assignment instruction comprises:
    Obtaining an upper limit control instruction, the upper limit control instruction including a user ID and a task allocation upper limit amount;
    Obtaining, according to the task assignment instruction, a current to-be-processed task amount corresponding to the user ID and a currently completed task amount;
    Obtaining a current total task amount based on the current to-be-processed task amount and the currently completed task amount;
    Determining whether the total amount of the current task is less than the task allocation upper limit amount;
    And if the current task total amount is less than the task allocation upper limit amount, performing obtaining a first task allocation list from the to-be-processed task list;
    If the total amount of the current task is not less than the task allocation upper limit, the user corresponding to the user ID is stopped from being allocated the to-be-processed task.
  14. The terminal device according to claim 9, wherein the obtaining a to-be-processed task list based on the task assignment instruction comprises:
    Determining a user attribute based on a user ID in the task assignment instruction;
    Determining, according to the user attribute, a task attribute of the to-be-processed task that can be allocated to a user corresponding to the user ID;
    The to-be-processed task list is obtained based on all the pending tasks that are the same as the task attributes.
  15. One or more non-transitory readable storage mediums storing computer readable instructions, wherein when the computer readable instructions are executed by one or more processors, cause the one or more processors to execute The following steps:
    Obtaining a task allocation instruction, the task assignment instruction including a user ID;
    Acquiring, according to the task assignment instruction, a to-be-processed task list, where the to-be-processed task list includes all pending tasks that can be allocated to the user corresponding to the user ID;
    Determining whether the task assignment instruction is the first allocation instruction of the day corresponding to the user ID;
    If the task assignment instruction is not the first time allocation instruction for the day corresponding to the user ID, obtaining a first task assignment list from the to-be-processed task list, and sending the first task assignment list to the user ID corresponding to the user ID user;
    The first task allocation list includes at least one of the to-be-processed tasks, and the number of the to-be-processed tasks in the first task allocation list is a newly added task amount.
  16. The non-volatile readable storage medium according to claim 15, wherein said computer readable instruction is after said step of determining whether said task assignment instruction is the first time allocation instruction on the day corresponding to the user ID When the one or more processors are executed, the one or more processors are further configured to perform the following steps:
    And if the task assignment instruction is the first allocation instruction of the day corresponding to the user ID, acquiring a second task allocation list from the to-be-processed task list, and sending the second task allocation list to the user corresponding to the user ID ;
    The second task allocation list includes at least one to-be-processed task, and the number of the to-be-processed tasks in the second task allocation list is a preset minimum task amount.
  17. The non-volatile readable storage medium according to claim 15, wherein said obtaining a first task allocation list from said to-be-processed task list;
    The computer program is executed by the processor to implement the following steps:
    Obtaining a current amount of the to-be-processed task corresponding to the user ID based on the task assignment instruction;
    Determining a manageable task amount corresponding to the user ID based on an acquisition time of the task assignment instruction;
    Determining the newly added task amount based on the current to-be-processed task amount and the processable task amount;
    And selecting, from the to-be-processed task list, the to-be-processed task that is consistent with the quantity of the newly added task, to obtain the first task allocation list.
  18. The non-volatile readable storage medium according to claim 17, wherein the determining the amount of processable tasks corresponding to the user ID based on the acquisition time of the task assignment instruction comprises:
    Determining the remaining working time of the day based on the acquisition time of the task assignment instruction;
    Determining a unit task processing time of the to-be-processed task based on an acquisition time of the task assignment instruction and an acquisition time of a previous task assignment instruction;
    A processable task amount corresponding to the user ID is determined based on the remaining work time of the day and the unit task processing time.
  19. The non-volatile readable storage medium according to claim 15, wherein the obtaining the first task allocation list from the to-be-processed task list further comprises:
    Obtaining an upper limit control instruction, the upper limit control instruction including a user ID and a task allocation upper limit amount;
    Obtaining, according to the task assignment instruction, a current to-be-processed task amount corresponding to the user ID and a currently completed task amount;
    Obtaining a current total task amount based on the current to-be-processed task amount and the currently completed task amount;
    Determining whether the total amount of the current task is less than the task allocation upper limit amount;
    And if the current task total amount is less than the task allocation upper limit amount, performing obtaining a first task allocation list from the to-be-processed task list;
    If the total amount of the current task is not less than the task allocation upper limit, the user corresponding to the user ID is stopped from being allocated the to-be-processed task.
  20. The non-volatile readable storage medium according to claim 15, wherein the obtaining a to-be-processed task list based on the task assignment instruction comprises:
    Determining a user attribute based on a user ID in the task assignment instruction;
    Determining, according to the user attribute, a task attribute of the to-be-processed task that can be allocated to a user corresponding to the user ID;
    The to-be-processed task list is obtained based on all the pending tasks that are the same as the task attributes.
PCT/CN2018/081420 2017-07-28 2018-03-30 Task allocating method and device, terminal device and storage medium WO2019019687A1 (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN201710627510.5A CN107832901A (en) 2017-07-28 2017-07-28 Method for allocating tasks, device, terminal device and storage medium
CN201710627510.5 2017-07-28

Publications (1)

Publication Number Publication Date
WO2019019687A1 true WO2019019687A1 (en) 2019-01-31

Family

ID=61643149

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/081420 WO2019019687A1 (en) 2017-07-28 2018-03-30 Task allocating method and device, terminal device and storage medium

Country Status (2)

Country Link
CN (1) CN107832901A (en)
WO (1) WO2019019687A1 (en)

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107832901A (en) * 2017-07-28 2018-03-23 平安科技(深圳)有限公司 Method for allocating tasks, device, terminal device and storage medium
CN108629560A (en) * 2018-04-18 2018-10-09 平安科技(深圳)有限公司 Task distributing method, electronic equipment and storage medium
CN108876051A (en) * 2018-06-28 2018-11-23 中国建设银行股份有限公司 Personnel assignment method and device
CN109255515A (en) * 2018-07-24 2019-01-22 武汉空心科技有限公司 A kind of task exploitation cloud platform based on page metering and unit time distribution

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104077701A (en) * 2014-06-09 2014-10-01 中国建设银行股份有限公司 Task processing method and device used for e-business platform
CN104392310A (en) * 2014-11-13 2015-03-04 深圳市玖昔物联科技发展有限公司 Networked work coordinated management system
CN105160453A (en) * 2015-07-16 2015-12-16 北京中亦安图科技股份有限公司 Task allocating method, device, and system based on location service
CN105809323A (en) * 2016-02-23 2016-07-27 平安科技(深圳)有限公司 Task allocation method and system
CN107832901A (en) * 2017-07-28 2018-03-23 平安科技(深圳)有限公司 Method for allocating tasks, device, terminal device and storage medium

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2011232788A (en) * 2010-04-23 2011-11-17 Nec Corp Workflow management system, workflow management method, and workflow management program
CN104239148B (en) * 2013-06-06 2018-05-18 腾讯科技(深圳)有限公司 A kind of distributed task dispatching method and device

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104077701A (en) * 2014-06-09 2014-10-01 中国建设银行股份有限公司 Task processing method and device used for e-business platform
CN104392310A (en) * 2014-11-13 2015-03-04 深圳市玖昔物联科技发展有限公司 Networked work coordinated management system
CN105160453A (en) * 2015-07-16 2015-12-16 北京中亦安图科技股份有限公司 Task allocating method, device, and system based on location service
CN105809323A (en) * 2016-02-23 2016-07-27 平安科技(深圳)有限公司 Task allocation method and system
CN107832901A (en) * 2017-07-28 2018-03-23 平安科技(深圳)有限公司 Method for allocating tasks, device, terminal device and storage medium

Also Published As

Publication number Publication date
CN107832901A (en) 2018-03-23

Similar Documents

Publication Publication Date Title
US10210221B2 (en) System and method for distributed database query engines
US20200050968A1 (en) Interactive interfaces for machine learning model evaluations
US9430288B2 (en) Job scheduling based on historical job data
US8924429B1 (en) Determining and extracting changed data from a data source
US10169715B2 (en) Feature processing tradeoff management
US20180314425A1 (en) Non-uniform memory access (numa) resource assignment and re-evaluation
US20180357111A1 (en) Data center operation
JP6542785B2 (en) Implementation of semi-structured data as first class database element
US10560511B2 (en) Adaptive tile framework
US9086902B2 (en) Sending tasks between virtual machines based on expiration times
EP2608067B1 (en) Accelerated query operators for high-speed, in-memory online analyctical processing queries and operations
US10430332B2 (en) System and method for performance tuning of garbage collection algorithms
US20150379430A1 (en) Efficient duplicate detection for machine learning data sets
US20160357816A1 (en) Many-core algorithms for in-memory column store databases
CN103177059B (en) Separate processing path for database computing engines
DE112013001308T5 (en) Managing tenant-specific records in a multi-tenant environment
US8122008B2 (en) Joining tables in multiple heterogeneous distributed databases
US10504120B2 (en) Determining a temporary transaction limit
JP4536817B2 (en) Dynamic relocation of workflow by end user
JP5298117B2 (en) Data merging in distributed computing
US20130091285A1 (en) Discovery-based identification and migration of easily cloudifiable applications
GB2508503A (en) Batch evaluation of remote method calls to an object oriented database
US9477512B2 (en) Task-based modeling for parallel data integration
US9852197B2 (en) ETL tool interface for remote mainframes
US20130263117A1 (en) Allocating resources to virtual machines via a weighted cost ratio

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 18838696

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase in:

Ref country code: DE