Task circulation method and device based on multiple tenants, electronic equipment and readable medium

By obtaining and distributing task information, and combining preset strategies to distribute tasks and review deliverables in a multi-tenant environment, the problem of high complexity of task circulation in a multi-tenant environment is solved, and task circulation is simplified and efficiency improvement is achieved.

CN119031041APending Publication Date: 2024-11-26BEIJING QINGSONG YIKANG INFORMATION TECHNOLOGY CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202410952855.8
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-07-16
Publication Date
2024-11-26

AI Technical Summary

Technical Problem

In a multi-tenant environment, the task transfer method of tenants is more complex and lacks effective solutions.

Method used

By obtaining task information for tasks to be dispatched, the task is dispatched to the target user according to the preset distribution strategy, and the task delivery items submitted by the target user are received and reviewed, and stored in the delivery library, simplifying the task circulation process.

Benefits of technology

The task transfer process in a multi-tenant environment is simplified, the accuracy and efficiency of task allocation are improved, and the complexity of tenant task transfer is reduced.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119031041A_ABST
    Figure CN119031041A_ABST
Patent Text Reader

Abstract

The invention relates to a multi-tenant-based task circulation method and device, electronic equipment and a readable medium, and the method comprises the steps: obtaining task information of a to-be-distributed task, and enabling each piece of task information to carry a tenant identifier corresponding to a current tenant; distributing the to-be-distributed task to the target user according to a preset distribution strategy and the task information; and receiving and checking a task deliverable carrying the tenant identifier submitted by the target user, and storing the checked task deliverable in a deliverable library. The task information of the to-be-distributed task of the current tenant is firstly obtained, then the to-be-distributed task is distributed to the user under the current tenant according to the preset distribution strategy, then the deliverable submitted by the user is checked, and finally the deliverable passing the checking is stored in the deliverable library, so that the task circulation process under the multi-tenant environment is simplified, and the task distribution efficiency is improved. The problem that the task circulation mode of the tenants in the multi-tenant environment is high in complexity is solved.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a multi-tenant-based task flow method, device, electronic device, and readable medium. Background Art

[0002] Multi-tenancy technology is a software architecture technology that allows multiple tenants to share the same software instance. Under this architecture, multiple tenants can use the same set of software services at the same time. Each tenant has its own data and configuration without interfering with each other.

[0003] In a multi-tenant environment, task transfer is a complex and critical process that involves multiple links such as task creation, assignment, monitoring execution, completion, and possible reassignment. When there are multiple tasks to be assigned to users under a tenant, a clear task assignment process needs to be designed to ensure that tasks can be accurately assigned to the right users and track the execution of tasks. Currently, the task transfer method for tenants in a multi-tenant environment is relatively complex.

[0004] To address the above-mentioned problems, no effective solution has been proposed yet. Summary of the invention

[0005] The present application provides a multi-tenant-based task flow method, device, electronic device and readable medium to solve the above-mentioned technical problem of "the complexity of the task flow method of tenants in a multi-tenant environment is high".

[0006] According to one aspect of an embodiment of the present application, the present application provides a task transfer method based on multiple tenants, including: obtaining task information of tasks to be dispatched, wherein each task information carries a tenant identifier corresponding to the current tenant; dispatching the tasks to be dispatched to target users according to a preset dispatching strategy and task information, wherein the target user is at least one user among multiple users under the current tenant; receiving and reviewing task deliverables submitted by the target user carrying the tenant identifier, and storing the reviewed task deliverables in the deliverable library.

[0007] Optionally, the tasks to be dispatched are dispatched to the target users according to a preset dispatching strategy and task information, including: when the preset dispatching strategy is a first dispatching strategy, obtaining user information of multiple users under the current tenant; selecting a first user matching the task information from the multiple users according to the user information, and determining a first task among the tasks to be dispatched, wherein the first task is a task among the tasks to be dispatched that can be completed by the first user; determining the first user as the target user, and dispatching the first task to the target user.

[0008] Optionally, the tasks to be dispatched are dispatched to the target user according to a preset dispatching strategy and task information, including: when the preset dispatching strategy is a second dispatching strategy, determining a second user from multiple users under the current tenant; obtaining user information of the second user, and matching the task information with the user information of the second user to obtain a second task corresponding to the user information, wherein the second task is a task among the tasks to be dispatched that can be completed by the second user; determining the second user as the target user, and dispatching the second task to the target user.

[0009] Optionally, the tasks to be dispatched are dispatched to the target user according to a preset dispatching strategy and task information, including: when the preset dispatching strategy is a third dispatching strategy, after dispatching the first task to the target user, determining an undispatched third task in the tasks to be dispatched, and obtaining task information of the third task; determining a third user from multiple users under the current tenant; matching the task information of the third task with the user information of the third user to obtain a fourth task corresponding to the user information of the third user, wherein the fourth task is a task in the third tasks that can be completed by the third user; and dispatching the fourth task to the third user.

[0010] Optionally, the tasks to be dispatched are dispatched to the target user according to a preset dispatching strategy and task information, including: when the preset dispatching strategy is the fourth dispatching strategy, after dispatching the second task to the target user, determining the undispatched fifth task in the tasks to be dispatched, and obtaining the task information of the fifth task; selecting a fourth user matching the task information of the fifth task from multiple users according to the user information of multiple users, and determining a sixth task in the fifth task, wherein the sixth task is a task in the fifth task that can be completed by the fourth user; and dispatching the sixth task to the fourth user.

[0011] Optionally, obtaining task information of tasks to be dispatched includes: obtaining a task template corresponding to the task to be dispatched, wherein the task template is pre-edited by a tenant manager, and the task template includes multiple editing areas, and the multiple editing areas include a task requirement area, a task type area, and a task reward area; extracting task requirements, task types, and task rewards of the tasks to be dispatched from the task template; and determining the task requirements, task types, and task rewards as task information.

[0012] Optionally, after receiving and reviewing the task deliverables with the tenant identifier submitted by the target user, if the task deliverables fail the review, the task is re-dispatched in any of the following ways: determining the target user to whom the task deliverables are to be sent, and determining the target task corresponding to the task deliverables, and re-dispatching the target task to the target user; determining the target task corresponding to the task deliverables, and distributing the target task again according to a preset distribution strategy.

[0013] According to another aspect of an embodiment of the present application, the present application provides a multi-tenant-based task transfer device, including: an acquisition module, used to obtain task information of tasks to be dispatched, wherein each task information carries a tenant identifier corresponding to the current tenant; a dispatch module, used to dispatch tasks to be dispatched to target users according to a preset dispatch strategy and task information, wherein the target user is at least one user among multiple users under the current tenant; a receiving module, used to receive and review task deliverables carrying the tenant identifier submitted by the target user, and store the reviewed task deliverables in a deliverable library.

[0014] According to another aspect of an embodiment of the present application, the present application provides an electronic device, including a memory, a processor, a communication interface and a communication bus, wherein the memory stores a computer program that can be run on the processor, the memory and the processor communicate through the communication bus and the communication interface, and the steps of the above method are implemented when the processor executes the computer program.

[0015] According to another aspect of an embodiment of the present application, the present application also provides a computer-readable medium having a non-volatile program code executable by a processor, and the program code enables the processor to execute the above method.

[0016] The above technical solution provided by the embodiment of the present application has the following advantages compared with the related art:

[0017] The present application adopts a task transfer method based on multi-tenants, including: obtaining task information of tasks to be dispatched, wherein each task information carries a tenant identifier corresponding to the current tenant; dispatching the tasks to be dispatched to the target user according to the preset dispatching strategy and task information, wherein the target user is at least one user among multiple users under the current tenant; receiving and reviewing the task deliverables submitted by the target user with the tenant identifier, and storing the task deliverables that pass the review in the deliverable library. By first obtaining the task information of the tasks to be dispatched of the current tenant, and then dispatching the tasks to be dispatched to the users under the current tenant according to the preset dispatching strategy, then reviewing the deliverables submitted by the users, and finally storing the deliverables that pass the review in the deliverable library, the task transfer process in the multi-tenant environment is simplified, and the problem of the high complexity of the task transfer method of tenants in the multi-tenant environment is solved. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.

[0019] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the related technologies, the drawings required for use in the embodiments or the related technical descriptions are briefly introduced below. Obviously, for ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.

[0020] Figure 1 A schematic diagram of a hardware environment for an optional multi-tenant-based task transfer method provided according to an embodiment of the present application;

[0021] Figure 2 A flowchart of an optional multi-tenant-based task transfer method provided according to an embodiment of the present application;

[0022] Figure 3 A flowchart of another optional multi-tenant-based task transfer method provided according to an embodiment of the present application;

[0023] Figure 4 A block diagram of an optional multi-tenant-based task transfer device provided according to an embodiment of the present application;

[0024] Figure 5 A schematic diagram of an optional electronic device structure provided in an embodiment of the present application. DETAILED DESCRIPTION

[0025] In order to make the purpose, technical solution and advantages of the embodiments of the present application clearer, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of this application.

[0026] In the subsequent description, the suffixes such as "module", "component" or "unit" used to represent elements are only used to facilitate the description of the present application and have no specific meaning. Therefore, "module" and "component" can be used interchangeably.

[0027] Multi-tenancy technology is a software architecture technology that allows multiple tenants to share the same software instance. Under this architecture, multiple tenants can use the same set of software services at the same time. Each tenant has its own data and configuration without interfering with each other.

[0028] In a multi-tenant environment, task transfer is a complex and critical process that involves multiple links such as task creation, assignment, monitoring execution, completion, and possible reassignment. When there are multiple tasks to be assigned to users under a tenant, a clear task assignment process needs to be designed to ensure that tasks can be accurately assigned to the right users and track the execution of tasks. Currently, the task transfer method for tenants in a multi-tenant environment is relatively complex.

[0029] In order to solve the problems mentioned in the background technology, according to one aspect of an embodiment of the present application, an embodiment of a multi-tenant-based task flow method is provided.

[0030] Optionally, in the embodiment of the present application, the multi-tenant-based task transfer method can be applied to Figure 1 In the hardware environment composed of the terminal 101 and the server 103 shown in FIG. Figure 1 As shown, the server 103 is connected to the terminal 101 via a network, and can be used to provide services (information acquisition services, data review services, etc.) for the terminal or a client installed on the terminal. A database 105 can be set on the server or independently of the server to provide data storage services for the server 103. The above-mentioned network includes but is not limited to: a wide area network, a metropolitan area network or a local area network, and the terminal 101 includes but is not limited to a PC, a mobile phone, a tablet computer, etc.

[0031] A multi-tenant-based task transfer method in the embodiment of the present application can be executed by the server 103, or can be executed by the server 103 and the terminal 101 together, such as Figure 2 As shown, including:

[0032] Step 201, obtaining task information of tasks to be dispatched, wherein each task information carries a tenant identifier corresponding to the current tenant;

[0033] Step 203: dispatching the task to be dispatched to the target user according to the preset dispatching strategy and the task information, wherein the target user is at least one user among the multiple users under the current tenant;

[0034] Step 205: receiving and reviewing the task deliverables with the tenant identification submitted by the target user, and storing the reviewed task deliverables in the deliverables library.

[0035] The multi-tenant-based task transfer method provided in this application is applied to any tenant end in a multi-tenant architecture, and each tenant end can independently obtain task information, assign tasks, and monitor task completion status and other processes.

[0036] Each tenant can register as a new tenant through the tenant management module, and then use the snowflake algorithm to generate a tenant ID as a unique tenant ID in the system and assign it to the newly registered tenant. All task flow interfaces need to carry the tenant ID, and the system will isolate data based on the tenant ID.

[0037] Each user can register as a task user through the user registration module. When registering, the system will collect the user's information, including but not limited to name, age, gender, skills, and contact information. The user information will also include whether the user is currently in a state where he can receive tasks. If the user is in a state where he can receive tasks, tasks can be assigned to the user. If the user is not in a state where he can receive tasks, tasks will not be assigned to the user.

[0038] Tasks can be assigned on the tenant side, and the current tenant's pending tasks can be assigned to the tenant's users. After the user completes the task in the unified task interface, he / she submits the task deliverable. It should be noted that the same user may receive multiple tasks from multiple tenants, and each task information will carry the corresponding tenant ID. After the user completes the task, he / she submits the tenant ID and the task deliverable to the system, and the system will send the task deliverable to the corresponding tenant according to the tenant ID.

[0039] The task information provided in this application includes but is not limited to task requirements (such as how many words an article requires, how long a video requires, etc.), task types (such as collecting videos, collecting articles, etc.) and task rewards (such as rewards in cash, points, physical objects, etc.).

[0040] The tenant side reviews the task deliverables submitted by the user. If the review is passed, the task deliverables will be stored in the current tenant's deliverable library. The deliverable libraries of different tenants are independent, and each tenant can view and export task deliverables in its own deliverable library.

[0041] When distributing tasks, the present application provides the concepts of distributing tasks based on user dimensions and distributing tasks based on task dimensions. Simply put, distributing tasks based on user dimensions is to find tasks that are more suitable for the user, and then distribute the matching tasks to the user; distributing tasks based on task dimensions is to find the user who is most capable of handling the task, and then distribute the task to the capable user.

[0042] You can choose to distribute tasks based on user dimension or task dimension, or you can combine them (which can be set according to actual needs). Next, we will explain in detail how to distribute tasks to target users based on preset distribution strategies and task information.

[0043] It should be noted that the same task may require multiple completion results, so a task can actually have multiple dispatch times, so different users may receive the same task.

[0044] As an optional embodiment, tasks to be dispatched are dispatched to target users according to a preset dispatching strategy and task information, including: when the preset dispatching strategy is a first dispatching strategy, obtaining user information of multiple users under the current tenant; selecting a first user matching the task information from multiple users according to the user information, and determining a first task among the tasks to be dispatched, wherein the first task is a task among the tasks to be dispatched that can be completed by the first user; determining the first user as a target user, and dispatching the first task to the target user.

[0045] The first distribution strategy provided in this application is a strategy for distribution based on the task dimension.

[0046] Specifically, selecting a first user matching the task information from multiple users according to the user information includes: finding a first user who can meet the task information according to the user information, and determining a first task corresponding to the task information that the first user meets. In simple terms, whichever user has the ability to complete the task will be selected as the first user of the task (i.e., the first task).

[0047] For example, if the task information of task A requires male users to complete it, then a male user is found as the first user based on the user information, and then task A is assigned to the first user. If a large number of male users are found, some of the users can also be selected from multiple male users as the first user.

[0048] By using the first distribution strategy to distribute tasks based on the task dimension, users who are more compatible with the task to be distributed can be found to complete the task, which can further ensure the completion of the task.

[0049] As an optional embodiment, the tasks to be dispatched are dispatched to the target user according to the preset dispatching strategy and task information, including: when the preset dispatching strategy is the second dispatching strategy, determining the second user from multiple users under the current tenant; obtaining the user information of the second user, and matching the task information with the user information of the second user to obtain a second task corresponding to the user information, wherein the second task is a task among the tasks to be dispatched that can be completed by the second user; determining the second user as the target user, and dispatching the second task to the target user.

[0050] The second distribution strategy provided in this application is a distribution strategy based on the user dimension.

[0051] The second user is determined from multiple users under the current tenant. The second user may be a randomly selected user or a specially designated user, which is not limited in this application.

[0052] The user information of the second user is obtained, and then the task information is matched with the user information of the second user to determine which tasks can meet the task requirements of the user information, and the tasks that can meet the requirements are used as the second tasks.

[0053] For example, if the user information of user A indicates that the user is good at writing articles, then a second task whose task type is article writing can be found from the tasks to be assigned, and the second task can be assigned to user A.

[0054] By using the second distribution strategy to distribute tasks based on the user dimension, it is possible to find as many tasks as possible that the user can complete, and to reduce resource loss caused by task switching when the same batch of tasks is distributed to multiple users.

[0055] As an optional embodiment, the tasks to be dispatched are dispatched to the target user according to a preset dispatching strategy and task information, including: when the preset dispatching strategy is a third dispatching strategy, after dispatching the first task to the target user, determining an undispatched third task in the tasks to be dispatched, and obtaining task information of the third task; determining a third user from multiple users under the current tenant; matching the task information of the third task with the user information of the third user to obtain a fourth task corresponding to the user information of the third user, wherein the fourth task is a task in the third tasks that can be completed by the third user; and dispatching the fourth task to the third user.

[0056] The third distribution strategy provided in the present application is a strategy of first performing a first distribution based on the task dimension and then performing a second distribution based on the user dimension.

[0057] The present application does not limit the first distribution strategy to be able to distribute all the tasks to be distributed, so after the first distribution is performed using the first distribution strategy, a second distribution can be continued based on the user dimension.

[0058] The specific steps of performing secondary distribution based on the user dimension are similar to the steps of the above-mentioned first distribution strategy, and this application will not repeat them here.

[0059] As an optional embodiment, the tasks to be dispatched are dispatched to the target user according to a preset dispatching strategy and task information, including: when the preset dispatching strategy is the fourth dispatching strategy, after dispatching the second task to the target user, determining the undispatched fifth task in the tasks to be dispatched, and obtaining the task information of the fifth task; selecting a fourth user matching the task information of the fifth task from multiple users according to the user information of multiple users, and determining the sixth task in the fifth task, wherein the sixth task is a task in the fifth task that can be completed by the fourth user; and dispatching the sixth task to the fourth user.

[0060] The fourth distribution strategy provided in the present application is a strategy of first performing a first distribution based on the user dimension and then performing a second distribution based on the task dimension.

[0061] The present application does not limit the second distribution strategy to being able to distribute all the tasks to be distributed, so after the first distribution is performed using the second distribution strategy, a second distribution can be continued based on the task dimension.

[0062] The specific steps of performing secondary distribution based on the task dimension are similar to the steps of the above-mentioned second distribution strategy, and this application will not repeat them here.

[0063] Preferably, after the task is dispatched, a unified task record will be stored and associated with the corresponding tenant identifier.

[0064] The present application also provides a distribution strategy that combines distribution based on the user dimension and distribution based on the task dimension, which can ensure the quality of task completion as much as possible and reduce resource consumption.

[0065] This application does not limit the distribution of tasks. All tasks to be distributed can be distributed within a preset number of times, or only a part of them can be distributed. The specific adjustments will be made based on the actual situation.

[0066] As an optional embodiment, obtaining task information of tasks to be dispatched includes: obtaining a task template corresponding to the task to be dispatched, wherein the task template is pre-edited by a tenant manager, and the task template includes multiple editing areas, and the multiple editing areas include a task requirement area, a task type area, and a task reward area; extracting task requirements, task types, and task rewards of the tasks to be dispatched from the task template; and determining the task requirements, task types, and task rewards as task information.

[0067] Optionally, the task template is generated by the tenant administrator and can be configured with attributes including task requirements, task type, and task rewards.

[0068] Optionally, tenant managers can select a task template in the task management module, obtain task information, and quickly create multiple tasks to be dispatched.

[0069] Optionally, the current tenant may not use the task template and independently create tasks through the task management module, and may configure attributes including task requirements, task types, and task rewards.

[0070] After the editing area of ​​the task template is filled with task information, the tenant can obtain the task information by extracting the content of each editor area in the task template.

[0071] This application provides unified task template management, which can quickly create tasks based on task templates, and then quickly obtain task information through task templates.

[0072] As an optional embodiment, after receiving and reviewing the task deliverables with the tenant identifier submitted by the target user, if the task deliverables fail the review, the task is re-dispatched in any of the following ways: determining the target user to whom the task deliverables are sent, and determining the target task corresponding to the task deliverables, and re-dispatching the target task to the target user; determining the target task corresponding to the task deliverables, and distributing the target task again according to the preset distribution strategy.

[0073] This application also provides a unified task review capability. The tenant side can review the task results, that is, review the task deliverables returned by the user. The approved task deliverables are stored in the delivery library, and the tenant has the right to view, manage and export the deliverables in the delivery library.

[0074] For example, tenants can view and review task deliverables in the review background. If the review is passed, the deliverable will be entered into the tenant's task deliverable library. If the review is not passed, it can be rejected and returned to the user for re-tasking, or the task can be reassigned to other people to complete (the specific dispatch process is similar to the above dispatch strategy).

[0075] For example, situations where the review fails include: for example, the task is to collect articles, and the content must be related to medicine, but the articles in the task deliverables submitted by the user are related to mathematics, then it is determined that it does not meet the task requirements and fails the review.

[0076] The present application also provides a multi-tenant system architecture, including: a tenant management module, used to perform tenant registration, data modification and other functions; a login module, used to perform tenant login / logout, user login / logout and other functions; a user registration module, used to perform user registration, data modification and other functions; a template management module, used to perform task template creation, editing, deletion and other functions; a task management module, used to perform task creation, editing, deletion and other functions; a task dispatching module: task dispatching; a user task management module, used to perform user task viewing, submission and other functions; a task review module, used to perform task deliverables viewing, review and other functions; a deliverables management module, used to perform task deliverables viewing, export and other functions.

[0077] Figure 3 A flowchart of another multi-tenant-based task transfer method provided for this application is shown in the figure, and the steps include: completing tenant creation after tenant registration; the tenant can log in at the corresponding tenant end; creating a task template, and then creating multiple tasks based on the task template; assigning tasks to users (including assigning tasks by user dimension and assigning tasks by user dimension); receiving task deliverables submitted by users, and then reviewing the task deliverables; if the review is passed, the task deliverables are stored in the task delivery library, if the review is not passed, the task is returned to the user (or the unfinished task can also be reallocated); after logging in to the tenant end, the tenant can export the deliverables to the task delivery library to view the deliverables.

[0078] The present application adopts a task transfer method based on multi-tenants, including: obtaining task information of tasks to be dispatched, wherein each task information carries a tenant identifier corresponding to the current tenant; dispatching the tasks to be dispatched to the target user according to the preset dispatching strategy and task information, wherein the target user is at least one user among multiple users under the current tenant; receiving and reviewing the task deliverables submitted by the target user with the tenant identifier, and storing the task deliverables that pass the review in the deliverable library. By first obtaining the task information of the tasks to be dispatched of the current tenant, and then dispatching the tasks to be dispatched to the users under the current tenant according to the preset dispatching strategy, then reviewing the deliverables submitted by the users, and finally storing the deliverables that pass the review in the deliverable library, the task transfer process in the multi-tenant environment is simplified, and the problem of the high complexity of the task transfer method of tenants in the multi-tenant environment is solved.

[0079] According to another aspect of the embodiment of the present application, the present application provides a task flow device based on multi-tenants, such as Figure 4 As shown, including:

[0080] The acquisition module 402 is used to acquire task information of the task to be dispatched, wherein each task information carries a tenant identifier corresponding to the current tenant;

[0081] A dispatching module 404, configured to dispatch the to-be-dispatched task to a target user according to a preset dispatching strategy and task information, wherein the target user is at least one user among a plurality of users under the current tenant;

[0082] The receiving module 406 is used to receive and review the task deliverables with the tenant identification submitted by the target user, and store the reviewed task deliverables in the deliverables library.

[0083] It should be noted that the acquisition module 402 in this embodiment can be used to execute step 201 in the embodiment of the present application, the distribution module 404 in this embodiment can be used to execute step 203 in the embodiment of the present application, and the receiving module 406 in this embodiment can be used to execute step 205 in the embodiment of the present application.

[0084] Optionally, the dispatch module 404 is also used to obtain user information of multiple users under the current tenant when the preset dispatch strategy is the first dispatch strategy; select a first user matching the task information from multiple users based on the user information, and determine a first task among the tasks to be dispatched, wherein the first task is a task among the tasks to be dispatched that can be completed by the first user; determine the first user as a target user, and dispatch the first task to the target user.

[0085] Optionally, the dispatch module 404 is also used to determine a second user from multiple users under the current tenant when the preset dispatch strategy is the second dispatch strategy; obtain user information of the second user, and match the task information with the user information of the second user to obtain a second task corresponding to the user information, wherein the second task is a task that can be completed by the second user among the tasks to be dispatched; determine the second user as a target user, and dispatch the second task to the target user.

[0086] Optionally, the dispatch module 404 is also used to, when the preset dispatch strategy is the third dispatch strategy, determine an undispatched third task among the tasks to be dispatched and obtain task information of the third task after dispatching the first task to the target user; determine a third user from multiple users under the current tenant; match the task information of the third task with the user information of the third user to obtain a fourth task corresponding to the user information of the third user, wherein the fourth task is a task in the third tasks that can be completed by the third user; and dispatch the fourth task to the third user.

[0087] Optionally, the distribution module 404 is also used to, when the preset distribution strategy is the fourth distribution strategy, determine the undistributed fifth task in the tasks to be distributed after distributing the second task to the target user, and obtain the task information of the fifth task; select a fourth user who matches the task information of the fifth task from multiple users based on the user information of multiple users, and determine the sixth task in the fifth task, wherein the sixth task is the task in the fifth task that can be completed by the fourth user; and distribute the sixth task to the fourth user.

[0088] Optionally, the acquisition module 402 is also used to obtain a task template corresponding to the task to be dispatched, wherein the task template is edited in advance by the tenant manager, and the task template includes multiple editing areas, and the multiple editing areas include a task requirement area, a task type area, and a task reward area; extract the task requirements, task type, and task reward of the task to be dispatched from the task template; and determine the task requirements, task type, and task reward as task information.

[0089] Optionally, the device also includes a processing module for, after receiving and reviewing the task deliverables carrying the tenant identifier submitted by the target user, if the task deliverables fail the review, re-dispatching the task in any of the following ways: determining the target user to whom the task deliverables are sent, and determining the target task corresponding to the task deliverables, and re-dispatching the target task to the target user; determining the target task corresponding to the task deliverables, and distributing the target task again according to a preset distribution strategy.

[0090] It should be noted that the examples and application scenarios implemented by the above modules and corresponding steps are the same, but are not limited to the contents disclosed in the above embodiments. It should be noted that the above modules as part of the device can be run in Figure 1 In the hardware environment shown.

[0091] According to another aspect of the embodiments of the present application, the present application provides an electronic device, such as Figure 5 As shown, it includes a memory 501, a processor 503, a communication interface 505 and a communication bus 507. The memory 501 stores a computer program that can be run on the processor 503. The memory 501 and the processor 503 communicate through the communication interface 505 and the communication bus 507. When the processor 503 executes the computer program, the steps of the above method are implemented.

[0092] The memory and processor in the above electronic device communicate via a communication bus and a communication interface. The communication bus may be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. The communication bus may be divided into an address bus, a data bus, a control bus, etc.

[0093] The memory may include a random access memory (RAM) or a non-volatile memory, such as at least one disk memory. Optionally, the memory may also be at least one storage device located away from the aforementioned processor.

[0094] The above-mentioned processor can be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), etc.; it can also be a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components.

[0095] According to another aspect of the embodiments of the present application, a computer-readable medium having a non-volatile program code executable by a processor is provided.

[0096] Optionally, the specific examples in this embodiment may refer to the examples described in the above embodiments, and this embodiment will not be described in detail here.

[0097] When the embodiments of the present application are specifically implemented, reference may be made to the above-mentioned embodiments, which have corresponding technical effects.

[0098] It is understood that the embodiments described herein may be implemented in hardware, software, firmware, middleware, microcode, or a combination thereof. For hardware implementation, the processing unit may be implemented in one or more application specific integrated circuits (ASIC), digital signal processors (DSP), digital signal processing devices (DSPD), programmable logic devices (PLD), field programmable gate arrays (FPGA), general purpose processors, controllers, microcontrollers, microprocessors, other electronic units for performing the functions described in the present application, or a combination thereof.

[0099] For software implementation, the technology described herein can be implemented by a unit that performs the functions described herein. The software code can be stored in a memory and executed by a processor. The memory can be implemented in the processor or outside the processor.

[0100] Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0101] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0102] In the embodiments provided in the present application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the modules is only a logical function division. There may be other division methods in actual implementation, such as multiple modules or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interfaces, devices or units, which can be electrical, mechanical or other forms.

[0103] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0104] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0105] If the function is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on such an understanding, the technical solution of the embodiment of the present application is essentially or the part that contributes to the prior art or the part of the technical solution can be embodied in the form of a software product, which is stored in a storage medium, including several instructions to make a computer device (which can be a personal computer, a server, or a network device, etc.) perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a ROM, a RAM, a magnetic disk or an optical disk. It should be noted that, in this article, relational terms such as "first" and "second" are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply that there is any such actual relationship or order between these entities or operations. Moreover, the term "include", "include" or any other variant thereof is intended to cover non-exclusive inclusion, so that the process, method, article or device including a series of elements includes not only those elements, but also includes other elements that are not explicitly listed, or also includes elements inherent to such a process, method, article or device. Without more constraints, an element defined by the phrase "comprising a..." does not exclude the existence of other identical elements in the process, method, article or apparatus comprising the element.

[0106] The above description is only a specific implementation of the present application, so that those skilled in the art can understand or implement the present application. Various modifications to these embodiments will be apparent to those skilled in the art, and the general principles defined herein can be implemented in other embodiments without departing from the spirit or scope of the present application. Therefore, the present application will not be limited to the embodiments shown herein, but will conform to the widest range consistent with the principles and novel features applied for herein.

Claims

1. A task transfer method based on multi-tenancy, It is characterized in that The method comprises: Obtaining task information of tasks to be dispatched, wherein each of the task information carries a tenant identifier corresponding to the current tenant; Dispatching the to-be-dispatched task to a target user according to a preset dispatching strategy and the task information, wherein the target user is at least one user among the multiple users under the current tenant; Receive and review the task deliverables carrying the tenant identification submitted by the target user, and store the task deliverables that pass the review in the deliverables library.

2. The method according to claim 1, It is characterized in that The step of dispatching the to-be-dispatched task to the target user according to the preset dispatching strategy and the task information includes: When the preset distribution strategy is the first distribution strategy, obtaining user information of the multiple users under the current tenant; Selecting a first user matching the task information from the multiple users according to the user information, and determining a first task among the tasks to be assigned, wherein the first task is a task that can be completed by the first user among the tasks to be assigned; The first user is determined as the target user, and the first task is assigned to the target user.

3. The method according to claim 1, It is characterized in that The step of dispatching the to-be-dispatched task to the target user according to the preset dispatching strategy and the task information includes: In a case where the preset distribution strategy is the second distribution strategy, determining a second user from the multiple users under the current tenant; Acquire user information of the second user, and match the task information with the user information of the second user to obtain a second task corresponding to the user information, wherein the second task is a task that can be completed by the second user among the tasks to be assigned; The second user is determined as the target user, and the second task is assigned to the target user.

4. The method according to claim 2, It is characterized in that The step of dispatching the to-be-dispatched task to the target user according to the preset dispatching strategy and the task information includes: In a case where the preset distribution strategy is the third distribution strategy, after the first task is distributed to the target user, an undistributed third task is determined in the tasks to be distributed, and task information of the third task is obtained; determining a third user from the plurality of users under the current tenant; Matching the task information of the third task with the user information of the third user to obtain a fourth task corresponding to the user information of the third user, wherein the fourth task is a task in the third task that can be completed by the third user; The fourth task is assigned to the third user.

5. The method according to claim 3, It is characterized in that The step of dispatching the to-be-dispatched task to the target user according to the preset dispatching strategy and the task information includes: In a case where the preset distribution strategy is the fourth distribution strategy, after the second task is distributed to the target user, an undistributed fifth task is determined in the tasks to be distributed, and task information of the fifth task is obtained; Selecting a fourth user matching the task information of the fifth task from the multiple users according to the user information of the multiple users, and determining a sixth task in the fifth task, wherein the sixth task is a task in the fifth task that can be completed by the fourth user; The sixth task is assigned to the fourth user.

6. The method according to claim 1, It is characterized in that The step of obtaining the task information of the task to be dispatched includes: Acquire a task template corresponding to the task to be assigned, wherein the task template is edited in advance by a tenant manager, and the task template includes a plurality of editing areas, and the plurality of editing areas include a task requirement area, a task type area, and a task reward area; Extracting the task requirements, task types and task rewards of the task to be assigned from the task template; The task requirement, the task type, and the task reward are determined as the task information.

7. The method according to claim 1, It is characterized in that After receiving and reviewing the task deliverable submitted by the target user and carrying the tenant identifier, if the task deliverable fails to pass the review, the task is reassigned in any of the following ways: Determine a target user to send the task deliverable, determine a target task corresponding to the task deliverable, and re-assign the target task to the target user; The target task corresponding to the task deliverable is determined, and the target task is dispatched again according to the preset dispatching strategy.

8. A task transfer device based on multi-tenancy, It is characterized in that include: An acquisition module, used to acquire task information of tasks to be dispatched, wherein each of the task information carries a tenant identifier corresponding to the current tenant; A dispatching module, configured to dispatch the to-be-dispatched task to a target user according to a preset dispatching strategy and the task information, wherein the target user is at least one user among the multiple users under the current tenant; The receiving module is used to receive and review the task deliverables carrying the tenant identification submitted by the target user, and store the task deliverables that pass the review into the deliverables library.

9. An electronic device comprising a memory, a processor, a communication interface and a communication bus, wherein the memory stores a computer program that can be run on the processor, and the memory and the processor communicate through the communication bus and the communication interface. It is characterized in that When the processor executes the computer program, the steps of the method according to any one of claims 1 to 7 are implemented.

10. A computer readable medium having a non-volatile program code executable by a processor, It is characterized in that The program code enables the processor to execute the method according to any one of claims 1 to 7.