Automatic task driving method and device and electronic equipment

Abstract

The invention provides an automatic task driving method and device and electronic equipment, and belongs to the field of data processing. The method comprises the steps of obtaining a user demand; determining a service identifier and a service type according to a user demand, wherein the service identifier is used for indicating specific service content related to ship transportation; a rule packet list is obtained from a rule packet library according to the service identifier and the service type, the rule packet list comprises a plurality of rule packets, and each rule packet is used for indicating a task execution process; determining a current business state of the business object according to the business identifier; generating a target task list according to the current service state and the rule packet list, wherein the target task list comprises a plurality of to-be-executed tasks; and sending a task message of the to-be-executed task to the target execution queue to obtain an execution result returned by a task execution system corresponding to the to-be-executed task, the task execution system being a consumer of the target execution queue. Automatic driving of ship transportation related processes is achieved, and the system efficiency is improved.

Description

Technical Field

[0001] This application belongs to the field of data processing, and specifically relates to an automated task-driven method, apparatus, and electronic device. Background Technology

[0002] With the accelerating pace of global economic integration, international maritime trade volume has shown a sustained growth trend, and as the most important logistics mode in international trade, shipping bookings have also surged. However, current shipping-related processes in the industry still largely rely on traditional manual operation methods, resulting in numerous technical bottlenecks that urgently need to be addressed.

[0003] Specifically, existing shipping-related business processes heavily rely on manual intervention: operators need to extract booking requests one by one from massive amounts of customer emails or Excel spreadsheets, manually visually check the compliance of each order, including the completeness of cargo information and special cargo declaration requirements; then, they need to manually compare the shipping company's schedule to match space and plan routes; finally, they need to manually maintain a bill of lading number allocation ledger to avoid duplicate numbers. This entire process is not only time-consuming, but also prone to oversights due to operator fatigue during peak periods, such as duplicate bill of lading numbers and conflicting shipping schedules. The traditional manual processing model is clearly unable to meet the needs of business development, and the industry urgently needs to achieve a digital transformation of the booking process through technological innovation. Summary of the Invention

[0004] This application provides an automated task-driven method, apparatus, and electronic device to automate ship transportation-related processes and improve system efficiency.

[0005] This application provides an automated task-driven method, including: Obtain user needs; The service identifier and service type are determined based on the user requirements. The service identifier is used to indicate the specific business content related to shipping. A list of rule packages is obtained from the rule package library based on the business identifier and the business type. The list of rule packages includes multiple rule packages, each of which is used to indicate a task execution process. The current business status of the business object is determined based on the business identifier; A target task list is generated based on the current business status and the rule package list, and the target task list includes multiple tasks to be executed. The task message of the pending task among the multiple pending tasks is sent to the target execution queue to obtain the execution result returned by the task execution system corresponding to the pending task, wherein the task execution system is the consumer of the target execution queue.

[0006] According to the automated task-driven method provided in this application, the step of obtaining a list of rule packages from a rule package library based on the business identifier and the business type includes: obtaining a set of rule packages from the rule package library based on the business type; determining at least one target rule package from the set of rule packages based on the business identifier; obtaining a list of dependency fields of the set of rule packages, the list of dependency fields indicating the dependency relationship of each rule package in the set of rule packages; and sorting the at least one target rule package sequentially according to the list of dependency fields to obtain a list of rule packages, wherein each subsequent rule package in the list depends on the execution result of the task to be executed corresponding to the preceding rule package.

[0007] According to the automated task-driven method provided in this application, the step of generating a target task list based on the current business state and the rule package list includes: performing the following operations for each target rule package in the rule package list: obtaining a decision tree corresponding to the target rule package, wherein the decision tree includes multiple condition layers and at least one task to be executed, each of the multiple condition layers indicating an execution condition, and the task to be executed being associated with at least one execution condition; sequentially matching the execution conditions in the multiple condition layers according to the current business state to obtain a matching result; determining whether a target task to be executed exists based on the matching result; if it exists, adding the target task to be executed to an initial task list; and generating the target task list based on the initial task list.

[0008] According to the automated task-driven method provided in this application, before sending the task message of the pending task among the plurality of pending tasks to the target execution queue, the method further includes: obtaining the warning rule for each pending task in the target task list; generating a warning list according to the warning rule; and entering the warning list into a warning monitoring system, wherein the warning monitoring system is used to output warning information when the execution status of the pending task meets the corresponding warning rule.

[0009] According to the automated task-driven method provided in this application, sending the task message of the pending task among the plurality of pending tasks to the target execution queue includes: performing the following operations for each pending task in the target task list: determining the business identifier corresponding to the pending task; determining the target business based on the business identifier; determining the pending task as a high-priority task if the target business enters a high-priority mode; adding the high-priority task to the high-priority task list; and calling the target execution queue to sequentially send the task messages of the pending tasks in the high-priority task list, wherein the target execution queue is a high-priority queue with high-priority mode enabled.

[0010] According to the automated task-driven method provided in this application, before the target execution queue is invoked to sequentially send task messages of the tasks to be executed in the high-priority task list, the method further includes: obtaining the blocking value of the current consumer group; if the blocking value does not exceed the blocking threshold, opening the high-priority mode of the high-priority queue; the step of invoking the target execution queue to sequentially send the tasks to be executed in the high-priority task list includes: obtaining the high-priority task list; invoking the high-priority queue to sequentially send task messages of the tasks to be executed in the high-priority task list.

[0011] According to the automated task-driven method provided in this application, the method further includes: obtaining a list of low-priority tasks, wherein the tasks to be executed included in the list of low-priority tasks are low-priority tasks; and calling the low-priority queue to send task messages of the tasks to be executed in the list of low-priority tasks in turn after the high-priority queue has been closed or after the high-priority queue has been consumed.

[0012] This application also provides an automated task-driven device, comprising: The first acquisition unit is used to acquire user needs; The first determining unit is used to determine the business identifier and business type according to the user requirements, wherein the business identifier is used to indicate specific business content related to shipping. The second acquisition unit is used to acquire a list of rule packages from the rule package library according to the business identifier and the business type. The list of rule packages includes multiple rule packages, and each rule package is used to indicate a task execution process. The second determining unit is used to determine the current business status of the business object based on the business identifier; A generation unit is configured to generate a target task list based on the current business status and the rule package list, wherein the target task list includes multiple tasks to be executed. The sending unit is used to send the task message of the task to be executed among the plurality of tasks to be executed to the target execution queue, so as to obtain the execution result returned by the task execution system corresponding to the task to be executed, wherein the task execution system is the consumer of the target execution queue.

[0013] This application also provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the automated task-driven method described above.

[0014] This application also provides a non-transitory computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the automated task-driven method as described above.

[0015] This application also provides a computer program product, including a computer program that, when executed by a processor, implements the automated task-driven method as described above.

[0016] The automated task-driven method, apparatus, and electronic device provided in this application first acquire user requirements, then determine a business identifier and business type based on the user requirements. The business identifier indicates specific business content related to shipping. Next, a list of rule packages is retrieved from a rule package library based on the business identifier and business type. This list includes multiple rule packages, each indicating a task execution process. Then, the current business state of the business object is determined based on the business identifier. Following this, a target task list is generated based on the current business state and the rule package list. This target task list includes multiple tasks to be executed. Finally, task messages for the tasks to be executed are sent to a target execution queue to obtain execution results returned by the task execution system corresponding to each task. The task execution system is a consumer of the target execution queue. This enables automated driving of shipping-related processes, improving system efficiency. Attached Figure Description

[0017] To more clearly illustrate the technical solutions in this invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of this invention. For those skilled in the art, other drawings can be obtained from these drawings without creative effort.

[0018] Figure 1 This is a flowchart illustrating an automated task-driven method provided in this application.

[0019] Figure 2 This is a schematic diagram of the decision tree provided in this application.

[0020] Figure 3 This is a schematic diagram of the functional units of an automated task-driven device provided in this application.

[0021] Figure 4 This is a schematic diagram of the structure of the electronic device provided in this application. Detailed Implementation

[0022] To make the objectives, technical solutions, and advantages of this invention clearer, the technical solutions of this invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this invention. All other embodiments obtained by those skilled in the art based on the embodiments of this invention without creative effort are within the scope of protection of this invention.

[0023] The terms "first," "second," etc., in the specification, claims, and accompanying drawings of this application are used to distinguish different objects, not to describe a specific order. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or apparatus that includes a series of steps or units is not limited to the listed steps or units, but may optionally include steps or units not listed, or may optionally include other steps or units inherent to these processes, methods, products, or apparatuses.

[0024] In this document, the term "embodiment" means that a particular feature, structure, or characteristic described in connection with an embodiment may be included in at least one embodiment of this application. The appearance of this phrase in various places throughout the specification does not necessarily refer to the same embodiment, nor is it a separate or alternative embodiment mutually exclusive with other embodiments. It will be explicitly and implicitly understood by those skilled in the art that the embodiments described herein can be combined with other embodiments.

[0025] Currently, the ship transportation process in the industry generally adopts the traditional manual operation mode. The whole process is not only time-consuming, but also prone to omissions due to operator fatigue during peak business periods.

[0026] To address the aforementioned problems, this application provides an automated task-driven method, apparatus, and electronic device. Please refer to... Figure 1 The automated task-driven method includes the following steps.

[0027] S101, Obtain user requirements.

[0028] The user request can indicate a business data change event or a business data query event. For example, the user request could be to add a booking to shipping company A.

[0029] S102, determine the service identifier and service type based on the user requirements.

[0030] The business identifier is used to indicate specific business content related to shipping. This business type can include order business types, booking business types, and Verified Gross Mass (VGM) business types, etc. Different business types correspond to multiple specific businesses, and each specific business has a unique business identifier. Specifically, the business identifier can also indicate information about the shipping company; that is, different shipping companies may use different business identifiers for the same specific business. If user requirements necessitate implementation based on multiple specific businesses, the business identifier can include multiple identifiers. If multiple business identifiers correspond to specific businesses belonging to different business types, then the business type can also include multiple types.

[0031] S103, Obtain a list of rule packages from the rule package library based on the service identifier and the service type.

[0032] The rule package list includes multiple rule packages, each of which is used to indicate a task execution process.

[0033] S104, determine the current business status of the business object based on the business identifier.

[0034] When determining the current business status, the business object can be located first based on the business identifier, which could be the corresponding shipping company. Then, the current business status corresponding to the specific business identified by the business identifier is determined. For example, if the specific business corresponding to the business identifier is customs clearance cancellation, the current business status to be queried is whether the booking was successful, and if so, whether the corresponding order has been confirmed.

[0035] S105, Generate a target task list based on the current business status and the rule package list.

[0036] The target task list includes multiple tasks to be executed.

[0037] S106, send the task message of the pending task among the multiple pending tasks to the target execution queue, so as to obtain the execution result returned by the task execution system corresponding to the pending task.

[0038] The task execution system is a consumer of the target execution queue. It can send task messages for tasks to be executed sequentially according to the task order in the target execution task list. Before sending the next task message, it can first determine whether the execution result of the current task has been returned; only after obtaining the execution result can the task message for the next task be sent. Specifically, before sending a task message, the task execution system corresponding to the task can be determined first; different task execution systems correspond to different shipping companies and / or different business contents. After determining the task execution system, the message queue corresponding to that task execution system is obtained, and the task message is sent by calling that message queue.

[0039] As can be seen, in this embodiment, user requirements are first obtained, and then a business identifier and business type are determined based on the user requirements. The business identifier indicates specific business content related to shipping. Next, the current business status of the business object is determined based on the business identifier. Then, a list of rule packages is obtained from the rule package library based on the current business status, the business identifier, and the business type. The list of rule packages includes multiple rule packages, each indicating a task execution process. Next, a target task list is generated based on the rule package list, including multiple tasks to be executed. Finally, task messages for the tasks to be executed are sent to the target execution queue to obtain the execution results returned by the task execution system corresponding to the tasks to be executed. The execution results indicate that the business data change event has been processed. This enables automated driving of shipping-related processes and improves system efficiency.

[0040] In one possible embodiment, obtaining a list of rule packages from a rule package library based on the business identifier and the business type includes: obtaining a set of rule packages from the rule package library based on the business type; determining at least one target rule package from the set of rule packages based on the business identifier; obtaining a list of dependency fields of the set of rule packages, the list of dependency fields indicating the dependency relationship of each rule package in the set of rule packages; and sorting the at least one target rule package sequentially according to the list of dependency fields to obtain a list of rule packages, wherein each subsequent rule package in the list depends on the execution result of the task to be executed corresponding to the preceding rule package.

[0041] Specifically, rule packages can be pre-generated based on the execution flow of each specific business. When relevant business needs to be executed, the rule package can be directly invoked, and the task to be executed can be obtained based on the execution flow within the rule package. Since different shipping companies may have different execution flows for the same task, the applicable shipping companies for each rule package can be determined when pre-generating the rule packages. When obtaining the rule package set based on business type, the specific shipping company can also be determined based on the business identifier. Then, the set of rule packages corresponding to that business type can be obtained. Finally, the set of rule packages is determined based on the shipping company corresponding to each rule package in the set of rule packages. That is, each rule package in the set of rule packages is the rule package corresponding to that shipping company under that business type.

[0042] In practice, a user's needs may consist of multiple tasks. Therefore, it is necessary to obtain the rule package corresponding to each task and then automatically drive the tasks to execute sequentially based on the corresponding rule package. For example, if the user's needs are to complete the process from placing an order to the goods being shipped out, the corresponding rule package could include the rule package associated with the order entry task, the rule package associated with the order verification task, the rule package associated with the booking task, the rule package associated with the shipping task, and the rule package associated with the document generation task.

[0043] In practice, each rule package in the rule package library can be modified individually. That is, if the execution flow of a task changes, or the shipping company updates its related execution flow, the rule packages to be updated can be filtered based on the task name and the shipping company. Then, the filtered rule packages are updated based on the updated content. This allows the next automated task execution to be based on the updated flow.

[0044] As can be seen, in this embodiment, obtaining a set of rule packages based on business type and business identifier, and then generating a list of rule packages based on dependency relationships, can achieve automated task driving and improve task execution efficiency and accuracy.

[0045] In one possible embodiment, generating the target task list based on the current business state and the rule package list includes: performing the following operations for each target rule package in the rule package list: obtaining a decision tree corresponding to the target rule package, the decision tree including multiple condition layers and at least one task to be executed, each of the multiple condition layers indicating an execution condition, and the task to be executed being associated with at least one execution condition; sequentially matching the execution conditions in the multiple condition layers according to the current business state to determine the target task to be executed; adding the target task to be executed to an initial task list; and determining the initial task list as the target task list if the initial task list includes the target task to be executed corresponding to each target rule package.

[0046] Please refer to Figure 2 , Figure 2 (a) in the table corresponds to the rule package for adding a booking, which includes two condition layers. First, it determines whether the booking is in the new booking status based on the current business status. Then, it determines whether the order corresponding to the new booking is valid based on the decision tree. If valid, it determines whether the order has been confirmed. If the order has been confirmed, a corresponding task to be executed is generated, i.e., an EDI booking is sent to the shipping company. If the order is invalid or unconfirmed, the task corresponding to this rule package will not be obtained. Figure 2 In clause (b), after the order corresponding to the new booking service has been confirmed, the rule flow in the rule package is as follows: If the order is valid, then task 1 to be executed is generated: receive the shipping company's BC receipt. After completing task 1 and receiving the shipping company's BC receipt, task 2 to be executed is generated: then update the single-ticket information according to the BC receipt. If the customer needs to cancel customs clearance after the order has been confirmed, then if the order is invalid, task 2 to be executed is generated: send a customs clearance cancellation application to the shipping company.

[0047] Specifically, when retrieving the task list, the rule packages in the rule package list can be executed sequentially based on the current business status. If an execution condition in a rule package is not met, no task corresponding to that rule package will be generated. After all rule packages have been polled, the current initial task list is determined as the target task list, and then task messages for the tasks to be executed in the target task list are sent. Then, the current business status is updated based on the execution results, and then the rule packages with no determined tasks to be executed are executed based on the updated current business status to obtain the corresponding tasks to be executed. The above steps are repeated until the target task list includes all tasks to be executed corresponding to the target rule packages.

[0048] Specifically, before sending the task message for the task to be executed based on the target task list, it can be determined whether there is a task to be executed with a sent task message in the target task list. If there is, the task to be executed with the sent task message is skipped.

[0049] As can be seen, in this embodiment, determining the tasks to be executed based on the decision tree can quickly identify the tasks to be executed for each specific business, thereby improving the accuracy and efficiency of task determination.

[0050] In one possible embodiment, before sending the task message of the pending task among the plurality of pending tasks to the target execution queue, the method further includes: obtaining the warning rule for each pending task in the target task list; generating a warning list according to the warning rule; and entering the warning list into a warning monitoring system, wherein the warning monitoring system is used to output warning information when the execution status of the pending task meets the corresponding warning rule.

[0051] The early warning rule can be a timeout warning, which sets an execution time for a task to be executed. If the execution result of the task is not obtained after the preset time, the early warning monitoring system outputs an early warning message. If the execution result of the task has been obtained and no early warning has been triggered, the early warning for that task is canceled from the early warning monitoring system.

[0052] As can be seen, in this embodiment, by determining early warning rules for each task to be executed and monitoring its execution process, early warnings can be issued in a timely manner for abnormal tasks to be executed, thereby improving the efficiency of the automated task-driven process.

[0053] In one possible embodiment, sending the task message of the pending task among the plurality of pending tasks to the target execution queue includes: performing the following operations for each pending task in the target task list: determining the service identifier corresponding to the pending task; determining the target service based on the service identifier; if the target service enters a high-priority mode, determining the pending task as a high-priority task; adding the high-priority task to the high-priority task list; and calling the target execution queue to sequentially send the task messages of the pending tasks in the high-priority task list, wherein the target execution queue is a high-priority queue with high-priority mode enabled.

[0054] Within this framework, a single business identifier can correspond to multiple rule packages, and the same business identifier may correspond to multiple tasks awaiting execution. If the specific business corresponding to the business identifier is a high-priority business, then all its corresponding tasks awaiting execution are also high-priority tasks. Similarly, if the target business corresponding to the business identifier is a low-priority business, then the task awaiting execution is added to a low-priority list, and the task messages for the tasks in the low-priority list are sent using a low-priority queue.

[0055] As can be seen, in this embodiment, determining the target execution queue based on the priority of the target business corresponding to the task to be executed can improve task execution efficiency.

[0056] In one possible embodiment, before the target execution queue is invoked to sequentially send task messages of the tasks to be executed in the high-priority task list, the method further includes: obtaining the blocking value of the current consumer group; if the blocking value does not exceed the blocking threshold, opening the high-priority mode of the high-priority queue; the invocation of the target execution queue to sequentially send the tasks to be executed in the high-priority task list includes: obtaining the high-priority task list; invoking the high-priority queue to sequentially send task messages of the tasks to be executed in the high-priority task list.

[0057] Specifically, the decision to enable high-priority mode for a high-priority queue can be determined based on the current blocking status of the consumer group. Only when high-priority mode is enabled will the queue be used to send task messages for pending tasks in the high-priority list. If high-priority mode is enabled for the high-priority queue, and the current consumer group's blocking value exceeds a preset value, then high-priority mode for the high-priority queue will be disabled.

[0058] In practice, after enabling the high-priority mode of the high-priority queue, a high-priority point can be marked as completed, and then the high-priority queue can be invoked to push task messages from the high-priority task list. Once consumption is complete, the high-priority consumption point is marked as completed.

[0059] As can be seen, in this embodiment, determining whether to enable the high-priority mode of the high-priority queue based on the consumption blocking situation can significantly improve the system's response efficiency, resource utilization, and business continuity.

[0060] In one possible embodiment, the method further includes: obtaining a list of low-priority tasks, wherein the tasks to be executed included in the list of low-priority tasks are low-priority tasks; and calling the low-priority queue to sequentially send task messages of the tasks to be executed in the list of low-priority tasks after the high-priority queue has been closed or the high-priority queue has been consumed.

[0061] The method for obtaining the low-priority task list can be the same as the method for obtaining the high-priority task list described above. When the consumption blocking threshold exceeds a preset value, the high-priority mode of the high-priority queue is disabled. When all task messages for the pending tasks in the high-priority list corresponding to the high-priority queue have been pushed, the high-priority queue has been consumed. At this time, the low-priority list is invoked to send the task messages for the pending tasks in the low-priority task list.

[0062] As can be seen, in this embodiment, sending high-priority tasks first and then sending lower-priority tasks based on the low-priority queue can improve system resource utilization, optimize task throughput and latency, and enhance system stability and fault tolerance.

[0063] The following describes an automated task-driving device provided in this application. The automated task-driving device described below corresponds to the automated task-driving method described above.

[0064] Please see Figure 3The automated task-driven device 300 includes: a first acquisition unit 301 for acquiring user requirements; a first determination unit 302 for determining a business identifier and a business type based on the user requirements, wherein the business identifier indicates specific business content related to ship transportation; a second acquisition unit 303 for acquiring a list of rule packages from a rule package library based on the business identifier and the business type, wherein the list of rule packages includes multiple rule packages, each of which indicates a task execution process; a second determination unit 304 for determining the current business status of a business object based on the business identifier; a generation unit 305 for generating a target task list based on the current business status and the list of rule packages, wherein the target task list includes multiple tasks to be executed; and a sending unit 306 for sending task messages of the tasks to be executed from the multiple tasks to be executed to a target execution queue, thereby obtaining the execution results returned by the task execution system corresponding to the task to be executed, wherein the task execution system is a consumer of the target execution queue.

[0065] In one possible embodiment, regarding the step of obtaining a list of rule packages from the rule package library based on the business identifier and the business type, the second obtaining unit 303 is specifically configured to: obtain a set of rule packages from the rule package library based on the business type; determine at least one target rule package from the set of rule packages based on the business identifier; obtain a list of dependency fields of the set of rule packages, the list of dependency fields indicating the dependency relationship of each rule package in the set of rule packages; and sort the at least one target rule package sequentially according to the list of dependency fields to obtain a list of rule packages, wherein each subsequent rule package in the list depends on the execution result of the task to be executed corresponding to the preceding rule package.

[0066] In one possible embodiment, regarding the generation of the target task list based on the current business state and the rule package list, the generation unit 305 is specifically configured to perform the following operations for each target rule package in the rule package list: Obtain the decision tree corresponding to the target rule package. The decision tree includes multiple condition layers and at least one task to be executed. Each condition layer indicates an execution condition, and the task to be executed is associated with at least one execution condition. Match the execution conditions in the multiple condition layers sequentially according to the current business state to obtain a matching result. Determine whether there is a target task to be executed based on the matching result. If there is, add the target task to be executed to the initial task list. Generate the target task list based on the initial task list.

[0067] In one possible embodiment, the automated task driving device 300 further includes an early warning unit. Before sending the task message of the pending task among the plurality of pending tasks to the target execution queue, the early warning unit is specifically used to: obtain the early warning rule for each pending task in the target task list; generate an early warning list according to the early warning rule; and input the early warning list into an early warning monitoring system, wherein the early warning monitoring system is used to output early warning information when the execution status of the pending task meets the corresponding early warning rule.

[0068] In one possible embodiment, in sending the task messages of the multiple tasks to be executed to the target execution queue, the sending unit 306 is specifically configured to: perform the following operations for each task to be executed in the target task list: determine the service identifier corresponding to the task to be executed; determine the target service based on the service identifier; if the target service enters a high-priority mode, determine that the task to be executed is a high-priority task; add the high-priority task to the high-priority task list; and call the target execution queue to sequentially send the task messages of the tasks to be executed in the high-priority task list, wherein the target execution queue is a high-priority queue with high-priority mode enabled.

[0069] In one possible embodiment, before the target execution queue sequentially sends the task messages of the tasks to be executed in the high-priority task list, the sending unit 306 is further configured to: obtain the blocking value of the current consumer group; and, if the blocking value does not exceed the blocking threshold, enable the high-priority mode of the high-priority queue; in terms of the target execution queue sequentially sending the tasks to be executed in the high-priority task list, the sending unit 306 is specifically configured to: obtain the high-priority task list; and invoke the high-priority queue to sequentially send the task messages of the tasks to be executed in the high-priority task list.

[0070] In one possible embodiment, the sending unit 306 is further configured to: obtain a list of low-priority tasks, wherein the tasks to be executed included in the list of low-priority tasks are low-priority tasks; and, after the high-priority mode of the high-priority queue has been turned off or the high-priority queue has been consumed, invoke the low-priority queue to sequentially send the task messages of the tasks to be executed in the list of low-priority tasks.

[0071] Please see Figure 4 , Figure 4 This is a schematic diagram of the structure of the electronic device provided in this application. For example... Figure 4As shown, the electronic device may include: a processor 410, a communications interface 420, a memory 430, and a communication bus 440, wherein the processor 410, the communications interface 420, and the memory 430 communicate with each other through the communication bus 440. The processor 410 can call logical instructions in the memory 430 to execute an automated task-driven method, which includes: obtaining user requirements; determining a business identifier and a business type based on the user requirements, wherein the business identifier indicates specific business content related to ship transportation; obtaining a list of rule packages from a rule package library based on the business identifier and the business type, wherein the list of rule packages includes multiple rule packages, each indicating a task execution process; determining the current business state of a business object based on the business identifier; generating a target task list based on the current business state and the rule package list, wherein the target task list includes multiple tasks to be executed; and sending task messages of the tasks to be executed from the multiple tasks to a target execution queue to obtain the execution results returned by the task execution system corresponding to the task to be executed, wherein the task execution system is a consumer of the target execution queue.

[0072] Furthermore, the logical instructions in the aforementioned memory 430 can be implemented as software functional units and, when sold or used as independent products, can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, or the part that contributes to the prior art, or a part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0073] On the other hand, the present invention also provides a non-transitory computer-readable storage medium storing a computer program thereon, which, when executed by a processor, implements an automated task-driven method provided by the methods described above. This method includes: acquiring user requirements; determining a business identifier and a business type based on the user requirements, the business identifier indicating specific business content related to shipping; acquiring a list of rule packages from a rule package library based on the business identifier and the business type, the list including multiple rule packages, each indicating a task execution process; determining the current business state of a business object based on the business identifier; generating a target task list based on the current business state and the rule package list, the target task list including multiple tasks to be executed; and sending task messages of the tasks to be executed from among the multiple tasks to a target execution queue to obtain execution results returned by the task execution system corresponding to the tasks to be executed, the task execution system being a consumer of the target execution queue.

[0074] In another aspect, this application also provides a computer program product, including a computer program that, when executed by a processor, implements any of the above-described automated task-driven methods. The method includes: acquiring user requirements; determining a business identifier and a business type based on the user requirements, the business identifier indicating specific business content related to shipping; acquiring a list of rule packages from a rule package library based on the business identifier and the business type, the list including multiple rule packages, each indicating a task execution process; determining the current business state of a business object based on the business identifier; generating a target task list based on the current business state and the rule package list, the target task list including multiple tasks to be executed; and sending task messages of the tasks to be executed from among the multiple tasks to a target execution queue to obtain execution results returned by the task execution system corresponding to the task to be executed, the task execution system being a consumer of the target execution queue.

[0075] The device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs. Those skilled in the art can understand and implement this without any creative effort.

[0076] Through the above description of the embodiments, those skilled in the art can clearly understand that each embodiment can be implemented by means of software plus necessary general-purpose hardware platforms, and of course, it can also be implemented by hardware. Based on this understanding, the above technical solutions, in essence or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product can be stored in a computer-readable storage medium, such as ROM / RAM, magnetic disk, optical disk, etc., and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute the methods described in the various embodiments or some parts of the embodiments.

[0077] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, and not to limit them; although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features; and these modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present invention.

Claims

1. An automated task-driven method, characterized in that, include: Obtain user needs; The service identifier and service type are determined based on the user requirements. The service identifier is used to indicate the specific business content related to shipping. A list of rule packages is obtained from the rule package library based on the business identifier and the business type. The list of rule packages includes multiple rule packages, each of which is used to indicate a task execution process. The current business status of the business object is determined based on the business identifier; A target task list is generated based on the current business status and the rule package list, and the target task list includes multiple tasks to be executed. The task message of the pending task among the multiple pending tasks is sent to the target execution queue to obtain the execution result returned by the task execution system corresponding to the pending task, wherein the task execution system is the consumer of the target execution queue.

2. The method according to claim 1, characterized in that, The step of obtaining a list of rule packages from the rule package library based on the service identifier and the service type includes: Retrieve a set of rule packages from the rule package library according to the business type; At least one target rule package is determined from the rule package set based on the business identifier; Obtain the dependency field list of the rule package set, the dependency field list being used to indicate the dependency relationship of each rule package in the rule package set; The at least one target rule package is sorted sequentially according to the dependency field list to obtain a rule package list, wherein each rule package in the rule package list depends on the execution result of the task to be executed corresponding to the previous rule package.

3. The method according to claim 2, characterized in that, The step of generating a target task list based on the current business status and the rule package list includes: Perform the following operations for each target rule package in the rule package list: Obtain the decision tree corresponding to the target rule package. The decision tree includes multiple condition layers and at least one task to be executed. Each condition layer indicates an execution condition, and the task to be executed is associated with at least one execution condition. The execution conditions in the multiple condition layers are matched sequentially according to the current business status to obtain the matching results; Based on the matching results, determine whether there is a target task to be executed; If it exists, add the target task to be executed to the initial task list; The target task list is generated based on the initial task list.

4. The method according to claim 1, characterized in that, Before sending the task message of the pending task from the plurality of pending tasks to the target execution queue, the method further includes: Obtain the warning rules for each task to be executed in the target task list; A warning list is generated based on the aforementioned warning rules; The warning list is entered into the warning monitoring system, which outputs warning information when the execution status of the task to be executed meets the corresponding warning rules.

5. The method according to any one of claims 1-4, characterized in that, Sending the task message of the pending task from the plurality of pending tasks to the target execution queue includes: Perform the following operations for each task to be executed in the target task list: Determine the business identifier corresponding to the task to be executed; The target service is determined based on the service identifier; When the target service enters a high-priority mode, the task to be executed is determined to be a high-priority task; Add the high-priority task to the high-priority task list; The target execution queue is invoked to send task messages of the tasks to be executed in the high-priority task list in sequence. The target execution queue is a high-priority queue with high-priority mode enabled.

6. The method according to claim 5, characterized in that, Before the execution queue of the target call sequentially sends the task messages of the tasks to be executed in the high-priority task list, the method further includes: Get the current blocking value of the consumer group; If the blocking value does not exceed the blocking threshold, the high-priority mode of the high-priority queue is enabled. The execution queue of the call target sequentially sends the tasks to be executed from the high-priority task list, including: Obtain the list of high-priority tasks; The high-priority queue is invoked to sequentially send task messages for the tasks to be executed in the high-priority task list.

7. The method according to claim 6, characterized in that, The method further includes: Obtain a list of low-priority tasks, wherein the tasks to be executed included in the list of low-priority tasks are low-priority tasks; Once the high-priority mode of the high-priority queue is turned off or the high-priority queue has finished consuming tasks, the low-priority queue is invoked to send the task messages of the pending tasks in the low-priority task list in sequence.

8. An automated task-driven device, characterized in that, include: The first acquisition unit is used to acquire user needs; The first determining unit is used to determine the business identifier and business type according to the user requirements, wherein the business identifier is used to indicate specific business content related to shipping. The second acquisition unit is used to acquire a list of rule packages from the rule package library according to the business identifier and the business type. The list of rule packages includes multiple rule packages, and each rule package is used to indicate a task execution process. The second determining unit is used to determine the current business status of the business object based on the business identifier; A generation unit is configured to generate a target task list based on the current business status and the rule package list, wherein the target task list includes multiple tasks to be executed. The sending unit is used to send the task message of the task to be executed among the plurality of tasks to be executed to the target execution queue, so as to obtain the execution result returned by the task execution system corresponding to the task to be executed, wherein the task execution system is the consumer of the target execution queue.

9. An electronic device comprising a memory, a processor, and a computer program stored in the memory and running on the processor, characterized in that, When the processor executes the computer program, it implements the automated task-driven method as described in any one of claims 1 to 7.

10. A non-transitory computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the automated task-driven method as described in any one of claims 1 to 7.

Images