Task processing method and device, electronic equipment and storage medium

Abstract

The embodiment of the invention discloses a task processing method and device, electronic equipment and a storage medium, and the method comprises the steps: generating an early warning work order based on a to-be-processed task when it is detected that the to-be-processed task has a processing exception and an exception reporting library does not comprise reporting information corresponding to the to-be-processed task; sending the early warning work order to a target collaboration platform, so that the task executor uploads the abnormal association information to the target collaboration platform; and receiving exception association information fed back by the target collaboration platform, and updating task association information of the to-be-processed task based on the exception association information so as to determine whether the to-be-processed task has processing exception based on the task association information. According to the method and the device, the problems of untimely abnormity monitoring, unclear abnormal nodes and low task processing efficiency caused by passive monitoring of the task are solved, the abnormity monitoring timeliness is improved, the abnormal nodes are accurately positioned, abnormity feedback is quickly performed, the task processing efficiency is improved, and the effect of improving the user experience is achieved.

Description

Technical Field

[0001] The embodiments of the present invention relate to the field of computer processing technology, and in particular to a task processing method, device, electronic device and storage medium. Background Art

[0002] In recent years, with the development and popularization of e-commerce services, the number of orders received by merchants on the platform has also increased. After receiving the order, it is usually necessary to initiate an order task based on a third party for processing, such as carrier processing. In the case of third-party processing, there may be various abnormal situations during the processing, such as slow order delivery, untimely collection, long transit time, and delivery errors. At this time, it is necessary to monitor the order task. The existing monitoring method is usually that the third party updates the logistics information based on the task processing situation, and the merchant or user determines which node in the task processing process has an abnormality based on the logistics information. When it is determined that there is an abnormality, the merchant or user will contact the third party to confirm the abnormality in the task.

[0003] When implementing the technical solution based on the above method, the inventor found the following problems:

[0004] This method of monitoring logistics information tasks by merchants or users through a third party that updates the tasks is relatively passive, resulting in problems such as untimely discovery of anomalies and unclear abnormal nodes. At the same time, merchants or users are required to actively contact the third party to solve the problem, so there is a problem of low task processing efficiency, which leads to low user satisfaction and high complaint rates. Summary of the invention

[0005] The present invention provides a task processing method, device, electronic device and storage medium, which can improve the timeliness of abnormal monitoring, accurately locate abnormal nodes, and quickly provide abnormal feedback, thereby achieving the technical effect of improving task processing efficiency and improving user experience.

[0006] In a first aspect, an embodiment of the present invention provides a task processing method, the method comprising:

[0007] When it is detected that a processing exception exists in a pending task, and the abnormality reporting library does not include the reporting information corresponding to the pending task, an early warning work order is generated based on the pending task; wherein the abnormality reporting library includes the reporting information uploaded in advance by the task executor;

[0008] Sending the warning work order to the target collaborative platform, so as to send the pending task to the corresponding task executor based on the target collaborative platform, so that the task executor uploads the abnormality-related information to the target collaborative platform;

[0009] Receive the exception association information fed back by the target collaborative platform, and update the task association information of the task to be processed based on the exception association information, so as to determine whether there is a processing exception in the task to be processed based on the task association information.

[0010] Furthermore, the method further comprises:

[0011] Generate reporting information in the abnormal reporting library;

[0012] The generating of the report information in the abnormal report library includes:

[0013] When receiving a request for reporting an exception, multiple exception reporting templates are retrieved and fed back to the target collaborative platform for selection and editing;

[0014] Receive a target abnormality report template, analyze the abnormal content in the abnormality report template, and determine the report information;

[0015] The reporting information includes the abnormal area, abnormal cause, abnormal recovery time and task executor.

[0016] Furthermore, the method further comprises:

[0017] When receiving a task to be processed, determining whether the task to be processed includes a processing time limit;

[0018] If so, based on the processing time limit and the preset duration, the warning time limit corresponding to the task to be processed is updated to determine whether there is any processing abnormality in the task to be processed based on the warning time limit.

[0019] Furthermore, the method further comprises:

[0020] When it is detected that the pending task has not been processed when the warning time limit is reached, determining whether the abnormality reporting database includes reporting information corresponding to the pending task;

[0021] If not, the early warning work order is generated based on the pending task, wherein the early warning work order includes the early warning time limit and the task identifier of the pending task.

[0022] Furthermore, the method further comprises:

[0023] If the abnormality reporting library includes reporting information corresponding to the task to be processed, then based on the abnormality recovery duration in the reporting information, the task association information corresponding to the task to be processed is updated to determine whether there is a processing abnormality in the task to be processed based on the task association information;

[0024] The task-related information includes the updated warning time limit.

[0025] Furthermore, the method further comprises:

[0026] If the processing time limit is not included, the warning time limit is determined based on the processing time limit corresponding to the task initiator and the preset duration.

[0027] Furthermore, the method further comprises:

[0028] The abnormality-related information includes the abnormality cause and the abnormality recovery time.

[0029] Furthermore, the method further comprises:

[0030] Based on the abnormality association information, determine the abnormality level and the responsible party;

[0031] The updated task association information is fed back to the task initiator and / or the task delivery party corresponding to the task to be processed.

[0032] Furthermore, the method further comprises:

[0033] The tasks to be processed include pickup tasks or successful delivery tasks, and correspondingly, the warning time limit includes the pickup warning time limit or the successful delivery warning time limit.

[0034] Furthermore, the method further comprises:

[0035] The task to be processed is marked as a warning task, so that when processing information of the warning task is detected, the warning mark of the task to be processed is cancelled.

[0036] In a second aspect, an embodiment of the present invention further provides a task processing device, the device comprising:

[0037] An early warning work order generation module is used to generate an early warning work order based on the pending task when it is detected that there is a processing exception in the pending task and the abnormality reporting library does not include the reporting information corresponding to the pending task; wherein the abnormality reporting library includes the reporting information uploaded in advance by the task executor;

[0038] A work order sending module, used for sending the warning work order to a target collaborative platform, so as to send the pending task to a corresponding task executor based on the target collaborative platform, so that the task executor uploads the abnormality-related information to the target collaborative platform;

[0039] The information updating module is used to receive the abnormality-related information fed back by the target collaborative platform, and update the task-related information of the pending task based on the abnormality-related information, so as to determine whether there is any processing abnormality in the pending task based on the task-related information.

[0040] In a third aspect, an embodiment of the present invention further provides an electronic device, the electronic device comprising:

[0041] one or more processors;

[0042] a storage device for storing one or more programs,

[0043] When one or more programs are executed by one or more processors, the one or more processors implement any task processing method as in the embodiments of the present invention.

[0044] In a fourth aspect, an embodiment of the present invention further provides a storage medium comprising computer executable instructions, which, when executed by a computer processor, are used to perform a task processing method as described in any one of the embodiments of the present invention.

[0045] The technical solution of the embodiment of the present invention generates a warning work order based on the pending task when it is detected that there is a processing exception in the pending task and the reporting information corresponding to the pending task is not included in the abnormal reporting library; sends the warning work order to the target collaborative platform, so as to send the pending task to the corresponding task executor based on the target collaborative platform, so that the task executor uploads the abnormality-related information to the target collaborative platform; receives the abnormality-related information fed back by the target collaborative platform, and updates the task-related information of the pending task based on the abnormality-related information, so as to determine whether there is a processing exception in the pending task based on the task-related information. The technical solution of the embodiment of the present invention solves the problem of passive monitoring of tasks in the prior art, resulting in untimely abnormal monitoring, unclear abnormal nodes and low task processing efficiency, and realizes the improvement of the timeliness of abnormal monitoring by actively monitoring the processing abnormality of the pending task, and generates a warning work order and sends it to the target collaborative platform when it is determined that there is a processing exception and it is detected that the abnormal reporting library does not include the reporting information of the task executor on the pending task, so as to realize active warning. Furthermore, based on the target collaborative platform, exception feedback is given to the task executor. When the task executor learns of the exception, the exception-related information is uploaded to the target collaborative platform, and then the task is updated based on the exception-related information fed back by the target collaborative platform, the exception problem is clarified, and the exception is quickly fed back while accurately locating the abnormal node, thereby improving the task processing efficiency and achieving the technical effect of improving the user experience. BRIEF DESCRIPTION OF THE DRAWINGS

[0046] In order to more clearly illustrate the technical solutions of the exemplary embodiments of the present invention, the following briefly introduces the drawings required to describe the embodiments. Obviously, the drawings introduced are only drawings of a part of the embodiments to be described in the present invention, rather than all the drawings. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.

[0047] Figure 1 A flowchart of a task processing method provided by an embodiment of the present invention;

[0048] Figure 2 A schematic diagram of a task processing method provided by an embodiment of the present invention;

[0049] Figure 3 A schematic diagram of an abnormality reporting method provided by an embodiment of the present invention;

[0050] Figure 4 A schematic diagram of a task processing method provided by an embodiment of the present invention;

[0051] Figure 5 A flowchart of a task processing method provided by an embodiment of the present invention;

[0052] Figure 6 A schematic diagram of a method for processing a pickup task provided by an embodiment of the present invention;

[0053] Figure 7 A schematic diagram of a method for processing a successful delivery task provided by an embodiment of the present invention;

[0054] Figure 8 A flowchart of a task processing method provided by an embodiment of the present invention;

[0055] Fig. 9 is a schematic diagram of a task processing method provided by an embodiment of the present invention;

[0056] Fig.10 A schematic diagram of the structure of a task processing device provided by an embodiment of the present invention;

[0057] Fig.11 The present invention is a schematic diagram of the structure of an electronic device provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0058] The present invention will be further described in detail below in conjunction with the accompanying drawings and embodiments. It is to be understood that the specific embodiments described herein are only used to explain the present invention, rather than to limit the present invention. It should also be noted that, for ease of description, only parts related to the present invention, rather than all structures, are shown in the accompanying drawings.

[0059] Before introducing the present technical solution, the application scenario may be described first. Exemplarily, the technical solution provided by the embodiment of the present invention may be used to monitor the initiated order task, which may be initiated by the task initiator and processed based on the task executor. For example, if the task is a transport task, the carrier is the task executor, and the task initiator may be a merchant. In the process of processing the transport task based on the task executor, there is a need to monitor the transport task, and it is necessary to monitor whether there are any abnormalities in the transport task, so as to clarify the abnormal situation and handle the abnormality when it is abnormal. When monitoring the transport task, it can be implemented based on the technical solution provided in this embodiment.

[0060] Figure 1 A flowchart of a task processing method provided in an embodiment of the present invention is provided. This embodiment is applicable to the situation of monitoring abnormal tasks. The method can be executed by a task processing device, which can be implemented in the form of software and / or hardware. The hardware can be an electronic device, such as a mobile terminal, a PC or a server.

[0061] like Figure 1 As shown, the method includes:

[0062] S110: When it is detected that a processing exception exists in a task to be processed, and the exception reporting database does not include reporting information corresponding to the task to be processed, a warning work order is generated based on the task to be processed.

[0063] Among them, pending tasks may be tasks that need to be monitored for abnormalities. For example, delivery tasks generated after a user places an order, sorting tasks, pickup tasks when a third party picks up items, or delivery tasks when a item is delivered properly, etc. The abnormal reporting library includes reporting information uploaded by the task executor, which may be uploaded in advance or uploaded after the abnormality is detected. The reporting information includes but is not limited to the abnormal area, abnormal cause, abnormal recovery time, and the task executor. The abnormal cause may refer to the reason why the task is handled abnormally, such as bad weather, sudden accidents, traffic failures, holidays, damaged packages, etc. The abnormal recovery time refers to the time it takes for the abnormality to be recovered.

[0064] In actual applications, the system can regularly monitor the nodes (such as sorting nodes, shipping nodes, collection nodes, transfer nodes, and delivery nodes, etc.) when processing pending tasks, and use the information contained in the nodes to determine whether there are processing exceptions. Determining whether there are processing exceptions can be based on pre-set exception rules. Optionally, the exception rules can be: the status of the pending task is delivered within a very short time, in which case it can be considered that there is a distribution exception; or, the transport order number of the pending task is not compliant, in which case it can be considered that there is a technical exception; or, the processing time reaches the promised processing time and it is still not delivered, in which case it can be considered that there is a transportation exception; or, the shipment has not been shipped after the expected shipping time, in which case it can be considered that there is a shipping exception. When it is detected that there is a processing exception in the pending task, it is possible to query from the exception reporting library whether it contains reporting information that matches the pending task. If it does, it means that the task executor has proactively reported the exception; if it does not, it means that the task executor has not proactively reported it and an early warning notification is required. At this time, an early warning work order can be generated based on the pending task. The early warning work order may contain task information, transportation information, delivery information or overdue time, etc., so as to feedback the early warning work order to the task executor, inform him of the exception and determine the cause.

[0065] For example, see Figure 2 After setting the exception rules, you can perform exception monitoring based on the exception rules. When an abnormal task is detected, you can determine whether the abnormal task has been actively reported. If so, you can perform data analysis according to the system rules to locate the abnormal problem later. If not, generate an early warning work order and feedback it to the target collaborative platform to verify the abnormal problem with the task executor.

[0066] In this embodiment, the reporting information in the exception reporting library can be the reporting content actively reported by the task executor when the task executor clearly knows that there is a processing exception in the task to be processed, and the system generates the reporting information in the exception reporting library for unified management.

[0067] In this embodiment, the implementation method of generating the reporting information in the exception reporting library can be: when receiving a request to report an exception, calling up multiple exception reporting templates and feeding them back to the target collaborative platform for selection and editing; receiving the target exception reporting template, and analyzing the exception content in the exception reporting template to determine the reporting information.

[0068] The target collaboration platform may be a pre-developed work platform, in which the reporting information of tasks proactively reported by the task executor may be stored. The abnormal reporting template may refer to a general and standardized document template, which may contain multiple items to be filled in, and is used to guide users to fill in specific information for reporting to avoid missing information.

[0069] Specifically, when the task executor clearly knows that there is a processing exception in the pending task, the task executor can actively initiate a request to report the exception to the system based on the task executor. After receiving the request, the system can parse the request and select a suitable exception reporting template based on the information carried in the request (such as exception type, task executor, task type, etc.) and feedback it to the target collaborative platform. After the target collaborative platform receives the exception reporting template, the task executor can select the exception reporting template to be used and use the input device to edit the relevant information in the exception reporting template, such as the information of the transported goods, the abnormal area, the cause of the abnormality, the abnormal recovery time, and the task executor, etc. The edited exception reporting template can be fed back to the system as the target exception reporting template based on the target collaborative platform. When the system receives the target exception reporting template, it can analyze the abnormal content in the exception reporting template, determine the reporting information, and store the reporting information in the exception reporting library for management. The advantage of setting the exception reporting template is that it can not only guide the task executor to edit the reporting information through the exception reporting template to prevent the omission of important information, but also improve the convenience of reporting information management and improve work efficiency.

[0070] For example, see Figure 3 The task executor can report the route or waybill abnormality through the target collaboration platform when it is clear that there are force majeure, large festivals, traffic control and other factors that cause route or waybill abnormality. When reporting the waybill abnormality, the interface is called to obtain the order information (including the order number), and the order information is automatically filled in the abnormal report template as the report information and pushed to the system (i.e. the task processing system) so that the system can store the report information in the abnormal report library. For further information, see Figure 4 After the task executor has identified the exception, he or she can report the exception based on the target collaborative platform. He or she can also edit the exception content according to the exception report template and push the exception content to the system based on the interface in the target collaborative platform. The system collects the exception content so that the system can subsequently analyze the cause of the exception, locate the problem, issue warnings, and collaboratively resolve the exception based on the exception content.

[0071] S120, sending the early warning work order to the target collaborative platform, so as to send the pending task to the corresponding task executor based on the target collaborative platform, so that the task executor uploads the abnormality-related information to the target collaborative platform.

[0072] The abnormality-related information may include the abnormality cause and abnormality recovery time, etc.

[0073] Specifically, the system can send the warning work order to the target collaborative platform. After receiving the warning work order, the target collaborative platform will send the pending task and / or the warning work order to the task executor who handles the pending task, so that the task executor can be informed of the pending task with processing exceptions. The task executor edits the abnormality-related information corresponding to the pending task to report the abnormality, and then uploads the abnormality-related information to the target collaborative platform, so that the abnormality-related information is fed back to the system based on the target collaborative platform.

[0074] S130, receiving the exception association information fed back by the target collaborative platform, and updating the task association information of the task to be processed based on the exception association information, so as to determine whether there is a processing exception in the task to be processed based on the task association information.

[0075] In this embodiment, when the abnormal correlation information fed back by the target collaborative platform is received, the task correlation information of the pending task can be updated through the abnormal correlation information. For example, the task processing time limit is corrected according to the abnormal recovery time, and the monitoring is re-established. Subsequently, the pending task is detected based on the updated task correlation information to see whether there is any processing abnormality. It should be noted that after determining the updated task correlation information, it is also possible to determine whether an early warning is needed based on the task correlation information. For example, please continue to refer to Figure 2 After receiving the abnormal correlation information fed back by the target collaborative platform, the system can determine whether the warning rules are met based on the abnormal correlation information. If not, no warning is needed. If so, the system can receive warnings and process them based on multiple parties such as the task executor, task initiator, consumer, platform A, etc., to achieve collaborative processing of abnormal tasks by multiple parties and improve the effectiveness of task processing.

[0076] The technical solution of the embodiment of the present invention generates a warning work order based on the pending task when it is detected that there is a processing exception in the pending task and the reporting information corresponding to the pending task is not included in the abnormal reporting library; sends the warning work order to the target collaborative platform, so as to send the pending task to the corresponding task executor based on the target collaborative platform, so that the task executor uploads the abnormality-related information to the target collaborative platform; receives the abnormality-related information fed back by the target collaborative platform, and updates the task-related information of the pending task based on the abnormality-related information, so as to determine whether there is a processing exception in the pending task based on the task-related information. The technical solution of the embodiment of the present invention solves the problem of passive monitoring of tasks in the prior art, resulting in untimely abnormal monitoring, unclear abnormal nodes and low task processing efficiency, and realizes the improvement of the timeliness of abnormal monitoring by actively monitoring the processing abnormality of the pending task, and generates a warning work order and sends it to the target collaborative platform when it is determined that there is a processing exception and it is detected that the abnormal reporting library does not include the reporting information of the task executor on the pending task, so as to realize active warning. Furthermore, based on the target collaborative platform, exception feedback is given to the task executor. When the task executor learns of the exception, the exception-related information is uploaded to the target collaborative platform, and then the task is updated based on the exception-related information fed back by the target collaborative platform, the exception problem is clarified, and the exception is quickly fed back while accurately locating the abnormal node, thereby improving the task processing efficiency and achieving the technical effect of improving the user experience.

[0077] Figure 5 The flowchart of a task processing method provided by an embodiment of the present invention is based on the above embodiment. Before determining whether the task to be processed has an abnormality, it is also possible to detect whether the task to be processed includes a processing time limit. The processing time limit can represent the effective time of the processing task, so as to determine whether the warning requirements are met based on the processing time limit, and then determine whether the task to be processed has an abnormality. The specific implementation method can refer to the technical solution of this embodiment. Among them, the technical terms that are the same or corresponding to the above embodiment are not repeated here.

[0078] like Figure 5 As shown, the method specifically comprises the following steps:

[0079] S210: Receive tasks to be processed.

[0080] S220, determine whether the task to be processed includes a processing time limit, if so, execute step S230, if not, execute step S240.

[0081] In this embodiment, the processing time limit can be automatically determined when the pending task is generated, for example, it can be calculated based on the task information (for example: the starting point of the task processing, the destination corresponding to the task, and the items to be delivered contained in the task) based on big data technology; it can also be specified by the task initiator according to user needs; it can also be determined based on the actual processing time of the pending task. It should be noted that the processing time limit is related to the pending task. For example, if the pending task is a collection task, the processing time limit is the shipping time limit; if the pending task is a delivery task, the processing time limit is the delivery time limit.

[0082] In practical applications, before determining whether the processing time is included in the pending tasks, the processing time can also be written into the cache. Figure 6 , monitor the visible messages of pending tasks to establish a monitoring table, and monitor the delivery / delivery messages of the task executor. For example, the delivery message is: 2023\07\06 19:00, the merchant A shipped, and the message contains (order number: 12345678, waybill number: 222, shipping address: A area b floor, receiving address: B area b floor, merchant ID: A0, shipping warehouse: 010, delivery time is 2023\07\0920:00, so that when receiving the pending tasks, it can be judged whether the pending tasks contain the processing time limit.

[0083] S230: Based on the processing time limit and the preset duration, update the warning time limit corresponding to the task to be processed, so as to determine whether there is any processing abnormality in the task to be processed based on the warning time limit.

[0084] Among them, the preset duration can be determined according to the actual working situation or the user's demand for task warnings. For example, it can be 24 hours, which can be used to buffer the warning. The warning time limit can refer to the time when the pending task reaches the warning. It should be noted that the warning time limit corresponds to the task type of the pending task. For example, if the pending task is a collection task, the warning time limit includes the collection warning time limit. If the pending task is a delivery task, the warning time limit includes the delivery warning time limit.

[0085] Specifically, when the pending tasks include a processing time limit, the processing time limit and the preset time length may be accumulated, and the accumulated value may be used as the warning time limit corresponding to the pending tasks. Figure 6 If the delivery time limit is included, the pickup warning time limit is the delivery time limit + the preset duration. The warning time limit can be used to monitor whether there are any processing anomalies in the pending tasks. For example, when the warning time limit is reached, it can be considered that the pending tasks are about to time out or have timed out.

[0086] S240: Determine the warning time limit based on the processing time limit corresponding to the task initiator and the preset time length.

[0087] Specifically, if the processing time limit is not included in the pending tasks, the actual processing time of the pending tasks can be obtained as the processing time limit. The processing time limit and the preset time length are accumulated to obtain the accumulated value as the warning time limit. Figure 6 If the delivery time is not included, the collection warning time is the actual delivery time + the preset time.

[0088] S250. When it is detected that the task to be processed has not been processed before the warning time limit is reached, determine whether the abnormal reporting library includes reporting information corresponding to the task to be processed; if so, execute step S260; if not, execute step S270.

[0089] In this embodiment, when it is detected that the actual processing time of the task to be processed reaches the warning time limit, but the task to be processed has not been processed accordingly, it is considered that there is a risk that the task is about to time out or has timed out. At this time, it can be determined whether the abnormal reporting library includes the reporting information corresponding to the task to be processed. If so, step S260 is executed, and if not, step S270 is executed. If it is detected that the actual processing time of the task to be processed reaches the warning time limit, the task to be processed has been processed accordingly, and the abnormality is resolved without warning.

[0090] For example, see Figure 6 If the pickup warning time limit has not been reached, continue to traverse the pickup monitoring table for monitoring. If the pickup warning time limit has been reached, determine whether the item has been picked up. If so, no warning is required. If not, determine whether the active reporting information in the abnormal reporting database can be matched. It should be noted that the processing methods for pickup tasks and delivery tasks are basically the same. For a schematic diagram of the method for processing delivery tasks, see Figure 7 , I will not go into details here.

[0091] S260: Based on the abnormality recovery time in the reporting information, the task association information corresponding to the task to be processed is updated to determine whether there is a processing abnormality in the task to be processed based on the task association information.

[0092] Among them, the task-related information includes the updated warning time limit.

[0093] In this embodiment, if the exception reporting library includes reporting information corresponding to the pending task, it means that the task executor has reported the processing exception of the pending task in advance. At this time, the warning time limit in the task association information corresponding to the pending task can be updated through the exception recovery time in the reporting information. For example, the warning time limit adds the exception recovery time limit on the basis of the original warning time limit. Accordingly, an updated warning time limit is obtained to monitor whether there is a processing exception in the pending task through the updated warning time limit. Exemplarily, matching the reporting information in the exception reporting library, the matching results may include: order number: 12345678, waybill number: 222, first-level exception type: performance exception, second-level exception type: collection timeout, abnormal link: logistics point, abnormal reason: large festival, expected abnormal recovery time: 2023\07\10.

[0094] S270: Generate an early warning work order based on the pending tasks.

[0095] Among them, the warning work order includes the warning time limit and task identification of the task to be processed.

[0096] In this embodiment, if the exception reporting library does not include reporting information corresponding to the task to be processed, it means that the active exception reporting information of the task executor on the task to be processed cannot be matched. At this time, an early warning work order can be generated based on the early warning time limit of the task to be processed and the task identifier, and the early warning work order can be sent to the target collaborative platform. The target collaborative platform will send the abnormal task to be processed to the task executor, so that the task executor receives feedback related information about the abnormal task to be processed.

[0097] S280, sending the early warning work order to the target collaborative platform, so as to send the pending task to the corresponding task executor based on the target collaborative platform, so that the task executor uploads the abnormality-related information to the target collaborative platform.

[0098] S290, receiving the exception association information fed back by the target collaborative platform, and updating the task association information of the task to be processed based on the exception association information, so as to determine whether there is a processing exception in the task to be processed based on the task association information.

[0099] The technical solution of the embodiment of the present invention determines whether the pending task includes a processing time limit when receiving the pending task, and then determines the warning time limit based on the processing time limit and the preset duration, thereby ensuring the rationality of the warning time limit determination, and when the pending task has not been processed before the warning time limit is reached, determines from the abnormal reporting library whether the reporting information corresponding to the pending task is included, so that if it is not included, the task executor is warned so that the task executor can feedback the reporting information after receiving the warning message, thereby improving the effectiveness of task processing.

[0100] Figure 8A flowchart of a task processing method provided by an embodiment of the present invention, based on the above embodiment, after updating the task association information of the task to be processed based on the exception association information, the exception accountability can also be performed through the exception association information, and its specific implementation method can refer to the technical solution of this embodiment. Among them, the technical terms that are the same or corresponding to the above embodiment are not repeated here.

[0101] like Figure 8 As shown, the method includes:

[0102] S310: When it is detected that a processing exception exists in a task to be processed, and the exception reporting database does not include reporting information corresponding to the task to be processed, an early warning work order is generated based on the task to be processed.

[0103] S320, sending the warning work order to the target collaborative platform, so as to send the pending task to the corresponding task executor based on the target collaborative platform, so that the task executor uploads the abnormality-related information to the target collaborative platform.

[0104] S330, receiving the exception association information fed back by the target collaborative platform, and updating the task association information of the task to be processed based on the exception association information, so as to determine whether there is a processing exception in the task to be processed based on the task association information.

[0105] S340: Determine the abnormality level and the responsible party based on the abnormality association information.

[0106] In this embodiment, the cause of the abnormality can be analyzed and the problem can be located according to the abnormality association information, and the abnormality level and the responsible party can be determined. For example, an abnormality analysis rule can be pre-set, and the abnormality cause and abnormality recovery time carried in the abnormality association information can be automatically analyzed according to the abnormality analysis rule, and then the abnormality level can be determined according to the abnormality cause and abnormality recovery time, and which party is the responsible party. For an example of the abnormality analysis rule table, see Table 1 below.

[0107] Table 1

[0108]

[0109] Continue to see Figure 6 After sending the warning work order to the target collaborative platform, the task executor can classify the abnormality according to the abnormality analysis rule table, combined with the abnormality cause and recovery time fed back by the target collaborative platform, for example, abnormality level: Level 2; responsible party: task executor. After the abnormality classification and responsible party determination, the processing results (such as refund, return, reminder, reissue, etc.) can also be communicated to the task initiator, task executor, consumer and other parties.

[0110] S350: Feedback the updated task association information to the task initiator and / or task delivery party corresponding to the task to be processed.

[0111] Among them, the task delivery party can correspond to the task executor.

[0112] Specifically, the task association information carrying the updated warning time limit can be fed back to the task initiator and / or task delivery party corresponding to the task to be processed, so that the task initiator and / or task delivery party can promptly understand the task association information of the task to be processed, so as to pay timely attention to and deal with the task to be processed accordingly.

[0113] In order to increase the attention to abnormal pending tasks and ensure the real-time status of pending tasks, when it is determined that there is an abnormality in the pending task, the task status of the pending task can be marked as a warning, and when the pending task is successfully processed, its warning mark can be cancelled. Specifically, the pending task can be marked as a warning task, so that when the processing information of the warning task is detected, the warning mark of the pending task can be cancelled.

[0114] In this embodiment, when it is determined that a pending task has a processing anomaly, the task can be marked as an early warning task. On this basis, the processing information of the early warning task can be monitored in real time. If the processing information of the early warning task is detected, the early warning mark of the pending task is cancelled and the early warning is lifted.

[0115] The technical solution of the embodiment of the present invention determines the abnormal level and the responsible party based on the abnormal association information, which facilitates the subsequent abnormal accountability and processing. At the same time, the updated task association information is fed back to the task initiator and / or task delivery party corresponding to the task to be processed, so that the task initiator and / or task delivery party can perform emergency operations and processing on the task in a timely and effective manner after receiving the information, so that the abnormality can be resolved in time to improve user satisfaction.

[0116] As an alternative embodiment of the above embodiment, Fig. 9 FIG. 1 is a schematic diagram of a task processing method provided according to an embodiment of the present invention. For details, please refer to the following specific content.

[0117] like Fig. 9As shown, the task processing method provided by the embodiment of the present invention can be implemented based on the task processing system. Among them, the task processing system includes but is not limited to a task flow module, a data precipitation module, an abnormal monitoring module, an abnormal warning module, and an abnormal release module. In practical applications, the task flow process monitoring (including the delivery / collection process, the transportation process, and the dispatch / delivery process) can be performed based on the task flow module, and the delivery time and task download time can be calculated based on the delivery / collection process. The delivery time and delivery time can be calculated based on the transportation process and the dispatch / delivery process, and then these information are sent to the data precipitation module. Based on the information sent by the task flow module received by the data precipitation module, the performance plan data of the pending task and the performance operation data are generated and sent to the abnormal monitoring module. Based on the abnormal monitoring module, the abnormal rules are defined according to the business, combined with the abnormal reporting information of the task executor (such as line, waybill abnormalities) and the performance plan data and performance operation data, abnormal monitoring, abnormal identification, and abnormal attribution processing are performed to build an abnormal indicator system. For example, fulfillment anomalies include timeouts and delayed orders; operational anomalies include false pickup, signature / loss, and damage; information anomalies include missing logistics tracks and terminal failures. Furthermore, when an abnormal task is detected, an alarm can be generated based on the abnormal warning module, and the data dashboard can be used to visualize the fulfillment anomaly. For example, the abnormal warning is assigned to the task initiator (merchant side) and the task executor (logistics side), and the task initiator is given a shipment reminder, delayed shipment report, and shipment timeout warning; the task executor is given a logistics stagnation warning, a delivery abnormality warning, an advance pickup warning, a pickup timeout warning, and a loss and damage warning. After the task initiator and the task executor receive the warning, the anomaly can be collaboratively processed. For example, the task initiator performs the outbound operation, and the task executor performs the pickup operation, logistics stagnation feedback, delivery / rejection feedback, etc., so that the anomaly is resolved and fed back to the consumer, realizing the data intercommunication between the three parties, improving the efficiency of abnormal task processing, and thus achieving the effect of improving user experience.

[0118] Fig.10 This is a structural diagram of a task processing device provided by an embodiment of the present invention. The device includes: an early warning work order generating module 410, a work order sending module 420 and an information updating module 430.

[0119] The warning work order generation module 410 is used to generate a warning work order based on the pending task when it is detected that there is a processing exception in the pending task and the abnormality reporting library does not include the reporting information corresponding to the pending task; wherein the abnormality reporting library includes the reporting information uploaded in advance by the task executor;

[0120] The work order sending module 420 is used to send the warning work order to the target collaborative platform, so as to send the pending task to the corresponding task executor based on the target collaborative platform, so that the task executor uploads the abnormality-related information to the target collaborative platform;

[0121] The information updating module 430 is used to receive the exception association information fed back by the target collaborative platform, and update the task association information of the pending task based on the exception association information, so as to determine whether there is any processing exception in the pending task based on the task association information.

[0122] Based on the above device, the device further includes a reporting information generation module, and the reporting information generation module is used to generate the reporting information in the abnormal reporting library.

[0123] Based on the above device, the reporting information generation module includes an abnormal reporting template feedback unit and a reporting information determination unit.

[0124] An exception reporting template feedback unit is used to retrieve multiple exception reporting templates when receiving a request to report an exception, and feed them back to the target collaborative platform for selection and editing;

[0125] A reporting information determining unit, configured to receive a target abnormality reporting template, analyze the abnormal content in the abnormality reporting template, and determine the reporting information;

[0126] The reporting information includes the abnormal area, abnormal cause, abnormal recovery time and task executor.

[0127] On the basis of the above-mentioned device, the device also includes a warning time limit determination module, which is used to determine whether the pending task includes a processing time limit when receiving the pending task; if so, based on the processing time limit and the preset duration, update the warning time limit corresponding to the pending task to determine whether there is any processing abnormality in the pending task based on the warning time limit.

[0128] Based on the above-mentioned device, the early warning work order generation module 410 is specifically used to determine whether the abnormal reporting library includes reporting information corresponding to the pending task when it is detected that the pending task has not been processed when the early warning period is reached; if not, the early warning work order is generated based on the pending task, wherein the early warning work order includes the early warning period and task identifier of the pending task.

[0129] Based on the above-mentioned device, the early warning work order generation module 410 is also used to update the task association information corresponding to the task to be processed based on the abnormal recovery time in the reporting information if the abnormal reporting library includes reporting information corresponding to the task to be processed, so as to determine whether there is a processing abnormality in the task to be processed based on the task association information; wherein the task association information includes the updated early warning time limit.

[0130] Based on the above device, the warning time limit determination module is further used to determine the warning time limit based on the processing time limit corresponding to the task initiator and the preset time length if the processing time limit is not included.

[0131] Based on the above device, the abnormality association information includes the abnormality cause and the abnormality recovery time.

[0132] Based on the above device, the device also includes an abnormality judgment module and a related information feedback module.

[0133] An abnormality judgment module is used to determine the abnormality level and the responsible party based on the abnormality association information;

[0134] The associated information feedback module is used to feed back the updated task associated information to the task initiator and / or task delivery party corresponding to the task to be processed.

[0135] On the basis of the above-mentioned device, the tasks to be processed include pickup tasks or successful delivery tasks, and correspondingly, the warning time limit includes pickup warning time limit or successful delivery warning time limit.

[0136] Based on the above device, the device also includes a warning marking module.

[0137] The early warning marking module is used to mark the task to be processed as an early warning task, so as to cancel the early warning mark of the task to be processed when processing information of the early warning task is detected.

[0138] The technical solution of the embodiment of the present invention generates a warning work order based on the pending task when it is detected that there is a processing exception in the pending task and the reporting information corresponding to the pending task is not included in the abnormal reporting library; sends the warning work order to the target collaborative platform, so as to send the pending task to the corresponding task executor based on the target collaborative platform, so that the task executor uploads the abnormality-related information to the target collaborative platform; receives the abnormality-related information fed back by the target collaborative platform, and updates the task-related information of the pending task based on the abnormality-related information, so as to determine whether there is a processing exception in the pending task based on the task-related information. The technical solution of the embodiment of the present invention solves the problem of passive monitoring of tasks in the prior art, resulting in untimely abnormal monitoring, unclear abnormal nodes and low task processing efficiency, and realizes the improvement of the timeliness of abnormal monitoring by actively monitoring the processing abnormality of the pending task, and generates a warning work order and sends it to the target collaborative platform when it is determined that there is a processing exception and it is detected that the abnormal reporting library does not include the reporting information of the task executor on the pending task, so as to realize active warning. Furthermore, based on the target collaborative platform, exception feedback is given to the task executor. When the task executor learns of the exception, the exception-related information is uploaded to the target collaborative platform, and then the task is updated based on the exception-related information fed back by the target collaborative platform, the exception problem is clarified, and the exception is quickly fed back while accurately locating the abnormal node, thereby improving the task processing efficiency and achieving the technical effect of improving the user experience.

[0139] The task processing device provided in the embodiment of the present invention can execute the task processing method provided in any embodiment of the present invention, and has the corresponding functional modules and beneficial effects of the execution method.

[0140] It is worth noting that the various units and modules included in the above system are only divided according to functional logic, but are not limited to the above division, as long as the corresponding functions can be achieved; in addition, the specific names of the functional units are only for the convenience of distinguishing each other, and are not used to limit the protection scope of the embodiments of the present invention.

[0141] Fig.11 The present invention is a schematic diagram of the structure of an electronic device provided by an embodiment of the present invention. Fig.11 A block diagram of an exemplary electronic device 50 suitable for implementing exemplary embodiments of the present invention is shown. Fig.11 The electronic device 50 shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present invention.

[0142] like Fig.11As shown, the electronic device 50 is in the form of a general computing device. The components of the electronic device 50 may include but are not limited to: one or more processors or processing units 501, a system memory 502, and a bus 503 connecting different system components (including the system memory 502 and the processing unit 501).

[0143] Bus 503 represents one or more of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, a processor or a local bus using any of a variety of bus structures. For example, these architectures include but are not limited to Industry Standard Architecture (ISA) bus, Micro Channel Architecture (MAC) bus, Enhanced ISA bus, Video Electronics Standards Association (VESA) local bus and Peripheral Component Interconnect (PCI) bus.

[0144] The electronic device 50 typically includes a variety of computer system readable media. These media can be any available media that can be accessed by the electronic device 50, including volatile and non-volatile media, removable and non-removable media.

[0145] System memory 502 may include computer system readable media in the form of volatile memory, such as random access memory (RAM) 504 and / or cache memory 505. Electronic device 50 may further include other removable / non-removable, volatile / non-volatile computer system storage media. By way of example only, storage system 506 may be used to read and write non-removable, non-volatile magnetic media ( Fig.11 not shown, usually called a "hard drive"). Although Fig.11 Not shown in the figure, a disk drive for reading and writing to a removable non-volatile disk (e.g., a "floppy disk"), and an optical disk drive for reading and writing to a removable non-volatile optical disk (e.g., a CD-ROM, a DVD-ROM, or other optical media) may be provided. In these cases, each drive may be connected to the bus 503 via one or more data medium interfaces. The memory 502 may include at least one program product having a set (e.g., at least one) of program modules that are configured to perform the functions of the embodiments of the present invention.

[0146] A program / utility 508 having a set (at least one) of program modules 507 may be stored, for example, in the memory 502, such program modules 507 including but not limited to an operating system, one or more application programs, other program modules, and program data, each of which or some combination may include an implementation of a network environment. The program modules 507 generally perform the functions and / or methods of the embodiments described herein.

[0147] The electronic device 50 may also communicate with one or more external devices 509 (e.g., keyboards, pointing devices, displays 510, etc.), may communicate with one or more devices that enable a user to interact with the electronic device 50, and / or communicate with any device that enables the electronic device 50 to communicate with one or more other computing devices (e.g., a network card, a modem, etc.). Such communication may be performed through an input / output (I / O) interface 511. Furthermore, the electronic device 50 may also communicate with one or more networks (e.g., a local area network (LAN), a wide area network (WAN), and / or a public network, such as the Internet) through a network adapter 512. As shown, the network adapter 512 communicates with other modules of the electronic device 50 through the bus 503. It should be understood that although Fig.11 Not shown, other hardware and / or software modules may be used in conjunction with the electronic device 50, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems.

[0148] The processing unit 501 executes various functional applications and data processing by running the programs stored in the system memory 502, such as implementing the task processing method provided in the embodiment of the present invention.

[0149] An embodiment of the present invention further provides a storage medium containing computer executable instructions, and when the computer executable instructions are executed by a computer processor, they are used to perform a task processing method, the method comprising:

[0150] When it is detected that a processing exception exists in a pending task, and the abnormality reporting library does not include the reporting information corresponding to the pending task, an early warning work order is generated based on the pending task; wherein the abnormality reporting library includes the reporting information uploaded in advance by the task executor;

[0151] Sending the warning work order to the target collaborative platform, so as to send the pending task to the corresponding task executor based on the target collaborative platform, so that the task executor uploads the abnormality-related information to the target collaborative platform;

[0152] Receive the exception association information fed back by the target collaborative platform, and update the task association information of the task to be processed based on the exception association information, so as to determine whether there is a processing exception in the task to be processed based on the task association information.

[0153] The computer storage medium of the embodiment of the present invention can adopt any combination of one or more computer-readable media. The computer-readable medium can be a computer-readable signal medium or a computer-readable storage medium. The computer-readable storage medium can be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination of the above. More specific examples (non-exhaustive list) of computer-readable storage media include: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In this document, a computer-readable storage medium can be any tangible medium containing or storing a program, which can be used by an instruction execution system, device or device or used in combination with it.

[0154] Computer-readable signal media may include data signals propagated in baseband or as part of a carrier wave, which carry computer-readable program code. Such propagated data signals may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. Computer-readable signal media may also be any computer-readable medium other than a computer-readable storage medium, which may send, propagate, or transmit a program for use by or in conjunction with an instruction execution system, apparatus, or device.

[0155] Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.

[0156] Computer program code for performing the operation of embodiments of the present invention may be written in one or more programming languages ​​or a combination thereof, including object-oriented programming languages, such as Java, Smalltalk, C++, and conventional procedural programming languages, such as "C" or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, as an independent software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer via any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0157] Note that the above are only preferred embodiments of the present invention and the technical principles used. Those skilled in the art will understand that the present invention is not limited to the specific embodiments herein, and that various obvious changes, readjustments and substitutions can be made by those skilled in the art without departing from the scope of protection of the present invention. Therefore, although the present invention has been described in more detail through the above embodiments, the present invention is not limited to the above embodiments, and may include more other equivalent embodiments without departing from the concept of the present invention, and the scope of the present invention is determined by the scope of the appended claims.

Claims

1. A task processing method, characterized in that: include: When it is detected that a processing exception exists in a pending task, and the abnormality reporting library does not include the reporting information corresponding to the pending task, an early warning work order is generated based on the pending task; wherein the abnormality reporting library includes the reporting information uploaded in advance by the task executor; Sending the warning work order to the target collaborative platform, so as to send the pending task to the corresponding task executor based on the target collaborative platform, so that the task executor uploads the abnormality-related information to the target collaborative platform; Receive the exception association information fed back by the target collaborative platform, and update the task association information of the task to be processed based on the exception association information, so as to determine whether there is a processing exception in the task to be processed based on the task association information.

2. The method according to claim 1, characterized in that Also includes: Generate reporting information in the abnormal reporting library; The generating of the report information in the abnormal report library comprises: When receiving a request for reporting an exception, multiple exception reporting templates are retrieved and fed back to the target collaborative platform for selection and editing; Receive a target abnormality report template, analyze the abnormal content in the abnormality report template, and determine the report information; The reporting information includes the abnormal area, abnormal cause, abnormal recovery time and task executor.

3. The method according to claim 1, characterized in that Before determining whether the task to be processed is abnormal, the method further includes: When receiving a task to be processed, determining whether the task to be processed includes a processing time limit; If so, based on the processing time limit and the preset duration, the warning time limit corresponding to the task to be processed is updated to determine whether there is any processing abnormality in the task to be processed based on the warning time limit.

4. The method according to claim 3, characterized in that: When it is detected that a processing exception exists in a task to be processed, and the abnormality reporting library does not include reporting information corresponding to the task to be processed, generating an early warning work order based on the task to be processed includes: When it is detected that the pending task has not been processed when the warning time limit is reached, determining whether the abnormality reporting database includes reporting information corresponding to the pending task; If not, the early warning work order is generated based on the pending task, wherein the early warning work order includes the early warning time limit and the task identifier of the pending task.

5. The method according to claim 4, characterized in that The method further comprises: If the abnormality reporting library includes reporting information corresponding to the task to be processed, then based on the abnormality recovery duration in the reporting information, the task association information corresponding to the task to be processed is updated to determine whether there is a processing abnormality in the task to be processed based on the task association information; The task-related information includes the updated warning time limit.

6. The method according to claim 3, characterized in that Also includes: If the processing time limit is not included, the warning time limit is determined based on the processing time limit corresponding to the task initiator and the preset duration.

7. The method according to claim 1, characterized in that The abnormality-related information includes the abnormality cause and the abnormality recovery time.

8. The method according to claim 7, characterized in that After the task association information of the to-be-processed task is updated based on the abnormal association information, the method further includes: Determine the abnormality level and the responsible party based on the abnormality association information; The updated task association information is fed back to the task initiator and / or the task delivery party corresponding to the task to be processed.

9. The method according to claim 1, characterized in that: The tasks to be processed include pickup tasks or successful delivery tasks, and correspondingly, the warning time limit includes the pickup warning time limit or the successful delivery warning time limit.

10. The method according to claim 1, characterized in that Also includes: The task to be processed is marked as a warning task, so that when processing information of the warning task is detected, the warning mark of the task to be processed is cancelled.

11. A task processing device, characterized in that: include: An early warning work order generation module is used to generate an early warning work order based on the pending task when it is detected that there is a processing exception in the pending task and the abnormality reporting library does not include the reporting information corresponding to the pending task; wherein the abnormality reporting library includes the reporting information uploaded in advance by the task executor; A work order sending module, used for sending the warning work order to a target collaborative platform, so as to send the pending task to a corresponding task executor based on the target collaborative platform, so that the task executor uploads the abnormality-related information to the target collaborative platform; The information updating module is used to receive the abnormality-related information fed back by the target collaborative platform, and update the task-related information of the pending task based on the abnormality-related information, so as to determine whether there is any processing abnormality in the pending task based on the task-related information.

12. An electronic device, characterized in that: The electronic device comprises: one or more processors; a storage device for storing one or more programs, When the one or more programs are executed by the one or more processors, the one or more processors implement the task processing method according to any one of claims 1 to 10.

13. A storage medium comprising computer executable instructions, wherein the computer executable instructions are used to perform the task processing method according to any one of claims 1 to 10 when executed by a computer processor.

Images