CN117149390A

CN117149390A - Task scheduling method and device, electronic equipment and readable storage medium

Info

Publication number: CN117149390A
Application number: CN202311174587.3A
Authority: CN
Inventors: 黄勇波; 陈赞军; 魏星; 尹斌; 毕云胜
Original assignee: Beijing Zhongguancun Kejin Technology Co Ltd
Current assignee: Beijing Zhongguancun Kejin Technology Co Ltd
Priority date: 2023-09-12
Filing date: 2023-09-12
Publication date: 2023-12-01

Abstract

The present disclosure provides a task scheduling method, an apparatus, an electronic device, and a readable storage medium, which ensure efficient and stable operation of an automation flow by acquiring task order information and task type information of trigger tasks, performing a sequencing process on the trigger tasks, and preparing a retry strategy for the tasks that are interrupted. The method comprises the following steps: generating a plurality of trigger tasks, and acquiring task sequence information and task type information corresponding to each trigger task; determining the execution sequence of a plurality of trigger tasks according to the task sequence information, and executing each trigger task in turn; monitoring whether the trigger tasks are interrupted or not in the executing process of each trigger task; under the condition that the trigger task with the interrupt is monitored, determining an interrupt processing strategy corresponding to the trigger task with the interrupt according to the task type information of the trigger task with the interrupt; and according to the interrupt processing strategy, performing interrupt processing on the trigger task with the interrupt.

Description

Task scheduling method and device, electronic equipment and readable storage medium

Technical Field

The disclosure relates to the technical field of computers, and in particular relates to a task scheduling method, a task scheduling device, electronic equipment and a readable storage medium.

Background

Along with the continuous promotion of the policies of cost reduction and synergy, the process robot RPA becomes an important component of enterprise digital and automatic transformation. The flow robot RPA can simulate manual operation of a user through a trigger, automatically execute repetitive tasks such as data input, report generation and document processing, and reduce labor cost and time cost of enterprises.

At present, the flow robot RPA still has some problems in practical application, such as incapability of determining the execution sequence of trigger tasks, incapability of processing tasks with interruption, and the like, so that the stability and usability of the flow robot RPA are reduced.

Disclosure of Invention

The invention provides a task scheduling method, a device, electronic equipment and a readable storage medium, which are used for sequencing trigger tasks and preparing retry strategies for tasks with interruption by acquiring task sequence information and task type information of the trigger tasks, so that the usability of an RPA (remote procedure robot) is improved, and the efficient and stable operation of an automatic procedure is ensured.

In a first aspect, the present disclosure provides a task scheduling method, including the steps of:

generating a plurality of trigger tasks, and acquiring task sequence information and task type information corresponding to each trigger task;

determining the execution sequence of the plurality of trigger tasks according to the task sequence information, and executing each trigger task in turn;

monitoring whether the trigger tasks are interrupted or not in the executing process of each trigger task; under the condition that an interrupted trigger task is monitored, determining an interrupt processing strategy corresponding to the interrupted trigger task according to task type information of the interrupted trigger task;

and carrying out interrupt processing on the trigger task with the interrupt according to the interrupt processing strategy.

In a second aspect, the present disclosure provides a task scheduling device, including:

the acquisition module is suitable for generating various trigger tasks and acquiring task sequence information and task type information corresponding to each trigger task;

the execution module is suitable for determining the execution sequence of the plurality of trigger tasks according to the task sequence information and executing each trigger task in turn; and the interrupt processing strategy is suitable for carrying out interrupt processing on the trigger task with the interrupt according to the interrupt processing strategy;

The monitoring module is suitable for monitoring whether the trigger tasks are interrupted or not in the execution process of each trigger task; and under the condition that the trigger task with the interrupt is monitored, determining an interrupt processing strategy corresponding to the trigger task with the interrupt according to the task type information of the trigger task with the interrupt.

In a third aspect, the present disclosure provides an electronic device comprising:

at least one processor; and

a memory communicatively coupled to the at least one processor; wherein,

the memory stores one or more computer programs executable by the at least one processor, one or more of the computer programs being executable by the at least one processor to enable the at least one processor to perform the above-described method.

In a fourth aspect, the present disclosure provides a computer readable storage medium having stored thereon a computer program, wherein the computer program when executed by a processor implements the above method.

In the embodiment provided by the disclosure, on one hand, multiple trigger tasks are generated, task sequence information and task type information corresponding to each trigger task are obtained, then the execution sequence of the multiple trigger tasks is determined according to the task sequence information, and each trigger task is executed in sequence; on the other hand, in the process of executing each trigger task, the executing state of the trigger task is detected, if the trigger task is monitored to be interrupted, a corresponding interrupt processing strategy is determined according to the task type information of the interrupted trigger task, and interrupt processing is carried out on the interrupted trigger task according to the interrupt processing strategy. The method comprises the steps of sequencing the execution sequence of trigger tasks by means of task sequence information of the trigger tasks, and then executing the trigger tasks; if the trigger task is interrupted, determining an interrupt processing strategy of the interrupted trigger task according to the task type information of the interrupted trigger task, and carrying out interrupt processing on the task according to the interrupt processing strategy. According to the application, the task sequence information and the task type information of the trigger tasks are acquired, the trigger tasks are sequenced, and the retry strategy is prepared for the tasks with interruption, so that the usability of the flow robot RPA is improved, and the efficient and stable operation of an automatic flow is ensured.

It should be understood that the description in this section is not intended to identify key or critical features of the embodiments of the disclosure, nor is it intended to be used to limit the scope of the disclosure. Other features of the present disclosure will become apparent from the following specification.

Drawings

The accompanying drawings are included to provide a further understanding of the disclosure, and are incorporated in and constitute a part of this specification, illustrate embodiments of the disclosure and together with the description serve to explain the disclosure, without limitation to the disclosure. The above and other features and advantages will become more readily apparent to those skilled in the art by describing in detail exemplary embodiments with reference to the attached drawings, in which:

FIG. 1 is a flow chart of a task scheduling method provided by an embodiment of the present disclosure;

FIG. 2 is a flow chart illustrating one specific example of a task scheduling method of the present application;

FIG. 3 is a block diagram of a task scheduling device provided by an embodiment of the present disclosure;

fig. 4 is a block diagram of an electronic device according to an embodiment of the present disclosure.

Detailed Description

For a better understanding of the technical solutions of the present disclosure, exemplary embodiments of the present disclosure will be described below with reference to the accompanying drawings, in which various details of the embodiments of the present disclosure are included to facilitate understanding, and they should be considered as merely exemplary. Accordingly, one of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the present disclosure. Also, descriptions of well-known functions and constructions are omitted in the following description for clarity and conciseness.

Embodiments of the disclosure and features of embodiments may be combined with each other without conflict.

As used herein, the term "and/or" includes any and all combinations of one or more of the associated listed items.

The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure. As used herein, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms "comprises" and/or "comprising," when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof. The terms "connected" or "connected," and the like, are not limited to physical or mechanical connections, but may include electrical connections, whether direct or indirect.

Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art. It will be further understood that terms, such as those defined in commonly used dictionaries, should be interpreted as having a meaning that is consistent with their meaning in the context of the relevant art and the present disclosure, and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein.

The task scheduling method according to the embodiments of the present disclosure may be performed by an electronic device such as a terminal device or a server, and the terminal device may be a vehicle-mounted device, a User Equipment (UE), a mobile device, a User terminal, a cellular phone, a cordless phone, a personal digital assistant (Personal Digital Assistant, PDA), a handheld device, a computing device, a vehicle-mounted device, a wearable device, or the like; the server may be an independent physical server, a server cluster or a distributed system formed by a plurality of physical servers, or a cloud server providing cloud computing service. The method may in particular be implemented by means of a processor calling a computer program stored in a memory.

At present, the flow robot RPA still has some problems in practical application, such as incapability of determining the execution sequence of trigger tasks, incapability of processing tasks with interruption, and the like, so that the stability and usability of the flow robot RPA are reduced. In order to solve the above problems, the present disclosure provides a task scheduling method, which performs sequencing processing on trigger tasks and determines a retry strategy for tasks that are interrupted by acquiring task order information and task type information of the trigger tasks, thereby improving the usability of the process robot RPA and ensuring efficient and stable operation of an automated process.

Fig. 1 is a flowchart of a task scheduling method according to an embodiment of the present disclosure.

Referring to fig. 1, the method includes:

step S110: and generating a plurality of trigger tasks, and acquiring task sequence information and task type information corresponding to each trigger task.

In an alternative implementation, when generating multiple trigger tasks, this is achieved by:

monitoring various types of business events through a flow robot RPA; triggering a task trigger corresponding to a business event under the condition of monitoring any type of business event, and generating a trigger task corresponding to the business event; wherein the plurality of types of business events include at least one of: a timed trigger event corresponding to a time type, a key trigger event corresponding to an input type, and a mail trigger event corresponding to a text type.

The trigger task is generated after the flow robot RPA monitors various types of business events; specifically, when the process robot RPA monitors any one of the multiple types of service events, a task trigger corresponding to the service event is triggered, and a trigger task corresponding to the service event is generated. Wherein, there are multiple monitoring processes in the flow robot RPA, each monitoring process can monitor the corresponding business event continuously; when a business event occurs, the monitoring process is activated, so that the monitoring process reports corresponding business event active information to the task trigger; and after receiving the active information of the business event, the task trigger triggers and generates a trigger task corresponding to the business event. Wherein, the business events of multiple types at least comprise one or more of timing trigger events corresponding to time types, key trigger events corresponding to input types and mail trigger events corresponding to text types; specifically, the timing trigger event corresponding to the time type is executed as follows: manually setting a time point by a user, and automatically executing a preset workflow when the time point is reached; the key trigger event corresponding to the input type is performed as follows: when a user presses a designated single key or presses a plurality of keys combined according to a specific pressing sequence, a preset workflow is automatically executed; the mail triggering event corresponding to the text type is performed as follows: when a user sends or receives a mail title, a text and an attachment containing a designated keyword through a mailbox, or sends a mail to a designated recipient and receives a mail sent by a designated sender, a preset workflow is automatically executed; more, the method can also comprise various types of trigger events such as webpage content acquisition events, API trigger events, folder monitoring events and the like; when the flow robot RPA monitors the multiple service events, the flow robot RPA monitors whether the triggering condition corresponding to each service event occurs or not, for example, a user manually sets a time point, sends or receives mails, presses a key by the user, and the like; that is, when the process robot RPA monitors that the user has the triggering condition, the process robot RPA reports the service event corresponding to the triggering condition, then generates a trigger task corresponding to the service event according to the task trigger, and executes the service event through the trigger task. Preferably, after generating the trigger task corresponding to the service event, storing the trigger task in a local database; the operation can store the trigger task, and is convenient to manage.

In one specific example, the specified keyword of the mail triggering event is set as "query", and the workflow corresponding to "query" is preset as "mark the mail as important and add to the calendar"; when the user receives the mail with the title or text containing the query keyword, the task trigger corresponding to the mail triggering event is triggered and a corresponding trigger task is generated, namely, the mail is marked as important and added into a schedule, and then the trigger task is stored in a local MySQL database for archiving and backup.

In summary, the implementation is directed to monitoring a business event by the process robot RPA, triggering a task trigger corresponding to the business event when the business event is monitored, and generating a corresponding trigger task.

After the trigger task is generated, task sequence information and task type information corresponding to the trigger task are acquired. The task sequence information and the task type information are basic attribute information of the trigger task; the task sequence information comprises time stamp information of the trigger task, wherein the time stamp information is used for representing generation time information of the trigger task, waiting time information of the trigger task which is not executed and the like; the task type information comprises priority and importance information of the task, and the information is used for representing the importance degree of the trigger task; if the trigger task is interrupted, the subsequent processing can be performed through task type information.

Step S120: and determining the execution order of various trigger tasks according to the task sequence information, and executing each trigger task in turn.

In an alternative implementation, when determining the execution order of a plurality of trigger tasks according to the task sequence information, and executing each trigger task in turn, the following manner is implemented:

first, according to the task sequence information corresponding to each trigger task, the initial bit information of each trigger task in the trigger task queue is determined. The task sequence information comprises time stamp information of the trigger task, and the time stamp information is determined according to the time generated by the trigger task. Since the flow robot RPA can only execute a single task at the same time, it is necessary to sort a plurality of trigger tasks to determine the execution order of each trigger task and sequentially execute each trigger task in order. After determining the execution sequence of each trigger task, all trigger tasks need to be formed into a task queue according to the execution sequence; specifically, initial bit information of each trigger task is generated according to timestamp information contained in task sequence information of each trigger task, and then all trigger tasks are formed into a task queue according to the initial bit information. According to normal processing logic, the tasks generated first are processed first and then the generated tasks are processed later, so that the generation time of each trigger task can be determined according to the time stamp information of each trigger task, the trigger tasks are further sequenced according to the generation time of each trigger task, and then all trigger tasks are formed into a task queue according to the sequencing result; it is known that the order of the trigger tasks generated earlier is the front in the task queue, and the order of the trigger tasks generated later is the later.

Each trigger task is then stored in the trigger task queue according to the initial bit order information. Wherein the trigger task queue may be a first-in first-out queue; when storing trigger tasks, follow the logic of 'stored trigger tasks are executed first and then stored trigger tasks are executed later', and the trigger tasks are ordered according to the time sequence generated when the trigger tasks are generated, so that the trigger tasks generated first in the trigger queue are executed first and then the trigger tasks generated first are executed later.

And finally, sequentially acquiring each trigger task from the trigger task queue and executing the trigger tasks. When each trigger task is acquired in sequence and executed, the trigger tasks stored in the trigger task queue are arranged according to the sequence of task generation, so that the generation time of each executed trigger task is earlier than that of the rest non-executed trigger tasks in the trigger task queue.

In one specific example, there are five trigger tasks A, B, C, D and E; after acquiring the task sequence information of each trigger task, the timestamps of the five trigger tasks are found to be 2 seconds, 3 seconds, 6 seconds, 5 seconds and 1 second respectively, namely, A is generated at 2 th second, B is generated at 3 rd second, C is generated at 6 th second, D is generated at 5 th second and E is generated at 1 st second; then the initial bit order information for these five trigger tasks is 2, 3, 5, 4, 1; storing the five tasks in a trigger task queue K according to the initial bit information, wherein the generated trigger task queue K= [ E, A, B, D, C ]; that is, E is first executed as the first generated trigger task, followed by A, B, D, C.

In summary, the implementation is directed to acquiring initial bit information of each trigger task according to task sequence information corresponding to each trigger task, then generating a trigger task queue, and sequentially executing each trigger task. By the mode, different trigger tasks are orderly organized into the queue, so that the task execution process of the process robot RPA is facilitated, and the smoothness and stability are improved.

In an alternative implementation manner, after determining initial bit information of each trigger task in the trigger task queue according to task sequence information corresponding to each trigger task, the method further includes the following implementation manner:

first, in the case where at least two trigger tasks whose initial bit order information is the same are detected, at least two trigger tasks whose initial bit order information is the same are determined as a conflicting task group. When the initial bit information of the two trigger tasks is the same, the ranking order of the two trigger tasks in the trigger task queue is the same; however, the flow robot RPA can only perform a single task at the same time, resulting in the failure to have tasks in the same order in the trigger task queue. Therefore, the two trigger tasks are determined to be a conflict task group, and then the two trigger tasks in the conflict task group are separately ordered, so that the initial bit information of the two trigger tasks is different; alternatively, if more than two trigger tasks exist at the same time with the same initial bit information, then the trigger tasks are determined to be conflicting task groups.

Then, the type priority of each trigger task in the conflict task group is determined according to the task type information of each trigger task in the conflict task group. After the conflict task group is determined, task type information of each trigger in the conflict task group is acquired; the task type information comprises priority and importance information of the task, and the information is used for representing the importance degree of the trigger task; because each trigger task is generated by different business events, each business event has importance and needs to respond to more important business events preferentially; therefore, when the initial bit information of two trigger tasks is the same, it is necessary to compare importance between the two trigger tasks and preferentially execute the trigger tasks that are more important. Alternatively, if two trigger tasks with the same initial rank and the same importance occur, the two trigger tasks may be defined as the same trigger task; the business events corresponding to the two trigger tasks are the same, and the business events occur twice at the same time point, so that two identical trigger tasks are generated; the processing mode is as follows: any trigger task is abandoned, and only one trigger task is reserved and executed.

And finally, according to the type priority of each trigger task in the conflict task group, adjusting the initial bit information of each trigger task in the conflict task group so that the initial bit information of each trigger task after adjustment is different. The method comprises the steps of sorting task type information of each trigger task according to a plurality of trigger tasks in a conflict task group; when sorting, the trigger tasks with high importance are arranged at the front, and the trigger tasks with low importance are arranged at the rear; after the sorting is completed, according to the sorting result, the trigger tasks with the same initial bit information are adjusted, and the initial bit information of the trigger tasks with high importance is arranged in front, so that all the trigger tasks have no same initial bit information.

In one specific example, there are five trigger tasks A, B, C, D and E; after acquiring the task sequence information of each trigger task, the timestamps of the five trigger tasks are found to be 2 seconds, 3 seconds, 5 seconds and 1 second respectively, namely, A is generated at 2 nd second, B is generated at 3 rd second, C is generated at 5 th second, D is generated at 5 th second and E is generated at 1 st second; then the initial bit order information for these five trigger tasks is 2, 3, 4, 1; storing the five tasks in a trigger task queue K according to the initial bit information, wherein the generated trigger task queue K= [ E, A, B, C & D ]; it can be known that, at this time, the two trigger tasks C, D have the same initial bit information, if the trigger task queues are directly generated, the bits of C, D in the trigger task queues are the same, which causes the process robot RPA to be confused when processing the two trigger tasks C, D (because the process robot RPA can only process one trigger task at a time, but the bits of C, D are the same); next, inquiring the task type information of C, D, wherein C is a trigger task corresponding to a mail triggering event, D is a trigger task corresponding to a key triggering event, and the importance of the trigger task corresponding to the mail triggering event is higher; therefore, the initial bit information of C, D is adjusted according to the importance of the trigger task, so that the initial bit information of C is higher than that of D, and the initial bit information of the five trigger tasks of A, B, C, D, E is updated to be 2, 3, 4, 5 and 1; finally, the trigger task queue K is adjusted according to the updated initial bit information, and the generated trigger task queue K= [ E, A, B, C, D ] can be normally processed by the flow robot RPA.

In a word, the implementation mode aims at carrying out reordering processing on the trigger tasks with the same initial bit information so as to solve the problem that the process robot RPA cannot advance the task process when encountering the trigger tasks with the same arrangement order, and improve the stability of the process robot RPA when carrying out task processing.

Step S130: monitoring whether the trigger tasks are interrupted or not in the executing process of each trigger task; and under the condition that the trigger task with the interrupt is monitored, determining an interrupt processing strategy corresponding to the trigger task with the interrupt according to the task type information of the trigger task with the interrupt.

After each trigger task is stored into a trigger task queue according to initial bit information, the flow robot RPA sequentially acquires and executes each trigger task according to the sequence of the trigger tasks stored in the trigger task queue; and, the flow robot RPA only acquires one trigger task at a time, and acquires the next trigger task after completing the trigger task. When executing each trigger task, the flow robot RPA monitors the real-time execution state of the trigger task; when the trigger task is interrupted, the flow robot RPA determines a corresponding processing strategy according to the task type information of the trigger task. Wherein, the occurrence of interrupt of the trigger task refers to the phenomenon that the trigger task fails to execute and terminates due to abnormal execution in the process of executing; for example, a certain trigger task is generated by a mail triggering event corresponding to a text type, that is, a user creates a corresponding trigger task after receiving a mail whose title or text contains a "query" keyword, and when executing the trigger task, the process robot RPA needs to perform an operation of "marking the mail as important and adding to a calendar"; at this time, if the mail is deleted or damaged, the marking cannot be performed, the calendar is full, a new mail calendar cannot be added, and the like, the trigger task cannot be executed, namely, interruption occurs; after the interrupt occurs, the flow robot RPA acquires task type information of the trigger task, and determines a corresponding processing strategy according to the task type information.

In an alternative implementation, when determining an interrupt processing policy corresponding to an interrupt-occurring trigger task according to task type information of the interrupt-occurring trigger task, the following is implemented:

determining an interrupt processing strategy corresponding to a trigger task with interrupt occurrence under the condition that the task type information is first type information, and retrying to execute the class strategy;

in the case that the task type information is the second type information, it is determined that the interrupt processing policy corresponding to the trigger task where the interrupt occurred is the abort execution class policy.

The task type information of the trigger task comprises first type information and second type information; the first type of information represents that the trigger task can be retried and the second type of information represents that the task cannot be retried; that is, if the task type information of the trigger task in which the interrupt occurs is the first type information, it is indicated that the trigger task can be retried; if the task type information of the trigger task in which the interrupt occurs is the second type information, it indicates that the trigger task cannot be retried. Preferably, if the trigger task with higher importance is interrupted, the task can be set to retry after the interruption occurs, so as to ensure the stability of the whole task flow; if the trigger task with lower importance is interrupted, the execution is directly stopped after the interruption is caused because the trigger task is not an important task, and retry is not needed, so that task resources are saved and the processing efficiency of a system is improved; therefore, task type information of a trigger task having a higher importance is set as an important task (first type information), and task type information of a trigger task having a lower importance is set as an unimportant task (second type information).

In one specific example, there is a trigger task A, B, and the task type information of the trigger task a is "important task", the task type information of the trigger task B is "unimportant task"; then, if an interrupt occurs when the flow robot RPA processes the trigger task a, a retry strategy may be executed on the trigger task a according to the task type information "important task" of the trigger task a; if an interrupt occurs while the flow robot RPA processes the trigger task B, the suspension policy may be executed on the trigger task B according to the task type information "unimportant task" of the trigger task B.

In summary, the implementation is to determine an execution policy of a trigger task after an interrupt occurs through task type information of the trigger task, and process the trigger task after the interrupt occurs according to the execution policy.

Step S140: and according to the interrupt processing strategy, performing interrupt processing on the trigger task with the interrupt.

In an alternative implementation manner, when the interrupt processing policy corresponding to the trigger task with the interrupt is a retry execution class policy, according to the interrupt processing policy, the interrupt processing is performed on the trigger task with the interrupt, which is implemented by the following manner:

Firstly, determining retry bit information of the interrupted trigger task in a trigger task queue according to task type information of the interrupted trigger task;

and then reinserting the interrupted trigger task into a trigger task queue according to the retry bit information so as to enable the interrupted trigger task to execute retry operation.

When determining that the trigger task can execute a retry strategy according to task type information of the trigger task with the interrupt, reinserting the trigger task with the interrupt into a trigger task queue, and waiting for the flow robot RPA to execute the task again; when the trigger task with the interrupt is reinserted into the trigger task queue, retry bit information of the trigger task with the interrupt needs to be determined according to importance in the task type information: when the order of the trigger task queue is determined, the order of the trigger tasks generated earlier in the trigger task queue is more forward according to the task sequence information corresponding to each trigger task (namely the generation time of the trigger tasks); since the generation time of the trigger task with the interrupt is definitely smaller than that of all the rest non-executed trigger tasks in the trigger task queue, when the retry bit information of the trigger task with the interrupt in the trigger task queue is determined, the determination is required according to the importance of the task (otherwise, the task is always arranged in front of all the rest non-executed trigger tasks); if the task is very important, then the task is inserted in a trigger task queue earlier; if the task is generally important, the task is inserted in a later position in the trigger task queue although retrying is performed on the trigger task, so as to ensure that the normal execution of the rest of the tasks in the trigger task queue is aged.

In one specific example, there are six trigger tasks A, B, C, D, E and F; storing the six tasks in a trigger task queue K according to the initial bit information, generating a trigger task queue K= [ E, A, F, D, B and C ], then sequentially executing the tasks in the trigger task queue, generating an interrupt when executing the trigger task A, and judging that the trigger task A can execute retry operation according to the task type information of the trigger task A; then, the remaining trigger task queues k= [ F, D, B, C ] at this time, and then the insertion bit times of the trigger task a in [ F, D, B, C ] are judged and generated according to the task type information of the trigger task a; after the judgment is carried out, the trigger task A is obtained as a task which is generally important, so that the trigger task A does not need to be retried immediately, namely the trigger task A does not need to be inserted into a very front position; at this time, the trigger task a is inserted into [ F, D, B, C ] according to the generated insertion order, the trigger task queue k= [ F, D, B, a, C ] is generated, and when the flow robot RPA executes the trigger task a again, the retry operation is executed for the trigger task a having the interrupt.

In summary, the implementation is aimed at inserting the interrupted trigger task into a reasonable position in the trigger queue through the task type information of the interrupted trigger task, so that the timeliness of executing the rest tasks in the trigger queue is ensured while the insertion according to the importance of the task is ensured.

In an alternative implementation, after reinserting the interrupted trigger task into the trigger task queue according to the retry bit information, the method further includes:

if the interrupted trigger task is interrupted again in the process of executing the retry operation, determining the current retry times of the interrupted trigger task;

repeatedly executing the step of determining retry bit information of the interrupted trigger task in the trigger task queue according to the task type information of the interrupted trigger task under the condition that the current retry frequency is smaller than a preset frequency threshold value, and reinserting the interrupted trigger task in the trigger task queue according to the retry bit information;

the preset times threshold is determined according to task type information of the trigger task with the interrupt.

If the interrupted trigger task is interrupted again when the retry operation is executed, the current retry number of the trigger task needs to be determined first to determine whether to allow the trigger task to execute the retry again. At this time, determining a preset time threshold of the trigger task according to the task type information of the trigger task; the preset times threshold is used for representing the times that the trigger task can execute retry; preferably, the preset number of times threshold of the important trigger task is set to be higher, and the preset number of times threshold of the general important trigger task is set to be lower; therefore, the important trigger task still has the retry times after a plurality of interrupts, and the probability of successful execution of the trigger task can be improved. If the retry number of the trigger task does not reach the preset number threshold, the trigger task can still continue to execute the retry; then the retry bit information for the trigger task is determined and then the task is reinserted into the trigger task queue (the specific steps of the insertion have been described in detail in the previous implementation and are not repeated here).

In summary, the implementation manner aims at explaining a processing manner that when an interrupted trigger task is subjected to retry, whether the trigger task can execute retry again is determined by a preset number of times threshold; the importance degree of the task can be determined according to the task type information of the trigger task, and a higher preset frequency threshold value is set for the important task, so that the probability of successful execution of the trigger task can be improved.

For easy understanding, fig. 2 shows a schematic flow chart of a specific example, and taking this example as an example, details of a specific implementation of the task scheduling method in the present application will be described in detail:

as shown in fig. 2, the task scheduling method of the present application is supported and operated by a trigger process manager 21, a trigger process task memory 22, and a business process processor 23. The trigger process manager 21 further includes a plurality of task triggers (only five task triggers are listed in the figure) corresponding to different service events, namely a timing trigger 211, a folder trigger 212, an API trigger 213, a mail trigger 214 and a hotkey trigger 215; wherein the timing trigger 211 is used for monitoring and generating service events related to timing class tasks, the folder trigger 212 is used for monitoring and generating service events related to folder opening, closing and storing and taking out class tasks, the API trigger 213 is used for monitoring and generating service events related to interface calling class tasks, the mail trigger 214 is used for monitoring and generating service events related to appointed mail types, and the hot key trigger 215 is used for monitoring and generating service events related to actions of pressing appointed single keys and combining key classes. The trigger process task memory 22 further includes a storage module 221, a push module 222, and an interrupt processing module 223; the storage module 221 stores the trigger tasks in a queue manner, detects conflict states of the trigger tasks, and processes the conflict trigger tasks; the pushing module 222 is configured to push the trigger tasks in the queue to the business process processor 23 according to a first-in first-out rule; the interrupt processing module 223 is configured to process the task with the interrupt, and when it is determined that the retry operation can be performed, transmit the task with the interrupt to the pushing module 222, so that the pushing module 222 pushes the task with the interrupt to the business process processor 23 again for processing. The business process processor 23 performs task processing on the trigger task pushed by the pushing module 222, and returns the task with the interrupt to the interrupt processing module 223 when the interrupt occurs.

The collaborative workflow between the trigger process manager 21, the trigger process task memory 22 and the business process processor 23 is described in detail below:

firstly, a trigger process manager creates trigger processes (embedded in a process robot RPA) corresponding to a timing trigger, a folder trigger, an API trigger, a mail trigger and a hot key trigger, and monitors corresponding business events according to the trigger processes; when an event related to a corresponding service is monitored, triggering a task trigger corresponding to the service event and generating a corresponding trigger task, and simultaneously storing the trigger task in a local database; in addition, to ensure reliability and stability of the system, the trigger process may record the status of each trigger task, such as running status, completion status, failure status, etc., in order to detect and repair problems in time.

Then, the storage module in the trigger process task memory stores all trigger tasks generated by the trigger process manager: acquiring task sequence information of each trigger task, determining initial bit information of each trigger task in a trigger task queue according to the task sequence information, and forming all trigger tasks into a queue according to the initial bit information; meanwhile, conflict detection is carried out on all trigger tasks, when two or more trigger tasks exist and initial bit information is the same, the positions of the trigger tasks with the same initial bit information in a trigger task queue are adjusted through the initial bit information of each trigger task, so that all trigger tasks are serialized; and finally, storing the trigger tasks into a queue data structure, and storing according to time sequence to wait for the call of the pushing module.

And then, a pushing module in the trigger process task memory sequentially reads each task in the trigger task queue and pushes the trigger tasks to the business process processor according to the sequence of the tasks.

Next, the business process processor queries each trigger task in the trigger task queue, and executes various automation tasks according to the sequence of the tasks: the business process processor automatically retrieves the earliest generated trigger task so as to execute the tasks in the trigger task queue according to time sequence; then, according to the time sequence, the corresponding business process is called to process the trigger task and the processing result is fed back; after one trigger task is completed, the next task is performed; and after each task in the trigger task queue is processed, the executing state and executing result of the task need to be returned in time so as to further detect and record the processing state and data at any time.

When the trigger task is interrupted, the business process processor returns the task to an interrupt processing module in a trigger process task memory; the interrupt processing module judges whether the task can be retried according to the task type information of the trigger task; when the task can be retried, transmitting the task to a pushing module, so that the pushing module pushes the task to a business process processor again for retrying; in addition, if the interrupt processing module receives a trigger task which is interrupted again in the retry process, a preset time threshold value is obtained according to task type information of the task, and under the condition that the retry time of the task is smaller than the preset threshold value, the task is transmitted to the pushing module again, so that the pushing module pushes the task to the business process processor again for retry processing. After receiving the retried interrupt task transmitted by the interrupt processing module, the pushing module generates the position of the task in the trigger task queue according to the task type information of the task, and pushes the task to the business process processor according to the position sequence.

The following describes in detail, again by way of a specific example, a specific flow of the task scheduling method of the present application:

this task can be accomplished automatically using the flow robot RPA when monitoring and querying the customer's account balance and sending an email to the relevant account balance in time. The financial scene based on the process robot RPA automatic execution process can greatly improve the reconciliation efficiency and reduce the manual error, and can more quickly and efficiently inquire the balance of the customer and send the E-mail, thereby further improving the service quality and the customer satisfaction.

The specific implementation mode is as follows:

firstly, setting a folder for storing a client bill, and setting a folder trigger for the folder; when the folder trigger detects that a new file is placed in the folder, a trigger task for inquiring account information of a client is triggered. After triggering the trigger task of balance inquiry, the RPA robot can acquire the account information of the client and inquire the account balance. Specifically, account information is extracted from a file based on the accounting document mode, and then the balance of a bank account is queried according to the account information, and the specific operation mode is as follows: first, customer account information including account name, account type, account number, balance, etc. is extracted from customer account documents (e.g., bills, emails); then, inquiring account balance from the bank API interface; finally, the query result is exported as a report, and the data file is saved at the designated location.

And then, exporting and storing a query result generated by a trigger task of the balance query into a data file so as to prepare for and process later, wherein the specific operation mode is as follows: firstly, converting the query result into a data file in a table format, such as a CSV or Excel format; then automatically generating an email according to the data file format, the user account and the email template; and finally, distinguishing and storing the generated data file and the mail attachment sent to the client to a designated position.

Finally, after the email is generated, the email is automatically sent to the customer.

It should be noted that, in the execution process of a whole set of processes, besides the folder triggers, a plurality of triggers are set: for example, when the account information is detected to be extracted, a trigger task for inquiring the account information of the client is triggered; triggering a trigger task for generating a mail template after the report of the derived query result is monitored; upon monitoring the generation of the mail template, a trigger task for sending the mail to the customer is triggered. That is, the execution process is performed in order by trigger tasks generated by a plurality of triggers to achieve a preset purpose. Specifically, there are trigger tasks for querying account information of the client, trigger tasks for generating a mail template, and trigger tasks for sending mails to the client; combining the tasks into a trigger task queue according to the generated time sequence, and then sequentially executing the trigger tasks; for example, if the trigger task of the mail template is generated to be interrupted, the task is reinserted into the trigger task queue and re-executed according to the importance of the task; if the trigger tasks for generating the mail templates and the trigger tasks for sending the mails to the clients are generated in the same time, the importance and the logic relation of the trigger tasks are compared, and then the ordering of the trigger tasks for generating the mail templates in the trigger task queue is arranged before the trigger tasks for sending the mails to the clients.

Through the trigger process manager, the trigger process task memory and the business process processor, the problems that task conflict, disordered task execution sequence, task interruption cause trigger task execution failure and the like occur when the process robot RPA automatically executes tasks can be effectively solved, and therefore the efficiency and stability of an automatic process are improved. By using the task scheduling method, the time of manual intervention can be greatly shortened, the purpose of automatic processing is realized, manual operation is not needed, the processing efficiency is improved, and the possibility of manual intervention is reduced; meanwhile, by realizing automatic processing, enterprises can reduce human resource investment, and more efficiently complete complicated daily work, so that the human resource transfer is more important in aspects of business development, strategy formulation and the like, and the competitiveness and market share of the enterprises are improved; meanwhile, automatic processing of data and report generation can be realized, and the work of manually arranging the data in a traditional mode is avoided, so that time and manpower resources are saved; because the technology can automatically process complicated data analysis and report generation work, enterprises can make valuable operation decisions faster, and the overall business level is improved; meanwhile, the data is verified, a corresponding data protection mechanism is set, data leakage is prevented, user trust is improved, and service flow and profit are increased.

As known in the above, in the embodiment provided by the present disclosure, on one hand, a plurality of trigger tasks are generated and task sequence information and task type information corresponding to each trigger task are acquired, and then an execution order of the plurality of trigger tasks is determined according to the task sequence information and each trigger task is executed in sequence; on the other hand, in the process of executing each trigger task, the executing state of the trigger task is detected, if the trigger task is monitored to be interrupted, a corresponding interrupt processing strategy is determined according to the task type information of the interrupted trigger task, and interrupt processing is carried out on the interrupted trigger task according to the interrupt processing strategy. The method comprises the steps of sequencing the execution sequence of trigger tasks by means of task sequence information of the trigger tasks, and then executing the trigger tasks; if the trigger task is interrupted, determining an interrupt processing strategy of the interrupted trigger task according to the task type information of the interrupted trigger task, and carrying out interrupt processing on the task according to the interrupt processing strategy. According to the application, the task sequence information and the task type information of the trigger tasks are acquired, the trigger tasks are sequenced, and the retry strategy is prepared for the tasks with interruption, so that the usability of the flow robot RPA is improved, and the efficient and stable operation of an automatic flow is ensured.

Fig. 3 shows a block diagram of a task scheduling device provided by an embodiment of the present disclosure.

Referring to fig. 3, an embodiment of the present disclosure provides a task scheduling device 30, including:

the acquiring module 31 is adapted to generate a plurality of trigger tasks and acquire task sequence information and task type information corresponding to each trigger task;

the execution module 32 is adapted to determine the execution order of the plurality of trigger tasks according to the task sequence information, and execute each trigger task in turn; the interrupt processing method comprises the steps of executing interrupt processing on a trigger task with interrupt according to an interrupt processing strategy;

a monitoring module 33 adapted to monitor whether an interrupt occurs to each trigger task during execution of the trigger task; and under the condition that the trigger task with the interrupt is monitored, determining an interrupt processing strategy corresponding to the trigger task with the interrupt according to the task type information of the trigger task with the interrupt.

In an alternative implementation, the type weights for each risk type data include: a power exponent and a power base;

the power base corresponding to the type weight of each risk type data is the same, and the power base is more than or equal to 1; and, the larger the risk parameter score is, the larger the power exponent corresponding to the type weight of the risk type data is.

In an alternative implementation, the monitoring module 33 is further adapted to:

In an alternative implementation, the execution module 32 is specifically adapted to:

according to task sequence information corresponding to each trigger task, initial bit information of each trigger task in a trigger task queue is determined;

storing each trigger task into a trigger task queue according to the initial bit information;

each trigger task is acquired from the trigger task queue in turn and executed.

In an alternative implementation, the execution module 32 is further adapted to:

under the condition that at least two trigger tasks with the same initial bit information are detected, determining the at least two trigger tasks with the same initial bit information as a conflict task group;

determining the type priority of each trigger task in the conflict task group according to the task type information of each trigger task in the conflict task group;

And adjusting the initial bit information of each trigger task in the conflict task group according to the type priority of each trigger task in the conflict task group so that the initial bit information of each trigger task after adjustment is different.

determining retry bit information of the interrupted trigger task in a trigger task queue according to task type information of the interrupted trigger task;

and reinserting the interrupted trigger task into a trigger task queue according to the retry bit information so as to enable the interrupted trigger task to execute retry operation.

if the interrupted trigger task sends the interrupt again in the process of executing the retry operation, determining the current retry times of the interrupted trigger task;

In an alternative implementation, the acquisition module 31 is specifically adapted to:

monitoring various types of business events through a flow robot RPA;

triggering a task trigger corresponding to a business event under the condition of monitoring any type of business event, and generating a trigger task corresponding to the business event;

wherein the plurality of types of business events include at least one of: a timed trigger event corresponding to a time type, a key trigger event corresponding to an input type, and a mail trigger event corresponding to a text type.

An embodiment of the present disclosure provides an electronic device with reference to fig. 4, including: at least one processor 501; at least one memory 502, and one or more I/O interfaces 503, coupled between the processor 501 and the memory 502; wherein the memory 502 stores one or more computer programs executable by the at least one processor 501, the one or more computer programs being executed by the at least one processor 501 to perform the task scheduling method described above.

The disclosed embodiments also provide a computer readable storage medium having a computer program stored thereon, wherein the computer program, when executed by a processor/processing core, implements the task scheduling method described above. The computer readable storage medium may be a volatile or nonvolatile computer readable storage medium.

Embodiments of the present disclosure also provide a computer program product comprising computer readable code, or a non-transitory computer readable storage medium carrying computer readable code, which when executed in a processor of an electronic device, performs the task scheduling method described above.

Those of ordinary skill in the art will appreciate that all or some of the steps, systems, functional modules/units in the apparatus, and methods disclosed above may be implemented as software, firmware, hardware, and suitable combinations thereof. In a hardware implementation, the division between the functional modules/units mentioned in the above description does not necessarily correspond to the division of physical components; for example, one physical component may have multiple functions, or one function or step may be performed cooperatively by several physical components. Some or all of the physical components may be implemented as software executed by a processor, such as a central processing unit, digital signal processor, or microprocessor, or as hardware, or as an integrated circuit, such as an application specific integrated circuit. Such software may be distributed on computer-readable storage media, which may include computer storage media (or non-transitory media) and communication media (or transitory media).

The term computer storage media includes both volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable program instructions, data structures, program modules or other data, as known to those skilled in the art. Computer storage media includes, but is not limited to, random Access Memory (RAM), read Only Memory (ROM), erasable Programmable Read Only Memory (EPROM), static Random Access Memory (SRAM), flash memory or other memory technology, portable compact disc read only memory (CD-ROM), digital Versatile Discs (DVD) or other optical disc storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by a computer. Furthermore, as is well known to those of ordinary skill in the art, communication media typically embodies computer readable program instructions, data structures, program modules or other data in a modulated data signal such as a carrier wave or other transport mechanism and may include any information delivery media.

The computer readable program instructions described herein may be downloaded from a computer readable storage medium to a respective computing/processing device or to an external computer or external storage device over a network, such as the internet, a local area network, a wide area network, and/or a wireless network. The network may include copper transmission cables, fiber optic transmissions, wireless transmissions, routers, firewalls, switches, gateway computers and/or edge servers. The network interface card or network interface in each computing/processing device receives computer readable program instructions from the network and forwards the computer readable program instructions for storage in a computer readable storage medium in the respective computing/processing device.

Computer program instructions for performing the operations of the present disclosure can be assembly instructions, instruction Set Architecture (ISA) instructions, machine-related instructions, microcode, firmware instructions, state setting data, or source or object code written in any combination of one or more programming languages, including an object oriented programming language such as Smalltalk, c++ or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The computer readable program instructions may be executed entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computer (for example, through the Internet using an Internet service provider). In some embodiments, aspects of the present disclosure are implemented by personalizing electronic circuitry, such as programmable logic circuitry, field Programmable Gate Arrays (FPGAs), or Programmable Logic Arrays (PLAs), with state information of computer readable program instructions, which can execute the computer readable program instructions.

The computer program product described herein may be embodied in hardware, software, or a combination thereof. In an alternative embodiment, the computer program product is embodied as a computer storage medium, and in another alternative embodiment, the computer program product is embodied as a software product, such as a software development kit (Software Development Kit, SDK), or the like.

Various aspects of the present disclosure are described herein with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the disclosure. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer-readable program instructions.

These computer readable program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks. These computer readable program instructions may also be stored in a computer readable storage medium that can direct a computer, programmable data processing apparatus, and/or other devices to function in a particular manner, such that the computer readable medium having the instructions stored therein includes an article of manufacture including instructions which implement the function/act specified in the flowchart and/or block diagram block or blocks.

The computer readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus or other devices to produce a computer implemented process such that the instructions which execute on the computer, other programmable apparatus or other devices implement the functions/acts specified in the flowchart and/or block diagram block or blocks.

The flowcharts and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of instructions, which comprises one or more executable instructions for implementing the specified logical function(s). In some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

Example embodiments have been disclosed herein, and although specific terms are employed, they are used and should be interpreted in a generic and descriptive sense only and not for purpose of limitation. In some instances, it will be apparent to one skilled in the art that features, characteristics, and/or elements described in connection with a particular embodiment may be used alone or in combination with other embodiments unless explicitly stated otherwise. It will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the scope of the disclosure as set forth in the appended claims.

Claims

1. A method for task scheduling, comprising:

2. The method according to claim 1, wherein determining an interrupt processing policy corresponding to the interrupt-generated trigger task according to task type information of the interrupt-generated trigger task comprises:

determining an interrupt processing strategy corresponding to the trigger task with interrupt occurrence to retry execution class strategy under the condition that the task type information is first type information;

and under the condition that the task type information is the second type information, determining that the interrupt processing strategy corresponding to the trigger task with the interrupt is an execution class strategy.

3. The method of claim 2, wherein determining the order of execution of the plurality of trigger tasks based on the task sequence information, and executing each trigger task in turn, comprises:

storing each trigger task into the trigger task queue according to the initial bit information;

And sequentially acquiring each trigger task from the trigger task queue and executing the trigger tasks.

4. The method of claim 3, wherein determining initial bit information of each trigger task in the trigger task queue according to task sequence information corresponding to each trigger task further comprises:

5. A method according to claim 3, wherein, in the case that the interrupt handling policy corresponding to the interrupt-occurring trigger task is a retry execution class policy, the performing interrupt handling on the interrupt-occurring trigger task according to the interrupt handling policy comprises:

Determining retry bit information of the interrupted trigger task in a trigger task queue according to the task type information of the interrupted trigger task;

and reinserting the trigger task with the interrupt into the trigger task queue according to the retry bit information so as to enable the trigger task with the interrupt to execute retry operation.

6. The method of claim 5, wherein said reinserting said interrupted trigger task into said trigger task queue based on said retry bit information further comprises:

repeatedly executing the task type information according to the interrupted trigger task under the condition that the current retry time is smaller than a preset time threshold, determining retry bit time information of the interrupted trigger task in a trigger task queue, and reinserting the interrupted trigger task into the trigger task queue according to the retry bit time information;

The preset times threshold is determined according to task type information of the trigger task with interruption.

7. The method of claim 6, wherein generating a plurality of trigger tasks comprises:

monitoring various types of business events through a flow robot RPA;

8. A task scheduling device, comprising:

9. An electronic device, comprising:

at least one processor; and

a memory communicatively coupled to the at least one processor; wherein,

the memory stores one or more computer programs executable by the at least one processor to enable the at least one processor to perform the method of any one of claims 1-7.

10. A computer readable storage medium, on which a computer program is stored, which, when being executed by a processor, implements the method according to any of claims 1-7.