Task distribution and follow-up method, device and system and storage medium

Abstract

The invention provides a task distribution and follow-up method, device and system and a storage medium, and the method comprises the steps: obtaining a first task request from a first message server, and enabling the first task request to comprise a task processing rule; analyzing the first task request according to a task processing rule to determine a second task request, a target task execution terminal and a second message server, and sending the second task request and the target task execution terminal to the second message server; obtaining task execution information from a second message server, and summarizing the task execution information to obtain a task execution progress; and sending the task execution progress to a first message server. Therefore, the task distribution and follow-up process is established for the universal task scene, manual processing is not needed, flexible processing of the task process is achieved, the task completion efficiency is improved, the cost is reduced, and the universality is high.

Description

Technical Field

[0001] The present disclosure relates to the field of computer technology, and in particular to a task distribution and follow-up method, device, system and storage medium. Background Art

[0002] In the process of collaborative office, communication can be carried out based on emails, text messages, phone calls or interviews to improve the efficiency of collaboration. Specifically, tasks can be assigned to specific task executors, and the task executors will feedback the task execution status to the task publisher. Among them, in order to ensure that the task can be completed smoothly, the task publisher needs to pay attention to the execution status of each executor and remind them to avoid delays in progress. In the prior art, a dedicated work order system has emerged to customize the task processing flow, thereby simplifying the task submission and processing process and improving the efficiency of task management.

[0003] However, the above-mentioned existing technologies are too dependent on specific IT systems or email services, and the distribution of tasks requires a lot of customized system development and process adjustments. In addition, the follow-up management of subsequent tasks requires manual processing, lacks flexible handling of the processing flow, is costly and has poor versatility. Summary of the invention

[0004] In order to overcome the problems existing in the related art, the present disclosure provides a task distribution and follow-up method, device, system and storage medium.

[0005] According to a first aspect of an embodiment of the present disclosure, a task distribution and follow-up method is provided, which is applied to a task manager, comprising:

[0006] Acquire a first task request from a first message server, wherein the first task request includes a task processing rule;

[0007] Parsing the first task request according to the task processing rule to determine a second task request, a target task execution terminal, and a second message server, and sending the second task request and the target task execution terminal to the second message server;

[0008] Acquire task execution information from the second message server, and summarize the task execution information to obtain task execution progress;

[0009] The task execution progress is sent to the first message server.

[0010] Optionally, in the embodiment of the present disclosure, the step of parsing the first task request according to the task processing rule to determine the second task request, the target task execution terminal, and the second message server includes:

[0011] Based on the task processing rules, a list of task execution terminals, the number of task reminders and the number of task statistics are obtained;

[0012] Determining a target task execution terminal based on the task issuing terminal corresponding to the first task request and the task execution terminal list;

[0013] Determining a second task request based on the target task execution terminal and the first task request;

[0014] A second message server is determined based on the target task execution terminal, the task reminder quantity and the task statistical quantity.

[0015] The second message server is determined based on the task execution terminal, the task reminder quantity and the task statistical quantity.

[0016] Optionally, in the embodiment of the present disclosure, determining a target task execution terminal based on the task issuing terminal corresponding to the first task request and the task execution terminal list includes:

[0017] Performing a first verification on the task issuing terminal corresponding to the first task request;

[0018] If the first verification passes, a second verification is performed on the task execution terminal in the task execution terminal list, and the task execution terminal that passes the second verification is determined as the target task execution terminal.

[0019] Optionally, in the embodiment of the present disclosure, determining the second message server based on the target task execution terminal, the task reminder quantity and the task statistical quantity includes:

[0020] Determining a candidate message server set based on the target task execution terminal;

[0021] Determine the number of tasks to be sent based on the target task execution terminal, the number of task reminders and the number of task statistics;

[0022] A second message server is determined based on the candidate message server set and the sending quantity.

[0023] Optionally, in an embodiment of the present disclosure, obtaining task execution information from the second message server and aggregating the task execution information to obtain the task execution progress includes: obtaining task execution information from the second message server according to a multiplexing code and a task flag, and aggregating the task execution information to obtain the task execution progress.

[0024] According to a second aspect of an embodiment of the present disclosure, a task distribution and follow-up method is provided, which is applied to a message manager, comprising:

[0025] Receiving a first task request sent by a task issuing terminal;

[0026] receiving a second task request and a target task execution terminal sent by the task manager, and sending the second task request to the corresponding target task execution terminal;

[0027] Receiving task execution information sent by the target task execution terminal;

[0028] Receive the task execution progress sent by the task manager, and feed back the task execution progress to the task issuing terminal.

[0029] Optionally, in the embodiment of the present disclosure, the method further includes:

[0030] Receive and store the task-related information sent by the task manager;

[0031] The access service of the task related information is provided to the task issuing terminal through the access interface.

[0032] According to a third aspect of an embodiment of the present disclosure, a task distribution and follow-up device is provided, which is applied to a task manager, including:

[0033] A receiving module, configured to obtain a first task request from a first message server, wherein the first task request includes a task processing rule;

[0034] A sending module, configured to parse the first task request according to the task processing rule to determine a second task request, a target task execution terminal and a second message server, and send the second task request and the target task execution terminal to the second message server;

[0035] A processing module, used for acquiring task execution information from the second message server, and summarizing the task execution information to obtain task execution progress;

[0036] The sending module is further used to send the task execution progress to the first message server.

[0037] According to a fourth aspect of an embodiment of the present disclosure, there is provided a task distribution and follow-up device, which is applied to a message server and includes:

[0038] A receiving module, used for receiving a first task request sent by a task issuing terminal;

[0039] A sending module, used for receiving a second task request and a target task execution terminal sent by the task manager, and sending the second task request to the corresponding target task execution terminal;

[0040] The sending module is further used to receive the task execution progress sent by the task manager, and feed back the task execution progress to the task issuing terminal.

[0041] According to a fifth aspect of the embodiment of the present disclosure, a task distribution and follow-up system is provided, the system comprising: a role manager, a task manager, a message server, a task storage, a task publishing terminal and a task execution terminal, wherein:

[0042] The task issuing terminal is used to send a role registration request to the role manager and / or send a first task request to the message server, and receive the task execution progress sent by the message server;

[0043] The task execution terminal is used to send a role registration request to the role manager and receive a second task request sent by the message server, and send task execution information to the message server;

[0044] The role manager is used to receive role registration requests sent by the task issuing terminal and the task executing terminal, and synchronize the registration information of the task issuing terminal and the task executing terminal that have completed registration to the task manager;

[0045] The message server is used to synchronize the first task request received from the task issuing terminal to the task manager, send the second task request received from the task manager to the task execution terminal, and send the task execution progress sent by the task manager to the task issuing terminal;

[0046] The task manager is configured to parse the first task request received from the message server to obtain the second task request, send the second task request to the message server, and summarize the task execution information obtained from the message server to obtain the task execution progress;

[0047] The task memory is used to store task summary information during the task execution process.

[0048] According to a sixth aspect of an embodiment of the present disclosure, there is provided an electronic device, including:

[0049] processor;

[0050] a memory for storing processor-executable instructions;

[0051] The processor is configured to implement the method described in the first aspect or the second aspect.

[0052] According to the seventh aspect of the embodiments of the present disclosure, a non-temporary computer-readable storage medium is provided, wherein the computer storage medium stores computer-executable instructions; after the computer-executable instructions are executed by a processor, the method described in the first aspect or the second aspect can be implemented.

[0053] The technical solution provided by the embodiments of the present disclosure may have the following beneficial effects:

[0054] The present disclosure proposes a task distribution and follow-up method, device, system and storage medium, the method comprising: obtaining a first task request from a first message server, wherein the first task request includes a task processing rule; parsing the first task request according to the task processing rule to determine a second task request, a target task execution terminal and a second message server, and sending the second task request and the target task execution terminal to the second message server; obtaining task execution information from the second message server, and summarizing the task execution information to obtain the task execution progress; sending the task execution progress to the first message server. Thus, the present disclosure establishes a task distribution and follow-up process for general task scenarios, without the need for manual processing, realizes flexible processing of task processes, improves task completion efficiency, reduces costs, and has strong versatility.

[0055] It is to be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0057] Figure 1 is a flowchart of a task distribution and follow-up method according to some embodiments of the present disclosure;

[0058] Figure 2 is a flowchart of a task distribution and follow-up method according to some embodiments of the present disclosure;

[0059] Figure 3 is a flowchart of a task distribution and follow-up method according to some embodiments of the present disclosure;

[0060] Figure 4 is an interactive flow chart of a task distribution and follow-up method according to some embodiments of the present disclosure;

[0061] Figure 5 is a structural schematic diagram of a task distribution and follow-up device according to some embodiments of the present disclosure;

[0062] Figure 6 is a structural schematic diagram of a task distribution and follow-up device according to some embodiments of the present disclosure;

[0063] Figure 7 is a structural schematic diagram of a task distribution and follow-up device according to some embodiments of the present disclosure;

[0064] Figure 8 is a structural diagram of a task distribution and follow-up system according to some embodiments of the present disclosure;

[0065] Fig. 9 It is a block diagram of an electronic device suitable for executing a task distribution and follow-up method according to some embodiments of the present disclosure. DETAILED DESCRIPTION

[0066] Some embodiments of the present disclosure will be described in detail here, and examples thereof are shown in the accompanying drawings. When the following description refers to the drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. Various changes, modifications and equivalents of the methods, systems and / or systems described herein will become apparent after understanding the present disclosure. For example, the order of operations described herein is merely an example and is not limited to those orders set forth herein, but can be changed as becomes apparent after understanding the present disclosure, except for operations that must be performed in a specific order. In addition, for clarity and brevity, descriptions of features known in the art may be omitted.

[0067] The embodiments described in some embodiments of the present disclosure below do not represent all embodiments consistent with the present disclosure. Instead, they are only examples of systems and methods consistent with some aspects of the present disclosure as detailed in the appended claims.

[0068] Figure 1 is a flowchart of a task distribution and follow-up method according to some embodiments of the present disclosure, such as Figure 1 As shown, the method is applied to a task manager and may include the following steps:

[0069] Step 101: Obtain a first task request from a first message server, wherein the first task request includes a task processing rule.

[0070] In the embodiment of the present disclosure, the first message server may be one of the multiple message servers corresponding to the task issuing terminal. For example, assuming that the task issuing terminal selects the email method to submit the first task request to s1.abc@mail.abc.com, the first task request will be stored in the email account of s1.abc in the email system mail.abc.com.

[0071] Furthermore, in the embodiment of the present disclosure, after the first task request is submitted to s1.abc@mail.abc.com, the task manager can log in to the account through the usage authority of the account to obtain the first task request.

[0072] Furthermore, in the embodiment of the present disclosure, the above-mentioned first task request may include the organization, task title, task content, task attachments, task time limit and task processing rules. Among them, the above-mentioned task title needs to contain the multiplexing code userspace, based on the uniqueness and readability of the multiplexing code, it is convenient to mark and distinguish different task publishing terminal IDs. And, the task title is formed by string concatenation of the multiplexing code and the task description. For example, the task title is defined as: userspace1 / Task1 description, where the " / " symbol is used to represent the concatenation operation of two strings. Table 1 is the first task request proposed in the embodiment of the present disclosure.

[0073] Table 1

[0074] Organization Task Title Task content Task attachments Task time limit Task processing rules Working Group 1 Task 1 Title Task 1 content Task 1 File 3 days Task 1 Rules

[0075] Further, in the embodiment of the present disclosure, the above-mentioned task processing rules may be a set of a series of operations defined by the task issuing terminal for the task processing method. Table 2 is a table of task processing rules in the embodiment of the present disclosure.

[0076] Table 2

[0077]

[0078] As shown in Table 2, the above-mentioned task processing rules may include multiple fields. Based on this, when submitting a task, the task publishing terminal may write the task processing rule fields into a separate file and submit it as an attachment. In this way, the task publishing terminal may customize the task processing rules to meet the needs of different users.

[0079] Step 102: parse the first task request according to the task processing rule to determine the second task request, the target task execution terminal and the second message server, and send the second task request and the target task execution terminal to the second message server.

[0080] In the disclosed embodiment, after the task manager obtains the first task request through the above steps, it can parse the first task request according to the task processing rules in the first task request to determine the second task request, the target task execution terminal and the second message server.

[0081] Specifically, in the embodiment of the present disclosure, the method for parsing the first task request according to the task processing rule to determine the second task request, the target task execution terminal and the second message server may include the following steps:

[0082] Step 1021: Based on the task processing rules, obtain the task execution terminal list, task reminder quantity and task statistics quantity;

[0083] Step 1022: Determine a target task execution terminal based on the task issuing terminal and the task execution terminal list corresponding to the first task request;

[0084] Step 1023: Determine a second task request based on the target task execution terminal and the first task request;

[0085] Step 1024: Determine a second message server based on the target task execution terminal, the number of task reminders, and the number of task statistics.

[0086] Among them, in the embodiment of the present disclosure, after obtaining the task execution terminal list through the task processing rules, the target task execution terminal can be determined based on the task publishing terminal and the task execution terminal list corresponding to the first task request. Specifically, in the embodiment of the present disclosure, the method for determining the target task execution terminal based on the task publishing terminal and the task execution terminal list corresponding to the first task request may include: performing a first check on the task publishing terminal corresponding to the first task request, and if the first check passes, performing a second check on the task execution terminal in the task execution terminal list, and determining the task execution terminal that passes the second check as the target task execution terminal.

[0087] Specifically, in the disclosed embodiment, the task manager can perform a first verification on the task publishing terminal corresponding to the first task request through the registration information synchronized by the role manager. If the task publishing terminal corresponding to the first task request is consistent with the registration information in the role manager, the first verification is passed; otherwise, the first verification is not passed. Among them, in the disclosed embodiment, after passing the first verification, the corresponding confirmation information of successful task submission can be generated and sent to the task publishing terminal via the first message server, wherein the confirmation information of successful task submission can include a task ID, such as SEQUENCE1. And, in the disclosed embodiment, the multiplexing code and task ID corresponding to each of the above-mentioned first task requests can effectively distinguish multiple task publishing terminals and the multiple task requests they publish.

[0088] Furthermore, in the embodiment of the present disclosure, if the first verification passes, a second verification is performed on the task execution terminal in the task execution terminal list through the registration information synchronized by the role manager, the unregistered task execution terminals in the task execution terminal list are deleted, and the task execution terminal that passes the second verification is determined as the target task execution terminal.

[0089] Furthermore, in the embodiment of the present disclosure, the information that the task execution terminal needs to know in the first task request can be determined as the second task request. Among them, the task title, task content, task attachments, and task time limit can be determined as the second task request, and the task title can include userspace and task ID information. Among them, the task processing rules in the first task request are used by the task manager to perform task message processing and are irrelevant to the specific task. Based on this, the task processing rules are not included in the second task request. For example, Table 3 is the second task request proposed in the embodiment of the present disclosure.

[0090] Table 3

[0091] Task Title Task content Task attachments Task time limit e1:Task 1 Title / SEQUENCE1 Task 1 content Task 1 File 3 days

[0092] As shown in Table 3, e1 in the task title is the userspace corresponding to the task execution terminal.

[0093] Further, in the embodiment of the present disclosure, the method for determining the second message server based on the target task execution terminal, the number of task reminders and the number of task statistics may include the following steps:

[0094] Step 1: Determine a candidate message server set based on the target task execution terminal;

[0095] Step 2: Determine the number of tasks to be sent based on the target task execution terminal, the number of task reminders, and the number of task statistics;

[0096] Step 3: Determine a second message server based on the candidate message server set and the sending quantity.

[0097] Among them, in the embodiment of the present disclosure, after the target task execution terminal is determined through the above steps, the set of all message servers corresponding to the target task execution terminal can be determined as the candidate message server set.

[0098] And, in the embodiment of the present disclosure, the method for determining the number of transmissions based on the target task execution terminal, the number of task reminders, and the number of task statistics may include: determining the number of transmissions by a calculation formula based on the target task execution terminal, the number of task reminders, and the number of task statistics, wherein the calculation formula is:

[0099] MailCount = Number of target task execution terminals × Number of task reminders × Number of task message delivery times +

[0100] Task statistics quantity.

[0101] Among them, in the embodiment of the present disclosure, after obtaining the sending number MailCount and the candidate message server set through the above steps, the second message server can be determined based on the candidate message server set and the sending number. Specifically, in the embodiment of the present disclosure, the method for determining the second message server based on the candidate message server set and the sending number may include: adding the sending number MailCount to the total number of sending times of each message server in the candidate message server set, and comparing the total number of sending times of each message server with the maximum number of sending times limit, and determining the message server that does not exceed the maximum number of sending times limit of the message server as the second message server. Among them, if the target task execution terminal corresponds to multiple second message servers, one is randomly selected from the multiple second message servers for sending. And, if the maximum number of sending times limit of all available message servers in the candidate message server set cannot meet the requirements of this task, a task rejection message is returned to the task issuing terminal; otherwise, the task is sent on each second message server respectively, and the total number of sending times on each second message server is updated to count the sending quantity requirements for the next task.

[0102] It should be noted that, in the embodiment of the present disclosure, the first message server and the second message server may be the same or different.

[0103] Step 103: Obtain task execution information from the second message server, and summarize the task execution information to obtain task execution progress.

[0104] In an embodiment of the present disclosure, the task manager may obtain task execution information from the second message server, and summarize the task execution information to obtain the task execution progress. Specifically, in an embodiment of the present disclosure, the method of obtaining task execution information from the second message server, and summarizing the task execution information to obtain the task execution progress may include: obtaining the task execution information from the second message server according to the multiplexing code and the task flag, and summarizing the task execution information to obtain the task execution progress.

[0105] Specifically, in the embodiment of the present disclosure, the task manager can collect and summarize the task related information on the second message server according to the multiplexing code and the task flag to obtain a task completion status statistics table and task execution progress, and perform corresponding actions according to the task completion status statistics table. For example, Table 4 is a task completion status statistics table provided in the embodiment of the present disclosure.

[0106] Table 4

[0107]

[0108] As shown in Table 4, the task manager sends reminder information to e2 and e3 according to the task processing rules and based on the registration information (email or SMS information) of the task execution terminals e2 and e3 in the role manager. For example, Table 5 is a reminder information table provided in an embodiment of the present disclosure.

[0109] Table 5

[0110]

[0111] Further, in the disclosed embodiment, the task manager summarizes the task execution information to obtain the task execution progress, wherein the task execution progress may include the task completion rate and the timeliness rate. The task completion rate may be obtained by dividing the number of task execution terminals that complete the task within the task time limit by the total number of task execution terminals; the task timeliness rate may be obtained by dividing the number of task execution terminals that complete the task within the task time limit by the total number of task execution terminals. And, in the disclosed embodiment, the task manager may periodically collect statistics on the long-term completion status of the task execution terminals.

[0112] Step 104: Send the task execution progress to the first message server.

[0113] In the disclosed embodiment, after obtaining the task execution progress through the above steps, the obtained task execution progress can be sent to the first message server and then sent to the task publishing terminal via the first message server, so that the task publishing terminal can follow up the task execution status in time.

[0114] Furthermore, in the embodiment of the present disclosure, if the task execution result in the task processing rule is "merged and sent to the task publishing terminal", the task manager can also send a task completion status statistics table to the task publishing terminal via the first message server, so that the task publishing terminal can process the task information on its own device.

[0115] Furthermore, in the embodiment of the present disclosure, if the task execution result in the task processing rule is "retained in the message server", the task manager can also send task-related information (such as a task completion status statistics table) to the first message server, so that the first message server can provide task-related information access services to the task publishing terminal through the access interface.

[0116] Further, in the embodiment of the present disclosure, if the task execution result in the task processing rule is "transferred to the task memory after merging", the task manager can send task related information (such as a task completion status statistics table) to the task memory through the first message server to save the task related information in the task memory. Among them, in the embodiment of the present disclosure, the task related information can be transmitted to the task memory using an SMTP or FTP or HTTP application data transmission interface. And, in the embodiment of the present disclosure, after the task manager sends the task related information to the task memory through the first message server, the task publishing terminal can process the task information on the task memory.

[0117] The present disclosure proposes a task distribution and follow-up method, which includes: obtaining a first task request from a first message server, wherein the first task request includes a task processing rule; parsing the first task request according to the task processing rule to determine a second task request, a target task execution terminal, and a second message server, and sending the second task request and the target task execution terminal to the second message server; obtaining task execution information from the second message server, and summarizing the task execution information to obtain the task execution progress; and sending the task execution progress to the first message server. Thus, the present disclosure establishes a task distribution and follow-up process for a general task scenario, without manual processing, realizing flexible processing of the task process, improving task completion efficiency, reducing costs, and having strong versatility.

[0118] Figure 2 is a flowchart of a task distribution and follow-up method according to some embodiments of the present disclosure, such as Figure 2 As shown, the method is applied to a message manager and may include the following steps:

[0119] Step 201: Receive a first task request sent by a task issuing terminal.

[0120] Step 202: Receive a second task request and a target task execution terminal sent by the task manager, and send the second task request to the corresponding target task execution terminal.

[0121] Step 203: Receive task execution information sent by the target task execution terminal.

[0122] Step 204: Receive the task execution progress sent by the task manager, and feed back the task execution progress to the task issuing terminal.

[0123] Among them, in the embodiments of the present disclosure, the relevant introduction of the above steps can refer to the detailed introduction in the above embodiments, and will not be repeated in the embodiments of the present disclosure.

[0124] Furthermore, in the disclosed embodiment, the above method may also receive and store the task-related information sent by the task manager, and provide the task-issuing terminal with access services for the task-related information through an access interface.

[0125] Furthermore, in the disclosed embodiment, each message server is configured with multiple usage and access accounts for each task manager, wherein the account can be reused by the task manager to serve multiple task publishing terminals and task executor terminals to ensure universality. In addition, the task publishing terminal can publish tasks through multiple accounts in the message server set, thereby improving the reliability and flexibility of message delivery, and can achieve load sharing of task files on multiple message servers.

[0126] The present disclosure proposes a task distribution and follow-up method, which includes: obtaining a first task request from a first message server, wherein the first task request includes a task processing rule; parsing the first task request according to the task processing rule to determine a second task request, a target task execution terminal, and a second message server, and sending the second task request and the target task execution terminal to the second message server; obtaining task execution information from the second message server, and summarizing the task execution information to obtain the task execution progress; and sending the task execution progress to the first message server. Thus, the present disclosure establishes a task distribution and follow-up process for a general task scenario, without manual processing, realizing flexible processing of the task process, improving task completion efficiency, reducing costs, and having strong versatility.

[0127] Figure 3 is a flowchart of a task distribution and follow-up method according to some embodiments of the present disclosure, such as Figure 3 As shown, the method is applied to the role manager and may include the following steps:

[0128] Step 301: Receive a first registration request from a task issuing terminal.

[0129] Step 302: Complete the registration of the task issuing terminal based on the first registration request, and send the first message server, the account corresponding to the first message server, and the reuse number of the corresponding account to the task issuing terminal.

[0130] In the embodiment of the present disclosure, the first registration request includes the task issuing terminal ID, the organization, the number in the organization, the email account and the SMS number. For example, Table 6 is a task issuing terminal role registration table proposed in the embodiment of the present disclosure.

[0131] Table 6

[0132]

[0133] And, in the embodiment of the present disclosure, the role manager can allocate to the task issuing terminal the first message server to which the task issuing terminal can submit tasks and the corresponding account in the first message server (such as email or SMS or MMS or FTP or HTTP), and the role manager can also provide the task issuing terminal with the reuse number of the corresponding account, that is, for different task issuing terminals, tasks can be submitted to the same first message server account, and when submitting tasks, the reuse number userspace needs to be carried to achieve isolation between each task issuing terminal. For example, Table 7 is a table of message servers and accounts allocated by the role manager to the task publisher terminal proposed in the embodiment of the present disclosure.

[0134] Table 7

[0135]

[0136] In the embodiment of the present disclosure, userspace can be generated by the md5 function value of the task publishing terminal ID and the random string. i =md5(p i + random string), where userspace i The reuse number of the task publishing terminal ID i, p i Also, in the embodiment of the present disclosure, a character string generation method that can ensure that each task issuing terminal is distinguishable from each other can be used to generate a reused number.

[0137] Furthermore, in the embodiment of the present disclosure, the above method may further include: receiving a second registration request of the task execution terminal, and completing the registration of the task execution terminal based on the second registration request.

[0138] In the embodiment of the present disclosure, the second registration request may include the task execution terminal ID, the organization, the number within the organization, the email account, the SMS number / telephone number, the group and the responsibilities.

[0139] Further, in the embodiment of the present disclosure, after completing the registration of the task issuing terminal and the task executing terminal, the role manager may synchronize the registration information of the task issuing terminal and the task executing terminal to the task manager.

[0140] The present disclosure proposes a task distribution and follow-up method, which includes: obtaining a first task request from a first message server, wherein the first task request includes a task processing rule; parsing the first task request according to the task processing rule to determine a second task request, a target task execution terminal, and a second message server, and sending the second task request and the target task execution terminal to the second message server; obtaining task execution information from the second message server, and summarizing the task execution information to obtain the task execution progress; and sending the task execution progress to the first message server. Thus, the present disclosure establishes a task distribution and follow-up process for a general task scenario, without manual processing, realizing flexible processing of the task process, improving task completion efficiency, reducing costs, and having strong versatility.

[0141] Figure 4 is an interactive flow chart of a task distribution and follow-up method according to some embodiments of the present disclosure, such as Figure 4 As shown, the interaction process may include the following steps:

[0142] Step 401: The task issuing terminal sends a first registration request to the role manager;

[0143] Step 402: The role manager sends the message server, the account corresponding to the message server, and the reuse number of the corresponding account to the task publishing terminal;

[0144] Step 403: The task execution terminal sends a second registration request to the role manager;

[0145] Step 404: The role manager synchronizes the registration information to the task manager;

[0146] Step 405: The task issuing terminal sends a first task request to the message server;

[0147] Step 406: The task manager obtains the first task request from the message server and parses the first task request;

[0148] Step 407: The task manager sends a second task request and a task execution terminal to the message server;

[0149] Step 408: The message server sends a second task request to the task execution terminal;

[0150] Step 409: The task execution terminal sends task execution information to the message server;

[0151] Step 410: The task manager obtains task execution information from the message server, summarizes the task execution information to obtain the task execution progress, and sends the task execution progress to the message server;

[0152] Step 411: The message server sends the task execution progress to the task issuing terminal;

[0153] Step 412: The task manager sends task related information to the message server; the message server, the account corresponding to the message server, and the reuse number of the corresponding account.

[0154] Step 413: The message server sends task related information to the task issuing terminal;

[0155] Step 414: The task manager sends the summarized task-related information to the message server;

[0156] Step 415: The message server sends the summarized task-related information to the task storage.

[0157] Figure 5 A task distribution and follow-up device is shown according to some embodiments of the present disclosure, and is applied to a task manager, such as Figure 5 As shown, the device may include:

[0158] The receiving module 501 is used to obtain a first task request from a first message server, wherein the first task request includes a task processing rule;

[0159] A sending module 502 is used to parse the first task request according to the task processing rule to determine the second task request, the target task execution terminal and the second message server, and send the second task request and the target task execution terminal to the second message server;

[0160] The processing module 503 is used to obtain the task execution information from the second message server and summarize the task execution information to obtain the task execution progress;

[0161] The sending module 502 is further used to send the task execution progress to the first message server.

[0162] In the embodiment of the present disclosure, the sending module 502 is specifically used for:

[0163] Based on the task processing rules, obtain the task execution terminal list, task reminder quantity and task statistics quantity;

[0164] Determine a target task execution terminal based on a list of task issuing terminals and task execution terminals corresponding to the first task request;

[0165] Determining a second task request based on the target task execution terminal and the first task request;

[0166] A second message server is determined based on the target task execution terminal, the number of task reminders, and the number of task statistics.

[0167] Optionally, in the embodiment of the present disclosure, the sending module 502 is further configured to:

[0168] Performing a first verification on the task issuing terminal corresponding to the first task request;

[0169] If the first verification passes, a second verification is performed on the task execution terminal in the task execution terminal list, and the task execution terminal that passes the second verification is determined as the target task execution terminal.

[0170] Optionally, in the embodiment of the present disclosure, the sending module 502 is further configured to:

[0171] Determining a candidate message server set based on the target task execution terminal;

[0172] Determine the number of tasks to be sent based on the target task execution terminal, the number of task reminders and the number of task statistics;

[0173] A second message server is determined based on the candidate message server set and the sending quantity.

[0174] Optionally, in the embodiment of the present disclosure, the processing module 503 is specifically used to:

[0175] The task execution information is obtained from the second message server according to the multiplexing code and the task flag, and the task execution information is summarized to obtain the task execution progress.

[0176] The present disclosure proposes a task distribution and follow-up device, which includes: a receiving module, which is used to obtain a first task request from a first message server, wherein the first task request includes a task processing rule; a sending module, which is used to parse the first task request according to the task processing rule to determine a second task request, a target task execution terminal and a second message server, and send the second task request and the target task execution terminal to the second message server; a processing module, which is used to obtain task execution information from the second message server, and summarize the task execution information to obtain the task execution progress; the sending module is also used to send the task execution progress to the first message server. As a result, the present disclosure establishes a task distribution and follow-up process for general task scenarios, without the need for manual processing, realizes flexible processing of task processes, improves task completion efficiency, reduces costs, and has strong versatility.

[0177] Figure 6 A task distribution and follow-up device is shown according to some embodiments of the present disclosure, and is applied to a message server, such as Figure 6 As shown, the device may include:

[0178] Receiving module 601, used for receiving a first task request sent by a task issuing terminal;

[0179] The sending module 602 is used to receive the second task request and the target task execution terminal sent by the task manager, and send the second task request to the corresponding target task execution terminal;

[0180] Receiving module 601, used to receive task execution information sent by the target task execution terminal;

[0181] The sending module 602 is further used to receive the task execution progress sent by the task manager, and feed back the task execution progress to the task issuing terminal.

[0182] In the embodiment of the present disclosure, the above device is also used for:

[0183] Receive and store task-related information sent by the task manager;

[0184] Through the access interface, access services for task-related information are provided to the task publishing terminal.

[0185] The present disclosure proposes a task distribution and follow-up device, which includes: a receiving module, which is used to obtain a first task request from a first message server, wherein the first task request includes a task processing rule; a sending module, which is used to parse the first task request according to the task processing rule to determine a second task request, a target task execution terminal and a second message server, and send the second task request and the target task execution terminal to the second message server; a processing module, which is used to obtain task execution information from the second message server, and summarize the task execution information to obtain the task execution progress; the sending module is also used to send the task execution progress to the first message server. As a result, the present disclosure establishes a task distribution and follow-up process for general task scenarios, without the need for manual processing, realizes flexible processing of task processes, improves task completion efficiency, reduces costs, and has strong versatility.

[0186] Figure 7 A task distribution and follow-up device is shown according to some embodiments of the present disclosure, and is applied to a role manager, such as Figure 7 As shown, the device may include:

[0187] The receiving module 701 is used to receive a first registration request from a task issuing terminal.

[0188] The sending module 702 is used to complete the registration of the task issuing terminal based on the first registration request, and send the first message server, the account corresponding to the first message server and the reuse number of the corresponding account to the task issuing terminal.

[0189] In the embodiment of the present disclosure, the above device is also used for:

[0190] A second registration request of the task execution terminal is received, and registration of the task execution terminal is completed based on the second registration request.

[0191] The present disclosure proposes a task distribution and follow-up device, which includes: a receiving module, which is used to obtain a first task request from a first message server, wherein the first task request includes a task processing rule; a sending module, which is used to parse the first task request according to the task processing rule to determine a second task request, a target task execution terminal and a second message server, and send the second task request and the target task execution terminal to the second message server; a processing module, which is used to obtain task execution information from the second message server, and summarize the task execution information to obtain the task execution progress; the sending module is also used to send the task execution progress to the first message server. As a result, the present disclosure establishes a task distribution and follow-up process for general task scenarios, without the need for manual processing, realizes flexible processing of task processes, improves task completion efficiency, reduces costs, and has strong versatility.

[0192] Figure 8 A task distribution and follow-up system is shown according to some embodiments of the present disclosure, the system includes: a role manager 801, a task manager 802, a message server 803, a task storage 804, a task publishing terminal 805 and a task execution terminal 806, wherein:

[0193] The task issuing terminal 805 is used to send a role registration request to the role manager and / or send a first task request to the message server, and receive the task execution progress sent by the message server;

[0194] The task execution terminal 806 is used to send a role registration request to the role manager and receive a second task request from the message server, and send task execution information to the message server;

[0195] The role manager 801 is used to receive role registration requests sent by the task issuing terminal and the task executing terminal, and synchronize the registration information of the task issuing terminal and the task executing terminal that have completed the registration to the task manager;

[0196] The message server 803 is used to synchronize the first task request sent by the task issuing terminal to the task manager, send the second task request sent by the task manager to the task execution terminal, and send the task execution progress sent by the task manager to the task issuing terminal;

[0197] The task manager 802 is used to parse the first task request sent by the message server to obtain a second task request, send the second task request to the message server, and summarize the task execution information obtained from the message server to obtain the task execution progress;

[0198] The task memory 804 is used to store task related information during the task execution process.

[0199] like Fig. 9 As shown, the electronic device 900 includes a computing unit 901, which can perform various appropriate actions and processes according to a computer program stored in a read-only memory (ROM) 902 or a computer program loaded from a storage unit 908 into a random access memory (RAM) 909. In the RAM 903, various programs and data required for the operation of the electronic device 900 can also be stored. The computing unit 901, the ROM 902, and the RAM 903 are connected to each other via a bus 904. An input / output (I / O) interface 905 is also connected to the bus 904.

[0200] A number of components in the electronic device 900 are connected to the I / O interface 905, including: an input unit 908, such as a keyboard, a mouse, etc.; an output unit 907, such as various types of displays, speakers, etc.; a storage unit 908, such as a disk, an optical disk, etc.; and a communication unit 909, such as a network card, a modem, a wireless communication transceiver, etc. The communication unit 909 allows the electronic device 900 to exchange information / data with other electronic devices through a computer network such as the Internet and / or various telecommunication networks.

[0201] The computing unit 901 may be a variety of general and / or special processing components with processing and computing capabilities. Some examples of the computing unit 901 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various dedicated artificial intelligence (AI) computing chips, various computing units running machine learning model algorithms, digital signal processors (DSPs), and any appropriate processors, controllers, microcontrollers, etc. The computing unit 901 performs the various methods and processes described above, such as task distribution and follow-up methods. For example, in some embodiments, the task distribution and follow-up methods may be implemented as a computer software program, which is tangibly contained in a machine-readable medium, such as a storage unit 908. In some embodiments, part or all of the computer program may be loaded and / or installed on the electronic device 900 via the ROM 902 and / or the communication unit 909. When the computer program is loaded into the RAM 903 and executed by the computing unit 901, one or more steps of the task distribution and follow-up methods described above may be performed. Alternatively, in other embodiments, the computing unit 901 may be configured to perform the task distribution and follow-up methods in any other appropriate manner (e.g., by means of firmware).

[0202] Various implementations of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), systems on chips (SOCs), load programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various implementations may include: being implemented in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which can be a special purpose or general purpose programmable processor that can receive data and instructions from a storage system, at least one input system, and at least one output system, and transmit data and instructions to the storage system, the at least one input system, and the at least one output system.

[0203] The program code for implementing the method of the present disclosure may be written in any combination of one or more programming languages. These program codes may be provided to a processor or controller of a general-purpose computer, a special-purpose computer, or other programmable data processing system, so that the program code, when executed by the processor or controller, enables the functions / operations specified in the flow chart and / or block diagram to be implemented. The program code may be executed entirely on the machine, partially on the machine, partially on the machine as a stand-alone software package and partially on a remote machine, or entirely on a remote machine or server.

[0204] In the context of the present disclosure, a machine-readable medium may be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, system, or electronic device. A machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, system, or electronic device, or any suitable combination of the foregoing. A more specific example of a machine-readable storage medium may include an electrical connection based on one or more lines, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage electronic device, a magnetic storage electronic device, or any suitable combination of the foregoing.

[0205] To provide interaction with a user, the systems and techniques described herein can be implemented on a computer having: a display system (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user; and a keyboard and pointing system (e.g., a mouse or trackball) through which the user can provide input to the computer. Other types of systems can also be used to provide interaction with a user; for example, the feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including acoustic input, voice input, or tactile input).

[0206] The systems and techniques described herein can be implemented in a computing system that includes backend components (e.g., as a data server), or a computing system that includes middleware components (e.g., an application server), or a computing system that includes frontend components (e.g., a user computer with a graphical user interface or a web browser through which a user can interact with implementations of the systems and techniques described herein), or a computing system that includes any combination of such backend components, middleware components, or frontend components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: a local area network (LAN), a wide area network (WAN), the Internet, and a blockchain network.

[0207] A computer system may include a client and a server. The client and the server are generally remote from each other and usually interact through a communication network. The relationship between the client and the server is generated by computer programs running on the corresponding computers and having a client-server relationship with each other. The server may be a cloud server, also known as a cloud computing server or cloud host, which is a host product in the cloud computing service system to solve the defects of difficult management and weak business scalability in traditional physical hosts and VPS services ("Virtual Private Server", or "VPS" for short). The server may also be a server of a distributed system, or a server combined with a blockchain.

[0208] It should be understood that the various forms of processes shown above can be used to reorder, add or delete steps. For example, the steps recorded in this disclosure can be executed in parallel, sequentially or in different orders, as long as the desired results of the technical solutions disclosed in this disclosure can be achieved, and this document does not limit this.

[0209] The above specific implementations do not constitute a limitation on the protection scope of the present disclosure. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions can be made according to design requirements and other factors. Any modification, equivalent substitution and improvement made within the spirit and principle of the present disclosure shall be included in the protection scope of the present disclosure.

Claims

1. A task distribution and follow-up method, characterized in that: Applies to Task Manager, including: Acquire a first task request from a first message server, wherein the first task request includes a task processing rule; Parsing the first task request according to the task processing rule to determine a second task request, a target task execution terminal, and a second message server, and sending the second task request and the target task execution terminal to the second message server; Acquire task execution information from the second message server, and summarize the task execution information to obtain task execution progress; The task execution progress is sent to the first message server.

2. The method according to claim 1, characterized in that The step of parsing the first task request according to the task processing rule to determine the second task request, the target task execution terminal and the second message server includes: Based on the task processing rules, a list of task execution terminals, the number of task reminders and the number of task statistics are obtained; Determining a target task execution terminal based on the task issuing terminal corresponding to the first task request and the task execution terminal list; Determining a second task request based on the target task execution terminal and the first task request; A second message server is determined based on the target task execution terminal, the task reminder quantity and the task statistical quantity.

3. The method according to claim 2, characterized in that The determining a target task execution terminal based on the task issuing terminal corresponding to the first task request and the task execution terminal list includes: Performing a first verification on the task issuing terminal corresponding to the first task request; If the first verification passes, a second verification is performed on the task execution terminal in the task execution terminal list, and the task execution terminal that passes the second verification is determined as the target task execution terminal.

4. The method according to claim 2, characterized in that The determining of the second message server based on the target task execution terminal, the task reminder quantity and the task statistical quantity includes: Determining a candidate message server set based on the target task execution terminal; Determine the number of tasks to be sent based on the target task execution terminal, the number of task reminders and the number of task statistics; A second message server is determined based on the candidate message server set and the sending quantity.

5. The method according to claim 1, characterized in that The step of obtaining the task execution information from the second message server and aggregating the task execution information to obtain the task execution progress includes: obtaining the task execution information from the second message server according to the multiplexing code and the task flag, and aggregating the task execution information to obtain the task execution progress.

6. A task distribution and follow-up method, characterized in that: Applicable to message servers, including: Receiving a first task request sent by a task issuing terminal; receiving a second task request and a target task execution terminal sent by the task manager, and sending the second task request to the corresponding target task execution terminal; Receiving task execution information sent by the target task execution terminal; Receive the task execution progress sent by the task manager, and feed back the task execution progress to the task issuing terminal.

7. The method according to claim 6, characterized in that The method further comprises: Receive and store the task-related information sent by the task manager; The access service of the task related information is provided to the task issuing terminal through the access interface.

8. A task distribution and follow-up device, characterized in that: Applies to Task Manager, including: A receiving module, configured to obtain a first task request from a first message server, wherein the first task request includes a task processing rule; A sending module, configured to parse the first task request according to the task processing rule to determine a second task request, a target task execution terminal and a second message server, and send the second task request and the target task execution terminal to the second message server; A processing module, used for acquiring task execution information from the second message server, and summarizing the task execution information to obtain task execution progress; The sending module is further used to send the task execution progress to the first message server.

9. A task distribution and follow-up device, characterized in that: Applicable to message servers, including: A receiving module, used for receiving a first task request sent by a task issuing terminal; A sending module, used for receiving a second task request and a target task execution terminal sent by the task manager, and sending the second task request to the corresponding target task execution terminal; The receiving module is used to receive the task execution information sent by the target task execution terminal; The sending module is further used to receive the task execution progress sent by the task manager, and feed back the task execution progress to the task issuing terminal.

10. A task distribution and follow-up system, characterized in that: The system includes: a role manager, a task manager, a message server, a task storage, a task publishing terminal and a task execution terminal, wherein: The task issuing terminal is used to send a role registration request to the role manager and / or send a first task request to the message server, and receive the task execution progress sent by the message server; The task execution terminal is used to send a role registration request to the role manager and receive a second task request sent by the message server, and send task execution information to the message server; The role manager is used to receive role registration requests sent by the task issuing terminal and the task executing terminal, and synchronize the registration information of the task issuing terminal and the task executing terminal that have completed registration to the task manager; The message server is used to synchronize the first task request received from the task issuing terminal to the task manager, send the second task request received from the task manager to the task execution terminal, and send the task execution progress sent by the task manager to the task issuing terminal; The task manager is configured to parse the first task request received from the message server to obtain the second task request, send the second task request to the message server, and summarize the task execution information obtained from the message server to obtain the task execution progress; The task memory is used to store task related information during the task execution process.

Images